Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Contents
1 Overview........................................................................................................................................................1
1.1 Basic Signaling Flow...........................................................................................................................1
1.1.1 Flow Classification...................................................................................................................1
1.1.2 Description to Basic Signaling Flow........................................................................................2
1.2 Basic Concept......................................................................................................................................4
1.2.1 UE Protocol State.....................................................................................................................4
1.2.2 UTRAN State Transition in Connection Mode........................................................................8
2 Network Selection Flow..............................................................................................................................15
2.1 UE Under Idle Mode.........................................................................................................................15
2.1.1 Overview.................................................................................................................................15
2.1.2 PMMN Selection and Reselection.........................................................................................16
2.2 Cell Selection and Reselection..........................................................................................................17
2.2.1 Cell Selection..........................................................................................................................17
2.2.2 Cell Reselection......................................................................................................................18
2.2.3 Cell Selection Away form Connection Mode.........................................................................18
2.2.4 Position Registraton................................................................................................................19
3 Handover Flow in the System....................................................................................................................21
3.1 Handover Overview...........................................................................................................................21
3.2 Soft Handover....................................................................................................................................22
3.2.1 Between Cells in NodeB........................................................................................................24
3.2.2 Between NodeBs in the Same RNC.......................................................................................24
3.2.3 Between RNCs.......................................................................................................................25
3.3 Hard Handover...................................................................................................................................26
i
iii
1 Overview
1.1 Basic Signaling Flow
1.1.1 Flow Classification
A variety of signaling flows exist in a UMTS system. In terms of protocol stack,
signaling flows can be access layer signaling flows or non-access layer signaling flows.
In terms of network composition, signaling flows can be categorized as circuitswitched or packet-switched.
Access layer and non-access layer signaling flows are actually so named from the
perspective of protocol stack. In the protocol stack, the RRC layer, RANAP layer, and
the protocol layers below them are access layers, while the MM, SM, CC, and SMS
layers above them are known as non-access layers. Simply put, the flow at the access
layer is the flow where the RNCs and NodeBs at the radio access layer need to take
part in the processing. The flow at a non-access layer refers to a signaling flow where
only UEs and CNs, but not RNCs or NodeBs, need to take part in the processing. The
signaling at the access layer paves the way for the signaling interaction at a non-access
layer. Through the signaling interaction at the access layer, a signaling path is
established between the UE and CN so that the signaling flow at a non-access layer can
be started.
The flows at the access layer include PLMN selection, cell selection, and radio
resource management flows. The radio resource management flows are the flows at the
RRC layer, including the RRC connection setup flow, flow of the signaling setup
between UEs and CNs, RAB setup flow, call release flow, handover flow, and SRNS
redirection flow. For the handover and SRNS redirection flows, the cross-RNC and
cross-SGSN/MSC cases exist. In such cases, SGSN/MSC is also needed. Therefore,
from the perspective of protocol stack, the flows at the access layer are all bottom layer
flows, through which bottom layer bearer is established for the signaling flows at upper
layers.
The non-access flow layer flows mainly include the CS domain mobility management,
the CS domain call control, the PS domain mobility management, and the PS domain
session management.
1
1.
When a subscriber UE is powered on, the signaling interaction at the access layer
is performed first. PLMN selection is then performed to select the network of a carrier,
followed by cell selection to reside in an appropriate cell. After that, an RRC
connection is established and the signaling connection on the Iu interface is set up. At
this point, through the signaling flows at these access layers, a signaling channel is
established between the UE and the CN in preparations for the signaling flows at nonaccess layers.
2.
are started. The subscriber then starts attached flows, including small flows such as
authentication, encryption, and location update.
3.
After the flows such as authentication pass, the UE enters the service-related
flows at non-access layers. Such flows include the call connection flows of the circuit
domain and the session management flows of the packet domain. Through these flows,
2
the service bearer links are established for the service. After that, the subscriber can
start to make a call or access the Internet.
4.
When the subscriber finishes using the service, the call connection flows of the
circuit domain and the session management flows of the packet domain are also
performed to tear down the service bearer links.
5.
If the subscriber powers off his/her mobile phone, the mobility management flows
at non-access layers are performed between the UE and CN to separate the circuit
domain from the packet domain.
6.
performs the signaling flows at the access layer to tear down the Iu signaling
connection and RRC signaling connection previously established.
At this point, the whole flow in which a subscriber powers on his/her mobile phone,
uses the service, and powers off the mobile phone without moving is complete. This
shows that the completion of the service process requires the cooperation between the
signaling flows at the access layer and those at non-access layers. The flows at the
access layer establish the signal bearer for the flows at non-access layers.
The version below describes one service flow with which the user make the called
service.
1.
network side.
2.
If no signaling connection exists between the UE and the CN, the signaling flows
at the access layer are performed between the UE, the RNC, and the CN to establish an
RRC connection and Iu interface signaling connection.
3.
performed.
4.
After that, service bearer links are established through the call connection flows of
the circuit domain and session management flows of the packet domain so that the
service can be performed.
5.
When the service is finished, the related service bearer links are torn down.
6.
Then, the signaling connections at the access layer, including the signaling
The previously described two flows mainly describe in general how to make services in
the case that the subscriber has no position change. This is only an overall and simple
description while various detailed flows are described in the subsequent chapters and
sections.
As mobile communication has the mobile feature, flows related to a variety of hanlding
mobilities are produced. For example, when the subscriber does not develop the
service, the position is changed, so as to produce such flows of mobility management
as position renewal; when the subscriber develops the service, the position changes so
as to produce such flows as handover and SRNS repositioning.
When UE is in the connection mode, there are following four kinds of state:
1.
CELL_DCH state
The cell to which the UE belongs can be obtained through the current active set of
the UE;
The UE can use the dedicated transport channel, uplink/downlink shard transport
channel, or a combination of these transport channels.
When the UE is in idle mode, the RRC connection is established on the dedicated
channel, and therefore the UE enters the CELL_DCH state from idle mode;
When in the CELL_FACH state, the UE uses the common transport channel and
uses the dedicated transport channel after a channel switchover. The UE enters the
CELL_DCH state from the CELL_FACH state.
5
2.
CELL_FACH state
A default uplink public channel or uplink shared transfer channel (such as RACH)
is assigned to the UE
The UE position in the cell level is known by UTRAN, which is the cell where the
UE initiated the latest cell renewal.
Monitor the BCH transfer channels and the decoding system information
messages of the current service cell
When the current cell turns to be another UTRA cell, one renewal process of the
cell is initiated.
Unless one new cell is selected, the allocated C-RNTI in the current cell is used as
the UE flag of the public transfer channel.
Transmit the uplink signaling and small data packet in the RACH
In the CELL_RACH state, if the data service is not activated during a period of
time, the UE will enter the CELL_PCH state so as to reduce the power
comsumption. Furthermore, when the UE temporary gets rid of the CELL_PCH
state and implements the cell renewal, after the renewal is finished, it will return
the CELL_PCH if no requirements are necessary in the UE and the network side.
3.
CELL_PCH state
No uplinking actve UE positions can be known by the UTRAN in the cell level,
which refers to the cell reported by the UE in the CELL_FACH state when the
latest cell renewal is initiated.
6
According to the DRX cycle monitor the paging time, and receive the paging
information on the PCH.
Monitor the BCH transfer channel of the current service cell to decode the system
information
In such case, the DCCH logic channel cannot be used. If the network tries to
initiate any activities, it needs to send one paging request on the PCCH logic
channel of the cell where the UE is located.
There are two ways for the UE to be converted to the CELL_FACH state: one way is to
make paging through the UTRAN while another way
4.
URA_PCH state
The UE uses the DRX technology to monitor the information on the PCH transfer
channel at some specific paging time.
The UE position is known by the UTRAN in the URA level, the specific one is the
URA reported in the CELL_FACH state when the latest URA renewal is initiated.
According to the DRX cycle monitor the paging time, and receive the paging
information on the PCH.
Monitor the BCH transfer channel of the current serive cell to decode the system
information
In such case, the DCCH logic channel cannot be used. If the network tries to
initiate any activities, it needs to send one paging request on the PCCH logic
channel of the cell where the UE is located.
In the URA_PCH state, no resources are allocated for the data transfer. Therefore,
if the UE has the data to transmit, firstly it is required to be coverted to the
7
CELL_FACH state.
When all the dedicated physical channels are released, the state transitions to
CELL_FACH. The state transition is completed through clear signaling (for example,
physical channel reconfiguration, radio bearer reconfiguration, radio bearer release,
radio bearer establishment, and transport channel reconfiguration)
3.
This state transition is completed through clear signaling (for example, physical
channel reconfiguration, radio bearer reconfiguration, radio bearer release, radio bearer
establishment, and transport channel reconfiguration).
4.
This state transition is completed through clear signaling (for example, physical
channel reconfiguration, radio bearer reconfiguration, radio bearer release, radio bearer
establishment, and transport channel reconfiguration)
5.
For DCH, multiple physical channel allocation policies should be provided. Such
allocation may be permanent (a DCH release message is needed) or based on time
segment or data volume.
For each burst packet, resource configuration can be completed through the fast
signaling on the DCH.
For each radio frame, the UE and network use the Transport Format Combination
Indicator (TFCI) to indicate the current data rates (respectively corresponding to uplink
and downlink traffic). In TDD mode, however, DCH and DSCH or USCH may be
mapped to different CCTrCHs, with their respective TFCIs completely independent.
DCH transport does not change because the DSCH/USCH exists at the same time. If
the configured combination set (the transport format set for a transport channel) is
8
Whether to use macro diversity (soft handover) depends on the data quantity and
frequency.
RRC connection mobility is processed by measurement report, soft handover, and nonsynchronization/synchronization.
7.
UE measurement (CELL_DCH)
In FDD mode, a UE with a specific capability (This UE supports the reception on one
SCCPCH and one DPCH simultaneously) can read the system information broadcast
on the FACH.
1.2.2.2 CELL_FACH State
1.
This state transition occurs when the UTRAN instructs the UE to enter the CELL_PCH
state through clear signaling, such as cell update confirmation and radio bearer
9
reconfiguration
3.
The UE enters the idle mode after releasing the RRC connection
4.
This state transition occurs when the UTRAN instructs the UE to enter the URA_PCH
state through clear signaling, such as URA update confirmation and radio bearer
reconfiguration.
5.
In the CELL_FACH state, the UE listens on a FACH. The UE should be able to send
uplink control signals and send small packets on the RACH.
The network can assign in advance transport channel parameters, such as the transport
format set, to the UE for use when the UE uses the DCH. When a physical channel is
assigned to the DCH, the UE should enter the CELL_DCH state and is used as the TFS
allocated in advance to the DCH
If no UE dedicated physical channel or transport channel configuration is specified, the
UE should use the common physical channel and transport channel configuration
according to the system information.
For uplink data transport, the UE reports the service traffic observed to the network so
that the network can re-assess the current resource allocation. This report should
contain the volume of data to be transported, buffer statuses within the UE, and so on.
When user data or control data is transmitted, a selection process is started to determine
whether to transport the data through a common transport channel or to transition to the
CELL_DCH state. This selection is dynamic and dependent on specific parameters,
such as service parameters (data size and packet burst frequency)
In FDD mode, the UTRAN can assign CPCH resources to the UE in the CELL_FACH
state. After being assigned CPCH resources, the UE continues to listen on the FACH.
The UE may use the RACH to send uplink control signals and small packets. The UE
can also choose to send large packets (larger than the packets carried on the RACH) on
the CPCH. The UE chooses either the RACH or one CPCH to maximally use the
available capacity on the channel
In FDD mode, for each CPCH used, the UE provides the UTRAN with CPCH
10
measurement data, including data, queue length (the size of the current data buffer),
average access time, and the service traffic of each CPCH used. Based on the
measurement information, the UTRAN can periodically reassign network resources.
The UTRAN assigns a CPCH set to each cell and assigns one to the UE. The UE can
dynamically access these CPCH resources without UTRAN control.
6.
In this state, the UE location on the cell level is known. When the UE selects a new cell
to observe the common downlink channel of the new cell, the UE uses the cell update
process to report to the UTRAN. Data transport can initiated on the downlink FACH
without paging in advance.
The UE listens on the system information about the UE itself and neighboring cells on
the broadcast channel and BCCH, and determines whether to perform a cell location
update based on this information
The UE should perform cell re-selection and start the cell update process when
selecting a new UTRA cell. If another non-UTRA radio access system cell is selected,
the UE should enter the idle mode and complete access according to the system
specifications
7.
UE measurement (CELL_FACH)
The UE should read the BCH to obtain valid system information. For each acquisition,
the UE may need the different combinations of the system information broadcast on the
BCH. The system information on the broadcast channel is arranged based on the time
the UE spends in obtaining the information needed.
After the system information is modified, the time arrangement information is updated
to reflect the change in the system information transported on the BCH. The new time
arrangement information is broadcast on the FACH to notify the UE of the change. If
11
the change is applicable to the UE, the modified system information is read on the
BCH.
1.2.2.3 CELL_PCH State
1.
The UE transitions to the CELL_FACH state is realized through the paging (paging
type 1) from the UTRAN or any uplink access.
2.
In the CELL_PCH state, the UE mobility is performed through the cell re-selection
process.
The UE should perform cell re-selection. When selecting a new UTRA cell, the UE
transites to the CELL_FACH state and starts a cell update process in the new cell. After
the cell update process is performed, if neither the UE nor the network transports data ,
the UE should return to the CELL_PCH state.
If another non-UTRA radio access system cell is selected, the UE should enter the idle
mode and complete access according to the system specifications.
When the UE activity is low, the UTRAN may order the UE to transition to the
URA_PCH state to reduce frequent cell updates. This transition is completed through
the CELL_FACH state. The UTRAN may provide a inactive timer and an optional
counter used to count the number of cell updates. When the number of cell updates
exceeds a certain limit (network parameter), the UTRAN orders the UE to transition to
the URA_PCH state.
4.
UE measurement (CELL_PCH)
The UE should read the BCH to obtain valid system information. For each acquisition,
the UE may need the different combinations of the system information broadcast on the
BCH. The system information on the broadcast channel is arranged based on the time
the UE spends in obtaining the information needed.
1.2.2.4 URA_PCH State
1.
Any activity will cause the UE to transition to the CELL_FACH state. For example, the
RACH performs uplink access or the paging (paging type 1) from the UTRAN.
Note that an RRC connection cannot be released in the URA_PCH state. The UE must
first transition to the CELL_FACH state before releasing the signing.
2.
In the URA_PCH state, the location of the UE on the URA level is known.
In this state, mobility is completed through the URA re-selection process. The UE
should perform cell re-selection. When selecting a new UTRA cell (This URA cell is
not the one originally used by the UE), the UE should transition to the CELL_FACH
state and initiate a URA update to the network. After the URA update process is
performed, if neither the UE nor the network transports data , the UE should return to
the URA_PCH state.
If another non-UTRA radio access system cell is selected, the UE should enter the idle
mode and complete access according to the system specifications.
4.
UE measurement (URA_PCH)
13
In the URA_PCH state, the mechanism of sending and updating system information is
the same as that in CELL_PCH state.
14
Indication
to user
Automatic/
Manual selection
PLMN Selection
and Reselection
Location
Registration
response
PLMNs
available
PLMN
selected
NAS Control
Cell Selection
and Reselection
Radio measurements
Registration
Area
changes
CM requests
Location
Registration
Figure 3 Idle Mode Process
15
After being powered on, the UE first selects a PLMN. After selecting a PLMN, the UE
begins to select a cell belonging to this PLMN. When such a cell is found, the
information about the neighboring cell can be obtained from the system information
(broadcast). Thus, the UE can select a cell with the best signals among these cells and
reside in the cell. Then, the UE initiates the location registration process (attach or
location update). If the operation succeeds, the UE resides in the cell. The UE resides
in the cell for four purposes:
1.
2.
3.
4.
When the UE resides in the cell and the registration succeeds, as the UE moves, the
signal strengths of the current cell and the neighboring cell keep changing. In this case,
the UE needs to select a most suitable cell. This is known as the cell re-selection
process. This most suitable cell is not necessarily the cell that currently has the best
signals. The reason is this: suppose the UE is at the edge of a cell and moves to and fro
between the two cells, which happen to belong to different LAs or RAs. Thus, the UE
needs to keep initiating location updates. This wastes not only resources but also the
UE energy. Therefore, there are certain rules as to which cell to be reselected among all
the cells.
After the UE reselects a cell, if the cell is found to belong to another rLA or RA, the
UE initiates the location update process so that the network obtains the latest UE
location information. The UE discovers LA or RA changes through the SIB1 in the
system broadcast information
If the location registration or update fails, for example, when the network rejects the
UE, or when the current PLMN is out of the coverage area, the UE can perform PLMN
re-selection to select another usable PLMN.
to find out the PLMN with the highest priority. In addition, there are two kinds of
modes to select and reselect: automatic and manual. In brief, the automatic network
selection is to select one PLMN for the UE according to the PLMN priority sequence
while the manual network selection is to display all the currently applicable networks
to the subscriber, give him/her the righ to select one PLMN.
Cell search
The purpose of cell search is to find a cell, which, though, may not belong to the
selected PLMN. The steps of cell search are as follows (A frequency needs to be locked
first, of course):
The UE obtains timeslot synchronization through the primary SCH. After timeslot
synchronization, frame synchronization needs to be performed. Frame synchronization
is completed through the synchronization code of the secondary SCH. In this
procedure, the scrambling code group of the cell is also determined. Then, the UE
associates each scrambling code of the scrambling code group on the CPICH until it
finds the greatest one among the related results. Thus, the primary scrambling code is
determined.
Obviously, if the UE already knows some information about the cell, such as the
frequency used and even the primary scrambling code, the above-mentioned procedure
can be accelerated greatly.
2.
From the above-mentioned procedure, the UE obtains the scrambling code of the
PCCPCH, whose channel code is known and unique through the whole UTRAN. Thus,
the UE can read the information of the broadcast channel.
When reading the MIB, the UE can determine whether the found PLMN is the one
intended, because there is a PLMN domain in the MIB. If yes, the UE finds another
SIB and obtains its contents based on the scheduling information in other SIBs
contained in the MIB. If not, the UE has to look for the next frequency, starting the
procedure all over again (from cell search).
If the current PLMN is the one intended by the UE, the UE reads SIB3 and obtains
"Cell selection and re-selection". Through the information obtained, the UE performs
calculations to determine whether the cell residence standards are met. If yes, the UE
considers the cell a suitable cell. The UE resides in the cell and reads the other system
information needed and initiates the location registration procedure.
If the above-mentioned conditions are not met, the UE reads SIB11 and obtains the
information on the neighboring cells. Thus, the UE can perform calculations and
determines whether the neighboring cell meets the cell selection residence standards.
If the UE finds that any neighboring meets the cell residence standards, the UE resides
in the cell, reads other system information needed, and initiates the location registration
procedure.
If the UE finds no cell that meets the cell residence standards, the UE considers that
there is coverage and continues the PLMN selection and re-selection.
19
Intra-mode handover: Softer handover, soft handover, and hard handover are intra-
mode handovers.
frequency handover
2.
Transition Between Modes: It refers to the transition to the UTRA TDD mode.
3.
the GSM system, namely, a handover to the 900 MHz, 1800 MHz, 1900 MHz GSM
systems.
During a hard handover, before a new link is established, the old link of a mobile
station is released. That is, a channel can be established only after it is released. The old
channel is torn down before being synchronized with the new channel. The old and the
new channels do not take effect at the same time.
During a soft handover or softer handover, the mobile station and UTRAN maintain at
least one link between them. That is, a channel is removed before a new channel is
established. The original channel is removed only after the new channel takes effect.
Inter-frequency handovers and inter-system handovers are always hard handovers.
Intra-frequency handovers are not necessarily soft handovers. For example, if no Iur
interface exists, a cross-Iur interface intra-frequency handover is a hard handover, and
the new and old links cannot take effect at the same time. Here is another example. If
the transmitting diversity modes of intra-frequency cells are different, no soft handover
can be performed, either.
Basic Concepts:
1.
Monitor set: Cells not in the active set but monitored according to the adjacent
21
cell list assigned by the UTRAN belong to the monitor set. The UE measures the cells
in the monitor set. If the measurement results meet certain conditions, these cells may
be added to the active set. Therefore, the monitor set is sometimes known as the
candidate set.
3.
Detected Set: Set of cells in neither the active set nor the monitor set.
During a softer handover, a mobile station is located where the coverage of two
adjacent sectors of a base station overlaps. The mobile station and base station
communicate with each other through two air interface channels. There is one air
interface channel in each sector. Thus, two spread spectrum codes need to be used in
the downlink and the mobile station can distinguish these signals. The mobile station
receives and processes these two signals through Rake receiver. This process is very
similar to multi-path reception except that despread spectrum codes are need to be
generated for each sector to ensure correct despread spectrum operations. In the uplink,
a similar process is performed on the base station: The code division channel of the
mobile station is received in each sector, sent to the same baseband Rake receiver, and
merged to the maximum ratio through a normal method. During a softer handover, for
each connection, only one power control loop is active.
During a soft handover, a mobile station is located where the coverage of two sectors
of different base stations overlaps. Same as a softer handover, the mobile station and
two base stations perform communication through two different air interface channels
at the same time. Same as a softer handover, the mobile station receives two channels
(signals) through merging to the maximum ratio by using a Rake receiver. From the
perspective of the mobile station, there is very little difference between a soft handover
and a softer handover. In the uplink, however, the difference between a soft handover
and a softer handover is very great: Two base stations receive the code division
channels from the mobile station, but the received data is sent to the RNC for selective
merging. This is because the frame reliability indicator provided for external loop
power control needs to be used in the RNC to select the better frame from the two
candidate frames. Such selection occurs each time the interlacing interval is complete.
That is, the selection occurs ever 10 ms to 80 ms.
23
In this case, the radio uplink can be merged in NodeB or the SRNC. If the radio uplink
is merged in NodeB, it is known as a softer handover.
The softer handover flow is basically the same as the soft handover flow between
NodeBs. The only difference is that a softer handover is a handover in NodeB, with Iub
interface message as RADIO LINK ADDITION REQUEST, while the switching Iub
interface message between NodeBs is RADIO LINK SETUP REQUEST.
Soft Handover Between RNCs in the Same MSC uses the Iur interface:
25
are completed through the following five types of operations, of which physical
channel reconfiguration is the most commonly performed operation.
1.
2.
3.
4.
5.
Upper-layer planning
The upper layer obtains the scheduling information of the compression mode, lowers
the data rate, and inserts DTX bits when a radio frame mapping is established to create
transfer slots.
2.
Change spreading spectrum factors to improve data rates. For example, the physical
layer changes the timeslot sequence number assigned by the upper layer from the
timeslot format corresponding to the spreading spectrum factor 128 to the timeslot
format corresponding to the spreading spectrum factor 64. This effectively doubles the
number of symbols for valid physical timeslots and creates blank timeslots.
3.
Puncturing methods
With the spread spectrum factor and channelized code sequence unchanged, the
puncturing of rate matching module in the code, multiplexing link at the physical layer
can be used to lower the data rates. The transfer gap lengths (TGL) generated in this
way, however, are relatively short.
A compression mode is generally used for the downlink. If the uplink enters the
compression mode, the downlink must enter the compression mode in cooperation at
27
28
inter-system cut-away consists of two phases: Iu interface CS-domain inter-system cutaway preparation and Uu interface inter-system cut-away request. Iu interface CSdomain inter-system cut-away preparation phase corresponds to the relocation
preparation message. Uu interface inter-system cut-away request phase corresponds to
the cut-away message HANDOVER FROM UTRAN COMMAND. CS-domain intersystem cut-aways involve the Iu interface relocation process and Uu interface system
CS-domain cut-away process. The Iu interface relocation process corresponds to the
resource allocation message. The Uu interface system CS-domain cut-away process
corresponds to the HANDOVER TO THE UTRAN COMPLETE message, with the Uu
interface system CS-domain cut-away process as an intermediate process.
A PS-domain handover can be initiated by the UE or by the network side. A PS-domain
cut-away is initiated by the network side for the UE in the CELL_DCH or
CELL_FACH state, involving the Uu interface PS-domain cut-away process and Iu
interface context information acquisition process. The Uu interface PS-domain cutaway process corresponds to the CELL CHANGE ORDER FROM UTRAN message.
The Iu interface context information acquisition is an intermediate process,
corresponding to the Iu interface context information acquisition message. The PSdomain cut-away initiated by the UE is for the UE in the CELL_FACH, CELL_PCH,
or URA_PCH state, triggered by the UE cell re-selection process and with no
corresponding message on Uu interface. Only the context information acquisition
process exists on the Iu interface. The context information acquisition process on the Iu
interface consists of two phases: Iu interface context information acquisition request
and context transfer, respectively corresponding to the messages SRNS CONTEXT
UE
REQUEST/SRNC
NODE B
CONTEXT
S R N RESPONSE
C
andC N SRNS
DATA
BFORWARD
SC
initiated by the network side corresponds to the RRC connection establishment request
H A N D O V E R FR O M U T R A N C O M M A N D
reason Inter-RAT cell change order. The subsequent RAB assignment message on Iu
A N D number
O V E R Cinformation
O M P L E T E about the PDCP and GTP-U.
interface contains theHserial
H A N D O V ER D ETECT
H A N D O V E R C O M PL E T E
IU R E L E A S E C O M M A N D
IU30R E L E A S E C O M P L E T E
R A D IO L IN K D E L E T IO N R E Q U E S T
R A D IO L IN K D E L E T IO N R E S P O N S E
UE
NODE B
SR N C
CN
B SC
H A N D O V E R R E Q U IR D
R E L O C A T IO N R E Q U E S T
R A D IO L IN K S E T U P R E Q U E S T
R A D IO L IN K S E T U P R E S P O N S E
R E L O C A T IO N R E Q U E S T A C K
H A N D O V ER CO M M A N D
H A N D O V ER TO U TR A N CO M M A N D
R A D IO L IN K R E S T O R E IN D IC A T IO N
R E L O C A T IO N D E T E C T
H A N D O V ER TO U TR A N C O M PLE TE
31
R E L O C A T IO N C O M P L E T E
CLEA R CO M M A N D
C L EA R C O M PLETE
UE
B SS
2G
SG SN
SR N S
3G
SG SN
32
new M S /
VLR
UE
NODE B
SR N C
CN
B SC
H A N D O V E R R E Q U IR D
R E L O C A T IO N R E Q U E S T
R A D IO L IN K S E T U P R E Q U E S T
R A D IO L IN K S E T U P R E S P O N S E
R E L O C A T IO N R E Q U E S T A C K
H A N D O V ER CO M M A N D
H A N D O V ER TO U TR A N CO M M A N D
R A D IO L IN K R E S T O R E IN D IC A T IO N
R E L O C A T IO N D E T E C T
H A N D O V ER TO U TR A N C O M PLE TE
33
R E L O C A T IO N C O M P L E T E
CLEA R CO M M A N D
C L EA R C O M PLETE
Cell update process among the cells in the RNC Depending on parameter
differences, this process can be divided into two flows: one requiring reconfiguration
(returning the RB/Trch/Phy reconfiguration complete message) and the other requiring
no reconfiguration (If a parameter such as a newly assigned C_RNTI, the UE needs to
return the Mobility Info Confirm message).
2.
Cell update process among different RNC cells This process is further divided
into two flows: one requiring relocation (updating SRNC) and the other requiring no
relocation (updating DRNC).
34
35
36
2.
message.
3.
4.
5.
6.
signaling connection;
2.
The UTRAN initiates the paging that triggers UE state transition to transit the UE
When the system information changes, the UTRAN initiates the paging that
triggers the UE to read the updated system information. In this case, the value label of
the master information block (MIB) is contained in the "BCCH modification info" in
PAGING TYPE 1 message.
38
UE
UTRAN
PAGING TYPE 1
The UTRAN sends the PAGING TYPE1 message when an appropriate paging
opportunity is available to start the paging process. The UTRAN can select multiple
paging opportunities to repeatedly page a UE to increase the possibility of the UE
correctly receiving paging messages.
The UE in idle mode or PCH state monitors the appropriate paging opportunities and
receives the paging messages from the network layer.
UE
UTRAN
PAGING TYPE 2
The UTRAN sends the PAGING TYPE2 message through the DCCH channel to
initiate the paging process. Such paging is also known as dedicated paging. The UE
receives and reads the contents in the PAGING TYPE 2 message and reports the
paging reason, paging record category identifier, and other information to the nonaccess layer of the local side. The paging flow is complete.
39
This process does not affect any other RRC process running on the UE side.
If the UE finds any protocol error in the PAGING TYPE 2 message received, the UE
discards the paging message, uses the AM RLC mode through the uplink DCCH, and
sends the RRC STATUS message to the UTRAN.
In this case, the UTRAN pages the UE by sending a PAGING TYPE1 message.
2.
connection mode.
In this case, the UTRAN first transitions the state of the UE from CELL_PCH or
URA_PCH to CELL_FACH by sending a PAGING TYPE1 message. Then, the
UTRAN pages the UE by sending a PAGING TYPE2 message.
4.
channels. If the RRC connection cannot be established, the RNC rejects the
establishment of the RRC connection.
DescriptionRRC connection establishment requests are always initiated by the UE.
An RRC connection release request is initiated by the RNC. Each UE can have up to
one RRC connection.
UE
NodeB
RNC
RRC
2.Allocate parameters
such asRNTIL1
L2
3. RADIO LINK SETUP REQUEST
NBAP
NBAP
4. RADIO LINK SETUP RESPONSE
NBAP
NBAP
RRC
7.DCCH: RRC CONNECTION SETUP COMPLETE
RRC
RRC
According to the RRC connection request cause and the system resource state, the
RNC decides that the UE is set up on the special channel, and allocates RNTI, radio
resources and other resources (L1 and L2 resources).
3.
The RNC sends the NodeB the RADIO LINK SETUP REQUEST to request the
NodeB for allocating the specific radio link resources necessary for the RRC
41
connection.
4.
The RNC uses the ALCAP protocols to set up the Iub interface user side transfer
bearer, and implements the synchronous process between the RNC and the NodeB.
6.
Through the downlink CCCH channel, the RNC sends the UE the RRC
After the UE verifies that the RRC connection setup succeeds, the newly setup
uplink DCCH channel sends the RNC the RRC CONNECTION SETUP COMPLETE
message. The RRC connection setup process is finished.
UE
NodeB
RNC
RRC
RRC
5.DCCH: RRC CONNECTION SETUP COMPLETE
RRC
RRC
42
UE
RNC
UE
SRNC
CN
RRC
2.INITIAL UE MESSAGE
RANAP
RANAP
3.CONNECITON CONFIRMSUCCESS
SCCP
SCCP
4.CONNECTION REFUSEFAILURE
SCCP
SCCP
After the RRC connection is set up, the UE sends the RNC the INITIAL DIRECT
TRANSFER information through the RRC connection while the information carries
such content as initial NAS information and NC flags sent to the CN by the UE.
2.
The RNC receives the initial direct transfer information of the UE, and sends the
CONNECTION REFUSE information to the SCCP while the SCCP connection setup
fails. If the RNC receives the information and verifies the signaling connection setup to
fail, the RNC enables the RRC release process.
For the NAS content carried during the initial direct transfer process, the CN will send
the UE the acceptance or refusal information to the service through the downlink direct
transfer process.
UE
SRNC
CN
RRC
2.DIRECT TRANSFER
RANAP
RANAP
1.
the uplink direct transfer process. The message contains such information as NAS
message and CN identification.
2.
The RNC routes the message according to the CN identifier in the message and
sends the NAS information carried in the message to the CN through a DIRECT
TRANSFER message on Iu interface. The uplink direct transfer process is complete.
Description: If the UPLINK DIRECT TRANSFER message includes the Measured
Results on RACH information unit, it shows that the message carries the measurement
report while the UTRAN uses the related analyzed information content to control the
radio resource and the rest of the message is still transmitted to the CN.
UE
SRNC
CN
1.DIRECT TRANSFER
RANAP
RANAP
RRC
downlink direct transfer process. The message contains the NAS message.
2.
DCCH channel in AM RLC mode. The message carries the NAS information that the
CN sends to the UE and CN identifier.
46
The UE receives and reads the DOWNLINK DIRECT TRANSFER message carrying
the NAS information. If the received message contains a protocol error, the UE sends
an RRC STATUS message on the uplink DCCH in AM RLC mode.
capability
information
includes
security
capability, location
capability,
After an RRC connection is established, when the RNC finds that the
changes, the UE sends the new UE capability information to the RNC through a UE
CAPABILITY INFORMATION message.
47
UE
UTRAN
UE CAPABILITY ENQUIRY
Through the downlink DCCH logic channel, the UTRAN introduces the AMRLC
mode to send the UE CAPABILITY ENQUIRY message to implement the UE
capability information query process.
1.
DCH-DCH: Before the RAB is established, an RRC connection uses the DCH.
CCH-DCH: Before the RAB is established, an RRC connection uses the CCH.
CCH-CCH: Before the RAB is established, an RRC connection uses the CCH.
4.6.1 DCH-DCH
When the current RRC state of the UE is DCH, the RAB assigned can be established
on DCH only. Based on radio link reconfiguration, the RAB establishment flow can be
divided into two scenarios:
1.
2.
The difference between the two is whether the new configuration parameter can be
used immediately when the NodeB and UE receive the configuration message
delivered by the Serving Radio Network Controller (SRNC).
49
SRNC, the NodeB cannot use the new configuration parameter immediately. Instead,
the NodeB prepares the corresponding radio resources, waits for the reconfiguration
execution message delivered by the SRNC, and obtains the synchronization time
specified by the SRNC;
2.
Upon receiving the configuration message delivered by the SRNC, the UE also
cannot immediately use the new configuration parameter. Instead, the UE obtains the
synchronization time specified by the SRNC in the message;
3.
At the synchronization time specified by the SRNC, NodeB and UE use the new
UE
NodeB
CN
SRNC
1. RAB ASSIGNMENT REQUEST
RANAP
RANAP
2.ALCAP setup
NBAP
RRC
NBAP
RRC
RANAP
1.
Upon receiving the RAB establishment request, the SRNC maps the QoS
parameters of the RAB to AAL2 link feature parameters and radio resource feature
parameters. The ALCAP of Iu interface initiates the user plane transport bearer
establishment process according to the AAL2 link feature parameters (For the PS
domain, this step does not exist).
3.
the controlled NodeB to request the controlled NodeB to prepare to add one or more
dedicated channels (DCHs) carrying RAB on the existing radio link.
4.
NodeB allocates the resources accordingly and then sends a RADIO LINK
The ALCAP of the Iub interface in the SRNC initiates the user plane transport
bearer establishment process on Iub interface. NodeB and SRNC exchange the
uplink/downlink
synchronization
frames
of
the
DCH
frame
protocol
for
synchronization.
6.
The SRNC sends a RADIO BEARER SETUP message of the RRC protocol to the
UE.
7.
Upon receiving the RADIO BEARER SETUP COMPLETE message, the SRNC
described as follows.
UE
NodeB
CN
SRNC
1. RAB ASSIGNMENT REQUEST
RANAP
RANAP
2.ALCAP setup
3. RADIO LINK RECONFIGURATION
REQUEST
NBAP
NBAP
4. RADIO LINK RECONFIGURATION
RESPONSE
NBAP
NBAP
RRC
7. RADIO BEARER SETUP COMPLETE
RRC
RRC
8. RAB ASSIGNMENT RESPONSE
RANAP
RANAP
Upon receiving the RAB establishment request, the SRNC maps the QoS
parameters of the RAB to AAL2 link feature parameters and radio resource feature
parameters. The ALCAP of Iu interface initiates the user plane transport bearer
establishment process according to the AAL2 link feature parameters (For the PS
domain, this step does not exist).
3.
NodeB assigns the resources accordingly and then returns a RADIO LINK
RECONFIGURATION RESPONSE message to the SRNC to which the NodeB
52
belongs, notifying the SRNC that the radio link reconfiguration is complete.
5.
The ALCAP of the Iub interface in the SRNC initiates the user plane transport
bearer establishment process on Iub interface. NodeB and SRNC exchange the
uplink/downlink
synchronization
frames
of
the
DCH
frame
protocol
for
synchronization.
6.
The SRNC sends a RADIO BEARER SETUP message of the RRC protocol to the
UE.
7.
After executing radio bearer setup, the UE sends a RADIO BEARER SETUP
Upon receiving the RADIO BEARER SETUP COMPLETE message, the SRNC
4.6.2 CCH-DCH
When a RRC connection is established on a CCH, the RNC can establish the assigned
RAB on a DCH according to the QoS parameters in the RAB assignment message. In
this case, the RRC connection state needs to be changed from CCH to DCH.
CCH-DCH RAB setup flow is shown in the following figure.
UE
NodeB
CN
SRNC
1. RABASSIGNMENT REQUEST
RANAP
RANAP
2. ALCAP setup
3. RADIO LINK SETUP REQUEST
NBAP
NBAP
4. RADIO LINK SETUP RESPONSE
NBAP
NBAP
RRC
7. RADIO BEARER SETUP COMPLETE
RRC
RRC
8. RAB ASSIGNMENT RESPONSE
RANAP
53
RANAP
Upon receiving the RAB establishment request, the SRNC maps the QoS
parameters of the RAB to AAL2 link feature parameters and radio resource feature
parameters. The ALCAP of Iu interface initiates the user plane transport bearer
establishment process according to the AAL2 link feature parameters (For the PS
domain, this step does not exist).
3.
The SRNC starts the radio link establishment process on Iub interface and sends a
RADIO LINK SETUP REQUEST message to the controlled NodeB to request the
NodeB to assign the specific radio link resources required for the RRC connection.
4.
The RNC establishes the Iub interface user plane transport bearer through ALCAP
The SRNC sends a RADIO BEARER SETUP message of the RRC protocol to the
UE.
7.
After executing radio bearer setup, the UE sends a RADIO BEARER SETUP
Upon receiving the RADIO BEARER SETUP COMPLETE message, the SRNC
4.6.3 CCH-CCH
When a RRC connection is established on a CCH, the RNC can continue to establish
the assigned RAB on a CCH according to the QoS parameters in the RAB assignment
message.
54
NodeB
UE
CN
SRNC
1. RAB ASSIGNMENT REQUEST
RANAP
RANAP
2.ALCAP setup
RRC
RRC
4.RADIO BEARER SETUP COMPLETE
RRC
5. RAB ASSIGNMENT RESPONSE
RANAP
RANAP
After the SRNC receives the RAB setup request, the SRNC maps the RAB QoS
parameter as the AAL2 link feature parameter and the radio resource feature parameter.
According to the AAL2 link feature parmameter, the Iu interface ALCAP enables the
transfer bearer setup process of the Iu interface user side.
3.
The SRNC sends the UE the RADIO BEARER SETUP message of the RRC
protocol.
4.
After the UE implements the radio bearer setup, the UE sends the SRNC the
After the SRNC receives the information that the radio bearer has implemented
the setup, the SRNC sends the CN the RAB ASSIGNMENT RESPONSE message. The
RAB setup process is finished.
55
If multiple RABs are established in CS domain, the CN initiates the RAB release
flow only for the RAB that needs to be released, without releasing the Iu signaling
connection.
2.
If only one RAB is established in PS domain, the CN first initiates the RAB
release flow for the RAB. When the release is complete, the CN sends an IU
RELEASE COMMAND message before releasing the Iu signaling connection on
Iu-PS interface. When the service release is complete, the SRNC determines
whether the RRC connection corresponds to any Iu signaling connection (CS
domain). If not, the RRC connection release process is initiated.
If multiple RABs are established in PS domain, the CN initiates the RAB release
57
flow only for the RAB that needs to be released, without releasing the Iu signaling
connection.
RNC
CN
IU RELEASE REQUEST
58
RNC
CN
1.IU RELEASE COMMAND
2.IU RELEASE COMPLETE
1.
the signaling connection release process. The message contains the reason for releasing
the signaling connection, for example, "Successful Relocation", "Normal Release",
"Release due to the UTRAN Generated Reason", "Relocation Cancelled", and "No
Remaining RAB". After sending the message, the CN no longer sends any connectionoriented RNAP message on this connection.
2.
Upon receiving the message, the RNC clears the related resources in the UTRAN.
The RNC sends an IU RELEASE COMPLETE message to the CN. The Iu connection
release process is complete.
DCH-DCH: Before the RAB is released, an RRC connection uses the DCH. After
CCH-CCH: Before the RAB is released, an RRC connection uses the CCH. After
DCH-CCH: Before the RAB is released, an RRC connection uses the DCH. After
2.
The RAB release flow of the DCH-DCH synchronous reconfiguration of radio links is
described
NodeB
Serving RNS
UE
Serving
RNC
RANAP
CN
NBAP
RRC
RRC
Apply new
transport format set
DCCH
RRC
RRC
RAB release flow. The message indicates the ID of the RAB to be released.
2.
the NodeB to request the NodeB to prepare for the releasing of the DCH carrying the
RAB.
3.
the SRNC to notify the SRNC that the release preparations are complete.
4.
The SRNC sends a RADIO BEARER RELEASE message to the UE to start the
the NodeB.
6.
the UE.
7.
8.
The SRNC uses ALCAP. In case of AAL2 bearer, the SRNC sends an AAL2
release message to start releasing the Iu data transport bearer between the SRNC and
CN (This step is not needed for the PS domain).
9.
The SRNC sends a RANAP RAB ASSIGNMENT RESPONSE to the CN. The
RNC
CN
RAB RELEASE REQUEST
61
NodeB
Serving RNS
UE
Serving
RNC
RANAP
1 IU RELEASE COMMAND
CN
RANAP
RRC
RRC
Apply new
transport format set
DCCH
RRC
RRC
9. IU RELEASE COMPLETE
RANAP
RANAP
1.
2.
the NodeB to request the NodeB to prepare for the releasing of the DCH carrying the
RAB.
3.
the SRNC to notify the SRNC that the release preparations are complete.
4.
The SRNC sends a RADIO BEARER RELEASE message to the UE to start the
the NodeB.
6.
the UE.
7.
8.
The SRNC uses ALCAP. In case of AAL2 bearer, the SRNC sends an AAL2
release message to start releasing the Iu data transport bearer between the SRNC and
CN.
62
9.
63
UE
SRNC
NodeB
1.RRC CONNECTION RELEASE
RRC
RRC
RRC
3. RADIO LINK DELETION REQUEST
NBAP
NBAP
4. RADIO LINK DELETION RESPONSE
NBAP
NBAP
5.ALCAP Release
the DCCH. The SRNC may sends the message for several times to ensure that the UE
receives the message.
2.
SRNC.
3.
When the resources in the NodeB are deleted, NodeB returns a RADIO LINK
The RNC uses ALCAP to initiate the releasing of the user plane transport bearer
64
UE
NodeB
SRNC
RRC
The SRNC sends an RRC CONNECTION RELEASE message through the CCCH to
the UE to initiate the RRC connection release flow, and the UE releases the resources.
When an RRC connection established on the common channel is released, no RRC
CONNECTION RELEASE COMPLETE message is sent. In addition, because cell
common resources are used, only the UE needs to be released directly and there is no
need to release NodeB resources and data transport bearer.
Description
The UTRAN may send the RRC CONNECTION RELEASE message for several times
to ensure that the UE receives the message correctly. The RRC SN values of these
messages are the same. The number of message retransfers and transfer interval are
controlled by the network.
65