UMTS Signalling PDF

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

Agenda:
Source: Editor (CSELT)
Title: 25.931 v1.1.1
UTRAN 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
3GPP
TR 25.931 V<1.1.10> (<1999-06>)
Technical Specification
3
rd
Generation Partnership Project (3GPP);
Technical Specification Group (TSG) RAN;
UTRAN Functions, Examples on Signalling Procedures
Reference
<Workitem> (<Shortfilename>.PDF)
Keywords
<keyword[, keyword]>
3GPP
Postal address
Office address
Internet
secretariat@3gpp.org
Individual 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.

25.931 V1.1.0 1 1999-06
5
Contents
1. Intellectual Property Rights........................................................................................................................ 7
2. Foreword .................................................................................................................................................... 7
3. Scope.......................................................................................................................................................... 7
4. References .................................................................................................................................................. 7
5. Definitions, abbreviations and notation ..................................................................................................... 8
5.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.......................................................................................................................................... 10
6.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)................................................................... 16
8.1 System Information Broadcasting....................................................................................................................... 16
9. Procedures related to a specific UE ......................................................................................................... 16
9.1 Paging................................................................................................................................................................. 17
9.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............................................................................................................................... 21
9.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 .............................................................................................................. 32
9.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
25.931 V1.1.0 1 1999-06
6
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.................................................................................................................................. 37
9.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 UTRAN GSM/BSS ............................................................................................................................... 55
9.15.2 GSM/BSS UTRAN............................................................................................................................... 57
9.15.3 UTRAN GPRS...................................................................................................................................... 58
9.15.4 UTRAN GSM/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) ............................................................. 62
9.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
25.931 V1.1.0 1 1999-06
7
1.Intellectual Property Rights
2.Foreword
This Technical Specification has been produced by the 3
rd
Generation Partnership Project, Technical Specification
Group RAN.
The contents of this TR may be subject to continuing work within the 3GPP and may change following formal TSG
approval. Should the TSG modify the contents of this TR, it will be re-released with an identifying change of release
date and an increase in version number as follows:
Version m.t.e
where:
m indicates [major version number]
x the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
etc.
y the third digit is incremented when editorial only changes have been incorporated into the specification.
3.Scope
This document describes the UTRAN functions by means of signalling procedure examples (Message Sequence Charts).
The signalling procedure examples show the interaction between the UE, the different UTRAN nodes and the CN to
perform system functions. This gives an overall understanding of how the UTRAN works in example scenarios
4.References
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply;
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity);
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case the latest version applies.
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[5] 25.931UTRAN Overall Description
[6] 25.414 UTRAN I
u
Interface RANAP Signalling
25.931 V1.1.0 1 1999-06
8
[7] 25.424 UTRAN I
ur
Interface RNSAP Signalling
[8] 25.434 UTRAN I
ub
Interface 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 Control
RNC 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:
25.931 V1.1.0 1 1999-06
9
Messages are always exchanged between nodes, i.e. the sender and the receiver of a message are nodes and not
single 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 the
procedures;
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 may
be indicated before the message name as shown in Figure 1.
UE Node B
Drift RNS
Node B
Serving RNS
RNC
Drift
RNC
Serving
CN
NBAP
MAC
NBAP
RANAP RANAP
RNSAP RNSAP
MAC
1. RACH : Message
RRC RRC
2. CCCH : Message
3. Message
6. Message
5. Message
[Parameters]
[Parameters]
[Parameters]
[Parameters]
[Parameters]
Action descr iption
NBAP NBAP
4. Message
[Parameters]
ALCAP Iub Bear er Setup/Release ALCAP Iur Bearer Setup
DCH DS DCH DS
7. DCH Data Fr ame
[Parameters]
Figure 1: Example of signalling procedure notation
25.931 V1.1.0 1 1999-06
10
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 CN
Uu 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 CN
Uu Iub Iur Iu
Transport Layers
Transport Layer
Transport Layers
RRC RNSAP RANAP RANAP
Transport Layers
RNSAP
DRNC
DCH, RACH, FACH, DSCH
RACH, FACH
DCCH
CCCH, DCCH
Figure 3: UTRAN and UE control plane protocol architecture (connected mode)
25.931 V1.1.0 1 1999-06
11
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 RNC CN
RAB Assignment Request RAB Establishment
RAB Release
Inter-RNS HO with switching in the CN
CN Source RNC
CN Source RNC
CN Source RNC
RAB Assignment Complete RAB Establishment
RAB Release
Source RNC CN
Source RNC CN
Relocation Required Hard HO with switching in the CN
UTRAN GSM/BSS handover
SRNS Relocation
Source RNC CN
Source RNC CN
Source RNC CN
Relocation Request Hard HO with switching in the CN
GSM/BSS handover UTRAN
SRNS Relocation
CN Target RNC
CN Source RNC
CN Target RNC
CN Target RNC
Relocation Request Acknowlede Hard HO with switching in the CN
SRNS Relocation
Target RNC CN
Target RNC CN
Target RNC CN
Relocation Command Hard HO with switching in the CN
SRNS Relocation
CN Source RNC
CN Source RNC
Relocation Detect Hard HO with switching in the CN
Target RNC CN
Target RNC CN
Relocation Complete Hard HO with switching in the CN
SRNS Relocation
Target RNC CN
Target RNC CN
Target RNC CN
Relocation Failure SRNS Relocation RNC CN
Iu Release Command Hard HO with switching in the CN
SRNS Relocation
CN Source RNC
CN Source RNC
CN Source RNC
Iu Release Complete Hard HO with switching in the CN Source RNC CN
25.931 V1.1.0 1 1999-06
12
SRNS Relocation
Source RNC CN
Source RNC CN
Paging Paging CN SRNC
RNSAP Procedures & Messages
For a detailed description of RNSAP procedures and messages refer to [7].
Radio Link Reconfiguration
Prepare
RAB Establishment
RAB Release
SRNC DRNC
SRNC DRNC
Radio Link Reconfiguration Ready RAB Establishment
RAB Release
DRNC SRNC
DRNC SRNC
Radio Link Reconfiguration RAB Establishment
RAB Release
SRNC DRNC
SRNC DRNC
Response
RAB Establishment
RAB Release
DRNC SRNC
DRNC SRNC
Commit
RAB Establishment
RAB Release
SRNC DRNC
SRNC DRNC
Radio Link Addition Soft Handover SRNC DRNC
Radio Link Addition Response Soft Handover DRNC SRNC
Radio Link Deletion Soft Handover SRNC DRNC
Radio Link Deletion Response Soft Handover DRNC SRNC
SRNS Relocation Commit SRNS Relocation Source RNC Target
RNC
NBAP Procedures & Messages
For a detailed description of NBAP procedures and messages refer to [8].
Radio Link Setup RRC Connection Establishment RNC Node B
25.931 V1.1.0 1 1999-06
13
Hard Handover
Soft Handover
RNC Node B
RNC Node B
Radio Link Setup Respose RRC Connection Establishment
Hard Handover
Soft Handover
Node B RNC
Node B RNC
Node B RNC
Radio Link Addition Soft Handover RNC Node B
Radio Link Addition Response Soft Handover RNC Node B
Radio Link Deletion RRC Connection Release
Hard Handover
Soft Handover
RNC Node B
RNC Node B
RNC Node B
Radio Link Deletion Response RRC Connection Release
Hard Handover
Soft Handover
Node B RNC
Node B RNC
Node B RNC
Prepare
RAB Establishment
RAB Release
RNC Node B
RNC Node B
Radio Link Reconfiguration Ready RAB Establishment
RAB Release
Node B RNC
Node B RNC
Commit
RAB Establishment
RAB Release
RNC Node B
RNC Node B
Paging Paging RNC Node 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.
25.931 V1.1.0 1 1999-06
14
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 Request
Q.aal2 Q.aal2
Q.aal2 Q.aal2
Establish Confirm
9Establish Request
Q.aal2 Q.aal2
Q.aal2 Q.aal2
Establish Confirm
Establish Request
Q.aal2 Q.aal2
Q.aal2 Q.aal2
Establish Confirm
Establish Request
Q.aal2 Q.aal2
Q.aal2 Q.aal2
Establish Confirm
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. UE SRNC DCCH
Direct Transfer NAS Signalling Conn. Est. UE SRNC DCCH
RRC Connection Request RRC Connection Est. UE SRNC CCCH
RRC Connection Setup RRC Connection Est. SRNC UE CCCH
RAB Setup RAB Establishment SRNC UE DCCH
RAB Setup Complete RAB Establishment UE SRNC DCCH
RAB Release RAB Release SRNC UE DCCH
RAB Release Complete RAB Release UE SRNC DCCH
Handover Command
Hard Handover SRNC UE
DCCH
25.931 V1.1.0 1 1999-06
15
Handover Complete
Hard Handover UE SRNC
DCCH
Active Set Update Soft Handover SRNC UE DCCH
Active Set Update Complete Soft Handover UE SRNC DCCH
Paging Paging for a UE in RRC Connected
Mode
SRNC UE DCCH
25.931 V1.1.0 1 1999-06
16
UTRAN Signaling Procedures
The signalling procedures shown in the following sections do not represent the complete set of possibilities, nor do they
mandate 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 (global
procedures)
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. SYSTEM INFORMATION (FFS)
3. SYSTEM INFORMATION
2. SYSTEM INFORMATION (Iub) (FFS)
UE Node B CRNC CN
NBAP NBAP
RRC RRC
RANAP RANAP
4. SYSTEM INFORMATION RRC RRC
5. SYSTEM INFORMATION RRC RRC
25.931 V1.1.0 1 1999-06
17
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 Mode
This 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 Node B
1.1
Node B
2.1
RNC
1
RNC
2
CN
RANAP
RANAP 1. Paging
NBAP
NBAP
2. Paging
3. PCCH : Paging
RANAP RANAP
1. Paging
NBAP
NBAP
2. 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 message
Paging.
Parameters: UE identifier, Paging Type.
2. RNC1 and RNC2 forward Paging message via NBAP to corresponding Nodes B (for example Node B 1.1, Node B
2.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.
25.931 V1.1.0 1 1999-06
18
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 Ser ving
RNC
CN
RRC RRC
2. DCCH : Paging
RANAP RANAP
1. 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 Ser ving
RNC
CN
1. RRC Connection Establishment
RRC RRC
2. DCCH : UE Capability Information
RRC
RRC
3. DCCH : Direct Transfer
RANAP 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 Information to 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 Capability Information could be
transferred after the initial NAS message (step 3). This issue is FFS.
25.931 V1.1.0 1 1999-06
19
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 RNS
Ser ving
RNC
5. NodeB-SRNC Data Tr ansport Bearer Sync
(FDD only)
Allocate RNTI
Select L1 and L2
parameter s
RRC RRC
1. CCCH : RRC Connection Request
NBAP NBAP
3. Radio Link Setup Response
NBAP NBAP
2. Radio Link Setup
RRC
RRC
6. CCCH : RRC Connection Setup
Start RX
Start TX
4. ALCAP Iub Data Tr ansport Bearer Setup
RRC Connection Establishment - DCH Establishment
1. The UE initiates set-up of an RRC connection by sending RRC message Connection Request on 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 RRC
connection. When a DCH is to be set-up, NBAP message Radio Link Setup is 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 control
information.
25.931 V1.1.0 1 1999-06
20
3. Node B allocates resources, starts PHY reception, and responses with NBAP message Radio Link Setup
Response.
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 Transport
bearer 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 Setup is 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 Establishment
The 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. Iu RELEASE COMPLETE
1. Iu RELEASE COMMAND
10. RADIO LINK DELETION RESPONSE( Iub)
8. RADIO LINK DELETION( Iub)
9. RADIO LINK DELETION RESPONSE( Iub)
6. RADIO LINK DELETION(
Iub)
5. RRC CONNECTION RELEASE COMPLETE (FFS)
4. RRC CONNECTION RELEASE
11. RADIO LINK DELETION
RESPONSE( Iur)
( Iur)
UE Node B
Dri ft RNS
Node B
Servi ng RNS
Drift
RNC
Serving
RNC
CN
RRC RRC
RRC RRC
N B AP NBAP
N B AP NBAP
RN S AP RNSAP
NBAP NBAP
NBAP NBAP
RN S AP RNSAP
RANAP RANAP
RANAP RANAP
3. ALCAP Iu Bearer
RELEASE
ALCAP Iur BEARER
RELEASE
13. ALCAP Iub BEARER RELEASE
25.931 V1.1.0 1 1999-06
21
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 RELEASE COMPLETE
1. Iu RELEASE COMMAND
5. RRC CONNECTION RELEASE COMPLETE (FFS)
4. RRC CONNECTION RELEASE
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RRC RRC
RRC RRC
RANAP RANAP
RANAP RANAP
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).
25.931 V1.1.0 1 1999-06
22
16 DCCH: RRC Connection Re-establishment
Complete
14. Downlink Transfer
10. Radio Link Setup
9. Radio Link Setup
2. Uplink Tr ansfer
RNSAP RNSAP
RNSAP RNSAP
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
RNSAP RNSAP
15. Transmission of
Uu Signalling
Message
RRC RRC
1. Reception of Uu
Signalling Message
ALCAP Iub
Bear er Setup
13. ALCAP Iur Bearer Setup
8. ALCAP Iub Bear er
Release
5. ALCAP Iur
Bear er Release
4. Radio Link Deletion Response
RNSAP RNSAP
RNSAP RNSAP
3. Radio Link Delition
7 Radio Link Deletion Response
NBAP NBAP
NBAP NBAP
6 Radio Link Delition
UE S-RNC Old
D-RNC
Old
Node B
New
D-RNC
New
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 RRC
Connection Re-establishment Request message on CCCH.
2. The new RNC delivers this message transparently as Uplink Transfer message to the serving RNC.
3./4./5./6./7./8. The SRNC initiates release of Iur/Iub Data Transport bearer using ALCAP protocol and also
release 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 the
RNSAP message Radio Link Setup to the target RNC.
10. The target RNC sends the NBAP message Radio Link Setup to the target Node B.
11. Node B allocates resources, and responses with NBAP message Radio Link Setup Response.
12. Target RNC responses with RNSAP message Radio Link Setup Response.
25.931 V1.1.0 1 1999-06
23
13. Serving RNC initiates set-up of Iur / Iub Data Transport bearer using ALCAP protocol. This request
contains the AAL2 Binding Identity to bind the Iur / Iub Data Transport Bearer to the DCH. The request for
set-up of Iur / Iub Data Transport bearer is acknowledged by target RNC / Node B.
14. The serving RNC sends the transparent RNSAP message Downlink transfer to 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 the
serving 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 Establishment
The 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.].
25.931 V1.1.0 1 1999-06
24
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RNSAP RNSAP
7. Radio Link Reconfigur ation
Ready
RRC
RRC
16. DCCH : Radio Access Bear er Setup Complete
NBAP
NBAP
8. Radio Link Reconfigur ation Ready
NBAP
NBAP
6 Radio Link Reconfiguration Ready
11. NodeB-SRNC Data Transport Bearer Sync.
NBAP
NBAP
14. Radio Link Reconfigur ation Commit
RNSAP RNSAP
Commit
NBAP
NBAP
13. Radio Link Reconfigur ation Commit
RRC
RRC
15. DCCH : Radio Access Bear er Setup
Apply new transport format set
Select L1, L2 and Iu Data
Transport Bearer parameters
RANAP RANAP
17. RAB Assignment
Complete
10. ALCAP Iub Data Transport Bearer Setup
2. ALCAP Iu Data
Transport Bearer Setup
RANAP RANAP
1. RAB Assignment
Request
[Establishment]
RNSAP RNSAP
Prepar e
[DCH Addition]
NBAP
NBAP
4. Radio Link Reconfigur ation Prepare
[DCH Addition]
NBAP
NBAP
5. Radio Link Reconfigur ation Prepare
[DCH Addition]
ALCAP Iur Bearer Setup 9. 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 Binding
Identity 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 Reconfiguration
Prepare).
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 Reconfiguration
Prepare).
Parameters: Transport Format Set, Transport Format Combination Set, Power control information, , DL
channelisation code.
25.931 V1.1.0 1 1999-06
25
5. SRNC requests its Node B to prepare establishment of DCH to carry the RAB (Radio Link Reconfiguration
Prepare).
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 Transport
Bearer.
7. DRNC notifies SRNC that the preparation is ready (Radio Link Reconfiguration Ready).
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 AAL2
Binding 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 Binding
Identity 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 Commit is 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 Setup is 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 Complete to SRNC.
17. SRNC sends RANAP message RAB Assignment Complete to CN.
9.6.2DCH - DCH Establishment - Unsynchronized (PSTN/ISDN Core
Network
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.931 V1.1.0 1 1999-06
26
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RNSAP RNSAP
8. RL Reconfiguration
Response
RRC
RRC
16. Radio Access Bearer Setup Complete
NBAP NBAP
12. Radio Link Reconfiguration Response
NBAP
NBAP
RRC
RRC
15. Radio Access Bearer Setup
Apply new transport format set
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 RNSAP
[DCH Addition]
NBAP
NBAP
4. Radio Link Reconfiguration
[DCH Addition]
NBAP
NBAP
[DCH Addition]
Q.aal2 Q.aal2
Q.aal2 Q.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 Request
message.
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 Data
Transport 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 new
DCH. It include in the message that the modification shall be done immediately without waiting for the command
message.
25.931 V1.1.0 1 1999-06
27
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.
control information.
5. SRNC requests its Node B setup a new DCH in the existing Radio Link.
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.
Bearer.
8. DRNC notifies SRNC that the setup is done.
Bearer.
9. SRNC initiates setup of Iur Data Transport Bearer using ALCAP protocol. This request contains the AAL2 Binding
Identity 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.
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 SETUP RESPONSE
7. RADIO ACCESS BEARER SETUP COMPLETE
6. RADIO ACCESS BEARER SETUP
1. RAB SETUP
3. RADIO LINK SETUP
RESPONSE(Iub)
2. RADIO LINK SETUP(Iub)
UE Node B
Serving RNS
Serving
RNC
CN
RANAP RANAP
NBAP NBAP
NBAP NBAP
RRC RRC
RRC RRC
RANAP RANAP
4. ALCAP Iub BEARER SETUP
5. ALCAP Iu BEARER
SETUP
25.931 V1.1.0 1 1999-06
28
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 common
transport 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 SETUP RESPONSE
4. RADIO ACCESS BEARER SETUP COMPLETE
3. RADIO ACCESS BEARER SETUP
1. RAB SETUP
UE Node B
Serving RNS
Serving
RNC
CN
RRC RRC
RRC RRC
RANAP RANAP
RANAP RANAP
2. ALCAP Iu BEARER
SETUP
25.931 V1.1.0 1 1999-06
29
UE Node B
Drift RNS
Node B
Serving RNS
Dr ift
RNC
Serving
RNC
CN
RNSAP RNSAP
Ready
RRC
RRC
14. DCCH : Radio Access Bear er Release Complete
NBAP
NBAP
NBAP
NBAP
NBAP
NBAP
12. Radio Link Reconfiguration Commit
RNSAP RNSAP
Commit
RRC
RRC
13. DCCH : Radio Access Bear er Release
Apply new tr ansport for mat set
RANAP RANAP
2. RAB Assignment
Complete
NBAP
NBAP
11. Radio Link Reconfiguration Commit
16. ALCAP Iub Data Tr ansport Bearer Release
3. ALCAP Iu Data
Tr ansport Bearer Release
RANAP RANAP
1. RAB Assignment
Request
[Release]
RNSAP RNSAP
Pr epar e
[DCH Deletion]
NBAP
NBAP
5. Radio Link Reconfigur ation Pr epare
[DCH Deletion]
NBAP
NBAP
6. Radio Link Reconfigur ation Pr epare
[DCH Deletion]
ALCAP Iur Bear er Release 15. ALCAP Iub Data Tr ansport Bearer Release
Radio Access Bearer Release - DCH - DCH Release - Synchronized
1. CN initiates release of the radio access bearer with RANAP message RAB Assignment Request.
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 Reconfiguration Request).
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).
8. DRNC notifies SRNC that release preparation is ready (Radio Link Reconfiguration Proceed).
25.931 V1.1.0 1 1999-06
30
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 Commit is sent from SRNC to DRNC.
11. NBAP message Radio Link Reconfiguration Commit is sent from DRNC to Node B.
12. NBAP message Radio Link Reconfiguration Commit is sent from SRNC to Node B.
Parameters:
13. RRC message Radio Access Bearer Release is 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 Complete to 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 protocol
16. Not used resources in SRNC and NodeB (Serving RNS, if any) are released. SRNC initiates release of Iub (Serving
RNS) 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.
25.931 V1.1.0 1 1999-06
31
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RNSAP RNSAP
Response
RRC
RRC
3. Radio Access Bearer Release Complete
NBAP
NBAP
NBAP
NBAP
RRC
RRC
2. Radio Access Bearer Release
RANAP RANAP
4. RAB Assignment
Complete
12. ALCAP Iub Data Transport Bearer Release
5. ALCAP Iu Data
Transport Bearer Release
RANAP RANAP
1. RAB Assignment
Request
[Release]
RNSAP RNSAP
[DCH Deletion]
NBAP
NBAP
[DCH Deletion]
NBAP
NBAP
[DCH Deletion]
ALCAP Iur Bearer Release 11. 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 ALCAP
protocol.
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.
8. SRNC requests its Node B to prepare release of DCH carrying the RAB.
9. Node B acknowledges DRNC.
10. DRNC acknowledges SRNC.
11. Node B acknowledges SRNC
25.931 V1.1.0 1 1999-06
32
12. SRNC initiates release of Iur Data Transport bearer using ALCAP protocol. Note: the release of the Iur link may
be 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 ACCESS BEARER RELEASE
5. RADIO ACCESS BEARER RELEASE COMPLETE
2. RAB RELEASE
RESPONSE
1. RAB RELEASE
UE Node B
Drift RNS
Node B
Serving RNS
Dr ift
RNC
Serving
RNC
CN
RANAP RANAP
RRC RRC
RRC RRC
RANAP RANAP
3. ALCAP Iu
BEARER RELEASE
25.931 V1.1.0 1 1999-06
33
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).
25.931 V1.1.0 1 1999-06
34
9.9.1DCH to DCH Modification
This example shows modification of a radio access bearer on a dedicated channel (DCH)
25.931 V1.1.0 1 1999-06
35
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 RECONFIGURATION
RESPONSE
4. RADIO ACCESS BEARER RECONFIGURATION COMPLETE
3. RADIO ACCESS BEARER RECONFIGURATION
UE Node B
Serving RNS
Serving
RNC
CN
RANAP RANAP
RRC RRC
RRC RRC
RANAP RANAP
2. ALCAP Iu BEARER
RECONFIGURATION
6. RADIO ACCESS BEARER RECONFIGURATION COMPLETE
RESPONSE
3. RADIO LINK SETUP
RESPONSE(Iub)
UE Node B
Serving RNS
Ser ving
RNC
CN
NBAP NBAP
NBAP NBAP
RRC RRC
RRC RRC
RANAP RANAP
RANAP RANAP
4. ALCAP Iu BEARER
RECONFIGURATION
25.931 V1.1.0 1 1999-06
36
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.
COMPLETE
RESPONSE(Iur )
(Iur )
RESPONSE(Iub)
6. RADIO LINK DELETION(Iub)
UE Node B
Drift RNS
Node B
Serving RNS
Dr ift
RNC
Serving
RNC
CN
RANAP RANAP
RRC RRC
RRC RRC
RNSAP RNSAP
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
Cell Update Procedure + Streamlining
(FFS)
ALCAP Iur BEARER RELEASE 9. ALCAP Iub BEARER RELEASE
2. ALCAP Iu BEARER
RECONFIGURATION
25.931 V1.1.0 1 1999-06
37
9.10Physical Channel Reconfiguration
The following example show the reconfiguration from one channel type to another(DCH to DCH)
9.11Channel Type Switching
The following examples show switching from one channel type to another.
9.11.1RACH/PCH to RACH/FACH
This example shows channel switching from RACH/PCH to RACH/FACH (URA connected to CELL Connected).
Note: The case showed is for when SRNS decides to perform an SRNS relocation immediately after a channel type
switching.
NOTE: The first and the second transition are included when the procedure is intitiated by UTRAN
2. PAGING
UE Node B
Serving RNS
Serving
RNC
CN
RRC RRC
Case1
1. PAGING NBAP NBAP
25.931 V1.1.0 1 1999-06
38
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 DCH
This example shows channel switching from RACH/FACH to DCH.
5. ACTIVE SET UPDATE COMPLETE
4. ACTIVE SET UPDATE
2. RADIO LINK SETUP
RESPONSE(Iub)
UE Node B
Serving RNS
Ser ving
RNC
CN
NBAP NBAP
NBAP NBAP
RRC RRC
RRC RRC
25.931 V1.1.0 1 1999-06
39
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 CHANNEL RECONFIGURATION COMPLETE
1. PHYSICAL CHANNEL RECONFIGURATION
RESPONSE(Iur )
(Iur )
RESPONSE(Iub)
UE Node B
Drift RNS
Node B
Serving RNS
Dr ift
RNC
Serving
RNC
CN
RRC RRC
RRC RRC
RNSAP RNSAP
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
(FFS)
ALCAP Iur BEARER RELEASE 7. ALCAP Iub BEARER RELEASE
25.931 V1.1.0 1 1999-06
40
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
Drift RNS
Dr ift
RNC
Ser ving
RNC
6. NodeB-SRNC Data Tr ansport Bearer Sync.
RNSAP RNSAP
1. Radio Link Addition
Start TX
NBAP NBAP
2. Radio Link Setup
RNSAP RNSAP
Response
NBAP NBAP
3. Radio Link Setup
Respose
Start RX
Decision to setup
new RL
RRC RRC
8. DCCH : Active Set Update Complete
RRC RRC
7. DCCH : Active Set Update
[Radio Link Addition]
ALCAP Iur Bearer Setup 5. ALCAP Iub Bear er 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 radio
resources 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 scrambling
code, DL channelisation code.
3. Node B allocates requested resources. Successful outcome is reported in NBAP message Radio Link Setup
Response.
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 Response to 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 AAL2
Binding Identity to bind the Iub Data Transport Bearer to DCH.
This may be repeated for each Iur/Iub Data Transport Bearer to be setup.
25.931 V1.1.0 1 1999-06
41
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
Drift RNS
Dr ift
RNC
Ser ving
RNC
RRC RRC
Decision to delete
old RL
RNSAP RNSAP
3. Radio Link Deletion
NBAP NBAP
RNSAP RNSAP
Response
NBAP NBAP
Response
Stop RX and TX
RRC RRC
1. DCCH : Active Set Update
[Radio Link Deletion]
ALCAP Iur Bearer Release 7. ALCAP Iub Bear er 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 Active
Set 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 Update Complete.
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.
5. Node B deallocates radio resources. Successful outcome is reported in NBAP message Radio Link Deletion
Response.
6. DRNC sends RNSAP message Radio Link Deletion Response to SRNC.
7. SRNC initiates release of Iur/Iub Data Transport Bearer using ALCAP protocol.
25.931 V1.1.0 1 1999-06
42
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 RNSAP
Start TX
RNSAP RNSAP
Response
NBAP NBAP
2. Radio Link Setup
NBAP NBAP
Start RX
Decision to setup
new RL and
release old RL
NBAP
9. Radio Link Release
NBAP NBAP
10. Radio Link Release Proceed
Stop RX and TX
11. ALCAP Iub Data Transport Bear er Release
RRC RRC
RRC RRC
7. DCCH : Active Set Update Command
[Radio Link Addition & Deletion]
NBAP
UE Node B
Drift RNS
Node B
Serving RNS
Dr ift
RNC
Ser ving
RNC
ALCAP Iur Bearer Setup 5. ALCAP Iub Data Transport Bear er 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 RRC
message Active Set Update Complete.
9. 11. See description 3. 7. in Section 9.12.2
25.931 V1.1.0 1 1999-06
43
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
25.931 V1.1.0 1 1999-06
44
9.13.1.1Intra Node B Hard Handover (DCH State)
12. RADIO LINK DELETION RESPONSE(Iub)
RESPONSE(Iur)
(Iur)
RESPONSE(Iub)
3. RADIO LINK ADDITION(Iub)
1. RADIO LINK ADDITION(Iub)
7. HANDOVER COMMAND
8. HANDOVER COMPLETE
6. RADIO LINK ADDITION
RESPONSE(Iur)
RESPONSE(Iub)
RESPONSE(Iub)
(Iur)
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
RRC RRC
RRC RRC
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
25.931 V1.1.0 1 1999-06
45
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
DCH:
Measurements
UE CRNC
Source
CRNC
Target
SRNC
Time during which
data transmission and
reception is suspended
MSC/SGSN
Target
RRC
4. Handover Command
On measurements results,
RNC decides to initiate a
Hard Handover
2. Common Channels are established on Iur
(FFS)
RRC
5. DCH: Handover
Complete
RRC
7. CCTH Release Request
RRC
RRC
8. CCTH Release Complete
(FFS if needed)
RRC
6.-Handover Complete
Whether this message is RNSAP or no it is
FFS
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
25.931 V1.1.0 1 1999-06
46
RNSAP RNSAP
1. Radio Link
Setup Request
Note 1
UE Node B
Source
Node B
Target
RNC
Source
RNC
target
SRNC
RRC
RRC
8. DCCH : Handover Complete
RNSAP
5. RL Setup
Response
Note 1
RRC
7. DCCH : Handover Command
RRC
[Hard Handover]
6. ALCAP Iur Data
Note 1
NBAP NBAP
2. Radio Link Setup
NBAP NBAP
NBAP NBAP
NBAP NBAP
11. Radio Link Deletion Response
12. ALCAP Iub Data Transport Bearer Release
RNSAP RNSAP
RNSAP RNSAP
Note 2
13. Radio Link
Deletion Response
Note 2
14. ALCAP Iur Data
Transport Bearer Release
Note 2
RNSAP
Hard Handover via Iur (DCH on Iur)
1. SRNC sends Radio Link Setup Request message 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 NBAP
message Radio Link Setup to 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 Link Setup
Response.
Parameters: Signalling link termination, Transport layer addressing information for the Iub Data Transport Bearer.
25.931 V1.1.0 1 1999-06
47
4. Target RNC initiates set-up of Iub Data Transport bearer using ALCAP protocol. This request contains the AAL2
Binding Identity to bind the Iub Data Transport Bearer to the DCH. The request for set-up of Iub Data Transport
bearer is acknowledged by Node B.
5. When the Target RNC has completed preparation phase, Radio Link Setup Response is 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 Binding
Identity 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 Command to the UE.
8. When the RRC connection is established with the target RNC and necessary radio resources have been allocated the
UE sends RRC message Handover Complete to the SRNC.
9. The SRNC sends a RNSAP message Radio Link Deletion to the source RNC. Note 2: This message is not
necessary when the source RNC is the SRNC.
10. The source RNC sends NBAP message Radio Link Deletion to the source Node B.
11. The source Node B de-allocates radio resources. Successful outcome is reported in NBAP message Radio Link
Deletion 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 the
SRNC. 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 AAL2
Binding 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, DCH
state)
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.
25.931 V1.1.0 1 1999-06
48
2. Relocation Requir ed
RANAP RANAP
RANAP RANAP
3. Relocation
Request
RANAP RANAP
6. Relocation
Request
Acknowledge
RANAP RANAP
1. Relocation Requir ed
UE Node B
Target
RNC
Source
RNC tar get MSC/SGSN SGSN/MSC
RANAP RANAP
4. Relocation Request
RANAP RANAP
7. Relocation Request Acknowledge
RANAP RANAP
14. Relocation
Complete
RANAP RANAP
15. Relocation Complete
RANAP RANAP
8. Relocation Comman d
RANAP
9. Relocation Comman d
RANAP
RRC RRC
13. DCCH : Han dover Complete
RANAP RANAP
11. Relocation
Detect
RANAP
RANAP 12. Relocation Detect
RRC
10. DCCH : Han dover Comman d
RRC
[Hard Handover]
RANAP
16. Iu Release Command
RANAP
RANAP
RANAP
5. ALCAP Iu Data
Tr anspor t Bear er Setup
18. ALCAP Iu Data Tr an spor t Bear er 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 Required messages to both CN nodes.
Parameters: target RNC identifier, Information field transparent to the CN node and to be transmitted to the
target RNC.
Upon reception of Relocation Required message 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 Request message 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 the
CN node. When RNC has completed preparation phase, Relocation Request Acknowledge is sent to the CN
element.
Parameters: transparent field to the CN which is to be transmitted to the Source RNS.
25.931 V1.1.0 1 1999-06
49
.8./9. When CN is ready for the change of SRNC, CN node sends a Relocation Command to 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 Detect message 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 complete to the target RNC.
14./15 After a succesful switch and resource allocation at target RNC, RNC sends Relocation Complete messages
to the involved CN nodes.
At any phase, before the Relocation Complete message 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 original
configuration easily restored. If any such unexpectional thing occurs a Relocation Failure message 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 Ser ving
RNC
RNSAP
4.CCCH: Cell Update Confirm
[S-RNTI, SRNC-ID, new S-RNTI,
new SRNC-ID, new C-RNTI]
Target
RNC
RNSAP
2. Uplink Signalling Transfer
CN
3. Serving RNC Relocation
Allocate C- RNTI
RRC RRC
Decision to per form
SRNC r elocation
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 a
CCCH message from a UE, controlling RNC allocates a C-RNTI for the UE.
25.931 V1.1.0 1 1999-06
50
2. Controlling RNC forward the received uplink CCCH message towards the SRNC by RNSAP Cell/URA Update
Indication message. C-RNC includes the allocated C-RNTI to the RNSAP message, which is used as a UE
identification within the C-RNC. Upon reception of the RNSAP message SRNC decides to perform a SRNS
Relocation towards the target RNC.
3. Serving RNC relocation procedure is executed as defined in Chapter SRNS Relocation (UE connected to a single
CN node). After completing SRNS Relocation, target RNC allocates new S-RNTI for the UE.
4. Serving RNC responds to UE by RRC Cell Update Confirm, including old S-RNTI and SRNC ID as UE
identifiers. Message contains also the new S-RNTI, SRNC-ID and C-RNTI.
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.
9.13.2.2Cell Update via Iur without SRNS relocation
This example shows an Inter RNS cell update in DRNS without SRNS relocation. In this example target RNS, source
RNS and serving RNS are all located separately from each other. Other scenarios can be easily derived from this most
comprehensive signalling procedure.
UE DRNC
Source
DRNC
Target
SRNC MSC/SGSN
RNSAP RNSAP
8. c-RNTI Release
3. Allocate C- RNTI
5. Decision:
Not to perform
SRNC relocation
RNSAP RNSAP
1. Reception of UL
DCCH/CCCH message.
2. Decoding of RNC-ID
from the UL message
RNSAP RNSAP
6. Downlink Signalling Transfer
Release C- RNTI
7. Sending DL
DCCH/CCCH
message
Cell Update via Iur without SRNS Relocation
1. UE sends a RRC message Cell Update to the UTRAN, after having made cell re-selection.
2. Upon reception of a CCCH/DCHT message from a UE, controlling RNC decodes the RNC ID and the S-RNTI.
3. The UE is not registered in the CRNC (RNC ID and SRNTI unknown), thus CRNC allocates C-RNTI for the
UE.
4. Controlling RNC forward the received uplink CCCH/DCCH message towards the SRNC by RNSAP UPLINK
SIGNALLING TRANSFER message. Messages includes also the cell-ID of the cell from which the message was
received and the allocated C-RNTI.
The CTCH DATA INDICATION message, used to transfer the received message from CRNC to SRNC any
CCCH/DTCH message that uses the RNC-ID plus S-RNTI as UE identifier, is introduced in contribution R3-
99N23.
25.931 V1.1.0 1 1999-06
51
5. Upon reception of the RNSAP message SRNC decides not to perform a SRNS Relocation towards the target
RNC.
6. SRNC replies with the RNSAP DOWNLINK SIGNALLING TRANSFER message containing the DL RRC
message 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 on URA level in the
UTRAN.
9.14.1Inter-RNS URA Update with SRNS Relocation
This example shows Inter-RNS URA Update with switching in the CN.
UE Ser ving
RNC
RNSAP
4.CCCH: URA Update Confir m
[S-RNTI, SRNC-ID,
new S-RNTI, new SRNC-ID]
Target
RNC
RNSAP
CN
3. Serving RNC Relocation
Allocate C- RNTI
RRC RRC
Decision to per form
SRNC r elocation
AllocateS- RNTI,
SRNC-ID,
Delete C-RNTI
Reception of UL
CCCH message
Decoding of RNC-ID
from the UL message
Inter RNS URA Update with switching in CN.
1. UE sends a RRC message URA Update to the UTRAN, after having made cell re-selection. Upon reception of a
CCCH message from an unknown UE, controlling RNC allocates a new C-RNTI for the UE.
2. Controlling RNC forwards the received uplink CCCH message towards the SRNC by RNSAP by RNSAP
UPLINK SIGNALLING TRANSFER message. Message includes alsoCell/URA Update Indication message. C-
RNC includes the allocated C-RNTI, which is to be used as a UE identification within the C-RNC, to the RNSAP
message. Upon reception of the RNSAP message SRNC decides to perform a SRNS Relocation towards the
target RNC.
3. Serving RNC relocation procedure is executed as defined in Chapter 'SRNS Relocation (UE connected to a
single CN node)'. After having completed SRNS Relocation, target RNC allocates new S-RNTI for the UE. New
SRNC also deletes the allocated C-RNTI, since it is not needed for an UE in RACH/PCH state.
4. Serving RNC acknowledges the message by RRC URA Update Confirm, including old S-RNTI and SRNC ID as
UE identifiers. Message contains also the new S-RNTI and RNC-ID.
25.931 V1.1.0 1 1999-06
52
It is ffs. whether a URA Update Complete is needed to confirm the successful reception of URA Update Confirm. The
decision is to be made by 3GPP RAN WG2.
9.14.2Inter-RNS URA Update via Iur without SRNS relocation
This example shows an Inter RNS URA update in DRNS without SRNS relocation. In this example target RNS, source
RNS and serving RNS are all located separately from each other. Other scenarios can be easily derived from this most
comprehensive signalling procedure.
UE DRNC
Source
DRNC
Target
SRNC MSC/SGSN
3. Allocate C- RNTI
5. Decision:
Not to perform
SRNC relocation
RNSAP RNSAP
4. Uplink Signalling Trasfer
[C-RNTI,
Uu Signalling Message ]
1. Reception of Uu
Signalling Message
2. Decoding of RNC-ID
from the UL message
RNSAP RNSAP
6. Downlink Signalling
Transfer
7. Transmission of
Uu Signalling Message
8. Release of C- RNTI
[C-RNTI,
Uu Signalling Message ]
Inter-RNS URA Update via Iur without SRNS relocation
1. UE sends a RRC message URA Update to the UTRAN, after having made cell re-selection and URA has
changed.
2. Upon reception of the message from a UE, controlling RNC decodes the RNC ID and the S-RNTI.
3. The UE is not registered in the CRNC (RNC ID and SRNTI unknown), thus CRNC allocates C-RNTI for the
UE.
4. Controlling RNC forward the received Uu signalling message towards the SRNC by RNSAP UPLINK
SIGNALLING TRANSFER message. Messages includes also the cell-ID from which the message was received
and the allocated C-RNTI.
5. Upon reception of the RNSAP message SRNC decides not to perform a SRNS relocation towards the target
RNC.
6. SRNC replies with the RNSAP DOWNLINK SIGNALLING TRANSFER message containing the DL Uu
signalling message to be sent to UE. Message includes also the C-RNTI and the Cell-ID indicated in the
preceeding UPLINK SIGNALLING TRANSFER message.
7. The URA Update Confirm is sent to the UE
8. DRNC releases the allocated C-RNTI.
25.931 V1.1.0 1 1999-06
53
Time during which
data transmission and
reception is suspended
UE CRNC
Source
CRNC
Target
SRNC MSC/SGSN
RNSAP RNSAP
7. RNTI Release Confirm
RNSAP RNSAP
6. RNTI Release
Request
8. Iur User plane release if necessary
3. Common Channels are established on Iur (FFS).
Allocate C- RNTI
Decision:
Not to perform
SRNC relocation
RNSAP RNSAP
1. Reception of UL
DCCH/CCCH message.
Decoding of RNC-ID
from the UL message
RNSAP RNSAP
4. Downlink Signalling Transfer
5. Cell Update Confirm
RRC
Delete S-RNTI
Example of Inter RNS URA update via Iur
9.14.3SRNS Relocation (UE connected to two CN nodes)
This example shows SRNS Relocation, in situation in which the UE is connected to two CN nodes simultaneously. It is
assumed that:
all cells in the active set are in one DRNC;
the CN performs hard switching of the user traffic.
25.931 V1.1.0 1 1999-06
54
2. Relocation Required
RANAP RANAP
RANAP RANAP
6. Relocation
Request Ack.
RANAP RANAP
1. Relocation Required
UE Node B RNC
Source
RNC
Target
MSC/SGSN SGSN/MSC
RANAP RANAP
4. Relocation Request
RANAP RANAP 3. Relocation Request
RANAP RANAP
7. Relocation Request Ack.
RANAP RANAP
9. Relocation Command
RANAP RANAP
8. Relocation Command
RANAP RANAP
12. Relocation
Complete
RANAP RANAP
RNSAP RNSAP
10. SRNC Relocation
Commit
RANAP
RANAP
RANAP
RANAP
5. ALCAP Iu Data
15. ALCAP Iu Data Transport Bearer Relelase
SRNS Relocation (UE connected to two CN nodes)
Note that the SRNC makes the decision to perform the Serving RNC relocation procedure. The Serving RNC also
decides into which RNC (Target RNC) the Serving RNC functionality is to be relocated.
1./2. The source SRNC sends Relocation Required messages to both CN nodes.
Parameters: target RNC identifier, Information field that the CN node(s) shall pass transparently to the target
RNC. This transparent field contains the UE identifier, number of CN nodes and other TBD data.
Upon reception of Relocation Required message the CN element prepares itself for the switch and may also
suspend user data traffic and/or signalling between UE and itself for some bearers.
3./4. When preparation is completed the CN node conveys a Relocation Request message to the target RNC.
Parameters: indication of which bearers should be routed towards this CN node, transparent information field
sent by the source RNC, UE identifier.
The target RNC uses the UE identifier to link the requests from multiple CN nodes to each other and to the
resources (e.g. Iub links) that the UE is currently using.
FFS: The target RNC allocates necessary Iur branches to be used after the SRNS Relocation switch will be
made.
5. The target RNC and CN node establish the new Iu transport bearers for each Radio Access Bearer related to
that CN node.
6./7. When the source RNC and the target RNC have completed its preparation phase, Relocation Request
Acknowledge message is sent to CN.
25.931 V1.1.0 1 1999-06
55
8./9. When the CN node is ready for the SRNC move, the CN node indicates the completion of preparation phase at
the CN side for the SRNS Relocation by sending the Relocation Command message. To the source RNC and
the target RNC.
10. When the source RNC has received Relocation Command messages from all the CN nodes, the source RNC
sends a Relocation Commit message to the target RNC. The target RNC executes both the DL and UL switch
for all bearers at the earliest suitable time instance.
After the switch UL traffic from node-B's is routed via the newly established Macro Diversity Combiner to the
new MAC/RLC entities and finally to the correct Iu transport bearer. UL data transmission to the old Iur
transport bearer is ceased.
DL data arriving from the new Iu link is routed to newly established RLC entities, to the MAC and to the
Macro Diversity Splitter and Nodes B. The DL data received from the old Iur is discarded.
11./12. Immediately after a succesfull switch at RNC, target RNC (=SRNC) sends Relocation Complete messages to
the involved CN nodes.
Upon reception of messages 9 and 10, the CN switches from the old Iu transport bearers to the new ones.
13./14. After a successful switch at the CN node, the CN node initiates the release of the Iu connection to the source
RNC by sending the RANAP message Iu Release Command.
15 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.
At any phase, before the SRNS Relocation Complete message 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 original configuration easily
restored. If any such abnormal thing occurs a SRNS Relocation Failure may be sent instead of any message numbered
3-11 described.
HO between UTRAN and GSM/BSS
This section presents some examples of handover procedure from UTRAN to GSM/BSS and vice versa.
The case of a UTRAN connected to UMTS CN connected to a 2G-MSC (i.e. via MAP/E interface) is shown, while the
case of an UTRAN connected .a GSM CN trough an IWF (where RANAP is interworked with BSSMAP) is not shown
because is equivalent from the point of view of the UTRAN.
The case of HO between UTRAN and GPRS and viceversa are also considered.
11.
UTRAN GSM/BSS
This example shows how handover (Hard Handover) is performed from UTRAN to GSM/BSS between a UMTS CN
and a 2G-MSC.
Note: Procedures between CN and MSC, and between MSC and BSC are out of the scope of WG3, and are only
included for clarity.
25.931 V1.1.0 1 1999-06
56
MAP/E MAP/E
2. Pr epar e
Handover
BSSMAP BSSMAP
4. Handover
Request Ack
RANAP RANAP
13. Iu Release
Complete
BSSMAP BSSMAP
3. Handover
Request
MAP/E MAP/E
5. Pr epar e
Handover
Response
RANAP RANAP
6. Relocation
Command
BSSMAP BSSMAP
8. Handover
Detect
BSSMAP BSSMAP
10. Handover
Complete
MAP/E MAP/E
11. Send End
Signal
Request
MAP/E MAP/E
14. Send End
Signal Response
RANAP RANAP
1. Relocation
Required
UE Node B RNC
Serving
CN MSC BSC BTS
RRC
7. DCCH : Handover Command
RRC
[Hard Handover]
RR
9. Handover Complete
RR
RANAP RANAP
12. Iu Release
Command
1. Upon detection of a trigger SRNC sends RANAP message Relocation Required to the CN.
2. The UMTS CN will forward this request to the GSM MSC (indicated in the received message) over the MAP/E
interface (MAP message Prepare Handover).
Note: Steps 3&4 follow the normal GSM procedures and are shown only for clarity.
5. Once initial procedures are complete in GSM MSC/BSS the MSC returns MAP/E message Prepare Handover.
6. CN responds to the initial request from SRNC by sending RANAP message Relocation Command to the SRNC.
7. Via existing RRC connection, SRNC sends RRC message Handover Command (Hard Handover) to the UE.
Parameters: Handover type.
Note: Procedures related to synchronisation etc. to GSM BSS are not shown.
Note: Step 8&10 follow normal GSM procedures and are shown only for clarity.
11. Detection of the UE within the GSM coverage results in the MSC sending MAP/E message Send End Signal
Request to the CN.
25.931 V1.1.0 1 1999-06
57
12. CN initiates release of resources allocated by the former SRNC (Iu Release Command).
13. Previously allocated bearer resources are released within UMTS (e.g. using RANAP and ALCAP protocols
[ALCAP not shown]) (Iu Release Complete).
14. Procedure is concluded from UMTS point of view by CN sending MAP/E message Send End Signal Response
(this message is not sent until the end of the call).
9.15.2GSM/BSS UTRAN
This example shows how handover (Hard Handover) is performed from GSM/BSS to UMTS between a UMTS CN and
a 2G-MSC.
Note: Procedures between CN and MSC, and between MSC and BSC are out of the scope of WG3, and are only
included for clarity.
RANAP RANAP
3. Relocation
Request
BSSMAP BSSMAP
1. Handover
Required
RANAP RANAP
4. Relocation
Request Ack.
MAP/E MAP/E
5. Prepare Handover
Response
MAP/E MAP/E
2. Prepare
Handover
BSSMAP BSSMAP
6. Handover
Command
MAP/E MAP/E
11. Send End Signal
Request
BSSMAP BSSMAP
12. Clear
Command
BSSMAP BSSMAP
13. Clear
Complete
RANAP RANAP
UE Node B RNC
Target
CN MSC BSC BTS
MAP/E MAP/E
14. Send End Signal
Response
RRC
9. DCCH : Handover Complete
RRC
RR
7. Handover Command
RR
RANAP RANAP
8. Relocation
Detect
GSM/BSS UTRAN handover
1. The BSC sends Handover Required message to the GSM MSC.
2. The MSC sends MAP/E message Prepare Handover to the UMTS CN.
3. The CN sends RANAP message Relocation Request to the Target RNC.
4. Response Relocation Request Acknowledge is returned to the CN by the target RNC via RANAP.
25.931 V1.1.0 1 1999-06
58
5. MAP/E message Prepare Handover Response is sent by the UMTS CN to the MSC.
Note: Step 6&7 follow normal GSM procedures and are shown only for clarity.
8. When target RNC has detected the UE, RelocationDetect message is sent to the CN node.
9. When the RRC connection is established with the target RNC and necessary radio resources have been allocated the
UE sends RRC message Handover complete to the target RNC.
10. Once complete the target RNC sends RANAP message Relocation Complete to the CN.
11. CN sends MAP/E message Send End Signal Request to the MSC.
12. The MSC sends Clear Command message to the BSC.
13. The BSC responds with Clear Complete message to the GSM
15. The MSC sends MAP/E message Send End Signal Response to the UMTS CN to conclude the procedure (this
message is not sent until the end of the call).
Note: The possibility to perform handover from GSM/BSS=>UMTS going directly in macrodiversity state
(i.e.establishing directly multiple macrodiversity paths) is FFS
GPRS UTRAN
This section shows UTRAN signalling procedures for GPRS to UTRAN handover.
UE Serving
RNC
1. UE initiated signalling connection establishment
CN
2. Direct Transfer
3. Radio Access Bearer Establishment
1. The UE selects a UTRAN cell, reads system information, and initiates establishment of a NAS signalling
connection.
See section UE Initiated Signalling Connection Establishment.
2. The NAS signalling connection between UE and CN can now be used for NAS message transfer (e.g. execution of
security functions).
See section Direct Transfer.
3. After necessary CN-GPRS preparations (e.g. UE context information retrieval), CN initiates establishment of
RAB(s).
See section Radio Access Bearer Establishment.
25.931 V1.1.0 1 1999-06
59
UTRAN GPRS, UE Initiated
This section shows UTRAN signalling procedures for UTRAN to GPRS handover initiated by UE cell reselection.
UE CN
1. Cell Reselect ion
t riggered
Serving
RNC
RANAP RANAP
RANAP RANAP
2. Iu Release Complet e
1. The UE selects a GPRS cell, reads system information, and initiates establishment of UE-GPRS connection.
2. After necessary CN-GPRS preparations (e.g. UE context information retrieval), CN initiates release of Iu
connection. SRNC releases the RRC connection.
UTRAN GPRS, Network Initiated
This section shows UTRAN signalling procedures for UTRAN to GPRS handover triggered by Serving RNC.
UE CN Serving
RNC
RANAP RANAP
RANAP RANAP
3. Iu Release Complet e
RRC RRC
1. Handover Command
1. Based on UE measurements, SRNC triggers the handover to a GPRS cell by sending a Handover Command to the
UE. UE initiates establishment of UE-GPRS connection.
2. After necessary CN-GPRS preparations (e.g. UE context information retrieval), CN initiates release of the RRC
connection.
3. SRNC releases all resources reserved for the UE.
9.15.3UTRAN GPRS
This example shows how handover is performed from GSM/BSS to GPRS between a UMTS CN and a 2G-SGSN.
9.15.4UTRAN GSM/BSS
This example shows how handover is performed from GPRS to GSM/BSS between a 2G-SGSN CN and a. UMTS
25.931 V1.1.0 1 1999-06
60
Load Indication
This section shows examples of load indication reporting.
Ciphering
This example shows ciphering procedure.
25.931 V1.1.0 1 1999-06
61
Transport CH Reconfiguration
Transport CH Reconfiguration (Dedicated CH to Dedicated CH)
13. TRANSPORT CHANNEL RECONFIGURATION COMPLETE
12. TRANSPORT CHANNEL RECONFIGURATION
10. RADIO LINK RECONFIGURATION
COMMIT(Iur )
COMMIT(Iub)
9. RADIO LINK RECONFIGURATION COMMIT(Iub)
READY(Iur )
PREPARE(Iur )
READY(Iub)
PREPARE(Iub)
READY(Iub)
PREPARE(Iub)
UE Node B
Drift RNS
Node B
Serving RNS
Dr ift
RNC
Serving
RNC
CN
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
NBAP
NBAP
NBAP
NBAP
RNSAP RNSAP
NBAP NBAP
RNSAP RNSAP
NBAP NBAP
RRC RRC
RRC RRC
ALCAP Iur
BEARER SETUP
ALCAP Iur
BEARER RELEASE
25.931 V1.1.0 1 1999-06
62
Transport CH Reconfiguration (RACH/FACH to RACH/FACH)
Note : this procedure is FFS
UE Node B
Serving RNS
Serving
RNC
CN
RRC RRC
RRC RRC
25.931 V1.1.0 1 1999-06
63
Transport CH Reconfiguration (RACH/FACH to Dedicated CH)
2. RADIO LINK SETUP
RESPONSE(Iub)
UE Node B
Serving RNS
Ser ving
RNC
CN
NBAP NBAP
NBAP NBAP
RRC RRC
RRC RRC
25.931 V1.1.0 1 1999-06
64
Transport CH Reconfiguration (Dedicated CH to RACH/FACH)
Note: this example shows the case of Transport CH Reconfiguration (Dedicated CH to RACH/FACH) combined with a
SRNS relocation
RESPONSE(Iur )
(Iur )
RESPONSE(Iub)
UE Node B
Drift RNS
Node B
Serving RNS
Dr ift
RNC
Serving
RNC
CN
RRC RRC
RRC RRC
RNSAP RNSAP
NBAP NBAP
NBAP NBAP
RNSAP RNSAP
(FFS)
ALCAP Iur
BEARER RELEASE
25.931 V1.1.0 1 1999-06
65
Notification
NOTE: The whole procedure is FFS.
1. NOTIFICATION (FFS)
3. NOTIFICATION
2. NOTIFICATION (Iub) (FFS)
UE Node B
Serving RNS
Serving
RNC
CN
NBAP NBAP
RRC RRC
RANAP RANAP
25.931 V1.1.0 1 1999-06
66
DL Code Reconfiguration
NOTE: The whole procedure is FFS.
2. DL CODE RECONFIGURATION
REQUEST (Iur)
1. DL CODE RECONFIGURATION
REQUEST(Iub)
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RNSAP RNSAP
NBAP NBAP
25.931 V1.1.0 1 1999-06
67
Direct Transfer
Uplink Direct Transfer
2. DIRECT TRANSFER
1. DIRECT TRANSFER
UE Node B
Serving RNS
Serving
RNC
CN
RRC RRC
RANAP RANAP
25.931 V1.1.0 1 1999-06
68
Downlink Direct Transfer
2. DIRECT TRANSFER
1. DIRECT TRANSFER
UE Node B
Serving RNS
Serving
RNC
CN
RRC
RANAP RANAP
RRC
25.931 V1.1.0 1 1999-06
69
Downlink Power Control
3. POWER CONTROL(Iub)
2. POWER CONTROL
(Iur)
1. POWER CONTROL(Iub)
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
NBAP NBAP
RNSAP RNSAP
NBAP NBAP
25.931 V1.1.0 1 1999-06
70
Document history
Date Version Comment
2 June 1999 1.1.0 Same as version 1.0.2, revisions accepted
30 May 1999 1.0.2 This version presents some editorial updated and some proposals to
cope with the decision taken at the last meeting (kawasaki, April 99).
Major changes are derscribed in the following list:
Updated figure for the protocol stack section 6.1
Updated message list for section 6.2
Modified figure and text in sections in order to allign it to the
RANAP unified HO and SRNS relocation procedures agreeded at
the Kawasaki meeting (april 99)
9.13.1.3 Hard HO with switching in the CN
9.14.3 SRNS Relocation
9.15.1 UTRAN => GSM/BSS HO
9.15.2 GSM/BSS => UTRAN HO
25.931 V1.1.0 1 1999-06
71
24 May 1999 1.0.1 This version includes the modification agreed at the TSG-RAN WG3
#3 in Kawasaki (Apr 99).
The following three changes are not introduced, they will be presnted
as editor proposals:
A new section for Q.AAL example into a new section 6.4.
A new figure in the protocol stack section 6.1
The name of the messages for HO should be modified in order to
cope with the unified procedures decided at the last eeting
Major introduced changes are listed below (number referred to old
numbering)
Q.aal2 flows were removed and the ALCAP boxes were put again in
scenario 9.4.1
Section 6.6 and 6.7 were removed due to the fact that these sections
are only related to WG2 issues.
ommon channel and CCH were replaced with common transport
channel and FACH/RACH
The term SRNC Relocation was replaced SRNS Relocation
Section 9.3.2 and 9.11.2 were replaced by a reference to the proper
WG2 documents, due to the fact that these sections are only related
to WG2 issues (Correct reference to be filled)
The section 9.13 was restructured and renamed (bawckward HO)
and merged with 9.14 (cell update is forward HO).
Section 9.14.2 was replaced with the content od Tdoc 355 from
Nokia, updated accordly with the modification decided at the
meeting
Section 9.17 was restructure and new section for HO between
UMTS and GPRS were introduced
Section 9.25 was removed (inband mechnism, example not needed)
A temporary annex was added to summarize the status of the
reccomandation.
April 99 1.0.0 Agreeded at TSG RAN April 99 and promoted to version 1.0.0 (the
same as 0.1.0
April 16
th
1999 0.1.0 Same as version 0.0.5, revision marks accepted
This version was sent to TSG RAN April 1999 meeting for approval
25.931 V1.1.0 1 1999-06
72
April 16
th
1999 0.0.5 This version contains mainly editorial enhancements. Major changes
are listed below
Section 6.1 SRNC Relocation Commit message was added
Section 9.17.2 Release Complete message was added
Section 9.2.1 Link Establishment and.Link Establishment
Acknowledge messages were added
April 6
tth
1999 0.0.4 This version contains mainly editorial enhancements. Major changes
are listed below:
section 7.1 and 7.2 were promoted to section 8 and 9 in order to
limit the deep in the subsection numbering; subsection were
promoted accordingly
Figure numberig was incomplete and also produces unclear
revision marks due to a bug of word; Only the numbering of the
first figures was left
Styles were aligned to make the document consistant
Hard Handover Proceeding 2 message was removed for
alignement with RNSAP procedures (section 9.17.4)
April 6
tth
1999 0.0.3 This version includes also the modification agreed at the TSG-RAN
WG3 march 1999 meeting. Major changes summary follows:
section 7.2.13.2.1 (Inter-RNS hard HO with switching in the CN-
single CN) was removed
section 7.2.14.2 (Inter-RNS cell Update via Iur) was added
section 7.2.15.2.1 (Inter-RNS URA Update via Iur) was added
section 7.2.13.2 (Inter-RNS Hard HO via Iur) was re-integrated
and filled with new contributions
March 1
st
1999 0.0.2 The correct first pages common for 3GPP were introduced (first page,
copyright, etc)
Revision marks are referred to the modification introduced to the
document AFTER the TSG-RAN WG3 first meeting Bon February
99, based on the minor comments received in line with the decision of
the previous meeting, (i.e. comments to the first draft merged version
are identified)
In this version the revision mark referred to version 0.0.0 were
accepted
25.931 V1.1.0 1 1999-06
73
February 15
th
1999 0.0.1 This version includes also the modification agreed at the TSG-RAN
WG3 first meeting based on new contributions
Notes
The general information dealing with references and copyrights are
not updated to the 3GPP ones (To be introduced when available)
The graphical look of the parts included from the TTC/ARIB
document still to be aligned by the editor to the rest of the document
(the content is supposed to be aligned)
February 4
th
1999 0.0.0
First draft version based on merge of the corresponding ETSI and
TTC/ARIB document as agreed at the TSG-RAN WG3 first meeting
Bon February 99. (Revision marks are referred to the ETSI one).
This version includes also the modification agreed at the TSG-RAN WG3
first meeting based on new contributions (except document 54 and 55,
from which is expected an electronic version with the agreed
modifications from the authors)
Notes
The general information dealing with references and copyrights are
not updated to the 3GPP ones (To be introduced when available)
Alignment of names of messages respect to the Iur and Iub
ETSI/ARIB merged interfaces is not complete. (To be
introduced/checked later when the correspondent documents will be
available in order to limit misalignment)
The graphical look of the parts included from the TTC/ARIB
document still to be aligned by the editor to the rest of the document
(the content is supposed to be aligned)
Reporter for I3.01 is:
Enrico Scarrone
CSELT
Tel. : +39 011 228 7084
Fax : +39 011 228 5520
Email : Enrico.Scarrone@cselt.it
This document is written in Microsoft Word version 97.
25.931 V1.1.0 1 1999-06
74
ANNEX: status of the document
1. Intellectual Property Rights TO BE FILLED (BY STAFF?)
2. Foreword TO BE FILLED (BY STAFF?)
3. Scope TO BE UPDATED? (PRESENTLY IT IS A VERY SHORT
DESCRIPTION)
4. References TO BE UPDATED
5. Definitions, abbreviations and notation TO BE UPDATED
5.3 Notation for the signalling procedures COMPLETED
6. UTRAN AND UE PROTOCOL ARC TO BE UPDATED
7. UTRAN Signaling Procedures TO BE UPDATED (iT IS ONLY A FOREWORD FOR THE NEXT
TWO CHAPTER)
8. Procedures not related to a specific UE (global procedures)
8.1 System Information Broadcasting STABLE,MISSING TEXT (CONTRIBUTION INVITED)
8.2 Cell Broadcast NOT STABLE (CONTRIBUTION INVITED)
9. Procedures related to a specific UE
9.1 Paging
9.1.1 Paging for a UE in RRC Idle ModeSTABLE
9.1.2 Paging for a UE in RRC Conn STABLE
9.2 NAS Signalling Connection Establishment
9.2.1 UE Initiated Signalling Connection Est.. STABLE
9.2.2 CN Initiated Signalling Connection Est.. NOT STABLE,MISSING FLOW AND TEXT
(CONTRIBUTION INVITED)
9.3 RRC Connection Establishment
9.3.1 DCH Establishment STABLE
9.3.2 RACH/FACH Establishment STABLE (MISSING REFERENCE)
9.4 RRC Connection Release
9.4.1 DCH Release STABLE,MISSING TEXT (CONTRIBUTION INVITED)
9.4.2 Common Transport Channel Release STABLE,MISSING TEXT (CONTRIBUTION INVITED)
9.5 RRC Connection Re-establishment
9.5.1 DCH Re-establishment NOT STABLE (CONTRIBUTION INVITED)
9.5.2 RACH/FACH Re-establishment NOT STABLE (CONTRIBUTION INVITED)
9.6 Radio Access Bearer Establishment
9.6.1 DCH - DCH Establishment Sync.. STABLE
9.6.2 DCH - DCH Establishment Unsyn.. STABLE
9.6.3 RACH/FACH - DCH Establishment STABLE,MISSING TEXT (CONTRIBUTION INVITED)
25.931 V1.1.0 1 1999-06
75
9.6.4 RACH/FACH - RACH/FACH Est.. STABLE,MISSING TEXT (CONTRIBUTION INVITED)
9.7 Radio Access Bearer Release
9.7.1 DCH - DCH Release - Synchronized SABLE
9.7.2 DCH - DCH Release - Unsynchronized STABLE
9.7.3 DCH - RACH/FACH Release NOT STABLE (CONTRIBUTION INVITED)
9.7.4 RACH/FACH - RACH/FACH ReleaseSTABLE,MISSING TEXT (CONTRIBUTION INVITED)
9.8 Radio Access Bearer Re-establishment NOT STABLE (CONTRIBUTION INVITED)
9.9 Radio Access Bearer Modification NOT STABLE (CONTRIBUTION INVITED)
9.10 Physical Channel Reconfiguration NOT STABLE (CONTRIBUTION INVITED)
9.11 Channel Type Switching
9.11.1 RACH/PCH to RACH/FACH STABLE, MISSING TEXT (CONTRIBUTION INVITED)
9.11.2 RACH/FACH to RACH/PCH STABLE (MISSING REFERENCE)
9.11.3 RACH/FACH to DCH STABLE, MISSING TEXT (CONTRIBUTION INVITED)
9.11.4 DCH to RACH/FACH NOT STABLE(CONTRIBUTION INVITED)
9.12 Soft Handover STABLE
9.13 Hard Handover
9.13.1 Backward Handover
9.13.1.1 Intra Node B Hard Handover STABLE, MISSING TEXT (CONTRIBUTION INVITED)
9.13.1.2 Hard Handover via .. NOT STABLE(CONTRIBUTION INVITED)
9.13.1.3 Hard Handover with switc.. NOT STABLE(CONTRIBUTION INVITED)
9.13.2 Forward Handover NOT STABLE(CONTRIBUTION INVITED)
9.15 HO between UTRAN and GSM/BSS
9.15.1 UTRAN GSM/BSS STABLE
9.15.2 GSM/BSS UTRAN STABLE
9.15.3 UTRAN GPRS NOT STABLE(CONTRIBUTION INVITED)
9.15.4 UTRAN GSM/BSS NOT STABLE(CONTRIBUTION INVITED)
9.16 Load Indication NOT STABLE(CONTRIBUTION INVITED)
9.17 Ciphering NOT STABLE(CONTRIBUTION INVITED)
9.18 Transport CH Reconfiguration
9.18.1 Transport CH Reconfiguration.. STABLE, MISSING TEXT (CONTRIBUTION INVITED)
9.18.2 Transport CH Reconfiguration.. NOT STABLE (CONTRIBUTION INVITED)
9.18.3 Transport CH Reconfiguration.. STABLE, MISSING TEXT (CONTRIBUTION INVITED)
9.18.4 Transport CH Reconfiguratio.. NOT STABLE (CONTRIBUTION INVITED)
9.19 Notification NOT STABLE (CONTRIBUTION INVITED)
25.931 V1.1.0 1 1999-06
76
9.20 DL Code Reconfiguration NOT STABLE (CONTRIBUTION INVITED)
9.21 Direct Transfer STABLE, MISSING TEXT (CONTRIBUTION INVITED)
9.22 Downlink Power Control STABLE, MISSING TEXT (CONTRIBUTION INVITED)

UMTS Signalling PDF

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

UMTS Signalling PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

TSG-RAN Working Group 3 RP-99348

RAN meeting #4 - Miami

All rights reserved.

Anda mungkin juga menyukai