Ip Dual Iub NSN

Nokia Siemens Networks WCDMA RAN, Rel.
RU20, Operating Documentation, Issue 03
Activating RAN74, RAN1634, RAN1449, and RAN1633: IP Based Iub and Dual Iub
DN70481473 Issue 02B Approval Date 2010-06-11
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2010. All rights reserved
Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures. Non-observance of these conditions and the safety instructions can result in personal injury or in property damage. Therefore, only trained and qualified personnel may install and maintain the system. The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.
The same text in German: Wichtiger Hinweis zur Produktsicherheit In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen. Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und Sachschden fhren. Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet. Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
Id:0900d8058076d397
DN70481473 Issue 02B
Table of Contents
This document has 38 pages. Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1 2 3 4 5 6 7 8 Activating IP based Iub for Flexi WCDMA BTS . . . . . . . . . . . . . . . . . . . . 9 Activating IP based Iub for UltraSite WCDMA BTS . . . . . . . . . . . . . . . . 15 Verifying IP based Iub for Flexi and UltraSite WCDMA BTS . . . . . . . . . 21 Deactivating IP based Iub for Flexi and UltraSite WCDMA BTS . . . . . . 22 Activating Dual Iub for Flexi WCDMA BTS . . . . . . . . . . . . . . . . . . . . . . 23 Activating Dual Iub for UltraSite WCDMA BTS . . . . . . . . . . . . . . . . . . . 29 Verifying Dual Iub for Flexi and UltraSite WCDMA BTS . . . . . . . . . . . . 37 Deactivating Dual Iub for Flexi and UltraSite WCDMA BTS . . . . . . . . . 38
Id:0900d8058076d397
List of Figures
Figure 1 Figure 2 Figure 3 Figure 4 IP-based Iub connectivity for Flexi WCDMA BTS . . . . . . IP-based Iub connectivity for UltraSite WCDMA BTS. . . Dual Iub connectivity for Flexi WCDMA BTS . . . . . . . . . Dual Iub connectivity for UltraSite WCDMA BTS . . . . . . ...... ...... ...... ...... .......9 . . . . . . 15 . . . . . . 24 . . . . . . 30
Id:0900d8058076d397
List of Tables
Table 1 Table 2 Allowed combinations for transport bearers on IP transport network . . 23 Allowed combinations for transport bearers on IP transport network . . 29
Id:0900d8058076d397
Summary of Changes
Summary of Changes
Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues. Please note that our issue numbering system is changing. For more information, see Guide to WCDMA RAN operating documentation. Changes between issues 02A (2010-03-24, WCDMA RAN RU20) and 02B (2010-0611, WCDMA RAN RU20) Activating IP based Iub for Flexi WCDMA BTS (1) A reference to a technical note has been added. Activating IP based Iub for UltraSite WCDMA BTS (2) A reference to a technical note has been added. A feature code for the RAN1634 feature has been changed. Activating Dual Iub for Flexi WCDMA BTS (5) Steps for configuring VLAN in the RNC were added in Configure the IP layer resources for the Iub user plane. A reference to a technical note has been added. Activating Dual Iub for UltraSite WCDMA BTS (6) Steps for configuring VLAN in the RNC were added in Configure the IP-layer resources for the Iub user plane with the MML interface. A reference to a technical note has been added.
Changes between issues 02 (2009-12-02, WCDMA RAN RU20) and 02A (2010-0324, WCDMA RAN RU20) BFD configuration commands have been corrected. A note about BTS reset during the activation has been added.
Activating IP based Iub for Flexi WCDMA BTS, Activating IP based Iub for UltraSite WCDMA BTS Warning has been added that ICSU static IP route is deleted when disconnecting IPNB from WBTS object. Note has been added that Iub MTU size changes require respective change in the ICSU MTU size.
Changes between issues 1-2 and 02 Chapter Activating Dual Iub for UltraSite WCDMA BTS has been added. Activating IP based Iub for Flexi WCDMA BTS Connection concept in figure IP-based Iub connectivity for Flexi WCDMA BTS has been modified. Instructions in Configure the IP-based Iub in Flexi WCDMA BTS have been updated. Step Configure DCN for RNC has been added. Parameters names have been corrected and updated.
Id:0900d8058076d394
Summary of Changes
Hardware requirements have been updated. Step Enable and check administrative status of IFGE0 has been added. Connection concept in figure IP-based Iub connectivity for UltraSite WCDMA BTS has been modified. Step Configure the IP-based Iub on the transport module in UltraSite WCDMA BTS (AXC) has been updated. Step Configure DCN for RNC has been added. Parameters names have been corrected and updated. Hardware requirements have been updated. Step describing configuration of Communication Control Port ID has been updated. Table Allowed combinations for transport bearers on IP transport network has been added. Hardware requirements have been updated. Step Configure the Dual Iub in the RNC RNW Object Browser GUI has been clarified. Steps in Configure the Dual Iub in Flexi WCDMA BTS have been expanded and clarified. Parameters names have been corrected and updated.
Activating IP based Iub for UltraSite WCDMA BTS
Activating Dual Iub for Flexi WCDMA BTS
Id:0900d8058076d394
Summary of Changes
Id:0900d8058076d394
Activating IP based Iub for Flexi WCDMA BTS
1 Activating IP based Iub for Flexi WCDMA BTS

Purpose Follow the procedure below to activate feature RAN74: IP based Iub for Flexi WCDMA BTS. For more information on the feature, see RAN74: IP based Iub for Flexi WCDMA BTS in WCDMA RAN, rel. RU10, feature descriptions. Exemplary reference configurations using this feature are presented in Configuring WCDMA RAN transport document. The configuration examples in the activation instructions use the IP addressing presented in figure IP-based Iub connectivity for Flexi WCDMA BTS.
Figure 1
IP-based Iub connectivity for Flexi WCDMA BTS
Before you start Enabling IP-based Iub requires the following interface units in the RNC: in RNC2600, the NPGE Gigabit Ethernet interface unit - RAN77: RNC Ethernet Physical Interface feature in RNC196/450, IP-interface upgrade - RAN1225: IP Interface Upgrade for RNC196 and RNC450 feature
In the Flexi WBTS, an FTIA, FTIB, FTJA, FTFB, or FTLB hybrid PDH/Ethernet transport sub-module is required. The feature is an optional application with a separate license control. This feature belongs to the application software. Before you activate the feature, make sure you have a valid license (a file including the feature information) installed. Before a licensed feature can be activated, the license must be transferred and installed in the RNC. For information on transferring the license to the RNC, see License management operations in RNC in WCDMA RAN license operation. You can install the license by using NetAct or a local MML interface. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. If you use the MML interface, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. When installing a new increment, the previously set state remains as the default.
Id:0900d805807861b2
For the specific instructions on the license installation in the RNC, see W7L INSTALL OR UPDATE LICENCE in W7 - Licence and Feature Handling. For more information, see Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN . Use the ZW7 command to activate the license for the feature with feature code 1079. Note that the license is capacity based, and the measure of the capacity is the number of BTSs. If the IP-based Iub is not ON, the IP based route ID cannot be configured. RNW configuration has to be done according to the network plan. Configuration can be created by using either the RNW object browser (RNC EM application) or the RNW plan interface. The IP-layer configuration can be managed using the local MML interface or the IP plan interface from NetAct. The following parameters are related to this feature: IPNB parameters for IP Iub control plane connections: IPNBId WBTSId IPBasedRouteId MinSCTPPortIub NodeBIPAddress NBAPDSCP CNBAP SCTPPortNumberCNBAP DNBAPList DNBAP CControlPortID SCTPPortNumberDNBAP IubTransportMedia IPNBId IPBasedRouteId MinUDPPortIub DSCPMedDCH DSCPLow DSCPHigh DSCPMedHSPA HSDPAULCToDSCP HSUPADLCToDSCP ToAWEOffsetNRTDCHIP ToAWEOffsetRTDCHIP ToAWSOffsetNRTDCHIP ToAWSOffsetRTDCHIP
WBTS parameters for IP Iub user plane connections:
The parameters can be configured with the RNC RNW object browser GUI.
10
Id:0900d805807861b2
BTS parameters can be configured with the BTS Site Manager or NetAct. For more information about BTS parameters, see Plan Editor Flexi Transport Module Parameters. Restart of the WBTS is required after activation of this feature.
g In case RNC and BTS are configured to the same Layer 2 broadcast domain(s) (for
example to the same VLANs), the IP addressing used for the user plane traffic and BFD sessions termination requires a special emphasis. For more details, see Technical Support Note, TN-RNC-SW-146 in NOLS. Steps 1 Configure the IP-based Iub in the RNC with the MML interface.
g If NPGEP unit is used, all physical connections must be plugged in during creation
of IFGEx otherwise all the NPGEP units report a fault and NPGEP with any missing Ethernet connection restarts. If VLAN is used: a) Enable and check administrative status of IFGE0: ZQRN:NPGE,0:IFGE0:::::UP; ZQRI; b) Create a VLAN interface to the NPGE-0 unit. The VLAN name is 'VL1', VLAN ID is 2 (VLAN ID can have value between 2 to 4094), the VLAN is attached to the physical interface IFGE0. ZQRM:NPGE,0:VL1:2:IFGE0; c) Configure the IP address of the VLAN interface. ZQRN:NPGE,0:VL1:10.2.1.1,P:29:; g Pay attention to the IP address planning with the VLAN configuration at system level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option. If VLAN is not used: d) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; ZQRI:NPGE,0:; Proceed with the configuration for both cases: e) Configure the gateway for the NPGE to the external router: ZQKC:NPGE,0:10.3.1.0,30:10.2.1.2:LOG; f) Create a DSPM (DSCP to PHB mapping) profile for the Ethernet interface (IFGE0): Refer to the ZQ8B command in the MML manual. This is optional; also a default value can be used. g) Assign a DSPM profile to an IP interface in the NPGE by using the given profile ID or the default profile ID: ZQ8S:NPGE,0:IFGE0:ENA::; h) Check the internal IPoATM from the NPGE to ICSU: ZQMQ:ICSU,0::NPGE,0:::ALL; i) Configure the Iub control plane subnet for ICSU units: ZQMN:1:10.1.1.0,26:; ZQML:; g The system configures the MTU for ICSU IP over ATM interface to value 1472 for the automatically generated internal full mesh IPoA. The ICSU Iub IPoA inter-
Id:0900d805807861b2
11
j)
face MTU value should not be configured greater than 1472 in order to keep the SCTP layer fragmentation aligned with the BTS SCTP defragmentation functionality. If the MTU size on Iub is configured to be smaller than 1500, respectively the MTU size for ICSU unit has to be descreased (with the MML ZQRN command) to avoid fragmentation at NPGE. Configure the IP based route to the IFGE0 for the Iub. Enter values for the bandwidth allocation according to the transport network dimensioning plan: ZQRU:ADD:1,"IUBWBTS1":8000:500:100:100:ON; ZQRC:NPGE,0:IFGE0:IPV4=10.2.1.1:ID=1:; or in case VLAN is used: ZQRC:NPGE,0:VL1:IPV4=10.2.1.1:ID=1:;
Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS.
g BFD configuration is an optional step.

a) Configure the BFD profile: ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure the BFD session between the RNC and BTS: ZYGS:C:NPGE,0,1,10.2.1.1,10.3.1.1:PROF=1,ALARM=OFF; c) Set the BFD session state to enabled and the alarm state to on when the BTS is integrated to the RNC: ZYGS:S:NPGE,0,1:ALARM=ON,MODE=0; 3 Configure DCN for the RNC. For instructions on configuring RNC (OMU) for data communication network (DCN), see Configuring IP stack in OMU in Configuring IP connection for RNC. 4 Configure the IP-based Iub in the RNC RNW Object Browser GUI.
f The system configures the static IP route in ICSU towards Control Plane Destination Address Iub. When the IPNB object is disconnected from the WBTS, the static IP route is deleted based on its ROUTE NUMBER. Do not delete the static IP route manually, as it may cause a situation where the ROUTE NUMBER which might be used by other manually created IP routes, is removed while the IPNB object is disconnected from the WBTS. a) Open the RNC RNW Object Browser GUI. b) Create the IPNB object for the IP-based Iub control plane connections by selecting Object h New h IP Iub h IPNB. 1. Provide the IPNB with an object identifier. 2. Give BTS CP/UP 10.3.1.1 IP address as a Control Plane Destination Address Iub. 3. The IP Based Route Identification value is retrieved from the WBTS object once IPNB and WBTS are connected (when the IPNB ID is set in the WBTS and the corresponding IPNB exists in the system). 4. Configure minSCTPPort (Minimum SCTP port number). Make sure that the SCTP Port ID have a unique value.
12
Id:0900d805807861b2
5. In the D-NBAP List enter 1 for the Communication Control Port ID; the SCTP Port Number for D-NBAP is automatically calculated. c) Create or modify the WBTS object so that it contains the IPNB reference and IP Iub user plane configuration. Ensure that the IPNB is selected, the IP Based Route ID is given, and the Iub Transport media selection is IP Iub. 1. Configure IPNBId (IPNB object identifier) into the WBTS data. 2. Set the attributes related to IP-based Iub user plane correctly. Set IPBasedRouteIdIub so that it refers to the IP based route configured per MML ZQRU / ZQRC for the given BTS. In the example provided, value 1 is used. In the IubTransportMedia (Iub Transport Media Selection) parameter, check IP Iub only. The default values can be used for MinUDPPortIub, DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP, ToAWEOffsetNRTDCHIP, ToAWEOffsetRTDCHIP, ToAWSOffsetNRTDCHIP, and ToAWSOffsetRTDCHIP. 5 Configure the IP-based Iub in the Flexi WCDMA BTS.
g Please note that depending on the BTS software release (WN6.0 or WN6.0 EP1),
the order of the steps might be different. a) Open the BTS Site Manager. b) Start TRS Commissioning. g The selection of the transport mode (ATM Iub/IP Iub/Dual Iub) can be made only in the BTS Site Manager Commissioning Wizard, not in the Flexi TRS Manager. c) Enter the name and Id of the BTS. Enter the transport (TRS) and BTS IP address for DCN. d) Set Transport Mode to Iub IP and take Ethernet interface (EIF) in use. e) Configure the Transport Ethernet Interface IP address (use example value 10.3.1.1/30). With WN6.0 EP1, when using VLANs, leave the IP address field empty and add new VLAN, configure the IP address, enter the Committed information rate and select Enable QoS checkbox. f) Configure Quality of Service settings or use default values. g) With WN6.0 and earlier releases, if VLAN was configured in the RNC, take the VLAN in use and assign a VLAN Id. h) Configure Far end SCTP subnet and ensure that the RNC ICSU IP is included in the subnet. In the example provided, the ICSU control plane subnet in the RNC is 10.1.1.1/26. i) Configure Minimum SCTP Port and Minimum UDP Port. The value of Minimum SCTP Port has to match the value set previously using RNC RNW Object Browser GUI. j) Fill in the values according to transport network planning for the CAC Committed Bit Rate, Signalling Bit Rate, and DCN Bit Rate. In the example provided, these are: 2 Mbit for CAC Committed Bit Rate, 100 kbit for Signalling, and DCN Bit Rate. k) Configure the BFD sessions to supervise the IP path to the RNC.
Id:0900d805807861b2
13
g The BFD configuration is an optional step. It requires BFD session established

in the RNC as instructed in step Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. l) Configure the synchronization source. m) Add the default gateway; ensure that the gateway is reachable given by the subnet mask in the Transport Ethernet Interface. In the example provided, the external router default gateway is 10.3.1.2.
g A timing source is not automatically available for the IP Iub, and the synchronization
source is provided by either a timing over packet master or Synchronous Ethernet. For more information, see Activating RAN1254: Timing over Packet for BTS Application SW and Activating RAN1708: BTS Synchronous Ethernet. Expected outcome The RAN74: IP based Iub for Flexi WCDMA BTS feature has been activated, and after the IPNB object creation NBAP/SCTP terminations are created at the RNC.
14
Id:0900d805807861b2
2 Activating IP based Iub for UltraSite WCDMA BTS

Purpose Follow the procedure below to activate feature RAN1634: IP Based Iub for UltraSite WCDMA BTS. For more information on the feature, see RAN1634: IP Based Iub for UltraSite WCDMA BTS in WCDMA RAN, rel. RU10, feature descriptions. Exemplary reference configurations using this feature are presented in Configuring WCDMA RAN transport document. The configuration examples in the activation instructions use the IP addressing presented in figure IP-based Iub connectivity for UltraSite WCDMA BTS.
Figure 2
IP-based Iub connectivity for UltraSite WCDMA BTS
Before you start Enabling IP-based Iub requires the following interface units in the RNC: in RNC2600, the NPGE Gigabit Ethernet interface unit - RAN77: RNC Ethernet Physical Interface feature in RNC196/450, IP-interface upgrade - RAN1225: IP Interface Upgrade for RNC196 and RNC450 feature
In the UltraSite WBTS, the IFUH or AXCF (available in RU20) unit is required. This feature is an optional application with a separate license control and belongs to the application software. Before you activate the feature, make sure you have a valid license (a file including the feature information) installed. Before a licensed feature can be activated, the license must be transferred and installed in the RNC. You can install the license by using NetAct or a local MML interface. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. If you use the MML interface, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. When installing a new increment, the previously set state remains as the default.
Id:0900d8058078296c
15
For more information, see Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN . Use the ZW7 command to activate the license for the feature with feature code 1294. Note that the license is capacity based, and the measure of the capacity is the number of BTSs. If the IP-based Iub is not ON, the IP based route ID cannot be configured. RNW configuration has to be carried out according to the network plan. Configuration can be done by using either the RNW Object Browser (RNC EM application), or the RNW plan interface. The IP-layer configuration can be managed using the local MML interface or the IP Plan interface from NetAct. The following parameters are related to this feature: IPNB parameters for IP Iub control plane connections: IPNBId WBTSId IPBasedRouteId MinSCTPPortIub NodeBIPAddress NBAPDSCP CNBAP SCTPPortNumberCNBAP DNBAPList DNBAP CControlPortID SCTPPortNumberDNBAP IubTransportMedia IPNBId IPBasedRouteIdlub MinUDPPortIub DSCPMedDCH DSCPLow DSCPHigh DSCPMedHSPA HSDPAULCToDSCP HSUPADLCToDSCP ToAWEOffsetNRTDCHIP ToAWEOffsetRTDCHIP ToAWSOffsetNRTDCHIP ToAWSOffsetRTDCHIP
WBTS parameters for IP Iub user plane connections:
The parameters can be configured with the RNC RNW Object Browser GUI. BTS parameters can be configured with the AXC Manager or NetAct. For more information about BTS parameters, see Plan Editor AXC Parameters. Restart of the WBTS is required during activation of this feature.
16
Id:0900d8058078296c
example to the same VLANs), the IP addressing used for the user plane traffic and BFD sessions termination requires a special emphasis. For more details, see Technical Support Note, TN-RNC-SW-146 in NOLS. Steps 1 Configure the IP-based Iub in the RNC with the MML interface.
of IFGEx otherwise all the NPGEP units report a fault and NPGEP with any missing Ethernet connection restarts. If VLAN is used: a) Enable and check administrative status of IFGE0: ZQRN:NPGE,0:IFGE0:::::UP; ZQRI; b) Create a VLAN interface to the NPGE-0 unit. The VLAN name is 'VL1', VLAN ID is 2 (VLAN ID can have value between 2 to 4094), the VLAN is attached to the physical interface IFGE0. ZQRM:NPGE,0:VL1:2:IFGE0; c) Configure the IP address of the VLAN interface. ZQRN:NPGE,0:VL1:10.2.1.1,P:29:; g Pay attention to the IP address planning with the VLAN configuration at system level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option. If VLAN is not used: d) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; ZQRI:NPGE,0:; Proceed with the configuration for both cases: e) Configure the gateway for the NPGE to the external router: ZQKC:NPGE,0:10.3.1.0,30:10.2.1.2:LOG; ZQKB:; f) Create a DSPM profile for the Ethernet interface (IFGE0): Refer to the ZQ8B command in the MML manual. This is optional; also a default value can be used. g) Assign a DSPM profile to an IP interface in the NPGE by using given profile ID or the default profile: ZQ8S:NPGE,0:IFGE0:ENA::; h) Check the internal IPoATM from the NPGE to ICSU: ZQMQ:ICSU,0::NPGE,0:::ALL; i) Configure the Iub control plane subnet for ICSU units: ZQMN:1:10.1.1.0,26:; ZQML:; g The system configures ICSU IP over ATM interface MTU to value 1472 for the automatically generated internal full mesh IPoA. The ICSU Iub IPoA interface MTU value should not be configured greater than 1472 in order to keep the SCTP layer fragmentation aligned with the BTS SCTP defragmentation functionality. If the MTU size on Iub is configured to be smaller than 1500, respec-
Id:0900d8058078296c
17
tively the MTU size for ICSU unit has to be descreased (with the MML ZQRN command) to avoid fragmentation at NPGE. j) Create a static route from the ICSU to the NPGE as a gateway: ZQKC:ICSU,0:10.3.1.0,30:10.2.1.1:LOG; ZQKB:; k) Configure the IP based route to the IFGE0 for the Iub. Give values for the bandwidth allocation according to the transport network dimensioning plan: ZQRU:ADD:1,"IUBWBTS1":8000:500:100:100:ON; ZQRC:NPGE,0:IFGE0:IPV4=10.2.1.1:ID=1:; or in case VLAN is used: ZQRC:NPGE,0:VL1:IPV4=10.2.1.1:ID=1:; 2 Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS.
g BFD configuration is an optional step.

a) Configure the BFD profile: ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure the BFD session between the RNC and BTS: ZYGS:C:NPGE,0,1,10.2.1.1,10.3.1.1:PROF=1,ALARM=OFF; c) Set the BFD session state to enabled and the alarm state to on when the BTS is integrated to the RNC: ZYGS:S:NPGE,0,1,:ALARM=ON,MODE=0; 3 Configure DCN for the RNC. For instructions on configuring RNC (OMU) for DCN, see Configuring IP stack in OMU in Configuring IP connection for RNC. 4 Configure the IP-based Iub in the RNC RNW Object Browser GUI.
f The system configures the static IP route in ICSU towards Control Plane Destination Address Iub. When the IPNB object is disconnected from the WBTS, the static IP route is deleted based on its ROUTE NUMBER. Do not delete the static IP route manually, as it may cause a situation where the ROUTE NUMBER which might be used by other manually created IP routes, is removed while the IPNB object is disconnected from the WBTS. a) Open the RNC RNW Object Browser GUI. b) Create the IPNB object for the IP-based Iub control plane connections by selecting Object h New h IP Iub h IPNB. 1. Provide the IPNB with an object identifier. 2. Give BTS CP/UP 10.3.1.1 IP address as a Control Plane Destination Address Iub. 3. The IP Based Route Identification value is retrieved from the WBTS object once IPNB and WBTS are connected (when the IPNB id is set in the WBTS and the corresponding IPNB exists in the system). 4. Configure minSCTPPort (Minimum SCTP port number). Make sure that the SCTP Port ID have a unique value.
18
Id:0900d8058078296c
5. In the D-NBAP List, when using the IFUH, the Communitcation Control Port ID must be set for each WAM unit (D-NBAP is terminated in WAM units). When using AXCF unit, the only possible value for the communication control port is 1. After entering the communication control port, the SCTP Port Number for DNBAP is automatically calculated. c) Create or modify the WBTS object so that it contains the IPNB reference and IP Iub user plane configuration. 1. Configure IPNBId (IPNB object identifier) in the WBTS object data. 2. Set the attributes related to IP-based Iub user plane correctly. Set IPBasedRouteIdIub so that it refers to the IP based route configured for the given BTS. In the example value 1 is used. In the IubTransportMedia (Iub Transport Media Selection) parameter, check the IP Iub only. Default values can be used for MinUDPPortIub , DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP, ToAWEOffsetNRTDCHIP, ToAWEOffsetRTDCHIP, ToAWSOffsetNRTDCHIP, and ToAWSOffsetRTDCHIP. 5 Configure the IP-based Iub in the transport module of UltraSite WCDMA BTS (AXC).
g The transport mode is changed by downloading an XML configuration file with IP

Iub settings in the AXC and activating it (for instructions, see Commissioning AXC with XML configuration file in Commissioning AXC). Note that the transport mode can also be changed with the AXC Manager, but this is supported only in a local connection with the AXC Manager.
g The amount of configured NBAP links should follow the UltraSite WCDMA BTS configuration.
the order of the steps might be different. a) Open the AXC Manager. b) Switch the transport mode to Iub IP in a local connection with the AXC Manager. Click Node h Switch Transport Mode and select Iub IP in the dialog window that opens. Click Switch to change the transport mode. c) Configure IFUH/AXCF interfaces. Select the interface in the hardware view. Take the IFUH/AXCF interface in use and modify Speed and Duplex if required. d) Configure transport addresses. g Transport address settings are needed for the IP Iub and synchronization. Click IP h Settings and select the Transport addresses tab. Select the unit from the list and click Modify. Enter the Local IP Address and Netmask. Modify the bandwidth limit if needed, and take Virtual LAN (VLAN) in use if necessary. e) Configure IP Iub settings. Click IP h Settings, select the IP Iub tab, and click Modify. Define the following settings: Far End SCTP Address and Far End SCTP Subnet (this is the RNC ICSU subnet)
Id:0900d8058078296c
19
Minimum SCTP Port: possible values range from 49152 to 65529. The value of Minimum SCTP Port has to match the value set previously using RNC RNW Object Browser GUI. Note that the BTS is reset if you modify the value of Minimum SCTP Port. Minimum UDP Port: possible values range from 49152 to 63135. It is recommended not to change the value of Minimum UDP Port during the AXC operation so that no calls are lost. CAC Committed Bit Rate: possible values range from 0.5 to 100 Mbps in 0.5 Mbps steps. Signaling Bit Rate: possible values range from 50 to 1000 kbps in 50 kbps steps. DCN Bit Rate: possible values range from 50 to 1000 kbps in 50 kbps steps. Configure the BFD sessions to supervise the IP path to the RNC. g The BFD configuration is an optional step. It requires BFD session established in the RNC as instructed in step Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. f) Configure IP routing Click IP h Settings, select Routing tab, select Display transport routing and add new routes by clicking Add. g) Click Activate BTS Settings in the Iub IP tab to activate the settings. h) Configure the Quality of Service settings. Click IP h Settings, select the Quality of Service tab, and click Modify Queue Weights and Modify Traffic Types. i) Configure other settings, such as synchronization and Management Protocol. g A timing source is not automatically available for the IP Iub, and the synchronization source is provided by either a timing over packet master or Synchronous Ethernet. For more information, see Activating RAN1254: Timing over Packet for BTS Application SW and Activating RAN1708: BTS Synchronous Ethernet.
g For detailed instructions on configuring AXC, see Commissioning AXC.

Expected outcome The RAN1634: IP based Iub for UltraSite WCDMA BTS feature has been activated, and during the IPNB object creation NBAP/SCTP terminations are created in the RNC.
20
Id:0900d8058078296c
Verifying IP based Iub for Flexi and UltraSite WCDMA BTS
3 Verifying IP based Iub for Flexi and UltraSite WCDMA BTS

Purpose Follow the procedure below to verify that the activation of the RAN74: IP based Iub for Flexi WCDMA BTS and RAN1634: IP based Iub for UltraSite WCDMA BTS features has been successful.
g If the features are not working as expected, check the alarms for Ethernet/BFD
related failures. Steps 1 2 3 4 Open the RNC RNW Object Browser GUI. Check the NBAP link states. Check whether the cell states are up and running. Perform the calls. Expected outcome IP-based Iub features RAN74 and RAN1634 have been activated successfully if the whole traffic can be carried over the IP transport.
Id:0900d8058063223c
21
Deactivating IP based Iub for Flexi and UltraSite WCDMA BTS
4 Deactivating IP based Iub for Flexi and UltraSite WCDMA BTS

IP-based Iub is not deactivated separately for the Flexi and UltraSite WCDMA BTS. The IP Iub configuration can be changed to the Dual Iub or ATM Iub configuration by following relevant instructions. In this case the Iub transport and BTS configuration need to be changed accordingly.
22
Id:0900d8058064ac0b
5 Activating Dual Iub for Flexi WCDMA BTS

Purpose Follow the procedure below to activate feature RAN1449: Dual Iub for Flexi WCDMA BTS. With Dual Iub feature up and running the Iub Control Plane connections and User Plane connections for common channels, basic SRB on R99 DCH, and RT DCH bearers are always carried on top of the ATM transport. With the WBTS IubTransportMedia attribute, part of the call and traffic types can be configured to be carried on top of the IP transport. PS NRT DCH HSDPA non-realtime traffic offload HSPA non-realtime offload HSPA traffic offload PS non-realtime traffic offload Full PS traffic offload Table 1 x x x x x x x x x x x x x x x NRT HSDPA NRT HSUPA Streaming HSDPA Streaming HSUPA
Allowed combinations for transport bearers on IP transport network With the feature RAN1470: HSUPA 2ms TTI or RAN1201: Fractional DPCH (SRB on HSPA) Dual Iub allows also to separate the following traffic classes: SRB HSPA Associated DL SRB DCH
For more information on the feature, see RAN1449: Dual Iub for Flexi WCDMA BTS in WCDMA RAN, rel. RU10, feature descriptions. Exemplary reference configuration using this feature is presented in Dual Iub for combined E1 and DSL backhaul network in Configuring WCDMA RAN transport document. From the capacity dimensioning viewpoint, Dual Iub requires planning the capacity requirements separately for the ATM and the IP parts of the Iub. For more information on the dimensioning of the Iub interface, see Dimensioning WCDMA RAN. The configuration examples in the activation instructions use the IP addressing presented in figure Dual Iub connectivity for Flexi WCDMA BTS.
Id:0900d805807861b0
23
Figure 3
Dual Iub connectivity for Flexi WCDMA BTS
Before you start Enabling Dual Iub requires the following interface units in the RNC: in RNC2600, the NPGE Gigabit Ethernet interface unit - RAN77: RNC Ethernet Physical Interface feature in RNC196/450, IP-interface upgrade - RAN1225: IP Interface Upgrade for RNC196 and RNC450 feature the support of SDH interfaces by NIS1 or NPS1 interface units
In the Flexi WBTS, an FTIA, FTIB, FTJA, FTFB, or FTLB hybrid PDH/Ethernet transport sub-module is required. The feature RAN1449: Dual Iub for Flexi WCDMA BTS is an optional application controlled with a separate license. This feature belongs to application software. Before you activate the feature, make sure you have a valid license installed. Before a licensed feature can be activated, the license (a file including the feature information) must be transferred and installed in the RNC. You can install the license by using NetAct or a local MML interface. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. If you use the MML interface, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. When installing a new increment, the previously set state remains as the default. For more information, see Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN . Use the ZW7 command to activate the license for the feature with feature code 1246. Note that the license is capacity based, and the measure of the capacity is the number of BTSs. If the Dual Iub feature is not ON, the IP based route ID cannot be configured. The count of Dual Iub WBTSs (the IP based route ID is defined and IubTransportMedia is HSPA) exceeding the capacity of Dual Iub is not allowed. RNW configuration is to be carried out according to the network plan. Configuration can be done by using either the RNW Object Browser (RNC EM application), or the RNW plan interface. IP-layer configuration can be managed using the local MML interface or the IP Plan interface from NetAct.
24
Id:0900d805807861b0
The following WBTS parameters for user plane connections carried on top of the IP transport are related to this feature: IubTransportMedia IPBasedRouteIdlub MinUDPPortIub DSCPMedDCH DSCPLow HSDPAULCToDSCP HSUPADLCToDSCP ToAWEOffsetNRTDCHIP
BTS parameters can be configured with the BTS Site Manager or NetAct. For more information about BTS parameters, see Plan Editor Flexi Transport Module Parameters. Restart of the WBTS is required after activation of this feature.
example to the same VLANs), the IP addressing used for the user plane traffic and BFD sessions termination requires a special emphasis. For more details, see Technical Support Note, TN-RNC-SW-146 in NOLS. Steps 1 Configure the ATM resources for Iub control plane connections and user plane connections. a) Create the Physical Trail Termination Point: ZYDC:1:SET=1::; b) Create the ATM interface: ZLAC:1:UNI,1,:; c) Create the Access Profile for the ATM interface: ZLAF:1:8:14:E:; 2 Configure the IP layer resources for the Iub user plane.
of IFGEx otherwise all the NPGEP units report a fault and NPGEP with any missing Ethernet connection restarts. If VLAN is used: a) Enable and check administrative status of IFGE0: ZQRN:NPGE,0:IFGE0:::::UP; ZQRI; b) Create a VLAN interface to the NPGE-0 unit. The VLAN name is 'VL1', VLAN ID is 2 (VLAN ID can have value between 2 to 4094), the VLAN is attached to the physical interface IFGE0. ZQRM:NPGE,0:VL1:2:IFGE0; c) Configure the IP address of the VLAN interface. ZQRN:NPGE,0:VL1:10.2.1.1,P:29:; g Pay attention to the IP address planning with the VLAN configuration at system level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option.
Id:0900d805807861b0
25
If VLAN is not used: d) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; Proceed with the configuration for both cases: e) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; f) Configure the gateway for the NPGE to the external router: ZQKC:NPGE,0:10.3.1.0,30:10.2.1.2:LOG; g) Create a DSPM profile for the Ethernet interface (IFGE0): Refer to the ZQ8B command in the MML manual. This is optional; also a default value can be used h) Assign a DSPM profile to an IP interface in the NPGE by using the given profile ID or the default profile: ZQ8S:NPGE,0:IFGE0:ENA::; i) Configure the IP based route to the IFGE0 for the Iub. Give values for the bandwidth allocation according to the transport network dimensioning plan: ZQRU:ADD:1,"IUBWBTS1":2000:500:100:100:ON; ZQRC:NPGE,0:IFGE0:IPV4=10.2.1.1:ID=1:; or in case VLAN is used: ZQRC:NPGE,0:VL1:IPV4=10.2.1.1:ID=1:; 3 Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS.
g BFD configuration is an optional step. However, by configuring BFD session and

binding it to the IP based route, IP path protection is ensured. a) Configure the BFD profile: ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure the BFD session between the RNC and BTS and bind it to previously configured IP based route (ROUTE=IP based route ID): ZYGS:C:NPGE,0,1,10.2.1.1,10.3.1.1:PROF=1,ALARM=OFF,ROUTE=1; c) Set the BFD session state to enabled and the alarm state to on, when the BTS is integrated to the RNC: ZYGS:S:NPGE,0,1,:ALARM=ON,MODE=0; 4 Configure the Dual Iub in the RNC RNW Object Browser GUI. a) Configure attributes related to the IP-based Iub user plane in the WCDMA BTS object. Set IPBasedRouteIdIub so that it refers to the IP based route configured for the given BTS. In the example provided, value 1 is used. IubTransportMedia should be configured according to the transport network planning. For example the NRT HSDPA and NRT HSUPA can be configured to the IP transport path, while the other traffic is routed to the ATM path. Default values can be used for MinUDPPortIub, DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP, ToAWEOffsetNRTDCHIP, and ToAWSOffsetNRTDCHIP.
26
Id:0900d805807861b0
b) Create the COCO object and give the desired COCO object id in the WBTS object. Configure the NBAP, AAL2 signalling, and AAL2 user plane connections according to the normal ATM Iub configuration principles. For the user plane connections the ATM and IP transport selection is based on the WBTS object IubTransportMedia parameter, and it is not directly dependent on the AAL2 VCC configuration in the COCO object. 5 Configure the Dual Iub in the Flexi WCDMA BTS.
the order of the steps might be different. a) Open the BTS Site Manager. b) Start Commissioning TRS. g The selection of the transport mode (ATM Iub/IP Iub/Dual Iub) can be made only in the Flexi BTS Site Manager Commissioning Wizard, not in the Flexi TRS Manager. c) Enter the name and Id of the BTS, and IP addresses for the DCN. d) Select at least one PDH interface and one Ethernet interface that are in use. Select the transport mode of the FTM as Dual Iub. e) Give BTS Transport Ethernet Interface address (in the example provided: 10.3.1.1/30). With WN6.0 EP1, when using VLANs, leave the IP address field empty and add new VLAN, configure the IP address, enter the Committed information rate and select Enable QoS checkbox. f) Configure Quality of Service settings or use default values. g) With WN6.0 and earlier releases, if VLAN was configured in the RNC, take the VLAN in use and assign a VLAN Id. h) Configure the minimum UDP port and CAC committed bit rate value (in the example provided: 2 Mbit/s). i) Configure the BFD session to supervise the IP path to the RNC. g The BFD configuration is an optional step. It requires BFD session established in the RNC as instructed in step Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. j) Select primary and secondary timing sources. k) Configure the default gateway for BTS routing (in the example provided: 10.3.1.2). Also add static routes if necessary. l) Create at least four traffic descriptors: one for the BTS capacity on the VP level, one for Iub signaling Terminations, one for AAL2 User Path, and one for DCN. g For detailed instructions on creating traffic descriptors, see Defining traffic descriptors in Commissioning Flexi WCDMA BTS. m) Create ATM Iub Terminations to BTS. Mandatory terminations for commissioning are the following: Common NBAP, Dedicated NBAP, AAL2 Signaling, and at least one User Path. g For detailed instructions on creating traffic descriptors, see Defining IUB terminations to BTS in Commissioning Flexi WCDMA BTS. n) Create a DCN interface for the remote access to the BTS. o) Configure the default gateway for DCN routing. Also add static routes if necessary.
g For the NBAP/Signalling and RT user traffic, the ATM VCCs for the Dual Iub are
configured in the same way as for ATM Iub.
Id:0900d805807861b0
27
g For detailed instructions on commissioning, see Commissioning Flexi WCDMA

BTS. Expected outcome The RAN1449: Dual Iub for Flexi WCDMA BTS feature has been activated.
28
Id:0900d805807861b0
Activating Dual Iub for UltraSite WCDMA BTS
6 Activating Dual Iub for UltraSite WCDMA BTS

Purpose Follow the procedure below to activate feature RAN1633: Dual Iub for UltraSite WCDMA BTS. With Dual Iub feature up and running the Iub Control Plane connections and User Plane connections for common channels, basic SRB on R99 DCH, and RT DCH bearers are always carried on top of the ATM transport. With the WBTS IubTransportMedia attribute, part of the call and traffic types can be configured to be carried on top of the IP transport. PS NRT DCH HSDPA non-realtime traffic offload HSPA non-realtime offload HSPA traffic offload PS non-realtime traffic offload Full PS traffic offload Table 2 x x x x x x x x x x x x x x x NRT HSDPA NRT HSUPA Streaming HSDPA Streaming HSUPA
Allowed combinations for transport bearers on IP transport network With the feature RAN1470: HSUPA 2ms TTI or RAN1201: Fractional DPCH (SRB on HSPA) Dual Iub allows also to separate the following traffic classes: SRB HSPA Associated DL SRB DCH
For more information on the feature, see RAN1633: Dual Iub for UltraSite WCDMA BTS in WCDMA RAN, rel. RU20, feature descriptions. Exemplary reference configuration using this feature is presented in Dual Iub for combined E1 and DSL backhaul network in Configuring WCDMA RAN transport document. From the capacity dimensioning viewpoint, Dual Iub requires planning the capacity requirements separately for the ATM and the IP parts of the Iub. For more information on the dimensioning of the Iub interface, see Dimensioning WCDMA RAN. The configuration examples in the activation instructions use the IP addressing presented in figure Dual Iub connectivity for UltraSite WCDMA BTS.
Id:0900d8058075c544
29
Figure 4
Dual Iub connectivity for UltraSite WCDMA BTS
Before you start Enabling Dual Iub requires the following interface units in the RNC: in RNC2600, the NPGE Gigabit Ethernet interface unit - RAN77: RNC Ethernet Physical Interface feature in RNC196/450, IP-interface upgrade - RAN1225: IP Interface Upgrade for RNC196 and RNC450 feature the support of SDH interfaces by NIS1 or NPS1 interface units the AXCF unit providing two 100/1000 Mbps Ethernet (electrical) and one 1000 Mbps SFP (optical) interfaces - RAN1701: AXCF unit for UltraSite WCDMA BTS feature g For information on installing and activating the AXCF unit, see Activating and operating the feature in RAN1701: AXCF unit for UltraSite WCDMA BTS. the IFUx unit for PDH or SDH interfaces g For information on installing and activating IFUx units, see Adding and replacing IFUs.
Enabling Dual Iub requires the following interface units in the UltraSite WBTS:
Feature RAN1633: Dual Iub for UltraSite WCDMA BTS is an optional application controlled with a separate license. This feature belongs to the application software. Before you activate the feature, make sure you have a valid license (a file including the feature information) installed. Before a licensed feature can be activated, the license must be transferred and installed in the RNC. You can install the license by using NetAct or a local MML interface. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. If you use the MML interface, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. When installing a new increment, the previously set state remains as the default. For more information, see Licence-based feature management, W7 - Licence and Feature Handling, and License Management Principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN . Use the ZW7 command to activate the license for the feature with feature code 1246.
30
Id:0900d8058075c544
Note that the license is capacity based, and the measure of the capacity is the number of BTSs. If the Dual Iub feature is not enabled, the IP based route ID cannot be configured. The count of Dual Iub WBTSs (the IP based route ID is defined, and IubTransportMedia is HSPA) exceeding the capacity of Dual Iub is not allowed. The RNW configuration has to be done according to the network plan. Configuration can be carried out by using either the RNW Object Browser (RNC EM application), or the RNW plan interface. The IP-layer configuration can be managed using the local MML interface or the IP Plan interface from NetAct. The following WBTS parameters for User Plane connections carried on top of the IP transport are related to this feature: IubTransportMedia IPBasedRouteIdlub MinUDPPortIub DSCPMedDCH DSCPLow HSDPAULCToDSCP HSUPADLCToDSCP ToAWEOffsetNRTDCHIP
BTS parameters can be configured with the AXC Manager or NetAct. For more information about BTS parameters, see Plan Editor AXC Parameters. Restart of the WBTS is required during activation of this feature.
example to the same VLANs), the IP addressing used for the user plane traffic and BFD sessions termination requires a special emphasis. For more details, see Technical Support Note, TN-RNC-SW-146 in NOLS. Steps 1 Configure the ATM resources for Iub control plane connections and user plane connections with the MML interface. a) Create the Physical Trail Termination Point: ZYDC:1:SET=1::; b) Create the ATM interface: ZLAC:1:UNI,1,:; c) Create the Access Profile for the ATM interface: ZLAF:1:8:14:E:; 2 Configure the IP-layer resources for the Iub user plane with the MML interface.
of IFGEx otherwise all the NPGEP units report a fault and NPGEP with any missing Ethernet connection restarts.
Id:0900d8058075c544
31
If VLAN is used: a) Enable and check administrative status of IFGE0: ZQRN:NPGE,0:IFGE0:::::UP; ZQRI; b) Create a VLAN interface to the NPGE-0 unit. The VLAN name is 'VL1', VLAN ID is 2 (VLAN ID can have value between 2 to 4094), the VLAN is attached to the physical interface IFGE0. ZQRM:NPGE,0:VL1:2:IFGE0; c) Configure the IP address of the VLAN interface. ZQRN:NPGE,0:VL1:10.2.1.1,P:29:; g Pay attention to the IP address planning with the VLAN configuration at system level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option. If VLAN is not used: d) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; ZQRI:NPGE,0:; Proceed with the configuration for both cases: e) Configure the gateway for the NPGE to the external router: ZQKC:NPGE,0:10.3.1.0,30:10.2.1.2:LOG; f) Create a DSPM profile for the Ethernet interface (IFGE0). Refer to the ZQ8B command in the MML manual. This is optional; also a default value can be used. g) Assign a DSPM profile to an IP interface in NPGE by using the given profile ID or the default profile: ZQ8S:NPGE,0:IFGE0:ENA::; h) Configure the IP based route to the IFGE0 for the Iub. Give values for the bandwidth allocation according to the transport network dimensioning plan: ZQRU:ADD:1,"IUBWBTS1":2000:500:100:100:ON; ZQRC:NPGE,0:IFGE0:IPV4=10.2.1.1:ID=1:; or in case VLAN is used: ZQRC:NPGE,0:VL1:IPV4=10.2.1.1:ID=1:; 3 Configure the bidirectional forwarding detection (BFD) session with the MML interface to supervise the IP path to the BTS.
g The BFD configuration is an optional step. However, by configuring BFD session

and binding it to the IP based route, IP path protection is ensured. a) Configure the BFD profile: ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure the BFD session between the RNC and BTS and bind it to previously configured IP based route (ROUTE=IP based route ID): ZYGS:C:NPGE,0,1,10.2.1.1,10.3.1.1:PROF=1,ALARM=OFF,ROUTE=1; c) Set the BFD session state to enabled and the alarm state to ON when the BTS is integrated to the RNC: ZYGS:S:NPGE,0,1,:ALARM=ON,MODE=0;
32
Id:0900d8058075c544
Configure the Dual Iub RNC in the RNC RNW Object Browser. a) Configure attributes related to the IP-based Iub user plane in the WCDMA BTS object. Set IPBasedRouteIdIub so that it refers to the IP based route configured for the given BTS. In the example provided, value 1 is used. IubTransportMedia is to be configured according to the transport network planning. For example the NRT HSDPA and NRT HSUPA can be configured to the IP transport path while the other traffic is routed to the ATM path. Default values can be used for MinUDPPortIub, DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP, ToAWEOffsetNRTDCHIP, and ToAWSOffsetNRTDCHIP. b) Create the COCO object and give the desired COCO object id in the WBTS object. Configure the NBAP, AAL2 signalling, and AAL2 user plane connections according to the normal ATM Iub configuration principles. For the user plane connections the ATM and IP transport selection is based on the WBTS object IubTransportMedia parameter, and it is not directly dependent on the AAL2 VCC configuration in the COCO object. g After the AXCF is enabled, there is only one D-NBAP, the communication control port of which is 1. Create the COCO object and give the desired COCO object id in the WBTS object.
Configure the Dual Iub in AXC. a) Open the AXC Manager. b) Select the desired transport mode. 1. Select Node h Switch Transport Mode. 2. Select Dual Iub and select Switch to activate the desired mode. The node goes for reboot and loses all the configurations afterwards. g While switching from the ATM Iub to Dual Iub mode, the Enable AXCF checkbox is automatically enabled and grayed out. The AXCF unit can not be uninstalled when the node is in the IP Iub or Dual Iub mode. 3. Once the AXC node comes up after rebooting, check the transport mode using the AXC Manager in the Hardware View window.
Configure AXCF interfaces in the Dual Iub mode.
the order of the steps might be different. a) In the AXC Manager, in the Interface pane of Hardware view choose the interface of AXCF unit, then select Modify. b) Take the AXCF interface in use and modify Speed and duplex if required. c) Configure transport addresses. g Transport address settings are needed for the Dual Iub and timing over packet. 1. Select IP h Settings and select the Transport Addresses tab. 2. Select the unit from the list and click Modify. The Modify Transport Ethernet Interface dialog window opens.
Id:0900d8058075c544
33
Enter the local IP address and netmask (in the example provided: 10.3.1.1/30). Modify the bandwidth limit for traffic shaping if required. The physical maximum of Ethernet bandwidth that can not be exceeded is 100 Mbps (Ethernet overhead included). You can choose whether you want the bandwidth to include or exclude the Ethernet overhead. If necessary, take virtual LAN (VLAN) in use by checking the VLAN box and entering the identifier of the VLAN that the interface belongs to. Possible values range from 2 to 4094. 3. Configure the BFD session to supervise the IP path to the RNC. g The BFD configuration is an optional step. It requires BFD session established in the RNC as instructed in step Configure the bidirectional forwarding detection (BFD) session with the MML interface to supervise the IP path to the BTS. To enable the BFD session, check In use and Active checkboxes in the Bidirectional Forwarding Detection section. Configure BFD-related parameters. BFD is a network protocol used to detect faults between two forwarding engines. It provides a low-overhead detection of faults even on physical media that do not support failure detection of any kind, such as Ethernet, virtual circuits, tunnels, and MPLS LSPs. BFD establishes a session between two endpoints over a particular link. Parameters that are set for establishing the BFD session are the following: Desired min. TX interval with the default value of 500 ms and the range 500-5000 ms in steps of 500 ms. Required min. RX interval with the default value of 500 ms and the range 500-5000 ms in steps of 500 ms. Detection multiplier with the default value of 5 and the range 2-10. Destination address (the IP address of the peer node that the BFD session is to be established to). g Detection multiplier multiplied by the negotiated transmit interval, provides the Detection Time for the transmitting system in Asynchronous mode. g Desired min. TX interval is the minimum interval, that the local system would like to use when transmitting BFD control packets. The value zero is reserved. g Required min. RX interval is the minimum interval, in microseconds, between received BFD Control packets that the system is capable of supporting. If the value is 0, the transmitting system does not expect the remote system to send any periodic BFD control packets. 7 Configure Iub terminations in the ATM or Dual mode with Enhanced UltraSite Baseband (EUBB) enabled. a) In the AXC Manager create Virtual Paths and Virtual Channels for Iub terminations. g For detailed instructions, see Configuring ATM interfaces in Commissioning AXC. Create one VC for the Common NBAP connection and one VC for Dedicated NBAP connections.
34
Id:0900d8058075c544
b) c)
d)
e)
AAL2 multiplexing is always enabled by default in the Dual Iub mode. If BTS AAL2 Multiplexing is in use, create one signaling link and up to eight user paths. Create VCs for signaling link and user paths. Select Configuration h Iub Terminations to BTS. Click New Common NBAP and New Dedicated NBAP and select a Virtual Channel from the dialog window that opens. g BTS AAL2 Multiplexing checkbox is enabled and grayed out in the Dual Iub mode as AAL2 multiplexing is always enabled by default. Configure AAL2 signaling links. 1. Select New AAL2 Signaling. 2. Select a Virtual Channel from the tree to create the Iub link. 3. Configure AAL2 signaling parameters: STC fault in use - By selecting this parameter, you can enable signalling transport converter (STC) fault indication. If selected, the generation of a STC Connection to signaling peer not established fault is triggered. Performance monitoring 4. Configure AAL2 End Addresses parameter. Autocalculation method - Choose a method for autocalculation from the list. The chosen method is used when A2EA and PID values are indicated. The possible values are: 1 VCC for WAM, N VCC for WAM, and Manual. The default value is N VCC for WAM. The values are available for compatibility with other configurations in previous releases with AXCF not available. In the installation with AXCF, there is only one single A2EA Address required for the UltraSite WBTS. This single value is provided automatically if the default value N VCC for WAM is selected. If the chosen value is either Manual or 1 VCC for WAM, no values are being suggested. It is strongly recommended to use only the default value N VCC for WAM so that the required single A2EA address is computed automatically. g The address can only be suggested if you have defined the BTS identifier. In Iub Terminations to BTS tab, select BTS Settings to define the BTS IP settings. For instructions, see Configuring BTS IP settings. g If BTS AAL2 Multiplexing is in use, only one signaling link is required. g You can delete a signaling link by selecting the signaling link and clicking Delete. You can modify a signaling link by selecting the signaling link and clicking Modify. While modifying the signaling link, you can not modify the VP/VC termination used for creating the signaling link. Configure AAL2 user paths. 1. Select New AAL2 User Path. g In the Dual Iub mode you can create up to eight user paths. 2. Select a Virtual Channel from the tree to create a user path. Configure AAL2 user path parameters: Autocalculation method - Choose a method for autocalculation from the list. The chosen method is used when A2EA and PID values are being suggested. If the chosen value is "Manual", no values are being suggested. The possible values are: 1 VCC for WAM, N VCC for WAM, and Manual. The default value is N VCC for WAM. Path identifier - Enter the path identifier in this field. PID identifies the used ATM virtual channel inside ANI. PID has to be unique within each signaling link. However, the same PID can be used for user paths of different signaling links.
Id:0900d8058075c544
35
f)
Timer Cu - Enter the Timer Cu value in this field. The possible values range from 0 to 31 ms. The default value is 2 ms. Timer Cu (composite unit timer) is the maximum delay for an incomplete ATM cell to be transmitted in ATM adaptation layer type 2 (AAL2). Usage - Select the appropriate usage method from among the following: DCH & HSDPA, DCH, HSDPA, RTDCH, NRTDCH, HSUPA, or HSPA. Performance monitoring - Select Performance monitoring if you want to enable the performance monitoring. Quality of Service - In the table you can modify queue weights. The rows in the table are always enabled and the weight is a mandatory parameter for each queue. AXC Manager proposes default values for weight parameters when a new A2UP is created. The possible values for the weight range from 1 to 1000 with 1 for the lowest priority and 1000 for the highest. Default values for weight parameters are the following: Q1: Strict queue, weight is not modifiable Q2: 1000 Q3: 500 Q4: 1 Default - With this button you set the default queue weight values in the Quality of Service table. g The Quality of Service table is visible only if: AXCF is present and AXC is in the EUBB mode. AAL2 multiplexing is enabled, which is always true for EUBB in the ATM Iub and Dual Iub mode. When EUBB is in the IP Iub mode, AAL2 multiplexing is always disabled. g You can delete a User Path by selecting the desired User Path and clicking Delete. You can modify a User Path by clicking Modify. While modifying the User Path you can modify only Performance Monitoring checkbox and QoS parameters. Click Activate BTS settings to take the new settings in use. It is recommended to activate the settings only after you have configured both Iub terminations and BTS IP settings.
Expected outcome Feature RAN1633: Dual Iub for UltraSite WCDMA BTS has been activated. Further information AAL2 signaling (STC alarm, Performance Monitoring and used WAMs with A2EA) and user paths (Performance monitoring) can be modified only when BTS AAL2 Multiplexing is enabled. NBAP terminations can not be modified at all.
g Note that deleting an Iub termination does not result in the deletion of Virtual
Channel or Termination. As a consequence of deleting a signaling link, the related user paths are removed, while virtual channel and termination are not deleted.
36
Id:0900d8058075c544
Verifying Dual Iub for Flexi and UltraSite WCDMA BTS
7 Verifying Dual Iub for Flexi and UltraSite WCDMA BTS

Purpose Follow the procedure below to verify that the activations of the RAN1449: Dual Iub for Flexi WCDMA BTS and RAN1633: Dual Iub for UltraSite WCDMA BTS features have been successful.
g If the feature is not working as expected, check the alarms for the Ethernet/BFD
related failures. Steps 1 2 3 4 5 Open the RNC RNW Object Browser GUI. Check the NBAP link states. Check the status of the user plane with bidirectional forwarding detection (BFD). Check whether the cell states are up and running. Perform the calls. Expected outcome Features RAN1449: Dual Iub for Flexi WCDMA BTS and RAN1633: Dual Iub for UltraSite WCDMA BTS have been activated successfully if the whole HSPA traffic can be carried over the IP transport.
Id:0900d8058059f3a9
37
Deactivating Dual Iub for Flexi and UltraSite WCDMA BTS
8 Deactivating Dual Iub for Flexi and UltraSite WCDMA BTS

The Dual Iub for Flexi and UltraSite WCDMA BTS feature is not deactivated separately. The Dual Iub configuration can be changed to the full IP Iub or ATM Iub configuration by following the relevant instructions. If the Dual Iub configuration is changed, the Iub transport and BTS configuration needs to be changed accordingly.
38
Id:0900d8058059f3a8

Ip Dual Iub NSN

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ip Dual Iub NSN

Загружено:

Авторское право:

Доступные форматы

Nokia Siemens Networks WCDMA RAN, Rel.

RU20, Operating Documentation, Issue 03

Important Notice on Product Safety

DN70481473 Issue 02B

DN70481473 Issue 02B

DN70481473 Issue 02B

DN70481473 Issue 02B

DN70481473 Issue 02B

Activating IP based Iub for UltraSite WCDMA BTS

Activating Dual Iub for Flexi WCDMA BTS

DN70481473 Issue 02B

DN70481473 Issue 02B

Activating IP based Iub for Flexi WCDMA BTS

1 Activating IP based Iub for Flexi WCDMA BTS

IP-based Iub connectivity for Flexi WCDMA BTS

DN70481473 Issue 02B

Activating IP based Iub for Flexi WCDMA BTS

WBTS parameters for IP Iub user plane connections:

DN70481473 Issue 02B

Activating IP based Iub for Flexi WCDMA BTS

DN70481473 Issue 02B

Activating IP based Iub for Flexi WCDMA BTS

g BFD configuration is an optional step.

DN70481473 Issue 02B

Activating IP based Iub for Flexi WCDMA BTS

DN70481473 Issue 02B

Activating IP based Iub for Flexi WCDMA BTS

g The BFD configuration is an optional step. It requires BFD session established

DN70481473 Issue 02B

Activating IP based Iub for UltraSite WCDMA BTS

2 Activating IP based Iub for UltraSite WCDMA BTS

IP-based Iub connectivity for UltraSite WCDMA BTS

DN70481473 Issue 02B

Activating IP based Iub for UltraSite WCDMA BTS

WBTS parameters for IP Iub user plane connections:

DN70481473 Issue 02B

Activating IP based Iub for UltraSite WCDMA BTS

DN70481473 Issue 02B

Activating IP based Iub for UltraSite WCDMA BTS

g BFD configuration is an optional step.

DN70481473 Issue 02B

Activating IP based Iub for UltraSite WCDMA BTS

g The transport mode is changed by downloading an XML configuration file with IP

DN70481473 Issue 02B

Activating IP based Iub for UltraSite WCDMA BTS

g For detailed instructions on configuring AXC, see Commissioning AXC.

DN70481473 Issue 02B

Verifying IP based Iub for Flexi and UltraSite WCDMA BTS

3 Verifying IP based Iub for Flexi and UltraSite WCDMA BTS

DN70481473 Issue 02B

Deactivating IP based Iub for Flexi and UltraSite WCDMA BTS

4 Deactivating IP based Iub for Flexi and UltraSite WCDMA BTS

DN70481473 Issue 02B

Activating Dual Iub for Flexi WCDMA BTS

5 Activating Dual Iub for Flexi WCDMA BTS

DN70481473 Issue 02B

Activating Dual Iub for Flexi WCDMA BTS

Dual Iub connectivity for Flexi WCDMA BTS

DN70481473 Issue 02B

Activating Dual Iub for Flexi WCDMA BTS

DN70481473 Issue 02B

Activating Dual Iub for Flexi WCDMA BTS