Professional Documents
Culture Documents
ZXWR RNC (V3 (1) .09.30) Commissioning Guide - Integration Manual - R1.0
ZXWR RNC (V3 (1) .09.30) Commissioning Guide - Integration Manual - R1.0
30)
Commissioning Guide
Integration Manual
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:
Email:
Revision History
Product Version
V3.09.30
Document Version
Serial Number
R1.0
Author
Date
2010-07-15
Document Version
R1.0
Prepared
by
Hu Zhigang
Reviewed by
Chen Taiming
Approved by
Chen Taiming
II
Description
2 NodeB Integration
3 Iu-CS Integration
4 Iu-PS Integration
5 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.2 Iub Integration Description..................................................................................19
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.2 Iub Integration Description..................................................................................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.1 Iub Interface Integration Parameters..................................................................25
2.4.2 Iub Integration Description..................................................................................26
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
VI
FIGURES
VII
VIII
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
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
AMC
AMR
ATM
CBS
CPICH
HS-DSCH
HS-PDSCH
HS-SCCH
IR
Incremental Redundancy
OVSF
PDU
QoS
Quality of Service
QPSK
RAB
RACH
RB Radio Bearer
RNC
RNS
RRC
RT Real Time
SIB System Information Block
SIR Signal-to-Interference Ratio
SRNC
STTD
TFRC
TFRI
URA
UTRA
1.3
1.4
Iub interface
ATM+IP
IPoverE1
IPoverE1+IP
ATM
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
1.6
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
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.
Related integration parameters have been obtained and data configuration of RNC
has finished.
2.
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.
Stands for
00
International network
01
SSF Value
Stands for
10
National network
11
From the above table, if SSF=3, SPC is reserved for national use.
1.8.2
2.
3.
1.8.3
NodeB Integration
Knowledge
Understanding the way of integration at the control plane of the Iub interface.
2.1
ATM over E1
2.1.1
RNC
default
value
Parameter
NodeB
default
value
Configure
via
jumper
E1/T1 resistance
Physical
layer
Transmi
ssion
network
IMA
layer
CTC
mode
ITC
mode
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
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
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.
2.1.4
IMA Layer
1.
11
2.
12
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
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.
To query the status, click RNC ManagedElement(P) > RNC configuration
centralized management > Dynamic data management object > AAL2 PATH.
14
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.
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
2.
Check the status of cells under the corresponding NodeB in the RNC.
To query the status, click RNC ManagedElement(P) > RNC configuration
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
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.
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.
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.
6.
After the above steps are performed, the integration of the Iub interface has been
completed.
2.2
2.2.1
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
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
PATH ID (valid only for AAL2)
ATM address
Upper-level user type AAL5 (NCP, CCP,
ALCAP)
CCP port No.
NBAP
NodeB ID
Local cell No.
Tx and Rx frequency points
2.2.2
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
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
2.3.1
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
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
PATH ID (valid only for AAL2)
ATM address
Upper-level user type AAL5 (NCP, CCP,
ALCAP)
CCP port No.
NBAP
NodeB ID
Local cell No.
Tx and Rx frequency points
2.3.2
21
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
information > 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
2.3.4
IMA Layer
1.
2.
23
group is normal.
2.3.5
ATM Layer
For the integration method, please see Section 2.1.5.
2.3.6
NBAP Layer
For the integration method, please see Section 2.1.6.
24
2.4
IP over E1
2.4.1
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
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
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
Board Properties Pages > Subunit Configuration > Subunit Detail > State
information > State Query.
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.
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.
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
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
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
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
For the integration method, please see Section 2.1.6.
2.5
IP over FE
2.5.1
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
(obligation, selfnegotiate)
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
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.
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.
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
2.5.4
IP Layer
For the integration method, please see Section 2.4.6.
2.5.5
SCTP Layer
For the integration method, please see Section 2.4.7.
2.5.6
NBAP Layer
For the integration method, please see Section 2.1.6.
33
2.6
34
Iu-CS Integration
3.1
ATM Mode
3.1.1
RNC
default
value
Parameter
NodeB
default
value
Configure
via
jumper
E1/T1 resistance
Physical
layer
Transmission
network
IMA
layer
CTC
mode
ITC
mode
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
PATH ID (valid only for AAL2)
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
RANAP
RNC ID
LAC
SAC
3.1.2
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
PATH ID (valid only for AAL2)
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)
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
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
Board Properties Pages > Subunit Configuration > Subunit Detail > State
information > State Query.
37
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.
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
Board Properties Pages > Subunit Configuration > Subunit Detail > State
information > State Query.
38
3.1.5
IMA Layer
For the integration method, please see Section 2.1.4.
3.1.6
ATM Layer
1.
39
2.
40
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.
3.1.7
MTP3B Layer
1.
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.
2.
42
43
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.
3.1.8
44
After the above steps are performed, the integration of the Iu-CS interface is completed.
3.2
IP Mode
3.2.1
Physical
layer
Parameter
RNC
default
value
Transmission
network
Resistance of RNC
and NodeB should
be consistent with
that of the
transmission
network.
Negotiation mode
(obligation, selfnegotiate)
RNC settings
should be
consistent with that
of the transmission
network.
NodeB
default
value
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
IT Message Receiving
Timer of SCCP
Subsystem 1, 142
PLMN
RANAP
RNCID
LAC
SAC
3.2.2
3.2.3
Physical Layer
1.
Check the state of GIPI subunit, and query the subunit state of the corresponding
GIPI 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 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
Board Properties Pages > Subunit Configuration > Subunit Detail > State
information > State Query.
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
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
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
3.2.7
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
RNC
default
value
Parameter
NodeB
default
value
Configure
via
jumper
E1/T1 resistance
Physical
layer
Transmission
network
IMA
layer
CTC
mode
ITC
mode
ATM
PVC
type/service
type
PCR
AAL5/CBR
valid
SCR
MBS
CDVT
valid
VPI/VCI
Maximum length of SAAL message
signaling
Signaling point coding
MTP3B
SLC
SSF
IT message sending timer of SCCP
SCCP
RANAP
PLMN
RNC ID
LAC
53
Protocol
layer
RNC
default
value
Parameter
Transmission
network
NodeB
default
value
SAC
GTP-U
4.1.2
Physical
layer
RNC
default
value
Parameter
Fiber multiplexing structure (SDH-AU4,
SDH-AU3, SONET-STS-3)
Transmission
network
Configure
via
jumper
ATM
PVC
type/service
type
PCR
AAL5/CBR
valid
SCR
MBS
CDVT
valid
VPI/VCI
Maximum length of SAAL message
signaling
Signaling point coding
MTP3B
SLC
SSF
IT message sending timer of SCCP
SCCP
RANAP
RNC ID
LAC
SAC
GTP-U
54
NodeB
default
value
Protocol
layer
Parameter
RNC
default
value
Transmission
network
NodeB
default
value
4.1.3
4.1.4
Physical Layer
For the integration method, please see Section 3.1.4.
4.1.5
IMA Layer
For the integration method, please see Section 3.1.5.
4.1.6
ATM Layer
For the integration method, please see Section 3.1.6.
4.1.7
MTP3B Layer
For the integration method, please see Section 3.1.7.
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
Parameter
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
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
4.2.3
Physical Layer
1.
Check the state of GIPI subunit, and query the subunit state of the corresponding
GIPI 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 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
Board Properties Pages > Subunit Configuration > Subunit Detail > State
information > State Query.
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
For the integration method, please see Section 3.2.5.
4.2.6
M3UA Layer
For the integration method, please see Section 3.2.6.
4.2.7
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
RNC
default
value
Parameter
Fiber multiplexing structure (SDH-AU4,
SDH-AU3, SONET-STS-3)
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
PATH ID (valid only for AAL2)
ATM address/ATM address coding plan
Maximum length of SAAL message
signaling
Signaling point coding
MTP3B
SLC
SSF
Upper-level user type of MTP3 (ALCAP)
IT Message sending timer of SCCP
SCCP
RNSAP
RNC ID
LAC
SAC
63
NodeB
default
value
5.1.2
5.1.3
Physical Layer
For the integration method, please see Section 3.1.4.
5.1.4
ATM Layer
For the integration method, please see Section 3.1.6.
5.1.5
MTP3B Layer
For the integration method, please see Section 3.1.7.
5.1.6
After the above steps are performed, the integration of the Iur interface is completed.
64
5.2
IP Mode
5.2.1
Physical
layer
Parameter
RNC default
layer
Transmission
network
Resistances of
RNC and NodeB
should be
consistent with
those of the
transmission
network
Negotiation mode
(obligation, selfnegotiate)
RNC settings
should be
consistent with
those of the
transmission
network
NodeB
default
value
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
5.2.3
Physical Layer
For the integration method, please see Section 4.2.3.
5.2.4
IP Layer
For the integration method, please see Section 4.2.4.
5.2.5
SCTP Layer
For the integration method, please see Section 4.2.5.
5.2.6
M3UA Layer
For the integration method, please see Section 4.2.6.
5.2.7
66