umts signalling.pdf

8/10/2019 UMTS signalling.pdf

1/75

TSG-RAN Working Group 3 RP-99348RAN meeting #4 - Miami

Agenda:

Source: Editor (CSELT)

Title: 25.931 v1.1.1UTRAN Functions, Examples on Signalling Procedures

Note: This version includes (as revision marks) the updates and the modification agreed at the RAN WG3 meeting#4 (Warwick, June 99).These changes have not yet been approved in RAN WG3


2/75


3/75

Reference

(.PDF)

Keywords

3GPP

Postal address

Office address

Internet

[email protected] copies of this deliverable

can be downloaded from

http://www.3gpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.

All rights reserved.


4/75

25.931 V1.1.0 1 1999-065

Contents

1. Intellectual Property Rights........................................................................................................................ 7

2. Foreword .................................................................................................................................................... 7

3. Scope.......................................................................................................................................................... 7

4. References..................................................................................................................................................7

5. Definitions, abbreviations and notation ..................................................................................................... 85.1 Definitions............................................................................................................................................................ 8

5.2 Abbreviations........................................................................................................................................................ 8

5.3 Notation for the signalling procedures.................................................................................................................. 8

6. UTRAN AND UE PROTOCOL ARCHITECTURE...............................................................................10

6.1 Protocol Architecture.......................................................................................................................................... 106.2 RANAP Procedures & Messages........................................................................................................................ 11

6.3 RNSAP Procedures & Messages........................................................................................................................ 12

6.4 NBAP Procedures & Messages .......................................................................................................................... 12

6.5 ALCAP............................................................................................................................................................... 13

6.5.1 Q2630.1 (Q.AAL 2) ................................................................................................................................... 13

6.6 RRC Procedures & Messages............................................................................................................................. 14

7. UTRAN Signaling Procedures................................................................................................................. 16

8. Procedures not related to a specific UE (global procedures)................................................................... 168.1 System Information Broadcasting....................................................................................................................... 16

9. Procedures related to a specific UE ......................................................................................................... 16

9.1 Paging................................................................................................................................................................. 179.1.1 Paging for a UE in RRC Idle Mode ........................................................................................................... 17

9.1.2 Paging for a UE in RRC Connected Mode................................................................................................. 17

9.2 NAS Signalling Connection Establishment ........................................................................................................ 18

9.2.1 UE Initiated Signalling Connection Establishment .................................................................................... 18

9.2.2 CN Initiated Signalling Connection Establishment .................................................................................... 19

9.3 RRC Connection Establishment.......................................................................................................................... 19

9.3.1 DCH Establishment.................................................................................................................................... 19

9.3.2 RACH/FACH Establishment...................................................................................................................... 20

9.4 RRC Connection Release.................................................................................................................................... 20

9.4.1 DCH Release.................................................................................................................................................. 20

9.4.2 Common Transport Channel Release ......................................................................................................... 21

9.5 RRC Connection Re-establishment..................................................................................................................... 21

9.5.1 DCH Re-establishment............................................................................................................................... 219.5.2 RACH/FACH Re-establishment................................................................................................................. 23

9.6 Radio Access Bearer Establishment ................................................................................................................... 23

9.6.1 DCH - DCH Establishment - Synchronized ............................................................................................... 23

9.6.2 DCH - DCH Establishment - Unsynchronized (PSTN/ISDN Core Network............................................. 25

9.6.3 RACH/FACH - DCH Establishment.......................................................................................................... 27

9.6.4 RACH/FACH - RACH/FACH Establishment............................................................................................ 28

9.7 Radio Access Bearer Release ............................................................................................................................. 28

9.7.1 DCH - DCH Release - Synchronized ......................................................................................................... 28

9.7.2 DCH - DCH Release - Unsynchronized..................................................................................................... 30

9.7.3 DCH - RACH/FACH Release .................................................................................................................... 32

9.7.4 RACH/FACH - RACH/FACH Release...................................................................................................... 32

9.8 Radio Access Bearer Re-establishment .............................................................................................................. 329.8.1 DCH - DCH Re-establishment ................................................................................................................... 32

9.8.2 RACH/FACH - DCH Re-establishment ..................................................................................................... 32

9.8.3 RACH/FACH - RACH/FACH Re-establishment....................................................................................... 32


5/75

25.931 V1.1.0 1 1999-066

9.9 Radio Access Bearer Modification..................................................................................................................... 33

9.9.1 DCH to DCH Modification........................................................................................................................ 34

9.9.2 RACH/FACH TO RACH/FACH Reconfiguration..................................................................................... 35

9.9.3 RACH/FACH TO DCH Reconfiguration................................................................................................... 35

9.9.4 DCH TO RACH/FACH RECONFIGURATION....................................................................................... 36

9.10 Physical Channel Reconfiguration................................................................................................................... 37

9.11 Channel Type Switching.................................................................................................................................. 379.11.1 RACH/PCH to RACH/FACH.................................................................................................................... 37

9.11.2 RACH/FACH to RACH/PCH .................................................................................................................... 38

9.11.3 RACH/FACH to DCH................................................................................................................................ 38

9.11.4 DCH to RACH/FACH................................................................................................................................ 39

9.12 Soft Handover.................................................................................................................................................. 39

9.12.1 Radio Link Addition (Branch Addition) .................................................................................................... 40

9.12.2 Radio link Deletion (Branch Deletion)....................................................................................................... 41

9.12.3 Radio link Addition & Deletion (Branch Addition & Deletion - simultaneously) ..................................... 42

9.13 Hard Handover ................................................................................................................................................ 43

9.13.1 Backward Hard Handover.......................................................................................................................... 43

9.13.2 Forward Hard Handover ............................................................................................................................ 49

9.14 URA Update .................................................................................................................................................... 51

9.14.1 Inter-RNS URA Update with SRNS Relocation ........................................................................................ 51

9.14.2 Inter-RNS URA Update via Iur without SRNS relocation ......................................................................... 52

9.14.3 SRNS Relocation (UE connected to two CN nodes).................................................................................. 53

9.15 HO between UTRAN and GSM/BSS .............................................................................................................. 55

9.15.1 UTRANGSM/BSS ............................................................ .............................................................. ..... 55

9.15.2 GSM/BSSUTRAN .................................................... ............................................................ ............... 57

9.15.3 UTRANGPRS........................................................... ............................................................ ............... 58

9.15.4 UTRANGSM/BSS ........................................................... .............................................................. ...... 59

9.16 Load Indication................................................................................................................................................ 60

9.17 Ciphering ......................................................................................................................................................... 60

9.18 Transport CH Reconfiguration ........................................................................................................................ 61

9.18.1 Transport CH Reconfiguration (Dedicated CH to Dedicated CH)............................................................. 61

9.18.2 Transport CH Reconfiguration (RACH/FACH to RACH/FACH) ............................................................. 629.18.3 Transport CH Reconfiguration (RACH/FACH to Dedicated CH)............................................................. 63

9.18.4 Transport CH Reconfiguration (Dedicated CH to RACH/FACH)............................................................. 64

9.19 Notification...................................................................................................................................................... 65

9.20 DL Code Reconfiguration................................................................................................................................ 66

9.21 Direct Transfer................................................................................................................................................. 67

9.21.1 Uplink Direct Transfer ............................................................................................................................... 67

9.21.2 Downlink Direct Transfer .......................................................................................................................... 68

9.22 Downlink Power Control ................................................................................................................................. 69

10. ANNEX: status of the document...........................................................................................................74


6/75


7/75

25.931 V1.1.0 1 1999-068

[7] 25.424 UTRAN IurInterface RNSAP Signalling

[8] 25.434 UTRAN IubInterface NBAB Signalling

[9] 25.832 Manifestations of Handover and SRNS Relocation

[10] UMTS YY.01 MS-UTRAN Radio Interface Protocol Architecture

[14] UMTS YY.31 Description of RRC protocol

Editor note: reference [10] and [14] should be updated, the numbering will be updated when the list will be stable

5.Definitions, abbreviations and notation

5.1Definitions

Refer to [5].

5.2Abbreviations

For the purposes of this specification the following abbreviations apply.

ALCAP Access Link Control Application Part

AS Access Stratum

BSSMAP Base Station System Management Application Part

CN Core Network

CRNC Controlling RNC

DCH Dedicated Channel

DRNS Drift RNS

L1 Layer 1

MAC Medium Access Control

MSC Message Sequence Chart

NAS Non Access Stratum

NBAP Node B Application Protocol

PCH Paging Channel

RAB Radio Access Bearer

RACH Random Access Channel

RANAP Radio Access Network Application Part

RLC Radio Link ControlRNC Radio Network Controller

RNS Radio Network Subsystem

RNSAP Radio Network Subsystem Application Part

RRC Radio Resource Control

SRNS Serving RNS

UE User Equipment

UMTS Universal Mobile Telecommunication System

UTRAN UMTS Terrestrial Radio Access Network

5.3Notation for the signalling procedures

Complex signalling procedures may involve several protocols in different nodes.

In order to facilitate the understanding of these procedures, the following rules in the drawing of Message Sequence

Chart (MSC) are applied:


8/75

25.931 V1.1.0 1 1999-069

Messages are always exchanged between nodes, i.e. the sender and the receiver of a message are nodes and notsingle protocol entities;

The protocol entity inside a node that is sending/receiving a message is represented by means of an ellipse,

containing the protocol entity name;

Each message is numbered, so that a numbered list with explanations can be added below the figure;

Message parameters may be specified as shown in Figure 1 only when required for a clear understanding of theprocedures;

Explicit signalling is represented by means of continuos arrows.

Inband signalling is represented by means of dotted arrows.

A description of the relevant actions may be included as shown in Figure 1.

The Setup and Release of Iub/Iur and Iu Data Transport Bearer with the ALCAP protocol is represented as shown

in Figure 1.

The transport channel used by the MAC protocol or the logical channel used by the RLC and RRC protocols maybe indicated before the message name as shown in Figure 1.

UE N ode B

Dr ift R NS

Node B

Serving RNS

RN C

D rif t

RN C

Serving

CN

NBAP

M AC

NBAP

RA NAP RAN AP

RN SAP RNSAP

M A C1. R AC H : Message

RR CRR C2. C CC H : Message

3. Message

6. Message

5. Message

[Parameters]

[Parameters]

[Parameters]

[Parameters]

[Parameters]

Action description

NBAPNBAP4. Message

[Parameters]

ALCA P Iub Bearer Setup/Release A LCA P Iur Bearer Setup

DCH DSDCH DS7. DCH Data Frame

[Parameters]

Figure 1: Example of signalling procedure notation


9/75

25.931 V1.1.0 1 1999-0610

6.UTRAN AND UE PROTOCOL ARCHITECTURE

Protocol Architecture

The complete UTRAN and UE protocol architecture for the control plane (including the transport layers) is shown in

Figure 2 (idle mode) and Figure 3 (connected mode). For a detailed description of the UTRAN Protocol Architecture

and of the Radio Protocol Architecture refer to [5] and [10] respectively.

RRC NBAP NBAP RANAP

UE Node B CRNC CNUu Iub Iu

Transport Layers Transport Layers

RANAP

Transport Layers

RRC

BCH, PCH

BCCH, PCCH

Figure 2: UTRAN and UE control plane protocol architecture (idle mode)

RRC NBAP NBAP

UE Node B SRNC CNUu Iub Iur Iu

Transport Layers Transport Layer Transport Layers

RRCRNSAP RANAPRANAP

Transport Layers

RNSAP

DRNC

DCH, RACH, FACH, DSCH

RACH, FACH

DCCH

CCCH, DCCH

Figure 3: UTRAN and UE control plane protocol architecture (connected mode)


10/75

25.931 V1.1.0 1 1999-0611

RANAP Procedures & Messages

For a detailed description of RANAP procedures and messages refer to [6].

Editor note: to be aligned with the protocol specification documents

Message Name UTRAN Procedure Direction

Initial UE Message NAS Signalling Connection Establish. Source RNCCN

RAB Assignment Request RAB Establishment

RAB Release

Inter-RNS HO with switching in the CN

CNSource RNC

CNSource RNC

CNSource RNC

RAB Assignment Complete RAB Establishment

RAB Release

Source RNCCN

Source RNCCN

Relocation Required Hard HO with switching in the CN

UTRANGSM/BSS handover

SRNS Relocation

Source RNCCN

Source RNCCN

Source RNCCN

Relocation Request Hard HO with switching in the CN


GSM/BSS handoverUTRAN

SRNS Relocation

CNTarget RNC

CNSource RNC

CNTarget RNC

CNTarget RNC

Relocation Request Acknowlede Hard HO with switching in the CN


SRNS Relocation

Target RNCCN

Target RNCCN

Target RNCCN

Relocation Command Hard HO with switching in the CN

SRNS Relocation

CNSource RNC

CNSource RNC

Relocation Detect Hard HO with switching in the CN


Target RNCCN

Target RNCCN

Relocation Complete Hard HO with switching in the CN


SRNS Relocation

Target RNCCN

Target RNCCN

Target RNCCN

Relocation Failure SRNS Relocation RNCCN

Iu Release Command Hard HO with switching in the CN

SRNS Relocation


CNSource RNC

CNSource RNC

CNSource RNC

Iu Release Complete Hard HO with switching in the CN Source RNCCN


11/75

25.931 V1.1.0 1 1999-0612

SRNS Relocation


Source RNCCN

Source RNCCN

Paging Paging CNSRNC

RNSAP Procedures & Messages

For a detailed description of RNSAP procedures and messages refer to [7].



Radio Link Reconfiguration

Prepare

RAB Establishment

RAB Release

SRNCDRNC

SRNCDRNC

Radio Link Reconfiguration Ready RAB Establishment

RAB Release

DRNCSRNC

DRNCSRNC

Radio Link Reconfiguration RAB Establishment

RAB Release

SRNCDRNC

SRNCDRNC


Response

RAB Establishment

RAB Release

DRNCSRNC

DRNCSRNC


Commit

RAB Establishment

RAB Release

SRNCDRNC

SRNCDRNC

Radio Link Addition Soft Handover SRNCDRNC

Radio Link Addition Response Soft Handover DRNCSRNC

Radio Link Deletion Soft Handover SRNCDRNC

Radio Link Deletion Response Soft Handover DRNCSRNC

SRNS Relocation Commit SRNS Relocation Source RNCTarget

RNC

NBAP Procedures & Messages

For a detailed description of NBAP procedures and messages refer to [8].



Radio Link Setup RRC Connection Establishment RNCNode B


12/75

25.931 V1.1.0 1 1999-0613

Hard Handover

Soft Handover

RNCNode B

RNCNode B

Radio Link Setup Respose RRC Connection Establishment

Hard Handover

Soft Handover

Node BRNC

Node BRNC

Node BRNC

Radio Link Addition Soft Handover RNCNode B

Radio Link Addition Response Soft Handover RNCNode B

Radio Link Deletion RRC Connection Release

Hard Handover

Soft Handover

RNCNode B

RNCNode B

RNCNode B

Radio Link Deletion Response RRC Connection Release

Hard Handover

Soft Handover

Node BRNC

Node BRNC

Node BRNC


Prepare

RAB Establishment

RAB Release

RNCNode B

RNCNode B

Radio Link Reconfiguration Ready RAB Establishment

RAB Release

Node BRNC

Node BRNC

Radio Link ReconfigurationCommit

RAB Establishment

RAB Release

RNCNode B

RNCNode B

Paging Paging RNCNode B

ALCAP

ALCAP is a generic name to indicate the protocol(s) used to establish data transport bearers on the Iu, Iur and Iub

interfaces. Q.2630.1 (Q AAL2) is one of the selected protocol to be used as ALCAP.

The following should be noted:

data transport bearers may be dynamically established using ALCAP or preconfigured;

transport bearers may be established before or after allocation of radio resources.

6.5.1Q2630.1 (Q.AAL 2)

Editor note: the exact procedures are needed to be derived from the reccomandation, therefore the following section

should b intended as example. Contribution invited.


13/75

25.931 V1.1.0 1 1999-0614

The following figure is showing an example of use of Q2630.1 in the UTRAN context, for the different interfaces

UE Node B

Drift RNS

Node B

Serving RNS

Drift

RNC

Serving

RNC

CN

11.

Establish RequestQ.aal2 Q.aal2

Q.aal2Q.aal2 Establish Confirm

9Establish Request Q.aal2Q.aal2

Q.aal2 Q.aal2Establish Confirm

Establish Request Q.aal2Q.aal2


Establish Request Q.aal2Q.aal2


RRC Procedures & Messages

For a detailed description of RRC procedures and messages refer to [14].


Message Name UTRAN Procedure Direction Logical Channel

UE Capability Information NAS Signalling Conn. Est. UESRNC DCCH

Direct Transfer NAS Signalling Conn. Est. UESRNC DCCH

RRC Connection Request RRC Connection Est. UESRNC CCCH

RRC Connection Setup RRC Connection Est. SRNCUE CCCH

RAB Setup RAB Establishment SRNCUE DCCH

RAB Setup Complete RAB Establishment UESRNC DCCH

RAB Release RAB Release SRNCUE DCCH

RAB Release Complete RAB Release UESRNC DCCH

Handover Command

Hard Handover SRNCUE

DCCH


14/75


15/75

25.931 V1.1.0 1 1999-0616

UTRAN Signaling Procedures

The signalling procedures shown in the following sections do not represent the complete set of possibilities, nor do theymandate this kind of operation. The standard will specify a set of elementary procedures for each interface, which may

be combined in different ways in an implementation. Therefore these sequences are merely examples of a typical

implementation.

Furthermore the list of parameters may not be complete, but should only be seen as examples of possible information

carried by the messages.

NOTE: the use of Radio Bearer Setup or Radio Bearer Assignement is FFS. This note is valid for all the document

8.Procedures not related to a specific UE (globalprocedures)

This section presents a number of signaling procedures not related to a specific UE. The protocol stack involved during

these procedures is the one shown in Figure 2.

8.1System Information Broadcasting

This example shows an example of System Information broadcasting.

Cell Broadcast

This example shows an example of broadcasting of User Information.

9.Procedures related to a specific UE

This section presents a number of signaling procedures related to a specific UE. The protocol stack involved during

these procedures is the one shown in Figure 3, with the exception of Paging for a UE in RRC Idle Mode that makes use

of the protocol stack shown in Figure 2.

1. SYST E M INFORMAT ION (FFS)

3 . SYST E M INFORMAT ION

2. SYST E M INFORMAT ION ( Iub ) (FFS)

UE Node B CRN C C N

NBAPNBAP

RR CRR C

R A N A PRANAP

4. SY ST E M IN FO RM AT IO N RRCRR C

5. S YST E M INFO RM A T IO N RRCRR C


16/75

25.931 V1.1.0 1 1999-0617

9.1Paging

This section presents two examples of Paging procedures for both the cases of a UE in RRC Idle Mode and RRC

Connected Mode.

9.1.1Paging for a UE in RRC Idle ModeThis example shows how paging is performed for a UE in RRC Idle Mode. The UE may be paged for a CS or PS

service. Since the UE is in RRC Idle Mode, the location is only known at CN level and therefore paging is distributed

over a defined geographical area (e.g. LA).

Note: Example below illustrates scenario where LA spans across 2 RNCs.

UE N ode B

1. 1

Node B

2. 1

RN C

1

RN C

2

CN

RANAPRA NAP 1. Paging

NBAPNBAP2. Paging

3. PCCH : Paging

RAN AP RA NAP1. Paging

NBAPNBAP2. Paging

4. PCCH: Paging

5. NAS Signalling Connection Establishment

Paging for a UE in RRC Idle Mode

1. CN initiates the paging of a UE over a LA spanning two RNCs (i.e. RNC1 and RNC2) via RANAP messagePaging.

Parameters: UE identifier, Paging Type.

2. RNC1 and RNC2 forward Pagingmessage via NBAP to corresponding Nodes B (for example Node B 1.1, Node B2.1).

Parameters: UE identifier.

3. Paging of UE performed by cell1

4. Paging of UE performed by cell2

5. UE detects page message from RNC1 and the procedure for NAS signalling connection establishment is followed

NAS message transfer over established signalling connection can now be performed.

9.1.2Paging for a UE in RRC Connected Mode

This can occur in case of two core network domains, with the mobility management independent of each other. Two

possible solutions exists:

The UTRAN coordinates the paging request with the existing RRC connection.

The UE coordinates the paging request with the existing RRC connection.


17/75

25.931 V1.1.0 1 1999-0618

The following example shows how paging is performed for a UE in RRC Connected Mode when the UTRAN

coordinates the paging request with the existing RRC connection using DCCH.

UE Serving

RN C

CN

RR CRR C2. DC CH: Paging

RANA P RANAP1. Paging

Paging for a UE in RRC Connected Mode when the UTRAN coordinates the paging request with the existing

RRC connection using DCCH

1. CN initiates the paging of a UE via RANAP message Paging.

Parameters: UE identifier, Paging Type.

2. SRNC sends RRC message Paging.

Parameters: Paging Type.

9.2NAS Signalling Connection Establishment

The following examples show establishment of a Signalling Connection either by the UE or by the CN.

9.2.1 UE Initiated Signalling Connection Establishment

This example shows establishment of a UE originated NAS Signalling Connection Establishment.

UE Serving

RN C

CN

1. RRC Connection Establishment

RR CRR C2. DC CH: UE Capability Information

RR CRR C3. DC CH: Direct Transfer

RANA P RANAP

4. Initial UE Message

NAS Signalling Connection Establishment

1. RRC Connection is established (see 9.3.1 or 9.3.2).

2. UE sends RRC message UE Capability Informationto SRNC.Parameters: UE Radio Capability (e.g. maximum number of simultaneous radio links, maximum TX power

capability, supported radio access types).

Note: To speed up the transfer of the initial NAS message the RRC message UE CapabilityInformationcould be

transferred after the initial NAS message (step 3). This issue is FFS.


18/75

25.931 V1.1.0 1 1999-0619

3. UE sends RRC Direct Transfer to SRNC.Parameters: Initial NAS Message (could for a GSM based CN be e.g. CM Service Request, Location Update

Request etc.) CN node indicator (it indicates the correct CN node into which the NAS message shall be forwarded).

4. SRNC initiates signalling connection to CN, and sends the RANAP message Initial UE Message.Parameters: Initial NAS Message (could for a GSM based CN be e.g. CM Service Request, Location Update

Request etc.).

The NAS signalling connection between UE and CN can now be used for NAS message transfer.

9.2.2CN Initiated Signalling Connection Establishment

This example shows establishment of a CN originated NAS Signalling Connection Establishment.

9.3RRC Connection Establishment

The following examples show establishment of a RRC connection either on a dedicated channel (DCH) or on a common

transport channel

9.3.1DCH Establishment

This example shows establishment of an RRC connection on a dedicated channel (DCH).

UE Node B

Serving RNSServing

RN C

5. NodeB-SRNC Data Transport Bearer Sync

(FDD only)

Allocate RNTI

Select L1 and L2parameters

RR CRR C1. C C C H: RRC Connection Request

NBAPNBAP3. Radio Link Setup Response

NBAPNBAP2. Radio Link Setup

RR CRR C

6. C C C H: RRC Connection Setup

Start RX

Start TX

4. ALCAP Iub Data Transport Bearer Setup

RRC Connection Establishment - DCH Establishment

1. The UE initiates set-up of an RRC connection by sending RRC message Connection Requeston CCCH.Parameters: UE identification, reason for RRC connection.

Note: Type of UE identification and Layer 1 Node B Acknowledge on RACH (CCCH) are FFS.

2. The SRNC decides to use a DCH for this RRC connection, allocates RNTI and radio resources for the RRCconnection. When a DCH is to be set-up, NBAP message Radio Link Setupis sent to Node B.

Parameters: Cell id, Transport Format Set, Transport Format Combination Set, frequency, UL scrambling

code(FDD only), Time Slots (TDD only), User Codes (TDD only),DL channelisation code, Power controlinformation.


19/75

25.931 V1.1.0 1 1999-0620

3. Node B allocates resources, starts PHY reception, and responses with NBAP message Radio LinkSetupResponse.

Parameters: Signalling link termination, , DL channelisation code (FDD only), Transport layer addressing

information (AAL2 address, AAL2 Binding Identity) for the Iub Data Transport Bearer.

4. SRNC initiates set-up of Iub Data Transport bearer using ALCAP protocol. This request contains the AAL2

Binding Identity to bind the Iub Data Transport Bearer to the DCH. The request for set-up of Iub Data Transportbearer is acknowledged by Node B.

5. Node B and SRNC establish synchronism for the Iub Data Transport Bearer. Then Node B starts DL transmission.(FDD only)

6. Message RRC Connection Setupis sent on CCCH from SRNC to UE.Parameters: UE identification, RNTI, Transport Format Set, Transport Format Combination Set, frequency, DL

scrambling code (FDD only), Time Slots (TDD only), User Codes (TDD only), DL channelisation code(FDD only),

Power control information.

9.3.2RACH/FACH EstablishmentThe procedure for establishment of an RRC connection on a common transport channel (RACH/FACH) is described in

[Editor note: appropriate reference to the WG2 documentation is needed]. A prerequisite for this example is that the

necessary Iub Data Transport bearer for the RACH/FACH is established prior to this procedure.

9.4RRC Connection Release

The following examples show RRC connection release either of a dedicated channel (DCH) or of a common transport

channel (RACH/FACH).

9.4.1DCH Release

This example shows RRC Connection release of a dedicated channel.

2 . I u R E L E A SE C O M P L E T E

1 . I u R EL EA S E C O MM A N D

1 0. R A DIO L IN K D E LE TIO N R ES PO N SE ( Iu b)

8 . R A D IO L IN K D E LE TI ON ( I ub )

9 . R A DIO L IN K D E LE TIO N R ES PO N SE ( I ub )

6 . R A D IO L IN K D E LE TI ON (Iub)

5 . R R C C O N N E C T I O N R E L E A S E C O M P L E T E ( F F S )

4 . R R C C O N N E C T I O N R E L E A S E

11. RADIO LINK DELETIONR E S P O N SE ( I u r)

7 . RADIO LINK DELETION

(Iur)

UE N o de BDr if t RN S

N o d e BS er vi ng R N S

DriftR N C

ServingR NC

C N

R R CR R C

R R CR R C

N B A PN B A P

N B A PN B A P

R N S A PR N S A P

N B A PN B A P

N B A PN B A P

R N S A PR N S A P

R A N A PR A N A P

R A N A PR A N A P

3 . A L C A P I u B e ar er

R E L E A S E

A L C A P I u r B EA R E R

R E L E A S E

1 3 . A L C A P I u b B E A R E R R E L E A S E

1 2 . A L C A P I u b B E A R E R R E L E A S E


20/75

25.931 V1.1.0 1 1999-0621

RRC Connection release of a dedicated channel

9.4.2Common Transport Channel Release

This example shows RRC Connection release of a common transport channel.

2. Iu R ELEASE C OM PLETE

1. Iu R ELEASE C OM M AND

5. R R C C ONNEC TION R ELEASE C OM PLETE (FFS)

4. R R C C ONNEC TION R ELEASE

U E N ode B

Dr ift RN S

Node B

S er vi ng R NS

Drift

RN C

Serving

RN C

CN

RR CRR C

RR CRR C

R ANAPR ANAP

R ANAPR ANAP

3. ALCAP Iu BEARER

RELEASE

RRC Connection release of a common transport channel

9.5RRC Connection Re-establishment

The following examples show re-establishment of a RRC connection either on a dedicated channel (DCH) or on a

common transport channel.

9.5.1DCH Re-establishment

This example shows re-establishment of a RRC connection on a dedicated channel (DCH).


21/75

25.931 V1.1.0 1 1999-0622

16 DCCH: RRC Connection Re-establishment

14. Downlink Transfer

12. Radio Link Setup Response

11. Radio Link Setup Response

10. Radio Link Setup

9. Radio Link Setup

2. Uplink TransferRNSAP RNSAP

R NSAP RNSAP

N BA P N BA P

N BA P N BA P

R NSAPR NSAP

R NSAP RNSAP

15. Transm ission of

Uu Signalling

Message

RRC RRC

1. Reception of Uu

Signalling Message

ALCAP Iub

Bearer Setup

13. ALCA P Iur Bearer Setup

8. ALCAP Iub Bearer

Release

5 . ALCAP Iu r

Bearer Release

4. Radio Link D eletion Response

RN SA P RN SA P

RN SA P RN SA P

3. Radio Link D elit ion

7 Radio Link Deletion Response

N BA P N BA P

N BA P N BA P

6 Radio Link D elit ion

U E S-RN C O ld

D-RNC

O ld

Node B

N ew

D-RNC

N ew

Node B

RRC connection Re-establishment (Anchor approach) DCH Re-establishment

1. The UE initiates the re-establishment of the RRC connection with the new cell by sending RRCConnection Re-establishment Requestmessage on CCCH.

2. The new RNC delivers this message transparently as Uplink Transfermessage to the serving RNC.

3./4./5./6./7./8. The SRNC initiates release of Iur/Iub Data Transport bearer using ALCAP protocol and alsorelease of Iur/Iub Radio resource using RNSAP / NBAP protocols.

9. The serving RNC allocates new RNTI and radio resources for the RRC connection on Iur, and sends theRNSAP message Radio Link Setupto the target RNC.

10. The target RNC sends the NBAP message Radio Link Setupto the target Node B.

11. Node B allocates resources, and responses with NBAP message Radio LinkSetup Response.

12. Target RNC responses with RNSAP message Radio LinkSetup Response.


22/75

25.931 V1.1.0 1 1999-0623

13. Serving RNC initiates set-up of Iur / Iub Data Transport bearer using ALCAP protocol. This requestcontains the AAL2 Binding Identity to bind the Iur / Iub Data Transport Bearer to the DCH. The request forset-up of Iur / Iub Data Transport bearer is acknowledged by target RNC / Node B.

14. The serving RNC sends the transparent RNSAP message Downlink transferto the new CRNC.

15. The New CRNC delivers this message as RRC Connection Re-establishment message on CCCH.

16. Message RRC Connection Re-establishment Complete is sent on the new DCCH from the UE to theserving RNC.

9.5.2RACH/FACH Re-establishment

This example shows re-establishment of a RRC connection on a common transport channel .

9.6Radio Access Bearer EstablishmentThe following examples show establishment of a radio access bearer on a dedicated channel (DCH) or on a common

transport channel (RACH/FACH) when the RRC connection already support a radio access bearer either on a dedicated

channel (DCH) or on a common transport channel (RACH/FACH).

9.6.1DCH - DCH Establishment - Synchronized

This example shows establishment of a radio access bearer on a dedicated channel (DCH) when the RRC connection

already uses a dedicated channel (DCH).

[FDD-The UE communicates via two Nodes B. One Node B is controlled by SRNC, one Node B is controlled by

DRNC]

[TDD The Nodes B shown in the figure are mutually exclusive in TDD mode.].


23/75

25.931 V1.1.0 1 1999-0624

UE N ode B

Dr ift R NS

Node B

Serving RNS

Drift

RN C

Serving

RN C

CN

RNSAP RN SAP

7. Radio Link Reconfiguration

Ready

RR CRR C16. D CC H: Radio Access Bearer Setup Complete

NBAPNBAP8. Radio Link Reconfiguration Ready

NBAPNBAP6 Radio Link Reconfiguration Ready

11. NodeB-SRNC Data Transport Bearer Sync.

NBAPNBAP 14. Radio Link Reconfiguration Comm it

RNSAP RN SAP


Commit

NBAPNBAP13. Radio Link Reconfiguration Commit

RR CRR C15. DC CH: Radio Access Bearer Setup

Apply new transport format set

Select L1, L2 and Iu Data

Transport Bearer parameters

RAN AP RA NAP

17. RAB Assignment

Complete


2. ALCAP Iu Data

Transport Bearer Setup

RAN AP RA NAP

1. RAB Assignment

Request

[Establishment]

RN SAP RN SAP


Prepare

[DCH A ddi t ion]

NBAPNBAP4. Radio Link Reconfiguration Prepare

[DCH Addi t ion]


[DCH A ddi t ion]

ALCAP Iur Bearer Setup9. ALCAP Iub Data Transport Bearer Setup

Radio Access Bearer Establishment - DCH - DCH Establishment - Synchronized

1. CN initiates establishment of the radio access bearer with RANAP message RAB Assignment Request.Parameters: RAB QoS parameters, Transport layer addressing information (AAL2 address, AAL2 Binding Identity)

for Iu Data Transport Bearer SRNC decides the requirements on L1, L2 and Iu Data Transport Bearer.

2. SRNC initiates set-up of Iu Data Transport bearer using ALCAP protocol. This request contains the AAL2 BindingIdentity to bind the Iu Data Transport Bearer to the Radio Access Bearer.

3. SRNC requests DRNC to prepare establishment of DCH to carry the RAB (Radio Link ReconfigurationPrepare).

Parameters: Transport Format Set, Transport Format Combination Set, Power control information, instructions for

DCH mapping on Iub Data Transport Bearers.

This step is applicableonly when more Nodes B are involved.

4. DRNC requests its Node B to prepare establishment of DCH to carry the RAB (Radio Link ReconfigurationPrepare).

Parameters: Transport Format Set, Transport Format Combination Set, Power control information, , DL

channelisation code.This step is applicableonly when more Nodes B are involved.


24/75

25.931 V1.1.0 1 1999-0625

5. SRNC requests its Node B to prepare establishment of DCH to carry the RAB (Radio Link ReconfigurationPrepare).

Parameters: Transport Format Set, Transport Format Combination Set, Power control information, Time Slots

(TDD only), User Codes (TDD only).

6. Node B allocates resources and notifies DRNC that the preparation is ready (Radio Link Reconfiguration Ready).

Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data TransportBearer.


7. DRNC notifies SRNC that the preparation is ready (Radio Link Reconfiguration Ready).Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport

Bearer.


8. Node B allocates resources and notifies SRNC that the preparation is ready (Radio Link Reconfiguration Ready).Parameters: DL channelisation code Per Cell (FDD only), Transport layer addressing information (AAL2 address,

AAL2 Binding Id) for Iub Data Transport Bearer.

9. SRNC initiates setup of Iur/Iub Data Transport Bearer using ALCAP protocol. This request contains the AAL2Binding Identity to bind the Iur/Iub Data Transport Bearer to DCH.


10. SRNC initiates setup of Iub Data Transport Bearer using ALCAP protocol. This request contains the AAL2 BindingIdentity to bind the Iub Data Transport Bearer to DCH.

11. The Nodes B and SRNC establish synchronism for the Iub and Iur Data Transport Bearer.This step is applicableonly for the FDD case..

12. RNSAP message Radio Link Reconfiguration Commitis sent from SRNC to DRNC.Parameters:


13. NBAP message Radio Link Reconfiguration Commit is sent from DRNC to Node B.Parameters:


14. NBAP message Radio Link Reconfiguration Commit is sent from SRNC to Node B.Parameters:

15. RRC message Radio Access Bearer Setupis sent by SRNC to UE.Parameters: Transport Format Set, Transport Format Combination Set, DL channelisation code per cell(FDD only),

Time Slots (TDD only), User Codes (TDD only).

16. UE sends RRC message Radio Access Bearer Setup Completeto SRNC.

17. SRNC sends RANAP message RAB AssignmentCompleteto CN.

9.6.2DCH - DCH Establishment - Unsynchronized (PSTN/ISDN CoreNetwork

This example shows an establishment of a radio access bearer on a dedicated channel (DCH) when the RRC connection

already uses a dedicated channel (DCH). The UE communicates via two Nodes B. One Node B is controlled by SRNC,

one Node B is controlled by DRNC. The reconfiguration time does not require to be synchronised among Node-Bs,

SRNC and UE.


25/75

25.931 V1.1.0 1 1999-0626

UE Node B

Drift RNS

Node B

Serving RNS

Drift

RNC

Serving

RNC

CN

RNSAP RNSAP

8. RL Reconfiguration

Response

RRCRRC16. Radio Access Bearer Setup Complete

NBAPNBAP12. Radio Link Reconfiguration Response



RRCRRC15. Radio Access Bearer Setup


Select L1, L2 and Iu Data

Transport Bearer parameters

RANAP RANAP

17. RAB Assignment

Complete

2. Establish Request

RANAP RANAP

1. RAB Assignment

Request

[Establishment]

RNSAP RNSAP3. RL Reconfiguration

[DCH Addition]

NBAPNBAP4. Radio Link Reconfiguration

[DCH Addition]

NBAPNBAP


[DCH Addition]

Q.aal2 Q.aal2

Q.aal2Q.aal2 6. Establish Confirm

11.

9. ALCAP Iur Data Transport Bearer Setup



Radio Access Bearer Establishment - DCH - DCH Establishment Unsynchronised

1. CN initiates establishment of the radio access bearer with RANAP Radio Access Bearer Assignment Requestmessage.

Parameters: RAB QoS parameters, AAL2 binding Identity

2. SRNC performs mapping of the RAB QoS parameters to AAL2 link characteristics and initiates set-up of Iu DataTransport bearer with Q.aal2 Establish Request message.

Parameters: Served User Generated Reference, AAL2 link characteristics

3. SRNC decided that there are no need for a synchronous RL reconfiguration, and requests DRNC to setup a newDCH. It include in the message that the modification shall be done immediately without waiting for the command

message.


26/75

25.931 V1.1.0 1 1999-0627

Parameters: Bearer ID, Mode= Unsynchronised, Transport Format Set, Transport Format Combination Set, Power

control information

4. DRNC requests its Node B to establish of a new DCH in the existing Radio Link.Parameters: Bearer ID, Mode= Unsynchronised, Transport Format Set, Transport Format Combination Set, Power

control information.

5. SRNC requests its Node B setup a new DCH in the existing Radio Link.Parameters: Bearer ID, Mode= Unsynchronised, Transport Format Set, Transport Format Combination Set, Power

control information

6. CN confirms the establishment of the transport bearer and binds it to the radio network layer.

7. Node B allocates resources and notifies DRNC that the setup is done.Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport

Bearer.

8. DRNC notifies SRNC that the setup is done.Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport

Bearer.

9. SRNC initiates setup of Iur Data Transport Bearer using ALCAP protocol. This request contains the AAL2 BindingIdentity to bind the Iur Data Transport Bearer to DCH.


11. DRNC performs bridging of Iub and Iur Data Transport bearers.

12. Node B allocates resources and notifies SRNC that the setup is done.Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport

Bearer.


14. The Nodes B and SRNC establish frame synchronism for the Iub and Iur Data Transport Bearer.

15. RRC message Radio Access Bearer Setup is sent by SRNC to UE.Parameters: Transport Format Set, Transport Format Combination Set.

16. UE sends RRC message Radio Access Bearer Setup Complete to SRNC.

17. SRNC sends RANAP message Radio Access Bearer Assignment Complete to CN.Parameters: Binding ID

9.6.3RACH/FACH - DCH Establishment

This example shows establishment of a radio access bearer on a dedicated channel (DCH) when the RRC connection

already uses a common transport channel (RACH/FACH).

8 . RAB SE T UP RE SPONSE

7. RADIO ACCE SS BE ARE R SE T UP COMPL E T E

6. RADIO ACCE SS BE ARE R SE T UP

1. RAB SETUP

3. RADIO L INK SE T UP

RESPONSE(Iub)

2. RADIO LINK SETUP(Iub)

UE Node B

Serving RNS

Serving

RN C

CN

RA NA P RA N A P

NBAPNBAP

NBAPNBAP

RR CRR C

RR CRR C

RA NA P RA N A P

4. AL CAP Iub BE ARE R SE T UP

5. AL CAP Iu BE ARE R

SE T UP


27/75

25.931 V1.1.0 1 1999-0628

9.6.4RACH/FACH - RACH/FACH Establishment

This example shows establishment of a radio access bearer on a common transport channel (RACH/FACH) when the

RRC connection already uses a common transport channel (RACH/FACH).

9.7Radio Access Bearer Release

The following examples show release of a radio access bearer either on a dedicated channel (DCH) or on a common

transport channel (RACH/FACH) when the RRC connection already uses a dedicated channel (DCH) or a commontransport channel (RACH/FACH).

9.7.1DCH - DCH Release - Synchronized

This example shows release of a radio access bearer on a dedicated channel (DCH) when the RRCconnection still uses a

dedicated channel (DCH) after the release.

[FDD - The UE communicates via two Nodes B. One Node B is controlled by SRNC, one Node B is controlled by

DRNC.]

[TDD The Nodes B shown in the figure are mutually exclusive in TDD mode.]

5 . RAB SE T UP RE SPONSE

4. RADIO ACCE SS BE ARE R SE T UP COMPL E T E

3. RADIO ACCE SS BE ARE R SE T UP

1. RAB SE T UP

UE N ode B

Serving RNS

Serving

RN C

C N

RR CRR C

RR CRR C

RA N AP RA NA P

RA N A P RA NA P


SE T UP


28/75

25.931 V1.1.0 1 1999-0629

UE N ode B

Dr ift R NS

Node B

Serving RNS

Drift

RN C

Serving

RN C

C N

RNSA P RNSA P


Ready

RR CRR C14. D CC H : Radio Access Bearer Release Complete



NBAPNBAP12. Radio Link Reconfigura t ion Commit

RNSA P RNSA P


Com m i t

RR CRR C13. D CC H: Radio Access Bearer Release


RAN AP RA N A P

2. RAB Assignment

Complete

NBAPNBAP11. Radio Link Reconfigura t ion C ommit

16. ALCA P Iub Data Transport Bearer Release

3. ALCAP Iu Data

Transport Bearer Release

RAN AP RA N A P

1. RAB Assignment

Request

[Release]

RN SA P RNSA P


Prepare

[DCH Delet ion]


[DCH Delet ion]

NBAPNBAP

6. Radio Link Reconfiguration Prepare

[DCH Delet ion]

ALCAP Iur Bearer Release15. ALCA P Iub Data Transport Bearer Release

Radio Access Bearer Release - DCH - DCH Release - Synchronized

1. CN initiates release of the radio access bearer with RANAP message RAB AssignmentRequest.

2. SRNC acknowledges the release of radio access bearer (RAB Assignment Complete).

3. SRNC initiates release of the Iu Data Transport bearer between the CN and the SRNC using the ALCAP protocol.

4. SRNC requests DRNC to prepare release of DCH carrying the RAB (Radio Link ReconfigurationRequest).Parameters: Transport Format Combination Set, UL scrambling code.


5. DRNC requests its Node B to prepare release of DCH carrying the RAB (Radio Link Reconfiguration Prepare).Parameters: Transport Format Combination Set, UL scrambling code, DL channelisation code.


6. SRNC requests its Node B to prepare release of DCH carrying the RAB (Radio Link Reconfiguration Prepare).Parameters: Transport Format Combination Set, UL scrambling code (FDD only), Time Slots (TDD only), User

Codes (TDD only).

7. Node B notifies DRNC that release preparation is ready (Radio Link Reconfiguration Ready).This step is applicableonly when more Nodes B are involved.

8. DRNC notifies SRNC that release preparation is ready (Radio Link ReconfigurationProceed).This step is applicableonly when more Nodes B are involved.


29/75

25.931 V1.1.0 1 1999-0630

9. Node B notifies SRNC that release preparation is ready (Radio Link Reconfiguration Ready).Parameters: DL channelisation code per cell (FDD only).

10. RNSAP message Radio Link Reconfiguration Commitis sent from SRNC to DRNC.This step is applicableonly when more Nodes B are involved.

11. NBAP message Radio Link Reconfiguration Commitis sent from DRNC to Node B.This step is applicableonly when more Nodes B are involved.

12. NBAP message Radio Link Reconfiguration Commitis sent from SRNC to Node B.Parameters:

13. RRC message Radio Access Bearer Releaseis sent by SRNC to UE.Parameters: Transport Format Set, Transport Format Combination Set, DL channelisation code per cell. (FDD

only), Time Slots (TDD only), User Codes (TDD only).

14. UE sends RRC message Radio Access Bearer Release Completeto SRNC.

15. Not used resources in DRNC and NodeB (Drift RNS) are released. DRNC initiates release of Iur and Iub (Drift

RNS) Data Transport bearer using ALCAP protocolThis step is applicableonly when more Nodes B are involved.

16. Not used resources in SRNC and NodeB (Serving RNS, if any) are released. SRNC initiates release of Iub (ServingRNS) Data Transport bearer using ALCAP protocol.

9.7.2DCH - DCH Release - Unsynchronized

This example shows release of a radio access bearer on a dedicated channel (DCH) when the RRC connection still uses

a dedicated channel (DCH) after the release. The UE communicates via two Nodes B. One Node B is controlled the

SRNC, one Node B is controlled by DRNC. The reconfiguration does not require to be synchronised among Node-Bs,

SRNC and UE.


30/75

25.931 V1.1.0 1 1999-0631

UE Node B

Drift RNS

Node B

Serving RNS

Drift

RNC

Serving

RNC

CN

RNSAP RNSAP


Response

RRCRRC3. Radio Access Bearer Release Complete



RRCRRC2. Radio Access Bearer Release

RANAP RANAP

4. RAB Assignment

Complete

12. ALCAP Iub Data Transport Bearer Release

5. ALCAP Iu Data


RANAP RANAP

1. RAB Assignment

Request

[Release]

RNSAP RNSAP


[DCH Deletion]


[DCH Deletion]


[DCH Deletion]

ALCAP Iur Bearer Release11. ALCAP Iub Data Transport Bearer Release

Radio Access Bearer Release - DCH - DCH Release - Unsynchronised

1. CN initiates release of the radio access bearer with RANAP Radio Access Bearer Assignment Request message.

2. RRC message Radio Access Bearer Release is sent by SRNC to UE.

3. UE sends RRC message Radio Access Bearer Release Complete to SRNC.

4. SRNC acknowledges the release of radio access bearer to CN

5. SRNC initiates release of the Iu Data Transport bearer between the CN and the SRNC using the ALCAPprotocol.

6. SRNC requests DRNC to release of DCH carrying the RAB.Parameters: Bearer ID, Unsynchronised, TFCS

7. DRNC requests its Node B to release of DCH carrying the RAB.Parameters: Bearer ID, Unsynchronised, TFCS

8. SRNC requests its Node B to prepare release of DCH carrying the RAB.Parameters: Bearer ID, Unsynchronised, TFCS

9. Node B acknowledges DRNC.

10. DRNC acknowledges SRNC.

11. Node B acknowledges SRNC


31/75

25.931 V1.1.0 1 1999-0632

12. SRNC initiates release of Iur Data Transport bearer using ALCAP protocol. Note: the release of the Iur link maybe done before step 10.

9.7.3DCH - RACH/FACH Release

This example shows release of a radio access bearer on a Dedicated channel (DCH) when the RRC connection still uses

a Common transport channel (RACH/FACH) after the release (DCH to RACH/FACH).

Note this example shows case where the SRNC decides to perform SRNS Relocation directly at the channel switching.

NOTE: This procedure is FFS

9.7.4RACH/FACH - RACH/FACH Release

This example shows release of a radio access bearer on a common transport channel (RACH/FACH) when the RRC

connection still uses a common transport channel (RACH/FACH) after the release (RACH/FACH to RACH/FACH.

9.8Radio Access Bearer Re-establishment

The following examples show re-establishment of a radio access bearer either on a dedicated channel (DCH) or on a

common transport channel (RACH/FACH) when the RRC connection already uses a dedicated channel (DCH) or a

common transport channel (RACH/FACH).

9.8.1DCH - DCH Re-establishment

This example shows re-establishment of a radio access bearer on a dedicated channel (RACH/FACH) when the RRC

connection already uses a dedicated channel (DCH).

9.8.2RACH/FACH - DCH Re-establishment

This example shows re-establishment of a radio access bearer on a dedicated channel (RACH/FACH) when the RRC

connection already uses a common transport channel (RACH/FACH).

9.8.3RACH/FACH - RACH/FACH Re-establishment

This example shows re-establishment of a radio access bearer on a common transport channel (RACH/FACH) when the

RRC connection already uses a common transport channel (RACH/FACH).

4 . RADIO ACCE SS BE ARE R RE L E ASE

5. RADIO ACCE SS BE ARE R RE L E ASE COMPL E T E

2. RAB RE L E ASE

RE SPONSE

1. RAB RE L E ASE

UE N ode B

Dr ift RN S

Node B

Serving RNS

Drift

RN C

Serving

RN C

CN

RA N A P RA N A P

RR CRR C

RR CRR C

RA N A P RA N A P

3. AL CAP Iu

BE ARE R RE L E ASE


32/75

25.931 V1.1.0 1 1999-0633

9.9Radio Access Bearer Modification

The following examples show modification of a radio access bearer established either on a dedicated channel (DCH) or

on a common transport channel (RACH/FACH).


33/75

25.931 V1.1.0 1 1999-0634

9.9.1DCH to DCH Modification

This example shows modification of a radio access bearer on a dedicated channel (DCH)


34/75

25.931 V1.1.0 1 1999-0635

9.9.2RACH/FACH TO RACH/FACH Reconfiguration

This example shows reconfiguration of a radio access bearer on a common transport channel (RAH/FACH to

RACH/FACH) .

This procedure is FFS. It is not yet clear if the Bearer should be effectively reconfigured of should be removed and set

up again

9.9.3RACH/FACH TO DCH Reconfiguration

This example shows reconfiguration of a radio access bearer on a common transport channel (RACH/FACH to DCH)

This procedure is FFS. It is not yet clear if the Bearer should be effectively reconfigured of should be removed and set

up again

x

1 . RAB RE CONFIGURAT ION

5. RAB RE CONFIGURAT ION

RE SPONSE

4. RADIO ACCE SS BE ARE R RE CONFIGURAT ION COMPL E T E

3. RADIO ACCE SS BE ARE R RE CON FIGURAT ION

UE Node B

Serving RNS

Serving

RN C

CN

RA N A P RA N A P

RR CRR C

RR CRR C

RA N A P RA N A P


RE CONFIGURAT ION

6. RADIO ACCE SS BE ARE R RE CONFIGURAT ION COMPL E T E

5. RADIO ACCE SS BE ARE R RE CONFIGURAT ION


RE SPONSE



RE SPONSE (Iub)


UE N ode B

Serving RNS

Serving

RN C

C N

N B A PNBAP

N B A PNBAP

RR CRR C

RR CRR C

RAN A P RA N A P

RA N A P RAN A P


RE CONFIGURAT ION


35/75

25.931 V1.1.0 1 1999-0636

9.9.4DCH TO RACH/FACH RECONFIGURATION

This example shows reconfiguration of a radio access bearer on a dedicated channel (DCH to RACH/FACH).

Note: this example shows the case where the SRNC decides to perform SRNS Relocation immediatly after the channel

switching.

This procedure is FFS.

1 . RAB RE CONFIGURAT ION

4. RADIO ACCE SS BE ARE R RE CONFIGURAT ION

COMPL E T E

3. RADIO ACCE SS BE ARE R RE CON FIGURAT ION

8. RADIO L INK DE L E T IONRESPONSE(Iur)

5 . RADIO L INK DE L E T ION

(Iur)


RESPONSE(Iub)

6 . RADIO L INK DE L E T ION(Iub)

UE Node B

Dr ift RN S

Node B

Serving RNS

Drift

RN C

Serving

RN C

C N

RA NA P RA N A P

RR CRR C

RR CRR C

RNSAPRNSAP

NBAPNBAP

NBAPNBAP

RNSAPRNSAP

Cell Upd ate Procedure + Streamlining

(FFS)

AL CAP Iu r BE ARE R RE L E ASE9. AL CAP Iub BE ARE R RE L E ASE


RE CONFIGURAT ION


36/75


37/75

25.931 V1.1.0 1 1999-0638

9.11.2RACH/FACH to RACH/PCH

The procedure for channel switching from RACH/FACH to RACH/PCH (Cell Connected to URA connected)) is

described in [Editor note: appropriate reference to the WG2 documentation is needed].

9.11.3RACH/FACH to DCHThis example shows channel switching from RACH/FACH to DCH.

5 . ACT IVE SE T UPDAT E COMPL E T E

4. ACT IVE SE T UPDAT E


RE SPONSE (Iub)


UE N ode B

Serving RNS

Serving

RN C

C N

N B A PN B A P

N B A PN B A P

RR CRR C

RR CRR C

3. AL CAP Iub BE ARE R SE T UP


38/75

25.931 V1.1.0 1 1999-0639

9.11.4DCH to RACH/FACH

This example shows channel switching from DCH to RACH/FACH.

DCH to RACH/FACH (SRNS Relocation)

The case showed is for when SRNS decides to perform an SRNS relocation immediately after a channel type switching.

9.11.4.2DCH to RACH/FACH (without SRNS Relocation)

9.12Soft Handover

This section presents some examples of soft handover procedures. The following cases are considered:

Radio Link Addition (Branch Addition);

Radio link Deletion (Branch Deletion);

Radio link Addition & Deletion (Branch Addition & Deletion - simultaneously).

Note that Soft Handover applies only to FDD mode.

2 . PHYSICAL CHANNE L RE CONFIGURAT ION COMPL E T E

1. PHYSICAL CHANNE L RE CON FIGURAT ION

6. RADIO L INK DE L E T ION

RESPONSE(Iur)


(Iur)


RESPONSE(Iub)

4. RADIO LINK DELETION(Iub)

UE N ode B

Dr if t R NS

Node B

Serving RNS

Drift

RN C

Serving

RN C

CN

RR CRR C

RR CRR C

RNSAPRNSAP

NBAPNBAP

NBAPNBAP

RNSAPRNSAP

Cell Upda te Procedure + Streamlining

(FFS)

AL CAP Iu r BE ARE R RE L E ASE7. ALCAP Iub BEARER RELEASE


39/75

25.931 V1.1.0 1 1999-0640

9.12.1Radio Link Addition (Branch Addition)

This example shows establishment of a radio link via a Node B controlled by another RNC than the serving RNC. This

is the first radio link to be established via this RNS, thus macro-diversity combining/splitting with already existing radio

links within DRNS is not possible.

UE Node B

Dr ift RN S

Drift

RN C

Serving

RN C


RNSA P RNSAP

1. Radio Link A ddition

Start TX

NBAP NBAP

2. Radio Link Setup

RNSAP RNSA P4. Radio Link Addition

Response

NBAP NBAP

3. Radio Link Setup

Respose

Start RX

Decision to setup

new RL

RR CRR C

8. DC CH: Active Set Update Com plete

RR CRR C

7. DC CH: Active Set Update

[Radio Link Addition]

ALCAP Iur Bearer Setup5. ALCAP Iub Bearer Setup

Soft Handover - Radio Link Addition (Branch Addition)

1. SRNC decides to setup a radio link via a new cell controlled by another RNC. SRNC requests DRNC for radioresources by sending RNSAP message Radio Link Addition. If this is the first radio link via the DRNC for this

UE, a new Iur signalling connection is established. This Iur signalling connection will be used for all RNSAP

signalling related to this UE.

Parameters: Cell id, Transport Format Set per DCH, Transport Format Combination Set, frequency, UL scrambling

code.

2. If requested resources are available, DRNC sends NBAP message Radio Link Setup to Node B.

Parameters: Cell id, Transport Format Set per DCH, Transport Format Combination Set, frequency, UL scramblingcode, DL channelisation code.

3. Node B allocates requested resources. Successful outcome is reported in NBAP message Radio Link SetupResponse.

Parameters: Signalling link termination, Transport layer addressing information (AAL2 address, AAL2 Binding

Identitie(s)) for Data Transport Bearer(s).

Then Node B starts the UL reception.

4. DRNC sends RNSAP message Radio Link Addition Responseto SRNC.Parameters: DL channelisation code, Transport layer addressing information (AAL2 address, AAL2 Binding

Identity) for Data Transport Bearer(s), Neighbouring cell information.

5. SRNC initiates setup of Iur/Iub Data Transport Bearer using ALCAP protocol. This request contains the AAL2Binding Identity to bind the Iub Data Transport Bearer to DCH.

This may be repeated for each Iur/Iub Data Transport Bearer to be setup.


40/75

25.931 V1.1.0 1 1999-0641

6. Node B and SRNC establish synchronism for the Data Transport Bearer(s), relative already existing radio link(s).Then Node B starts DL transmission.

7. SRNC sends RRC message Active Set Update(Radio Link Addition) to UE on DCCH.Parameters: Update type, Cell id, DL scrambling code, DL channelisation code, Power control information, Ncell

information.

8. UE acknowledges with RRC message Active Set Update Complete.

9.12.2Radio link Deletion (Branch Deletion)

This example shows deletion of a radio link belonging to a Node B controlled by another RNC than the serving RNC.

UE Node B

Dr ift RN S

Drift

RN C

Serving

RN C

RR CRR C

2. DC CH: Active Set Update Com plete

Decision to delete

old RL

RNSA P RNSAP

3. Radio Link Deletion

NBAP NBAP


RNSAP RNSA P


Response

NBAP NBAP


Response

Stop RX and TX

RR CRR C

1. DC CH: Active Set Update

[Radio Link Deletion]

ALCAP Iur Bearer Release7. ALCAP Iub Bearer Release

Soft Handover - Radio Link Deletion (Branch Deletion)

1. SRNC decides to remove a radio link via an old cell controlled by another RNC. SRNC sends RRC message ActiveSet Update(Radio Link Deletion) to UE on DCCH.

Parameters: Update type, Cell id.

2. UE deactivates DL reception via old branch, and acknowledges with RRC message Active Set UpdateComplete.

3. SRNC requests DRNC to deallocate radio resources by sending RNSAP message Radio Link Deletion.Parameters: Cell id, Transport layer addressing information.

4. DRNC sends NBAP message Radio Link Deletionto Node B.Parameters: Cell id, Transport layer addressing information.

5. Node B deallocates radio resources. Successful outcome is reported in NBAP message Radio Link DeletionResponse.

6. DRNC sends RNSAP message Radio Link Deletion Responseto SRNC.

7. SRNC initiates release of Iur/Iub Data Transport Bearer using ALCAP protocol.


41/75

25.931 V1.1.0 1 1999-0642

9.12.3Radio link Addition & Deletion (Branch Addition & Deletion -simultaneously)

This example shows simultaneous deletion of of a radio link belonging to a Node B controlled by the serving RNC and

the establishment of a radio link via a Node B controlled by another RNC than the serving RNC. This is the first radio

link to be established via this RNS, thus macro-diversity combining/splitting with already existing radio links within

DRNS is not possible.

This procedures is needed when the maximum number of branches allowed for the macrodiversity set has already been

reached.


RNSAP RNSA P

1. Radio Link Addition

Start TX

RNSA P RNSAP

4. Radio Link Ad dition

Response

NBAP NBAP2. Radio Link Setup

NBAP NBAP3. Radio Link Setup Response

Start RX

Decision to setup

new RL and

release old RL

NBAP 9. Radio Link Release

NBAP NBAP10. Radio Link Release Proceed

Stop RX and TX


RR CRR C8. DC CH: Active Set Update Com plete

RR CRR C

7. DC CH: Active Set Update Command

[Radio Link Addition & Deletion]

NBAP

UE Node B

Dr ift RN S

Node B

Serving RNS

Drift

RN C

Serving

RN C

ALCAP Iur Bearer Setup5. ALCAP Iub Data Transport Bearer Setup

Soft Handover - Radio link Addition & Deletion (Branch Addition & Deletion - simultaneously)

1. 6. See description 1. 6. in Section 9.12.1.

7. SRNC sends RRC message Active Set Update(Radio Link Addition & Deletion) to UE on DCCH.Parameters:Update type, Cell id, DL scrambling code, DL channelisation code, Power control information, Ncell

information.

8. UE disactivates DL reception via old branch, activates DL reception via new branch and acknowledges with RRCmessage Active Set Update Complete.

9. 11. See description 3. 7. in Section 9.12.2


42/75

25.931 V1.1.0 1 1999-0643

9.13Hard Handover

This section presents some examples of hard handover procedures. These ls procedures are for both dedicated and

common channells and may be applied in the following cases:

intra-frequency Hard Handover (TDD mode);

inter-frequency Hard Handover (FDD and TDD mode).

9.13.1Backward Hard Handover

This sections shows some examples of hard handover in the case of network initiated backward handovers


43/75

25.931 V1.1.0 1 1999-0644

9.13.1.1Intra Node B Hard Handover (DCH State)


12 . RADIO L INK DE L E T ION RE SPONSE (Iub)


RESPONSE(Iur)


(Iur)



RESPONSE(Iub)

3. RADIO LINK ADDITION(Iub)

1. RADIO LINK ADDITION(Iub)

7 . HANDOVE R COMMAND

8. HANDOVE R COMPL E T E

6. RADIO L INK ADDIT ION

RESPONSE(Iur)

5 . RADIO L INK ADD IT ION

RESPONSE(Iub)

4 . RADIO L INK ADDIT ION

RESPONSE(Iub)

2 . RADIO L INK ADD IT ION

(Iur)

U E N ode B

Dr ift RN S

Node B

Serving RNS

Drift

RN C

Serving

RN C

CN

NBAPNBAP

NBAPN B A P

RNSAPRNSAP

RR CRR C

RR CRR C

N B A PNBAP

NBAPNBAP

RNSAPRNSAP

N B A PNBAP

NBAPNBAP

RNSAPRNSAP

N B A PN B A P

N B A PNBAP

RNSAPRNSAP


44/75

25.931 V1.1.0 1 1999-0645

Hard Handover via Iur (DSCH/DCH State)

This section shows an example of Hard Handover via Iur.

Note: this procedure is for FFS.

4. Handover Command

Whether this message is RNSAP or no it

is FFS

D CH :

Measurements

UE CRN C

Source

CRN C

Target

SRN C

Time during which

data transmission and

reception is suspended

MSC/SGSN

Target

RR C

4. Handover Command

On measurements results,

RNC decides to initiate a

Hard Handover

2. Common Channels are established on Iur

(FFS)

RR C

5. DCH: Handover

Comple te

RR C7. CCTH Release Request

RR C

RR C

8. CCTH Release Comple te

(FFS if needed) RR C

6.-Handover Complete

Whether this message is RNSAP or no it is

FF S

Inter-RNS Hard Handover via Iur

Hard Handover via Iur (DCH State)

This section shows an example of Hard Handover via Iur, when themobile is in DCH state


45/75

25.931 V1.1.0 1 1999-0646

RNSAPRNSAP

1. Radio Link

Setup Request

Note 1

UE Node B

Source

Node B

Target

RNC

Source

RNC

target

SRNC

RRC RRC8.DCCH: Handover Complete

RNSAP

5. RL Setup

Response

Note 1

RRC7.DCCH: Handover Command

RRC

[Hard Handover]

6. ALCAP Iur Data

Transport Bearer Setup

Note 1

NBAP NBAP2. Radio Link Setup

NBAP NBAP3. Radio Link Setup Response

NBAP NBAP10. Radio Link Deletion

NBAP NBAP11. Radio Link Deletion Response



RNSAP RNSAP

RNSAP RNSAP


Note 2

13. Radio Link

Deletion Response

Note 2

14. ALCAP Iur Data


Note 2

RNSAP

Hard Handover via Iur (DCH on Iur)

1. SRNC sends Radio Link Setup Requestmessage to the target RNC.Parameters: target RNC identifier, s-RNTI, Cell id, Transport Format Set, Transport Format Combination Set.Note

1: This message is not necessary when the target RNC is the SRNC.

2. The target RNC allocates RNTI and radio resources for the RRC connection (if possible), and sends the NBAPmessage Radio Link Setupto the target Node-B. Parameters: Cell id, Transport Format Set, Transport Format

Combination Set, frequency, UL scrambling code (FDD only), Time Slots (TDD only), User Codes (TDD only),

DL channelisation code (FDD only), Power control information.

3. Node B allocates resources, starts PHY reception, and responses with NBAP message Radio LinkSetupResponse.

Parameters: Signalling link termination, Transport layer addressing information for the Iub Data Transport Bearer.


46/75

25.931 V1.1.0 1 1999-0647

4. Target RNC initiates set-up of Iub Data Transport bearer using ALCAP protocol. This request contains the AAL2Binding Identity to bind the Iub Data Transport Bearer to the DCH. The request for set-up of Iub Data Transport

bearer is acknowledged by Node B.

5. When the Target RNC has completed preparation phase, Radio Link Setup Responseis sent to the SRNC.Note 1:This message is not necessary when the target RNC is the SRNC.

6. SRNC initiates set-up of Iur Data Transport bearer using ALCAP protocol. This request contains the AAL2 BindingIdentity to bind the Iur Data Transport Bearer to the DCH. The request for set-up of Iur Data Transport bearer is

acknowledged by Target RNC.Note 1: This message is not necessary when the target RNC is the SRNC

7. SRNC sends a RRC message Handover Commandto the UE.

8. When the RRC connection is established with the target RNC and necessary radio resources have been allocated theUE sends RRC message Handover Completeto the SRNC.

9. The SRNC sends a RNSAP message Radio Link Deletionto the source RNC.Note 2: This message is notnecessary when the source RNC is the SRNC.

10. The source RNC sends NBAP message Radio Link Deletion to the source Node B.Parameters: Cell id, Transport layer addressing information.

11. The source Node B de-allocates radio resources. Successful outcome is reported in NBAP message Radio LinkDeletion Response.

12. The source RNC initiates release of Iub Data Transport bearer using ALCAP protocol.

13. When the source RNC has completed the release the RNSAP message Radio Link Deletion Response is sent to theSRNC.Note 2: This message is not necessary when the source RNC is the SRNC.

14. SRNC initiates release of Iur Data Transport bearer using ALCAP protocol. This request contains the AAL2Binding Identity to bind the Iur Data Transport Bearer to the DCH. The request for release of Iur Data Transport

bearer is acknowledged by the Source RNC.Note 2: This message is not necessary when the source RNC is the

SRNC.

9.13.1.3Hard Handover with switching in the CN (UE connected to two CN nodes, DCHstate)

This example shows Inter-RNS Hard Handover with switch in CN, in a situation in which the UE is connected to two

CN nodes simultaneously node and will be using one node B directly under the target RNC after the hard handover.


47/75

25.931 V1.1.0 1 1999-0648

2. Relocation RequiredRA N A P RAN A P

RA N A P RAN A P

3. Relocation

Request

RAN A P RA NA P

6. Relocation

Request

Acknowledge

RA N A P RA N A P1. Relocation Required

UE N ode B

Target

RN C

Source

RN C target M SC /SG SN SG SN /M SC

RA N A P RAN A P4. Relocation Request

RA NA P RA N A P7. Relocation Request Acknowledge

RA N A P RAN A P

14. Relocation

Comple te

RA NA P RA N A P15. Relocation Complete

RA NA P RA N A P8. Reloca tion Comm and

RA N A P

9. Reloca tion Comm and

RA N A P

RRC RRC13. D C C H: Handover Comple te

RA N A P RAN A P

11. Relocation

Detect

RA N A PRA N A P12. Relocation Detect

RR C10. D C C H: Handover Command

RR C

[Hard Handover]

RA N A P16. Iu Release Comman d

RA N A P

RA N A P 17. Iu Release Comman d RA N A P

5. ALCAP Iu Data

Transport Bearer Se tup

18. ALCAP Iu Data Transport Bearer Release

Hard Handover with switching in the CN (UE connected to two CN nodes, DCH state)

Serving RNC makes the decision to perform the Hard Handover via CN. Serving RNC also decides into which RNC

(Target RNC) the Serving RNC functionality is to be relocated.

1./2. SRNC sends Relocation Requiredmessages to both CN nodes.

Parameters: target RNC identifier, Information field transparent to the CN node and to be transmitted to thetarget RNC.

Upon reception of Relocation Requiredmessage CN element prepares itself for the switch and may also

suspend data traffic between UE and itself for some bearers.

3./4. When preparation is completed CN node conveys a Relocation Requestmessage to the target RNC.

Parameters: bearer ID's requested to be rerouted towards the CN node, from which the Relocation Request

originated.

CN indicates in the message whether it prefers point to multipoint type of connections within CN or hard

switch in CN. In this example the latter is assumed.

Target RNC allocates necessary resources within the UTRAN to support the radio links to be used after

completion of the Hard Handover procedure.

5./6./7 Target RNC and CN node establish the new Iu transport bearers for each Radio Access Bearer related to theCN node. When RNC has completed preparation phase, Relocation Request Acknowledgeis sent to the CN

element.

Parameters: transparent field to the CN which is to be transmitted to the Source RNS.


48/75

25.931 V1.1.0 1 1999-0649

.8./9. When CN is ready for the change of SRNC, CN node sends a Relocation Commandto the RNC. Message

contains the transparent field provided by Target RNC.

Parameters: information provided in the Information field from the target RNC.

9. Source RNC sends a RRC message Handover Command(Hard Handover) to the UE.

Parameters: Handover type.

11./12. When target RNC has detected the UE, Relocation Detectmessage is sent to the CN nodes.Target RNC switches also the connection towards the new Iu, when UE is detected. After the switch UL

traffic from node-B's is routed via the newly established MDC to the new MAC/RLC entities and finally to

the correct Iu transport bearer.

DL data arriving from the new Iu link is routed to newly established RLC entities, to the MAC and to the

MD-splitter and Nodes B.

13. When the RRC connection is established with the target RNC and necessary radio resources have been

allocated the UE sends RRC message Handover completeto the target RNC.

14./15 After a succesful switch and resource allocation at target RNC, RNC sends Relocation Completemessages

to the involved CN nodes.

At any phase, before the Relocation Completemessage is sent, the old communication link between the CN

and UE is all the time existing and working and the procedure execution can be stopped and originalconfiguration easily restored. If any such unexpectional thing occurs a Relocation Failuremessage may be

sent instead of any message numbered 3-10 and 13-14 described in this above.

16./17. The CN nodes initiates the release of the Iu connections to the source RNC by sending RANAP message Iu

Release Command.

18. Upon reception of the release requests from the CN nodes the old SRNC executes all necessary procedures to

release all visible UTRAN resources that were related to the RRC connection in question.

9.13.2Forward Hard Handover

This sections shows some examples of hard handover in the case of mobile initiated forward handovers.

Some examples of Cell Update procedures are shown, i.e. those procedures that update the position of the UE when a

RRC connection exists and the position of the UE is known on cell level in the UTRAN.

Cell Update with with SRNS relocation

This example shows Inter-RNS Cell Update with switching in the CN (with SRNS relocation).

UE Serving

RN C

RNSAP

4. CCCH: Cell Update Confirm

[S-RNTI, SRNC-ID, new S-RNTI,

new SRNC-ID, new C-RNTI]

Target

RN C

RNSAP2. Uplink Signalling Transfer

CN

3. Serving RNC Relocation

Allocate C- RNTI

RR CRR C

Decision to perform

SRNC relocation

Allocate S- RNTI,

SRNC-ID

[C-RNTI, UL message]

Reception of UL

CCCH message.

Decoding of RNC-ID

from the UL message

Cell Update with SRNS Relocation

1. UE sends a RRC message Cell Update to the UTRAN, after having made cell re-selection. Upon reception of aCCCH message from a UE, controlling RNC allocates a C-RNTI for the UE.


49/75


50/75

25.931 V1.1.0 1 1999-0651

5. Upon reception of the RNSAP message SRNC decides not to perform a SRNS Relocation towards the targetRNC.

6. SRNC replies with the RNSAP DOWNLINK SIGNALLING TRANSFER message containing the DL RRCmessage to be sent to UE. Message includes also the C-RNTI and the Cell-ID indicated in the proceeding CTCH

Indication message.

The CTCH DATA RESPONSE message, used as a response to a CTCH DATA INDICATION message when

the SRNC decides not to perform the SRNS Relocation, is introduced in contribution R3-99N23.

7. The Cell Update Confirm is sent to the UE

8. SRNC send the C-RNTI Release to source RNC. Source RNC releases the C-RNTI.

Note: It is ffs. whether a Cell Update Complete is needed to confirm the successful reception of Cell Update Confirm.

The decision is to be made by 3GPP RAN WG2.

URA Update

This section presents some examples of URA Update procedures, i.e. those procedures that update the UTRAN

registration area of a UE when a RRC connection exists and the position of the UE is known

umts signalling.pdf

Documents