Contents
1 UTRAN System Architecture......................................................................................................................1
1.1 UTRAN Architecture...........................................................................................................................1
1.2 Explanation Related to RNS................................................................................................................1
1.3 UTRAN Common Protocol model......................................................................................................2
2 UMTS Interface Hierarchy..........................................................................................................................7
2.1 Control Plane and User Plane..............................................................................................................7
2.2 Access Layer and Non-access Layer...................................................................................................7
3 Interface and Protocol..................................................................................................................................1
3.1 Protocol Overview...............................................................................................................................1
3.1.1 RRC Connection Setup.............................................................................................................1
3.1.2 Network Registration Process..................................................................................................2
3.1.3 Connection Release Process.....................................................................................................4
3.2 Protocol Related to Interface Uu.........................................................................................................6
3.2.1 Uu Interface protocol architecture............................................................................................6
3.2.2 Status of RRC Protocol..........................................................................................................13
3.2.3 Some Explanations.................................................................................................................14
3.3 Protocol related to Interface Iu..........................................................................................................14
3.3.1 IU interface architecture.........................................................................................................14
3.3.2 Protocol Structure of Iu Interface...........................................................................................15
3.3.3 Some Explanations.................................................................................................................20
3.3.4 RANAP Process......................................................................................................................22
3.4 Protocol related to Interface Iur.........................................................................................................24
3.4.1 Function and Structure of Interface Iur..................................................................................24
i
ii
Core Network
Iu
UTRAN
Iu
RNS
RNS
Iur
RNC
Iub
Node B
RNC
Iub
Iub
Node B
Node B
Iub
Node B
DRNC (Drift RNC): In the case of soft handover of UMTS, UE can use several RNSs.
Figure 2 shows the relation of SRNS and DRNS.
Figure 2 SRNS and DRNS
Core Network
Iu
DRNS
Iur
SRNS
Cells
UE
Several links can exist inside one UE at the same time. The user data to access DRNS
is sent to SRNS from DRNS via Interface Iur. DRNC wont process the data but
transmit it between Interface Iub and Interface Iur transparently. One UE can access
one or several DRNSs.
CRNC (Control RNC): When UE access one RNS, the RNC of the RNS is called
CRNC. Therefore, in Figure 2, both SRNC and DRNC are CRNC. CRNC manages the
resources of the whole cell. SRNC schedules data on user DCH and CRNC schedules
data on CCH.
For Source RNC (S-RNC) and Target RNC (T-RNC), refer to Chapter of Interface Iu.
Radio
Network
Layer
Control Plane
User Plane
Application
Protocol
Data
Stream(s)
Transport Network
Control Plane
Transport Network
User Plane
ALCAP(s)
Signalling
Bearer(s)
Signalling
Bearer(s)
Data
Bearer(s)
Physical Layer
Horizontal, The Protocol Structure consists of two main layers, Radio Network Layer,
and Transport Network Layer. All UTRAN related issues are visible only in the Radio
Network Layer, and the Transport Network Layer represents standard transport
technology that is selected to be used for UTRAN, but without any UTRAN specific
requirements.
Vertical, UTRAn falls into the following 4 planes: control plane , user plane , TNL
control plane , TNL user plane.
Control plane
The Control Plane Includes the Application Protocol, i.e. RANAP, RNSAP or NBAP,
and the Signalling Bearer for transporting the Application Protocol messages.
Among other things, the Application Protocol is used for setting up bearers for (i.e.
Radio Access Bearer or Radio Link) in the Radio Network Layer. In the three plane
structure the bearer parameters in the Application Protocol are not directly tied to the
User Plane technology, but are rather general bearer parameters.
The Signalling Bearer for the Application Protocol may or may not be of the same type
as the Signalling Protocol for the ALCAP. The Signalling Bearer is always set up by
O&M actions.
User plane
3
The User Plane Includes the Data Stream(s) and the Data Bearer(s) for the Data
Stream(s). The Data Stream(s) is/are characterised by one or more frame protocols
specified for that interface.
The Transport Network Control Plane does not include any Radio Network Layer
information, and is completely in the Transport Layer. It includes the ALCAP
protocol(s) that is/are needed to set up the transport bearers (Data Bearer) for the User
Plane. It also includes the appropriate Signalling Bearer(s) needed for the ALCAP
protocol(s).
The Transport Network Control Plane is a plane that acts between the Control Plane
and the User Plane. The introduction of Transport Network Control Plane makes it
possible for the Application Protocol in the Radio Network Control Plane to be
completely independent of the technology selected for Data Bearer in the User Plane.
When Transport Network Control Plane is used, the transport bearers for the Data
Bearer in the User Plane are set up in the following fashion. First there is a signalling
transaction by the Application Protocol in the Control Plane, which triggers the set up
of the Data Bearer by the ALCAP protocol that is specific for the User Plane
technology.
The independence of Control Plane and User Plane assumes that ALCAP signalling
transaction takes place. It should be noted that ALCAP might not be used for all types
Data Bearers. If there is no ALCAP signalling transaction, the Transport Network
Control Plane is not needed at all. This is the case when pre-configured Data Bearers
are used.
It should also be noted that the ALCAP protocol(s) in the Transport Network Control
Plane is/are not used for setting up the Signalling Bearer for the Application Protocol
or for the ALCAP during real time operation.
The Signalling Bearer for the ALCAP may or may not be of the same type as the
Signalling Bearer for the Application Protocol. The Signalling Bearer for ALCAP is
always set up by O&M actions.
The Data Bearer(s) in the User Plane, and the Signalling Bearer(s) for Application
Protocol, belong also to Transport Network User Plane. As described in the previous
4
subclause, the Data Bearers in Transport Network User Plane are directly controlled by
Transport Network Control Plane during real time operation, but the control actions
required for setting up the Signalling Bearer(s) for Application Protocol are considered
O&M actions.
Non-Access Stratum
Radio
protocols
(1)
Radio
protocols
(1)
UE
Iu
Iu
proto
cols
proto
cols
(2)
(2)
Access Stratum
UTRAN
Radio
(Uu)
Iu
CN
CM Service Request
RNCUE
Authentication Request
UERNC
Authentication Response
RNCUE
CM Service Accept
UERNC
SETUP
RNCUE
Call Processing
RNCUE
Alerting
RNCUE
Connect
UERNC
Connect Acknowledge
Network registration
Connection release
Node B
Serving RNS
UE
RRC
Serving
RNC
Allocate RNTI
Select L1 and L2
parameters
2. Radio Link Setup Request
NBAP
NBAP
Start RX
description
3. Radio Link Setup Response
NBAP
NBAP
DCH-FP
DCH-FP
RRC
RRC
5. Downlink Synchronisation
6. Uplink Synchronisation
DCH-FP
DCH-FP
Start TX
description
7. CCCH : RRC Connection Setup
RRC
8. DCCH : RRC Connection Setup Complete
RRC
Detailed
descriptions:
At the beginning, UE does not have dedicated channel resources, so it sends the
message of RRC connection setup on CCCH (RACH).
9
RNC allocates RNTI and available resources to UE, decides to allocate DCH to UE,
and inform Node B to allocate DCH to UE with NBAP message of Radio Link Setup
Request.
Node B allocates resources to UE, starts to receive, and returns Radio Link Setup
Response to RNC.
At this time, there are no resources of the transmission network on Interface Iub, so
ALCAP of SRNC sends the message of ERQ (Establish Request). This message
contains AAL2 binding ID. This ID can help Node B to bind the data transmission
bearer on Interface Iub and DCH, and sends the message of ECF (Establish Confirm)
back to RNC.
Node
and
SRNC
perform
the
frame
synchronization
via
Downlink
10
Detailed descriptions:
After RRC connection sets up, UE establishes DCH. UE needs to change information
11
12
Detailed descriptions:
After Location Update completes, CN initiates Iu release process.
SRNC sends the message of RRC connection release to RRC.
UE sends the message of RRC connection release back to RNC.
RNC informs Node B to delete RL and after deleting RL, Node B replies to RNC.
RNC informs CN that returns Iu release completes via RANAP.
CN initiates to release SCCP link and RNC returns the message of SCCP release
confirmation.
RNC initiates to release the transmission resources on Interface Iub.
13
GC
DC
Duplication avoidance
Nt
GC
DC
UuS boundary
U-plane information
C-plane signalling
L3
control
Radio
Bearers
control
control
control
control
RRC
PDCP
RLC
RLC
PDCP
L2/PDCP
RLC
RLC
RLC
RLC
RLC
BMC
L2/BMC
RLC
L2/RLC
Logical
Channels
MAC
L2/MAC
Transport
Channels
PHY
L1
The Uu
interface is layered into three protocol layers:
Layer 2 is split into following sublayers: Medium Access Control (MAC), Radio Link
Control (RLC), Packet Data Convergence Protocol (PDCP) and Broadcast/Multicast
Control (BMC). Layer 3 and RLC are divided into Control (C-) and User (U-) planes.
PDCP and BMC exist in the U-plane only.
In the C-plane, Layer 3 is partitioned into sublayers where the lowest sublayer, denoted
as Radio Resource Control (RRC), interfaces with layer 2 and terminates in the
14
Priority handling between data flows of one UE. When selecting between the
Transport Format Combinations in the given Transport Format Combination Set,
15
Access Service Class selection for RACH and CPCH transmission. The RACH
resources (i.e. access slots and preamble signatures) and CPCH resources (i.e.
access slots and preamble signatures) may be divided between different Access
Service Classes in order to provide different priorities of RACH and CPCH usage.
In addition it is possible for more than one ASC or for all ASCs to be assigned to
the same access slot/signature space. Each access service class will also have a set
of back-off parameters associated with it, some or all of which may be broadcast
by the network. The MAC function applies the appropriate back-off and indicates
to the PHY layer the RACH and CPCH partition associated to a given MAC PDU
transfer.
Header
compression
and
decompression.
Header
compression
and
Transfer of user data. Transmission of user data means that PDCP receives
PDCP SDU from the NAS and forwards it to the RLC layer and vice versa.
Paging/notification. The RRC layer can broadcast paging information from the
network to selected UEs. Higher layers on the network side can request paging
and notification. The RRC layer can also initiate paging during an established
RRC connection.
Routing of higher layer PDUs. This function performs at the UE side routing of
19
higher layer PDUs to the correct higher layer entity, at the UTRAN side to the
correct RANAP entity.
Control of requested QoS. This function shall ensure that the QoS requested for
the Radio Bearers can be met. This includes the allocation of a sufficient number
of radio resources.
Outer loop power control. The RRC layer controls setting of the target of the
closed loop power control.
Control of ciphering. The RRC layer provides procedures for setting of ciphering
(on/off) between the UE and UTRAN.
Initial cell selection and re-selection in idle mode. Selection of the most suitable
cell based on idle mode measurements and cell selection criteria.
Integrity protection. This function adds a Message Authentication Code (MACI) to those RRC messages that are considered sensitive and/or contain sensitive
information.
This function configures the lower layers (L1, L2) of the UE when it shall listen to
the resources allocated for CBS based on scheduling information received from
BMC.
in
service
CELL_DCH
out of
service
in
service
in
service
GSM
Connected
Mode
GPRS
Packet
Transfer
Mode
CELL_FACH
out of
service
Release RRC
Connection
GSM:
Handover
UTRA:
Inter-RAT
Handover
CELL_PCH
Cell reselection
Establish RRC
Connection
Release of
temporary
block flow
Release RR
Connection
Establish RR
Connection
Initiation of
temporary
block flow
Idle Mode
21
URA_PCH status is similar to CELL_PCH status. The network can only determine the
URA cell which the UE locates in.
The introduction of CELL_PCH status and URA_PCH status is to keep UE always in
online status in order not to waster radio resources.
Node B
RNC
Iu-CS
Node B
PS
Domain
Iu-PS
Node B
RNC
BC
Domain
Node B
Iu-BC
Iu Interface
The
Iu
interface is specified at the boundary between the Core Network and UTRAN. Figure
depicts the logical division of the Iu interface. From the Iu perspective, the UTRAN
access point is an RNC. The Iu interface towards the PS-domain of the core network is
22
called Iu-PS, and the Iu interface towards the CS-domain is called Iu-CS. The
differences between Iu-CS and Iu-PS are treated elsewhere in the present document.
The Iu interface to the Broadcast domain is called Iu-BC.
There shall not be more than one Iu interface (Iu-PS) towards the PS-domain from any
one RNC. Each RNC shall not have more than one Iu interface (Iu-CS) towards its
default CN node within the CS domain, but may also have further Iu interfaces (Iu-CS)
towards other CN nodes within the CS domain. (See [6] for definition of Default CN
node.) These further Iu interfaces (Iu-CS) shall only be used as a result of intra-MSC
inter-system handover or SRNS relocation, in the case the anchor CN node directly
connects to the target RNC. There shall not be more than one Iu interface (Iu-BC) from
an RNC towards the Broadcast domain.
In the separated core network architecture, this means that there shall be separate
signalling and user data connections towards the PS and CS domains this applies in
both transport and radio network layers.
In the combined architecture, there shall be separate connections in the user plane
towards the PS and CS domains (in both transport and radio network layers). In the
control plane, there shall be separate SCCP connections to the two logical domains.
In either architecture, there can be several RNCs within UTRAN and so UTRAN may
have several Iu access points towards the Core Network. As a minimum, each Iu access
point (in UTRAN or CN) shall independently fulfil the requirements of the relevant Iu
specifications
23
Radio
Network
Layer
Transport
Network
Layer
Control Plane
User Plane
RANAP
Iu UP Protocol
Layer
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
Q.2630.1
Q.2150.1
SCCP
MTP3b
MTP3b
SSCF-NNI
SSCF-NNI
SSCOP
SSCOP
AAL5
AAL5
AAL2
ATM
Physical Layer
24
Radio
Network
Layer
Control Plane
User Plane
RANAP
Iu UP Protocol
Layer
Transport
Network
Layer
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
SCCP
M3UA
MTP3-B
GTP-U
SCTP
SSCF-NNI
SSCF-NNI
UDP
IP
SSCOP
IP
AAL5
AAL5
ATM
ATM
Physical Layer
Physical Layer
RANAP: user plane application protocol. It provides the signalling service between
UTRAN and CN that is required to fulfil the RANAP functions. RANAP protocol has
the following functions:
Relocating serving RNC. This function enables to change the serving RNC
functionality as well as the related Iu resources (RAB(s) and Signalling
connection) from one RNC to another.
Overall RAB management. This function is responsible for setting up, modifying
and releasing RABs.
Queuing the setup of RAB. The purpose of this function is to allow placing some
requested RABs into a queue, and indicate the peer entity about the queuing.
Requesting RAB release. While the overall RAB management is a function of the
CN, the RNC has the capability to request the release of RAB.
25
Controlling overload in the Iu interface. This function allows adjusting the load in
the Iu interface.
Paging the user. This function provides the CN for capability to page the UE.
Controlling the tracing of the UE activity. This function allows setting the trace
mode for a given UE. This function also allows the deactivation of a previously
established trace.
Transport of the initial NAS signalling message from the UE to CN. This function
Controlling the security mode in the UTRAN. This function is used to send the
security keys (ciphering and integrity protection) to the UTRAN, and setting the
operation mode for security functions.
Controlling location reporting. This function allows the CN to operate the mode in
which the UTRAN reports the location of the UE.
Location reporting. This function is used for transferring the actual location
information from RNC to the CN.
26
Reporting general error situations. This function allows reporting of general error
situations, for which function specific error messages have not been defined.
Location related data. This function allows the CN to either retrieve from the RNC
deciphering keys (to be forwarded to the UE) for the broadcasted assistance data,
or request the RNC to deliver dedicated assistance data to the UE.
SCCP: The SCCP is used to support signalling messages between the CNs and the
RNC. One user function of the SCCP, called Radio Access Network Application Part
(RANAP), is defined. The RANAP uses one signalling connection per active UE and
CN for the transfer of layer 3 messages. RANAP may use SSN, SPC and/or GT and
any combination of them as addressing schemes for the SCCP. Which of the available
addressing scheme to use for the SCCP is an operator matter. A new SCCP connection
is established when information related to the communication between a UE and the
network has to be exchanged between RNC and CN, and no SCCP connection exists
between the CN and the RNC involved, for the concerned UE.
MTP3B: provides message routing, discrimination and distribution (for point-to-point
link only), signaling link management load sharing and changeover/back between link
within one link-set. The need for multiple link-sets is precluded.
SAAL-NNI: SAAL-NNI [1] consists of the following sub-layers: - SSCF [3], - SSCOP
[2] and AAL5 [6]. The SSCF maps the requirements of the layer above to the
requirements of SSCOP. Also SAAL connection management, link status and remote
processor status mechanisms are provided. SSCOP provides mechanisms for the
establishment and release of connections and the reliable exchange of signalling
information between signalling entities. Adapts the upper layer protocol to the
requirements of the Lower ATM cells.
IUUP: user plane protocol.
GTP-U: GTP-U is used as the user data bearer towards the PS domain.RANAP
Signalling is used to establish, modify and release the GTP-U tunnels towards the PS
domain.
AAL2: AAL2 is used as the user data bearer towards the CS domain.Q.2630.2 is used
as the protocol for dynamically setup AAL-2 connections over Iu towards the CS
domain. Q.2630.2 adds new optional capabilities to Q.2630.1.
27
One UE can use 2 RNSs at the same time. The data can be sent on two RLs. In
addition, the data that UE sends to DRNC is sent to SRNC via Interface Iur, and SRNC
will combine them and send to CN.
If UE continues to move, the RL deterioration of UE on SRNS cannot be used again,
which will cause the following case.
Figure 13 SRNS relocation (II)
UE and SRNC have no direct contact, but all data still pass SRNC and reach CN via
Interface Iur. It will cause the waste of resources. Therefore, SRNS relocation should
be initiated, which can move Interface Iu from SRNC to DRNC. In the course of
SRNC relocation, SRNC (Serving RNC) is also called Source RNC and DRNC is also
28
called Target RNC. Figure 14 shows the result after the relocation completes.
Figure 14 SRNS Relocation (III)
SRNS relocation is the process to move Interface Iu from Source RNC to Target RNC.
Initiating
Successful Outcome
Unsuccessful Outcome
Procedure
Message
Response message
Response message
Iu Release
IU RELEASE
IU
COMMAND
COMPLETE
Relocation
RELOCATIO
RELOCATION
RELOCATION
Preparation
N REQUIRED
COMMAND
PREPARATION
RELEASE
FAILURE
Relocation
RELOCATIO
RELOCATION
RELOCATION
Resource
N REQUEST
REQUEST
FAILURE
Allocation
ACKNOWLEDGE
Relocation
RELOCATIO
RELOCATION
Cancel
N CANCEL
CANCEL
ACKNOWLEDGE
SRNS Context
SRNS
SRNS
Transfer
CONTEXT
RESPONSE
REQUEST
29
CONTEXT
Elementary
Initiating
Successful Outcome
Unsuccessful Outcome
Procedure
Message
Response message
Response message
Security Mode
SECURITY
SECURITY
SECURITY
Control
MODE
COMPLETE
MODE
MODE
REJECT
COMMAND
Data
Volume
Report
DATA
DATA
VOLUME
REPORT
VOLUME
REPORT
REQUEST
Reset
RESET
RESET
ACKNOWLEDGE
Reset
RESET
RESET
Resource
RESOURCE
ACKNOWLEDGE
RESOURCE
Location
LOCATION
LOCATION
related Data
RELATED
RELATED
DATA
RESPONSE
LOCATION RELATED
DATA
DATA FAILURE
REQUEST
Table 2 Class 2
Elementary Procedure
Message
Iu Release Request
IU RELEASE REQUEST
Relocation Detect
RELOCATION DETECT
Relocation Complete
RELOCATION COMPLETE
SRNS
DATA
FORWARD
COMMAND
SRNS Context Forwarding from Source RNC
to CN
SRNS Context Forwarding to Target RNC from
CN
Paging
PAGING
Common ID
COMMON ID
CN Invoke Trace
CN INVOKE TRACE
CN Deactivate Trace
CN DEACTIVATE TRACE
LOCATION
REPORTING
CONTROL
Location Report
LOCATION REPORT
Initial UE Message
INITIAL UE MESSAGE
Direct Transfer
DIRECT TRANSFER
Overload Control
OVERLOAD
30
Elementary Procedure
Message
Error Indication
ERROR INDICATION
Table 3 Class 3
Elementary Procedure
Initiating Message
Response Message
RAB Assignment
RAB
RAB
ASSIGNMENT
REQUEST
ASSIGNMENT
RESPONSE x N (N>=1)
Radio
Network
Layer
Control Plane
User Plane
RNSAP
Iur Data
Stream(s)
Transport Network
Control Plane
ALCAP(Q.2630.1)
STC (Q.2150.1)
SCCP
MTP3-B
Transport Network
User Plane
M3UA
MTP3-B
M3UA
SSCF-NNI
SSCF-NNI
SCTP
SSCF-NNI
SSCF-NNI
SCTP
SSCOP
IP
SSCOP
IP
AAL5
AAL5
AAL2
ATM
Physical Layer
The protocol structure of Interface Iur control plane (including RNL and TNL) is same
as that of Interface Iu control plane.
31
RNCs.
3GPP prescribes that Interface Iur is a logic entity. That is, Interface Iur and Interface
Iu can either share one channel for the transmission or connect via independent
physical interface.
Link
Setup
Initiating Message
RADIO
LINK
SETUP
Successful Outcome
Unsuccessful Outcome
Response message
Response message
RADIO
LINK
SETUP RESPONSE
FAILURE
RADIO
RADIO
REQUEST
Radio
Link
Addition
Radio
Link
Deletion
RADIO
LINK
ADDITION
ADDITION
REQUEST
RESPONSE
RADIO
LINK
RADIO
DELETION
DELETION
REQUEST
RESPONSE
ADDITION FAILURE
LINK
RADIO
Radio
RECONFIGURAT
RECONFIGURATI
RECONFIGURATION
ION PREPARE
ON READY
FAILURE
Unsynchronis
RADIO
RADIO
ed Radio Link
RECONFIGURAT
RECONFIGURATI
RECONFIGURATION
Reconfigurati
ION REQUEST
ON RESPONSE
FAILURE
Physical
PHYSICAL
PHYSICAL
PHYSICAL
Channel
CHANNEL
CHANNEL
CHANNEL
Reconfigurati
RECONFIGURAT
RECONFIGURATI
RECONFIGURATION
on
ION REQUEST
ON COMMAND
FAILURE
Reconfigurati
RADIO
LINK
Synchronised
Link
LINK
LINK
LINK
RADIO
LINK
on Preparation
LINK
LINK
RADIO
LINK
on
32
Elementary
Procedure
Initiating Message
Successful Outcome
Unsuccessful Outcome
Response message
Response message
Dedicated
DEDICATED
DEDICATED
DEDICATED
Measurement
MEASUREMENT
MEASUREMENT
MEASUREMENT
Initiation
INITIATION
INITIATION
INITIATION
REQUEST
RESPONSE
FAILURE
Common
COMMON
COMMON
COMMON
Transport
TRANSPORT
TRANSPORT
TRANSPORT
Channel
CHANNEL
CHANNEL
CHANNEL
Resources
RESOURCES
RESOURCES
RESOURCES
Initialisation
REQUEST
RESPONSE
FAILURE
Common
COMMON
COMMON
COMMON
Measurement
MEASUREMENT
MEASUREMENT
MEASUREMENT
Initiation
INITIATION
INITIATION
INITIATION
REQUEST
RESPONSE
FAILURE
Information
INFORMATION
INFORMATION
INFORMATION
Exchange
EXCHANGE
EXCHANGE
EXCHANGE
Initiation
INITIATION
INITIATION
INITIATION
REQUEST
RESPONSE
FAILURE
Initiating Message
UPLINK
SIGNALLING
TRANSFER
INDICATION
Downlink Signalling Transfer
DOWNLINK
SIGNALLING
TRANSFER
REQUEST
Relocation Commit
RELOCATION COMMIT
Paging
PAGING REQUEST
Synchronised
Radio
Link
Reconfiguration Commit
Synchronised
Radio
RADIO
LINK
RECONFIGURATION
LINK
RECONFIGURATION
COMMIT
Link
RADIO
Reconfiguration Cancellation
CANCEL
Dedicated
DEDICATED
Measurement
MEASUREMENT
Termination
TERMINATION REQUEST
33
Elementary Procedure
Compressed
Mode
Initiating Message
Command
[FDD]
Common
Transport
Channel
COMMON
TRANSPORT
CHANNEL
Resources Release
Error Indication
ERROR INDICATION
DL
[TDD]
REQUEST
POWER
TIMESLOT
CONTROL
INDICATION
Radio Link Congestion
COMMON
MEASUREMENT
TERMINATION REQUEST
Common Measurement Failure
COMMON
MEASUREMENT
FAILURE
INDICATION
Information Reporting
INFORMATION REPORT
INFORMATION
EXCHANGE
TERMINATION REQUEST
Information Exchange Failure
INFORMATION
EXCHANGE
FAILURE
INDICATION
34
Radio Network
Control Plane
Transport
Network
Control Plane
CPCH FP
USCH FP
DSCH FP
FACH FP
PCH FP
DCH FP
RACH FP
Node B
Application Part
(NBAP)
Radio
Network
Layer
User Plane
ALCAP
Q.2630.1
Q.2150.2
Transport
Layer
SSCF-UNI
SSCF-UNI
SSCOP
SSCOP
AAL Type 5
AAL Type 5
AAL Type 2
ATM
Physical Layer
Node B
Control
Port
Controlling RNC
Iub
RACH
Data
port
Iub
FDD
CPCH
Data
port
Iub
FACH
Data
port
Iub
DSCH
Data
port
Iub
FDD TFCI2
Data
Port
Iub
PCH
Data
port
Iub
TDD USCH
Data
port
Iub
DCH
Data
port
Iub
DSCH
Data
port
Iub
Communication
FDD TFCI2
Control
Data
Port
port
Cell
Cell
...
Node B
Cell
Iub
TDD USCH
Data
port
Iub
DCH
Data
port
Communication
Control
Port
Cell
Cell
Cell
35
Successful Outcome
Message
CELL
SETUP
Unsuccessful
Outcome
Response message
Response message
CELL
CELL
SETUP
SETUP
REQUEST
RESPONSE
FAILURE
Cell
CELL
CELL
CELL
Reconfigurati
RECONFIGURATIO
RECONFIGURATIO
RECONFIGURATIO
on
N REQUEST
N RESPONSE
N FAILURE
Cell Deletion
CELL
CELL
DELETION
DELETION
REQUEST
RESPONSE
Common
COMMON
COMMON
Transport
TRANSPORT
Channel
CHANNEL
Setup
REQUEST
RESPONSE
FAILURE
Common
COMMON
COMMON
COMMON
Transport
TRANSPORT
TRANSPORT
TRANSPORT
Channel
CHANNEL
CHANNEL
CHANNEL
Reconfigurati
RECONFIGURATIO
RECONFIGURATIO
RECONFIGURATIO
on
N REQUEST
N RESPONSE
N FAILURE
Common
COMMON
COMMON
Transport
TRANSPORT
TRANSPORT
Channel
CHANNEL
CHANNEL
Deletion
DELETION
DELETION
REQUEST
RESPONSE
36
COMMON
TRANSPORT
SETUP
CHANNEL
TRANSPORT
SETUP
CHANNEL
SETUP
Elementary
Procedure
Successful Outcome
Message
Unsuccessful
Outcome
Response message
Response message
Physical
PHYSICAL SHARED
PHYSICAL
PHYSICAL
Shared
CHANNEL
SHARED
SHARED CHANNEL
Channel
RECONFIGURATIO
CHANNEL
RECONFIGURATIO
Reconfigure
N REQUEST
RECONFIGURATIO
N FAILURE
[TDD]
N RESPONSE
Audit
AUDIT REQUEST
AUDIT RESPONSE
AUDIT FAILURE
Block
BLOCK RESOURCE
BLOCK RESOURCE
BLOCK RESOURCE
Resource
REQUEST
RESPONSE
FAILURE
Radio
RADIO
Setup
Link
REQUEST
SETUP RESPONSE
LINK
RADIO
SETUP FAILURE
LINK
System
SYSTEM
SYSTEM
SYSTEM
Information
INFORMATION
INFORMATION
INFORMATION
Update
UPDATE REQUEST
UPDATE
UPDATE FAILURE
Common
COMMON
COMMON
COMMON
Measurement
MEASUREMENT
MEASUREMENT
MEASUREMENT
Initiation
INITIATION
INITIATION
INITIATION
REQUEST
RESPONSE
FAILURE
RESPONSE
Radio
Link
Addition
Radio
Link
Deletion
RADIO
LINK
RADIO
LINK
RADIO
ADDITION
ADDITION
ADDITION
REQUEST
RESPONSE
FAILURE
RADIO
LINK
RADIO
DELETION
DELETION
REQUEST
RESPONSE
RADIO
Radio
RECONFIGURATIO
RECONFIGURATIO
RECONFIGURATIO
N PREPARE
N READY
N FAILURE
Reconfigurati
RADIO
LINK
Synchronised
Link
LINK
LINK
LINK
RADIO
LINK
on
Preparation
Unsynchronis
RADIO
ed
RECONFIGURATIO
RECONFIGURATIO
RECONFIGURATIO
N REQUEST
N RESPONSE
N FAILURE
Dedicated
DEDICATED
DEDICATED
DEDICATED
Measurement
MEASUREMENT
MEASUREMENT
MEASUREMENT
Initiation
INITIATION
INITIATION
INITIATION
REQUEST
RESPONSE
FAILURE
RESET REQUEST
RESET RESPONSE
Radio
Link
LINK
RADIO
LINK
RADIO
LINK
Reconfigurati
on
Reset
37
Elementary
Procedure
Successful Outcome
Message
Unsuccessful
Outcome
Response message
Response message
Cell
CELL
CELL
CELL
Synchronisati
SYNCHRONISATIO
SYNCHRONISATIO
SYNCHRONISATIO
on Initiation
[3.84Mcps
REQUEST
RESPONSE
FAILURE
Cell
CELL
CELL
CELL
Synchronisati
SYNCHRONISATIO
SYNCHRONISATIO
SYNCHRONISATIO
on
Reconfigurati
RECONFIGURATIO
RECONFIGURATIO
RECONFIGURATIO
on
N REQUEST
N RESPONSE
N FAILURE
Cell
CELL
CELL
CELL
Synchronisati
SYNCHRONISATIO
SYNCHRONISATIO
SYNCHRONISATIO
on
Adjustment
REQUEST
RESPONSE
FAILURE
Information
INFORMATION
INFORMATION
INFORMATION
Exchange
EXCHANGE
EXCHANGE
EXCHANGE
Initiation
INITIATION
INITIATION
INITIATION
REQUEST
RESPONSE
FAILURE
INITIATION
INITIATION
INITIATION
TDD]
[3.84
Mcps TDD]
ADJUSTMENT
ADJUSTMENT
ADJUSTMENT
[3.84Mcps
TDD]
Table 7 Class 2
Elementary Procedure
Message
Audit Required
COMMON
MEASUREMENT
FAILURE
INDICATION
Synchronised Radio Link Reconfiguration Commit
Elementary Procedure
Message
DEDICATED
MEASUREMENT
FAILURE
INDICATION
Downlink Power Control [FDD]
Unblock Resource
Error Indication
ERROR INDICATION
RADIO
LINK
PREEMPTION
REQUIRED
INDICATION
Cell Synchronisation Reporting [3.84Mcps TDD]
CELL
SYNCHRONISATION
FAILURE
INDICATION
Information Reporting
INFORMATION REPORT
INFORMATION
INDICATION
39
EXCHANGE
FAILURE