ran documentation guide

8/13/2019 RAN Documentation Guide

1/101

RAN

6.0

System Description

Issue 01

Date 2007-04-20

Part Number

Huawei Technologies Proprietary


2/101

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any

assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright 2007 Huawei Technologies Co., Ltd. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but the statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Proprietary
http://www.huawei.com/http://www.huawei.com/


3/101

Contents

About This Document.....................................................................................................................1

1 Introduction to the RAN System.............................................................................................1-1

1.1 RAN in the UMTS..........................................................................................................................................1-2

1.2 RAN Architecture...........................................................................................................................................1-21.3 RAN External Interfaces.................................................................................................................................1-3

1.4 RAN Internal Interfaces..................................................................................................................................1-4

2 RAN Functions...........................................................................................................................2-1

2.1 User Data Transfer..........................................................................................................................................2-2

2.2 Overall System Access Control.......................................................................................................................2-2

2.2.1 Admission Control.................................................................................................................................2-3

2.2.2 Congestion Control................................................................................................................................2-3

2.2.3 System Information Broadcasting..........................................................................................................2-3

2.3 Radio Channel Ciphering and Deciphering....................................................................................................2-42.4 Mobility Management.....................................................................................................................................2-4

2.4.1 Handover................................................................................................................................................2-4

2.4.2 SRNS Relocation....................................................................................................................................2-5

2.4.3 Paging.....................................................................................................................................................2-5

2.4.4 Positioning..............................................................................................................................................2-5

2.4.5 NASNode Selection..............................................................................................................................2-5

2.4.6 Shared Networks Access Control...........................................................................................................2-6

2.4.7 Hierarchical Cell Structure.....................................................................................................................2-6

2.5 Radio Resource Management and Control......................................................................................................2-6

2.5.1 Radio Environment Monitoring.............................................................................................................2-7

2.5.2 Combining/Splitting Control..................................................................................................................2-7

2.5.3 Connection Setup and Release...............................................................................................................2-8

2.5.4 Allocation and Deallocation of Radio Bearers.......................................................................................2-8

2.5.5 Radio Protocols......................................................................................................................................2-8

2.5.6 RF Power Control...................................................................................................................................2-8

2.5.7 Radio Channel Encoding and Decoding................................................................................................2-9

2.5.8 Initial Access Detection and Handling...................................................................................................2-9

2.5.9 CN Distribution for NAS Messages.......................................................................................................2-9

2.6 Broadcast and Multicast..................................................................................................................................2-9

RAN

System Description Contents

Issue 01 (2007-04-20) Huawei Technologies Proprietary i
http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://00-3%20about%20this%20document.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://00-3%20about%20this%20document.pdf/


4/101

2.6.1 Broadcast and Multicast Messaging.....................................................................................................2-10

2.6.2 Broadcast and Multicast Flow Control.................................................................................................2-10

2.6.3 CBS Status Reporting...........................................................................................................................2-10

3 Introduction to NodeBs.............................................................................................................3-13.1 NodeB Family.................................................................................................................................................3-2

3.1.1 Overview of the BTS3812E...................................................................................................................3-2

3.1.2 Overview of the BTS3812A...................................................................................................................3-3

3.1.3 Overview of the DBS3800.....................................................................................................................3-4

3.1.4 Overview of the iDBS3800....................................................................................................................3-5

3.2 Introduction to the BTS3812E.......................................................................................................................3-5

3.2.1 System Architecture of the BTS3812E .................................................................................................3-5

3.2.2 Software Structure of the BTS3812E/BTS3812ABTS3812AE.............................................................3-7

3.2.3 Logical Structure of the BTS3812E.......................................................................................................3-8

3.2.4 Technical Specifications for the BTS3812E/BTS3812A.......................................................................3-9

3.2.5 Configuration Types of the BTS3812E/BTS3812A..............................................................................3-9

3.3 Introduction to the BTS3812A.....................................................................................................................3-11

3.3.1 Introduction to the BTS3812A.............................................................................................................3-11

3.3.2 Software Structure of the BTS3812E/BTS3812ABTS3812AE...........................................................3-13

3.3.3 Logical Structure of the BTS3812A.....................................................................................................3-14

3.3.4 Technical Specifications for the BTS3812E/BTS3812A.....................................................................3-15

3.3.5 Configuration Types of the BTS3812E/BTS3812A............................................................................3-15

3.4 Introduction to the DBS3800.......................................................................................................................3-17

3.4.1 DBS3800 Family Products...................................................................................................................3-183.4.2 System Architecture of the DBS3800..................................................................................................3-20

3.4.3 Logical Structure of the DBS3800.......................................................................................................3-20

3.4.4 Software Structure of the DBS3800.....................................................................................................3-20

3.4.5 Technical Specifications for the DBS3800..........................................................................................3-22

3.4.6 Configuration Types of the DBS3800..................................................................................................3-22

3.5 Introduction to the iDBS3800.......................................................................................................................3-23

3.5.1 iDBS3800 Family Products..................................................................................................................3-23

3.5.2 System Architecture of the iDBS3800.................................................................................................3-24

3.5.3 Logical Structure of the iDBS3800......................................................................................................3-25

3.5.4 Capacityof the iDBS3800 ...................................................................................................................3-25

3.5.5 Configuration Types of the iDBS3800.................................................................................................3-26

3.6 NodeB OM System.......................................................................................................................................3-29

4 Introduction to the RNC...........................................................................................................4-1

4.1 RNC Physical Structure..................................................................................................................................4-3

4.2 RNC Logical Structure....................................................................................................................................4-4

4.3 RNC Software Structure..................................................................................................................................4-5

4.4 RNC Technical Specifications........................................................................................................................4-6

4.5 RNC Hardware Configuration Types..............................................................................................................4-7

4.6 RNC OM System............................................................................................................................................4-9

Contents

RAN

System Description

ii Huawei Technologies Proprietary Issue 01 (2007-04-20)
http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/http://01-02%20ran%20functions.pdf/


5/101

5 Introduction to RAN OM.........................................................................................................5-1

5.1 RAN OM System............................................................................................................................................5-2

5.2 RAN OM Network Solutions..........................................................................................................................5-2

5.3 Introduction to the M2000...............................................................................................................................5-2

5.3.1 M2000 Centralized Topology Management..........................................................................................5-3

5.3.2 M2000 Centralized Configuration Management....................................................................................5-5

5.3.3 M2000 Centralized Fault Management..................................................................................................5-7

5.3.4 M2000 Centralized Performance Management....................................................................................5-10

5.3.5 M2000 Centralized Security Management...........................................................................................5-12

5.3.6 M2000 Centralized Software Management..........................................................................................5-14

5.3.7 M2000 Signaling Trace Management..................................................................................................5-15

5.3.8 M2000 Device Panel Management......................................................................................................5-15

5.3.9 M2000 Centralized System Management............................................................................................5-15

5.3.10 M2000 Northward Interfaces.............................................................................................................5-17

5.3.11 M2000 Time Management.................................................................................................................5-17

5.3.12 M2000 Customized Report Management..........................................................................................5-18

5.3.13 M2000 Technical Specifications........................................................................................................5-18

RAN

System Description Contents

Issue 01 (2007-04-20) Huawei Technologies Proprietary iii
http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/


6/101


7/101

Figures

Figure 1-1RAN in the UMTS..............................................................................................................................1-2

Figure 1-2RAN architecture................................................................................................................................1-3

Figure 1-3RAN external interfaces.....................................................................................................................1-4

Figure 1-4RAN internal interfaces......................................................................................................................1-4

Figure 3-1Components of the BTS3812E system...............................................................................................3-6

Figure 3-2Software structure of the BTS3812E/BTS3812ABTS3812AE..........................................................3-7

Figure 3-3Logical structure of the BTS3812E....................................................................................................3-9

Figure 3-4Components of the BTS3812A system............................................................................................3-12

Figure 3-5Software structure of the BTS3812E/BTS3812ABTS3812AE........................................................3-13

Figure 3-6Logical structure of the BTS3812A..................................................................................................3-15

Figure 3-7DBS3800 system..............................................................................................................................3-18

Figure 3-8System architecture of the DBS3800................................................................................................3-20

Figure 3-9Software structure of the DBS3800..................................................................................................3-21

Figure 3-10iDBS3800 family products.............................................................................................................3-23Figure 3-11iDBS3800 system architecture.......................................................................................................3-25

Figure 3-12Typical configuration 1..................................................................................................................3-27



Figure 3-15NodeB OM System.........................................................................................................................3-29

Figure 4-1RNC physical structure.......................................................................................................................4-3

Figure 4-2RNC logical structure....................................................................... ..................................................4-4

Figure 4-3FAM software structure......................................................................................................................4-5

Figure 4-4BAM software structure.....................................................................................................................4-6

Figure 4-5LMT software structure......................................................................................................................4-6

Figure 4-6RNC minimum configuration................................................................................................. ............4-7

Figure 4-7RNC maximum configuration.................................................................................................... ........4-8

Figure 4-8RNC OM subsystem........................................................................................... ................................4-9

RAN

System Description Figures

Issue 01 (2007-04-20) Huawei Technologies Proprietary v
http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://01-01%20introduction%20to%20the%20ran%20system.pdf/


8/101


9/101

Tables

Table 3-1Configurations of the BTS3812E.......................................................................................................3-10

Table 3-2Configurations of the BTS3812A......................................................................................................3-10

Table 3-3Configurations of the BTS3812E.......................................................................................................3-16

Table 3-4Configurations of the BTS3812A......................................................................................................3-16

Table 3-5Typical configurations of the DBS3800............................................................ ................................3-22

Table 3-6BBU3806 capacity.............................................................................................................................3-26

Table 3-7RHUB3808 capacity..........................................................................................................................3-26

Table 3-8pRRU3801 capacity...........................................................................................................................3-26

Table 3-9iDBS3800 configuration principles....................................................................................................3-26

Table 4-1RNC hardware......................................................................................................................................4-3

Table 4-2RNC typical configurations..................................................................................................................4-8

Table 5-1Topology object management..............................................................................................................5-3

Table 5-2Resource Management.........................................................................................................................5-6

Table 5-3Performance data management..........................................................................................................5-11Table 5-4M2000 system capacity......................................................................................................................5-18

Table 5-5Number of equivalent NEs of the UMTS NEs...................................................................................5-19

Table 5-6Bandwidth requirements for managing the UMTS NEs (excluding RNCs and NodeBs).................5-19

Table 5-7Bandwidth requirements for managing RNCs and NodeBs (Each NodeB covers three cells.).........5-19

Table 5-8Performance data processing capability of various servers...............................................................5-20

Table 5-9Storage capacity of various servers....................................................................................................5-21

Table 5-10M2000 alarm processing capability.................................................................................................5-21

Table 5-11Number of M2000 clients simultaneously started on the server......................................................5-21

Table 5-12Specifications of different models of M2000 servers......................................................................5-22

Table 5-13Power consumption of all the equipment in the M2000 system......................................................5-22

Table 5-14Reliability specifications for the M2000 system of the single-server configuration.......................5-23

Table 5-15Reliability specifications for the M2000 system of the HA configuration......................................5-24

Table 5-16Climatic requirements for the equipment storage ...........................................................................5-25

Table 5-17Waterproof requirements.................................................................................................................5-25

Table 5-18Storage requirements for physically active materials......................................................................5-26

Table 5-19Storage requirements for chemically active materials.....................................................................5-26

Table 5-20Storage requirements related to mechanical stress...........................................................................5-26

Table 5-21Climatic requirements for transporting the equipment....................................................................5-27

Table 5-22Requirements for physically active materials in the transportation environment............................5-28

RAN

System Description Tables

Issue 01 (2007-04-20) Huawei Technologies Proprietary vii
http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-03%20introduction%20to%20nodebs.pdf/


10/101

Table 5-23Transportation requirements for physically active materials...........................................................5-28

Table 5-24Transportation requirements related to mechanical stress...............................................................5-28

Table 5-25Temperature and humidity requirements for the operation of the M2000 system...........................5-29

Table 5-26Other climatic requirements for the operation of the M2000 system..............................................5-29

Table 5-27Operation requirements for physically active materials...................................................................5-30

Table 5-28Operation requirements for chemically active materials..................................................................5-30

Table 5-29Operation requirements related to mechanical stress.......................................................................5-31

Tables

RAN

System Description

viii Huawei Technologies Proprietary Issue 01 (2007-04-20)
http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/http://01-05%20introduction%20to%20ran%20om.pdf/


11/101

About This Document

Purpose

This document describes Huawei RAN system including the introduction to the RAN, RAN

functions, NodeB, RNC, and RAN OM system.

Related Versions

The following table lists the product versions related to this document.

Product Name Version

RNC V100R008

NodeB V100R008

Intended Audience

This document is intended for the following users:

l Network planners

l Field engineers

l System engineers

l Shift operators

l Network operators

l

Network administrators

Update History

Refer to Changes in RAN System Description.

Organization

1 Introduction to the RAN System

The RAN system is the Radio Access Network (RAN) of the 3rd Generation Wideband Code

Division Multiple Access (WCDMA) system. This guide describes the RAN in the UMTS, RANarchitecture, internal and external interfaces of RAN.

RAN

System Description About This Document

Issue 01 (2007-04-20) Huawei Technologies Proprietary 1
http://-/?-http://01-01%20introduction%20to%20the%20ran%20system.pdf/http://-/?-


12/101

2 RAN Functions

The RAN functions include user data transfer, overall system access control, radio channel

ciphering and deciphering, mobility management, radio resource management and control, and

reporting of broadcast and multicast services and flows.

3 Introduction to NodeBs

NodeBs are network elements in the UTRAN. NodeBs are used to implement the coverage of

radio signals that are transmitted to and received from the UEs. NodeBs are connected to RNCs

through the Iub interface.

4 Introduction to the RNC

The RNC is classified into hardware system and software system physically, or switching

subsystem and service processing subsystem logically.

5 Introduction to RAN OM

The RAN system provides complete operations and maintenance. This part describes the RANOM network, RAN OM networking scheme, and M2000 functions.

Conventions

1. Symbol Conventions

The following symbols may be found in this document. They are defined as follows

Symbol Description

DANGER

Indicates a hazard with a high level of risk that, if not avoided,

will result in death or serious injury.

WARNING

Indicates a hazard with a medium or low level of risk which, if

not avoided, could result in minor or moderate injury.

CAUTION

Indicates a potentially hazardous situation that, if not avoided,

could cause equipment damage, data loss, and performance

degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save your

time.

NOTE Provides additional information to emphasize or supplement

important points of the main text.

2. General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files,directories,folders,and users are in boldface. For

example,log in as user root.

About This Document

RAN

System Description

2 Huawei Technologies Proprietary Issue 01 (2007-04-20)
http://01-05%20introduction%20to%20ran%20om.pdf/http://01-04%20introduction%20to%20the%20rnc.pdf/http://01-03%20introduction%20to%20nodebs.pdf/http://01-02%20ran%20functions.pdf/


13/101


Italic Book titles are in italics.

Courier New

Terminal display is in Courier New.

3. Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{x | y | ...} Alternative items are grouped in braces and separated by verticalbars.One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets and

separated by vertical bars.One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical

bars.A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Alternative items are grouped in braces and separated by vertical

bars.A minimum of zero or a maximum of all can be selected.

4. GUI Conventions


Boldface Buttons,menus,parameters,tabs,window,and dialog titles are in

boldface. For example,click OK.

> Multi-level menus are in boldfaceand separated by the ">" signs.

For example,choose File > Create > Folder .

5. Keyboard Operation


Key Press the key.For example,press Enterand press Tab.

Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+A

means the three keys should be pressed concurrently.

Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the two

keys should be pressed in turn.

6. Mouse Operation

RAN

System Description About This Document

Issue 01 (2007-04-20) Huawei Technologies Proprietary 3


14/101

Action Description

Click Select and release the primary mouse button without moving the

pointer.

Double-click Press the primary mouse button twice continuously and quickly

without moving the pointer.

Drag Press and hold the primary mouse button and move the pointer

to a certain position.

About This Document

RAN

System Description

4 Huawei Technologies Proprietary Issue 01 (2007-04-20)


15/101

1Introduction to the RAN SystemAbout This Chapter

The RAN system is the Radio Access Network (RAN) of the 3rd Generation Wideband Code

Division Multiple Access (WCDMA) system. This guide describes the RAN in the UMTS, RAN

architecture, internal and external interfaces of RAN.

1.1 RAN in the UMTS

The UMTS isthe 3rd Generation WCDMA radio telecommunication system. The RAN is the

radio access network of the UMTS.

1.2 RAN Architecture

The RAN system consists of the RNC, NodeB, and M2000. The RNC and the NodeB are networkelements and the M2000 is an EMS of the RAN. The RAN implements its functions through the

interconnection between the RNC, NodeB, and M2000.

1.3 RAN External Interfaces

The RAN system provides the external interfaces in compliance with the 3GPP protocols,

including theUu, Iu, and Itf-N interfaces. As open interfaces, the Uu and Iu interfaces can be

used for the interconnection between devices of different vendors. The Itf-N is a private interface.

1.4 RAN Internal Interfaces

The RAN system provides internal equipments with the interfaces in compliance with the 3GPP

protocols, including the Iub, Iur, and Itf-S interfaces. As open interfaces, the Iub and Iur

interfaces can be used for the interconnection between devices of different vendors. The Itf-S

interface is a private interface.

RAN

System Description 1 Introduction to the RAN System

Issue 01 (2007-04-20) Huawei Technologies Proprietary 1-1


16/101

1.1 RAN in the UMTS

The UMTS is the 3rd Generation WCDMA radio telecommunication system. The RAN is theradio access network of the UMTS.

The position of the UMTS RAN is shown in Figure 1-1.

Figure 1-1RAN in the UMTS

The UMTS consists of the following three parts:

l User Equipment (UE): provides communication interfaces and various services for users.

l Core Network (CN): provides the Circuit Switched (CS), Packet Switched (PS), and

network interconnection functions.

l Radio Access Network (RAN): provides all the radio functions, including radio network

coverage and UE-to-CN links.

1.2 RAN Architecture

The RAN system consists of the RNC, NodeB, and M2000. The RNC and the NodeB are network

elements and the M2000 is an EMS of the RAN. The RAN implements its functions through the

interconnection between the RNC, NodeB, and M2000.

Figure 1-2shows the RAN architecture.


RAN

System Description

1-2 Huawei Technologies Proprietary Issue 01 (2007-04-20)


17/101

Figure 1-2RAN architecture

The RAN architecture is described as follows:

l Several Radio Network Systems (RNSs) constitutes an RAN.

l Each RNS consists of one RNC and serveral NodeBs.

The Radio Network Controller (RNC) controls the whole RNS.

NodeB, a base station controlled by the RNC in the UMTS, implements the radio network

coverage functions and provides air interfaces for UEs.

l M2000, an EMS, provides concentrated maintenance for the whole system of RAN. That

is, the M2000 can directly maintain the RNC and provide maintenance for the NodeB

through the RNC.

1.3 RAN External Interfaces

The RAN system provides the external interfaces in compliance with the 3GPP protocols,

including the Uu, Iu, and Itf-N interfaces. As open interfaces, the Uu and Iu interfaces can be

used for the interconnection between devices of different vendors. The Itf-N is a private interface.

Figure 1-3shows the RAN external interfaces.

RAN




18/101

Figure 1-3RAN external interfaces

The Iu interface is an interface between the RAN and the CN. The Iu interfaces consist of the

following interfaces:

l Iu-CS interface: connects the RAN and the MSC (that is, MSC Server and MGW)

l Iu-PS interface: connects the RAN and the SGSN.

l Iu-BC interface: connects the RAN and the CBC.

The Uu interface is an interface between the RAN and the UE.

The Itf-N interface is an interface between the RAN and the NMS.

1.4 RAN Internal Interfaces

The RAN system provides internal equipments with the interfaces in compliance with the 3GPP

protocols, including the Iub, Iur, and Itf-S interfaces. As open interfaces, the Iub and Iur

interfaces can be used for the interconnection between devices of different vendors. The Itf-S

interface is a private interface.

Figure 1-4shows the RAN internal interfaces.

Figure 1-4RAN internal interfaces

The Iub interface is an interface between the NodeB and the RNC. An RNC controls the NodeB

through the Iub interface and several RNCs constitute an RNS.

The Iur interface is an interface between the RNCs and also between different RNSs.


RAN

System Description



19/101

The Itf-S interface is the interface through which the M2000 provides maintenance for the RNC

and the NodeB.

RAN




20/101


21/101

2RAN FunctionsAbout This Chapter

The RAN functions include user data transfer, overall system access control, radio channel

ciphering anddeciphering, mobility management, radio resource management and control, and

reporting of broadcast and multicast services and flows.

2.1 User DataTransfer

RAN user data transfer refers to the RAN user data transmission through the Uu and Iu interfaces.

2.2 Overall System Access Control

Overall system access refers to the process and method of connecting the UMTS service or

equipment users to the RAN system. The UMTS controls the access of UEs through admission

control, congestion control, and system information broadcasting. The user system access can

be initiated by a UE, for example, the UE originates a call. Or the access can be initiated at the

CN side when the UE terminates a call.

2.3 Radio Channel Ciphering and Deciphering

Radio channel ciphering and deciphering function is a process in which the UTRAN and the UE

cipher or decipher the data on the Uuinterface. This function can prevent an unauthorized third

party from visiting the ongoing data transmission on the Uu interface.

2.4 Mobility Management

Mobility management refers to the support and management of communication services that the

UTRAN system provides for the movable UEs.

2.5 Radio Resource Management and Control

This function is to distribute and maintain the radio communication resources. The UMTS radio

resources are shared by the CS and the PS services.

2.6 Broadcast and Multicast

This function is to send messages from a single point to multiple points. The broadcast function

is to send service information to all the users in a specified area. The multicast function is to

send service information to some of the users, most of whom are subscribers, in a specified area.

Broadcast and multicast services include broadcast and multicast information distribution,

broadcast and multicast flow control, and CBS status report.

RAN

System Description 2 RAN Functions



22/101

2.1 User Data TransferRAN user data transfer refers to the RAN user data transmission through the Uu and Iu interfaces.

According to the 3GPP protocols, the services are classified into the following categories to

meet different QoS requirements:

l Session services: require high real-time transmission, allowing bit errors to some extent,

such as voice telephony and videophone.

l Streaming services: require high real-time, stable and continuous transmission of data

stream, for example, the multimedia service.

l Interactive services: require relatively low real-time transmission but highly integrated and

accurate data. For example, webpage browsing and location-based services.

l Background services: have no requirement for real-time transmission but highly integrated

and accurate data, such as sending and receiving e-mails.The RAN system supports different QoS services defined by the 3GPP protocols, including CS

services, PS services, and their hybrid services.

CS services are as follows:

l AMR session services

l CS transparent data session services

l CS transparent data streaming services

l CS non-transparent data streaming services

PS services are as follows:

l PS session services

l PS streaming services

l PS interactive services

l PS background services

Hybrid services are as follows:

l CS hybrid services

l PS hybrid services

l CS and PS hybrid services

2.2 Overall System Access ControlOverall system access refers to the process and method of connecting the UMTS service or

equipment users to the RAN system. The UMTS controls the access of UEs through admission

control, congestion control, and system information broadcasting. The user system access can

be initiated by a UE, for example, the UE originates a call. Or the access can be initiated at the

CN side when the UE terminates a call.

2.2.1 Admission Control

Admission control aims to receive or reject new users, new RABs, or new radio links, forexample, the newly-added links due to handover.

2 RAN Functions

RAN

System Description



23/101

2.2.2 Congestion Control

Congestion control is applied to monitoring, detecting or handling the system that is nearly or

already overloaded.

2.2.3 System Information Broadcasting

System information broadcasting refers to the information that the network system broadcaststo the UE.

2.2.1 Admission Control

Admission control aims to receive or reject new users, new RABs, or new radio links, for

example, the newly-added links due to handover.

In the RAN system, when new radio links are set up, the system load increases and overall

interference rises. As a result, the system becomes unstable, which affects the network service

quality. Therefore, the control over new user access and new link setup is required.

The admission control is applied to the situations when more radio resources are needed, for

example, at the initial access of UEs, or during the RAB assignment and reconfiguration, or

during the handover.

This function is used to adjust system load and avoid overload based on the results of interference

and resource measurements. Different priorities and specific scenarios exert much impact on the

result of admission control.

l The CRNC implements the admission control related to uplink interference and downlink

power.

l The SRNC implements the admission control related to the Iu interface.

2.2.2 Congestion ControlCongestion control is applied to monitoring, detecting or handling the system that is nearly or

already overloaded.

System overload or near overload indicates that some network resources are already or nearly

exhausted. In this case, the operating system becomes unstable and the quality of network

services is at a lower level. Therefore, congestion control must be performed to restore the

network status and avoid any negative impact on users.

For example, when a cell is overloaded to the extent of congestion, the cell load is immediately

reduced through a fast decrease in data rates or a sudden break of low-priority calls.

2.2.3 System Information BroadcastingSystem information broadcasting refers to the information that the network system broadcasts

to the UE.

System information is the network-related Access Stratum (AS) or Non-Access Stratum (NAS)

information. The UE can operate in the network only when it obtains such information.

The AS or NAS system information are broadcast by the UTRAN to cells through the BCH.

RAN




24/101

2.3 Radio Channel Ciphering and Deciphering

Radio channel ciphering and deciphering function is a process in which the UTRAN and the UE

cipher or decipher the data on the Uu interface. This function can prevent an unauthorized third

party from visiting the ongoing data transmission on the Uu interface.

The radio channel ciphering and deciphering is a pure counting function using the ciphering

algorithms defined by protocols. The UEA0 and UEA1 algorithms are used for the UTRAN

ciphering while the UIA1 algorithm is used for integrity protection.

2.4 Mobility Management

Mobility management refers to the support and management of communication services that the

UTRAN system provides for the movable UEs.

2.4.1 Handover

Handover refers to the process that the UE changes its radio links during the communications.

Handover is mainly used to maintain uninterrupted services for the moving UE during the

communication.

2.4.2 SRNS Relocation

The Serving RNS (SRNS) relocation refers to the process that the UE moves from one serving

RNC to another. The UE related information on the original RNC is transferred to the target

RNC and theassociated Iu interface is also connected to the target RNC.

2.4.3 Paging

Paging refersto the process that the network searches the UE through broadcasting. Paging is

used when the UE terminates a call. The network requests the UE for connection by using the

paging function.

2.4.4 Positioning

Positioning isto decide the geographic location of the UE in the coverage of UMTS.

2.4.5 NAS Node Selection

NAS Node Selection (NNS) refers tothe initial CN node selection specified by the UTRAN for

the UE. The NAS initial message and the Link Layer Control (LLC) message are routed from

the UE to theCN node.

2.4.6 SharedNetworks Access Control

This functionenables the RAN to apply the specified UE access control over the RAN Location

Area (LA) or the LA of neighboring networks at the CN's request.

2.4.7 Hierarchical Cell Structure

According to the coverage and propagation loss, the UTRAN cells are classified into wide area,

middle range, and local area, which form a Hierarchical Cell Structure (HCS). The HCS

implements a flexible coverage for the network of low cost and high quality.

2.4.1 Handover

Handover refers to the process that the UE changes its radio links during the communications.

Handover is mainly used to maintain uninterrupted services for the moving UE during thecommunication.

2 RAN Functions

RAN

System Description



25/101

A handover is in the charge of the network or simply the UE. The handover function is

implemented in the SRNC or the UE or both.

Handover is classified into the following:

l Soft handover: an intra-frequency handover during which the old link is removed after anew link is set up.

l Hard handover: includes intra-frequency and inter-frequency handovers during which the

old link is removed before a new link is set up.

l Inter-system handover: a handover between different systems, for example, the UMTS-to-

GSM handover.

2.4.2 SRNS Relocation

The Serving RNS (SRNS) relocation refers to the process that the UE moves from one serving

RNC to another. The UE related information on the original RNC is transferred to the target

RNC and the associated Iu interface is also connected to the target RNC.

The relocation of SRNS can reduce the consumption of Iur bandwidth, especially when the Iur

interface is established through the routes of CN devices, and also can shorten the call delay.

The relocation is initiated by the SRNC and implemented by the CN, SRNC, and DRNC.

2.4.3 Paging

Paging refers to the process that the network searches the UE through broadcasting. Paging is

used when the UE terminates a call. The network requests the UE for connection by using the

paging function.

UTRAN paging is classified into the following two types:

l Paging Type 1: When the UE is in IDLE, CELL_PCH, or URA_PCH state, the UTRAN

sends paging messages to the UE through the PCH.

l Paging Type 2: When the UE is in CELL_FACH or CELL_DCH state, the UTRAN sends

paging messages to the UE through the DCH or FACH.

2.4.4 Positioning

Positioning is to decide the geographic location of the UE in the coverage of UMTS.

The UE positioning, an important function of the UMTS, has a promising future in the 3G mobile

communication system.

The positioning functions include three basic technologies, that is, CELL-ID+RTT, OTDOA-

IPDL and A-GPS, and their hybrid technologies.

2.4.5 NAS Node Selection

NAS Node Selection (NNS) refers to the initial CN node selection specified by the UTRAN for

the UE. The NAS initial message and the Link Layer Control (LLC) message are routed from

the UE to the CN node.

In the UMTS, the RNC can connect several CN nodes, such as the MSC Server and the SGSN.

Therefore, the NAS message of UE is routed to the UTRAN-specified target CN node, whichis called NAS Node Selection.

RAN




26/101

The NRI is carried by the NAS initial signaling message or LLC message. If the UTRAN

specifies a CN node for the NRI, the NAS signaling message can be routed to the specified

address of CN node. Otherwise, or if the UTRAN fails to obtain an NRI, the message will be

routed to an available CN node also specified by the UTRAN.

2.4.6 Shared Networks Access Control

This functionenables the RAN to apply the specified UE access control over the RAN Location

Area (LA) orthe LA of neighboring networks at the CN's request.

The shared networks access control is based on the entire PLMN or Shared Networks Area

(SNA). The SNA corresponds to one or more LAs in the PLMN that controls the access of UE.

To apply the shared networks access control to an RAN or one of the neighboring network

systems, the RAN can decide whether the associated LA belongs to the SNA.

In this case, the SNA access information indicates that the UE is allowed to access the PLMN

or the SNA. If the access of a specified UE is restricted, the CN should provide the SNA access

information about the UE.

2.4.7 Hierarchical Cell Structure

According to the coverage and propagation loss, the UTRAN cells are classified into wide area,

middle range, and local area, which form a Hierarchical Cell Structure (HCS). The HCS

implements a flexible coverage for the network of low cost and high quality.

The UTRAN radio coverage cells include the following types:

l Macro cell: a wide area coverage mainly applied to outdoors. As a basic radio coverage, it

allows the lowest coupling loss of 70 dB between the NodeB and UE.

l Micro cell: a middle range coverage applied to indoors. With a smaller area, it allows thelowest coupling loss of 53 dB between the NodeB and UE.

l Pico cell: a local area coverage mainly applied to indoors. It allows the lowest coupling

loss of 45 dB between the NodeB and the UE.

2.5 Radio Resource Management and Control

This function is to distribute and maintain the radio communication resources. The UMTS radio

resources are shared by the CS and the PS services.

2.5.1 Radio Environment MonitoringThis function is to take measurements on radio channels of both existing and neighboring cells,

and provide the estimation of radio channel quality based on measurement results.

2.5.2 Combining/Splitting Control

This function is to combine or split information flows and to implement data transmission

between the UTRAN and a single UE through multiple physical channels. Combining and

splitting refer to the ways to control information flows.

2.5.3 Connection Setup and Release

This function involves controlling connection setup and release in the RAN.

2.5.4 Allocation and Deallocation of Radio Bearers

This function involves allocating or releasing radio bearers (RBs) according to the requests ofconnection setup and release and the QoS of RABs.

2 RAN Functions

RAN

System Description



27/101

2.5.5 Radio Protocols

This function is to carry user data and signaling through RBs and provide data transmission over

the Uu interface according to the QoS requirements. With this function, the UTRAN adjusts the

services to radio transmission.

2.5.6 RF Power ControlThis function is to control the transmit power of NodeBs and UEs, which can reduce radio

interference, improve the quality of radio links, and expand system capacity.

2.5.7 Radio Channel Encoding and Decoding

Radio channel encoding is a function to encode the data to be transmitted on radio channels and

provide redundancy for data transmission according to the encoding algorithm. Radio channel

decoding is a function to obtain the transmitted data from radio channels and provide error

detection and error correction according to the decoding algorithm.

2.5.8 Initial Access Detection and Handling

This function enables the UTRAN to detect initial access information of UE and respond to UE's

requests.2.5.9 CN Distribution for NAS Messages

This function enables the UE and the SRNC to add the CN indicator to an AS message and send

the message to an associated NAS entity.

2.5.1 Radio Environment Monitoring

This function is to take measurements on radio channels of both existing and neighboring cells,

and provide the estimation of radio channel quality based on measurement results.

The required measurements include the following:

l Received signal strengthl Estimated Bit Error Rate (BER)

l Propagation environment estimation

l Transport range

l Doppler frequency shift

l Synchronization status

l Received interference level

l Total downlink transmit power per cell

The function,applied to both UTRAN and UE, adjusts radio resources according to themeasurementresults and thus ensures the stability of radio links.

2.5.2 Combining/Splitting Control

This functionis to combine or split information flows andto implement data transmission

between the UTRAN and a single UE through multiple physical channels. Combining and

splitting referto the ways to control information flows.

The combingfunction of uplink information flows can implement the associated algorithms for

any use, suchas maximum rate combining algorithm, selection combining algorithm, selection

diversity algorithm, and equal gain combining algorithm. To reduce the Bit Error Rate (BER),

the combining and splitting control and the channel encoding control must be able to interactwith each other.

RAN




28/101

2.5.3 Connection Setup and Release

This function involves controlling connection setup and release in the RAN.

The function is performed for:

l Providing end-to-end connection setup and release to meet the requirement of other

functional entities, for example, when a call is made.

l Providing management and maintenance for the established end-to-end connection in the

RAN, for example, when a handover is performed.

2.5.4 Allocation and Deallocation of Radio Bearers

This function involves allocating or releasing radio bearers (RBs) according to the requests of

connection setup and release and the QoS of RABs.

The RB is set up when a call is originated; the RB is released when the call is terminated. Thesetup or release of RBs can also be performed during the call, for example, when the user service

requires changes or the macro diversity is used.

The allocation and deallocation of RBs are implemented by the CRNC and the SRNC.

2.5.5 Radio Protocols

This function is to carry user data and signaling through RBs and provide data transmission over

the Uu interface according to the QoS requirements. With this function, the UTRAN adjusts the

services to radio transmission.

The function of radio protocols includes the following:

l Multiplexing of services and UEs on RBs

l Segmentation and reassembly

l Acknowledged/Unacknowledged delivery according to the QoS

2.5.6 RF Power Control

This function is to control the transmit power of NodeBs and UEs, which can reduce radio

interference, improve the quality of radio links, and expand system capacity.

The WCDMA is a self-interference system, that is, in this system any UE can be a possible cause

of interference to other UEs. A UE of high transmit power may cause great interference to otherUEs.

The UTRAN power control function consists of the following:

l Open loop power control: applies to the control of the initial power of channels.

l Closed loop power control: consists of outer loop and inner loop. The outer loop power

control, used between the UTRAN and the UE, sets the target SIR according to the BLER.

The inner loop power control, used between the NodeB and the UE, adjusts the channel

power according to the SIR.

The UL power control include the UL open loop, UL inner loop, and UL outer loop.

The DL power control include the DL open loop, DL inner loop, and DL outer loop.

2 RAN Functions

RAN

System Description



29/101

2.5.7 Radio Channel Encoding and Decoding

Radio channel encoding is a function to encode the data to be transmitted on radio channels and

provide redundancy for data transmission according to the encoding algorithm. Radio channel

decoding is a function to obtain the transmitted data from radio channels and provide errordetection and error correction according to the decoding algorithm.

Errors may occur in the data transmission on radio channels, so associated methods must be

taken to detect and correct the errors.

In this case, redundancy is added to the source data on radio channels through the encoding

function. Therefore, during the decoding of radio channels, the redundancy can facilitate the

detection and correction of errors in data transmission.

The UMTS radio channel encoding algorithm and the redundancy degree are used to ensure the

rate and quality of transmission based on logical channels and data types.

The methods to encode radio channels include convolutional coding, interleaving, CRC check,

and Turbo code.

2.5.8 Initial Access Detection and Handling

This function enables the UTRAN to detect initial access information of UE and respond to UE's

requests.

The initial access handling provides the possible solutions to call collision detection. With the

completion of initial access, communications resources are allocated to the UE.

2.5.9 CN Distribution for NAS Messages

This function enables the UE and the SRNC to add the CN indicator to an AS message and send

the message to an associated NAS entity.

As one of the RRC functions, this function is performed to transmit the NAS messages through

an UE-to-CN transparent traversal in the AS.

In the downlink, each single NAS message is sent by the SRNC to the UE.

In the uplink, the CN indicator is added to the AS message by the UE. The SRNC evaluates this

AS message indicator and then sends the NAS message to the associated RANAP instance of

the peer end over the Iu interface.

2.6 Broadcast and MulticastThis function is to send messages from a single point to multiple points. The broadcast function

is to send service information to all the users in a specified area. The multicast function is to

send service information to some of the users, most of whom are subscribers, in a specified area.

Broadcast and multicast services include broadcast and multicast information distribution,

broadcast and multicast flow control, and CBS status report.

2.6.1 Broadcast and Multicast Messaging

This function enables the UTRAN to send the received broadcast and multicast messages to the

associated BMC entity on each cell for further processing.

2.6.2 Broadcast and Multicast Flow Control

RAN




30/101

This function enables the UTRAN to control the broadcast and multicast flows according to the

status of RNC processing unit.

2.6.3 CBS Status Reporting

This function provides the CBC with reports on the status of CBS messages that are being

broadcast.

2.6.1 Broadcast and Multicast Messaging

This function enables the UTRAN to send the received broadcast and multicast messages to the

associated BMC entity on each cell for further processing.

The broadcast and multicast messaging depends on a mapping between the service area and the

RNC-controlled area. The mapping is implemented through the OM functions.

2.6.2 Broadcast and Multicast Flow Control

This function enables the UTRAN to control the broadcast and multicast flows according to thestatus of RNC processing unit.

When the BMC processing unit of RNC fails to receive new service requests, it indicates that

the BMC is in congestion. In this case, the broadcast and multicast control is performed to inform

the data source of the congestion and solve the problem by reducing the amount of data flowing

to the BMC.

2.6.3 CBS Status Reporting

This function provides the CBC with reports on the status of CBS messages that are being

broadcast.

Network operators provide the Cell Broadcast Service (CBS) for mobile users in a specified areaby broadcasting some common information.

The RNC collects status data from each cell, for example, the completed broadcast list, and

matches the data with service areas. Then the data is reported to the CBC according to its requests.

2 RAN Functions

RAN

System Description



31/101

3Introduction to NodeBsAbout This Chapter

NodeBs are network elements in the UTRAN.NodeBs are used to implement the coverage of

radio signals that are transmitted to and received from the UEs. NodeBs are connected to RNCs

through the Iub interface.

3.1 NodeB Family

Huawei offers a series of WCDMA NodeBs that comply with the 3GPP protocols. The NodeB

family has the BTS3812A, BTS3812E, DBS3800, and iDBS3800 to meet your requirements for

actual conditions, such as cities, suburbs, rural areas, expressways, railways, and subways.

3.2 Introduction to the BTS3812E

The BTS3812E is an indoor macro NodeB, which ensures large capacity and wide coverage. It

is applicable to urban areas with very high potential for traffic growth.

3.3 Introduction to the BTS3812A

The BTS3812A is an outdoor macro NodeB, which ensures large capacity and wide coverage.

It is applicable to urban areas with very high potential for traffic growth.

3.4 Introduction to the DBS3800

DBS3800 is a distributed NodeB system that has medium size and requires small space. It is

applicable to special scenarios such as railways, expressways, and tunnels.

3.5 Introduction to the iDBS3800

iDBS3800 is an indoor distributed NodeB. It is applicable to indoor areas with a large traffic

volume, such as the office buildings, residential buildings, hotels, shopping malls, and hospitals.

3.6 NodeB OM System

NodeB OM system is applied to managing, monitoring, and maintaining the software, hardware,

and configuration of NodeBs to ensure stable operations of NodeBs. The subsystem provides a

great diversity of operating and maintaining methods and also the platforms for different

scenarios.

RAN

System Description 3 Introduction to NodeBs



32/101

3.1 NodeB Family

Huawei offers a series of WCDMA NodeBs that comply with the 3GPP protocols. The NodeBfamily has the BTS3812A, BTS3812E, DBS3800, and iDBS3800 to meet your requirements for

actual conditions, such as cities, suburbs, rural areas, expressways, railways, and subways.

3.1.1 Overview of the BTS3812E

The BTS3812E is an indoor macro NodeB. The BTS3812E is used in urban areas, business

centers, and large-sized and medium-sized cities with very high potential for traffic growth.

3.1.2 Overview of the BTS3812A

The BTS3812A is an outdoor macro NodeB. The BTS3812A is used in urban areas, business

centers, and large-sized and medium-sized cities with high potential for traffic growth.

3.1.3 Overview of the DBS3800

The DBS3800 can provide flexible WCDMA radio access solutions under different network

situations to meet operators' specific requirements. The combination of different modules can

achieve seamless coverage in multiple typical scenarios, for example, cities, suburbs, rural areas,

highway, railway, and hot spots.

3.1.4 Overview of the iDBS3800

The iDBS3800 is used in indoor areas with a large traffic volume, such as the office buildings,

residential buildings, hotels, shopping malls, and hospitals.

3.1.1 Overview of the BTS3812E

The BTS3812E is an indoor macro NodeB. The BTS3812E is used in urban areas, businesscenters, and large-sized and medium-sized cities with very high potential for traffic growth.

The BTS3812E has the following benefits:

l Capacity: One BTS3812E supports up to 1024 and 1536 Channel Elements (CEs) in the

uplink (UL) and the downlink (DL) respectively. One BTS3812E also supports up to 12

cells and 6 sectors. Each sector supports up to 4 carriers.

l Coverage: The BTS3812E supports particular configurations of different sectors having

differentcarriers and different transmit power. The maximum search radius is 180 km. The

1-way receiver sensitivity is better than 125 dBm. The BTS3812E supports transmit

diversity. The BTS3812E can be connected to the Remote Radio Unit (RRU).

l Multiband applications: The BTS3812E supports frequency bands 2100 MHz, 1900 MHz,1800 MHz, 900 MHz, and 850 MHz and supports cabinet sharing between any two bands

to meet your requirements in different regions.

l Topology: The BTS3812E supports multiple topologies such as star, chain, tree, and ring.

The BTS3812E supports satellite and microwave transmission.

l Transmission interfaces: The data on the Iub interface can be transmitted in the channelized

and non-channelized ATM transmission based on E1/T1 and STM-1/OC-3 and in the IP

transmission based on E1/T1 and FE. The BTS3812E supports the UNI link, IMA link,

fractional ATM link, and hub NodeB.

l Clock and synchronization: The BTS3812E supports the clock extracted from the Iub

interface, the Global Positioning System (GPS) clock, BITS clock, and internal clock.

3 Introduction to NodeBs

RAN

System Description



33/101

l High Speed Downlink Packet Access (HSDPA): HSDPA and R99/R4 services are

supported by the same carrier. The downlink peak rate is up to 14.4 Mbit/s and the uplink

peak rate is up to 384 kbit/s. Each cell supports 64 HSDPA users.

l High Speed Uplink Packet Access (HSUPA): HSUPA phase 1 is supported. The uplink

application layer peak rate is up to 1.44 Mbit/s (DL) and peak rate over the Uu interface is1.92 Mbit/s. Each cell supports 20 HSUPA users.

l Multimedia Broadcast and Multicast Service (MBMS): With this technology, the NodeB

can save resources on the Uu interface either by sending multimedia broadcast services to

the UEs in a cell over common channels or by sending multicast services subscribed by the

UEs in the cell.

l Installation: With a modular design that supports cabling at the front of the cabinet, the

NodeB cabinet is easy to install and maintain.

l The BTS3812E can be maintained on the LMT or the iManager M2000 (M2000 for short),

a centralized management center. The BTS3812E supports local maintenance, remote

maintenance, and reverse maintenance.

l Enhanced antenna system: The antenna system of the BTS3812E supports Antenna

Interface Standards Group (AISG) protocols, the TMA and STMA, and Remote Electrical

Tilt (RET).

l High-speed access of UEs: The NodeB allows UEs to enjoy services in a vehicle moving

at the speed of up to 400 km/h.

l IP RAN: The IP transmission mode enables all-IP transmission on the Iub and Iur interface.

Data services can be transmitted over low rate links. This helps you make use of the IP

transmission resources.

3.1.2 Overview of the BTS3812A

The BTS3812A is an outdoor macro NodeB. The BTS3812A is used in urban areas, business

centers, and large-sized and medium-sized cities with high potential for traffic growth.

The BTS3812A has the following benefits:

l Capacity: One BTS3812A supports up to 1024 and 1536 Channel Elements (CEs) in the

uplink (UL) and the downlink (DL) respectively. One BTS3812A also supports up to 12

cells and 6 sectors. Each sector supports up to 4 carriers.

l Coverage: The BTS3812A supports particular configurations of different sectors having

different carriers and different transmit power. The maximum search radius is 180 km. The

1-way receiver sensitivity is better than 125 dBm. The BTS3812A supports transmit

diversity. The BTS3812A can be connected to the Remote Radio Unit (RRU).l Multiband applications: The BTS3812A supports frequency bands 2100 MHz, 1900 MHz,

1800 MHz, 900 MHz, and 850 MHz and supports cabinet sharing between any two bands

to meet your requirements in different regions.

l Topology: The BTS3812A supports multiple topologies such as star, chain, tree, and ring.

The BTS3812A supports satellite and microwave transmission.

l Transmission interfaces: The data on the Iub interface can be transmitted in the channelized

and non-channelized ATM transmission based on E1/T1 and STM-1/OC-3 and in the IP

transmission based on E1/T1 and FE. The BTS3812A supports the UNI link, IMA link,

fractional ATM link, and hub NodeB.

l

Clock and synchronization: The BTS3812A supports the clock extracted from the Iubinterface, the Global Positioning System (GPS) clock, BITS clock, and internal clock.

RAN

System Description 3 Introduction to NodeBs



34/101

l High Speed Downlink Packet Access (HSDPA): HSDPA and R99/R4 services are

supported by the same carrier. The downlink peak rate is up to 14.4 Mbit/s and the uplink

peak rate is up to 384 kbit/s. Each cell supports 64 HSDPA users.

l High Speed Uplink Packet Access (HSUPA): HSUPA phase 1 is supported. The uplink

application layer peak rate is up to 1.44 Mbit/s (DL) and peak rate over the Uu interface is1.92 Mbit/s. Each cell supports 20 HSUPA users.

l Multimedia Broadcast and Multicast Service (MBMS): With this technology, the NodeB

can save resources on the Uu interface either by sending multimedia broadcast services to

the UEs in a cell over common channels or by sending multicast services subscribed by the

UEs in the cell.

l Installation: With a modular design that supports cabling at the front of the cabinet, the

NodeB cabinet is easy to install and maintain.

l The BTS3812A can be maintained on the LMT or the iManager M2000 (M2000 for short),

a centralized management center. The BTS3812A supports local maintenance, remote

maintenance, and reverse maintenance.

l Enhanced antenna system: The antenna system of the BTS3812A supports Antenna

Interface Standards Group (AISG) protocols, the TMA and STMA, and Remote Electrical

Tilt (RET).

l High-speed access of UEs: The NodeB allows UEs to enjoy services in a vehicle moving

at the speed of up to 400 km/h.

l IP RAN: The IP transmission mode enables all-IP transmission on the Iub and Iur interface.

Data services can be transmitted over low rate links. This helps you make use of the IP

transmission resources.

l The BTS3812A that complies with the standard is configured with a environment

monitoring and adjustment system. This enables the cabinet to adapt to various

environments.

3.1.3 Overview of the DBS3800

The DBS3800 can provide flexible WCDMA radio access solutions under different network

situations to meet operators' specific requirements. The combination of different modules can

achieve seamless coverage in multiple typical scenarios, for example, cities, suburbs, rural areas,

highway, railway, and hot spots.

The typical application scenarios of the DBS3800 are described as follows:

Site Requirements Solution

Launching a new outdoor 3G site; there is no

equipment room; the power backup system is

required; the 3G NodeB is installed outdoors.

Configuration of BBU3806 (48 V) +

RRU3801C (48 V) + APM100

Launching a new outdoor 3G site; the power

backup system is available; the power backup

system can provide space for the BBU3806.

Configuration of BBU3806 (48 V) +

RRU3801C (48 V)

Launching 3G services at a 2G site; the 2G BTS

has spare space; the 3G NodeB does not occupy

much space;

ran documentation guide

Documents