Download - ETSI TR 125 931 V3.7.1 (2006-06)
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
1/82
ETSI TR 125 931 V3.7.1 (2006-06)Technical Report
Universal Mobile Telecommunications System (UMTS);UTRAN functions, examples on signalling procedures
(3GPP TR 25.931 version 3.7.1 Release 1999)
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
2/82
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
3/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)23GPP TR 25.931 version 3.7.1 Release 1999
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI inrespect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identitiesorGSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp .
http://webapp.etsi.org/IPR/home.asphttp://webapp.etsi.org/IPR/home.asphttp://webapp.etsi.org/key/queryform.asphttp://webapp.etsi.org/key/queryform.asphttp://webapp.etsi.org/IPR/home.asp -
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
4/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)33GPP TR 25.931 version 3.7.1 Release 1999
Contents
Intellectual Property Rights................................................................................................................................2
Foreword.............................................................................................................................................................2Foreword.............................................................................................................................................................5
1 Scope ........................................................................................................................................................6
2 References ................................................................................................................................................6
3 Definitions, abbreviations and notation....................................................................................................63.1 Definitions..........................................................................................................................................................63.2 Abbreviations ................................................................ ........................................................ .............................73.3 Notation for the signalling procedures ................................................... ............................................................9
4 UTRAN and UE protocol Architecture..................................................................................................104.1 Protocol Architecture ........................................................... ......................................................... ...................104.2 RANAP Procedures & Messages ..................................................... ....................................................... .........104.3 SABP Procedures & Messages...................................................... ........................................................... ........114.4 RNSAP Procedures & Messages..................................... ........................................................... ......................114.5 NBAP Procedures & Messages........................................................... .................................................... .........124.6 ALCAP.............................................................................................................................................................144.6.1 Q2630.1 (Q.AAL 2)........ .................................................... ...................................................... ..................144.7 RRC Procedures & Messages............................................................ ...................................................... .........144.8 BMC Procedures & Messages....................................... ....................................................... ............................154.9 DCH Frame Protocol Messages ............................................................... ........................................................164.10 DSCH Frame Protocol Messages ........................................................ .............................................................164.11 USCH Frame Protocol Messages ........................................................ .............................................................16
5 UTRAN Signalling Procedures..............................................................................................................16
6 Procedures not related to a specific UE (global procedures)..................................................................176.1 System Information Broadcasting ................................................................ ....................................................176.2 Service Area Broadcast ....................................................... .......................................................... ...................17
7 Procedures related to a specific UE........................................................................................................187.1 Paging...............................................................................................................................................................187.1.1 Paging for a UE in RRC Idle Mode and RRC connected mode (CELL_PCH and URA_PCH states).......187.1.2 Paging for a UE in RRC Connected Mode (CELL_DCH and CELL_FACH states) .................................197.2 NAS Signalling Connection Establishment........................... .................................................................. .........207.3 RRC Connection Establishment ............................................................. ..........................................................207.3.1 DCH Establishment ........................................................ .......................................................... ..................207.3.2 RACH/FACH Establishment...................................................... ....................................................... .........227.3.3 DCH Establishment with Pre-emption ............................................................... ..................................................... .227.4 RRC Connection Release ........................................................... ............................................................ ..........247.4.1 DCH Release .......................................................... ......................................................... ...........................247.4.2 Common Transport Channel Release ............................................................... ..........................................257.5 RRC Connection Re-establishment......................................................... ........................................................ .257.5.1 DCH Re-establishment ....................................................... ...................................................... ..................257.5.1.1 RRC connection Re-establishment (Anchor approach) DCH Re-establishment................................257.5.1.2 RRC Connection Re-establishment with SRNC Relocation - DCH Re-establishment................ .........277.6 Radio Access Bearer Establishment..................................................... ............................................................287.6.1 DCH - DCH Establishment - Synchronised................................................... .............................................287.6.2 DCH - DCH Establishment - Unsynchronised .............................................................................. .............307.6.3 RACH/FACH - DCH Establishment .............................................................. ............................................327.6.4 RACH/FACH - RACH/FACH Establishment.......................................................... ..................................337.7 Radio Access Bearer Release ..................................................... ............................................................. .........347.7.1 DCH - DCH Release - Synchronised.... ...................................................................... ................................347.7.2 DCH - DCH Release - Unsynchronised............................................................ ..........................................367.7.4 RACH/FACH - RACH/FACH Release .......................................................... ............................................37
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
5/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)43GPP TR 25.931 version 3.7.1 Release 1999
7.8 Radio Access Bearer Modification.......................... ........................................................... ..............................387.8.1 DCCH on DCH - Synchronised..................................................... .................................................... .........387.8.2 DCCH on RACH/FACH ..................................................... ...................................................... .................397.9 Physical Channel Reconfiguration ....................................................... ............................................................407.9.1 Physical Channel Reconfiguration (DCH)............................ ............................................................. .........407.9.2 Physical Channel Reconfiguration (CRNC Controlled) ....................................................... ......................42
7.10 Soft Handover (FDD)............................................................ ........................................................ ...................427.10.1 Radio Link Addition (Branch Addition)....................................................... ..............................................437.10.2 Radio link Deletion (Branch Deletion) ............................................................... ........................................447.10.3 Radio link Addition & Deletion (Branch Addition & Deletion - simultaneously) .....................................457.10.4 DSCH Mobility Procedure in Soft Handover (Moving DSCH within the Active Set) ...............................467.11 Hard Handover ................................................... ........................................................ ......................................487.11.1 Backward Hard Handover .................................................... .................................................... ..................487.11.1.1 Hard Handover via Iur (DCH State)........................................... .......................................................... .487.11.1.2 Hard Handover with switching in the CN (UE connected to two CN nodes, DCH state).....................527.11.2 Forward Hard Handover ................................................. .......................................................... ..................547.11.2.1 Cell Update with SRNS relocation........................................................ ................................................557.11.2.2 Cell Update via Iur without SRNS relocation ............................................................. ..........................557.11.2.3 Cell Update via Iur without SRNS relocation (with C-RNTI reallocation) ..........................................57
7.11.2.4 Cell Update via Iur with USCH/DSCH, without SRNS relocation....... ................................................577.12 URA Update...................................................... ........................................................ .......................................597.12.1 Inter-RNS URA Update with SRNS Relocation................................................ .........................................597.12.2 Inter-RNS URA Update via Iur without SRNS relocation .................................................... .....................607.12.3 SRNS Relocation (UE connected to two CN nodes) ...................................................... ............................627.13 HO & Cell Reselection between UTRAN and GSM/BSS ................................................................... ............637.13.1 UTRAN
GSM/BSS................................................................................................................................64 7.13.1.1 UTRAN
GSM/BSS ........................................................ ............................................................... ...647.13.1.2 Service Based Intersystem Handover.............. ........................................................ ..............................657.13.1.3 Directed Retry ........................................................... ......................................................... ...................667.13.2 GSM/BSS
UTRAN................................................................................................................................67 7.13.3 GPRS
UMTS Cell Reselection ....................................................................... .......................................687.13.4 UMTS
GPRS Cell Reselection, UE Initiated.........................................................................................687.13.5 UMTS GPRS Cell Reselection, Network Initiated ...................................................................... ..........697.14 Transport Channel Reconfiguration(DCH to DCH)................................................................ .........................697.14.1 Synchronised Transport Channel Reconfiguration ..................................................... ................................697.14.2 Unsynchronised Transport Channel Reconfiguration................................................. ................................717.15 Direct Transfer ........................................................... .......................................................... ............................727.15.1 Uplink Direct Transfer........ ................................................................. ...................................................... .727.15.2 Downlink Direct Transfer ........................................................... ....................................................... .........737.16 Downlink Power Control [FDD] ........................................................ ..................................................... .........737.17 USCH/DSCH Configuration and Capacity Allocation [TDD]............................................................ .............747.18 Channel and Mobile State Switching on Iur............................................................. ........................................767.18.1 General Description .......................................................... ....................................................... ...................767.18.2 Switching from Cell_FACH to Cell_DCH State .......................................................... ..............................767.18.3 Switching from Cell_DCH to Cell_FACH State ........................................................ ................................77
Annex A (informative): Change History ..............................................................................................80
History ..............................................................................................................................................................81
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
6/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)53GPP TR 25.931 version 3.7.1 Release 1999
Foreword
This Technical Report (TR) has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formalTSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
7/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)63GPP TR 25.931 version 3.7.1 Release 1999
1 Scope
The present 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.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (includinga GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] TR 25.990: "Vocabulary".
[2] TS 25.401: "UTRAN Overall Description".
[3] TS 25.413: "UTRAN Iu Interface RANAP Signalling".
[4] TS 25.423: "UTRAN Iur Interface RNSAP Signalling".
[5] TS 25.433: "UTRAN Iub Interface NBAP Signalling".
[6] TR 25.832: "Manifestations of Handover and SRNS Relocation".
[7] TS 25.301: "Radio Interface Protocol Architecture".
[8] TS 25.331: "RRC Protocol Specification".
[9] TS 25.419: "UTRAN Iu Interface: Service Area Broadcast Protocol SABP".
[10] TS 25.324: "Radio Interface for Broadcast/Multicast Services".
[11] TR 25.925: "Radio Interface for Broadcast/Multicast Services".
[12] TS 23.041: "Technical realisation of Cell Broadcast Service (CBS)".
[13] TS 25.425: "UTRAN Iur Interface User Plane Protocols for Common Transport Channel Data
Streams".
[14] TS 25.435: "UTRAN Iub Interface User Plane Protocols for Common Transport Channel Data
Streams".
[15] TS 25.427: "UTRAN Iub/Iur Interface User Plane Protocol for DCH Data Streams".
3 Definitions, abbreviations and notation
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1], [2] and [4] apply.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
8/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)73GPP TR 25.931 version 3.7.1 Release 1999
3.2 Abbreviations
For the purposes of the present document the following abbreviations apply:
NOTE: More extensive abbreviations on UMTS are provided in [1].
AAL2 ATM Adaptation Layer type 2ACK Acknowledgement
AICH Acquisition Indicator Channel
ALCAP Access Link Control Application Part
AM Acknowledged Mode
AS Access StratumATM Asynchronous Transfer Mode
BCCH Broadcast Control Channel
BCFE Broadcast Control Functional Entity
BER Bit Error Rate
BLER Block Error Rate
BMC Broadcast/Multicast Control
BSS Base Station Sub-system
BSSMAP Base Station System Management Application PartCCCH Common Control Channel
CCPCH Common Control Physical Channel
CFN Connection Frame Number
CM Connection Management
CN Core Network
CPCH Common Packet Channel
CPICH Common Pilot Channel
CRNC Controlling RNC
C-RNTI Cell RNTI
CS Circuit Switched
DCA Dynamic Channel Allocation
DCCH Dedicated Control Channel
DCFE Dedicated Control Functional EntityDCH Dedicated Channel
DC-SAP Dedicated Control SAP
DL Downlink
DPCCH Dedicated Physical Control Channel
DPCH Dedicated Physical Channel
DRAC Dynamic Resource Allocation Control
DRNC Drift RNC
DRNS Drift RNS
DRX Discontinuous Reception
DSCH Downlink Shared Channel
DTCH Dedicated Traffic Channel
EP Elementary Procedure
FACH Forward Access ChannelFAUSCH Fast Uplink Signalling Channel
FDD Frequency Division Duplex
FFS For Further Study
FN Frame Number
FP Frame Protocol
ID Identifier
IE Information Element
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
IP Internet Protocol
ISCP Interference on Signal Code PowerL1 Layer 1
L2 Layer 2L3 Layer 3
LAI Location Area Identity
MAC Medium Access Control
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
9/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)83GPP TR 25.931 version 3.7.1 Release 1999
MCC Mobile Country Code
MM Mobility Management
MNC Mobile Network Code
MS Mobile Station
MSC Mobile services Switching Center
NAS Non Access Stratum
NBAP Node B Application ProtocolNt-SAP Notification SAP
NW Network
O Optional
ODMA Opportunity Driven Multiple AccessPCCH Paging Control Channel
PCH Paging Channel
PDCP Packet Data Convergence Protocol
PDSCH Physical Downlink Shared Channel
PDU Protocol Data Unit
PLMN Public Land Mobile NetworkPNFE Paging and Notification Control Functional Entity
PRACH Physical Random Access Channel
PS Packet SwitchedPSCH Physical Synchronisation Channel
P-TMSI Packet Temporary Mobile Subscriber Identity
PUSCH Physical Uplink Shared ChannelQoS Quality of Service
RAB Radio Access Bearer
RACH Random Access Channel
RAI Routing Area Identity
RANAP Radio Access Network Application Part
RB Radio BearerRFE Routing Functional Entity
RL Radio Link
RLC Radio Link Control
RNC Radio Network ControllerRNS Radio Network SubsystemRNSAP Radio Network Subsystem Application Part
RNTI Radio Network Temporary Identifier
RRC Radio Resource Control
RSCP Received Signal Code Power
RSSI Received Signal Strength Indicator
SAI Service Area IdentifierSAP Service Access Point
SCCP Signalling Connection Control Part
SCFE Shared Control Function Entity
SF Spreading Factor
SFN System Frame Number
SGSN Serving GPRS Support NodeSHCCH Shared Control Channel
SIR Signal to Interference Ratio
SRNC Serving RNC
SRNS Serving RNS
S-RNTI SRNC - RNTI
SSDT Site Selection Diversity TransmissionTDD Time Division Duplex
TEID Tunnel Endpoint Identifier
TF Transport Format
TFCI Transport Format Combination Indicator
TFCS Transport Format Combination Set
TFS Transport Format Set
TME Transfer Mode EntityTMSI Temporary Mobile Subscriber Identity
Tr Transparent
Tx Transmission
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
10/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)93GPP TR 25.931 version 3.7.1 Release 1999
UARFCN UMTS Absolute Radio Frequency Channel Number
UE User Equipment
UL Uplink
UM Unacknowledged Mode
UMTS Universal Mobile Telecommunication System
UNACK Unacknowledgement
URA UTRAN Registration AreaU-RNTI UTRAN-RNTI
USCH Uplink Shared Channel
UTRAN UMTS Terrestrial Radio Access Network
3.3 Notation 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:
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 continuous 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 protocolsmay be indicated before the message name as shown in figure 1
UE Node BD rif t R NS
Node BServing RNS
RN CDr ift
RN CServing
CN
NBAP
M AC
NBAP
RANAP RANA P
RNSAP RNSA P
M AC1. R A CH : Message
RR CRR C2. CCC H : Message
3. M essage
6. Message
5. Message
[Parameters]
[Parameters]
[Parameters]
[Parameters]
[Parameters]
Action description
NBAPNBAP4. Message
[Parameters]
A LCAP Iub Bearer Setup/Release ALCAP Iur Bearer Setup
Figure 1: Example of signalling procedure notation
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
11/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)103GPP TR 25.931 version 3.7.1 Release 1999
4 UTRAN and UE protocol Architecture
4.1 Protocol Architecture
For a detailed description of the Protocol Architecture and the Radio Protocol Architecture for the UTRAN and the UErefer to [2] and [7] respectively.
4.2 RANAP Procedures & Messages
For a detailed description of RANAP procedures and messages refer to [3]. Only Messages mentioned in the present
document are shown. For each message is also given the list of example procedures where the message is used, as
provided by this document.
Table 1
Message Name UTRAN Procedure Direction
Direct Transfer Uplink Direct TransferDownlink Direct Transfer
RNC
CNCN RNC
Initial UE Message NAS Signalling Connection Establishment RNC CN
Iu Release Command RRC Connection ReleaseHard HO with switching in the CNSRNS Relocation
UTRAN GSM/BSS handover
CN
RNC
CN RNC
CN
RNC
CN
RNC
Iu Release Complete RRC Connection ReleaseHard HO with switching in the CNSRNS Relocation
UTRAN GSM/BSS handover
RNC
CN
RNC CN
RNC CN
RNC
CN
Paging Paging for a UE in RRC Idle ModePaging for a UE in RRC Connected Mode
CN
RNC
CN
RNC
Radio Access Bearer AssignmentRequest Radio Access Bearer EstablishmentRadio Access Bearer ReleaseRadio Access Bearer Modification
CN
RNCCN RNC
CN RNC
Radio Access Bearer AssignmentResponse
Radio Access Bearer EstablishmentRadio Access Bearer ReleaseRadio Access Bearer Modification
RNC CN
RNC CN
RNC
CN
Relocation Command Hard HO with switching in the CNSRNS Relocation
UTRAN GSM/BSS handover
CN
RNC
CN
RNC
CN RNC
Relocation Complete Hard HO with switching in the CNSRNS Relocation
GSM/BSS handover
UTRAN
RNC CN
RNC CN
RNC
CN
Relocation Detect Hard HO with switching in the CNSRNS Relocation
GSM/BSS handover UTRAN
RNC
CN
RNC
CN
RNC CN
Relocation Failure SRNS Relocation RNC CN
Relocation Request Hard HO with switching in the CNSRNS RelocationGSM/BSS handover
UTRAN
CN
RNC
CN RNC
CN
RNC
Relocation Request Acknowledge Hard HO with switching in the CNSRNS Relocation
GSM/BSS handover UTRAN
RNC CN
RNC
CN
RNC CN
Relocation Required Hard HO with switching in the CNSRNS Relocation
UTRAN
GSM/BSS handover
RNC
CN
RNC CN
RNC
CN
RAB Release Request RRC Connection Establishment RNC CN
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
12/82
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
13/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)123GPP TR 25.931 version 3.7.1 Release 1999
Table 3
Message Name UTRAN Procedure Direction
Common Transport ChannelResources Release
Cell Update SRNC DRNC
Common Transport ChannelResources Initialisation Request
Cell Update SRNC
DRNC
Common Transport ChannelResources InitialisationResponse
Cell Update DRNC SRNC
DL Power Control Request Downlink Power Control SRNC
DRNC
Downlink Signalling TransferRequest
RRC Connection Re-establishmentURA Update
SRNC DRNC
SRNC
DRNC
Radio Link Deletion Request RRC Connection Re-establishmentSoft HandoverHard Handover
SRNC DRNC
SRNC
DRNC
SRNC DRNC
Radio Link Deletion Response RRC Connection Re-establishmentSoft HandoverHard Handover
DRNC
SRNC
DRNC SRNC
DRNC SRNCRadio Link Failure Indication Hard Handover DRNC
SRNC
Radio Link ReconfigurationRequest
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel Reconfiguration
SRNC
DRNCSRNC
DRNC
SRNC DRNC
SRNC
DRNC
Radio Link ReconfigurationCommit
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel ReconfigurationRadio Access Bearer Modification
SRNC DRNC
SRNC
DRNC
SRNC
DRNC
SRNC DRNC
SRNC
DRNC
Radio Link ReconfigurationPrepare
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel ReconfigurationRadio Access Bearer Modification
SRNC DRNC
SRNC
DRNC
SRNC
DRNC
SRNC DRNC
SRNC DRNCRadio Link ReconfigurationReady
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel ReconfigurationRadio Access Bearer Modification
DRNC SRNC
DRNC SRNC
DRNC
SRNC
DRNC SRNC
DRNC SRNCRadio Link ReconfigurationResponse
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel Reconfiguration
DRNC SRNC
DRNC SRNC
DRNC
SRNC
DRNC SRNC
Radio Link Restore Indication Soft HandoverHard HandoverChannel and Mobile State Switching on Iur
DRNC
SRNC
DRNC SRNC
DRNC SRNC
Radio Link Setup Request RRC Connection Re-establishment
Hard HandoverUSCH/DSCH Configuration and Capacity Allocation [TDD]
SRNC
DRNC
SRNC DRNCSRNC
DRNC
Radio Link Setup Response RRC Connection Re-establishmentHard HandoverUSCH/DSCH Configuration and Capacity Allocation [TDD]
DRNC SRNC
DRNC
SRNC
DRNC
SRNC
Relocation Commit SRNS Relocation URA Update Source RNC
Target RNC
Uplink Signalling TransferIndication
RRC Connection Re-establishmentURA Update
DRNC SRNC
DRNC SRNC
4.5 NBAP Procedures & Messages
For a detailed description of NBAP procedures and messages refer to [5]. Only Messages mentioned in the presentdocument are shown. For each message is also given the list of example procedures where the message is used, as
provided by this document.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
14/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)133GPP TR 25.931 version 3.7.1 Release 1999
Table 4
Message Name UTRAN Procedure Direction
DL Power Control Request Downlink Power Control RNC Node B
Physical Shared ChannelReconfiguration Request
USCH/DSCH Configuration and Capacity Allocation [TDD] RNC
Node B
Physical Shared Channel
Reconfiguration Response
USCH/DSCH Configuration and Capacity Allocation [TDD] Node B
RNC
Radio Link Deletion RRC Connection ReleaseRRC Connection Re-establishmentHard HandoverSoft Handover
RNC
Node B
RNC
Node B
RNC Node B
RNC
Node B
Radio Link Deletion Response RRC Connection ReleaseRRC Connection Re-establishmentHard HandoverSoft Handover
Node B RNC
Node B
RNC
Node B
RNC
Node B RNC
Radio Link Failure Indication Hard Handover Node B
RNC
Radio Link ReconfigurationCommit
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel Reconfiguration
Transport Channel ReconfigurationRadio Access Bearer Modification
RNC
Node B
RNC
Node B
RNC Node B
RNC
Node BRNC
Node B
Radio Link ReconfigurationPrepare
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel ReconfigurationRadio Access Bearer Modification
RNC Node B
RNC
Node B
RNC Node B
RNC Node B
RNC
Node B
Radio Link ReconfigurationReady
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel ReconfigurationRadio Access Bearer Modification
Node B RNCNode B
RNC
Node B
RNC
Node B RNC
Node B
RNC
Radio Link ReconfigurationRequest
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel Reconfiguration
RNC Node B
RNC
Node BRNC
Node B
RNC Node B
Radio Link ReconfigurationResponse
Radio Access Bearer EstablishmentRadio Access Bearer ReleasePhysical Channel ReconfigurationTransport Channel Reconfiguration
Node B
RNC
Node B RNC
Node B
RNC
Node B
RNC
Radio Link Restore Indication RRC Connection EstablishmentRRC Connection Re-establishmentSoft HandoverHard HandoverChannel and Mobile State Switching on Iur
Node B
RNC
Node B
RNC
Node B RNC
Node B RNC
Node B
RNC
Radio Link Setup Request RRC Connection EstablishmentRRC Connection Re-establishment
Hard HandoverSoft HandoverUSCH/DSCH Configuration and Capacity Allocation [TDD]
RNC Node B
RNC
Node B
RNC Node BRNC Node B
RNC
Node B
Radio Link Setup Response RRC Connection EstablishmentRRC Connection Re-establishmentHard HandoverSoft HandoverUSCH/DSCH Configuration and Capacity Allocation [TDD]
Node B RNC
Node B
RNC
Node B
RNC
Node B RNC
Node B
RNC
System Information UpdateRequest
System Information BroadcastingService Area Broadcast
RNC Node B
RNC
Node B
System Information UpdateResponse
System Information BroadcastingService Area Broadcast
Node B RNC
Node B
RNC
Radio Link Preemption Required
Indication
RRC Connection Establishment Node B RNC
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
15/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)143GPP TR 25.931 version 3.7.1 Release 1999
4.6 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 protocols 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.
4.6.1 Q2630.1 (Q.AAL 2)
The following figure is showing an example of use of Q.2630.1 in the UTRAN context, for the different interfaces.
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
11.
Establish RequestQ.aal2 Q.aal2
Q.aal2Q.aal2 Establish Confirm
Establish Request Q.aal2Q.aal2
Q.aal2 Q.aal2Establish Confirm
Establish Request Q.aal2Q.aal2
Q.aal2 Q.aal2Establish Confirm
Establish Request Q.aal2Q.aal2
Q.aal2 Q.aal2Establish Confirm
Figure 2: Example on Q.2630.1
4.7 RRC Procedures & Messages
For a detailed description of RRC procedures and messages refer to [8]. Only Messages mentioned in the present
document are shown. For each message is also given the list of example procedures where the message is used, as
provided by this document.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
16/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)153GPP TR 25.931 version 3.7.1 Release 1999
Table 5
Message Name UTRAN Procedure Direction
Active Set Update Soft Handover RNC UE
Active Set Update Complete Soft Handover UE
RNC
Cell Update RRC Connection Re-establishmentCell Update
UE RNC
UE
RNC
Cell Update Confirm RRC Connection Re-establishmentCell Update
RNC UE
RNC
UE
Direct Transfer NAS Signalling Conn. Establishment UE RNCDownlink Direct Transfer Downlink Direct Transfer RNC UE
Initial Direct Transfer NAS Signalling Connection Establishment UE
RNC
Measurement Control Downlink Power Control RNC UEMeasurement Report Downlink Power Control UE RNC
Paging Type 1 Paging for a UE in RRC Idle Mode and RRC connectedmode (CELL_PCH and URA_PCH states) Paging for a UEin RRC Connected Mode
RNC
UE
Paging Type 2 Paging for a UE in RRC Connected Mode (CELL_DCH andCELL_FACH states)
RNC
UE
Physical Channel Reconfiguration Physical Channel Reconfiguration
Hard Handover
RNC
UE
RNC UEPhysical Channel ReconfigurationAllocation
USCH/DSCH Configuration and Capacity Allocation [TDD] RNC
UE
Physical Channel ReconfigurationComplete
Physical Channel ReconfigurationHard Handover
UE
RNC
UE
RNC
PUSCH Capacity Request USCH/DSCH Configuration and Capacity Allocation [TDD] UE
RNC
RB Reconfiguration USCH/DSCH Configuration and Capacity Allocation [TDD] RNC UE
RB Reconfiguration Complete USCH/DSCH Configuration and Capacity Allocation [TDD] UE
RNC
RB Release Radio Access Bearer Release RNC
UE
RB Release Complete Radio Access Bearer Release UE RNC
RB Setup Radio Access Bearer Establishment RNC
UE
RB Setup Complete Radio Access Bearer Establishment UE
RNC
RRC Connection Release RRC Connection Release RNC UE
RRC Connection Release Complete RRC Connection Release UE RNCRRC Connection Request RRC Connection Establishment. UE
RNC
RRC Connection Setup RRC Connection Establishment RNC UERRC Connection Setup Complete RRC Connection Establishment UE RNC
System Information System Information Broadcasting Node B
UE
Transport Channel Reconfiguration Physical Channel Reconfiguration RNC UE
Transport Channel ReconfigurationComplete
Physical Channel Reconfiguration UE
RNC
UE Capability Information NAS Signalling Conn. Establishment. UE
RNC
Uplink Direct Transfer Uplink Direct Transfer UE
RNC
URA Update Cell Update UE RNCURA Update Confirm Cell Update RNC
UE
UTRAN Mobility Information Confirm RRC Connection Re-establishmentCell UpdateURA Update
UE
RNCUE
RNC
UE RNC
Handover from UTRAN Command UTRAN to GSM/BSS handover RNC
UE
Handover to UTRAN Complete GSM /BSS to UTRAN handover UE
RNC
Cell Change Order from UTRAN UMTS to GPRS Cell Reselection RNC UE
4.8 BMC Procedures & Messages
For a detailed description of BMC procedures and messages refer to [11] and [12]. Only Messages mentioned in the
present document are shown. For each message is also given the list of example procedures where the message is used,
as provided by this document.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
17/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)163GPP TR 25.931 version 3.7.1 Release 1999
Table 6
Message Name UTRAN Procedure Direction
CBS Message Service Area Broadcast Node B UE
4.9 DCH Frame Protocol MessagesFor a detailed description of DCH Frame protocol messages refer to [15]. Only Messages mentioned in the present
document are shown. For each message is also given the list of example procedures where the message is used, as
provided by this document.
Table 7
Message Name UTRAN Procedure Direction
Downlink Synchronisation RRC Connection EstablishmentRadio Access Bearer EstablishmentSoft Handover
SRNC
Node B
SRNC Node B
SRNC Node B
Uplink Synchronisation RRC Connection EstablishmentRadio Access Bearer Establishment
Soft Handover
Node B SRNC
Node B SRNC
Node B
SRNC
4.10 DSCH Frame Protocol Messages
For a detailed description of DSCH Frame protocol messages refer to [13]. Only Messages mentioned in the present
document are shown. For each message is also given the list of example procedures where the message is used, as
provided by this document.
Table 8
Message Name UTRAN Procedure Direction
DSCH Capacity Allocation USCH/DSCH Configuration and Capacity Allocation [TDD] DRNC
SRNC
DSCH Capacity Request USCH/DSCH Configuration and Capacity Allocation [TDD] SRNC DRNC
4.11 USCH Frame Protocol Messages
For a detailed description of DSCH Frame protocol messages refer to [14]. Only Messages mentioned in the present
document are shown. For each message is also given the list of example procedures where the message is used, asprovided by this document.
Table 9
Message Name UTRAN Procedure Direction
Dynamic PUSCH Assign USCH/DSCH Configuration and Capacity Allocation [TDD] RNC Node B
5 UTRAN Signalling 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.
The list of parameters is not be complete, but should only be seen as help for the understanding of the examples.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
18/82
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
19/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)183GPP TR 25.931 version 3.7.1 Release 1999
1.Write-replace
UE Node B RNC CN
BMCBMC
SABPSABP
4. CTCH: CBS Message
BMCBMC
5. CTCH: CBS Message
BMCBMC
SABPSABP
2. Write-replace Complete
3. CTCH: CBS Message
Figure 4: Service Area Broadcast
1. The CN asks the RNC for an information Broadcast via SABP message Write-replace.Parameters: Broadcast-Message-Content, Service-Area-List.
2. The RNC confirm the ability to broadcast the information sending Write-Replace Complete message to the CN
via SABP. (If the RNC can not Broadcast the information as requested, Write-replace Failuremessageis return to
the CN).
3./4./5. The information is broadcasted on the air interface by BMC message CBS Message. carried over CTCH
channel.Parameters: Message ID, CB Data.
Note that the Node B is transparent to this messaging because (as mentioned in [10],[11] and [12]) the BMC protocol is
terminated in RNC (see also [7]).
7 Procedures related to a specific UE
This clause presents a number of signalling procedures related to a specific UE.
7.1 Paging
This subclause presents two examples of Paging procedures for both the cases of a UE in RRC Idle Mode and RRC
Connected Mode.
7.1.1 Paging for a UE in RRC Idle Mode and RRC connected mode(CELL_PCH and URA_PCH states)
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.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
20/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)193GPP TR 25.931 version 3.7.1 Release 1999
UE Node B
1. 1
Node B
2. 1
RN C
1
RN C
2
CN
RANAPRANAP1. Paging
2. PC C H: Paging Type 1
RA NA P RAN AP1. Paging
3. PC C H: Paging Type 1
Figure 5: 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: CN Domain Indicator, Permanent NAS UE Identity, Temporary UE Identity, Paging Cause.
2. Paging of UE performed by cell1 using Paging Type 1 message.3. Paging of UE performed by cell2 using Paging Type 1 message.
The UE detects page message from RNC1 (as example) and the procedure for NAS signalling connection establishment
follows. NAS message transfer can now be performed.
This procedure described for RRC idle mode, applies also to the RRC connected mode in the case of CELL_PCH andURA_PCH states.
7.1.2 Paging for a UE in RRC Connected Mode (CELL_DCH andCELL_FACH states)
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.
The following example shows how paging is performed for a UE in RRC Connected Mode (CELL_DCH and
CELL_FACH states) when the UTRAN coordinates the paging request with the existing RRC connection using DCCH.
UE Serving
RN C
C N
RRCRRC2. D C C H : Paging Type 2
RA N A P RA N A P
1. Paging
Figure 6: Paging for a UE in RRC Connected Mode (CELL_DCH and CELL_FACH states)
1. CN initiates the paging of a UE via RANAP message Paging.
Parameters: CN Domain Indicator, Permanent NAS UE Identity, Temporary UE Identity, Paging Cause.2. SRNC sends RRC message Paging Type 2.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
21/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)203GPP TR 25.931 version 3.7.1 Release 1999
7.2 NAS Signalling Connection Establishment
This example shows establishment of a NAS Signalling Connection.
This establishment could be request by the terminal by itself (for example to initiate a service) or could be stimulated bya paging from the CN.
UE Serving
RN C
C N
1. RRC Connect ion Establ ishment
RRCRR C2. D C C H : Initial Direct Transfer
RA N A P RA N A P
3. Ini t ial UE Message
Figure 7: NAS Signalling Connection Establishment
1. RRC Connection is established (see 7.3.1 or 7.3.2).
2. UE sends RRC Initial 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).
3. SRNC initiates signalling connection to CN, and sends the RANAP message Initial UE Message.
Parameters: NAS PDU (could for a GSM based CN be e.g. CM Service Request, Location Update Request etc.),
CN domain indicator (indicating the CN domain towards which this message is sent).
The NAS signalling connection between UE and CN can now be used for NAS message transfer.
7.3 RRC Connection Establishment
The following examples show establishment of a RRC connection either in dedicated transport channel (DCH) state or
in common transport channel (RACH/FACH) state.
7.3.1 DCH Establishment
This example shows establishment of an RRC connection in dedicated transport channel (DCH) state.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
22/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)213GPP TR 25.931 version 3.7.1 Release 1999
5. Downlink Synchronisation
U E No d e B
Serving RNSServing
R N C
DCH-FPDC H-F P
Allocate RNTI
Select L1 and L2
parameters
R R CR RC1. CCCH : RRC Connection Request
N B A PN B A P3. Radio Link Setup Response
N B A PN B A P
2. Radio Link Setup Request
R RCR R C7. CCCH : RRC Connection Setup
Start RX
Start TX
4. ALCAP Iub Data Transport Bearer Setup
R RCR R C9. D CC H : RRC Connection Setup Complete
DCH-FPDC H-F P
6. Uplink Synchronisation
N B A PN B A P
8. Radio Link Restore Indication
Figure 8: RRC Connection Establishment - DCH Establishment
1. The UE initiates set-up of an RRC connection by sending RRC Connection Request message on CCCH.
Parameters: Initial UE Identity, Establishment cause.
2. The SRNC decides to use a DCH for this RRC connection, allocates U-RNTI and radio resources for the RRC
connection. When a DCH is to be set-up, NBAP message Radio Link Setup Request 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), Power control information.
3. Node B allocates resources, starts PHY reception, and responds with NBAP message Radio LinkSetup
Response.
Parameters: Signalling link termination, Transport layer addressing information (AAL2 address, AAL2 Binding
Identity) for the Iub Data Transport Bearer.
4. SRNC initiates set-up of Iub Data Transport bearer using ALCAP protocol. This request contains the AAL2
Binding Identity to bind the Iub Data Transport Bearer to the DCH. The request for set-up of Iub Data Transportbearer is acknowledged by Node B.
5./6.The Node B and SRNC establish synchronism for the Iub and Iur Data Transport Bearer by means of exchange
of the appropriate DCH Frame Protocol frames Downlink Synchronisation and Uplink Synchronisation. Then
Node B starts DL transmission.
7. Message RRC Connection Setup is sent on CCCH from SRNC to UE.
Parameters: Initial UE Identity, U-RNTI, Capability update Requirement, Transport Format Set, Transport
Format Combination Set, frequency, DL scrambling code (FDD only), Time Slots (TDD only), User Codes
(TDD only), Power control information.
8. Node B achieves uplink sync and notifies SRNC with NBAP message Radio Link Restore Indication.
9. Message RRC Connection SetupComplete is sent on DCCH from UE to SRNC.Parameters: Integrity information, ciphering information, UE radio access capability.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
23/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)223GPP TR 25.931 version 3.7.1 Release 1999
7.3.2 RACH/FACH Establishment
This example shows establishment of an RRC connection on the RACH/FACH common transport channel. Aprerequisite for this example is that the necessary Iub Data Transport bearer for the RACH/FACH is established prior to
this procedure.
U E Node B
Serving RNSServing
RN C
R RCRR C1 . CCCH : RRC Connection Request
R RCRR C2. CCCH : RRC Connection Setup
RR CRR C3. D CC H : RRC Connection Setup Complete
Figure 8b: RRC Connection Establishment RACH/FACH Establishment
1. The UE initiates set-up of an RRC connection by sending RRC Connection Request message on CCCH.
Parameters: Initial UE Identity, Establishment cause.
2. The SRNC decides to use RACH/FACH for this RRC connection and allocates both U-RNTI and C-RNTIidentifiers. Message RRC Connection Setup is sent on CCCH.
Parameters: Initial UE Identity, U-RNTI, C-RNTI, Capability update Requirement, frequency (optionally).
3. UE sends RRC Connection SetupComplete on a DCCH logical channel mapped on the RACH transport channel.
Parameters: Integrity information, ciphering information, UE radio access capability.
7.3.3 DCH Establishment with Pre-emption
This example shows the establishment of an RRC Connection in dedicated transport channel (DCH) state with pre-emption of resouces as a result of Node B Admission Control. This assumes that that the RL(s) pre-empted are the onlyRL(s) for a RAB that is released.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
24/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)233GPP TR 25.931 version 3.7.1 Release 1999
2. Radio Link Setup Request
9. RRC Connection Release Complete
8. RRC Connection Release
11. Radio Link Deletion Response
10. Radio Link Deletion Request
UE
Low PriorityNode B
Ser ving RN S
ServingRNC
CN
RRC
RRCRRC
NBAP
NBAPNBAP
NBAP
RANAP
RANAP
6. ALCAP Iu Bearer Release
5. Iu Release Command
7. Iu Release Complete
RRC
RANAP
NBAP
NBAP
RANAP
Node B admission control
threshold exceeded
3. Radio Link Preemption Requi red Indication
RNC identifies that the
RAB needs to be released
RANAP RANAP4. RAB Release Request
NBAP NBAP
12. ALCAP Iub B earer Release
13. Radio Link Setup Response
NBAP NBAP
UE
Hi Priority
RRC RRC1. CCCH: RRC Connection Request
15. Downlink Synchronisation
DCH-FP
RRCRRC17. CCCH: RRC Connection Set up
Start TX
14. ALCAP Iub Data Transport Bearer Setup
RRCRRC19.DCCH: RRC Connection Setup Comple te
16. Uplink Synchronisation
NBAPNBAP18. Radio Link Restore Indication
DCH-FP
DCH-FP
DCH-FP
Figure 8c RRC Connection Establishment - DCH Establishment with pre-emption
1. See 7.3.1 Item 1.
2. When a DCH is to be set-up, NBAP message Radio Link Setup Request is sent to the Node B.3. Node B attempts to allocate resources, but is unable to and responds with NBAP message Radio Link
Preemption Required Indication, and starts the Tpreempt timer.
Parameters: RLInformation IE.
4. The SRNC pre-empts a RL and may send a RANAP message RAB Release Request to the CN.
Cause: RAB Pre-empted
5. If the CN agrees to the release of the dedicated Channel it sends the message Iu Release Command to the
SRNC.
6. The SRNC initiates release of the Iu Data Transport bearer using ALCAP protocol.
7. The SRNC confirms the release by sending a Iu Release Complete message to the CN.
8. Message RRC Connection Release from SRNC to UE intiates the RRC connection release.
Parameters: Release Cause - Pre-emptive release
9. Message RRC Connection Release Complete from the UE to SRNC to confirm the RRC connection release.
10. The SRNC initiates the release of the link by sending Radio Link Deletion to the Node B. The Node B stops theTpreempt timer.
11. The Node B confirms the release of the link by sending the Radio Link Deletion Response to the SRNC
12. The Node B initiates release of the Iub Data Transport Bearer using ALCAP protocol.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
25/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)243GPP TR 25.931 version 3.7.1 Release 1999
13. The Node B responds to Item 2 with NBAP message Radio Link Setup Response.
14-20 See 7.3.1 Items 4-9
7.4 RRC Connection Release
The following examples show RRC connection release either of a dedicated channel (DCH) or of a common transport
channel (RACH/FACH).
7.4.1 DCH Release
This example shows RRC Connection release of a dedicated channel, in the case of macrodiversity on two nodes B, the
first one connected to the Serving RNC, the second one to the Drift RNC.
10. Radio Link Deletion Response
8. Radio Link D eletion
9. Radio Link Deletion Response
6. Radio Link Deletion
5 . RRC Connec tion Re lease Com ple te
4 . RRC Connec tion Re lease
11. Radio Link Deletion Response
7. Radio Link Deletion
UE N o de B
Dr ift RN S
Node B
S e rv in g R N S
DriftR NC
ServingR NC
C N
RR C
R RCRR C
N B A P
N B A P
R N S A P
N B A PNBAP
N B A P
R N S A P
R A N A P
R A N A P
3. ALCAP Iu Bearer Release
ALCAP Iur Beare r
Release13. ALCAP Iub Bearer Release
12. ALCAP Iub Bearer Release
1 . Iu Re lease Comm and
2. Iu Release Complete
R RC
R A N A P
N B A P
R N S A P
N B A P
NBAP
R N S A P
R A N A P
Figure 9: RRC Connection release of a dedicated channel
1. The CN initiates the release of a dedicated Channel by sending the message Iu Release Command to the SRNC.
Parameters: Cause.
2. The SRNC confirms the release by sending a Iu Release Complete message to the CN.
Parameters: Data volume Report (if data volume reporting to PS is required).
3. The SRNC initiates release of Iu Data Transport bearer using ALCAP protocol.
4. Message RRC Connection Release from SRNC to UE to initiate the RRC connection release.
Parameters: Cause.
5. Message RRC Connection Release Complete from UE to SRNC to confirm the RRC connection release.
6. The SRNC initiates the release of the link by sending the Radio Link Deletion to the Node B (SRNC).
7. The SRNC initiates the release of the link by sending the Radio Link Deletion to the Drift RNC.
8. The Drift RNC initiates the release of the link by sending the Radio Link Deletion to the Node B (Drift RNC).
9. The Node B (SRNC) confirms the release of the link by sending the Radio Link Deletion Response to the
SRNC.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
26/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)253GPP TR 25.931 version 3.7.1 Release 1999
10. The Node B (Drift RNC) confirms the release of the link by sending the Radio Link Deletion Response to the
Drift RNC.
11. The Drift RNC confirms the release of the link by sending the Radio Link Deletion Response to the SRNC.
12. The Node B (SRNC) initiates release of Iub Data Transport bearer using ALCAP protocol.
13. The Node B (Drift RNC) initiates release of Iub Data Transport bearer using ALCAP protocol.
14. The Drift RNC initiates release of Iur Data Transport bearer using ALCAP protocol.
7.4.2 Common Transport Channel Release
This example shows RRC Connection release of a common transport channel.
2. Iu Release Complete
1. Iu Release Command
5. RRC C onnect ion Release Complete
4. RRC Co nnect ion Release
U E N o de B
Dr ift RN S
No d e B
S erv in g R NS
Drif t
RN C
Serving
RN C
CN
RR C
RR C
RANAP
RANAP
3. ALCAP Iu Bearer Release
RANAP
RANAP
RR C
RR C
Figure 10: RRC Connection release of a common transport channel
1. The CN initiates the release of a dedicated Channel by sending the message Iu Release Command to the SRNC.
Parameters: Cause.
2. The SRNC confirms the release by sending a Iu Release Complete message to the CN.Parameters: Data volume Report (if data volume reporting to PS is required).
3. The SRNC initiates release of Iu Data Transport bearer using ALCAP protocol.
4. Message RRC Connection Release from SRNC to UE to initiate the RRC connection release.
Parameters: Cause.
5. Message RRC Connection Release Complete from UE to SRNC to confirm the RRC connection release.
7.5 RRC Connection Re-establishment
The following examples show re-establishment of a RRC connection on a dedicated channel (DCH) Examples of RRC
Connection Re-establishment on a common channel (RACH/FACH) are found in the "Cell Update" section of thisdocument.
7.5.1 DCH Re-establishment
7.5.1.1 RRC connection Re-establishment (Anchor approach) DCH Re-establishment
This example shows re-establishment of a RRC connection in dedicated transport channel (DCH) state.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
27/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)263GPP TR 25.931 version 3.7.1 Release 1999
16 D C CH: UTR AN M obility Information Confirm
14. Dow nlink Signalling Transfer Request
[Cell Update Confirm]
6. Radio Link Setup Response
5. Radio Link Setup Response
4. Radio Link Setup Request
3. Radio Link Setup Request
2. U plink Signalling Transfer Indication
[Cell Update] R N S A P R N S A P
RNSAP RNSAP
N B A P N B A P
N B A P N B A P
RNSAPR N S A P
R N S A P R N S A P
15. Transmission of Uu
Signalling M essage [Cell Update
Confirm]
R R C R R C
1. Reception of U u Signalling
Message [CCCH : Cel l Update]
ALCAP Iu b
Bearer Setup7 . ALCAP Iur Bearer Setup
13. ALCAP Iub Bearer
Release
10 . ALCAP Iur
Bearer Release
9. Radio Link Deletion Response
RNSAP RNSAP
RNSAP RNSAP
8. Radio Link Deletion
12. Radio Link Deletion Response
N B A P N B A P
N B A P N B A P
11 Radio Link Deletion
UE S -RNC Old
D-RNC
O ld
Node B
N ew
D-RNC
N ew
Node B
Figure 11: 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 Cell Update message
on CCCH.
2. The new RNC delivers this message transparently as Uplink Signalling TransferIndication message to the
serving RNC, the RNSAP delivers it to the RRC.
3. The serving RNC allocates radio resources for the RRC connection on Iur, and sends the RNSAP message
Radio Link Setup Request to the target RNC.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
28/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)273GPP TR 25.931 version 3.7.1 Release 1999
4. The target RNC sends the NBAP message Radio Link Setup Request to the target Node B.
5. Node B allocates resources, and responds with NBAP message Radio Link Setup Response.
6. Target RNC responds with RNSAP message Radio Link Setup Response.
7. 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.
8./9./10./11./12./13. 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.
14. The RRC in the serving RNC prepare a RRC Connection Re-establishment message and the RNSAP sends it in
the transparent message Downlink Signalling Transfer Request to the new CRNC.
15. The New CRNC delivers the Cell Update Confirm message on CCCH.
16. Message UTRAN Mobility Information Confirm is sent on the new DCCH from the UE to the serving RNC.
7.5.1.2 RRC Connection Re-establishment with SRNC Relocation - DCH Re-establishment
This subclause shows an example for the RRC Connection Re-establishment procedure, in dedicated transport channel
(DCH) state.
It is assumed that a signalling link is available on the Iur, but no DCH is established on this interface.
UE Node B
Serving
Node B
Target
RN C
Serving
RN C
Target
M SC
Ol d
M SC
Ne w
N B A P4. Radio Link Deletion Response
N B A P
RR C10 . CCCH : Cell Update Confirm
RR C
N B A P3. Radio Link Deletion
N B A P
6. SRNC Relocation
5. ALCAP Iub D ata Transport Bearer Deletion
RR C12 . DC CH : UTRAN Mobility Information Confirm
RR C
1. Reception of Uu Signalling Message
Cell Update
RNSAP
2. Uplink Signalling
Transfer IndicationRNSAP
[Cell Update]
N B A P8. Radio Link Setup Response
N B A P
N B A P7. Radio Link Setup Request
N B A P
9. ALCAP Iub D ata Transport Bearer Setup
Allocation ofCRNTI and
D R N T I
Release of CRNTI and
D R N T I
Allocation of SRNTI
N B A P11. Radio Link Restore Indication
N B A P
Figure 12: RRC Connection Re-establishment with SRNC Relocation - DCH Re-establishment
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
29/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)283GPP TR 25.931 version 3.7.1 Release 1999
1. The UE initiates the re-establishment of the RRC connection with the new cell by sending Cell Update message
on CCCH. The message is received by the Target RNC.
2. The target RNC delivers the received message transparently as Uplink Signalling Transfer Indication message
to the serving RNC.
3. The Serving RNC sends NBAP message Radio Link Deletion to Node B.
Parameters: Cell id, Transport layer addressing information.
4. Node B deallocates radio resources. Successful outcome is reported in NBAP message Radio Link Deletion
Response.
5. The SRNC initiates release of Iub Data Transport bearer using ALCAP protocol.
6. SRNC relocation procedure is triggered by the reception of the message Cell Update embedded in theRNSAP
Uplink Signalling Transfer Indication message (relocation is performed in parallel with Radio Link release).
7. The target RNC (new SRNC) allocates RNTI and radio resources for the RRC connection, and sends the NBAP
message Radio Link Setup Request 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), Power control information.
8. Target Node B allocates resources, starts PHY reception, and responses with NBAP message Radio LinkSetup
Response.Parameters: Signalling link termination, Transport layer addressing information for the Iub Data Transport
Bearer.
9. Target RNC (new 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.
10. Message Cell Update Confirm is sent on CCCH from target RNC (new SRNC) to UE.Parameters: Old RNTI, New RNTI, Transport Format Set, Transport Format Combination Set, frequency, DL
scrambling code (FDD only), Time Slots (TDD only), User Codes (TDD only).
11. Target Node B achieves uplink sync on the Uu and notifies SRNC with NBAP message Radio Link Restore
Indication.
12. Message UTRAN Mobility Info Confirm is sent on the new DCCH from the UE to the Target RNC (new
SRNC).
NOTE 1: SRNC Relocation execution is performed asynchronously with respect to the RL deletion procedure (step
3/4).
NOTE 2: Whether SRNC Relocation involves two MSCs (as depicted in the figure) or a single one, has no impact
on the UTRAN message flow shown in this example.
7.6 Radio Access Bearer EstablishmentThe following examples show establishment of a radio access bearer on a dedicated channel (DCH) or on a common
transport channel (RACH/FACH) when the RRC connection already support a radio access bearer either on a dedicated
channel (DCH) or on a common transport channel (RACH/FACH).
7.6.1 DCH - DCH Establishment - Synchronised
This example shows establishment of a radio access bearer (DCH) in dedicated transport channel (DCH) RRC state.
[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.].
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
30/82
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
31/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)303GPP TR 25.931 version 3.7.1 Release 1999
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).
Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data TransportBearer.
8. Node B allocates resources and notifies SRNC that the preparation is ready (Radio Link Reconfiguration
Ready).
Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport
Bearer.
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./12./13./14. The Nodes B and SRNC establish synchronism for the Iub and Iur Data Transport Bearer by meansof exchange of the appropriate DCH Frame Protocol frames Downlink Synchronisation and UplinkSynchronisation.
15. RNSAP message Radio Link Reconfiguration Commit is sent from SRNC to DRNC.
Parameters:
16. NBAP message Radio Link Reconfiguration Commit is sent from DRNC to Node B.
Parameters:
17. NBAP message Radio Link Reconfiguration Commit is sent from SRNC to Node B.Parameters:
18. RRC message Radio Access Bearer Setup is sent by SRNC to UE.
Parameters: Transport Format Set, Transport Format Combination Set, Time Slots (TDD only), User Codes(TDD only).
19. UE sends RRC message Radio Access Bearer Setup Complete to SRNC.
20. SRNC sends RANAP message Radio Access Bearer Assignment Response to CN.
7.6.2 DCH - DCH Establishment - Unsynchronised
This example shows the establishment of a radio access bearer (DCH) in dedicated transport channel (DCH) RRC state.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.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
32/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)313GPP TR 25.931 version 3.7.1 Release 1999
UE Node BDrift RNS
Node BServing RNS
DriftRNC
ServingRNC
CN
RNSAP RNSAP7. RL Reconfiguration
Response
RRCRRC18. DCCH:Radio Bearer Setup Complete
NBAPNBAP 11. Radio Link Reconfiguration Response
NBAPNBAP6. Radio Link Reconfiguration Response
13. Downlink Synchronisation
RRCRRC17. DCCH:Radio Bearer Setup
Apply new transport format set
Select L1, L2 and Iu DataTransport Bearer parameters
RANAP RANAP19. RAB Assignment
Response
RANAP RANAP1. RAB Assignment
Request
Not required towardsPS domainRNSAP RNSAP
3. RL Reconfiguration Request
[DCH Addition]NBAPNBAP 4. RL Reconfiguration Request
[DCH Addition]
NBAPNBAP5. Radio Link Reconfiguration
[DCH Addition]
10.
8. ALCAP Iur Data Transport Bearer Setup
9. ALCAP Iub Data Transport Bearer Setup
12. ALCAP Iub Data Transport Bearer Setup
2. ALCAP Iu Data Transport Bearer Setup
DCH-FPDCH-FP
15. Downlink SynchronisationDCH-FPDCH-FP
14. Uplink SynchronisationDCH-FPDCH-FP
16. Uplink SynchronisationDCH-FPDCH-FP
Figure 14: Radio Access Bearer Establishment - DCH - DCH Establishment Unsynchronised
1. CN initiates establishment of the radio access bearer with RANAP Radio Access Bearer Assignment Requestmessage.
Parameters: radio access bearer parameters, User Plane Mode, Transport Address, Iu Transport Association.
2. SRNC performs mapping of the radio access bearer QoS parameters to AAL2 link characteristics and initiates
set-up of Iu Data Transport bearer using ALCAP protocol (this step is not required towards PS domain).
Parameters: Served User Generated Reference, AAL2 link characteristics
3. SRNC decided that there are no need for a synchronous RL reconfiguration, and requests DRNC to setup a newDCH sending the RL Reconfiguration Request message. The modification shall be done immediately without
waiting for the command message.
Parameters: Bearer ID, Transport Format Set, Transport Format Combination Set, Power control information.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
33/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)323GPP TR 25.931 version 3.7.1 Release 1999
4. DRNC requests its Node B to establish of a new DCH in the existing Radio Link sending the RL
Reconfiguration Request message.
Parameters: Bearer ID, Transport Format Set, Transport Format Combination Set, Power control information.
5. SRNC requests its Node B setup a new DCH in the existing Radio Link sending the RL Reconfiguration
Request message.
Parameters: Bearer ID, Transport Format Set, Transport Format Combination Set, Power control information.6. Node B allocates resources and notifies DRNC that the setup is done sending the RL Reconfiguration
Response message.
Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport
Bearer.
7. DRNC notifies SRNC that the setup is done sending the RL Reconfiguration Response message.Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport
Bearer.
8. 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.
9. SRNC initiates setup of Iub Data Transport Bearer using ALCAP protocol. This request contains the AAL2Binding Identity to bind the Iub Data Transport Bearer to DCH.
10. DRNC performs bridging of Iub and Iur Data Transport bearers.
11. Node B allocates resources and notifies SRNC that the setup is sending the RL Reconfiguration Response.
Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport
Bearer.
12. 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.
13./14./15./16. The Nodes B and SRNC establish synchronism for the Iub and Iur Data Transport Bearer by means
of exchange of the appropriate DCH Frame Protocol frames Downlink Synchronisation and Uplink
Synchronisation.
17. RRC message Radio Bearer Setup is sent by SRNC to UE.
Parameters: Transport Format Set, Transport Format Combination Set.
18. UE sends RRC message Radio Bearer Setup Complete to SRNC.
19. SRNC sends RANAP message Radio Access Bearer Assignment Response to CN.
Parameters: Transport Address (Always for PS domain; for CS domain only if modified), Iu Transport
Association (Always for PS domain; for CS domain only if modified).
7.6.3 RACH/FACH - DCH Establishment
This example shows the establishment of a radio access bearer (DCH) in common transport channel (RACH/FACH)RRC State.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
34/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)333GPP TR 25.931 version 3.7.1 Release 1999
UE Node BDrift RNS
Node BServing RNS
DriftRNC
ServingRNC
CN
RRCRRC8. DCCH:Radio Bearer Setup Complete
NBAPNBAP 3. Radio Link Setup Response
RRCRRC6. DCCH:Radio Bearer Setup
RANAP RANAP9. RAB Assignment
Response
RANAP RANAP1. RAB Assignment
Request[Establishment]
NBAP
NBAP 2. Radio Link Setup Request
4. ALCAP Iub Data Transport Bearer Setup
5. ALCAP Iu Data Transport Bearer Setupnot required towards PS domain
NBAPNBAP 7. Radio Link Restore Indication
Figure 15: Radio Access Bearer Establishment RACH/FACH - DCH Establishment Unsynchronised
1. CN initiates establishment of the radio access bearer with RANAP Radio Access Bearer Assignment Request
message.
Parameters: radio access bearer parameters, User Plane Mode, Transport Address, Iu Transport Association.
2. DRNC requests its Node B to establish of a new DCH in the existing Radio Link sending the Radio Link Setup
Request message.
Parameters: Transport Format Set, Transport Format Combination Set, Power control information.
3. Node B allocates resources and notifies SRNC that the setup is sending the Radio Link Setup Response.
Parameters: Transport layer addressing information (AAL2 address, AAL2 Binding Id) for Iub Data Transport
Bearer.
4. 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.
5. SRNC performs mapping of the radio access bearer QoS parameters to AAL2 link characteristics and initiates
set-up of Iu Data Transport bearer using ALCAP protocol (this step is not required towards PS domain)
6. RRC message Radio Bearer Setup is sent by SRNC to UE.
Parameters: Transport Format Set, Transport Format Combination Set.
7. Node B achieves uplink sync and notifies SRNC with NBAP message Radio Link Restore Indication.
8. UE sends RRC message Radio Bearer Setup Complete to SRNC.
9. SRNC sends RANAP message Radio Access Bearer Assignment Response to CN.
7.6.4 RACH/FACH - RACH/FACH Establishment
This example shows the establishment of a radio access bearer (RACH/FACH) in common transport channel
(RACH/FACH) RRC state.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
35/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)343GPP TR 25.931 version 3.7.1 Release 1999
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RRCRRC48. DCCH: Radio Bearer Setup Complete
RRCRRC3. DCCH:Radio Bearer Setup
RANAP RANAP
5. RAB AssignmentResponse
RANAP RANAP
1. RAB AssignmentRequest
[Establishment]
2. ALCAP Iu Data Transport Bearer Setup
not required towards PS domain
Figure 16: Radio Access Bearer Establishment RACH/FACH RACH/FACH Establishment Unsynchronised
1. CN initiates establishment of the radio access bearer with RANAP Radio Access Bearer Assignment Request
message.
Parameters: radio access bearer parameters, User Plane Mode, Transport Address, Iu Transport Association.
2. SRNC performs mapping of the radio access bearer QoS parameters to AAL2 link characteristics and initiates
set-up of Iu Data Transport bearer using ALCAP protocol (this step is not required towards PS domain).
3. RRC message Radio Bearer Setup is sent by SRNC to UE.
Parameters: Transport Format Set, Transport Format Combination Set.
4. UE sends RRC message Radio Bearer Setup Complete to SRNC.
5. SRNC sends RANAP message Radio Access Bearer Assignment Response to CN.
7.7 Radio 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).
7.7.1 DCH - DCH Release - Synchronised
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.
[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.]
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
36/82
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
37/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)363GPP TR 25.931 version 3.7.1 Release 1999
10. NBAP message Radio Link Reconfiguration Commit is sent from DRNC to Node B.
11. NBAP message Radio Link Reconfiguration Commit is sent from SRNC to Node B.
12. RRC message Radio Bearer Release is sent by SRNC to UE.
Parameters: Transport Format Set, Transport Format Combination Set, Time Slots (TDD only), User Codes
(TDD only).
13. UE sends RRC message Radio Bearer Release Complete to SRNC.
14. Not used resources in DRNC and Node B (Drift RNS) are released. DRNC initiates release of Iur and Iub (Drift
RNS) Data Transport bearer using ALCAP protocol
15. Not used resources in SRNC and Node B (Serving RNS, if any) are released. SRNC initiates release of Iub
(Serving RNS) Data Transport bearer using ALCAP protocol.
16. SRNC acknowledges the release of radio access bearer (Radio Access Bearer Assignment Response). Note:
This message may be sent any time after step 1 provided the RNC is prepared to receive new establishment
request of a radio access bearer identified by the same radio access bearer identifier.
7.7.2 DCH - DCH Release - UnsynchronisedThis 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.
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RNSAP RNSAP
9. RL Reconfiguration
Response
RRCRRC
3. DCCHRadio Bearer Release Complete
NBAPNBAP10. Radio Link Reconfiguration Response
NBAPNBAP8. Radio Link Reconfiguration Response
RRCRRC2. DCCHRadio Bearer Release
RANAP RANAP
13. RAB Assignment
Response
12. ALCAP Iub Data Transport Bearer Release
4. ALCAP Iu Data
Transport Bearer Releasenot required towards PS domain
RANAP RANAP
1. RAB Assignment
Request
[Release]
RNSAP RNSAP
5. RL ReconfigurationRequest
[DCH Deletion]
NBAPNBAP6. RL Reconfiguration Request
[DCH Deletion]
NBAPNBAP7. RL Reconfiguration Request
[DCH Deletion]
ALCAP Iur Bearer Release11. ALCAP Iub Data Transport Bearer Release
Figure 18: 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 Bearer Release is sent by SRNC to UE.
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
38/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)373GPP TR 25.931 version 3.7.1 Release 1999
3. UE sends RRC message Radio Bearer Release Complete to SRNC.
4. SRNC initiates release of the Iu Data Transport bearer between the CN and the SRNC using the ALCAP
protocol (this step is not required towards PS domain).
5. SRNC requests DRNC to release of DCH carrying the radio access bearer.
Parameters: DCH ID, TFCS.
6. DRNC requests its Node B to release of DCH carrying the radio access bearer.Parameters: DCH ID, TFCS.
7. SRNC requests its Node B to prepare release of DCH carrying the radio access bearer.
Parameters: DCH ID, TFCS.
8. Node B acknowledges DRNC.
9. DRNC acknowledges SRNC.
10. Node B acknowledges SRNC.
11. SRNC initiates release of Iur Data Transport bearer using ALCAP protocol. Note: the release of the Iur link may
be done before step 9.
12. SRNC initiates release of Iub Data Transport bearer using ALCAP protocol. Note: the release of the Iub link
may be done before step 9.
13. SRNC acknowledges the release of radio access bearer to CN. Note: This message may be sent any time after
step 3 provided the RNC is prepared to receive new establishment request of a radio access bearer identified by
the same radio access bearer identifier.
7.7.4 RACH/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).
UE Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
CN
RRCRRC3. DCCHRadio Bearer Release Complete
RRCRRC2. DCCHRadio Bearer Release
RANAP RANAP
4. RAB Assignment
Response
5. ALCAP Iu Data
Transport Bearer Releasenot required towards PS domain
RANAP RANAP
1. RAB Assignment
Request
[Release]
Figure 19: Radio Access Bearer Release - RACH/FACH - RACH/FACH Release
1. CN initiates release of the radio access bearer with RANAP Radio Access Bearer Assignment Request
message.
2. RRC message Radio Bearer Release is sent by SRNC to UE.
3. UE sends RRC message Radio Bearer Release Complete to SRNC.
4. SRNC acknowledges the release of radio access bearer to CN.
5. SRNC initiates release of the Iu Data Transport bearer between the CN and the SRNC using the ALCAPprotocol (this step is not required towards PS domain).
-
7/27/2019 ETSI TR 125 931 V3.7.1 (2006-06)
39/82
ETSI
ETSI TR 125 931 V3.7.1 (2006-06)383GPP TR 25.931 version 3.7.1 Release 1999
7.8 Radio 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). The procedure starts from a radio access bearer assignment because
does not exist a special message to modify a radio access bearer, instead an "assignment" message is used.
7.8.1 DCCH on DCH - Synchronised
This