ZXWR RNC (V3 (1) .09.30) Commissioning Guide - Integration Manual - R1.0

ZXWR RNC (V3.09.
30)
Commissioning Guide
Integration Manual
ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATIN you agree to the following terms. If you
do not agree to the following terms, please notice that you are not allowed to use this document.
Copyright 2009 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
and
are registered trademarks of ZTE CORPORATION. ZTEs company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyones access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual,
relevant contract or laws and regulations in relevant country (countries).
This document is provided as is and as available. Information contained in this document is
subject to continuous update without further notice due to improvement and update of ZTE
CORPORATIONs products and technologies.
ZTE CORPORATION
Address:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website:
http://dms.zte.com.cn (Technical Support)
Email:
TSM.Aftersales@zte.com.cn
ZTE Confidential Proprietary
2014 ZTE CORPORATION. All rights reserved.
Revision History
Product Version
V3.09.30
Document Version
Serial Number
R1.0
Reason for Revision

First published
Author
Date
2010-07-15
Document Version
R1.0
Prepared
by
Hu Zhigang
Reviewed by
Chen Taiming
Approved by
Chen Taiming
II
About This Document

Summary
Chapter
Description
1 Introduction to RNC System

Integration
Introduction to RNC system integration
2 NodeB Integration
Description of NodeB integration
3 Iu-CS Integration
Description of Iu-CS integration
4 Iu-PS Integration
Description of Iu-PS integration
5 Iur Integration
Description of Iur integration
Applicable to: RNC commissioning engineers (both ZTE engineers and ZTEs
subcontractors)
III
TABLE OF CONTENTS
1 Introduction to RNC System Integration......................................................................1
1.1 Scope of Application.....................................................................................................1
1.2 Acronyms and Abbreviations.........................................................................................1
1.3 RNC External Interfaces...............................................................................................3
1.4 Classification of Transmission Bearer Modes of RNC External Interfaces....................4
1.5 Structure of RNC External Interface Protocol Stack......................................................5
1.6 Principles for RNC Integration.......................................................................................5
1.7 Preparation for RNC Integration....................................................................................6
1.7.1 Check of Hardware...............................................................................................6
1.7.2 Check of Data Configuration................................................................................6
1.8 Parameter Conversion Related with RNC Integration...................................................6
1.8.1 SPC Conversion...................................................................................................6
1.8.2 ATM Address Conversion.....................................................................................7
1.8.3 PVC Bandwidth Unit Conversion..........................................................................8
2 NodeB Integration..........................................................................................................9
2.1 ATM over E1.................................................................................................................9
2.1.1 Description of Integration Parameters for Iub Transmission.................................9
2.1.2 Iub Integration Description..................................................................................10
2.1.3 Physical Layer....................................................................................................10
2.1.4 IMA Layer........................................................................................................... 11
2.1.5 ATM Layer..........................................................................................................13
2.1.6 NBAP Layer........................................................................................................15
2.2 ATM over STM-1.........................................................................................................18
2.2.1 Iub Interface Integration Parameters..................................................................18
2.2.3 Physical Layer....................................................................................................19
2.2.4 ATM Layer..........................................................................................................20
2.2.5 NBAP Layer........................................................................................................21
2.3 ATM over CSTM-1......................................................................................................21
2.3.1 Iub Integration Parameters.................................................................................21
2.3.3 Physical Layer....................................................................................................22
2.3.4 IMA Layer........................................................................................................... 23
2.3.5 ATM Layer..........................................................................................................24
2.3.6 NBAP Layer........................................................................................................24
2.4 IP over E1................................................................................................................... 25
2.4.3 Physical Layer....................................................................................................26
2.4.4 HDLC Layer........................................................................................................27
2.4.5 PPP Layer..........................................................................................................27
2.4.6 IP Layer..............................................................................................................28
2.4.7 SCTP Layer........................................................................................................29
2.4.8 OMCB................................................................................................................ 30
IV
2.4.9 NBAP Layer........................................................................................................30

2.5 IP over FE................................................................................................................... 30
2.5.3 Physical Layer....................................................................................................31
2.5.4 IP Layer..............................................................................................................33
2.5.5 SCTP Layer........................................................................................................33
2.5.6 NBAP Layer........................................................................................................33
2.6 ATM and IP Mixed Transmission................................................................................34
3 Iu-CS Integration.......................................................................................................... 35
3.1 ATM Mode.................................................................................................................. 35
3.1.1 Description of Iu-CS Integration Parameters (E1)...............................................35
3.1.2 Description of Iu-CS Integration Parameters (STM-1)........................................36
3.1.3 Description of Iu-CS Integration..........................................................................37
3.1.4 Physical Layer....................................................................................................37
3.1.5 IMA Layer........................................................................................................... 39
3.1.6 ATM Layer..........................................................................................................39
3.1.7 MTP3B Layer.....................................................................................................41
3.1.8 SCCP Layer and RANAP Layer.........................................................................44
3.2 IP Mode...................................................................................................................... 45
3.2.1 Description of Iu-CS Integration Parameters......................................................45
3.2.2 Description of Iu-CS Integration..........................................................................46
3.2.3 Physical Layer....................................................................................................46
3.2.4 IP Layer..............................................................................................................48
3.2.5 SCTP Layer........................................................................................................49
3.2.6 M3UA Layer.......................................................................................................50
4 Iu-PS Integration.......................................................................................................... 53
4.1 ATM Mode.................................................................................................................. 53
4.1.1 Description of Iu-PS Integration Parameters (E1)...............................................53
4.1.2 Description of Iu-PS Integration Parameters (STM-1)........................................54
4.1.3 Description of Iu-PS Integration..........................................................................55
4.1.4 Physical Layer....................................................................................................55
4.1.5 IMA Layer........................................................................................................... 55
4.1.6 ATM Layer..........................................................................................................55
4.1.7 MTP3B Layer.....................................................................................................55
4.1.9 GTP-U Layer......................................................................................................55
4.2 IP Mode...................................................................................................................... 56
4.2.1 Description of Iu-PS Integration Parameters......................................................56
4.2.2 Description of Iu-PS Integration..........................................................................58
4.2.3 Physical Layer....................................................................................................58
4.2.4 IP Layer..............................................................................................................60
4.2.5 SCTP Layer........................................................................................................61
4.2.6 M3UA Layer.......................................................................................................61
5 Iur Integration............................................................................................................... 63
5.1 ATM Mode.................................................................................................................. 63
5.1.1 Description of Iur Integration Parameters...........................................................63

5.1.2 Description of Iur Integration..............................................................................64
5.1.3 Physical Layer....................................................................................................64
5.1.4 ATM Layer..........................................................................................................64
5.1.5 MTP3B Layer.....................................................................................................64
5.1.6 SCCP Layer and RNSAP Layer.........................................................................64
5.2 IP Mode...................................................................................................................... 65
5.2.1 Description of Iur Integration Parameters...........................................................65
5.2.2 Description of Iur Integration..............................................................................66
5.2.3 Physical Layer....................................................................................................66
5.2.4 IP Layer..............................................................................................................66
5.2.5 SCTP Layer........................................................................................................66
5.2.6 M3UA Layer.......................................................................................................66
5.2.7 SCCP Layer and RNSAP Layer.........................................................................66
VI
FIGURES
VII
Figure 1-1 RNC external transmission interfaces..........................................................4

Figure 1-2 Structure of protocol stack............................................................................5
Figure 2-3 E1 subunit status..........................................................................................11
Figure 2-4 E1 status at NodeB side...............................................................................11
Figure 2-5 IMA link status..............................................................................................12
Figure 2-6 IMA group status...........................................................................................13
Figure 2-7 PVC status.....................................................................................................14
Figure 2-8 AAL2 status...................................................................................................15
Figure 2-9 SSCOP keep-active signaling......................................................................15
Figure 2-10 NCP and CCP status...................................................................................16
Figure 2-11 Cells status..................................................................................................17
Figure 2-12 Common transport channels.....................................................................17
Figure 2-13 Cell setup standard signaling....................................................................18
Figure 2-14 Direct transfer message.............................................................................18
Figure 2-15 APBE subunit state.....................................................................................20
Figure 2-16 SDTB/SDTA subunit state query................................................................22
Figure 2-17 E1 link status query....................................................................................23
Figure 2-18 IMA link status............................................................................................23
Figure 2-19 IMA group status.........................................................................................24
Figure 2-20 SDTB/SDTA subunit state..........................................................................26
Figure 2-21 E1 link status...............................................................................................27
Figure 2-22 HDLC link status.........................................................................................27
Figure 2-23 Tracing PPP signaling................................................................................28
Figure 2-24 SLA test.......................................................................................................29
Figure 2-25 SCTP status.................................................................................................30
Figure 2-26 Iub Interface Integration Parameters in IP Over FE Mode.......................30
VIII
Figure 2-27 GIPI subunit state.......................................................................................32

Figure 2-28 Alarm of GIPI external port.........................................................................33
Figure 3-29 E1 subunit state query...............................................................................38
Figure 3-30 APBE subunit state query..........................................................................39
Figure 3-31 PVC link state..............................................................................................40
Figure 3-32 AAL2 link status query...............................................................................41
Figure 3-33 SSCOP link signaling tracing.....................................................................41
Figure 3-34 No. 7 link status..........................................................................................42
Figure 3-35 Adjacent office signaling point status......................................................43
Figure 3-36 Office route query.......................................................................................44
Figure 3-37 Signaling link test result.............................................................................44
Figure 3-38 SCCP connection establishment messages.............................................45
Figure 3-41 SLA test.......................................................................................................49
Figure 3-42 SCTP state...................................................................................................50
Figure 3-43 AS and ASP state........................................................................................51
Figure 3-44 Active route information.............................................................................52
Figure 3-45 SCCP connection establishment...............................................................52
Figure 4-46 SLA test.......................................................................................................56
Figure 4-49 SLA test.......................................................................................................61
IX
TABLES
Table 1-1 Classification of Transmission Bearer Modes of RNC External Interfaces. 4
Table 1-2 The Meaning of Each SSF Value.....................................................................6
Table 2-3 Description of Integration Parameters for Iub Transmission.......................9
Table 2-4 Iub Integration Parameters in ATM Over STM-1 Bearer Mode....................19
Table 2-5 Iub Integration Parameters in ATM Over CSTM-1 Bearer Mode..................21
Table 2-6 Iub Interface Integration Parameters in the IP Over E1 Mode ....................25
Table 3-7 Description of Iu-CS Integration Parameters (E1)........................................35
Table 3-8 Description of Iu-CS Integration Parameters (STM-1).................................36
Table 3-9 Iu-CS Integration Parameters........................................................................45
Table 4-10 Description of Iu-PS Integration Parameters (E1)......................................53
Table 4-11 Description of Iu-PS Integration Parameters (STM-1)................................54
Table 4-12 Description of Iu-PS Integration Parameters..............................................56
Table 5-13 Description of Iur Integration Parameters..................................................63
Table 5-14 Description of Iur Integration Parameters..................................................65
Introduction
Integration
to
RNC
System
Knowledge
1.1
Understanding the common used WCDMA acronyms and abbreviations.
Getting to know the interfaces involved in the RNC integration.
Understanding the transmission bearer modes used at different interfaces.
Getting to know the protocol structure of different interfaces.
Understanding the principles of RNC integration.
Learning about the preparations for the RNC integration.
Being familiar with the parameter conversions involved in the RNC integration.
Scope of Application
This manual describes the interfaces involved in RNC integration, and the transmission
bearer mode of each interface, the general planning for RNC integration, and the
integration of each interface under various transmission bearer modes.
1.2
Acronyms and Abbreviations

16QAM
16 Quadrature Amplitude Modulation
AMC
Adaptive Modulation and Coding
AMR
Adaptive Multi Rate
ATM
Asynchronous Transfer Mode
CBS
Cell Broadcast Service
CCTrCH Coded Composite Transport Channel

CN Core Network
CPICH
Common Pilot Channel
CQI Channel Quality Indicator

DPCCH Dedicated Physical Control Channel
DPDCH Dedicated Physical Data Channel
FDDFrequency Division Duplex
HARQ
Hybrid Automatic Repeat Request
HSDPA High Speed Downlink Packet Access

HS-DPCCH
High Speed-Dedicated Physical Control Channel
HS-DSCH
High Speed-Downlink Shared Channel
HS-PDSCH
High Speed-Physical Downlink Shared Channel
HS-SCCH
High Speed-Shared Control Channel
IR
Incremental Redundancy
OVSF
Orthogonal Variable Spreading Factor
PDU
Protocol Data Unit
QoS
Quality of Service
QPSK
Quadrature Phase Shift Keying
RAB
Radio Access Bearer
RACH
Random Access Channel
RB Radio Bearer
RNC
Radio Network Controller
RNS
Radio Resource System
RRC
Radio Network Control
RT Real Time
SIB System Information Block
SIR Signal-to-Interference Ratio
SRNC
Serving Radio Network Controller
STTD
Space Time Transmit Diversity
TCP/IP Transmission Control Protocol/Internet Protocol

TFCI
Transport Format Combination Indicator
TFRC
Transport Format Resource Combination
TFRI
Transport Format and Resource Indicator
TPCTransmit Power Control

TTI Transmission Time Interval
UE User Equipment
UL Up Link(Reverse Link)
UMTS
Universal Mobile Telecommunications System
URA
UTRAN Registration Area
UTRA
Universal Terrestrial Radio Access
UTRAN Universal Terrestrial Radio Access Network

WCDMA Wideband Code Division Multiple Access
1.3
RNC External Interfaces

RNC external transmission interfaces are shown in Figure 1 -1.
Figure 1-1 RNC external transmission interfaces
1.4
Classification of Transmission Bearer Modes of

RNC External Interfaces
RNC external transmission bearer modes can be divided as described in Table 1 -1..
Table 1-1 Classification of Transmission Bearer Modes of RNC External Interfaces

Type of interface
Interface transmission bearer mode

ATM
IP
Iub interface
ATM+IP
IPoverE1
IPoverE1+IP
ATM
Iu interface (including CS and

PS)
IP
ATM+IP (ATM bears signaling, IP bears services)
IP+ATM (IP bears signaling, ATM bears services)
Iur interface
ATM
IP
When the mixed networking method is used at the Iub interface, usually non-real-time
data service runs on IP bearer of the RNC or NodeB, and real time service, signaling,
and OMCB data stream run on ATM or IPoverE1 bearer.
1.5
Structure of RNC External Interface Protocol

Stack
The structure of RNC external interface protocol stack is shown in Figure 1 -2.
Figure 1-2 Structure of protocol stack
1.6
Principles for RNC Integration

1.
Integrate the control plane first, and then the user plane.
2.
Integrate the control plane and the user plane in the bottom-up order on the
protocol stack.
1.7
Preparation for RNC Integration
1.7.1
Check of Hardware
1.7.2
1.
RNC has been installed and powered on, and is running normally.
2.
RNC has been connected with the interfaces involved in the integration physically.
3.
NodeB has been installed and powered on, and is running normally.
Check of Data Configuration

1.
Related integration parameters have been obtained and data configuration of RNC
has finished.
2.
Data configuration of NodeB has finished.
1.8
Parameter
Integration
1.8.1
SPC Conversion
Conversion
Related
with
RNC
SPC provided by the operator is usually in the format: X-Y (X stands for SSF, and Y
stands for SPC), and the SPC mode (14 bit or 24 bit) will also be specified. When
configure data, we should convert Y into a decimal coding. If the SPC mode is 14 bit, we
will convert it into 3-8-3 mode; if it is 24 bit, we will convert it to 8-8-8 mode.
For example: In the RNC integration of Yanji Unicom in Jilin province, the SPC of
Ericssons MGW is 3-2052 (14 bit), which means SSF=3, SPC=2052, and the SPC
mode is 24 bit.
1.
SSF has 2 bits, and its value is between 0-3. The meaning of each value is shown
in Table 1 -2.
Table 1-2 The Meaning of Each SSF Value

SSF Value
Stands for
00
International network
01
Spare (for international use only)
SSF Value
Stands for
10
National network
11
Reserved for national use
From the above table, if SSF=3, SPC is reserved for national use.
1.8.2
2.
The SPC mode is 14 bit, so it should be converted to 3-8-3 mode.
3.
SPC=2052, which is a hexadecimal coding. We should convert it to a binary digit

first which is 10000001010010, and then according to the 3-8-3 mode, divide it to
001-00000000-100 (If there are less than three digits at the first part, add 0).
Finally, convert each segment into decimal number; the result is 1.0.4.
ATM Address Conversion

ATM takes the address formats as follows.
The commonly used format is E164 at present.

ZTEs M31 supports E164 and NSAP formats, and NASP is the default one.
For example:
If the RNC ATM address provided by the operator is in E164 format: 070320000000000,
then we need to convert it to the NSAP format.
The AFI of the E614 format is 45, which is a hexadecimal number. Put it before
070320000000000, we can get 45070320000000000. And then divide it at two-digit
interval from left to right. If the last segment has only one digit, put an F at the end, for
example 45.07.03.20.00.00.00.00.0F. Finally, convert each two-digit segment into a
decimal number. The result is the ATM address in NSAP format, which is
69.07.03.32.00.00.00.00.15.
1.8.3
PVC Bandwidth Unit Conversion

Usually the bandwidth unit is cps at the CN side, and ZTE uses kpbs in data
configuration at the RNC side. The ATM cell has 53 bytes, therefore 1 cps = 1*53*8 bps
= 424 bps = 0.424 Kbps.
NodeB Integration
Knowledge
Understanding the way of integration at the control plane of the Iub interface.
Learning about the integration of the radio cells.
Being familiar with the OMCB integration in different bearer mode.
2.1
ATM over E1
2.1.1
Description of Integration Parameters for Iub Transmission

Table 2-3 Description of Integration Parameters for Iub Transmission
Protoco
l layer
RNC
default
value
Parameter
NodeB
default
value
Configure
via
jumper
E1/T1 resistance
Physical
layer
Transmi
ssion
network
E1/T1 frame format

E1/T1 long and short cables (currently,
RNC supports short cable only)
Scrambling code type of link direction in
IMA link configuration
IMA
layer
Near-end clock sending mode of IMA

Group
CTC
mode
ITC
mode
Tx frame length and Rx frame length of

IMA group
ATM
PVC type (AAL5, AAL2)

PVC
type
/service
type
PCR
AAL2/
CBR
valid
AAL2/
RTVBR
valid
AAL2/
valid
SCR
MBS
CDVT
valid
valid
valid
valid
Protoco
l layer
RNC
default
value
Parameter
Transmi
ssion
network
NodeB
default
value
UBR
AAL5/
CBR
valid
valid
VPI/VCI
PATH ID (valid only for AAL2)
ATM address
Upper-level user type of AAL5
(NCP,CCP, ALCAP)
CCP port No.
NBAP
NodeB ID
Local cell No.
Tx and Rx frequency points
2.1.2
Iub Integration Description

Follow the bottom-up order on the protocol stack to integrate the physical layer, IMA
layer, ATM layer and NABP layer in turn.
2.1.3
Physical Layer
1.
Check the status of E1 subunit, and query the E1 subunit status of the
corresponding DTB at the RNC side.
To query the state, right-click DTB on the rack figure, select Show Board
Properties Pages > Subunit Configuration > Subunit Detail > State
information > State Query.
If the availability Status and the HW Status are both normal, the subunit status is
normal. If they are abnormal, please check whether theres any problem with the
DTB board, whether E1 is connected properly, and whether DIP and jumper are
normal.
10
Figure 2-3 E1 subunit status
2.
Check E1 L1-L32 on the DTB panel. If the E1 LED indicators are flashing slowly at
1 HZ, all the E1 links are normal.
3.
Check the status of all the E1 lines at the NodeB side, and make sure these E1
links have been added to corresponding IMA group in the configuration at the
NodeB side and the Status is Normal.
Figure 2-4 E1 status at NodeB side
2.1.4
IMA Layer
1.
Check the status of the corresponding IMA E1 link in the RNC.
11
To query the state, click RNC ManagedElement(P) > RNC configuration

centralized management > Dynamic data management object > IMA link.
In the normal status, both Local terminal and Remote terminal of all the IMA E1
links are in the Active state.
Figure 2-5 IMA link status
2.
Check the status of the corresponding IMA group in the RNC

centralized management > Dynamic data management object > IMA group.
If the Local state and the Remote state are both Running, the status of this IMA
group is normal. If it is abnormal, check whether the configuration of the integration
parameters of the two IMA groups, for instance, the scrambling and descrambling
configuration, are consistent.
12
Figure 2-6 IMA group status
2.1.5
ATM Layer
1.
Check the status of corresponding PVC in the RNC. The status at Root side and
Branch side should be both normal.
To query the status, click RNC ManagedElement(P) > RNC configuration
centralized management > Dynamic data management object > PVC.
13
Figure 2-7 PVC status
2.
Check the status of corresponding AAL2 in the RNC. The Administrative status
should be Unblock, the Local Block Status and the Remote Block Status should
be both Not Congested, and the Path Resetting Status should be No.
centralized management > Dynamic data management object > AAL2 PATH.
14
Figure 2-8 AAL2 status
3.
For the AAL5 of non-OMCB type, trace SSCOP at the transport network SAAL
layer. In the normal state, there should be SSCOP keep-alive POLL and STAT
messages sent and received between the RNC and the NodeB.
Figure 2-9 SSCOP keep-active signaling
4.
2.1.6
For the AAL5 of OMCB type, ping the NodeB operation and maintenance address
on the OMCB server. In the normal state, the link between the OMCB and the
NodeB should be able to be established.
NBAP Layer
1.
Query NCP and CCP status of the corresponding NodeB in the RNC.
15

centralized management > Dynamic data management object > NodeB port.
In the normal status, the Administrative State is Unlock, the Operational Status
is Enabled, and the Availability Status of CCP is Normal, the Availability Status
of NCP is unavailable.
Figure 2-10 NCP and CCP status
2.
Check the status of cells under the corresponding NodeB in the RNC.
centralized management > Dynamic data management object > Cell and
Channel..
In the normal status, the Administrative State is Unlock, the Existing State is
Existing, and the Availability Status is Normal.
16
Figure 2-11 Cells status
3.
Log in to the NodeB from the DMS to check whether the common transport
channels are complete. Keep on refreshing the query. In the normal state, there
should be one BCH, one PCH, one RACH and two FACHs all the time.
Figure 2-12 Common transport channels
4.
After the above items have been checked, block and unblock the local cells on the
EOMS, and trace the RNC signaling, there should be cell setup standard
17
signaling.
Figure 2-13 Cell setup standard signaling
5.
Turn on the testing UE and register on the network, there will be messages of
rrcConnectionSetupComplete and initialdirectransfer having been sent from the
UE to the RNC.
Figure 2-14 Direct transfer message
6.
After the above steps are performed, the integration of the Iub interface has been
completed.
2.2
ATM over STM-1
2.2.1
Iub Interface Integration Parameters

ATM over STM-1 and ATM over E1 are two different transmission bearer modes.
Therefore, as to integration, they mainly differ from each other in the integration of the
18
transport layer, while the integrations of the other protocol layers of the two bearer
modes are the same. The basic integration parameters of ATM over STM-1 are shown in
Table 2 -4.
Table 2-4 Iub Integration Parameters in ATM Over STM-1 Bearer Mode
Protocol
layer
Physical
layer
RNC
default
value
Parameter
Transmission
network
NodeB
default
value
Fiber multiplexing structure (SDH-AU4,

SDH-AU3, SONET-STS-3)
ATM OAM functional switch
ATM
PVC type/
service type
PCR
AAL2/CBR
valid
AAL2/RTVBR
valid
AAL2/UBR
valid
AAL5/CBR
valid
SCR
MBS
CDVT
valid
valid
valid
valid
valid
VPI/VCI
ATM address
Upper-level user type AAL5 (NCP, CCP,
ALCAP)
CCP port No.
NBAP
NodeB ID
Local cell No.
2.2.2

Follow the bottom-up order on the protocol stack to integrate the physical layer, IMA
layer, ATM layer and NABP layer in turn.
2.2.3
Physical Layer
1.
Check the state of APBE subunit, and the subunit state of corresponding APBE at
the RNC side. For APBE/2, there is only one subunit; for APBE, there are four
subunits. In the normal state, the subunit Availability Status and HW Status
should both be normal.
To query the state, right-click APBE on the rack figure, and click Show Board
Properties Pages > Subunit Configuration > Subunit Detail > State
19
Figure 2-15 APBE subunit state
2.
Check the state of APBE LED indicators. In the normal state, the ACT LED
indicator should be constantly on.
ACT1-4 and SD1-4 correspond to 1-4 optical interfaces respectively. The ACT1
LED indicator constantly on indicates that the current optical interface is active, and
SD1 LED indicator constantly on indicates that the current optical interface receives
optical signal.
2.2.4
ATM Layer
For integration method, please see Section 2.1.5.
20
2.2.5
NBAP Layer
For integration method, please see Section 2.1.6.
2.3
ATM over CSTM-1
2.3.1
Iub Integration Parameters

ATM over CSTM-1 differs from ATM over E1 in the transmission bearer. Therefore, as to
integration, they mainly differ from each other in the integration of the transport layer,
while the integrations of the other protocol layers of the two bearer modes are the same.
The basic integration parameters of ATM over CSTM-1 are shown in Table 2 -5.
Table 2-5 Iub Integration Parameters in ATM Over CSTM-1 Bearer Mode
Protocol
layer
Physical
layer
RNC
default
value
Parameter
Transmission
network
NodeB
default
value

SDT-PCM arrangement mode
ATM
PVC type/
servic type
PCR
AAL2/CBR
valid
AAL2/RTVBR
valid
AAL2/UBR
valid
AAL5/CBR
valid
SCR
MBS
CDVT
valid
valid
valid
valid
valid
VPI/VCI
ATM address
Upper-level user type AAL5 (NCP, CCP,
ALCAP)
CCP port No.
NBAP
NodeB ID
Local cell No.
2.3.2

Follow the bottom-up order on the protocol stack to integrate physical layer, IMA layer,
21
ATM layer and NABP layer in turn.
2.3.3
Physical Layer
1.
Check the subunit state of SDTB/SDTA, and that of the corresponding board at the
RNC side. SDTB has 63 subunits, and SDTA has 126 subunits. In the normal state,
the subunit Availability Status and HW Status should both be normal.
To query the state, right-click SDTB/SDTA on the rack figure, and select Show
Board Properties Pages > Subunit Configuration > Subunit Detail > State
Figure 2-16 SDTB/SDTA subunit state query
2.
Check the status of all the E1 links at the NodeB side and make sure these E1 links
have been added to the corresponding IMA group in the configuration at the NodeB
side and the Status is Normal.
22
Figure 2-17 E1 link status query
2.3.4
IMA Layer
1.
Check the status of the corresponding IMA E1 link in the RNC.

centralized management > Dynamic data management object > IMA link.
In the normal status, both Local terminal and Remote terminal of all the IMA E1
links are in the Active state.
Figure 2-18 IMA link status
2.
Check the status of the corresponding IMA group in the RNC

centralized management > Dynamic data management object > IMA group.
If the Local state and the Remote state are both Running, the status of this IMA
23
group is normal.
Figure 2-19 IMA group status
2.3.5
ATM Layer
For the integration method, please see Section 2.1.5.
2.3.6
NBAP Layer
24
2.4
IP over E1
2.4.1

Table 2-6 Iub Interface Integration Parameters in the IP Over E1 Mode
Protocol
layer
Physical
layer
Parameter
RNC default
value
Transmission
network
E1/T1 resistance
Resistances of
RNC and NodeB
should be
consistent with
those of the
transmission
network.
E1/T1 frame
format
RNC settings
should be
consistent with
that of the
transmission
network.
NodeB default
value
E1/T1 long and

short cables
(currently, RNC
supports short
cable only)
HDLC
layer
ML-PPP
layer
SCTP
layer
E1 time slot
adopted by
HDLC link
Number of links
in ML-PPP
IP of PPP peer
layers
Four parameters
of SCTP (local
end IP and port
number, peer end
IP and port
number)
IP address in IP
transmission
path, and
bandwidth
CCP port No.
NBAP
Local cell No.

Tx and Rx
frequency points
25
2.4.2

2.4.3
Physical Layer
1.
Check the subunit state of SDTB/SDTA, and that of the corresponding board at the
RNC side. SDTB has 63 subunits, and SDTA has 126 subunits. In the normal state,
the subunit Availability Status and the HW Status should both be normal.
To query the state, right-click SDTB/SDTA on the rack figure, and select Show
Figure 2-20 SDTB/SDTA subunit state
26
2.
Check the status of all the E1 links at the NodeB side and make sure these E1 links
have been added to the corresponding IMA group in the configuration at the NodeB
side and the Status is Normal.
Figure 2-21 E1 link status
2.4.4
HDLC Layer
Check the status of all the HDLCs at the NodeB side, and make sure they are added to
the corresponding ML-PPP group in the configuration at the NodeB side, and the Status
is Normal.
Figure 2-22 HDLC link status
2.4.5
PPP Layer
Trace PPP signaling at the NodeB side in the DMS. There should be PPP_
ECHO_REQUEST and PPP_REPLY messages transmitted alternatively.
27
Figure 2-23 Tracing PPP signaling
2.4.6
IP Layer
Test the connectivity of the IP layer with SLA in the RNC. The source address of the test
is the IP address configured for the DSP of RUB, and the target address is the IP
address of the PPP peer layer. In the normal state, the Send Request Number and the
Receive Reply Number should be the same.
28
Figure 2-24 SLA test
2.4.7
SCTP Layer
Check the state of the NodeB SCTP in the RNC.
To query the state, click RNC ManagedElement(P) > RNC configuration centralized
management > Dynamic data management object > Basic Connection
Configuration Information of SCTP.
In the normal state, Associated State should be ESTABLISHED; Congestion Flag
should be Not congestion; and SSM state should be Activated.
29
Figure 2-25 SCTP status
2.4.8
OMCB
Ping the NodeB operation and maintenance address on the OMCB server. The link
between the OMCB and the NodeB should be able to be established.
2.4.9
NBAP Layer
2.5
IP over FE
2.5.1

Figure 2-26 Iub Interface Integration Parameters in IP Over FE Mode
Protocol
layer
Physical
layer
Parameter
Media type (GE
optical port, GE
cable port, FE
cable port)
RNC default
value
Transmission
network
NodeB default
value
Resistances of
RNC and
NODEB should
be consistent
with those of the
transmission
network.
30
Protocol
layer
Parameter
Negotiation mode
(obligation, selfnegotiate)
RNC default
value
Transmission
network
NodeB default
value
Negotiation
mode
Duplex mode (full

duplex mode,
half duplex
mode)
MTU
IPV4/IPV6
IP layer
SCTP
layer
IP package
fragmenting and
defragmenting
support
Four parameters
of SCTP (RNC IP
and port, NODEB
IP and port)
IP address in IP
transmission path
NodeB ID
CCP port No.
NBAP
Local cell No.

Tx and Rx
frequency points
2.5.2

2.5.3
Physical Layer
1.
Check the state of GIPI subunit, and query the subunit state of the corresponding
board at the RNC side.
GIPI with GE interface has one subunit, which corresponds to one GE optical
port or cable port.
GIPI with FE interface has four interfaces, which correspond to 4 FE cable

ports.
In the normal state, the subunit Availability Status and the HW Status should
both be normal.
31
To query the state, click Show Board Properties Pages > Subunit
Configuration > Subunit Detail > State information > State Query.
Figure 2-27 GIPI subunit state
2.
Check whether there is any problem with the external network port of GIPI, In the
normal state, there should be no such an alarm as External Port of Board is
Down.
32
Figure 2-28 Alarm of GIPI external port
2.5.4
IP Layer
2.5.5
SCTP Layer
2.5.6
NBAP Layer
33
2.6
ATM and IP Mixed Transmission

Interconnect the ATM link and the IP link perceptively; they should be both unblocked.
34
Iu-CS Integration
3.1
ATM Mode
3.1.1
Description of Iu-CS Integration Parameters (E1)

Table 3-7 Description of Iu-CS Integration Parameters (E1)
Protocol
layer
RNC
default
value
Parameter
NodeB
default
value
Configure
via
jumper
E1/T1 resistance
Physical
layer
Transmission
network
E1/T1 frame format

E1/T1 long and short cables (currently, RNC
supports short cable only)
IMA
layer
Near-end clock sending mode of IMA Group
CTC
mode
ITC
mode
Tx frame length and Rx frame length of IMA

group
ATM
PVC
type/service
type
PCR
AAL2/CBR
valid
AAL2/RTVBR
valid
AAL2/UBR
valid
AAL5/CBR
valid
SCR
MBS
CDVT
valid
valid
valid
valid
valid
VPI/VCI
ATM address/ATM address coding plan
Maximum length of SAAL message
signaling package
Signaling point coding
MTP3B
SLC
SSF
Upper-level user type of MTP3 (ALCAP)
35
Protocol
layer
SCCP
RNC
default
value
Parameter
NodeB
default
value
Transmission
network
IT message sending timer of SCCP

IT message receiving timer of SCCP
PLMN
RANAP
RNC ID
LAC
SAC
3.1.2
Description of Iu-CS Integration Parameters (STM-1)

In most scenarios, STM-1 bearer mode is used at the Iu interface (via the optical port of
the APBE board). Only in few pilot offices, the Iu interface is connected via E1 port of the
DTB/IMAB board.
Table 3-8 Description of Iu-CS Integration Parameters (STM-1)

Protocol
layer
Physical
layer
RNC
default
value
Parameter
Transmission
network

ATM
PVC
type/service
type
PCR
AAL2/CBR
valid
AAL2/RTVBR
valid
AAL2/UBR
valid
AAL5/CBR
valid
SCR
MBS
CDVT
valid
valid
valid
valid
valid
VPI/VCI
signaling package
Signaling Point Coding
MTP3B
SLC
SSF
SCCP
IT Message Sending Timer of SCCP

IT Message Receiving Timer of SCCP
36
NodeB
default
value
Protocol
layer
Parameter
RNC
default
value
Transmission
network
NodeB
default
value
PLMN
RANAP
RNC ID
LAC
SAC
3.1.3
Description of Iu-CS Integration

The integration should follow the bottom-up order on the protocol stack: physical layer,
IMA layer, ATM layer, MTP3B layer, SCCP layer, and RANAP layer.
3.1.4
Physical Layer
1.
Check the E1 subunit state, and that of the corresponding DTB board at the RNC
side. The subunit Availability Status and the HW Status should both be normal.
To query the state, right-click the DTB board on the rack figure and select Show
37
Figure 3-29 E1 subunit state query
2.
Check whether the E1 LED indicators L1-L32 on the DTB panel flash at 1 Hz (slow
flash).
3.
For the APBE board in the STM-1 transmission mode, check the subunit state of
the APBE and that of the corresponding APBE board at the RNC side.
APBE/2 has only one subunit.
APBE has four subunits.
In the normal state, the subunit Availability Status and the HW Status should both
be normal.
To query the state, right-click the APBE board on the rack figure and select Show
38
Figure 3-30 APBE subunit state query
3.1.5
IMA Layer
3.1.6
ATM Layer
1.
Check the corresponding PVC state in the RNC.

To query the state, Click RNC ManagedElement(P) > RNC configuration
centralized management > Dynamic data management object > PVC.
The state of the Root side and the Branch side should both be Normal.
39
Figure 3-31 PVC link state
2.
Check the corresponding AAL2 state in the RNC.

To check the state, Click RNC ManagedElement(P) > RNC configuration
centralized management > Dynamic data management object > AAL2 PATH.
In the normal state, the Administrative Status should be Unblock, the Local
Block Status and Remote Block Status should be Not Congestion, and the
Path resetting Status should be No. If multi AAL2 links are configured, you
should block them one by one to make a call test.
40
Figure 3-32 AAL2 link status query
3.
For AAL5, it is required to trace the SSCOP of the SAAL at the transport network
layer. In the normal state, there should be SSCOP keep-alive messages POLL and
STAT sending between the RNC and the MGW.
Figure 3-33 SSCOP link signaling tracing
3.1.7
MTP3B Layer
1.
Check the status of the corresponding No.7 link in the RNC.

To query the state: Click RNC ManagedElement(P) > RNC configuration
41
centralized management > Dynamic data management object > No. 7 link.
In the normal state, MTP3 Link Status should be In Service; Not Congested,
and MTP3 Link Status (traffic) should be No Alarm; Normal.
Figure 3-34 No. 7 link status
2.
Query the status of the adjacent office signaling point in RNC.

To query the status, Click RNC ManagedElement(P) > RNC configuration
centralized management > Dynamic data management object > Adjacent
Office signaling point.
In the normal state, Access Flag should be Accessible. Right-click an office ID,
you can see information of the current route.
42
Figure 3-35 Adjacent office signaling point status
43
Figure 3-36 Office route query
3.
The status of adjacent office signaling point can also be queried by tracing the
signaling of the MTP3B layer in the RNC. In the normal state, you can see the RNC
send the SLTM message, the MGW reply with the SLTA message, and the MGW
send the SLTM message, the RNC replies with the SLTA message. That means
the transmission at the MTP3B layer is unblocked, and the adjacent office signaling
point is reachable.
Figure 3-37 Signaling link test result
3.1.8
SCCP Layer and RANAP Layer

For the SCCP layer, when the UE location is changed, trace the signaling at the SCCP
layer. If there are the CR and CC messages, and no alarm about the subsystem 1 or
142, the SCCP layer is normal.
44
Figure 3-38 SCCP connection establishment messages
After the above steps are performed, the integration of the Iu-CS interface is completed.
3.2
IP Mode
3.2.1
Description of Iu-CS Integration Parameters

Table 3-9 Iu-CS Integration Parameters
Protocol
layer
Physical
layer
Parameter
RNC
default
value
Transmission
network
Media type (GE optical

port, GE cable port, FE
cable port)
Resistance of RNC
and NodeB should
be consistent with
that of the
transmission
network.
Negotiation mode
RNC settings
should be
consistent with that
of the transmission
network.
NodeB
default
value
Duplex mode (full duplex

mode, half duplex mode)
MTU
IPV4/IPV6
IP layer
IP package fragmenting
and defragmenting
support
Four parameters of
SCTP (RNC IP and port,
NODEB IP and port)
SCTP
layer
IP address in IP
transmission path
SCTP CRC check mode
SCTP client/server mode
M3UA
Network profile
Routing CONTEXTID
45
Protocol
layer
Parameter
RNC
default
value
Transmission
network
NodeB
default
value
APP server AS usage ID

AS traffic mode
N value of load sharing
mode
IT Message Sending
Timer of SCCP
SCCP
IT Message Receiving
Timer of SCCP
Subsystem 1, 142
PLMN
RANAP
RNCID
LAC
SAC
3.2.2
Description of Iu-CS Integration

The Iu-CS integration should follow the bottom-up order on the protocol stack: physical
layer, IP layer, SCTP layer, M3UA layer, SCCP layer, and RANAP layer.
3.2.3
Physical Layer
1.
GIPI board at the RNC side.
port or cable port.
GIPI with FE interface has four interfaces, which correspond to four FE cable
ports.
In the normal state, the subunit Availability Status and the HW Status should be
normal.
To query the state, right-click GIPI board on the rack figure, and select Show
46
2.
Check whether there is any problem with the GIPI external port. In the normal state,
there is no such an alarm as External Port of Board is Down.
47
3.2.4
IP Layer
In the RNC test the connectivity of the IP layer with the SLA. The Send Request
Number and the Receive Reply Number should be the same.
The source address of test is the IP address configured for the DSP of the RUB,
and the target address is the address configured for the user plane of MSC/MGW.
The source address of test is the IP address configured for SCTP, and the target
address is the SCTP address configured for SGSN.
48
3.2.5
SCTP Layer
Check the state of the MSC SCTP in the RNC.
To query the state, click RNC ManagedElement(P) > RNC configuration centralized
management > Dynamic data management object > Basic Connection
Configuration Information of SCTP.
In the normal state, Associated State should be ESTABLISHED; Congestion Flag
State should be Not Congestion; and SSM State should be Activated.
49
Figure 3-42 SCTP state
3.2.6
M3UA Layer
1.
In the RNC, query the state of the AS and ASP used at the M3UA layer.
To query the state, Click RNC ManagedElement(P) > RNC configuration
centralized management > Dynamic data management object > As and Asp.
The AS State and ASP State should be Active.
50
Figure 3-43 AS and ASP state
2.
In the RNC, query the state of the office maintained by the M3UA.
To check the state, click RNC ManagedElement(P) > RNC configuration
centralized management > Dynamic data management object > Adjacent
Office signaling point.
In the normal state, information of the active route can be checked.
51
Figure 3-44 Active route information
3.2.7

layer. If there are CR and CC messages, and no alarm about the subsystem 1 or 142,
the SCCP layer is normal.
Figure 3-45 SCCP connection establishment
After the above steps are performed, the integration of the Iu-CS interface is completed.
52
Iu-PS Integration
4.1
ATM Mode
4.1.1
Description of Iu-PS Integration Parameters (E1)

Table 4-10 Description of Iu-PS Integration Parameters (E1)
Protocol
layer
RNC
default
value
Parameter
NodeB
default
value
Configure
via
jumper
E1/T1 resistance
Physical
layer
Transmission
network
E1/T1 frame format

E1/T1 long and short cables (currently,
RNC supports short cable only)
IMA
layer
Near-end clock sending mode of IMA

Group
CTC
mode
ITC
mode
Tx frame length and Rx frame length of

IMA group
PVC type (SIG_AAL5, USER_AAL5)
ATM
PVC
type/service
type
PCR
AAL5/CBR
valid
SCR
MBS
CDVT
valid
VPI/VCI
signaling
MTP3B
SLC
SSF
SCCP

Subsystem 1,143
RANAP
PLMN
RNC ID
LAC
53
Protocol
layer
RNC
default
value
Parameter
Transmission
network
NodeB
default
value
SAC
GTP-U
4.1.2
Destination GTP-U address

Local GTP-U address and mask
Description of Iu-PS Integration Parameters (STM-1)

In most scenarios, STM-1 bearer mode is used on the Iu interface (connected via the
optical port of the APBE board). Only in few pilot offices, the Iu interface is connected by
an E1 on the DTB/IMAB board.
Table 4-11 Description of Iu-PS Integration Parameters (STM-1)

Protocol
layer
Physical
layer
RNC
default
value
Parameter
Transmission
network
Configure
via
jumper

PVC type (SIG_AAL5, USER_AAL5)
ATM
PVC
type/service
type
PCR
AAL5/CBR
valid
SCR
MBS
CDVT
valid
VPI/VCI
signaling
MTP3B
SLC
SSF
SCCP

Subsystem 1,143
PLMN
RANAP
RNC ID
LAC
SAC
GTP-U
Destination GTP-U address
54
NodeB
default
value
Protocol
layer
Parameter
RNC
default
value
Transmission
network
NodeB
default
value
Local GTP-U address and mask
4.1.3
Description of Iu-PS Integration

4.1.4
Physical Layer
4.1.5
IMA Layer
4.1.6
ATM Layer
4.1.7
MTP3B Layer
4.1.8

4.1.9
GTP-U Layer
In the RNC, test the connectivity of the IP layer with the SLA. The source IP address is
the GTP-U address configured at the RNC side and the target IP address the GTP-U
address configured for the SGSN. In the normal state, the Send request Number is the
same as the Receive reply Number.
55
4.2
IP Mode
4.2.1
Description of Iu-PS Integration Parameters

Table 4-12 Description of Iu-PS Integration Parameters
Protocol
layer
Physical
layer
Parameter
Media type (GE

optical port, GE
cable port, FE
cable port)
Negotiation mode
RNC
default
layer
Transmission
network
NodeB
default
layer
Resistances of RNC
and NodeB should
be consistent with
those of the
transmission
network.
RNC settings should
be consistent with
those of the
transmission
network.
56
Protocol
layer
Parameter
RNC
default
layer
Transmission
network
NodeB
default
layer
Duplex mode (full

duplex mode, half
duplex mode)
MTU
IPV4/IPV6
IP layer
IP package
fragmenting and
defragmenting
support
Four parameters of
SCTP
(RNC IP and port,
NodeB IP and port)
SCTP
layer
IP address in IP
transmission path
SCTP CRC check
mode
SCTP client/server
mode
Network profile
Routing context ID
M3UA
APP server as
usage ID
AS traffic mode
N value of load
sharing mode
IT message
sending timer of
SCCP
SCCP
IT message
receiving timer of
SCCP
Subsystem 1,142
PLMN
RANAP
RNCID
RAC
SAC
GTP-U
Destination GTP-U
address
Local GTP-U
address and mask
57
4.2.2
Description of Iu-PS Integration

IP layer, SCTP layer, M3UA layer, SCCP layer, and RANAP layer.
4.2.3
Physical Layer
1.
GIPI board at the RNC side.
port or cable port.
GIPI with FE interface has four interfaces, which correspond to four FE cable
ports.
In the normal state, the subunit Availability Status and the HW Status should be
normal.
To query the state, right-click GIPI board on the rack figure, and select Show
58
2.
Check whether there is any problem with the GIPI external port. In the normal state,
there is no such an alarm as External Port of Board is Down.
59
4.2.4
IP Layer
In the RNC, test the connectivity of the IP layer with the SLA. The Send Request
Number and the Receive Reply Number should be the same.
The source address of test is the IP address configured for the DSP of the RUB,
and the target address is the address configured for the user plane of MSC/MGW.
The source address of test is the IP address configured for SCTP, and the target
address is the SCTP address configured for SGSN.
60
4.2.5
SCTP Layer
4.2.6
M3UA Layer
4.2.7

layer. If there are CR and CC messages, and no alarm about the subsystem 1 or 142,
the SCCP layer is normal.
61
After the above steps are performed, the integration of the Iu-PS interface is completed.
62
Iur Integration
5.1
ATM Mode
5.1.1
Description of Iur Integration Parameters

Table 5-13 Description of Iur Integration Parameters
Protocol
layer
Physical
layer
RNC
default
value
Parameter
Transmission
network
Configure
via
jumper

ATM
PVC
type/service
type
PCR
AAL2/CBR
valid
AAL2/RTVBR
valid
AAL2/UBR
valid
AAL5/CBR
valid
SCR
MBS
CDVT
valid
valid
valid
valid
valid
VPI/VCI
signaling
MTP3B
SLC
SSF
IT Message sending timer of SCCP
SCCP
IT Message receiving timer of SCCP

Subsystem 1,143
PLMN
RNSAP
RNC ID
LAC
SAC
63
NodeB
default
value
5.1.2
Description of Iur Integration

5.1.3
Physical Layer
5.1.4
ATM Layer
5.1.5
MTP3B Layer
5.1.6
SCCP Layer and RNSAP Layer

For the SCCP layer, perform an inter-Iur interface soft handover. When the message of
radio link addition request is detected at the Iur interface, trace the SCCP layer. There
should be CR and CC messages, and no alarm about the subsystem 1 or 142.
After the above steps are performed, the integration of the Iur interface is completed.
64
5.2
IP Mode
5.2.1
Description of Iur Integration Parameters

Table 5-14 Description of Iur Integration Parameters
Protocol
layer
Physical
layer
Parameter
RNC default
layer
Transmission
network
Media type (GE

optical port, GE
cable port, FE
cable port)
Resistances of
RNC and NodeB
should be
consistent with
those of the
transmission
network
Negotiation mode
RNC settings
should be
consistent with
those of the
transmission
network
NodeB
default
value
Duplex mode (full

duplex mode, half
duplex mode)
MTU
IPV4/IPV6
IP layer
IP package
fragmenting and
defragmenting
support
Four parameters of
SCTP
(RNC IP and port,
NodeB IP and port)
SCTP
layer
IP address in IP
transmission path
SCTP CRC check
mode
SCTP client/server
mode
Network profile
M3UA
Routing
CONTEXTID
APP server AS
usage ID
AS traffic mode
65
Protocol
layer
Parameter
RNC default
layer
Transmission
network
NodeB
default
value
N value of load
sharing mode
SCCP
IT Message
Sending Timer of
SCCP
IT Message
Receiving Timer of
SCCP
PLMN
RANSAP
RNCID
LAC
SAC
5.2.2
Description of Iur Integration

IP layer, SCTP layer, M3UA layer, SCCP layer, and RANAP layer.
5.2.3
Physical Layer
5.2.4
IP Layer
5.2.5
SCTP Layer
5.2.6
M3UA Layer
5.2.7
SCCP Layer and RNSAP Layer

66

ZXWR RNC (V3 (1) .09.30) Commissioning Guide - Integration Manual - R1.0

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

ZXWR RNC (V3 (1) .09.30) Commissioning Guide - Integration Manual - R1.0

Uploaded by

Copyright:

Available Formats

ZXWR RNC (V3.09.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

http://dms.zte.com.cn (Technical Support)

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

Reason for Revision

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

About This Document

1 Introduction to RNC System

Introduction to RNC system integration

Description of NodeB integration

Description of Iu-CS integration

Description of Iu-PS integration

Description of Iur integration

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

2.4.9 NBAP Layer........................................................................................................30

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

5.1.1 Description of Iur Integration Parameters...........................................................63

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

Figure 1-1 RNC external transmission interfaces..........................................................4

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

Figure 2-27 GIPI subunit state.......................................................................................32

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

Understanding the common used WCDMA acronyms and abbreviations.

Getting to know the interfaces involved in the RNC integration.

Understanding the transmission bearer modes used at different interfaces.

Getting to know the protocol structure of different interfaces.

Understanding the principles of RNC integration.

Learning about the preparations for the RNC integration.

Acronyms and Abbreviations

16 Quadrature Amplitude Modulation

Adaptive Modulation and Coding

Adaptive Multi Rate

Asynchronous Transfer Mode

Cell Broadcast Service

CCTrCH Coded Composite Transport Channel

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXWR RNC (V3.09.30) Commissioning Guide Internal Use Only

Common Pilot Channel