Beruflich Dokumente
Kultur Dokumente
Purpose:
Grasp the model of UTRAN common protocol
Reference:
ZTE WCDMA Fundamental Priciple
Contents
Highlights:
Core Network
Iu Iu
RNS RNS
UTRAN
Iur
RNC RNC
Inside UTRAN, the interface between RNC and Node B is Interface Iub.
1
1.2 Explanation Related to RNS
RNS (Radio Network Subsystem): The general name for one RNC and all Nodes B it
manages.
SRNC (Serving RNC): The RNS connecting with CN is called SRNS and the RNC of
RNS is called SRNC.
DRNC (Drift RNC): In the case of soft handover of WCDMA, UE can use several
RNSs. Fig. Explanation Related to RNS-2 shows the relation of SRNS and DRNS.
Core Network
Iu
DRNS SRNS
Iur
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 Fig. Explanation Related to RNS-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.
2
Chapter 1 WCDMA UTRAN System Archetecture
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
3
WR_BT06_E1_0 Interface Protocol and signaling flow
O&M actions.
User plane
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.
4
Chapter 1 WCDMA UTRAN System Archetecture
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
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.
5
2 WCDMA Interface Hierarchy
Highlights:
Control the radio access bearer and the connection between UE and the network;
In UTRAN, each interface of RNL has user plane and control plane.
The user plane data and control plane data of all RNL belong to TNL user plane. TNL
control plane protocol is ALCAP, belonging to SAAL (Signalling AAL) of ATM.
7
N o n -A cce s s S tra tu m
R a dio R a dio Iu Iu
p ro to - pro to - p ro to p ro to
co ls co ls co ls co ls
(1 ) (1 ) (2) (2 )
A c ce ss S tra tu m
UE UTR AN CN
R a d io Iu
(U u )
Fig. Access Layer and Non-access Layer-4 Access Layer and Non-access Layer
In AMR voice telephone (the calling party), there are several UE-CN signaling, which
are the control plane signaling of non-access layer. These signaling are encapsulated in
RRC protocol first and then transmitted to RNC transparently. RNC decodes these
signaling out of RRC messages, encapsulates into RANAP, and then transmits to CN
transparently via RANAP.
UERNC SETUP
RNCUE Alerting
RNCUE Connect
8
3 Interface and Protocol
Highlights
Network registration
Connection release
Fig. Protocol Related to Interface Uu-8 shows the flow of RRC connection setup.
9
UE Node B Serving
Serving RNS RNC
Allocate RNTI
Select L1 and L2
parameters
Start RX
description
3. Radio Link Setup Response
NBAP NBAP
5. Downlink Synchronisation
DCH-FP DCH-FP
6. Uplink Synchronisation
DCH-FP DCH-FP
Start TX
description
7. CCCH : RRC Connection Setup
RRC 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).
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.
10
Chapter 1 WCDMA UTRAN System Archetecture
Although DCH resources on Interface Iub are ready, UE does not know it. Therefore,
SRNC sends the message of RRC Connection Setup to UE on CCCH (FACH), and
informs UE of related parameters.
11
WR_BT06_E1_0 Interface Protocol and signaling flow
Detailed descriptions:
12
Chapter 1 WCDMA UTRAN System Archetecture
After RRC connection sets up, UE establishes DCH. UE needs to change information
with CN (this is signaling interaction of non-access layer and readers of non-access
layer signaling can refer to [3]), that is, to initiate the Location Update. This message is
encapsulated in the RRC message of Initial Direct Transfer, which is sent to RNC by
UE.
RRC of RNC receives the message of Initial Direct Transfer, decodes the high-layer
messages from it, and sends to RANAP entity. RANAP entity will encapsulate the
message of Location Update into Initial UE Message and sends it to CN through
SCCP entity. At this time, there is no signaling connection between RNC and CN, so
the message of Initial UE Message of RANAP is encapsulated into SCCP connection
setup massage (CR) and sent to CN.
SCCP entity of CN receives the SCCP connection setup request. It returns SCCP
connection setup message (CC) to RNC and sends the RANAP massage contained in
CR messages to RANAP entity. RANAP entity decodes the message of Location
Update of NAS layer and sends it to the related modules on NAS layer for processing.
After receiving the message of Location Update from UE, CN initiates the
authentication. The signalling during the authentication process is transmitted
transparently. RNC and Node B only transfer between UE and CN, but do not process
messages. Messages of Authentication Request and Authentication Response are
NAS messages, too. They are encapsulated into the message of Direct Transfer of
RANAP and RRC.
After the authentication check on UE is passed, CN initiates the security mode process.
It is to encrypt and protect the data and signaling of the air interface. Messages of
security mode are not transmitted transparently and it needs RNC processing.
After the authentication check is passed and the security mode is initiated, CN sends
the message of Location Update Accept to UE, informing that UE registration
succeeds. This message is transmitted transparently.
13
WR_BT06_E1_0 Interface Protocol and signaling flow
Detailed descriptions:
RNC informs Node B to delete RL and after deleting RL, Node B replies to RNC.
CN initiates to release SCCP link and RNC returns the message of SCCP release
confirmation.
Fig. Protocol Related to Interface Uu-8 shows the architecture of Uu Interface protocol.
GC Nt DC
Duplication avoidance
GC Nt DC
UuS boundary
C-plane signalling U-plane information
RRC control L3
Radio
control
control
control
control
Bearers
PDCP
PDCP L2/PDCP
BMC
L2/BMC
Logical
Channels
MAC L2/MAC
Transport
Channels
PHY L1
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.
15
WR_BT06_E1_0 Interface Protocol and signaling flow
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
UTRAN. The next sublayer provides 'Duplication avoidance' functionality. It
terminates in the CN but is part of the Access Stratum; it provides the Access Stratum
Services to higher layers. The higher layer signalling such as Mobility Management
(MM) and Call Control (CC) is assumed to belong to the non-access stratum..
The RLC sublayer provides ARQ functionality closely coupled with the radio
transmission technique used. There is no difference between RLC instances in C and U
planes.The UTRAN can be requested by the CN to prevent all loss of data (i.e.
independently of the handovers on the radio interface), as long as the Iu connection
point is not modified. This is a basic requirement to be fulfilled by the UTRAN
retransmission functionality as provided by the RLC sublayer.However, in case of the
Iu connection point is changed (e.g. SRNS relocation, streamlining), the prevention of
the loss of data may not be guaranteed autonomously by the UTRAN but relies on
'Duplication avoidance' functions in the CN.There are primarily two kinds of signalling
messages transported over the radio interface - RRC generated signalling messages and
NAS messages generated in the higher layers. On establishment of the signalling
connection between the peer RRC entities three or four UM/AM signalling radio
bearers may be set up. Two of these bearers are set up for transport of RRC generated
signalling messages - one for transferring messages through an unacknowledged mode
RLC entity and the other for transferring messages through an acknowledged mode
RLC entity.
- Priority handling between data flows of one UE. When selecting between the
16
Chapter 1 WCDMA UTRAN System Archetecture
17
WR_BT06_E1_0 Interface Protocol and signaling flow
- 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.
- 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.
18
Chapter 1 WCDMA UTRAN System Archetecture
The Radio Resource Control (RRC) layer handles the control plane signalling of Layer
3 between the UEs and UTRAN. The RRC performs the following functions:
19
WR_BT06_E1_0 Interface Protocol and signaling flow
is initiated by a request from higher layers at the UE side to establish the first
Signalling Connection for the UE. The establishment of an RRC connection includes
an optional cell re-selection, an admission control, and a layer 2 signalling link
establishment. The release of an RRC connection can be initiated by a request from
higher layers to release the last Signalling Connection for the UE or by the RRC layer
itself in case of RRC connection failure. In case of connection loss, the UE requests re-
establishment of the RRC connection. In case of RRC connection failure, RRC releases
resources associated with the RRC connection.
- 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
20
Chapter 1 WCDMA UTRAN System Archetecture
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.
21
WR_BT06_E1_0 Interface Protocol and signaling flow
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 WCDMA, all statuses of UE are scheduled by RRC protocol. One UE has several
RRC statuses, such as, Idle and DCH. Fig. Protocol Related to Interface Uu-9 shows
the status and status conversion (containing GSM status).
Idle Mode
Fig. Protocol Related to Interface Uu-9 RRC Status and Status Conversion
CELL_FACH status indicates that UE does not use any dedicated channel but uses the
common channel when the traffic is small. UL uses RACH and DL uses FACH. In this
status, UE can initiate cell reselection process and UTRAN can determine which cell
UE locates in.
CELL_PCH status indicates that UE only intercepts PCH and BCH. In this status, UE
can reselect the cell. During the reselection, it converts into CELL_FACH status, the
cell update initiates, and it returns to CELL_PCH status. The network can determine
the cell which the UE locates in.
22
Chapter 1 WCDMA UTRAN System Archetecture
URA_PCH status is similar to CELL_PCH status. The network can only determine the
URA cell which the UE locates in.
In CELL_PCH, URA_PCH or Idle status, UE can intercept PCH and BCH, and can
receive the message of Paging. In CELL_DCH or CELL_FACH status, UE cannot
intercept PCH and BCH. Paging Type 2 is introduced to page UE in these two statuses.
Usually, the permanent ID information of UE (such as, IMSI) will not be saved in
RNC. When UE is making a call, CN informs RNC of the IMSI of the UE with the
message of Command ID of RANAP. When CN requires RNC to page a specific UE,
RNC will judge which RRC status the IMSI to page is in, to decide the paging type
(Paging Type 1 or Paging Type 2).
RNC Iu-CS
Node B
PS
Domain
Node B Iu-PS
RNC BC
Node B Domain
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 I u interface. From the Iu perspective, the
23
WR_BT06_E1_0 Interface Protocol and signaling flow
UTRAN access point is an RNC. The Iu interface towards the PS-domain of the core
network is 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
Fig. Protocol related to Interface Iu-10 shows the structure of Interface Iu-CS protocol
and Fig. Protocol related to Interface Iu-11 shows the structure of Interface Iu-PS
protocol.
24
Chapter 1 WCDMA UTRAN System Archetecture
SCCP Q.2150.1
MTP3b MTP3b
SSCF-NNI SSCF-NNI
SSCOP SSCOP
ATM
Physical Layer
25
WR_BT06_E1_0 Interface Protocol and signaling flow
M3UA
MTP3-B
GTP-U
SCTP
SSCF-NNI
SSCF-NNI UDP
SSCOP IP IP
AAL5 AAL5
ATM ATM
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.
26
Chapter 1 WCDMA UTRAN System Archetecture
- 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 NAS information between UE and CN (see [8]). This function has
two sub-classes:
1. Transport of the initial NAS signalling message from the UE to CN. This function
transfers transparently the NAS information. As a consequence also the Iu signalling
connection is set up.
- 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.
27
WR_BT06_E1_0 Interface Protocol and signaling flow
- 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.
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.
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
28
Chapter 1 WCDMA UTRAN System Archetecture
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.
One case:
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.
29
WR_BT06_E1_0 Interface Protocol and signaling flow
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
called Target RNC. Fig. 5.3-5 shows the result after the relocation completes.
SRNS relocation is the process to move Interface Iu from Source RNC to Target RNC.
30
Chapter 1 WCDMA UTRAN System Archetecture
31
WR_BT06_E1_0 Interface Protocol and signaling flow
SSCF-NNI
SSCF-NNI SCTP SSCF-NNI
SSCF-NNI SCTP
SSCOP IP SSCOP IP
AAL5 AAL5 AAL2
ATM
Physical Layer
32
Chapter 1 WCDMA UTRAN System Archetecture
The protocol structure of Interface Iur control plane (including RNL and TNL) is same
as that of Interface Iu control plane.
Interface Iur is to transmit data when UE performs the soft handover between adjacent
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.
As shown in Fig Protocol related to Interface Iu-12, when UE crosses RNSs, DRNC
can forward DCH data to SRNC via Interface Iur. DRNC does not process DCH data
but directly send DCH data at Interface Iub to Interface Iur. DCH frames of Interface
Iur and Interface Iub keep consistent, to greatly reduce DCH data processing by
DRNC.
33
WR_BT06_E1_0 Interface Protocol and signaling flow
34
Chapter 1 WCDMA UTRAN System Archetecture
35
WR_BT06_E1_0 Interface Protocol and signaling flow
Node B
PCH FP
RACH FP
FACH FP
DSCH FP
USCH FP
CPCH FP
Radio
DCH FP
Application Part
Network (NBAP)
Layer
ALCAP
Q.2630.1
Q.2150.2
Transport
SSCF-UNI SSCF-UNI
Layer
SSCOP SSCOP
AAL Type 5 AAL Type 5 AAL Type 2
ATM
Physical Layer
......
C
ont
rollin
gRN
C
N
od
e B Iu
b Iu
b
Iu
b Iu
b Iu
b C
ommu
n ic
a tio
n Iu
b Iu
b Iu
b C
omm
unicatio
n
C
ontr
o l Iu
b Iu
b Iu
b Iu
b D
SCH D
SCH
F
DD T
F CI2 T
DD USCH DCH C
ontrol F
DD TFCI2 T
DD USCH DC
H Co
ntrol
Port R
ACH FD
D F
ACH PCH Da
ta Da
ta
D a
ta D a
ta Da
ta Port D a
ta D a
ta Da
ta Po
rt
Da
ta C
PCH Da
ta Da
ta po
rt po
rt
Po
rt po
rt po
rt po
rt po
rt po
rt
po
rt Da
ta po
rt po
rt
po
rt
T
ra
fficte
rmin
atio
npo
in
t T
rafficte
rmin
atio
npo
in
t
C
omm
onT r
an spor
tC ha
nne
ls
, N
odeB N
od
eBC
om mu
n ica
tionCo
nte
xts
,
withattr
ibute
s witha
ttrib
u te
s
...
C
ell C
ell C
ell C
ell C
ell C
ell
36
Chapter 1 WCDMA UTRAN System Archetecture
Node B communication context and the corresponding DSCH/DCH port are related to
dedicated user services.
There is only one NCP link on one Node B. RNC sends all Node B common control
signaling from NCP. NCP link must be setup before operating, maintaining, and
controlling Node B.
There can be several CCP links on one Node B. RNC sends all Node B dedicated
control signaling from CCP link. Usually, one cell inside Node B can be configured
with one CCP (it is just a routine, not certain.)
37
WR_BT06_E1_0 Interface Protocol and signaling flow
38
Chapter 1 WCDMA UTRAN System Archetecture
39
WR_BT06_E1_0 Interface Protocol and signaling flow
40
Chapter 1 WCDMA UTRAN System Archetecture
RNC Node B
Node B
startup NCP,CCP and ALCAP set up
process Reset process
NBAP. Cell setup request
NBAP and cell setup response
NBAP and SCCPCH setup request
NBAP and SCCPCH setup response
ALCAP: ERQ(FACH)
ALCAP :ECF
Cell setup ALCAP:ERQ(PCH)
process
ALCAP:ECF
FP synchronization process
NBAP: RACH setup request
NBAP: RACH setup response
ALCAP:ERQ( RACH)
ALCAP: ECF
PCCPCH
NBAP: System information update request
NBAP: System information update response
41
WR_BT06_E1_0 Interface Protocol and signaling flow
DT(Authentication req)
DT(Authentication resp)
DT(setup)
DT(call proceeding)
RL setup resp .
DCH_FP:Downlink SYNC
DCH_FP:Uplink SYNC
RB setup
DT(alerting)
DT(connect)
DT(connect ack)
Fig. CS Call Origination Flow (RRC Setup on CCH)-19 Call Origination Flow (RRC Setup on CCH)
42
Chapter 1 WCDMA UTRAN System Archetecture
RL setup req
RL setup resp.
DCH_FP:Downlink SYNC
DCH_FP:Uplink SYNC
DT(Authentication req)
DT(Authentication resp)
DT(setup)
DT(call proceeding)
RL reconfig commit
RB setup
DT(alerting)
DT(connect)
DT(connect ack)
Fig. CS Call Origination Flow (RRC Setup on DCH)-20 CS Call Origination Flow (RRC Setup on
43
WR_BT06_E1_0 Interface Protocol and signaling flow
DCH)
RL setup req
RL setup resp.
DCH_FPDL SYNC
DCH_FPUL SYNC
Initial UE message
DT(Authentication req)
DT(Authentication resp)
DT(setup)
DT(call confirmed)
RL reconfig commit
RB setup
DT(alerting)
DT(connect)
DT(connect ack)
44
Chapter 1 WCDMA UTRAN System Archetecture
Fig CS Call Termination Flow-21 CS Call termination Flow (RRC Setup on DCH)
RL delete
RL delete resp
ALCAP REL. req
ALCAP REL. cfn
45
WR_BT06_E1_0 Interface Protocol and signaling flow
RL delete
RL delete resp
ALCAP REL. req
ALCAP REL. cfn
46