03-Chapter 3 Cell Related Procedure Analysis PDF

Protocols and Signalling Analysis
HUAWEI UMTS Radio Access Network Table of Contents
Table of Contents
Chapter 3 Cell Related Procedure Analysis ............................................................................... 3-1

3.1 Overview ............................................................................................................................ 3-1
3.2 Procedures Involved in Cell Setup..................................................................................... 3-1
3.2.1 Resource Status Indication ..................................................................................... 3-1
3.2.2 Resource Audit........................................................................................................ 3-2
3.2.3 Cell Setup................................................................................................................ 3-3
3.2.4 Common Transport Channel Setup ........................................................................ 3-4
3.2.5 Iub Interface User Plane Setup ............................................................................... 3-4
3.2.6 System Information Update..................................................................................... 3-5
3.2.7 Common Measurement Initiation ............................................................................ 3-5
3.2.8 Cell Reconfiguration ................................................................................................ 3-6
3.2.9 Cell Deletion ............................................................................................................ 3-7
3.2.10 Resource Status Indication Message ................................................................... 3-8
3.2.11 Audit Response Message ................................................................................... 3-12
3.2.12 Cell Setup Request Message.............................................................................. 3-16
3.2.13 Common Transport Channel Setup Request Message ...................................... 3-20
3.2.14 System Information Update Request Message .................................................. 3-26
3.3 A Cell Setup Example...................................................................................................... 3-28
Huawei Technologies Proprietary
i
HUAWEI UMTS Radio Access Network Chapter 3 Cell Related Procedure Analysis
Chapter 3 Cell Related Procedure Analysis
3.1 Overview
Successful cell setup is prerequisite to normal communication of the WCDMA system.

The BSC6800 can implement cell setup in two ways:
z Cell setup via O&M system
This procedure is directly initiated by an RNC and involves such procedures as
cell setup, common transport channel setup, Iub interface data transport bearer
setup, system information update, common measurement initiation, and so on.
z Cell setup triggered by resource audit response from NodeB
The RNC initiates a resource audit procedure towards a NodeB. The NodeB
sends an audit response to the RNC. Then, the RNC initiates a cell setup
procedure. The steps thereafter are similar to those involved in the cell setup
through the O&M system.
This chapter introduces the procedures involved in cell setup and a cell setup
example.
3.2 Procedures Involved in Cell Setup
3.2.1 Resource Status Indication
NodeB CRNC
RESOURCE STATUS INDICATION
Figure 3-1 Resource status indication procedure
The NodeB uses a resource status indication to report its physical resources to the
RNC. In the following cases, the NodeB triggers the resource status indication
procedure:
z When a local cell is added to the NodeB, that is, it becomes existent
z When a local cell is deleted form the NodeB, that is, it becomes nonexistent.
3-1
z When a local cell changes in its capability at the NodeB

z When a cell changes in its capability and/or its resource operational state at the
NodeB
z When common physical channels and/or common transport channels change in
their capabilities at the NodeB
z When a communication control port changes in its resource operational state at
the NodeB
z When a local cell group changes its resource capability at the NodeB
The NodeB initiates a RESOURCE STATUS INDICATION message to the CRNC in
each of the above cases, as shown in Figure 3-1. This message may contain the
trigger cause and the associated logical resource information.
3.2.2 Resource Audit
The resource audit procedure is executed by the CRNC to audit the configuration and
status of the logical resources in the NodeB. A complete audit of a NodeB is
performed by one or more audit procedures and each procedure carries an audit
sequence number. The audit may cause the CRNC to know the logical resources of
the NodeB and re-synchronize its resources with those of the NodeB.
The procedure is initiated with an AUDIT REQUEST message sent from the CRNC to
the NodeB, as shown in Figure 3-2.
z If the [Start of Audit Sequence] information element (IE) in the AUDIT REQUEST
message is set to “start of audit sequence”, a new audit sequence is started, any
ongoing audit sequence shall be aborted, and the NodeB shall provide (part of
the) audit information.
z If the [Start of Audit Sequence] IE is set to ”not start of audit sequence”, the
NodeB shall provide (part of) the remaining audit information not already provided
during this audit sequence.
NodeB CRNC
AUDIT REQUEST
AUDIT RESPONSE
Figure 3-2 Resource audit procedure
The NodeB responds to the resource audit request of the RNC by an AUDIT
RESPONSE message. The AUDIT RESPONSE message includes information about
physical common channel of logical cell, CCP, local cell, and local group cell. Where,
3-2
the local cell and the local cell group information are the abstraction of the NodeB’s
physical resources. In this way, the RNC can distribute the logical resources of the cell
according to the abstract data.
z If the AUDIT RESPONSE message completes the audit sequence, the NodeB
shall set the [End of Audit Sequence Indicator] IE in the AUDIT RESPONSE
message to “End of Audit Sequence”.
z If not all audit information is provided in the AUDIT RESPONSE message, the
NodeB shall set the [End of Audit Sequence Indicator] IE in the AUDIT
RESPONSE message to “Not End of Audit Sequence”.
3.2.3 Cell Setup
NodeB CRNC
CELL SETUP REQUEST
CELL SETUP RESPONSE
Figure 3-3 Cell setup procedure
After receiving the AUDIT RESPONSE message from the NodeB, the CRNC sends a
CELL SETUP REQUEST message to the NodeB if the conditions of cell setup are
satisfied. The NodeB shall set up a new cell according to the parameters included in
that message, as shown in Figure 3-3.
z If the CELL SETUP REQUEST message includes one or more [Secondary
CPICH Information] IEs, the NodeB shall configure and activate the Secondary
CPICHs (SCPICHs) in the cell according to received configuration data.
z The [Maximum Transmission Power] IE value shall be stored in the NodeB and at
any time, the total maximum output power in the cell shall not be greater than this
value.
z If the CELL SETUP REQUEST message includes one or more [Closed Loop
Timing Adjustment Mode] IEs, the value(s) shall be stored in the NodeB and
applied when closed loop feed-back mode diversity is used on DPCH.
When the cell is successfully configured, the NodeB shall store the [Configuration
Generation ID] IE value and send a CELL SETUP RESPONSE message as a
response.
When the cell is successfully configured, there shall be CPICH(s), Primary SCH
(PSCH), Secondary SCH (SSCH), Primary CCPCH (PCCPCH) and BCH. The cell and
3-3
the channels are set to Enabled state. When the cell is not successfully configured, the
CELL SETUP FAILURE message shall be sent to the CRNC.
3.2.4 Common Transport Channel Setup
The common transport channel setup procedure is used for establishing the following
channels: Secondary CCPCH (SCCPCH), FACH, PCH, PICH, PRACH, RACH, and
AICH.
NodeB CRNC
COMMON TRANSPORT CHANNEL SETUP

REQUEST
COMMON TRANSPORT CHANNEL SETUP

RESPONSE
Figure 3-4 Common transport channel setup procedure
The procedure is initiated with a COMMON TRANSPORT CHANNEL SETUP

REQUEST message sent from the CRNC to the NodeB. One message can configure
only one of the following combinations:
z One SCCPCH, and FACHs, PCH and PICH related to that SCCPCH
z One PRACH, one RACH and one AICH related to that PRACH
If successfully setting up the common transport channel, the NodeB responds with a
COMMON TRANSPORT CHANNEL SETUP RESPONSE message to the CRNC. If
failing to set up the common transport channel, the NodeB responds with a COMMON
TRANSPORT CHANNEL SETUP FAILURE message.
Note:
The transport channel synchronization procedure in user plane follows the successful
establishment of downlink common transport channel. After the PCH is established
successfully, the node synchronization procedure in user plane might follow.
3.2.5 Iub Interface User Plane Setup
The CRNC sends an ALCAP message Q.AAL2 ESTABLISH REQUEST to the NodeB,
requesting for Iub interface user plane establishment. After a successful establishment,
3-4
the NodeB responds with an ALCAP message Q.AAL2 ESTABLISH CONFIRM to the
CRNC, indicating the Iub interface user plane is established.
3.2.6 System Information Update
NodeB CRNC
SYSTEM INFORMATION UPDATE

REQUEST
SYSTEM INFORMATION UPDATE

RESPONSE
Figure 3-5 System information update procedure
After all common transport channels are set up, the CRNC sends a SYSTEM
INFORMATION UPDATE REQUEST message to the NodeB, as shown in Figure 3-5.
That message includes the system information broadcast in segments on the BCCH
and the scheduling information of each segment.
If the NodeB successfully updates the system information on the broadcast channel
according to the parameters in the SYSTEM INFORMATION UPDATE REQUEST
message, it responds to the CRNC with a SYSTEM INFORMATION UPDATE
RESPONSE message. Otherwise, the NodeB responds with a SYSTEM
INFORMATION UPDATE FAILURE message.
3.2.7 Common Measurement Initiation
NodeB CRNC
COMMON MEASUREMENT INITIA TION

REQUEST
COMMON MEASUREMENT INITIATION

RESPONSE
Figure 3-6 Common measurement initiation procedure
The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST

message sent from the CRNC to the NodeB using the NodeB control port, as shown in
Figure 3-6. That message includes the measurement object type (such as cell and
RACH), common measurement type (such as Tx carrier power and Rx total wide band
3-5
power), and report characteristics (such as On-Demand report, periodic report, and
event report). Upon receipt of the message, the NodeB initiates the requested
measurement according to the parameters in the request.
If the NodeB is able to initiate the measurement requested by the CRNC, it responds
with a COMMON MEASUREMENT INITIATION RESPONSE message sent over the
NodeB control port. If the initiation fails, it responds with a COMMON
MEASUREMENT INITIATION FAILURE message.
3.2.8 Cell Reconfiguration
The cell reconfiguration procedure is used for an RNC to reconfigure a cell in a NodeB
when the cell parameters need to be modified, as illustrated in Figure 3-7.
NodeB CRNC
CELL RECONFIGURATION REQUEST
CELL RECONFIGURATION RESPONSE
Figure 3-7 Cell reconfiguration procedure
The CRNC sends a CELL RECONFIGURATION REQUEST message to the NodeB.

Upon reception, the NodeB reconfigures the cell according to the parameter included
in the message.
z If the CELL RECONFIGURATION REQUEST message includes the [Primary
SCH Information] IE, the NodeB reconfigures Primary SCH power in the cell
according to the [Primary SCH Power] IE value.
z If the CELL RECONFIGURATION REQUEST message includes the [Secondary
SCH Information] IE, the NodeB reconfigures Secondary SCH power in the cell
according to the [Secondary SCH Power] IE value.
CPICH Information] IE, the NodeB reconfigures Primary CPICH power in the cell
according to the [Primary CPICH Power] IE value. The NodeB adjusts all the
transmitted power levels relative to the Primary CPICH power according to the
new value.
z If the CELL RECONFIGURATION REQUEST message includes one or more
[Secondary CPICH Information] IEs, the NodeB reconfigures the power for each
Secondary CPICH in the cell according to their [Secondary CPICH Power] IE
value.
3-6

CCPCH Information] IE, the NodeB reconfigures BCH power in the cell according
to the [BCH Power] IE value.
z If the CELL RECONFIGURATION REQUEST message includes the [Maximum
Transmission Power] IE, the value shall be stored in the NodeB and, at any time,
the total maximum output power in the cell shall not be greater than this value.
If reconfiguring the cell successfully, the NodeB stores the new [Configuration
Generation ID] IE value and sends a CELL RECONFIGURATION RESPONSE
message as a response. If failing to reconfigure the cell, the NodeB sends a CELL
RECONFIGURATION FAILURE message.
If the CELL RECONFIGURATION REQUEST message includes the [Synchronization

Configuration] IE, the NodeB reconfigures the indicated parameters in the cell
according to the IE value. When the parameters in the [Synchronization Configuration]
IE affect the thresholds applied to a radio link set, the NodeB immediately starts the
new thresholds.
3.2.9 Cell Deletion
The cell deletion procedure is used to delete a cell from a NodeB, as illustrated in
Figure 3-8.
NodeB CRNC
CELL DELETION REQUEST
CELL DELETION RESPONSE
Figure 3-8 Cell deletion procedure
1) The CRNC sends a CELL DELETION REQUEST message to the NodeB. Upon
reception, the NodeB deletes the cell and any remaining common and dedicated
channels within the cell. The states of the deleted cell and common channels
shall be set to Not Existing. The NodeB deletes all radio links and all NodeB
communication contexts within the cell. The NodeB also initiates releasing of the
corresponding transport bearers in the user plane.
2) After deleting the cell, the NodeB returns a CELL DELETION RESPONSE
message as a response.
3-7
3.2.10 Resource Status Indication Message
I. Message Structure
IE/Group name Presence Semantics description
Message Discriminator M –
Message Type M –
Transaction ID M –
Indication Type M –
CHOICE Indication Type M –
>No Failure –
>>Local Cell Information –
>>>Local Cell ID M –
>>>Add/Delete Indicator M –
>>>DL or Global Capacity Credit C-add –
>>>UL Capacity Credit O –
>>>Common Channels Capacity C-add –

Consumption Law
>>>Dedicated Channels C-add –

Capacity Consumption Law
>>>Maximum DL Power C-add –

Capability
>>>Minimum Spreading Factor C-add –
>>>Minimum DL Power C-add –

Capability
>>>Local Cell Group ID O –
>>Local Cell Group –

Information
>>>Local Cell Group ID M –
>>>DL or Global Capacity Credit M –
3-8
>>>Common Channels Capacity M –

Consumption Law
>>>Dedicated Channels M –
>Service Impacting –
>>Local Cell Information –
>>>Local Cell ID M –
>>>DL or Global Capacity Credit O –
>>>Common Channels Capacity O –

Consumption Law
>>>Dedicated Channels O –
>>>Maximum DL Power O –
Capability
>>>Minimum Spreading Factor O –
>>>Minimum DL Power O –
Capability
>>Local Cell Group –

Information
>>>Local Cell Group ID M –
>>>DL or Global Capacity Credit O –
>>>Common Channels Capacity O –

Consumption Law
>>>Dedicated Channels O –
>>Communication Control –
Port Information
>>>Communication Control Port M –
3-9

ID
>>>Resource Operational State M –
>>>Availability Status M –
>>Cell Information –
>>>C-ID M –
>>>Resource Operational State O –
>>>Availability Status O –
>>>Primary SCH Information O –
>>>Secondary SCH Information O –
>>>Primary CPICH Information O –
>>>Secondary CPICH –
Information
>>>>Secondary CPICH M –
Individual Information
>>>Primary CCPCH Information O –
>>>BCH Information O –
>>>Secondary CCPCH –
Information
>>>>Secondary CCPCH M –
Individual Information
>>>PCH Information O –
>>>PICH Information O –
>>>FACH Information –
>>>>FACH Individual M –
Information
>>>PRACH Information –
>>>>PRACH Individual M –
Information
3-10
>>>RACH Information –
>>>>RACH Individual M –
Information
>>>AICH Information –
>>>>AICH Individual Information M –
>>>PCPCH Information –
>>>>PCPCH Individual M –
Information
>>>CPCH Information –
>>>>CPCH Individual M –
Information
>>>AP-AICH Information –
>>>>AP-AICH Individual M –
Information
>>>CD/CA-ICH Information –
>>>>CD/CA-ICH Individual M –
Information
>>>SCH Information O –
Cause O –
3-11
II. Example
3.2.11 Audit Response Message
3-12
Message Type M –
End Of Audit Sequence Indicator M –
Cell Information –
>C-ID M –
>Configuration Generation ID M –
>Resource Operational State M –
>Availability Status M –
>Local Cell ID M –
>Primary SCH Information O –
>Secondary SCH Information O –
>Primary CPICH Information O –
>Secondary CPICH Information –
>>Secondary CPICH Individual M –

Information
>Primary CCPCH Information O –
>BCH Information O –
>Secondary CCPCH Information –
>>Secondary CCPCH Individual M –

Information
>PCH Information O –
>PICH Information O –
>FACH Information –
>>FACH Individual Information M –
>PRACH Information –
>>PRACH Individual Information M –
3-13
>RACH Information –
>>RACH Individual Information M –
>AICH Information –
>>AICH Individual Information M –
>PCPCH Information –
>>PCPCH Individual Information M –
>CPCH Information –
>>CPCH Individual Information M –
>AP-AICH Information –
>>AP-AICH Individual Information M –
>CD/CA-ICH Information –
>>CD/CA-ICH Individual M –
Information
>SCH Information O –
Communication Control Port –

Information
>Communication Control Port ID M –
>Resource Operational State M –
>Availability Status M –
Local Cell Information –
>Local Cell ID M –
>DL or Global Capacity Credit M –
>UL Capacity Credit O –
>Common Channels Capacity M –

Consumption Law
>Dedicated Channels Capacity M –

Consumption Law
>Maximum DL Power Capability O –
3-14
>Minimum Spreading Factor O –
>Minimum DL Power Capability O –
>Local Cell Group ID O –
Local Cell Group Information –
>Local Cell Group ID M –
>DL or Global Capacity Credit M –
>UL Capacity Credit O –
>Common Channels Capacity M –

Consumption Law
>Dedicated Channels Capacity M –

Consumption Law
Criticality Diagnostics O –
3-15
II. Example
3.2.12 Cell Setup Request Message
3-16
Message Type M –
Local Cell ID M –
C-ID M Cell ID
Configuration Generation ID M –
T_Cell M Offset of T_cell against BFN
UARFCN M –
UARFCN M –
Maximum Transmission Power M Maximum transmission

power
Closed Loop Timing Adjustment O –

Mode
Primary Scrambling Code M Primary scrambling code of

cell
Synchronization Configuration –
>N_INSYNC_IND M –
>N_OUTSYNC_IND M –
>T_RLFAILURE M –
DL TPC pattern 01 count M –
Primary SCH Information –
>Common Physical Channel ID M –
>Primary SCH Power M –
>TSTD Indicator M –
Secondary SCH Information –
>Secondary SCH power M –
3-17
>TSTD Indicator M –
Primary CPICH Information –
>Primary CPICH power M –
>Transmit Diversity Indicator M –
Secondary CPICH Information –
>DL Scrambling code M –
>FDD DL Channelisation Code M –

Number
>Secondary CPICH Power M –
>Transmit Diversity Indicator M –
Primary CCPCH Information –
>BCH Information –
>>Common Transport Channel ID M –
>>BCH Power M PCPICH transmission power
>STTD Indicator M –
Limited power increase –

information
>Power_Raise_Limit M –
>DL_power_averaging_window_siz M –
e
3-18
II. Example
3-19
3.2.13 Common Transport Channel Setup Request Message
Message Discriminator M
Message Type M
Transaction ID M
C-ID M Cell ID
Configuration Generation ID M
CHOICE common physical channel M

to be configured
>Secondary CCPCH Situation when the

SCCPCH established
>>Secondary CCPCH
>>>Common Physical Channel ID M
>>>FDD SCCPCH Offset M SCCPCH timing offset
>>>DL Scrambling Code C-PCH
>>>FDD DL Channelisation Code M

Number
>>>TFCS M –
>>>Secondary CCPCH Slot M –

Format
>>>TFCI Presence C– –
SlotFormat
>>>Multiplexing Position M –
>>>Power Offset Information Power offset
>>>>PO1 M TFCI bit power offset
>>>>PO3 M Preamble bit power offset
>>>STTD Indicator M –
3-20
>>>FACH Parameters –
>>>>Common Transport Channel M –

ID
>>>>Transport Format Set M –
>>>>ToAWS M –
>>>>ToAWE M –
>>>>Max FACH Power M –
>>>PCH Parameters

ID
>>>>Transport Format Set M –.
>>>>ToAWS M –
>>>>ToAWE M –.
>>>>PCH Power M –
>>>>PICH Parameters
>>>>>Common Physical Channel M –

ID
>>>>>FDD DL Channelisation M –.
Code Number
>>>>>PICH Power M –
>>>>>PICH Mode M –.
>>>>>STTD Indicator M –
>PRACH Situation when PRACH

established
>>PRACH
>>>Common Physical Channel ID M
>>>Scrambling Code Number M
>>>TFCS M –.
3-21
>>>Preamble Signatures M
>>>Allowed Slot Format

Information
>>>>RACH Slot Format M
>>>RACH Sub Channel Numbers M
>>>Puncture Limit M
>>>Preamble Threshold M
>>>RACH Parameters –

ID
>>>>Transport Format Set M –
>>AICH Parameters –
>>>Common Physical Channel ID M –
>>>AICH Transmission Timing M –
>>>FDD DL Channelisation Code M –

Number
>>>AICH Power M –
>>>STTD Indicator M –
>PCPCHes Situation when PCPCH

established
>>CPCH Parameters –
>>>Common Transport Channel ID M –
>>>Transport Format Set M –
>>>AP Preamble Scrambling Code M –
>>>CD Preamble Scrambling Code M –
>>>TFCS M –
>>>CD Signatures O –
>>>CD Sub Channel Numbers –
3-22
>>>Puncture Limit M –
>>>CPCH UL DPCCH Slot Format M –
>>>UL SIR M –
>>>Initial DL transmission Power M –
>>>Maximum DL Power M –
>>>Minimum DL Power M –
>>>PO2 M –
>>>PO3 M –
>>>FDD TPC DL Step Size M –
>>>N_Start_Message M –
>>>N_EOT M –
>>>Channel Assignment Indication M –
>>>CPCH Allowed Total Rate M –
>>>PCPCH Channel Information –
>>>>Common Physical Channel ID M –
>>>>CPCH Scrambling Code M –

Number
>>>>DL Scrambling Code M –
>>>>FDD DL Channelisation Code M –

Number
>>>>PCP Length M –
>>>>UCSM Information C-NCA –
>>>>>Min UL Channelisation Code M –

Length
>>>>>NF_max M –
>>>>>Channel Request –
Parameters
>>>>>>AP Preamble Signature M –
3-23
>>>>>AP Sub Channel Number O –
>>>VCAM Mapping Information C-CA –
>>>>Min UL Channelisation Code M –

Length
>>>>NF_max M –
>>>>Max Number of PCPCHes M –
>>>>SF Request Parameters –
>>>>>AP Preamble Signature M –
>>>>>AP Sub Channel Number O –
>>>AP-AICH Parameters –

Number
>>>>AP-AICH Power M –
>>>>CSICH Power M –
>>>>STTD Indicator M –
>>>CD/CA-ICH Parameters –

Number
>>>>CD/CA-ICH Power M –
>>>>STTD Indicator M –
3-24
II. Example
3-25
3.2.14 System Information Update Request Message
Message Type M –
C-ID M –
BCCH Modification Time O –
MIB/SB/SIB Information –
>IB Type M –
>IB OC ID M –
>CHOICE IB DeletionIndicator M –
>>NoDeletion –
>>>SIB Originator C-SIB –
>>>IB SG REP O –
>>>Segment Information –
>>>>IB SG POS O –
>>>>Segment type C– –
CRNCOriginati
on
>>>>IB SG DATA C– –
CRNCOriginati
on
>>Deletion –
3-26
II. Example
3-27
3.3 A Cell Setup Example
This section describes an example of cell setup triggered by the resource status
indication procedure, as illustrated in Figure 3-9.
In this example, two SCCPCHs and one PRACH are set up in the cell. One SCCPCH
bears two FACHs and the other SCCPCH bears two FACHs and one PCH. The
PRACH bears one RACH.
3-28
Node B RNC
1.NCP:RESOURCE STATUS INDICATION
2. NCP: AUDIT REQUEST
3.NCP: AUDIT RESPONSE
4.NCP: CELL SETUP REQUEST
5.NCP: CELL SETUP RESPONSE
6.NCP: COMMON TRANSPORT CHANNEL SETUP REQUEST
7.NCP: COMMON TRANSPORT CHANNEL SETUP RESPONSE
8.ALCAP:QAAL2 ESTABLISH REQUEST
9.ALCAP:QAAL2 ESTABLISH CONFIRM
10.NCP: COMMON TRANSPORT CHANNEL SETUP REQUEST
11.NCP: COMMON TRANSPORT CHANNEL SETUP RESPONSE
18.NCP:COMMON TRANSPORT CHANNEL SETUP REQUEST
19.NCP:COMMON TRANSPORT CHANNEL SETUP RESPONSE
20. ALCAP: QAAL2 ESTABLISH REQUEST
21. ALCAP: QAAL2 ESTABLISH CONFIRM
22. ALCAP: QAAL2 ESTABLISH REQUEST
23. ALCAP: QAAL2 ESTABLISH CONFIRM
3-29
NodeB RNC
24. NCP: SYSTEM INFORMATION UPDATE REQUEST
25 NCP: SYSTEM INFORMATION UPDATE RESPONSE
26. NCP: COMM ON M EASUREM ENT INITIATION REQUEST
27. NCP: COMM ON M EASUREM ENT INITIATION RESPONSE
32. NCP: M EASUREM ENT REPORT
Figure 3-9 Cell setup procedure
Each step is explained as follows:

1) The NodeB sends a RESOURCE STATUS INDICATION message to the CRNC.
The message may contain the trigger cause and the associated logical resource
information.
2) The CRNC sends an AUDIT REQUEST message to the NodeB to initiate the
resource audit procedure.
3) The CRNC performs an audit of the configuration and status of the logical
resources in the NodeB. It may also re-synchronize its resources with those of the
NodeB. After the audit, the NodeB returns an AUDIT RESPONSE message to the
CRNC.
4) The CRNC sends a CELL SETUP REQUEST message to the NodeB to initiate a
cell setup procedure.
5) The NodeB reserves the necessary resources and configures a new cell
according to the parameters in the CELL SETUP REQUEST message. After the
cell setup, the NodeB returns a CELL SETUP RESPONSE message to the
CRNC, confirming that the cell is successfully set up.
3-30
6) The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST

message to the NodeB, requesting the NodeB to set up a PRACH.
7) The NodeB returns a COMMON TRANSPORT CHANNEL SETUP RESPONSE
message, confirming that the common transport channel is successfully set up.
8) The CRNC sends a QAAL2 ESTABLISH REQUEST message to the NodeB
using the ALCAP protocol to initiate an Iub interface data transport bearer
establishment procedure. The message contains an AAL2 binding identity to bind
the Iub interface data transport bearer to the RACH.
9) The NodeB returns a QAAL2 ESTABLISH CONFIRM message to the CRNC as a
response.
10) The CRNC sends a COMMON TRANSPORT CHANNEL SETUP REQUEST
message to the NodeB, requesting the NodeB to set up an SCCPCH. Here, the
SCCPCH bears two FACHs and one PCH.
message, confirming that the common transport channel is successfully set up.
12) 14) 16) The CRNC sends a QAAL2 ESTABLISH REQUEST message to the
NodeB to initiate an Iub interface data transport bearer establishment procedure.
This procedure is implemented three times to set up three Iub interface data
transport bearers. Each QAAL2 ESTABLISH REQUEST message contains an
AAL2 binding identity to bind the corresponding Iub interface data transport
bearer to the two FACHs and one PCH.
13) 15) 17) The NodeB returns a QAAL2 ESTABLISH CONFIRM message to the
CRNC as a response. Corresponding to the three QAAL2 ESTABLISH
REQUEST messages, the NodeB returns three QAAL2 ESTABLISH CONFIRM
messages to the CRNC.
18) The CRNC sends a COMMON TRANSPORT CHANNEL SEUTP REQUEST
message to the NodeB, requesting the NodeB to set up an SCCPCH. This
SCCPCH bears two FACHs.
message, confirming the successful setup of the common transport channel.
20) 22) The CRNC sends an ALCAP message QAAL2 ESTABLISH REQUEST to the
NodeB to initiate an Iub interface data transport bearer establishment procedure.
This procedure is implemented two times to set up two Iub interface data
transport bearers. Each QAAL2 ESTABLISH REQUEST message contains an
AAL2 binding identity to bind the corresponding Iub interface data transport
bearer to the two FACHs.
21) 23) The NodeB returns a QAAL2 ESTABLISH CONFIRM message to the CRNC
as a response. Corresponding to the two QAAL2 ESTABLISH REQUEST
messages, the NodeB returns two QAAL2 ESTABLISH CONFIRM messages to
the CRNC.
24) The CRNC sends a SYSTEM INFORMATION UPDATE REQUEST message to
the NodeB.
3-31
25) The NodeB returns a SYSTEM INFORMATION UPDATE RESPONSE message,

confirming the successful update of the system information.
26) 28) 30) The RNC sends a COMMON MEASUREMENT INITIATION REQUEST
message to the NodeB. The message is sent three times, requesting for three
types of common measurements: Tx carrier power measurement in the form of
periodic report, RTWP measurement in the form of periodic report and Tx carrier
power measurement in the form of event-E report.
27) 29) 31) Corresponding to the three COMMON MEASUREMENT INITIATION
REQUEST messages, the NodeB returns three COMMON MEASUREMENT
INITIATION RESPONSE messages, confirming the successful initiation of the
common measurement.
32) According to the RNC request, the NodeB periodically sends the Tx carrier power
MEASUREMENT REPORT.
33) According to the RNC request, the NodeB periodically sends the RTWP
MEASUREMENT REPORT.
34) According the RNC request, the NodeB sends the Tx carrier power
MEASUREMENT REPORT only when the event E occurs.
So far, the setup of the cell has completed and the UEs can access the network.
3-32

03-Chapter 3 Cell Related Procedure Analysis PDF

Uploaded by

Copyright:

Available Formats

You might also like

03-Chapter 3 Cell Related Procedure Analysis PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

03-Chapter 3 Cell Related Procedure Analysis PDF

Uploaded by

Copyright:

Available Formats

Protocols and Signalling Analysis

HUAWEI UMTS Radio Access Network Table of Contents

Chapter 3 Cell Related Procedure Analysis ............................................................................... 3-1

Huawei Technologies Proprietary

Chapter 3 Cell Related Procedure Analysis

Successful cell setup is prerequisite to normal communication of the WCDMA system.

3.2 Procedures Involved in Cell Setup

3.2.1 Resource Status Indication

RESOURCE STATUS INDICATION

Figure 3-1 Resource status indication procedure

Huawei Technologies Proprietary

z When a local cell changes in its capability at the NodeB

3.2.2 Resource Audit

Figure 3-2 Resource audit procedure

Huawei Technologies Proprietary

3.2.3 Cell Setup

CELL SETUP REQUEST

CELL SETUP RESPONSE

Figure 3-3 Cell setup procedure

Huawei Technologies Proprietary

3.2.4 Common Transport Channel Setup

COMMON TRANSPORT CHANNEL SETUP

COMMON TRANSPORT CHANNEL SETUP

Figure 3-4 Common transport channel setup procedure

The procedure is initiated with a COMMON TRANSPORT CHANNEL SETUP

3.2.5 Iub Interface User Plane Setup

Huawei Technologies Proprietary

3.2.6 System Information Update

SYSTEM INFORMATION UPDATE

SYSTEM INFORMATION UPDATE

Figure 3-5 System information update procedure

3.2.7 Common Measurement Initiation

COMMON MEASUREMENT INITIA TION

COMMON MEASUREMENT INITIATION

Figure 3-6 Common measurement initiation procedure

The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST

Huawei Technologies Proprietary

3.2.8 Cell Reconfiguration

CELL RECONFIGURATION REQUEST

CELL RECONFIGURATION RESPONSE

Figure 3-7 Cell reconfiguration procedure

The CRNC sends a CELL RECONFIGURATION REQUEST message to the NodeB.

Huawei Technologies Proprietary

z If the CELL RECONFIGURATION REQUEST message includes the [Primary

If the CELL RECONFIGURATION REQUEST message includes the [Synchronization

3.2.9 Cell Deletion

CELL DELETION REQUEST

CELL DELETION RESPONSE

Figure 3-8 Cell deletion procedure

Huawei Technologies Proprietary

3.2.10 Resource Status Indication Message

CHOICE Indication Type M –

>>Local Cell Information –

>>>DL or Global Capacity Credit C-add –

>>>UL Capacity Credit O –

>>>Common Channels Capacity C-add –

>>>Dedicated Channels C-add –