Download pdf - RNC Integration

Nokia Siemens Networks WCDMA RAN, Rel. RU10, System Library, v. 3

Integrating RNC

DN03471554

Issue 11D DRAFTApproval Date 2009/09/21

2 DN03471554Issue 11D DRAFT

Integrating RNC

Id:0900d805805de913

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 DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, 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 2009. All rights reserved

f 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 zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

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 Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN03471554Issue 11D DRAFT

3

Integrating RNC

Id:0900d805805de913

Table of ContentsThis document has 177 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1 RNC integration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Configuring physical interface, and synchronisation inputs and outputs for ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1 Configuring PDH for ATM transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Creating IMA group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.3 Configuring SDH for ATM transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.4 Creating SDH protection group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5 Defining external time source for network element . . . . . . . . . . . . . . . . 242.6 Configuring synchronisation inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Creating phyTTP for ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 Creating ATM resources in RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5 Creating IP resources in RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.1 Creating and modifying VLAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . 395.2 Configuring IP parameters and addresses of interfaces. . . . . . . . . . . . 415.3 Configuring signalling transport over IP over ATM for control plane . . . 445.4 Configuring signalling transport over IP over Ethernet for control plane 465.5 Configuring IP resources for Iub control plane (RNC-BTS/AXC). . . . . . 505.6 Configuring IP for user plane with NPGE(P) . . . . . . . . . . . . . . . . . . . . . 52

6 Configuring RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.1 Configuring SSH server in OMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.2 Configuring the RNC object for the first time . . . . . . . . . . . . . . . . . . . . . 616.3 Configuring Iu-CS parameters of the RNC . . . . . . . . . . . . . . . . . . . . . . 626.4 Configuring Iur parameters of the RNC . . . . . . . . . . . . . . . . . . . . . . . . . 636.5 Configuring Iu-PS parameters of the RNC. . . . . . . . . . . . . . . . . . . . . . . 646.6 Creating local signalling configuration for RNC . . . . . . . . . . . . . . . . . . . 65

7 Creating Iu-CS interface (RNC-MGW) for ATM . . . . . . . . . . . . . . . . . . . 687.1 Configuring physical interface and synchronisation. . . . . . . . . . . . . . . . 687.2 Creating phyTTP and ATM resources . . . . . . . . . . . . . . . . . . . . . . . . . . 697.3 Configuring the RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.4 Configuring ATM-based signalling channels . . . . . . . . . . . . . . . . . . . . . 717.4.1 Creating remote MTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717.4.2 Activating MTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757.4.3 Setting MTP level signalling traffic load sharing . . . . . . . . . . . . . . . . . . 777.4.4 Creating remote SCCP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 787.4.5 Activating SCCP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817.5 Creating routing objects and digit analysis for Iu interface in RNC . . . . 837.6 Creating routing objects and digit analysis with subdestinations and routing

policy for Iu interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

8 Creating Iu-CS interface (RNC-MGW) for IP . . . . . . . . . . . . . . . . . . . . . 928.1 Planning site configuration for signalling . . . . . . . . . . . . . . . . . . . . . . . . 92


Integrating RNC

Id:0900d805805de913

8.2 Creating M3UA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968.3 Configuring IP for User Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

9 Creating Iur interface (RNC-RNC) for ATM . . . . . . . . . . . . . . . . . . . . . 1009.1 Configuring physical interface and synchronisation . . . . . . . . . . . . . . . 1009.2 Creating phyTTP and ATM resources . . . . . . . . . . . . . . . . . . . . . . . . . 1019.3 Configuring the RNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029.4 Configuring signalling channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039.5 Creating routing objects and digit analysis for Iur interface in RNC . . . 1049.6 Creating routing objects and digit analysis with subdestinations and routing

policy for Iur interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

10 Creating Iur interface (RNC-RNC) for IP. . . . . . . . . . . . . . . . . . . . . . . . 11310.1 Configuring signalling transport over IP over Ethernet for control plane. . .

11310.2 Creating M3UA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11710.3 Configuring IP for User Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

11 Creating Iu-PS interface (RNC-SGSN) for ATM . . . . . . . . . . . . . . . . . . 12111.1 Configuring physical interface and synchronisation . . . . . . . . . . . . . . . 12111.2 Creating phyTTP and ATM resources . . . . . . . . . . . . . . . . . . . . . . . . . 12211.3 Configuring the RNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12311.4 Configuring signalling channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12411.5 Configuring IP for Iu-PS user plane with NPS1(P) . . . . . . . . . . . . . . . . 125

12 Creating Iu-PS interface (RNC-SGSN) for IP . . . . . . . . . . . . . . . . . . . . 13012.1 Configuring signalling transport over IP over Ethernet for control plane. . .

13012.2 Creating M3UA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13412.3 Configuring IP for User Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

13 Creating Iub interface (RNC-BTS) for ATM . . . . . . . . . . . . . . . . . . . . . 13813.1 Configuring physical interface and synchronisation . . . . . . . . . . . . . . . 13813.2 Creating phyTTP and ATM resources . . . . . . . . . . . . . . . . . . . . . . . . . 13913.3 Creating radio network connection configuration (ATM, Dual Iub) . . . . 14013.4 Creating ATM termination point for IP over ATM connection . . . . . . . . 14213.5 Configuring IP for BTS O&M (RNC-BTS/AXC) via ATM. . . . . . . . . . . . 143

14 Creating Iub interface (RNC-BTS) for IP. . . . . . . . . . . . . . . . . . . . . . . . 14814.1 Configuring IP resources for Iub control plane (RNC-BTS/AXC) . . . . . 14814.2 Configuring IP for User Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15014.3 Configuring IP for BTS O&M (RNC-BTS/AXC) via Ethernet . . . . . . . . . 151

15 Creating Iub interface (RNC-BTS) for dual-Iub . . . . . . . . . . . . . . . . . . . 153

16 Configuring radio network objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15416.1 Configuring the RNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15416.2 Creating frequency measurement control . . . . . . . . . . . . . . . . . . . . . . . 15516.3 Creating handover path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15616.4 Creating a WCDMA BTS site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15716.5 Creating a virtual WCDMA BTS site . . . . . . . . . . . . . . . . . . . . . . . . . . . 16016.6 Creating a WCDMA cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161


5

Integrating RNC

Id:0900d805805de913

16.7 Creating a virtual WCDMA cell object . . . . . . . . . . . . . . . . . . . . . . . . . 16316.8 Creating an internal adjacency for a WCDMA cell . . . . . . . . . . . . . . . . 16416.9 Creating an external adjacency for a WCDMA cell . . . . . . . . . . . . . . . 16616.10 Creating radio network connection configuration (ATM, Dual Iub) . . . 16816.11 Creating IPNB object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

17 Printing alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17117.1 Printing alarms using LPD protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 17117.2 Printing alarms via Telnet terminal or Web browser . . . . . . . . . . . . . . 173

Related information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175


Integrating RNC

Id:0900d805805de913

List of FiguresFigure 1 Integrating RNC interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 2 Example network and logical interfaces between network elements . . . 14Figure 3 Connecting NPGE to multiple IP networks for Iub interface . . . . . . . . . . 56Figure 4 Configure NPGEP to multiple IP network via OSPF . . . . . . . . . . . . . . . . 57Figure 5 AAL bearer establishment from RNC 1 to RNC 2. . . . . . . . . . . . . . . . . . 71Figure 6 Alternative and percentage routing between RNC and MGW . . . . . . . . 88Figure 7 Alternative and percentage routing between two RNCs . . . . . . . . . . . . 109Figure 8 ATM virtual channel connections and IP addresses with NPS1 connected

to GPLC unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Figure 9 ATM virtual channel connections and IP addresses with one NPS1 con-

nected to different SGSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Figure 10 Configuring O&M network towards BTS via the ATM interface on OMU . .

144Figure 11 Configuring O&M network towards BTS via the ATM interface on NPS1(P)

144Figure 12 Example of IP configuration for BTS O&M when star topology and OSPF

are used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Figure 13 Configuring IP for BTS O&M (RNC-BTS) via Ethernet, case A . . . . . . 151Figure 14 Configuring IP for BTS O&M (RNC-BTS) via Ethernet, case B . . . . . . 151


7

Integrating RNC

Id:0900d805805de913

List of TablesTable 1 Parameters and values for creating phyTTP . . . . . . . . . . . . . . . . . . . . 28Table 2 Parameters and values for creating an ATM interface connected to a phys-

ical layer Trail Termination Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Table 3 Parameters and values for creating the access profile of the ATM interface

31Table 4 Parameters and values for creating VPLtps . . . . . . . . . . . . . . . . . . . . . 31Table 5 Parameters and values for creating VCLtps for CBR traffic . . . . . . . . . 32Table 6 Parameters and values for creating VPLtps . . . . . . . . . . . . . . . . . . . . . 32Table 7 Parameters and values for creating VCLtps . . . . . . . . . . . . . . . . . . . . . 33Table 8 Parameters and values for creating VPLtps for UBR traffic . . . . . . . . . 33Table 9 Parameters and values for creating VPLtps for CBR traffic . . . . . . . . . 34Table 10 Parameters and values for creating VPLtps for UBR+ traffic . . . . . . . . 35Table 11 Parameters and values for creating VCLtps for UBR connection . . . . . 35Table 12 Parameters and values for creating VCLtps for CBR traffic . . . . . . . . . 36Table 13 Parameters and values for creating VCLtps for UBR+ traffic . . . . . . . . 37


Integrating RNC

Id:0900d805805de83f

Summary of changes

Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Note that the issue numbering system is changing. For more information, see Guide to WCDMA RAN Documentation.

Changes between issues 11-3 and 11DA note in Configuring IP for User Plane with NPGE(P) has been updated to include the latest inforrmation on configuring the MTU.

The following chapters have been updated to include the latest user interface:

• Configuring Iu-CS parameters of RNC • Configuring Iu-PS parameters of RNC

Editorial changes have been made to the following chapters:

• Configuring IP parameters and addresses of interfaces • Setting MTP level signalling traffic load sharing • Configuring IP for Iu-PS user plane with NPS1(P) • Configuring IP for BTS O&M (RNC - BTS/AXC) via ATM • Configuring IP for BTS O&M (RNC-BTSAXC) via Ethernet

Changes between issues 11-2 and 11-3Creating ATM resources in RNC

• ZLCC command has been updated. • The description for parameter UBRSHARE has been updated.

Configuring IP parameters and addresses of interfaces

The TCU related column was deleted in the table.

Configuring IP for User Plane with NPGE(P)

• The reference about IP based route binding to the related interface has been added. • The note about QRU MML command has been updated.

Configuring Iu-CS parameters of the RNC

Information on the IP/Ethernet option has been added in the step related to checking core network related parameters.

Configuring Iur parameters of the RNC

Information on the IP/Ethernet option has been added in the step related to checking the parameters of the neighboring RNCs.

Configuring Iu-PS parameters of the RNC

Information on the IP/Ethernet option has been added in the step related to checking core network related parameters.

Configuring IP for Iu-PS user plane with NPS1(P)

• The reference about IP based route binding to the related interface has been added. • The note about QRU MML command has been updated. • Information on the configuration of RNC RNW database Iu-PS objects to the corre-

sponding PS CN element has been added.


9

Integrating RNC Summary of changes

Id:0900d805805de83f

Changes between issues 11-1 and 11-2Creating ATM resources in RNC

Information that EPD cannot be enabled in NPS1, NIS1, or NIP1 has been added.

Configuring signalling transport over IP over Ethernet for control plane

Steps about enabling IP forwarding have been added in the examples.

Configuring IP resources for Iub Control Plane (RNC-BTS/AXC)

A step on Modifying local IP sub-net for Iub control plane has been added.

Configuring IP for user plane with NPGE(P)

A step on IFGE UP creation has been added.

Planning site configuration for signalling

Example configuration for SCTP multi-homing (under IP over ethernet steps) has been updated so that it includes two NPGE(P) units.

Configuring IP for BTS O&M (RNC-BTS/AXC)

Editorial changes have been made and links updated.

Creating an external adjacency for a WCDMA cell

A note on System Information Block type 11bis (SIB11bis) has been added.


Integrating RNC

Id:0900d805805de83f

Summary of changes


11

Integrating RNC RNC integration overview

Id:0900d805805de842

1 RNC integration overviewYou can start the integration of a network element after the network element has been successfully installed and commissioned. During the commissioning phase, the network elements have been configured and tested as stand-alone entities. During the integra-tion phase the interconnections between the network elements are configured and their parameters are customised. After successful integration the network element is ready for commercial use.

For more information on integrating RNC to NetAct, see Integrating RNC to NetAct.

g IPv6 is not supported in current releases in WCDMA RAN even if it is included in some IP configuration instructions.

Required integration planning informationThe network planning process delivers all required information for network element installation, commissioning and integration. Network planning can be divided into the fol-lowing phases: transmission & transport and radio network planning.

The following planning activities must be accomplished before the integration phase starts:

1. radio network planning2. Transport/Transmission network planning (refers here to the ATM on SDH/PDH or

IP/Ethernet network planning.3. IP network planning

Integrating RNC interfaces overviewIn Figure Integrating RNC interfaces the RNC integration procedure is presented in a graphical format. It shows the steps involved with integrating each of the interfaces, and the correct order in which the steps should be carried out. Linking to the correct docu-mentation sections is provided below the figure.


Integrating RNC

Id:0900d805805de842

RNC integration overview

Figure 1 Integrating RNC interfaces

1. Create a physical interface configuration, configure synchronisation inputs and outputsSee Configuring PDH for ATM transport, Creating IMA group, Configuring SDH for ATM transport, Creating SDH protection group, Defining external time source for network element and Configuring synchronisation inputs.

2. Create a physical layer trail termination point (ATM option only)See Creating phyTTP.

Iupc ADIFIur

Iu-BCIub

Create a physical interface configuration, configure

synchronisation inputs and outputs

Create a physical layer trail termination point (ATM only)

Create ATM/IP resources

Configure A-GPS

location services171

2

3

4

Configure WBTS

and WCEL10

Configure ADJS,

ADJI,ADJG11

Create HOPS,

HOPI, HOPG9

Create FMCS,

FMCI, FMCG8

Create radio

network connection

configuration

(if IPNB alternative,

step 12, is not used)

5

13

Configure signalling channels

Configure IP for

Iu-PS user plane

Configure

Iu-BC parameters7 16

6Create routing objects and

digit analysis

Configure IP

for BTS O&M15

Configure RNC (create IUPS, IUCS, IUR, and IPQM objects)

Iu-PSIu-CS

14Create ATM termination

point for IP over ATM

(optional) (optional) (optional)

Create IPNB object

(if COCO alternative,

step 13, is not used)

12


13

Integrating RNC RNC integration overview

Id:0900d805805de842

3. Create ATM/IP resourcesSee Creating ATM resources in RNC and for IP resource creation see Configuring IP parameters and addresses of interfaces and Creating and modifying VLAN inter-faces and .

4. Configure RNCFor Iu-PS, Iu-CS, and Iur, you need to configure the respective objects (IUPS, IUCS, IUR). Note that with IP/Eth transport option and with NPS1 HW at Iu-PS, the IPQM object needs to be created before the IUPS and IUCS objects are referred to in the IPQM object.See Configuring the RNC object for the first time, Configuring Iu-CS parameters of RNC, Configuring Iu-PS parameters of RNC, Configuring Iur parameters of RNC, Creating local signalling configuration for RNC, and Activating Service Area Broad-cast in RAN2.0023: Service Area Broadcast, Feature Activation Manual.

5. Configure signalling channels (Iu-CS, Iur and Iu-PS) See Creating remote MTP configuration, Activating MTP configuration, Setting MTP level signalling traffic load sharing, Creating remote SCCP configuration, Activating SCCP configuration, Planning site configuration for signalling, and Creating M3UA configuration.

6. Create routing objects and digit analysis (Iu-CS and Iur ATM option) See Creating routing objects and digit analysis for Iu interface in RNC and Creating routing objects and digit analysis with subdestinations and routing policy for Iu inter-face.

7. Configure IP for Iu-PS user plane (ATM option with GTPU HW)See Configuring IP for Iu-PS User Plane (RNC-SGSN).

8. Create FMCS, FMCI, FMCGSee Creating frequency measurement control.

9. Create HOPS; HOPI, HOPGSee Creating handover path.

10. Configure WBTS and WCELSee Creating a WCDMA BTS site and Creating a WCDMA cell.

11. Configure ADJS, ADJI, ADJGSee Creating an internal adjacency for a WCDMA cell and Creating an external adjacency for a WCDMA cell.

12. Create IPNB (IP based Iub option)See Creating IPNB objects.

13. Create radio network connection configuration (with ATM Iub or Dual Iub option)See Creating radio network connection configuration.

14. Create ATM termination point for IP over ATM (with ATM Iub option)See Creating ATM termination point for IP over ATM connection.

15. Configure IP for BTS O&MSee Configuring IP for BTS O&M (RNC - BTS/AXC).

16. Configure Iu-BC parameters

See Activating Service Area Broadcast in RAN2.0023: Service Area Broadcast, Feature Activation Manual.

17. Configure AGPS location servicesSee Defining IP addresses and IP routes to RRMU units, Configuring ESA24-0, Configuring ESA24-1, Activating the Iupc interface, and Activating A-GPS Using


Integrating RNC

Id:0900d805805de842

RNC integration overview

External Reference Network in Features RAN223 and 875: A-GPS Using External Reference Network, Feature Activation Manual.

Example networkThe integration instructions are based on the following third generation example network:

Figure 2 Example network and logical interfaces between network elements

The logical interfaces for the RNC in the 3rd generation network are presented in the following list.

Iu-CS Logical interface that is used to carry traffic between the radio network controller (RNC) and circuit switched core network domain.

Iu-PS Logical interface between the RNC and the SGSN

Iur Logical interface for the interconnection of two RNC components of the UMTS terrestrial radio access network (UTRAN) system

Iub logical interface between the RNC and the WBTS

Iu-BC logical interface between the RNC and the cell broadcast centre (CBC)

ADIF Logical interface between the RNC and the A-GPS Server

Iupc Logical interface between the RNC and the Stand-alone SMLC

NWI3 CORBA-based proprietary management interface between network management system (NMS) and mediation devices or network ele-ments.

Multimedia

Gateway

Iu-PSIur

IubBTS

Iu-BC

CBC

MSC Server

SAS

ADIF

A-GPS

Server

SGSNRNC

Iu-CS

Iupc

NetAct

Iub NWI3

AXC

BTS


15

Integrating RNC Configuring physical interface, and synchronisation in-puts and outputs for ATM

Id:0900d805805de857

2 Configuring physical interface, and synchro-nisation inputs and outputs for ATM

2.1 Configuring PDH for ATM transportPurposeThis procedure describes how to configure the PDH/ATM interface for the NIP1 inter-face unit. The mode of the PDH interface must be the same for all the exchange termi-nals in the plug-in unit. That is why the NIP1 unit must be given as a parameter when the PDH mode is configured.

Usually the existing default values for the PDH supervision are adequate and you do not have to change them. If needed, you can configure and modify the exchange terminal supervision parameters. To guarantee timing information, it is recommended to use B8ZS line coding.

When you have configured new PDH exchange terminals (PET), you may have to modify their functional modes. Choose either E1 (ETSI-specific functional modes) or T1 (ANSI-specific functional modes). In a fractional E1/T1/JT1, you can select the timeslots that are used to carry user data.

g IMA functionality is not supported over fractional E1/T1/JT1 lines.

The network elements provide a synchronisation interface for external timing reference signals. For information on synchronisation, see Configuring synchronisation inputs in Synchronisation and Timing.

Before you startMake sure that you have created a functional unit description for the PETs. For instruc-tions, see Creating and attaching functional unit description in Hardware Configuration Management.

Steps

1 Interrogate the current configuration of the PET (YAI)ZYAI:PET;

2 Set the interface operation mode of NIP1 (YAE)Set the operation mode if you want to change it. The impedance parameter can be given only if the operation mode given is E1.

ZYAE:NIP1,<network interface unit index>,<interface operation mode>:[<impedance>];

If you change the impedance or the operation mode, you must restart the unit so that the changes are taken into use. For instructions, see Restarting functional unit in Recovery and Unit Working State Administration.

3 Modify E1 functional modes if needed (YEC)You can first print out the ETSI-specific frame modes with the command:


Integrating RNC

Id:0900d805805de857

Configuring physical interface, and synchronisation in-puts and outputs for ATM

ZYEI;

If the current frame mode does not match with the frame mode of the interface unit, which is connected to the remote end of this line, you can modify it with the command:

ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);

g Double frame mode does not support synchronisation status messages (SSM).

For information on synchronisation, see Configuring synchronisation inputs in Synchro-nisation and Timing.

4 Modify T1 functional modes if needed (YEG)You can print out the ANSI-specific T1 functional modes with command:

ZYEH;

If the current frame mode does not match with the frame mode of the interface unit that is connected to the remote end of this line, you can modify it with command:

ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|7.5|15|22.5);

g T1 does not support synchronisation status messages (SSM).

For information on synchronisation, see Configuring synchronisation inputs in Synchro-nisation and Timing.

5 Configure PET (YAM)ZYAM:PET,<PET index>...:[ON|OFF]:[DIA=(ON|OFF)|LINE=ON|OFF)]...:[<SA bit number SSM>];

6 Modify PET timeslot usage (YAW)You can modify PET timeslot usage with command:

ZYAW:<PET index>...:<timeslot number>...,[ON|OFF def];

7 Create an IMA group, if necessaryIf you want to use more than one transmission line, you must create an IMA group for the physical links. Configure PET (YAM) and Modify PET timeslot usage (YAW) are repeated for each link which is selected to the IMA group. For instructions, see Creating IMA group.

8 Create physical layer Trail Termination Point (phyTTP)For instructions, see Creating phyTTP.

Example: Configuring PDH for ATM transport

1. Set the interface operation mode of NIP1 with index number 9 to T1.ZYAE:NIP1,9,T1;

2. Restart the unit.ZUSU:NIP1,9;


17

Integrating RNC Configuring physical interface, and synchronisation in-puts and outputs for ATM

Id:0900d805805de857

3. Modify the frame alignment mode of the T1 PET with index 9.ZYEG:PET,9:ESF,B8ZS,0;

4. Disable scrambling for PETs with indexes between 9 and 15.ZYAM:PET,9&&15:OFF::;


Integrating RNC

Id:0900d805805de848

2.2 Creating IMA groupPurposeThis procedure describes how you can create an IMA group and add exchange termi-nals to it. You can later connect an external ATM interface to the phyTTP that has been created for the IMA group.

You must create an IMA group if you want to use more than one PDH-based transmis-sion lines for additional capacity or for securing traffic even in line failure situations. For example, if one E1 line is used in transmission, you can create an IMA group of two E1 lines and give value 1 to the minimum number of links parameter. Even if one line fails, the ATM interface stays up.

The maximum allowed number for each IMA group is 8 exchange terminals. The IMA group must be created at both ends of the physical links.

g IMA functionality is not supported over fractional E1/T1/JT1 lines.

Before you startMake sure that you have configured the PDH exchange terminals (PETs) before you create an IMA group. For the instructions, see Configuring PDH for ATM transport.

The PETs to be combined to an IMA group must belong to the same NIP1 functional unit. Check which functional unit a PET belongs to with the USI command.

Each PET is identified by its exchange terminal index, which is a system-wide unique numerical value. In addition, the system assigns a link ID to each PET. This link ID is unique in the IMA group.

One of the physical links functions as the Timing Reference Link (TRL) of the IMA group, which is identified by its link ID. The system assigns the TRL to the IMA group.

Steps

1 Create IMA group (YBC)ZYBC:[<IMA group id>] | <system select> def:[<exchange terminal type> | PET def],<exchange terminal index>...:<minimum number of links>;

g Define the IMA group size, which is the total number of the links, so that the IMA group capacity will be equal to or greater than the planned capacity of the ATM inter-face.

Further informationYou can add more PETs later on to the group with the YBA command. The maximum number of PETs in an IMA group is 8.

2 Create phyTTP for the IMA groupSee the instructions in Creating phyTTP.

Further informationYou can interrogate IMA groups with the YBI command, modify them with the YBM command, and delete an IMA group with the YBD command.

It is possible to remove exchange terminals from an IMA group with the YBR command.


19

Integrating RNC

Id:0900d805805de848

Adding or removing links automatically affects the bandwidth of the access profile of the ATM interface.

Example: Creating IMA group

1. Create an IMA group using the IMA group ID selected by the system.The type of exchange terminal is PET by default. The IMA group combines PDH exchange terminals 0, 5 and 14. The minimum required number of links in the group is 2.ZYBC::,0&5&14:2;

2. Add the exchange terminal 12 to the IMA group 3.ZYBA:3:12;


Integrating RNC

Id:0900d805805de84b

2.3 Configuring SDH for ATM transportPurposeThis procedure describes how to configure the SDH/ATM interface and modify the SDH exchange terminal (SET) configuration. You can define how the transmission capacity is divided, and change the threshold levels for performance monitoring to meet the expected quality of the transmission network.

Before you startYou must create the functional unit description for the SETs. For instructions, see Creating and attaching functional unit description in Hardware Configuration Manage-ment.

Steps

1 Interrogate the SET (YAI)With the following command you can find out the current exchange terminal configura-tion.

ZYAI:<SET>,<SET index>;

2 If you want to modify the default settings, configure the SET (YAN)

☞ When VC mapping is changed, the affected higher and lower order paths are set to their default values.

Note that for the NIS1, NIS1P, NPS1, and NPS1P units, only one loopback status (diag-nostic or line) can be active at a time.

Currently the SES BIP, SD BER, and SF BER parameters are not used for the higher or lower order paths. The SES BIP threshold for the higher order paths is the same as the one used for the multiplex section of the SET.

The following parameter values are irrelevant to the ATM traffic:

• mapping mode parameter values VC4VC11 and VC4VC12 • payload mapping mode parameter values ASYNCH, BITSYNCH, and BYTESYNCH

ZYAN:<SDH exchange terminal index>...,[<higher order path number>|<higher order path number>,<lower order path number>]:[<SES BIP threshold>]:[<SD BER threshold>]:[<SF BER threshold>]:[DIA=(ON|OFF)|LINE=(ON|OFF)|LASER=(ON|OFF)]...:[VC4|VC4VC11|VC4VC12]:[SDH|ATMML|SONET]:[ASYNCH|BITSYNCH|BYTESYNCH];

3 Set the SDH trace (YAS)You can set the SDH trace already during integration or later on, if necessary. The SDH trace trail must be configured identically to both trails related to a specific phyTTP (logical path) in a protection group. When you configure a trace for a trail that is part of a protection group, the system automatically applies the changes to the other trail of the pair and sends a notification on this.

☞ Trace types EXPPATH and EXPREG are not currently supported.


21

Integrating RNC

Id:0900d805805de84b

ZYAS:<SDH exchange terminal index>,[<higher order path number>|<higher order path number>,<lower order path number>]:(OUTPATH|EXPPATH|OUTREG|EXPREG),(RESET|SET1|SET16|SET64),<trace value>;

For more information on the trails, see Creating SDH protection group.

4 Create SDH protection group, if necessaryIf you want to secure the traffic even when a line fails, you need to create an SDH pro-tection group. See instructions in Creating SDH protection group.

5 Create phyTTPSee instructions in Creating phyTTP.

Further informationYou can interrogate the incoming SDH traces with command YAT.

Example: Configuring SDH for ATM transport

1. Modify the SES BIP threshold of the SET 1 to 2300 frames per second.ZYAN:1:2300;

2. Modify the outgoing path trace of the VC path 1 of SET 1. Use the 16-byte format.ZYAS:1,1:OUTPATH,SET16,"OUT PATH TRACE";


Integrating RNC

Id:0900d805805de84e

2.4 Creating SDH protection groupPurposeYou can create a protection group which is formed by two SDH exchange terminals (SET). Multiplex Section (MS) trail linear protection is used to protect a single multiplex section trail by replacing a working MS trail if the working trail fails or if the performance falls below the required level. There are two supported protection protocols:

• linear, bi-directional Multiplex Section Protection (MSP) 1+1 compatible with 1:n protocol, and

• linear, bi-directional Automatic Protection Switching (APS) 1+1.

Both protocols can be used either in revertive or in non-revertive mode.

The SDH trace trail must be configured identically to both trails related to the same logical path in a protection group. Otherwise, the system prevents the protection group creation.

Steps

1 Create SDH protection group (YWC)ZYWC:[<protection group id>|<system select> def],[<protection switching mode>|NONREV def],[<protocol variant>|MSP def]:<Working section SDH exchange terminal index>,<Protection section SDH exchange terminal index>:[<wait to restore time>|300 seconds def];

For NPS1P, you must configure the resources identically. For example, if you choose the third SET of one unit for the protection group, you must choose the third SET also of the other unit.

2 Create Physical layer Trail Terminal Point (phyTTP), if necessaryIf the protected SDH interfaces are for ATM traffic transport, you need to create phyTTP.

See the instructions for creating the Physical layer Trail Termination Point in Creating phyTTP.

Expected outcomeThe system generates the 0101 SDH PROTECTION SWITCHING EXECUTED notice if the protection switch operation succeeds.

Unexpected outcomeThe system generates the 3183 SDH PROTECTION SWITCHING FAILED alarm if the protection switch operation fails.

If the far end has not been configured to support the correct SONET APS configuration, the system generates the 3307 MISMATCH IN SONET APS CONFIGURATION alarm.

If the far end of the protected multiplex section is not able to use the protection section, the system generates the 3334 FAR END PROTECTION SECTION FAILURE alarm.

Further informationYou can interrogate the protection group configuration and protection switching status information with the YWI command, modify the configuration with the YWM command,


23

Integrating RNC

Id:0900d805805de84e

and delete the configuration with the YWD command. Note that a protection group cannot be deleted if a phyTTP has been created for it.

Example: Configuring SDH protection group with default protection protocol parameter values

1. Create a protection group of SET 7 (working section) of NIS1P-1 and SET 4 (protec-tion section) of NIS1P-0 with protection group ID 3.The default protection switching mode, bidirectional non-revertive, and protocol variant MSP 1+1 are used.ZYWC:3,,:7,4:;

Example: Configuring SDH protection group with SONET APS variant of the pro-tection protocol and with revertive mode

1. Create a protection group of SET 8 (working section) and SET 9 (protection section) of IWS1T-0 with protection group ID 4.Revertive mode and APS 1+1 variant are used.Default of wait to restore time is used. ZYWC:4,REV,APS:8,9;


Integrating RNC

Id:0900d805805de851

2.5 Defining external time source for network elementPurposeThe IP addresses used in the Commissioning stage for setting the time and date are pre-defined and temporary; therefore, you need to configure the time source IP address again, using the DCM command, after the internal DCN network has been configured during the integration stage.

The external time source is located in the Nokia NetAct time server. IPA2800-based network elements check the time and date every 15 minutes, preferably against the OMS time server, using NTP messages.

g IP connections must be created before you can define the external time source in Nokia NetAct time server.

Steps

1 Check the current date and time in the network element (DCD)ZDCD;

2 Check the NTP server IP address (DCI)ZDCI;

3 Set the IP address to the NTP time server (DCM)ZDCM:<ip version>,<ip address block 1>;

Expected outcomeWhen you have defined the external time source, in 15 minutes all the clocks in the network element will have the same time as the external time source has. The internal clock located in the network element gives a time stamp for all the functions that the computer unit does.


25

Integrating RNC

Id:0900d805805de854

2.6 Configuring synchronisation inputsPurposeYou can configure and control synchronisation with MML commands. Usually synchro-nisation-related MML commands are used for setting the synchronisation system-related parameters and also for getting information from the synchronisation system.

By using the correct MML command, you can force the system clock to use a synchro-nised operating mode or a free-run operating mode. Under certain operating conditions, for example calibration, this is a necessary action.

You must always create synchronisation inputs when taking a network element into use. You can change the inputs later, if needed. The following order of steps is not obligatory.

You can check the available synchronisation references with the DYI command.

Use the DYS command to set a synchronisation reference as the forced reference of the system clock. Notice that the forced reference can even be lost and the operation mode of the system clock is changed to Holdover. The changes in the quality of the other ref-erences do not affect the forced reference setting.

Whenever a synchronisation reference that is used in the synchronisation of the system clocks, is lost, the reference is considered to be available after the WTR (Wait To Restore) time has expired. The default WTR is five minutes.

Enable the distribution of the outgoing signal if you want to distribute the signal outside the network element.

Set the operation mode when testing the network element. Usually this is done automat-ically by the system.

g If you have set the operation mode to FREE, when testing the system for instance, you have to set the mode back to SYNC. This is not done by the system.

Steps

1 Set the parameters for all synchronisation references (DYM)The highest priority value (PRI) is 1. The highest synchronisation status message value (SSM) is 1, the lowest is 14. In addition, value 0 is used when the quality of the reference is unknown, and value 15 is used when the reference must not be used in synchronisa-tion.

The SSM value is entered manually to external references. All line references, including the PDH line interfaces, get their SSM values on line from the frame structure of the incoming signal. You have to set parameters for at least one synchronisation reference.

g PRI value must be removed from the references (it should be set to PRI=X) that have not been actually connected to a so-called connected NIU through which the synchronisation references are connected to the system.

g The Framing mode for the incoming PDH references must support the transfer of the SSM values. For instructions about configuring the Framing mode, see Config-uring PDH for ATM transport.

If the Framing mode for the incoming PDH references does not support the transfer of SSM values, the references can be set with the PRI value.

ZDYM:<synchronisation reference>,<reference index>,<mode of external reference>:PRI=<priority value>,SSM=<ssm value>;


Integrating RNC

Id:0900d805805de854

2 Check the automatic synchronisation setting (DYI)When the parameters for at least one synchronisation reference with OK status are set for the first time during system start-up, the system will synchronise automatically. In this case you do not have to manually set the operation mode.

ZDYI:<identification of information>,<identification of reference>;

3 Set the operation mode (DYT)If the system clock has not locked into the reference even though the reference is avail-able, it can be forced to lock into the reference by using the DYT command. This command is not normally used in the commissioning phase and it must not be used instead of entering parameters for a synchronisation reference.

ZDYT:MODE=<operation mode>;

4 Check the values of the WTR timers for the references (DYI)ZDYI;

5 Modify the values of WTR timers (DYL)The default value for the WTR timer is 5 minutes. If you want to change it, use the parameter SET. If you want to switch it off, you need to give the RESET command. If you want that the WTR timer is not set at all when the used synchronisation reference is lost, use SET parameter to change the value of the WTR timer to 0.

ZDYL: <synchronisation reference>, <reference index>: <action>, <value>;

g RESET option means that the running WTR timer for a synchronisation reference will be initialised immediately to 0 but if you want to disable the WTR timer, you must SET the value of WTR timer to 0.

6 Check which references have been enabledZDYP;

7 Enable the distribution of outgoing synchronisation (DYE)Enable the distribution of outgoing synchronisation if you want to distribute the signal outside the network element.

Give the ENA value for the ACT parameter.

g The Framing mode for the outgoing PDH references must be such that the SSM values can be written into it. For instructions on configuring the Framing mode, see Configuring PDH for ATM transport.

ZDYE:<synchronisation reference>,<reference index>...:ACT=<action>;


27

Integrating RNC

Id:0900d805805de854

8 Check the SSM generation valuesZDYI:SSMGEN;

9 Change the SSM generation values if necessaryZDYK:<synchronisation reference>,<reference index>:<SSM generation>;

10 Use the synchronisation reference as the forced reference of system clock (DYS)Use the DYS command to set a synchronisation reference as the forced reference of the system clock. Notice that the forced reference can even be lost and the operation mode of the system clock is changed to Holdover. The changes in the quality of the other ref-erences do not affect the forced reference setting.

Give the value Y for the ACT parameter.

You can release synchronisation reference as the forced reference of system clock by giving the value N for the ACT parameter.

ZDYS:<synchronisation reference>,<reference index>:ACT=<action>;

11 Control general settings for the synchronisation system (DYR)

g With the command DYR you can reset the switching type of references, set special configuration, cut the outgoing external reference, or include or remove SSM value as selection criteria. The SSM value of the reference can be included or removed from the selection criteria when the best reference is selected to be used in the syn-chronisation of the system clocks. By default, the SSM and priority values are used when the references are ordered. You can control whether the SSM value is used or not during the reference selection.

g You must enter the parameters for the connected references to make them avail-able for the synchronisation system. The PRI value other than PRI=X tells the system that the synchronisation reference is ready to be used in the synchronisation of the system clocks. Before using it, make sure that the status of the reference is OK.

ZDYR:<command identification>,<command action>;


Integrating RNC

Id:0900d805805de859

Creating phyTTP for ATM

3 Creating phyTTP for ATMPurposeThe Physical layer Trail Termination Point (phyTTP) is configured between the physical layer and the ATM layer. The phyTTP ID is used when creating the ATM inter-face.

You can create a phyTTP for a single PDH exchange terminal (PET), an IMA group, a single SDH VC path, or a VC path of an SDH protection group.

g You cannot create a phyTTP for a single SDH VC path of a 2N redundant network interface unit. The phyTTP for a 2N redundant unit must be created for the VC path of the SDH protection group that has been created for the unit.

Before you startYou must configure the PDH or SDH interfaces (PET, SET, an IMA group, a single SDH VC path or a VC path of an SDH protection group) before you can create the phyTTP for them. For configuration instructions, see Configuring PDH for ATM transport and Configuring SDH for ATM transport.

If you need to interrogate the phyTTP configuration or the operational state of the phyTTP, use the YDI command.

Steps

1 Create a physical layer Trail Termination Point (YDC)

g The MML command for creating the phyTTP includes a parameter, payload type, for separating ATM traffic from PPP traffic. However, only ATM traffic is supported in this release.

ZYDC:<phyTTP>:(PET=<PDH exchange terminal>|IMA=<IMA group>|SET= <SDH exchange terminal>|PROTGROUP= <protection group>):[<VC path number>|<default>def]:[ATM def|PPP],[ON def|OFF];

Parameter Value

If you are creating phyTTP to a SET:

SET index of the SET

VC path number VC path number

If you are creating phyTTP to a PET:

PET index of the PET

If you are creating phyTTP to an IMA group:

IMA ID of the IMA group

If you are creating phyTTP to an SDH protection group:

PROTGROUP ID of the protection group

VC path number VC path number

Table 1 Parameters and values for creating phyTTP


29

Integrating RNC Creating phyTTP for ATM

Id:0900d805805de859

Further informationYou can delete a phyTTP with the YDD command. After the deletion, its physical resources are free to be used again; for example, you can add PET to an existing IMA group or you can protect SET by creating a protection group. On the other hand, IMA/protection group can be deleted if there is no phyTTP related to it.

The phyTTP cannot be deleted if it is used by the upper layer, that is, if there is an ATM interface created on it. You can use the YDI command to check whether the phyTTP is in use or not.

Example: Creating a phyTTP for a SETCreate a phyTTP with ID 1 of the SET with index 0 and VC path number 1.

ZYDC:1:SET=0:1:;

Example: Creating a phyTTP for a PETCreate a phyTTP with ID 1 of the PET with index 10.

ZYDC:1:PET=10;

Example: Creating a phyTTP for an IMA groupCreate a phyTTP with ID 2 of the IMA with index 20.

ZYDC:2:IMA=20;

Example: Creating a phyTTP for an SDH protection groupCreate a phyTTP with ID 4 for path 1 of protection group 4.

ZYDC:4:PROTGROUP=4:1:;


Integrating RNC

Id:0900d805805de85c

Creating ATM resources in RNC

4 Creating ATM resources in RNCPurposeThis procedure provides instructions for creating ATM resources on the following inter-faces:

• Iu-CS between RNC and MGW • Iu-PS between RNC and SGSN • Iu-BC between RNC and CBC • Iur between two RNCs • Iub between RNC and BTS

RNC uses MTP3 as the AAL type 2 signalling transport on all interfaces except on the Iub interface where SAAL UNI signalling is used.

When defining traffic parameter values, take into account the capacity limitations of an ATM interface. If the resources are misconfigured, the system will reject the creation of VP/VC connections later. See also Taking termination point into use fails.

Before you startConfigure the hardware (including exchange terminals) and the physical resources. See Physical interfaces in ATM network.

Steps

1 Create an ATM interface connected to a physical layer Trail Termination Point (LAC)ZLAC:<interface id>:<interface type>,<phyTTP>:<ADMINISTRATIVE STATE>;

Note that the interface will be unlocked.

Parameter Value

interface id Select a numerical value.

If you do not set the value manually, the system will choose a free numerical value.

interface type UNI for Iub interface

NNI for all other interfaces

UNI for mixed interfaces

phyTTP the identifier of the phyTTP

ADMINISTRATIVE STATE LOCKED-USAGE ADMINISTRATIVELY PROHIBITED

UNLOCKED-USAGE ADMINISTRA-TIVELY ALLOWED

The default is UNLOCKED

Table 2 Parameters and values for creating an ATM interface connected to a physical layer Trail Termination Point


31

Integrating RNC Creating ATM resources in RNC

Id:0900d805805de85c

2 Create the access profile of the ATM interface (LAF)ZLAF:<interface id>:<max VPI bits>:<max VCI bits>:<UPC/NPC mode>;

For details on creating the access profile, see ATM interface access profile.

Expected outcomeThe system will set the bandwidth to fully use the capacity of the physical resource. The printout indicates the Maximum ingress bandwidth value and Maximum egress bandwidth value used.

3 If you are creating ATM resources for the Iub interface

Then

Create ATM termination points using RNC RNW Object BrowserYou may need to do either (A) or (B) as follows:

(A) To create connection configuration for the Iub interface, see the instructions in Creating Radio Network Connection Configuration. The following tables indicate what values you should give for the parameters.

Parameter Value

interface id The same as the interface id selected in step 1.

This parameter is obligatory.

max VPI bits Select a suitable value, for example 5. Setting the value to 5 allows VPI values from 0 to 31 to be used.

max VCI bits Select a suitable value equal to or greater than 6, for example, 7. Setting the value to 7 allows VCI values from 32 to 127 to be used.

UPC/NPC mode Select whether UPC/NPC (policing) is to be enabled or disabled for this interface.

It is recommended to set the UPC/NPC mode as 'D' for Iub interface.

Table 3 Parameters and values for creating the access profile of the ATM interface

Parameter Value



VPI Select a VPI value within the range defined in step 2.

VP level traffic shaping Depends on network planning

egress service category CBR

Table 4 Parameters and values for creating VPLtps


Integrating RNC

Id:0900d805805de85c


☞ Ingress/Egress PPD should be set as enabled or disabled based on the type of traffic carried on the VCLtp:

• E(enabled) - AAL5 based channels (MTP3SL, AAL2SL, DNBAP, CNBAP, IPOAM, IPOAUD, IPOART)

• D(disabled) - Other channels (AAL2UD) • PVCUD could be either E or D according to the real traffic it carries

However, note that EPD is not supported and cannot be enabled in NIS1(P), NIP1 or NPS1(P).

For information about UBR+ (UBRPLUS) service category VCLtp configuration, see step 9.

(B) To create ATM termination points for IPoA connection, see the instructions in Creating ATM termination point for IP over ATM connection. The following tables indicate what values you should give to the parameters.

egress PCR Depends on network planning

Parameter Value

interface id/VPI Select one of the IF/VPI created for COCO.

VCI Select a VCI value within the range defined in step 2.

service category CBR

EPD See the Tip following the table

PPD See the Tip following the table

ingress PCR Depends on network planning


Table 5 Parameters and values for creating VCLtps for CBR traffic

Parameter Value




VP level traffic shaping Depends on network planning

egress service category Depends on network planning

egress QoS class Depends on network planning


Table 6 Parameters and values for creating VPLtps

Parameter Value

Table 4 Parameters and values for creating VPLtps (Cont.)


33


Id:0900d805805de85c

☞ The rest of the steps except the last one in this procedure are not necessary for Iub interface.

4 Create VPLtps for UBR traffic, if necessary (LCC)You need to create VPLtps for UBR traffic (IP over ATM connection) for the following:

• In Iu-CS interface, one VPLtp for O&M traffic. Depending on the network planning, this may not be necessary.

• In Iu-PS interface, the necessary number for data traffic. • In Iu-BC interface, the necessary number for IP traffic and data traffic.

ZLCC:<interface id>, <tp type>, <VPI>,,<VPL service level>:<segment endpoint info>,<VP level traffic shaping>::<egress service category>,,,<egress QoS class>:;

5 Create VPLtps for CBR traffic (LCC)You need to create VPLtps for CBR traffic for the following:

Parameter Value


service category Depends on network planning

EPD See the Tip in step 3

PPD See the Tip in step 3

QoS class Depends on network planning



Table 7 Parameters and values for creating VCLtps

Parameter Value



tp type VP


VPL service level VC

segment endpoint info Depends on network planning

VP level traffic shaping NO

egress service category U (UBR)

egress QoS class U (Unspecified Class)

Table 8 Parameters and values for creating VPLtps for UBR traffic


Integrating RNC

Id:0900d805805de85c


• In Iu-CS interface, the necessary number for SS7 (MTP3SL) signalling or SS7 sig-nalling over IP (IPOAM), and routing AAL type 2 user data (AAL2UD).

• In Iu-PS interface, the necessary number for SS7 (MTP3SL) or SS7 signalling over IP (IPOAM) signalling traffic.

• In Iu-BC interface, the necessary number for IP traffic (IP over ATM connections).☞ If an ATM Virtual Path Leased Line service is used to implement the Iu-BC inter-

face, a VPLtp should be created as CBR type with defined Peak Cell Rate. VP level traffic shaping should be enabled to limit the peak cell rate of the VP and thus avoid cell loss due to policing in the ATM network.

• In Iur interface, the necessary number for SS7 (MTP3SL) signalling or SS7 signal-ling over IP (IPOAM), and routing AAL type 2 user data (AAL2UD).

ZLCC:<interface id>, <tp type>, <VPI>,,<VPL service level>:<segment end point info>,<VP level traffic shaping>::<egress service category>,,,<egress QoS class>:::<egress PCR>,<egress PCR unit>;

For details on creating termination points of CBR type, see Basic guideline for calculat-ing CDVT.

6 Create VPLtps for UBR+ (UBRPLUS) traffic (LCC)You need to create the necessary number of VPLtps for AAL type 2 user data (AAL2UD) traffic in Iub interface.

Note that the VPs are non-shaped for UBR+.

ZLCC:<interface id>,<tp type>,<VPI>,,<VPL service level>:<segment endpoint info>,<VP level traffic shaping>::<egress service category>,,,<egress QoS

Parameter Value



tp type VP




VP level traffic shaping For Iu-BC, FULL

For other interfaces, depends on network planning

egress service category C (CBR)

egress QoS class C1 (QoS Class number 1)


egress PCR unit Depends on network planning

Table 9 Parameters and values for creating VPLtps for CBR traffic


35


Id:0900d805805de85c

class>:::<egress PCR>,<egress PCR unit>,,,<egress MDCR>,<egress MDCR unit>;

7 Create VCLtps for UBR traffic, if necessary (LCC)You need to create VCLtps for UBR traffic for the following:

• In Iu-PS interface, the necessary number for data traffic. You need at least one IP over ATM connection per GTPU unit.

• In Iu-BC interface, the necessary number for IP traffic and data traffic. You need at least one IP over ATM connection per ICSU unit.

ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingress service category>,<ingress EPD>,<ingress PPD>,<ingress QoS class>:<egress service category>,<egress EPD>,<egress PPD>,<egress QoS class>;

Parameter Value



tp type VP




VP level traffic shaping NO

egress service category UP (UBRPLUS)

egress QoS class U



egress MDCR Depends on network planning

egress MDCR unit Depends on network planning

Table 10 Parameters and values for creating VPLtps for UBR+ traffic

Parameter Value



tp type VC



Table 11 Parameters and values for creating VCLtps for UBR connection


Integrating RNC

Id:0900d805805de85c


8 Create VCLtps for CBR traffic (LCC)You need to create VCLtps under the VPLtp(s) for CBR traffic for the following:

• In Iu-CS interface, the necessary number of VCLtps for SS7 (MTP3SL) signalling and routing AAL type 2 user data (AAL2UD) traffic.

• In Iu-PS interface, the necessary number for SS7 (MTP3SL) signalling and data traffic (IPOAUD).

• In Iur interface, the necessary number of VCLtp for SS7 (MTP3SL) signalling and routing AAL type 2 user data (AAL2UD) traffic.

• In lur, lu-CS and lu-PS interface, the necessary number of VCLtps for SS7 signalling over IP (SIGTRAN) traffic (IPOAM).

ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingress service category>,<ingress EPD>,<ingress PPD>,<ingress QoS class>:<egress service category>,<egress EPD>,<egress PPD>,<egress QoS class>::<ingress PCR>,<ingress PCR unit>:<egress PCR>,<egress PCR unit>;

ingress service category U (UBR)

ingress EPD See the Tip in step 3

ingress PPD See the Tip in step 3

ingress QoS class U

egress service category U (UBR)

egress EPD See the Tip in step 3

egress PPD See the Tip in step 3

egress QoS class U

Parameter Value

Table 11 Parameters and values for creating VCLtps for UBR connection (Cont.)

Parameter Value



tp type VC



ingress service category C (CBR)



ingress QoS class C1

Table 12 Parameters and values for creating VCLtps for CBR traffic


37


Id:0900d805805de85c

For details on creating termination points of CBR type, see Basic guideline for calculat-ing CDVT.

9 Create VCLtps for UBR+ (UBRPLUS) traffic (LCC)You need to create the necessary number of VCLtps for AAL type 2 user data (AAL2UD) traffic in Iub interface.

ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingress service category>,<ingress EPD>,<ingress PPD>,<ingress QoS class>,<ingress UBRSHARE>:<egress service category>,<egress EPD>,<egress PPD>,<egress QoS class>,<egress UBRSHARE>::<ingress PCR>,<ingress PCR unit>,,,<ingress MDCR>,<ingress MDCR unit>:<egress PCR>,<egress PCR unit>,,,<egress MDCR>,<egress MDCR unit>;

egress service category C (CBR)



egress QoS class C1


ingress PCR unit Depends on network planning



Parameter Value

Table 12 Parameters and values for creating VCLtps for CBR traffic (Cont.)

Parameter Value



tp type VC



ingress service category UP (UBRPLUS)



ingress QoS class U

ingress UBRSHARE * optional

egress service category UP (UBRPLUS)


Table 13 Parameters and values for creating VCLtps for UBR+ traffic


Integrating RNC

Id:0900d805805de85c


*) UBRSHARE UBRSHARE is used to differentiate the traffic (RT-DCH, NRT-DCH, HSUPA, HSDPA). The possible values of UBRSHARE are 0~1000. UBRSHARE differentiates Weight for UBR+ VCLtp.

• For NPS1, the Weight is affected by UBRSHARE only. The Weight is in direct proportion to int(UBRSHARE/20). If you set a value to a integer under 40, it has the same effect as you set it to 40.

• For NIS1, CBR VCLtp, UBR+ VCLtp and UBR VCLtp all use WRR scheduling method. • Weight for CBR VCLtp is affected by CBR VCLtp's PCR. • Weight for UBR+ VCLtp is affected by UBR+ VCLtp's MDCR

and UBRSHARE. • Weight for UBR VCLtp is affected by UBR VCLtp's UBRSHARE

(the value of UBRSHARE is 1).


egress QoS class U

egress UBRSHARE * optional


ingress PCR unit Depends on network planning

ingress MDCR Depends on network planning

ingress MDCR unit Depends on network planning



egress MDCR Depends on network planning

egress MDCR unit Depends on network planning

Parameter Value

Table 13 Parameters and values for creating VCLtps for UBR+ traffic (Cont.)


39

Integrating RNC Creating IP resources in RNC

Id:0900d805805de872

5 Creating IP resources in RNC

5.1 Creating and modifying VLAN interfacesPurposeYou can create and delete a VLAN interface with commands QRM and QRR. After VLAN interface is created, you can configure parameters of VLAN interfaces with the QRN command. NPGE(P) is the only unit to support VLAN interface. The VLAN interface is configured according to IEEE 802.1Q protocol.

Steps

1 Interrogate the VLAN interfacesCheck the configured VLAN interfaces of the computer unit before configuring the new ones.

ZQRE:[<UNIT TYPE>],[<UNIT INDEX>]:[<VLAN NAME>]:[<VLAN ID>]:[<VLAN PHYSICAL INTERFACE>];

2 Create the VLAN interfacesCreate the VLAN interface identified by the VLAN name and the VLAN ID, and attach them to one physical GE interface.

ZQRM:<UNIT TYPE>,<UNIT INDEX>:<VLAN NAME>:<VLAN ID>:<VLAN PHYSICAL INTERFACE>;

The VLAN name should be exclusive within one unit and the VLAN ID should also be only attached to one physical interface.

3 Delete the VLAN interfacesIdentify the VLAN interface you want to delete by the parameters VLAN name or VLAN ID within one unit. The VLAN interface parameters should be removed with command QRG before deleting the VLAN interface.

ZQRR:<UNIT TYPE>,<UNIT INDEX>:[<VLAN NAME>:<VLAN ID>];

4 Configure or modify the parameters of the VLAN interfacesConfigure or modify the IPv4 address, MTU and if state into the existing VLAN interface. For detailed instructions, see Configuring IP parameters and addresses of interfaces.

g The VLAN interface's status is dependent on the Ethernet interface. It requires Ethernet interface with up status first.

5 Delete the VLAN interface parametersZQRG:<unit type>,<unit index>:<interface name...>;

Example: This example shows how to create and configure the VLAN interface.


Integrating RNC

Id:0900d805805de872

Creating IP resources in RNC

1. Create a VLAN interface to NPGE-0 unit.The VLAN name is 'VL8', the VLAN ID is 5, and they are attached to physical inter-face IFGE0.ZQRM:NPGE,0:VL8:5:IFGE0;

2. Interrogate all VLAN interfaces in NPGE-0ZQRE:NPGE,0;

3. Delete the VLAN interface and whose name is 'VL8'ZQRR:NPGE,0::VL8;

4. Configure IP address to the VLAN interfaceZQRN:NPGE,0:VL8:10.1.1.8,P:24:;

5. Modify the MTU value and its state of the VLAN interfaceZQRN:NPGE,0:VL8::::1200:UP;


41

Integrating RNC

Id:0900d805805ca5ba

5.2 Configuring IP parameters and addresses of interfacesPurposeYou can configure a new network interface or IP address with the QRN command in IPv4.

The interface-specific instructions for configuring IP interfaces can be found in the Inte-gration instructions.

Steps

1 Interrogate network interfaces (QRI)Check the configured network interfaces of the computer unit before configuring new ones.

All IPv4 addresses of the network interface will be displayed.

ZQRI:<unit type>,<unit index>::YES;

2 Create IPv4 interfaces (QRN)Identify the IP interface you want to create with parameters unit type, unit index and interface name. You can also add an IPv4 address of the network interface by giving the desired IPv4 address.

The default value for netmask length is 8 (A class), 16 (B class), or 24 (C class).

For 2N NPGE(P)/NPS1(P) unit, only logical address can be configured because the IP configuration on NPGE(P)/NPS1(P) should always be identical.

ZQRN:<unit type>,[<unit index>]:<interface name>,[<point to point interface type>]:[<IP address>],:[<netmask length>]:[<destination IP address>]:[<MTU>]:[<state>];

g If the jumbo frames is supported, it is recommended to configure the MTU with enough big value, for example 4500 on NPGE(P) (IFGE0/IFGE1) interface to avoid fragmentation because the fragmentation/defragmentation affects the NPGE(P)'s performance.

3 Modify IPv4 interfaces (QRN)Identify the IP interface you want to modify with parameters unit type, unit index and interface name.

ISU and OMU units NPGE units NPS1 units

EL AA IFGE IFFE IFAI IFAE IFFE IFAI

Min MTU

1500 500 500 1500 500 500 1500 500

Max MTU

1500 9180 4500 1500 4500 9180 1500 4500

Default MTU

1500 9180 1500 1500 1500 9180 1500 1500


Integrating RNC

Id:0900d805805ca5ba

ZQRN:<unit type>,[<unit index>]:<interface name>,[<point to point interface type>]:[<IP address>],:[<netmask length>]:[<destination IP address>]:[<MTU>]:[<state>];

The numbered or unnumbered point to point interface type parameter is valid only for ATM point-to-point interfaces. If you want to change the point-to-point inter-face type you must remove the interface by using the command QRG and configure it to another point-to-point interface type.

N A numbered interface has a unique IP address. This is the default value.

U An unnumbered interface does not have a unique IP address. It shares its IP address with the Ethernet interface IP address.

4 Delete IPv4 interface (QRG)All IPv4 addresses of this interface will be deleted along with the network interface. If IP address is identified, only this IP address will be deleted.

ZQRG:<unit type>,<unit index>:<interface name...>:<IP address>;

5 Change existing IP configuration for a point-to-point interfaceIf you want to change the IP configuration in a point-to-point interface where InATMARP is used, follow the steps below:

a) Block the IPoA VCC (QMG)ZQMG:UNIT=<unit type> | <ATM=<ATM interface> | USAGE=<usage> | INDEX=<unit index>:[<VPI> | all def,<VCI> | all def]:<change>;

b) Delete the existing routing. If OSPF is in use, delete the OSPF interface:ZQKL:<unit type>,<unit index>: [<interface identification>];If static routing is in use, delete all the static routes that have been configured for the interface. For detailed instructions, see Creating and modifying static routes.

c) Delete the IP address (QRG)ZQRG:<unit type>,<unit index>:<interface name...>;

d) Create the new IP address (QRN)ZQRN:<unit type>,<unit index>:<interface name>,(<point to point interface type>):(<IP address>),(<IP address type> ):(<netmask length>):(<destination IP address>):(<MTU>):(<state>);

e) Unblock the IPoA VCC (QMG)ZQMG:UNIT=<unit type> | <ATM=<ATM interface> | USAGE=<usage> | INDEX=<unit index>:[<VPI> | all def,<VCI> | all def]:<change>;

f) Reconfigure routing.If OSPF is in use, reconfigure the OSPF parameters:ZQKF:<unit type>,<unit index>:<interface identification>:<area identification>;If static routing is in use, create new static routes. For detailed instructions, see Creating and modifying static routes.


43

Integrating RNC

Id:0900d805805ca5ba

Example: Adding a new IP address to OMUThis example shows how to add new IP addresses to the EL0 interface of the OMU unit with index 0. The IPv4 address of the interface is 10.20.41.130 and netmask length is 24.

ZQRN:OMU,0:EL0:10.20.41.130,P:24;

Example: Creating a logical IP address for a 2N redundant unitIf you want to create a logical address for a 2N redundant unit, do not include the unit index parameter and assign the value L to the IP address type parameter. In IPv4 logical IP address configuration, for example, the netmask length is 27 and the status is set to UP.

ZQRN:OMU:EL0:131.228.45.179,L:27:::UP;

ZQRN:NPGEP,0:IFGE0:192.168.3.3,L:24:::UP:;

Example: Changing the existing IPv4 configuration for a point-to-point interfaceThis example changes the IPv4 configuration for OMU interface AA11.

1. Block the IPoA VCC (QMG)ZQMG:ATM=11:0,32:2;

2. Delete the OSPF interface in OMU-1 (QKL)ZQKL:OMU,1:AA11;

3. Delete the IP address in OMU-1 (QRG)ZQRG:OMU,1:AA11;

4. Create the new IP address (QRN)ZQRN:OMU:AA11,U:10.1.1.2,L::10.1.12.1:1500:UP;

5. Unblock the IPoA VCC (QMG)ZQMG:ATM=11:0,32:1;

6. Reconfigure the OSPF parameters (QKF)ZQKF:OMU,1:AA11:10.1.12.0;ZQKF:OMU,0:AA11:10.1.12.0;


Integrating RNC

Id:0900d805805de866

5.3 Configuring signalling transport over IP over ATM for control planePurposeThe purpose of this procedure is to configure the IP-based signalling transport over ATM connection for RNC control plane. IP-based Iu-PS, Iu-CS and Iur SS7 signalling stack can be used. For more detailed description, refer to Planning site configuration for sig-nalling and Creating M3UA configuration.

Before you startATM resources must be created before starting this procedure. Signalling unit shall be in active state before configuration starts.

Steps

1 Configure two IP over ATM interfaces to a signalling unit (QMF)ZQMF:<unit type>,[<unit index>],<logical connection type>:<IP interface>:<ATM interface>,<VPI number>,<VCI number>:[<encapsulation method>],[<usage|IPOAM def>];

g Signalling unit should be in an active state before configuration.

2 Assign IP addresses to both ATM interfaces of a signalling unit (QRN)ZQRN:<unit type>,[<unit index>]:<interface name>,[<point to point interface type>]:<IP address>,[<IP address type>]:[<netmask_length>]:[<destination IP address>]:[<MTU>]:[<state>];

g IP addresses must be assigned from different sub-networks.

3 Create static routes if needed (QKC)ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>,[<local IP address>]:[<route type>]:[<route preference>];

g The parameter local IP address is only valid for local IP address based default route. For normal static routes, you do not need to give the local IP address. For more infor-mation about local IP address based default routes, refer to Creating and modifying static routes.

4 Make the IP configuration changesWhen making changes to an IPoA configuration on ICSU, there should be no sockets in ESTABLISHED state using the relevant IP address. This can be achieved by removing the SCTP association from the association set. After all necessary changes to IPoA con-figuration are done, a new association can be added to the association set.


45

Integrating RNC

Id:0900d805805de866

Example: The following example shows how to configure ICSU-0 to connect to SGSN with IP over ATM connection. Suppose the subnet address for Iu-PS signaling of SGSN is 10.2.3.0/24. The ATM AAL5 connection should be configured properly beforehand.

ZQMF:ICSU,0,L:AA0:1,0,40:1,IPOAM;

ZQRN:ICSU,0:AA0,N:10.20.1.1,L::10.20.1.2:;

ZQKC:ICSU,0:10.2.3.0,24:10.20.1.2,:LOG:;


Integrating RNC

Id:0900d805805de869

5.4 Configuring signalling transport over IP over Ethernet for control planePurposeThe purpose of this procedure is to configure the IP-based signalling transport over Ethernet for RNC control plane. IP-based Iu-PS, Iu-CS, and Iur SS7 signalling stack can be used. For detailed description, refer to Planning site configuration for signalling and Creating M3UA configuration.

Before you startCheck that the LAN cables are correctly attached to the NPGE(P) unit. For more infor-mation, see Cable Lists in Site documentation.

The signalling unit and the NPGE(P) unit should be in active state before the configura-tion starts.

Steps

1 Assign the IP addresses to the Ethernet interfaces of the NPGE(P) unit (QRN)ZQRN:<unit type>,[<unit index>]:<interface name>:<IP address>,<L/P>:[<netmask length>]:;

g The IP addresses must be assigned from different sub-networks.

2 Create the static routes in the NPGE(P) unit (QKC)ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>,[<local IP address>]:[<route type>]:[<route preference>];

3 Prepare the internal IP over ATM connection

a) Use the existing full mesh IPoA for Iur/Iu interfaceThe system maintains a full mesh IPoA connection between ICSU and NPGE(P) unit. It is mainly used for IP based Iub interface.The instructions of configuring IP address for Iub on top of the full mesh IPoA was included in chapter Configuring IP resources for Iub Control Plane (RNC-BTS/AXC) step 5. It is recommended to use the same configuration for Iur/Iu interface to simplify the process.

b) Configure separate internal IP over ATM interface to a signalling unit and the NPGE(P) unit (QMC)ZQMC:ICSU,[<unit index>],L:<IP interface>:<NPGE/NPGEP>,<unit index>,L:<IP interface>::;

g The signalling unit and the NPGE(P) unit should be in an active state before the configuration starts.

4 Assign the IP addresses to both ATM interfaces of a signalling unit and the NPGE(P) unit (QRN)ZQRN:<unit type>,[<unit index>]:<interface name>,U/N:<IP address>,L:32:[<destination IP address>]:<MTU size>:;


47

Integrating RNC

Id:0900d805805de869

g The parameter IP address and the destination IP address configured to the signal-ling unit should be the parameter destination IP address and the IP address config-ured to the NPGE(P) unit.

The full mesh IPoA uses unnumbered addressing by default. Because the system expects an existing IP address during configuration, the IP address can be config-ured to LO0 interface first.

The MTU size should be no more than PMTU among all the connections. If one of those connections is connected to FlexiBTS, the PMTU should be no larger than 1472.

5 Create the static routes in the signalling unit (QKC)ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>,[<local IP address>]:[<route type>]:[<route preference>];

g The IP address for the internal IP over ATM interface of NPGE(P) unit is used as a gateway address for the signalling unit to route traffic.

The parameter local IP address is only valid for local IP address based default route. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes.


7 Create OSPF configuration in NPGE(P) unit if needed (QKF)If dynamic route is used, refer to chapter Creating OSPF configuration for O&M connec-tion to NetAct.

8 Configure the OSPF to inform other OSPF routers of the ICSUs' IP sub-net if needed (QKJ)Redistribution can also be used to inform the IP sub-net of ICSU with the QKU MML command.

If the dynamic route is used, refer to chapter Creating OSPF configuration for O&M con-nection to NetAct.

Example: Configuring signalling transport over IP over Ethernet for control planeThe following example shows how to configure ICSU-0 to connect to SGSN with multi-homing IP over Ethernet connection, going through NPGEP-0 and NPGEP-2.

The existing internal IPoA network is used to simplify the configuration.

The IP addresses for ICSU-0 are 10.20.1.1 and 10.20.2.1. They are used later as the SCTP primary source IP address and the secondary source IP address.


Integrating RNC

Id:0900d805805de869

The IP address for NPGEP-0 is 10.20.1.2 and the IP address for NPGEP-2 is 10.20.2.2.

The sub-net addresses for Iu-PS signaling of SGSN are 10.2.3.0/24 and 10.2.4.0/24.

The IP addresses for SGSN are 10.2.3.1 and 10.2.4.1.

The IP addresses for site routers are 10.20.1.3 and 10.20.2.3.

1. Enable IP forwarding in the NPGE(P)This is used for routing the packets.ZQRT:NPGEP,0:IPF=YES,;ZQRT:NPGEP,2:IPF=YES,;

2. Assign IP addresses to the Ethernet interfacesZQRN:NPGEP,0:IFGE0:10.20.1.2,L:24;ZQRN:NPGEP,2:IFGE0:10.20.2.2,L:24;

3. Create the static routes for the NPGE(P)ZQKC:NPGEP,0:10.2.3.0,24:10.20.1.3;ZQKC:NPGEP,2:10.2.4.0,24:10.20.2.3;

4. Check the existing internal IPoA interfacesZQMQ:ICSU,0;

5. Assign IP addresses to the IPoA interfacesThe interfaces are from the output of step 1. • AA495 <-> IFAI79 of NPGEP-0 • AA496 <-> IFAI79 of NPGEP-2The IP addresses for NPGEP is used also in internal IPoA interface.ZQRN:ICSU,0:LO0:10.20.1.1;ZQRN:ICSU,0:LO0:10.20.2.1;ZQRN:ICSU,0:AA495,U:10.20.1.1,L::10.20.1.2:;ZQRN:ICSU,0:AA496,U:10.20.2.1,L::10.20.2.2:;ZQRN:NPGEP,0:IFAI79,U:10.20.1.2,L::10.20.1.1;ZQRN:NPGEP,2:IFAI79,U:10.20.2.2,L::10.20.2.1;

6. Create static routes for the ICSUZQKC:ICSU,0:10.2.3.0,24:10.20.1.2,:LOG:;ZQKC:ICSU,0:10.2.4.0,24:10.20.2.2,:LOG:;

7. Verify the IP connectivity from ICSU to SGSNZQRX:ICSU,0:IP=10.20.1.3;ZQRX:ICSU,0:IP=10.20.2.3;ZQRX:ICSU,0:IP=10.2.3.1;ZQRX:ICSU,0:IP=10.2.4.1;

Example: Configuring signalling transport over IP over Ethernet for control plane with OSPFThe following example shows how to configure the ICSU-0 to connect to SGSN with multi-homing IP over Ethernet connection, going through NPGEP-0 and NPGEP-2.








49

Integrating RNC

Id:0900d805805de869








8. Create OSPF for NPGE(P)a) Configure the area(s) that include also the neighbouring routers

ZQKE:NPGEP,0:0.0.0.1;ZQKE:NPGEP,2:0.0.0.1;

b) Configure two interfaces for that area. The values for parameters area identification, hello interval, and router dead interval must be the same as in the external router.IFGE0 or IFGE1 can be selected as the primary route for signalling traffic by giving different OSPF costs. The interface with lower cost will be preferred.ZQKF:NPGEP,0:IFGE0:0.0.0.1:::10;ZQKF:NPGEP,2:IFGE0:0.0.0.1:::20;


Integrating RNC

Id:0900d805805de86c

5.5 Configuring IP resources for Iub control plane (RNC-BTS/AXC)PurposeThe purpose of this procedure is to prepare and configure IP resources for Iub control plane.


Steps

1 Start the MMI Window in the Element Manager

2 Connect RNC to BTS/AXC via NPGE(P)The NPGE(P) unit is used for Ethernet connection to the external IP network. In Iub, only IPv4 is supported for the control plane.

Check that the LAN cables are correctly attached to the NPGE(P) unit. For more infor-mation, see Cable Lists in Site documentation.

a) Interrogate the states of the units in the system (USI)Check that the units for which you are going to create network interfaces are in working state (WO-EX). Enter the name of the unit for the unit type parameter.ZUSI:<unit type>;

b) Assign an IP address to the external Ethernet interface of NPGE(P) (QRN)See instructions in Configuring IP parameters and addresses of interfaces.ZQRN:<unit type>,<unit index>:<interface name>:<IP address>,:<netmask length>:::;

g The external IP interface addresses must be configured in different sub-nets.

3 Configure the default static routes for NPGE(P)Create the default static routes from NPGE(P) to the external destination (for example, a router). See instructions in Creating and modifying static routes.

g 2N redundant units (NPGEP) must have logical static routes for IPv4.

You can have several NPGE(P) interfaces to the same destination network. To enable load sharing in the NPGE(P) units, configure default routes through more than one NPGE(P) interfaces.

4 Configure IP based route in NPGE(P)IP based route ID is used by ICSU to select a right NPGE(P), through which signalling traffic is routed. For detailed instructions, refer to chapter IP based route configration.


51

Integrating RNC

Id:0900d805805de86c

5 Configure local IP sub-net for Iub control planeSystem selects ICSU for NBAP links based on load sharing algorithm. So all ICSUs' AAx interfaces used for internal IPoA connections between ICSU and NPGE(P) shall have one IP address from the same IP sub-net configured.

a) Interrogate the states of internal IPoA connections created by the system (QMQ)Check that all ICSUs have internal IPoA connections to all NPGE(P). The range of interface names on ICSU side is from AA450 to AA511. The range of interface name on NPGE(P) side is from IFAI30 to IFAI79. The interface name for the unit is allo-cated by the unit logical address statically.ZQMQ:ICSU;

b) Configure local IP sub-net address for Iub control plane (QMN)ZQMN:1:<IPV4 address>,<netmask length>:;

c) Check the local IP sub-net and IP address configurationThe IP address for all the reserved internal IPoA is configured. The range of the IP address is from the sub-net IP address to the sub-net IP address plus 63. The IP address for the ICSU unit is allocated by the unit logical address statically, while the IP address for the NPGE(P) unit is allocated by unit address dynamically. This means the IP address for the NPGE(P) unit may be changed if the NPGE(P) is changed from WO-EX to SE-NH and then from SE-NH to WO-EX.ZQML;ZQRI:<unit_type>,<unit_index>;

6 Modify local IP sub-net for Iub control planeBefore deleting the local IP sub-net, make sure that there are no NBAP links in the sub-net. The RNW object browser should be used to check these links and all the links should be deleted before the local IP sub-net is deleted. Otherwise, even the sub-net is recreated with the same sub-net address, some links will not recover. In that case, the RNW object browser is used to remove these dead links.


Integrating RNC

Id:0900d805806207e2

5.6 Configuring IP for user plane with NPGE(P)PurposeThe NPGE(P) unit is used for Ethernet connections to the IP based interfaces, such as Iub, Iur, Iu-CS, Iu-PS. NPGE(P) unit terminates UDP/IP protocols and forwards packets to SGSN, MGW, RNC, and so on.

Before you startCheck that the LAN cables are correctly attached to the NP2GE unit. For more informa-tion, see Cable Lists in Site documentation.

Steps

1 Interrogate the states of the units in the system (USI)Check that the units for which you are going to create network interfaces are in working state (WO-EX). Enter the unit name for the unit type parameter.

ZUSI:<unit type>;

2 Configure the Ethernet interface in NPGE(P) (optional)Change the Ethernet interface working rate if the connected Ethernet device requires it. The communication fails if different working mode is set on the connected Ethernet devices.

NPGE(P) also provides Ethernet shaping functionality, so a specific value for the band-width can be associated to the IFGE Ethernet interface (not allowed for IFFE interface) to restrict the output rate.

For detailed instructions, see chapter Configuring Etherent interfaces

ZQAS:<unit type>,<unit index>:<IFGE0|IFGE1>:[<rate value>],[<bandwidth value>];

3 Create VLAN interface in NPGE(P) (optional)First create VLAN interface if VLAN functionality is used in NPGE(P). See instructions in Creating and modifying VLAN interfaces.

ZQRM:<NPGE/NPGEP>,<unit index>:<VLAN name>:<VLAN id>:<VLAN physical interface>;

4 Assign an IP address to the external Ethernet interface or VLAN interface of NPGE(P) unitSee instructions in Configuring IP parameters and addresses of interfaces.

For IPv4:

ZQRN:<unit type>,<unit index>:<interface name>:<IP address>,:[<netmask length>]:::;

g Ensure the IFGE interface in UP state before activating the VLAN interface. Create the VLAN interface before configuring IP address.


53

Integrating RNC

Id:0900d805806207e2

g If the jumbo frames are supported, it is recommended to configure the MTU with enough big value, for example 1600 on NPGE(P) (IFGE0/IFGE1) interface to avoid fragmentation because the fragmentation/defragmentation affects the NPGE(P)'s performance. The defragmentation of unordered fragments is not supported in NPGE(P).

The QRN MML command is used to change the MTU value.

ZQRN:<unit type>,<unit index>:<interface name>::::[<MTU>]:;

5 Assign an IP address to the loopback interface of NPGE(P) unit, if necessaryFor detailed instructions, see chapter Configuring IP parameters and addresses of inter-faces.

For IPv4:


6 Configure IP based routeSet up the IP based route identifier list and designate the committed bandwidth as well as committed signalling bandwidth. Then configure the IP based route according to the identifier list. For details, see WCDMA Radio Network Configuration Parameters.

The IP based route is bound to the correct WBTS/Iur/Iu-CS/Iu-PS interface with the RNC RNW Object Browser before taking it into use, for details, see chapter Configuring RNC.

ZQRU:<action mode>:<[ip_based_route_id],[ip_based_route_name]>:[ip_based_route_bandwidth]:[committed_bandwidth]:[committed_signal_bandwidth]:[committed_dcn_bandwidth]:[ifc_option],[ifc_ratio];

g If the 'committed_bandwith', 'committed_signal_bandwidth' and 'committed_dcn_bandwidth' are all zero, it means no CAC is done in this IP based route. In the ADD mod, the ip_based_route_name is obligotary, the default values for 'ip_based_route_bandwidth', 'committed_bandwith', 'committed_signal_bandwidth' and 'committed_dcn_bandwidth' are zero. The 'ifc_option' can be ON only when connected to the Iub interface. When the 'ifc_option' is ON, it means there is flow control for this IP based route. In the MOD mode, the ip_based_route_id is obligatory, the 'ifc_option' can not be modified and the 'ifc_ratio' can be modified when original 'ifc_option' is ON.

ZQRC:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<IPV4>]=<IP ADDRESS>:<ID/NAME>=<IP BASED ROUTE ID/”IP BASED ROUTE NAME”>;

If an IP based route is attached to more than one IP address, it means load sharing for this IP based route is enabled.

g The IP based route CAC can not work in load sharing mode.

7 Configure the static routes for NPGE(P)Create the static routes from NPGE(P) to the external destination (for example, a router). See instructions in Creating and modifying static routes.


Integrating RNC

Id:0900d805806207e2

2N redundant units (NPGEP) must have logical static routes. You can have several NPGE(P) interfaces to the same destination network. To enable load sharing in the NPGE(P) units, configure static routes through more than one NPGE(P) interfaces.

g The internal load sharing handles the incoming and outgoing RTP/UDP/IP streams respectively. The source IP address selection based on IP based route configuration and the outgoing interface selection based on routing table are totally independent from each other. For outgoing traffic, the source IP address allocated to IFGE0 can be transmitted via IFGE1 or vice vesa. To avoid the asymmetric traffic behavior, there are IP based routes per destination subnet and the routes can be configured through the same interface as selected source IP address for that connection.

For IPv4:

ZQKC:<unit type>,<unit index>:<destination IP address>,[<netmask length>]:<gateway IP address>:[<route type>]:[<route preference>];

8 Create the BFD session and associate it with IP based route, if necessaryBFD sessions monitor the IP path status and, if configured so, provide the alarms. Each BFD session monitors the path between a local and a remote IP endpoint.One or more than one BFD sessions can be associated to an IP based route so that the IP link status can be used by the system in order to prevent an unavailable IP path and give a fast call setup failure on that IP based route. For details about BFD configuration, see YG - BFD Supervision Handling document.

ZYGS:C:<unit type>,<unit index>,<session_id>,<local IP address>,<remote IP address>:PROF=<BFD profile id>,ALARM=<ON/OFF>,ROUTE=<IP based route id>;

9 Create OSPF configuration, if necessaryCurrently, OSPF only supports IPv4 and is licence based. If you want to use OSPF routing on the Iu-PS interface, create the configuration as follows:

a) Set the IP address for loopbackZQRN:<unit type>,<unit index>:<interface name>:<IP address>;

b) Configure the OSPF to inform other OSPF routers of the loopback addressZQKU:<unit type>,<unit index>:<redistribute type and identification>:<metric>;

c) Configure the area(s) that include also the neighbouring routersZQKE:<unit type>,<unit index>:<area identification>:<stub area>,[<stub area route cost>],<totally stubby area>;

d) Configure an interface for that areaZQKF:<unit type>,<unit index>:<interface specification>:<area identification>:[<hello interval>]:[<router dead interval>]:[<ospf cost>]:[<election priority>]:[<passive>]: [<authentication> | <authentication>,<password>];

10 Create the user defined DSPM profile (optional)Besides the default mapping profile, you can create the DSCP to PHB mapping profile. For more information, see Configuring DSCP to PHB mapping profile.


55

Integrating RNC

Id:0900d805806207e2

g For the two parameters 'PROFILE ID' and 'PROFILE NAME', you need to enter a value for at least one of them.

ZQ8B:<MODE>:[<PROFILE ID>]:[<PROFILE NAME>]:[<DATA TYPE>]:[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>";

11 Create the user defined PHB profile (optional)You can create the PHB mapping profile. For more information, see Configuring PHB profile.

g For the two parameters 'PROFILE ID' and 'PROFILE NAME', you need to enter the value for at least one of them.

ZQ8V:<MODE|CR/MO>:<[PROFILE ID]:[PROFILE NAME]>:<PHB VALUE>:[QUEUE WEIGHT],[MIN THRESHOLD],[MAX THRESHOLD],[WRED MAX DROP PROBABILITY],[XPONENTIAL WEIGHT FACTOR],[VLAN PRIORITY];

12 Assign the DSPM and PHB profile for NPGE(P) (optional)See instructions in Configuring and interrogating IP interface QoS parameters.

ZQ8S:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<ENABLED/DISABLED>]:[<ID1=DSPM PROFILE ID>/<NAME=”DSPMPROFILE NAME”>]:[<ID2=PHB PROFILE ID>/<NAME2=”PHB PROFILENAME”>];

Example: Configuring Ethernet interfaces between NPGE units and the external routers for Iub interfaceThe following example shows how to connect NPGE(P) unit to RNC via external physical routers for Iub interface.

The corresponding WBTS object of RNC RNW database is configured to contain the IP based route id references for the user plane traffic.

1. Interrogate the state of the unitsZUSI:NPGEP;

2. Configure the Ethernet shaping rate to limit the outgoing trafficThe same configuration must be set to the redundant unit separately.ZQAS:NPGEP,0:IFGE0:BANDWIDTH=800;ZQAS:NPGEP,1:IFGE0:BANDWIDTH=800;

3. Create IPv4 address in Ethernet or VLAN interface for the NPGE unitConfigure IPv4 address in Ethernet interface.ZQRN:NPGEP,0:IFGE0:10.33.160.4,P:28;orConfigure IPv4 address in VLAN interface.ZQRN:NPGEP,0:IFGE0:::::UP;ZQRM:NPGEP,0:VL38:8:IFGE0;ZQRN:NPGEP,0:VL38:10.33.160.4,P:28;


Integrating RNC

Id:0900d805806207e2

4. Configure the IP based route to NPGE for one BTSZQRU:ADD:20,"IPROUTE":11000:10000:100:100:ON,60;ZQRC:NPGEP,0:IFGE0:IPV4=10.33.160.4:ID=20;The ‘ip_based_route_bandwidth’, 'committed_bandwith', 'committed_signal_bandwidth', and 'committed_dcn_bandwidth' should be config-ured according to the bandwidth of last mile connection to the BTS.RNC does CAC based on 'committed_bandwith'. When the 'ifc_option' is ON, it means there is flow control for this IP based route and RNC does traffic shaping for the BTS.

5. Create static routes from NPGE to BTS via the external routerZQKC:NPGEP,0:10.33.161.0,24:10.33.160.1:PHY;

Figure 3 Connecting NPGE to multiple IP networks for Iub interface6. Create a BFD sessions and associate it with the IP based route to monitor the IP link

towards BTSIt is assumed that the remote BTS IP address is 10.33.161.2.ZYGS:C:NPGEP,0,1,10.33.160.4,10.33.161.2:PROF=0,ALARM=ON,ROUTE=20;

7. Create a user defined DSPM profile with the given ID and nameZQ8B:CR:1:"DSPM-PROFILE-1":DEC:EF="12,13",AF2="32",AF4="24,25":;

8. Assign a DSPM profile to an IP interface in NPGE by the given profile IDZQ8S:NPGEP,0:IFGE0:ENA:ID1=1:;

NPGEP-0(WO) IFGE0

NPGEP-1(SP) IFGE0

IP Network

10.33.161.110.33.160.4/28

10.33.160.4/28

10.33.160.1


57

Integrating RNC

Id:0900d805806207e2

Example: Configuring Ethernet interfaces between NPGE units and external routers for Iu-CS interface with one IP based route across multiple NPGE units

Figure 4 Configure NPGEP to multiple IP network via OSPF

The Iu-CS objects of RNC RNW database corresponding to the CS core network element are configured to contain the IP based route id references for the given MGW destination user plane sub nets.

One IP based route is attached to two IP addresses, it means to do load sharing for this IP based route. Two IP addresses added to different NPGEs is selected in a round-robin mode.

1. Interrogate the state of the unitsZUSI:NPGE;

2. Create the Ethernet interfaces for the NPGE unitsZQRN:NPGE,0:IFGE0:10.1.1.1,P:28;ZQRN:NPGE,0:IFGE1:10.1.1.20,P:28;ZQRN:NPGE,1:IFGE0:10.1.2.1,P:28;ZQRN:NPGE,1:IFGE1:10.1.2.20,P:28;

3. Set the loopback IP addresses for the NPGE unitsZQRN:NPGE,0:LO0:10.2.1.100,L:32;ZQRN:NPGE,1:LO0:10.2.2.100,L:32;

4. Configure the IP based route to NPGE for different IP networksZQRU:ADD:20,"IPROUTE":11000:10000:100:100:OFF;ZQRC:NPGE,0:LO0:IPV4=10.2.1.100:ID=20;ZQRC:NPGE,0:LO0:IPV4=10.2.2.100:ID=20;

5. Create OSPF from NPGE to MGW via the external routera) Configure the area(s) that include also the neighbouring routers

ZQKE:NPGE,0:0.0.0.1;ZQKE:NPGE,1:0.0.0.1;

NPGE

MGW

NPGE0

10.2.1.100

10.2.1.100

10.2.1.100

NPGE1

LO0

10.2.2.100

IFGE1 10.1.2.20/28

IFGE0 10.1.1.1/28

IFGE1 10.1.1.20/28

IFGE0 10.1.2.1/28

LO0


Integrating RNC

Id:0900d805806207e2

b) Configure two interfaces on each NPGE for that area. The values for parameters area identification, hello interval and router dead interval must be the same as in the external router.IFGE0 or IFGE1 can be selected as the primary route for user traffic by giving different OSPF costs. The interface with lower cost is preferred.ZQKF:NPGE,0:IFGE0:0.0.0.1:::10;ZQKF:NPGE,0:IFGE1:0.0.0.1:::20;ZQKF:NPGE,1:IFGE0:0.0.0.1:::10;ZQKF:NPGE,1:IFGE1:0.0.0.1:::20;

c) Configure the OSPF to inform other OSPF routers of the loopback addressZQKJ:NPGE,0:0.0.0.1:ADD:10.2.1.100:;ZQKJ:NPGE,1:0.0.0.1:ADD:10.2.2.100:;If the area in this example step 5.a is not configured as stub area, redistribution can be also used to inform the address of LO0.ZQKU:NPGE,0:IF=LO0;ZQKU:NPGE,1:IF=LO0;


59

Integrating RNC Configuring RNC

Id:0900d805805de886

6 Configuring RNC

6.1 Configuring SSH server in OMUPurposeThe Secure Shell (SSH) protocol introduces a secure alternative to the Telnet protocol, which means that a user can connect to the MMI system in the OMU unit using an encrypted and integrity-protected remote terminal connection. A user can connect to the SSH server in OMU using any SSH client, which supports SSH version 2, 2048 bit long RSA keys and 1024 bit long DSA keys.

In addition to the normal remote MMI connections, the Secure MMI Window and Mea-surement Explorer applications of the RNC Element Manager Application Launcher utilize SSH connections instead of Telnet and therefore setting up the SSH server in OMU unit is a mandatory task.

Steps

1 Execute the following MML commands to activate the SSH server

a) Activate the SSH server feature.ZW7M:FEA=1306:ON;

b) Create a new RSA key pair.ZI2K:PUBLICRSA,PRIVATERSA:RSA:2048:;

c) Create a new DSA key pair.ZI2K:PUBLICDSA,PRIVATEDSA:DSA:1024:;

d) Configure SSH server.ZI2S:IPV4STATE=ON,IPV4PORT=:IPV6STATE=OFF:RSAKEY=PRIVATERSA, DSAKEY=PRIVATEDSA::;

2 Log in the respective OMS unit of the RNC and execute the following steps as a root user

a) Connect to the SSH server in OMU with correct IP address and valid username.ssh <userid>@<IP address of OMU unit>

b) Accept and store the RSA key to the OMS unit and log in the OMU unit.The SSH client will prompt you to accept the RSA key fingerprint of the OMU unit before the connection can be established, as seen in the example printout below:

The authenticity of host '10.10.10.10 (OMU.RNC.OPERATOR.COM)'can't be established.RSA key fingerprint is 02:bd:25:ed:96:8d:82:e0:67:1c:18:66:93:69:be:ef.Are you sure you want to continue connecting (yes/no)?

c) Answer "yes".The OMS unit will store the RSA key fingerprint and will not prompt to accept it the next time. SSH client then notifies that the key has been stored:

Warning: Permanently added '10.10.10.10' (RSA) to the list of known hosts.

d) Type in the password of the respective user name, when prompted:<userid>@10.10.10.10's password:


Integrating RNC

Id:0900d805805de886

Configuring RNC

3 Optional step: Deactivate Telnet server for both MMI and service terminal, if requiredNote that when the SSH server has been activated in the OMU unit, it is possible to deactivate the Telnet server if insecure connection methods are not allowed.

The following step is optional and causes the Telnet server to stop responding and only SSH connections will be accepted.

Execute the following MML commands using the SSH-based MMI session, which was established from OMS previously:

ZI2T:TYPE=MML:IPV4STATE=OFF:IPV6STATE=OFF:;

ZI2T:TYPE=ST:IPV4STATE=OFF:IPV6STATE=OFF:;


61

Integrating RNC

Id:0900d805805de877

6.2 Configuring the RNC object for the first timePurposeWhen the RNC RNW Object Browser is first taken into use after commissioning, the very first task is to configure the RNC by setting the required parameters. This is done because the RNC object is the topmost object in the hierarchy, and so it has to be created first. Please note that the RNC RNW Object Browser provides online help to assist you in carrying out the tasks. You can access the online help by clicking the Help button in the RNC dialogue.

g If this initial phase of the configuration is not successful, the user cannot proceed with the rest of the configuration tasks.

Before you startOMU and OMS have to be configured to the operators O&M network. For more informa-tion, see Configuring IP for O&M backbone (RNC - NetAct) in IP Connection Configura-tion for RNC.

Steps

1 Open the RNC RNW Object Browser.A dialogue appears indicating that the RNC has not been configured.

2 Click OK.The RNC dialogue appears.

3 Configure the RNC.Enter values at least for the obligatory parameters marked with yellow. For more infor-mation on parameters, see WCDMA Radio Network Configuration Parameters.

g You cannot change the value of RNC identifier afterwards.

4 Click OK to confirm operation.

Expected outcomeThe general parameters of the RNC have been set.

Unexpected outcomeIf in any phase of the configuration an error occurs, you must acknowledge it by clicking OK. The parameter window where the error occurred is displayed, and you can either modify the parameters and try again or cancel the operation.


Integrating RNC

Id:0900d805805de87a

6.3 Configuring Iu-CS parameters of the RNCBefore you startThe RNC object has to be opened before the procedure can take place.

g If the multi-operator RAN feature is in use, you have to create and configure one Iu-CS interface per operator.

g If the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

Steps

1 Select the IUCS object.

2 Select Object → Open.

Expected outcomeThe Modify IUCS dialog appears.

3 Fill in and check core network related parameters.When using the IP/Ethernet option, configure the IP address and the subnet.

When using the IP/Ethernet option, configure the reference information of the MGW user plane IP subnet and the RNC IP based route id in the IUCS object. The MGW des-tination IP address that is signaled to the RNC at the RAB assignment is being used to retrieve the corresponding RNC IP based route reference for the Iu-CS connections. The corresponding IP based route is configured at the RNC IP layer configuration.

For more information on activating IP based Iu-CS, see Activating IP based Iu-CS in Activating RAN75 and RAN750: IP based Iu-CS and IP based Iu-PS.

Fill in and check the core network related data, that is, SS7 signaling parameters and the identification parameter of the core network element. Also fill in all RANAP-related parameters. For more information on parameters, see WCDMA Radio Network Config-uration Parameters.

g If there are cells under this core network that already use the Global PLMNid param-eter, their value cannot be changed.

4 Check the value of the digit analysis tree (ATM transport only).You can find this parameter on the General tab of the RNC object.

g Once you have created digit analyses with an MML, do not change the value of digit analysis tree from the GUI.


63

Integrating RNC

Id:0900d805805de87d

6.4 Configuring Iur parameters of the RNCBefore you startThe Iur interface must be created for each neighboring RNC. The maximum amount of RNC Iur interfaces is 32.

The RNC object has to be opened before the procedure can take place.

Steps

1 Select the neighboring RNCs tab from the RNC dialogue.

2 Fill in and check the parameters of the neighboring RNCs.When using the IP/Ethernet option, configure the IP based route id reference informa-tion in the IUR object. The IP based route id is used in the RNC to reserve the Iur user plane IP transport bearer resources. The corresponding IP based route is configured at the RNC IP layer configuration.

For more information on activating IP-based Iur, see Activating IP based Iur in Activating RAN76: IP based Iur.

Fill in and check the identification parameters of the neighboring RNCs as well as the SS7 related signaling parameters. For more information on parameters, see WCDMA Radio Network Configuration Parameters.

3 Check the value of the digit analysis tree (ATM transport only).You can find this parameter on the General tab of the RNC object.

g Once you have created digit analyses with an MML, do not change the value of the digit analysis tree from the GUI.


Integrating RNC

Id:0900d805805de880

6.5 Configuring Iu-PS parameters of the RNCBefore you startThe RNC object has to be opened before the procedure can take place.

g If the multi-operator RAN feature is in use, you have to create and configure one Iu-PS interface per operator.

g If the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

Steps

1 Select the IUPS object.

2 Select Object → Open.

Expected outcomeThe Modify IUPS dialog appears.

3 Fill in and check core network related parameters.When using the IP/Ethernet option or IP over ATM option with NPS1 network interface card, then configure the reference information of the PS core network element user plane IP subnet and the RNC IP based route id in the IUPS object. The PS core network element destination IP address that is signaled to the RNC at the RAB assignment is being used to retrieve the corresponding RNC IP based route reference for the Iu-PS connections. The corresponding IP based route is configured at the RNC IP layer con-figuration. The IP based route id reference information is not needed with GTPU HW based Iu-PS.

For more information on activating IP-based Iu-PS, see Activating IP based Iu-PS in Activating RAN75 and RAN750: IP based Iu-CS and IP based Iu-PS.

Fill in and check the core network related data, that is, SS7 signaling parameters and the identification parameter of the core network element. Also fill in all RANAP-related parameters. For more information on parameters, see WCDMA Radio Network Config-uration Parameters.

g If there are cells under this core network that already use the Global PLMNid param-eter, their value cannot be changed.

4 Check the value of the digit analysis tree (ATM transport).You can find this parameter on the General tab of the RNC object.

g Once you have created digit analyses with an MML, do not change the value of digit analysis tree from the GUI.


65

Integrating RNC

Id:0900d805805de883

6.6 Creating local signalling configuration for RNCBefore you startCheck that the network element has all the necessary equipment and software.

g Note the following in relation to the NPC command when using Nodal Function to connect two adjacent RNCs via MGW Rel.4:

Since the signalling links are used for SCCP signalling, the value of both the service existing for STP messages and the service existing for user part of own signalling point parameter must be Y.

ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F;

g In Japan, you must read the subfields of the signalling point code for commands NRP, NSC and NRC in reverse order. This differs from the standard procedure used elsewhere in the world. For example, in Japan, the signalling point code 23–8–115, would be read as 115–8–23.

Steps

1 Create SS7 services

Before you startThe signalling messages coming into the network element can be transmitted to the network element's own user parts, or they can be switched forwards, or both. Depending on the services configured to the network element, some of the signalling messages are unnecessary. Data on service information determines how the signalling messages coming into the network element are received and switched.

Steps

a Check that all necessary services exist (NPI)Check that all needed services exist in the network element by using the NPI command. The services SNM and SNT usually exist automatically in the network element.

The needed services depend on the type and use of the network element. In Radio Network Controller (RNC) or Multimedia Gateway Rel.4 (MGW Rel.4) type of network elements at least the following services are needed:

• SNM — signalling network management messages • SNT — signalling network testing and maintenance messages • SCCP — signalling connection control part • AAL2 — AAL type 2 signalling protocol

b Create the necessary services (NPC)Use the parameters service existing for STP messages and service existing for user part of own signalling point to choose whether the service is active for the STP messages and/or to the user parts of the own sig-nalling point.

Check the process family identifiers from the Site Specific Documents as there can be some exceptions to the values given in the following example commands.

ZNPC:<signalling network>,00,SNM:Y:Y,07F,06D;


Integrating RNC

Id:0900d805805de883

ZNPC:<signalling network>,01,SNT:Y:Y,07F,;

ZNPC:<signalling network>,03,SCCP:Y:Y,208,10F;

ZNPC:<signalling network>,0C,AAL2:Y:Y,452;

2 Create own MTP signalling point (NRP)The own signalling point has to be defined before you can create the other objects of the signalling network. Use the command NRP to create the own MTP signalling point. A network element can be connected to several signalling networks. The NRI command displays all existing signalling points.

There are special network-specific parameters related to the signalling networks, and you can output them using the NMO command. These parameters define, for example, the congestion method used in the signalling network. For more information about the network-specific parameters, see SS7 signalling network parameters.

g The same NRP command is used to create a new signalling network.

ZNRP:<signalling network>,<signalling point code>,<signalling point name>,STP:<ss7 standard>:<number of spc subfields>:<spc subfield lengths>;

3 Create own SCCP signalling point (NFD)Before you start creating the signalling point, check what the Signalling Point Code (SPC) of the system's own signalling point is by using the NRI command.

ZNFD:<signalling network>, <signalling point code>,<signalling point parameter set number>:<subsystem number>,<subsystem name>,<subsystem parameter set number>,[<subsystem status test>]: ::: ;

g The value YES for the subsystem status test parameter is valid only when the parameter WHITE_BOOK_MGMT_USED (12) of the used SCCP signalling point parameter set has value YES (check this with the OCI command).

When an SCCP signalling point and SCCP subsystems are created, a parameter set is attached to them. In most cases the predefined parameter sets are the most suitable, but if the predefined parameter sets do not cover all occurring situations, you can create more parameter sets, modify the relevant parameters and then attach the new parame-ter set to the SCCP signalling point and SCCP subsystem. For more information, see SCCP signalling point parameters and SCCP subsystem parameters.

4 Add local subsystems to the signalling point (NFB), if necessaryZNFB:[<signalling network>],<signalling point codes>:<subsystem number>,<subsystem name>,<subsystem parameter set number>,[<subsystem status test>];

5 Activate local SCCP subsystems (NHC), if necessaryZNHC:<signalling network>, <signalling point codes>: <subsystem>:ACT;

To display the subsystem states, use the NHI or NFJ command.


67

Integrating RNC

Id:0900d805805de883

For more information, see States of SCCP subsystems.


Integrating RNC

Id:0900d805805de8b4

Creating Iu-CS interface (RNC-MGW) for ATM

7 Creating Iu-CS interface (RNC-MGW) for ATM

7.1 Configuring physical interface and synchronisationFor information on configuring physical interfaces and synchronisation, see Section Configuring physical interface and configuring synchronisation inputs and outputs.


69

Integrating RNC

Id:0900d805805de893

7.2 Creating phyTTP and ATM resourcesFor information on creating phyTTP and ATM resources, see Creating phyTTP and Creating ATM resources in RNC.


Integrating RNC

Id:0900d805805de899

7.3 Configuring the RNC For information on configuring the RNC object, see Configuring the RNC object for the first time.

For information on configuring the Iu-CS parameters of RNC, see Configuring Iu-CS parameters of RNC.

For information on configuring the Iu-PS parameters of RNC, see Configuring Iu-PS parameters of RNC.

For information on configuring the Iur parameters of RNC, see Configuring Iur parame-ters of RNC.

For information on configuring the Iu-BC parameters of RNC, see Section Activating service area broadcast in Feature RAN2.0023: Service Area Broadcast.

For information on creating the local signalling configuration for RNC, see Creating local signalling configuration for RNC.


71

Integrating RNC

Id:0900d805805de8ac

7.4 Configuring ATM-based signalling channels

7.4.1 Creating remote MTP configuration

PurposeIn most cases the MTP needs to be configured to the network element. Before config-uring the MTP, the signalling network has to be planned with great care. See SS7 network planning principles.

The SS7 signalling configuration is needed for the following interfaces:

• Iu-CS interface, between MGW and RNC. The configuration is based on ATM or IP (SIGTRAN). For the ATM configuration, see the instructions in this chapter. For information on configuring SS7 signalling over IP (SIGTRAN), see Planning site con-figuration for signalling and Creating M3UA configuration.

• Iur interface, between RNC and RNC; nodal functionality in MGW (see Figure AAL bearer establishment from RNC 1 to RNC 2 for illustration). The configuration is based on ATM or IP (SIGTRAN). For the ATM configuration, see the instructions in this chapter. For information on configuring SS7 signalling over IP (SIGTRAN), see Planning site configuration for signalling and Creating M3UA configuration.

Figure 5 AAL bearer establishment from RNC 1 to RNC 2

• Iu-PS interface, between RNC and SGSN. The configuration is based on ATM or IP (SIGTRAN). For the ATM configuration, see the instructions in this chapter. For information on configuring SS7 signalling over IP (SIGTRAN), see Planning site con-figuration for signalling and Creating M3UA configuration.

Before you startBefore you start to create signalling links, check that the SS7 services and the MTP sig-nalling point have been created. For instructions, see Creating local signalling configu-ration for RNC.

The parameter set related to the signalling link can be used to handle several signalling link timers and functions. If the ready-made parameter packages do not cover all occur-ring situations, you can create more parameter sets, modify the relevant parameters and

MGW 1

RNC 1

MGW 2

RNC 2

Iur

Iu-CS

Iu-CS

MGW 3

Nb Nb

H.248

RANAP

BICC

Iur

MSC

Server

MSC

Server


Integrating RNC

Id:0900d805805de8ac

then attach the new parameter set to the signalling link. It is advisable to find out if there will be such special situations before you start configuring the MTP. See Signalling link parameters. The following are two examples of special situations in which TDM signal-ling links require modifications in the parameter set:

• One of the signalling links goes via satellite, and the level 2 error correction method has to be preventive_cyclic_retransmission instead of the usual basic_method.

• National SS7 specification defines some of the timer values so that they are different from the general recommendations.

Steps

1 Check that the signalling links are distributed evenly between different ICSUsUse the following command to display the existing signalling links.

ZNCI;

It is recommended that you allocate signalling links between all working ICSU units to distribute the load.

2 Create signalling links (NCS)

g Before creating ATM signalling links, check that there are free VCLtps available and that they are correctly configured. For instructions, see Create VCLtps for CBR traffic in Creating ATM resources in RNC.

g Remember to check that the network element is adequately equipped before you start creating signalling links. You can do this with the WFI command.

To create ATM signalling links, give the command:

ZNCS:<signalling link number>:<external interface id number>,<external VPI-VCI>:<unit type>,<unit number>:<parameter set number>;

It is advisable to create the signalling links belonging to the same signalling link set into different signalling units, if this is possible. This way a switchover of the signalling unit does not cause the whole signalling link set to become unreachable.

g The Signalling Link Code (SLC) and the Time Slot (TSL) have to be defined so that they are the same at both ends of the signalling link.

You can number the signalling links within the network element as you wish. The default value for the number is always the next free number.

To interrogate existing signalling links, use the NCI or NEL command.

3 Create SS7 signalling link set (NSC)Create a signalling link set for each destination.

!

It is very important that signalling links belonging to the same linkset are allocated to dif-ferent ICSU units to avoid the whole linkset to become unavailable in an ICSU switcho-ver.


73

Integrating RNC

Id:0900d805805de8ac

A signalling link set consists of one or several links. The signalling links belonging to the signalling link set cannot be activated until the signalling link set is connected to a sig-nalling route set.

You can reserve more links for a link set with the NSC command. You can later add links to a signalling link set with the NSA command.

ZNSC:<signalling network>,<signalling point code>,<signalling link set name>:<signalling link number>,<signalling link code>;

The parameters signalling network and signalling point code define the network element where the signalling link set leads to.

To interrogate the existing signalling link sets, use the NSI or NES command.

4 Create signalling route set to MGW (NRC)When a signalling route set is created, a parameter set is attached to it. The parameter set can be used to handle several MTP3 level functions. If the predefined parameter sets do not cover all occurring situations, you can create more parameter sets, modify the relevant parameters and then attach the new parameter set to the signalling route set. See Signalling route set parameters.

Create a signalling route set for each destination.

You can create all signalling routes that belong to the same route set at the same time with the same command.

ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter set number>,<load sharing status>,<restriction status>:<signaling transfer point network>,<signalling transfer point code>,<signalling transfer point name>,<signalling route priority>;

The parameters signalling transfer point code and signalling transfer point name are used when the created signalling route is indirect, that is, the route goes via signalling transfer point (STP). There is no need to use those two parameters when the RNC is directly connected to the MGW.

g A signalling point cannot be used as an STP unless it is first equipped with a direct signalling route.

For more information about signalling route set priorities, see SS7 network planning principles.

To add signalling routes to an existing signalling route set, use the NRA command.

5 Create signalling route set to MSS via MGW (NRC) Create a signalling route set for each destination.

You can create all signalling routes that belong to the same route set at the same time with the same command. Later you can add signalling routes to a route set with the NRA command.

ZNRC:<signalling network>,<signalling point code>,<signalling point name>,<parameter set number>,<load sharing status>,<restriction status>:<signaling transfer point network>,<signalling transfer point code>,<signalling transfer point name>,<signalling route priority>;


Integrating RNC

Id:0900d805805de8ac

The route goes via MGW which is working as a signalling transfer point (STP) when the created signalling route is indirect.

The parameters signalling transfer point code and signalling transfer point name are the same as the MGW's signalling point code and the name of the MGW.


75

Integrating RNC

Id:0900d805805de89f

7.4.2 Activating MTP configuration

Steps

1 Allow activation of the signalling links (NLA)Use the following command to allow the activation of the previously created signalling links:

ZNLA:<signalling link numbers>;

2 Activate the signalling links (NLC)Use the following command to activate the previously created signalling links:

ZNLC:<signalling link numbers>,ACT;

The signalling links assume either state AV-EX (active) or UA-INS if the activation did not succeed. Activation may fail because links at the remote end are inactive or the transmission link is not working properly.

For more information, see States of signalling links.

g To interrogate the states of signalling links, use the commands NLI or NEL.

3 Allow activation of the signalling routes (NVA)Use the following command to allow the activation of the previously created signalling routes:

ZNVA:<signalling network>,<signalling point code>:<signalling transfer point network>,<signalling transfer point code>;

4 Activate signalling routes (NVC)The following command activates the previously created signalling routes:

ZNVC:<signalling network>,<signalling point code>:<signalling transfer point network>,<signalling transfer point code>:ACT;

g To interrogate the states of signalling routes, use the NVI, NER or NRI commands.

When you are dealing with a direct signalling route, the signalling route set assumes the state AV-EX if the related link set is active; otherwise it assumes the state UA-INS. A signalling route going through an STP can also assume the state UA-INR if the STP has sent a Transfer Prohibited (TFP) message concerning the destination point of the route set. For more information, see States of signalling routes.

Example: Example of activating an MTP configurationIn this example, you change the state of a signalling route which is leading to the signal-ling point 302. The route is defined in the signalling point 301 that is located in the national signalling network NA0.

First, you change the signalling route state to ACTIVATION ALLOWED, and then you can take the signalling route into service.

ZNVA:NA0,302:;

The execution printout can be as follows:


Integrating RNC

Id:0900d805805de89f

ALLOWING ACTIVATION OF SIGNALLING ROUTE DESTINATION: SP ROUTES: SPNET SP CODE H/D NAME NET SP CODE H/D NAME--- ------------------ ----- --- --------------- ----- NA0 0302/00770 MSS2 NA0 0302/00770 MSS2 ACTIVATION ALLOWEDCOMMAND EXECUTED

After this, you use the NVC command to activate the route:

ZNVC:NA0,302::ACT;

The execution printout can be as follows:

CHANGING SIGNALLING ROUTE STATE DESTINATION: SP ROUTES: SP OLD NEWNET SP CODE H/D NAME NET SP CODE H/D NAME STATE STATE PRIO--- ------------------ ----- --- -------------- ------- ------- ------ ---- NA0 0302/00770 MSS2 NA0 0302/00770 MSS2 UA-INU AV-EX 2 COMMAND EXECUTED


77

Integrating RNC

Id:0900d805805c9f5c

7.4.3 Setting MTP level signalling traffic load sharing

PurposeWith MTP level signalling traffic load sharing you can share the signalling traffic between signalling routes and between signalling links belonging to the same link set.

Within a signalling link set, load sharing is implemented so that it automatically covers all links that are in active state.

Load sharing between signalling routes takes effect only after you have allowed load sharing by defining the same priority for all signalling routes and by allowing load sharing in that route set.

Before you startBefore setting the load sharing, plan carefully which kind of load sharing is suitable in the signalling network. For more information, see MTP level signalling network.

See also Modifying MTP level signalling traffic load sharing.

Steps

1 Check signalling route priorities and load sharing status, if needed (NRI)ZNRI:<signalling network>,<signalling point code>;

2 Check MTP load sharing data (NEO)Check which signalling links transmit each of the Signalling Link Selection Field (SLS) values.

You can use this command to separately interrogate the load sharing data concerning either messages generated by the own signalling point or STP signalling traffic.

g ANSI standards recommend different number of bits in SLS code to be used for load sharing than ITU standards do. ANSI standards also give specific instructions on which bit(s) in SLS code to use for STP selection.

ZNEO:;

3 Modify signalling route priority, if needed (NRE)The priority can vary between 0-7, the primary priority being 7.

ZNRE:<signalling network>,<signalling point code>:<signalling transfer point network>,<signalling transfer point code>,<new signalling route priority>;

4 Allow load sharing in the signalling route set, if needed (NRB)If load sharing is not allowed in the signalling route set (output of the NRI command), you have to change the load sharing status.

ZNRB:<signalling network>,<signalling point codes>:LOAD=<load sharing status>;


Integrating RNC

Id:0900d805805de8a6

7.4.4 Creating remote SCCP configuration

PurposeThe SCCP is needed on a network element if the element:

• is used for switching calls • is used for switching IN services • acts as SCCP-level Signalling Transfer Point (STP).

Before you startCheck that the whole network has been carefully planned, that all necessary hardware has been installed on the network element, and that the Message Transfer Part (MTP) has already been configured.

Verify the following items:

• Check that the signalling points have been created on the MTP (the NRI command). • Check which parameter set is used, and whether it is necessary to modify the values

of existing parameter sets to meet the present conditions and requirements (the OCI command).

• Check which subsystems are used. • Check the data on subsystem parameter sets (the OCJ command), and the possible

modifications on them (the OCN command). • Check that the SCCP service has been created on the MTP level (the NPI com-

mand).Before you can create the SCCP to the network element, the SCCP service has to be created. To check that the service has been created, use the NPI command. If there is no SCCP service created on the MTP level, create it with the NPC command (more information in Creating remote MTP configuration).

g The SCCP management subsystem (SCMG) is automatically created when you create the SCCP for the signalling point.

g The subsystems which use the Transaction Capabilities are configured in a similar way, and no further configuration is needed (as the TC is automatically used for suitable subsystems).

Steps

1 Create remote SCCP signalling points and subsystems (NFD)In addition to creating the SCCP signalling point and its subsystems, you need to define the other SCCP signalling points and the subsystems of the other SCCP signalling points of the network, which are involved in SCCP level traffic.

ZNFD:<signalling network>, <signalling point code>, <signalling point parameter set>: <subsystem number>, <subsystem name>, <subsystem parameter set number>,Y;

You can add more subsystems to a signalling point later by using the NFB command. The system may need new subsystems, for example, when new services are installed, software is upgraded or network is expanded.

When you are adding subsystems, you need to know which parameter set you want the subsystems to use or which one has to be used.


79

Integrating RNC

Id:0900d805805de8a6

You can display the existing parameter sets by using the OCJ command. When you want to modify the parameters, use the OCN command, and to create a new parameter set, use the OCA command.

2 Create translation results, if necessary (NAC)The translation result refers to those routes where messages can be transmitted. All the signalling points that are meant to handle SCCP level traffic must be defined at a signal-ling point.

At this stage you have to decide whether the routing is based on global title (GT) or on subsystem number.

ZNAC:NET=<primary network>,DPC=<primary destination point code>,RI=<primary routing indicator>;

If you want to have a back-up system for routes or the network, you can create alterna-tive routes that will then be taken into service if the primary route fails. Also it is possible to use load sharing for up to 16 destinations by giving value YES for parameter <load sharing>.

3 Create global title analysis, if necessary (NBC)Before creating the global title analysis, check the number of the translation result so you can attach the analysis to a certain result. Use the NAI command.

For more information about global title analysis, see SS7 network planning principles.

ZNBC:ITU=<itu-t global title indicator>,LAST=<last global title to be analysed>:TT=<translation type>,NP=<numbering plan>,NAI=<nature of address indicator>:<digits>:<result record index>;

4 Set broadcast status (OBC)It is recommended to add local broadcast status of SCCP subsystem to RNC. The local broadcast status (using the OBC command) informs the subsystems of the own signal-ling point about changes in the subsystems of the remote signalling points.

g When setting the broadcasts, consider carefully what broadcasts are needed. Incor-rect or unnecessary broadcasts can cause problems and/or unnecessary traffic in the signalling network.

Depending on the network element, the subsystems needing the broadcast function are the following:

• RANAP Radio Access Network Application Part • RNSAP Radio Network Subsystem Application Part

Local broadcasts:

ZOBC:<network of affected subsystem>,<signalling point code of affected subsystem>,<affected subsystem number>:<network of local subsystem>,<local subsystem number>:<status>;

'BROADCAST STATUS OF SCCP SIGNALLING POINTS' definitions (using the OBM and OBI commands) are not needed in the RNSAP and RANAP interfaces connected to RNC, because they cause too much unnecessary signalling.


Integrating RNC

Id:0900d805805de8a6

For more information, see SCCP level signalling network.


81

Integrating RNC

Id:0900d805805de8a9

7.4.5 Activating SCCP configuration

Steps

1 Activate remote SCCP signalling points (NGC)ZNGC:<signalling network>, <signalling point codes>:ACT;

You do not have to activate the own SCCP signalling point.

2 Check that the signalling point is active (NFI/NGI)ZNFI;

OR

ZNGI;

Notice that if you use the default values in this command, only the signalling points of network NA0 are shown. For more information, see States of SCCP signalling points.

Expected outcomeIn the command printout, the state of signalling point should be AV-EX.

Unexpected outcomeIf the signalling point assumes state UA-INS, there is a fault on the MTP level.

Example: When you examine an example system using the NFI or NGI commands, all signalling points should be in normal state AV-EX. Note that the signalling point 101H cannot be seen because the SCCP is not defined in it.

For command ZNGI:NA0,:N; the execution printout can be as follows:

SCCP STATES

DESTINATION: SP ROUTING: SP NET SP CODE H/D NAME STATE RM NET SP CODE H/D NAME STATE --- ------------------ ----- ----- -- --- ------------------ ----- ------- NA0 0102/00258 PSTN2 AV - NA0 0102/00258 PSTN2 AV-EX NA0 0301/00769 RNC1 OWN SP NA0 0302/00770 MSS2 AV - NA0 0302/00770 MSS2 AV-EX

NA0 0311/00785 RNC1 AV - NA0 0311/00785 RNC1 AV-EX

NA0 0312/00786 BSC2 AV - NA0 0312/00786 BSC2 AV-EX

COMMAND EXECUTED

3 Activate remote SCCP subsystems (NHC)ZNHC:<signalling network>, <signalling point codes>: <subsystem>:ACT;

To display the subsystem states, use the NHI or NFJ command.


Integrating RNC

Id:0900d805805de8a9

When remote subsystems are being activated, their status is not checked from the remote node. The remote subsystem status becomes AV-EX if the remote node is avail-able, although the actual subsystem may be unavailable or even missing. The status of the unavailable subsystem will be corrected with the response method as soon as a message is sent to it.

Use the NHI command to check that the subsystems have assumed state AV-EX. If not, the reason may be faulty or missing distribution data. Correct the distribution data and check the state again. Another reason for the subsystems not to be operating is that the subsystem at the remote end is out of service.

For more information, see States of SCCP subsystems.

4 Set the SS7 network statistics, if neededBy setting the SS7 network statistics, you can monitor the performance of the SS7 network. You do not have to do it in the integration phase; you can do it later.


83

Integrating RNC

Id:0900d805805de8ae

7.5 Creating routing objects and digit analysis for Iu interface in RNCPurposeThis procedure describes how to create routing objects for the Iu interface with MML commands. The associated signalling used is broadband MTP3 signalling. The routing objects must be created at both ends of the Iu interface between two network elements before any user plane connections can be built between them. The analysis tree for con-figuring the Iu interface is set by using the RNC RNW Object Browser application.

g When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 49, add digits 4 and 9.

Before you startBefore you create routing objects, make sure that the appropriate signalling (broadband MTP3) has been created and the associated VC link termination points (VCLtps) for the endpoints have been created. Furthermore, the route under which the endpoints are to be created must allow these type of the endpoints.

Steps

1 Create an AAL type 2 route (RRC)ZRRC:ROU=<route number>,TYPE=<route type>: PRO=<protocol>:NET=<signalling network>,SPC=<signalling point code>,ANI=<aal2 node identifier>;

The ANI must be identical for all routes with the same SPC and the same signalling network.

2 Check that there is a free VCLtp (LCI)ZLCI:<interface id>,VC:<VPI>:FREE;

Of these VCIs, all those with the service category CBR in both directions can be used in the next step.

3 Create an endpoint (LJC)ZLJC:<route number>,<connection id>:<interface id>,<VPI>,<VCI>:(LOCAL | PEER):[<loss ratio>, <mux delay>]:[<sl interface id>, <sl VPI>, <sl VCI>]:[(IFC=)<IFC Profile ID>];

Repeat steps 1-3 in the RNC before continuing with step 4.

g You must create a corresponding routing structure (steps 1-3) in the remote (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER own-ership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection.


Integrating RNC

Id:0900d805805de8ae

4 Unblock the AAL type 2 path (LSU)The endpoints must have been created at both ends of the interface before the AAL type 2 path between them can be unblocked.

ZLSU:<ANI>:<AAL type 2 path identifier>:<execution time>;

Expected outcomeThe execution printout followed by the unblocking should indicate that both the local end and the remote end of the AAL type 2 path are in an unblocked state.

Unexpected outcomeThe AAL type 2 path is still in blocked state. Repeat the unblocking command.

Unexpected outcomeIf the remote end has not agreed unblocking,

Then

verify that the remote end is working properly and that it can be reached. Then repeat the command. As long as the remote end cannot agree to unblocking an AAL type 2 path, the system will not select it.

5 Create digit analysis (RDC)Create a digit analysis for a specific digit sequence. Add an AFI before the digit sequence in order to avoid conflicts with different number formats. Check that the analysis tree has been set for the Iu interface by using the RNC RNW object browser.

ZRDC:DIG=<digits>,TREE=<analysis tree>:ROU=<route number>;

g The address identifies the location of a network termination point. ATM End System Adresses (AESAs) are defined by ATM Forum. AESA consists of Initial Domain Part (IDP) and Domain Specific Part (DSP) and it is always 40 digits long. The IDP spec-ifies an administration authority which has the responsibility for allocating and assigning values of the DSP.

The first two digits of IDP are called Authority and Format Identifier (AFI). The AFI indicates the type of AESA that will follow. The last part of IDP is the actual IDP address. The leading zeroes of AESA numbers are used as padding digits to fill up the address. A trailing F(s) are used to obtain octet (2 digits) alignment or to make the number left justified.

The leading zeroes and trailing F(s) are removed before creating a digit analysis. This is important because, when system analyses received digits a corresponding conversion is made. If digit analyses are created otherwise, the correct, matching analysis result cannot be found.

• E.164 AESAE.164 part of E.164 AESA is the 16 digits after AFI (45). E.164 part may include leading zeroes and/or a trailing F. The rest of the number is DSP part.

• DCC AESADCC part of DCC AESA is 4 digit ISO country code after AFI (39). DCC part may include F(s). The rest of the number is DSP part.


85

Integrating RNC

Id:0900d805805de8ae

• ICD AESA ICD part of ICD AESA is 4 digits after AFI (47). ICD part may include F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken into account when handling analyses:

• E.164 ATM format (AFI = 0 x 45) • Zeros between AFI and the following non-zero digit are removed. • The 16th digit of E.164 part (F digit) is removed. • Example: 45000000358951121F --> 45358951121

• DCC ATM format (AFI = 0 x 39) • The fourth digit (F digit) is removed. • Example: 39123F1234 --> 391231234

• ICD ATM format (0 x 47) • Possible F digits are removed from the ICD part of the number (F digits are

removed from digits 1-4). • Example: 47123F1234 --> 471231234

Further information

☞ When having several long digit analyses leading to the same route, you can benefit from using the wildcard analysis. Instead of listing all the digit analyses separately you can use the default analysis. For example, the following analyses in the same tree mean that all the analyses starting with 4535840 except 45358403452 and 4535840221 are directed to Route B.

45358403452 -> route A

4535840221 -> route A

4535840% -> route B

A default analysis is created automatically, when you enter a shorter or a longer analysis that has the same starting digits as an existing analysis in the same tree.

Example: Create routing objects for Iu interface

1. Create an AAL type 2 route. The route number is 13, the protocol is Message Transfer Part Level 3, the signalling network is NA0, the signalling point code is 24, and the AAL type 2 node identifier is AAL2HEL1.ZRRC:ROU=13,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=24,ANI=AAL2HEL1;

2. Check that there is a free VCLtp under the VPLtp(s).ZLCI:5,VC:<VPI>:FREE;Note that you can check all the available VPIs. Out of these VCIs all those with service category CBR in both directions can be used in the next step.

3. Create a VCC endpoint (VCCep) under the route 13 created in the first step. The AAL type 2 path is 11. The interface ID is 5, VPI 12, and VCI 1045. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10–3 and the AAL type 2 multiplexing delay is 10 ms.ZLJC:13,11:5,12,1045:LOCAL:3,100:;

g You must create a corresponding routing structure (steps 1-3) in the remote (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the con-nection; if this end of the connection has LOCAL ownership value, the other end


Integrating RNC

Id:0900d805805de8ae

must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection.

4. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and the allowed waiting time for the execution of the blocking command is 18 seconds.ZLSU:AAL2HEL1:11:18;

5. Create digit analysis without charging for a digit sequence 491234 in analysis tree 25.ZRDC:DIG=491234,TREE=25:ROU=13;


87

Integrating RNC

Id:0900d805805de8b1

7.6 Creating routing objects and digit analysis with subdesti-nations and routing policy for Iu interfacePurposeThere are two different approaches in creating digit analysis for the Iu interface:

• creating (basic) digit analysis, where each destination has only one subdestination • creating digit analysis, where each destination can have more than one subdestina-

tion.

Creating subdestinations for a destination and defining routing policy (the latter approach above) are optional features. In general, creating basic digit analysis is suffi-cient, and it is recommended that the latter approach be used only if there is a definite need (for example, alternative routing) for several subdestinations and routing policy measures. The routing policy function allows you to utilise alternative routing and per-centage call distribution (also known as load sharing). With alternative routing, another subdestination can be used if connection to primary direction is broken or the subdes-tination selected before is congested. With percentage call distribution, traffic to a des-tination can be distributed among two or more subdestinations in predefined proportions.

g The system can use alternative routing only if you have purchased this feature.

The following figure illustrates the alternative routing and the percentage call distribution between RNC and MGW:


Integrating RNC

Id:0900d805805de8b1

Figure 6 Alternative and percentage routing between RNC and MGW

Before you startBefore you create routing objects, make sure that the appropriate (broadband MTP3) signalling has been created and the associated VC link termination points (VCLtps) for the endpoints have been created.

You can print the analysis and the components by using the commands of the RI command group.

g If the RNC owns the AAL type 2 path, it starts the AAL2 channel identifier (CID) reservation from 8. If the MGW owns the AAL type 2 path, the RNC starts the reser-vation from 255.

Steps

1 Create an AAL type 2 route (RRC)ZRRC:ROU=<route number>,TYPE=AAL2:PRO=MTP3:NET=<signalling network>,SPC=<signalling point code>,ANI=<AAL2 node identifier>;

RNC

Oulu

MGW / ATM Switch

Gothenburg

MGW / ATM Switch

Helsinki1

MGW / ATM Switch

Hamburg

MGW

London

Address =

4535840114

Digit analysis

Destination

London

Route 11 Route 2 Route 3

SecondaryPrimary

TREE 55, DIGITS 4535840114

50 % 50 %

Route 2

Route 11

Route 3

SubdestinationGothenburg

SubdestinationHamburg

SubdestinationHelsinki1


89

Integrating RNC

Id:0900d805805de8b1


All those VCIs with service category CBR in both directions can be used in the next step.


g You must create a corresponding routing structure (steps 1-3) in the MGW (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if one end of the connection has LOCAL ownership value, the other end must have PEER own-ership value and vice versa. The AAL type 2 path identifier must have the same value at both ends of a certain connection.

4 Unblock the AAL type 2 path (LSU)Unblock the AAL type 2 path in both RNC and MGW.


Expected outcomeThe execution printout should indicate that both the local end and the remote end of the AAL type 2 path are in unblocked state.

Unexpected outcomeThe AAL type 2 path is still in blocked state. Make sure that the configuration of the AAL type 2 path is done correspondingly at the other end of the connection. Then repeat the unblocking command.

5 Create subdestinations (RDE)ZRDE:NSDEST=<name of subdestination>:ROU=<route number>;

g You can attach from 1 to 5 subdestinations to each destination. Repeat the command to create the required number of subdestinations.

6 Create a destination and define an alternative routing for the destination (RDE)ZRDE:NDEST=<name of destination>,ALT=<alternative>:NSDEST=<name of subdestination>;

g Repeat this command separately for all the subdestinations that you want to attach to the same destination (NSDEST).

7 Create digit analysis (RDC)Create a digit analysis for a specific digit sequence. The specific digit sequence is the MGW AAL type 2 Service Endpoint Address of the remote end.


Integrating RNC

Id:0900d805805de8b1

The number of the analysis tree must be the same as the tree number set for the desired Virtual Media Gateway (VMGW) with the JVC command.

g When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 45 add digits 4 and 5.

ZRDC:DIG=<digits>,TREE=<analysis tree>:NDEST=<name of destination>;

8 Define the subdestination selection order and percentage call distribution (RMM)By setting a percentage to an alternative, you could change the subdestination type to percentage routing. Alternative routing can be chosen by giving 'A' instead of percent-age value.

This sets the subdestination type to alternative routing.

g If you want to use alternative routing for the subdestinations, don't define new sub-destination type and percentages (by RMM). Alternative routing is the default routing policy.

g The sum of all the percentage values entered for subdestinations must be 100.

ZRMM:NDEST=<destination name>:SELO=<selection order>,CHECK=<check associated analyses>:SPERC0=<percentage value of subdestination 0>,SPERC1=<percentage value of subdestination 1>,SPERC2=<percentage value of subdestination 2>,SPERC3=<percentage value of subdestination 3>,SPERC4=<percentage value of subdestination 4>;

Example: Create routing objects and digit analysis for Iu interface with percent-age routingIn the following example routing objects and digit analysis with several subdestinations are created. The example also describes how traffic flow over several subdestinations can be manipulated with percentage routing and alternative routing.

1. Create an AAL type 2 route between RNC and MGW. The route number is 11, the protocol is Message Transfer part 3, the signalling network is NA0, the signalling point code is 701, and the identifier of the AAL type 2 destination node is AAL2MGW1.ZRRC:ROU=11,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=701,ANI=AAL2MGW1;

2. Check that there is a free VCLtp.ZLCI:<interface id>,VC:<VPI>:FREE;Note that you can check all the VPIs available. All the VCIs with service category CBR in both directions can be used in the next step.

3. Create an endpoint of VC level (VCCep) under route 11 created in the first step. AAL type 2 path is 5. It is based on the TPI with interface id 2, VPI 1, and VCI 33. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10–

3 and the AAL type 2 multiplexing delay is 10 ms.ZLJC:11,5:2,1,33:LOCAL:3,100:;

g You must create a corresponding routing structure (steps 1-3) in the MGW (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the con-


91

Integrating RNC

Id:0900d805805de8b1

nection; if one end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value at both ends of a certain connection.

4. Unblock the AAL type 2 path 5 in RNC. The ANI is AAL2MGW1 and the allowed waiting time for the execution of the blocking commands is 18 seconds.ZLSU:AAL2MGW1:5:18;g You must also unblock the AAL type 2 path in the MGW.

5. Create three subdestinations, 'HELSINKI1', 'GOTHENBURG' and 'HAMBURG' leading to outside routes:ZRDE:NSDEST=HELSINKI1:ROU=11;ZRDE:NSDEST=GOTHENBURG:ROU=2;ZRDE:NSDEST=HAMBURG:ROU=3;g In this example, it is assumed that routes 2 and 3 have been created separately

by following steps 1 to 4 above.6. Create the destination LONDON, define three subdestinations for it and define

HELSINKI1 as the primary routing subdestination, GOTHENBURG as the first alter-native and HAMBURG as the second alternative:ZRDE:NDEST=LONDON,ALT=0:NSDEST=HELSINKI1;ZRDE:NDEST=LONDON,ALT=1:NSDEST=GOTHENBURG;ZRDE:NDEST=LONDON,ALT=2:NSDEST=HAMBURG;

7. Create digit analysis for the digit sequence 4535840114 in analysis tree 55.ZRDC:DIG=4535840114,TREE=55:NDEST=LONDON;

8. Create the subdestination selection order and percentage call distibution.Define the selection order and percentage call distribution values of routing alterna-tives so that the primary subdestination uses alternative routing and the first and the second alternatives use percentage routing. The overflow traffic of the primary alter-native is shared out between the first and the second alternatives:ZRMM:NDEST=LONDON:SELO=A-P,CHECK=Y:SPERC0=A,SPERC1=50,SPERC2=50;

Once you have created subdestinations and defined percentage call distribution or alter-native routing for these, you can modify these settings with the RMM command.


Integrating RNC

Id:0900d805805de8c0

Creating Iu-CS interface (RNC-MGW) for IP

8 Creating Iu-CS interface (RNC-MGW) for IP

8.1 Planning site configuration for signallingThis procedure lists the issues you need to consider when planning the site configura-tion for signalling over IP solutions, that is, IP over ATM and IP over Ethernet. It may not be necessary to do the steps in the order they are presented here.

It is recommended that the same DiffServ is used for all SCTP associations in the asso-ciation set in the M3UA. The settings of the DiffServ code used for M3UA signalling are common to all those applications whose traffic goes via the same SCTP association.

The M3UA implementation supports the DSCP feature. The application reads a param-eter from the file (PRFILE) that tells the DiffServ codepoint used for signalling. The parameter will be common to all signalling applications in the network element. The parameter is called DSCP_FOR_SIGNALLING, the range is from 0H to 0FFH with 0H as default.

The maximum delay that is allowed between the network elements is not specified. See Q706 ITU-T recommendation for reference. An application of the M3UA sets real limits. The M3UA does not contain for example signalling link switchover within a signalling link set, and therefore it cannot achieve the same service level as MTP3 in message trans-port. Packet loss may happen in the M3UA as on MTP level 3.

In IP over Ethernet case, the LAN infrastructure, such as the point-to-point capacity of the LAN, should be known when planning the site configuration. Modifiable SCTP parameters are necessary for the associations to function according to the Q706 ITU-T recommendation.

You can plan the redundancy either by using SCTP multi-homing or by using 2N redun-dant NPGEP units. Redundancy of associations can be handled on several levels:

• on the network element level: If signalling units are configured with logical IP addresses (which is highly recommended), it is possible to do a signalling unit swi-tchover procedure so that the current M3UA configuration is recovered.

• on the unit level.

Before you startIf IP over ATM solution is used, configure ATM resources for it. See Creating ATM resources in RNC.

g In addition to the MML based configuration the IP over ATM connection can be con-figured via the IP plan interface from the NetAct. The IP plan support covers the basic support for the MML commands QMF, QRN and QKC and does not contain the OSPF configuration. For further details, refer to document WCDMA RAN Mass Operations.

Take the following points into consideration when planning site configuration for signal-ling:

1. Use logical IP addresses.This enables making a unit switchover so that IP addresses remain the same.

2. Use logical static IP routes.This helps to make a static IP route configuration and ensure that after the unit swi-tchover, signalling connection works as before the unit switchover.


93

Integrating RNC Creating Iu-CS interface (RNC-MGW) for IP

Id:0900d805805de8c0

g SCTP multi-homing configuration is required to configure two IP sub-networks to each signalling unit. For this reason, the number of IP routes increases rapidly in each peer. Good IP addressing and good IP network design are key issues to avoid such a situation.

3. Use multi-homed connections for signalling over IP, if possible.In this case, IFGE0 and IFGE1 (for IP over Ethernet) or AA0 and AA1 (for IPoA) should belong to different sub-networks. This kind of configuration ensures that the primary path is separated from the secondary path.

4. Point-to-point message travelling time should be explored.If the failure detection time has been planned, it is important to reduce it to the same level as that of the SS7 network by tuning the SCTP parameters.

Steps for planning the site configuration for IP over ATM

1. Plan the IPoA interfaces for SCTP multi-homing.AA0 and AA1 should belong to different sub-networks. SCTP multi-homing enables better redundancy and therefore it is the recommended redundancy mode for sig-nalling. It is recommended to use a symmetric configuration in the case of SCTP multi-homing. For more information on SCTP configurations, see SCTP multi-homing.

2. Tune the SCTP parameters.By tuning the SCTP parameters, a failure detection time of association can be reduced to the same level as that of the SS7 network required. For more information on SCTP parameters, see Modifying SCTP association level parameters.

3. Plan IP addresses management and configuration.Use logical IP addresses.For further information, refer to Configuring IP Connections for RNC.☞ In the following example, two IP over ATM interfaces are created to the same

ICSU. In this way, SCTP multi-homing with two different IP networks can be sup-ported.

Example: Creating two IP over ATM interfaces to the same ICSU1. Configure two IP over ATM interfaces (AA0 and AA1) over the VCLtp created

during configuring ATM resources (QMF)g Signalling unit must be in an active state (that is, in WO-EX state) before

configuration.ZQMF:ICSU,0,L:AA0:2,20,30:1,IPOAM;ZQMF:ICSU,0,L:AA1:2,20,31:1,IPOAM;

2. Assign IP addresses to both ATM interfaces configured in the previous step (QRN)g IP addresses must be assigned from different subnetwork.ZQRN:ICSU,0:AA0:1.2.3.4:32:1.2.3.1;ZQRN:ICSU,0:AA1:2.2.3.4:32:2.2.3.1;

3. Create static routes if needed (QKC)g When the destination address (OYA) associated with signaling point is just

the destination address (QRN) of IPoA connection, it is unnecessary to create static routes.

ZQKC:ICSU,0:10.2.3.0,:1.2.3.1:LOG:;ZQKC:ICSU,0:20.2.3.0,:2.2.3.1:LOG:;


Integrating RNC

Id:0900d805805de8c0

Creating Iu-CS interface (RNC-MGW) for IP

Steps for planning the site configuration for IP over EthernetIf the system is taken into use for the first time, you should create the IP configuration before creating the SCTP association. Creation of logical IP address in the signalling unit changes the unit automatically from SP-EX state to WO-EX state.

☞ One NPGEP unit pair supports 2N redundant Ethernet ports. The used Ethernet ports have the same logical IP address but only one of them is in active state. This is different from the SCTP multi-homing configuration, where both Ethernet ports used have their own IP addresses from different IP subnetworks, so that both Ethernet interfaces are active simultaneously.

1. a) Plan the redundancy using SCTP multi-homing.Ethernet port 0 and Ethernet port 1 should belong to different subnetworks. They can be two different Ethernet ports of one NPGE(P) unit, or two NPGE(P) units. The recommended option is to use two NPGE(P) units. If one NPGE(P) unit is used, two internal IP over ATM connections are needed between the signalling unit and the NPGE(P) unit. Otherwise, one internal IP over ATM connection for each NPGE(P) is needed.SCTP multi-homing enables better redundancy and therefore it is the recommended redundancy mode for signalling. It is recommended to use a symmetric configuration in the case of SCTP multi-homing. For more information on SCTP configurations, see SCTP multi-homing.ORb) Plan the redundancy using 2N redundant NPGEP.2N redundant NPGEP units bring redundancy to all Ethernet traffic and can be used together with SCTP multi-homing. However, using 2N redundant NPGEP units is more important when SCTP multi-homing cannot be used.When configuring a logical IP address, two Ethernet ports with the same name of the NPGEP pair get the same logical IP address. If the Ethernet port (for example, IFGE0) of the working unit fails, the Ethernet port of the spare unit can take the responsibility for the failed one, and the SCTP associations can continue working normally.

2. Tune the SCTP parameters.By tuning the SCTP parameters, a failure detection time of association could be reduced to the same level as that of the SS7 network required. For more information on SCTP parameters, see Modifying SCTP association level parameters

3. Plan IP addresses management and configuration.Logical IP addresses should be used if possible.IP addresses are needed for the Ethernet ports of NPGE(P) and for the internal IP over ATM interfaces of the selected signalling unit and the NPGE(P). The IP address for the internal IP over ATM interface of NPGE(P) is used as a gateway address. The interface type of the internal IP over ATM has to be NUMBERED.

4. Create static IP routes (QKC).Use logical IP route configuration.Configurations are needed both in the signalling unit and in the NPGE(P).

5. Configure the LAN.Configure the lower level LAN.

For further information, refer to Configuring IP Connections for RNC.


95

Integrating RNC Creating Iu-CS interface (RNC-MGW) for IP

Id:0900d805805de8c0

Example: Configuring symmetric SCTP multi-homingThe following example shows how to configure ICSU-0 to connect to SGSN with multi-homing IP over Ethernet connection, going through NPGEP-0 and NPGEP-2.

The existing internal IP over ATM (IPoA) network is used to simplify the configuration.






1. Enable IP forwarding in NPGE(P), which is used for routing the packetsZQRT:NPGEP,0:IPF=YES,;ZQRT:NPGEP,2:IPF=YES,;




5. Assign IP addresses to the internal IPoA interfacesThe interfaces are from the output of step 1. • AA495 <-> IFAI79 of NPGEP-0 • AA496 <-> IFAI79 of NPGEP-2The IP addresses for NPGEP are used also in the internal IPoA interfacesZQRN:ICSU,0:LO0:10.20.1.1;ZQRN:ICSU,0:LO0:10.20.2.1;ZQRN:ICSU,0:AA495,U:10.20.1.1,L::10.20.1.2:;ZQRN:ICSU,0:AA496,U:10.20.2.1,L::10.20.2.2:;ZQRN:NPGEP,0:IFAI79,U:10.20.1.2,L::10.20.1.1;ZQRN:NPGEP,2:IFAI79,U:10.20.2.2,L::10.20.2.1;

6. Configure static routes for ICSUZQKC:ICSU,0:10.2.3.0,24:10.20.1.2,:LOG:;ZQKC:ICSU,0:10.2.4.0,24:10.20.2.2,:LOG:;



Integrating RNC

Id:0900d805805de8b9

8.2 Creating M3UA configurationPurposeRNC supports IP-based Iu and Iur SS7 signalling stack. SS7 over IP signalling link set can be configured in the RNC using either IPoA (IP over ATM) or IP over Ethernet.

Before you startIf IP over ATM solution is used, do the following first before performing this procedure:

• Configure ATM resources. For instructions, see Creating ATM resources in RNC. For information on planning site configuration for IP over ATM, see Planning site configuration for signalling.

• Configure the IP-based signalling transport over ATM connection for RNC control plane. For instructions, see Configuring signalling transport over IP over ATM for control plane.

If IP over Ethernet solution is used, do the following first before performing this proce-dure:

• Create the LAN configuration. For more information, see Planning site configuration for signalling.

• Configure the IP-based signalling transport over Ethernet for RNC control plane. For instructions, see Configuring signalling transport over IP over Ethernet for control plane.

g You should always use the logical IP address of the unit and logical static route con-figuration when possible. Otherwise, there may be problems after unit switchover.

Steps

1. Create own signalling point, if a signalling point does not exist (NRP).ZNRP:<signalling network>,<signalling point code>,<signalling point name>,<own signalling point handling>:<ss7 standard>:<number of spc subfields>:<spc subfield lengths>;

2. Create an association set (OYC).OYC:<association set name>:<role>: [SCTP USER | M3UA def];Remember to check if the association set parameters are correct. For more informa-tion, refer to section Modifying association set level parameters of M3UA.

3. Add associations to the association set (OYA).OYA:<association set name>:<unit type>,<unit index>:<parameter set name>: [stream count | 1 def];

g By default, the number of stream in the M3UA association is 16. It should be noted that if the other peer cannot support as many inbound streams as the client has assigned an outbound stream, then SCTP protocol establishes an association by using lower value of number of stream. This should be taken into account when considering the resources of the client.

4. Configure transport addresses of SCTP association (OYP).OYP:<SCTP association>:<source address 1>, [source address 2], [source port]: <primary destination address>, [netmask/prefix], [secondary destination address], [netmask/prefix]: [destination port];In this phase, define the source and destination port numbers and source and des-tination IP addresses for the SCTP association.


97

Integrating RNC

Id:0900d805805de8b9

5. Check the associations (OYI).OYI:[ [NAME=<association set name> | NBR=<association set number>...] | <all> def]: [A | H | H def];Verify that the associations were created correctly and that they have correct IP addresses by using the OYI command.

6. Create IP type SS7 signalling link and link set (NSP).NSP:<signalling network>, <signalling point code>, <signalling link set name>: <signalling link number>: <association set name>;In this step, create a signalling link set to destination point. A network indicator value and signalling point code address of destination point are defined explicitly where the association set is connected.

7. Create the SS7 signalling route set (NRC).NRC:<signalling network>, <signalling point code>, <signalling point name>, [<parameter set number> | 0 def], [<load sharing status> | D def ], [<restriction status> | N def ]: ( [<signalling transfer point network> | <signalling network> def ], [<signalling transfer point code> | <signalling point code> def ], [<signalling transfer point name> | <signalling point name> def ], <signalling route priority> )... ;

8. Activate the SCTP associations of the association set (OYS).OYS:<SCTP user>:<SCTP association name>:<state>;

9. Activate the signalling network configuration.The activation procedure is the same as when you create a non-IP connection. When you activate an SS7 signalling link, the system automatically attempts to activate all the associations belonging to the association set. The SS7 signalling link is active if at least one association belonging to its association set is active. To inter-rogate the states of the associations, use the OYI command. For more information, see Activating MTP configuration in Configuring Signalling Connections in ATM Network (RNC).

Further informationExample: Creating IP configuration between RNC (client) and MSS (server).

g This is only one example of M3UA usage. The configuration example can be applied to all environments where M3UA is planned to be used.

The SIGU units of the MSS (MSS10) are as follows:

SIGU 0

EL0 131.228.40.10

EL1 131.228.41.10

SIGU 1

EL0 131.228.40.11

EL1 131.228.41.11

The ICSU units of the RNC (RNC400) are as follows:

ICSU 0

AA511 132.228.45.4

AA511 132.228.46.4


Integrating RNC

Id:0900d805805de8b9

ICSU 1

AA511 132.228.45.5

AA511 132.228.46.5

The NPGE units of the RNC (RNC400) are as follows:

NPGE 0

IFGE0 132.228.45.40

IFGE1 132.228.46.40

IFAI0 is connected with AA0 of ICSU-0




IP routes are configured correctly.

Creating M3UA configuration between RNC and MSS for Iu-CS interface

1. Create own signalling point, if a signalling point does not exist.ZNRP:NA0,400,SP400,STP:STAND=ITU-T:3::;

2. Create an association set called TOMSS10.ZOYC:TOMSS10:C;

3. Add two associations to the association set TOMSS10.ZOYA:TOMSS10:ICSU,0,:SS7:;ZOYA:TOMSS10:ICSU,1,:SS7:;

4. Add SCTP transport addresses to the association.ZOYP:M3UA:TOMSS10,0:"132.228.45.4","132.228.46.4": "131.228.40.10",24,"131.228.41.10",24,;ZOYP:M3UA:TOMSS10,1:"132.228.45.5","132.228.46.5": "131.228.40.11",24,"131.228.41.11",24,;

5. Verify the IP addresses in the association set TOMSS10.ZOYI:NAME=TOMSS10:A;

6. Create an SS7 signalling link set to use the association set TOMSS10.ZNSP:NA0,<signalling link set point code>,<signalling link set name>,<signalling link number>,:TOMSS10;

7. Create the SS7 signalling route set with the NRC command.ZNRC:NA0:<signalling point code>,<signalling route set name>:;

8. Activate the SCTP associations.ZOYS:M3UA:TOMSS10,0:ACT;ZOYS:M3UA:TOMSS10,1:ACT;

9. Activate the signalling links.ZNLA:<signalling link number>;ZNLC:<signalling link number>, ACT;

10. Activate the signalling route sets.ZNVA:NA0,<signalling point code>:,;ZNVC:NA0,<signalling point code>:,:ACT;

For MSS configuration, refer to appropriate MSS documentation.


99

Integrating RNC

Id:0900d805805de8bc

8.3 Configuring IP for User PlaneTo configure IP for User Plane, see Configuring IP for User Plane with NPGE/NPGEP.


Integrating RNC

Id:0900d805805de8cb

Creating Iur interface (RNC-RNC) for ATM

9 Creating Iur interface (RNC-RNC) for ATM



101

Integrating RNC

Id:0900d805805de893



Integrating RNC

Id:0900d805805de899








103

Integrating RNC

Id:0900d805805de8c2

9.4 Configuring signalling channelsSee Sections Configuring ATM-based signalling channels, and for IP, see Planning site configuration for signalling and Creating M3UA configuration.


Integrating RNC

Id:0900d805805de8c5

9.5 Creating routing objects and digit analysis for Iur interface in RNCPurposeThis procedure describes how to create routing objects and digit analyses for the Iur interface with MML commands. The analysis tree used for configuring the Iur interface is set by using the RNC RNW object browser application.

g When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 49, add digits 4 and 9.

Before you startBefore you create routing objects, make sure that the appropriate signalling (broadband MTP3) has been created and the associated VC link termination points (VCLtps) for the endpoints have been created. Additionally, the route under which the endpoints are to be created must allow the type of the endpoints.

Steps

1 Create an AAL type 2 route (RRC)ZRRC:ROU=<route number>,TYPE=AAL2:PRO=<protocol>:NET=<signalling network>,SPC=<signalling point code>,ANI=<aal2 node identifier>;

The ANI is to be identical for all routes with the same SPC and the same signalling network.


Out of these VCIs all these with the service category CBR in both directions can be used in the next step.


Repeat steps 1-3 in the remote RNC before continuing with step 4.

g You must create a corresponding routing structure (steps 1-3) in the remote (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if this end of the connection has LOCAL ownership value, the other end must have PEER own-ership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection.


105

Integrating RNC

Id:0900d805805de8c5



Expected outcomeThe execution printout followed by the unblocking should indicate that both the local end and the remote end of the AAL type 2 path are in unblocked state and the state has been agreed with the remote end.

Unexpected outcomeIf the AAL type 2 path is still in blocked state,

Then

repeat the unblocking command

Unexpected outcomeIf the remote end has not agreed to unblocking,

Then

verify that the remote end is working properly and it can be reached. Then repeat the command. As long as the remote end cannot agree to unblocking an AAL type 2 path, the system will not select it.

5 Create digit analysis (RDC)Create a digit analysis without charging for a specific digit sequence. Add an AFI before the digit sequence in order to avoid conflicts with other number formats. The analysis tree has been set for the Iur interface by using the RNC RNW object browser.


g The address identifies the location of a network termination point. ATM End System Adresses (AESAs) are defined by ATM Forum. AESA consists of Initial Domain Part (IDP) and Domain Specific Part (DSP) and it is always 40 digits long. The IDP spec-ifies an administration authority which has the responsibility for allocating and assigning values of the DSP.

The first two digits of IDP are called Authority and Format Identifier (AFI). The AFI indicates the type of AESA that will follow. The last part of IDP is the actual IDP address. The leading zeroes of AESA numbers are used as padding digits to fill up the address. A trailing F(s) are used to obtain octet (2 digits) alignment or to make the number left justified.

The leading zeroes and trailing F(s) are removed before creating a digit analysis. This is important because, when system analyses received digits a corresponding conversion is made. If digit analyses are created otherwise, the correct, matching analysis result cannot be found.

• E.164 AESAE.164 part of E.164 AESA is the 16 digits after AFI (45). E.164 part may include leading zeroes and/or a trailing F. The rest of the number is DSP part.


Integrating RNC

Id:0900d805805de8c5

• DCC AESADCC part of DCC AESA is 4 digit ISO country code after AFI (39). DCC part may include F(s). The rest of the number is DSP part.

• ICD AESA ICD part of ICD AESA is 4 digits after AFI (47). ICD part may include F(s). The rest of the number is DSP part.

The following changes in the format of numbers must be taken into account when handling analyses:

• E.164 ATM format (AFI = 0 x 45) • Zeros between AFI and the following non-zero digit are removed. • The 16th digit of E.164 part (F digit) is removed. • Example: 45000000358951121F --> 45358951121

• DCC ATM format (AFI = 0 x 39) • The fourth digit (F digit) is removed. • Example: 39123F1234 --> 391231234

• ICD ATM format (0 x 47) • Possible F digits are removed from the ICD part of the number (F digits are

removed from digits 1-4). • Example: 47123F1234 --> 471231234

Further information

☞ Transporting Iur and Iu-CS user plane traffic on the same AAL type 2 route is also possible.

In this configuration, steps 1-4 above can be omitted. In step 5 above, separate digit analyses for both Iur and Iu-CS are needed, but those should be attached to the same AAL type 2 route.

☞ When having several long digit analyses leading to the same route, you can benefit from using the wildcard analysis. Instead of listing all the digit analyses separately you can use the default analysis. For example, the following analyses in the same tree mean that all the analyses starting with 4535840 except 45358403452 and 4535840221 are directed to Route B.

45358403452 -> route A

4535840221 -> route A

4535840% -> route B

A default analysis is created automatically, when you enter a shorter or a longer analysis that has the same starting digits as an existing analysis in the same tree.

Example: Create routing objects and digit analysis for Iur interface

1. Create an AAL type 2 route between two RNCs. The route number is 13, the protocol is Message Transfer Part Level 3, the signalling network is NA0, the signalling point code is 35, and AAL type 2 node identifier is AAL2HEL1.ZRRC:ROU=13,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=35,ANI=AAL2HEL1;

2. Check that there is a free VCLtp.ZLCI:5,VC:<VPI>:FREE;Note that you can check all the VPIs available. Out of these VCIs all those with service category CBR in both directions can be used in the next step.


107

Integrating RNC

Id:0900d805805de8c5

3. Create an endpoint of VC level (VCCep) under the route 13 created in the first step. AAL type 2 path is 11. The interface ID is 5, VPI 12, and VCI 1045. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10–3 and the AAL type 2 multiplexing delay is 10 ms.ZLJC:13,11:5,12,1045:LOCAL:3,100:;

g You must create a corresponding routing structure (steps 1-3) in the remote (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the con-nection; if this end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value in both ends of a certain connection.

4. Unblock the AAL type 2 path 11. The ANI is AAL2HEL1 and the allowed waiting time for the execution of the blocking command is 18 seconds.ZLSU:AAL2HEL1:11:18;

5. Create digit analysis without charging for a digit sequence 491234 in analysis tree 24.ZRDC:DIG=491234,TREE=24:ROU=13;


Integrating RNC

Id:0900d805805de8c8

9.6 Creating routing objects and digit analysis with subdesti-nations and routing policy for Iur interfacePurposeThere are two different approaches in creating digit analysis for the Iur interface:

• creating (basic) digit analysis, where each destination has only one subdestination • creating digit analysis, where each destination can have more than one subdestina-

tion.

Creating subdestinations for a destination and defining routing policy (the latter approach above) are optional features. In general, creating basic digit analysis is suffi-cient, and it is recommended that the latter approach be used only if there is a definite need (for example, alternative routing) for several subdestinations and routing policy measures. The routing policy function allows you to utilise alternative routing and per-centage call distribution (also known as load sharing). With alternative routing, another subdestination can be used if connection to primary direction is broken or the subdes-tination selected before is congested. With percentage call distribution, traffic to a des-tination can be distributed among two or more subdestinations in predefined proportions.

g If trying of the selected alternative ends up to congestion, the system can fetch a new alternative from the configured ones providing that you have purchased this feature. This holds both for alternative routing and percentage call distribution.

The following figure illustrates the alternative routing and the percentage call distribution between two RNCs:


109

Integrating RNC

Id:0900d805805de8c8

Figure 7 Alternative and percentage routing between two RNCs

Before you startBefore you create routing objects, make sure that the appropriate (broadband MTP3) signalling has been created and the associated VC link termination points (VCLtps) for the endpoints have been created.

You can print the analysis and the components by using the commands of the RI command group.

g If the RNC owns the AAL type 2 path, it starts the AAL2 channel identifier channel identifier (CID) reservation from 8. Otherwise, it starts the AAL2 channel identifier (CID) reservation from 255. Therefore make sure to set the ownership consistently: one RNC owns the AAL 2 path (OWNERSHIP=LOCAL), the other RNC gets the indicator that its peer is the owner (OWNERSHIP=PEER). With this mechanism you avoid the CID reservation collision.

RNC

Docklands

RNC / ATM Switch

Camden

RNC / ATM Switch

Mayfair1

RNC / ATM Switch

NottingHill

RNC

Soho

Address =

4535840114

Digit analysis

Destination

Soho

Route 11 Route 2 Route 3

SecondaryPrimary

TREE 55, DIGITS 4535840114

50 % 50 %

Route 2

Route 11

Route 3

SubdestinationCamden

SubdestinationNottingHill

SubdestinationMayfair1


Integrating RNC

Id:0900d805805de8c8

Steps

1 Create an AAL type 2 route (RRC)ZRRC:ROU=<route number>,TYPE=AAL2:PRO=MTP3:NET=<signalling network>,SPC=<signalling point code>,ANI=<AAL2 node identifier>;

The ANI is to be identical for all routes with the same SPC and the same signalling network.


All those VCIs with service category CBR in both directions can be used in the next step.


Repeat steps 1-3 in the remote RNC before continuing with step 4.

g You must create a corresponding routing structure (steps 1-3) in the remote (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the connection; if one end of the connection has LOCAL ownership value, the other end must have PEER own-ership value and vice versa. The AAL type 2 path identifier must have the same value at both ends of a certain connection.



Expected outcomeThe execution printout should indicate that both the local end and the remote end of the AAL type 2 path are in unblocked state.

Unexpected outcomeThe AAL type 2 path is still in blocked state. Repeat the unblocking command.

Unexpected outcomeIf the remote end has not agreed unblocking,

Then

Repeat the command if necessary.Verify that the remote end is working properly and that it can be reached. Then repeat the command. As long as the remote end cannot agree to unblocking an AAL type 2 path, the system will not select it.


111

Integrating RNC

Id:0900d805805de8c8

5 Create subdestinations (RDE)ZRDE:NSDEST=<name of subdestination>:ROU=<route number>;

g You can attach from 1 to 5 subdestinations to each destination. Repeat the command to create the required number of subdestinations.

6 Create a destination and define an alternative routing for the destination (RDE)ZRDE:NDEST=<name of destination>,ALT=<alternative>:NSDEST=<name of subdestination>;

g Repeat this command separately for all the subdestinations that you want to attach to the same destination (NSDEST).

7 Create digit analysis (RDC)Create a digit analysis for a specific digit sequence. Add an AFI before the digit sequence in order to avoid conflicts with different number formats.

g When creating digit analysis, you must add an Authority and Format Identifier (AFI) before the digit sequence in order to avoid conflicts with different number formats. AFI indicates the format of AESA number (the first byte of AESA). If, for example, AFI is 45 add digits 4 and 5.


8 Define the subdestination selection order and percentage call distribution (RMM)By setting a percentage to an alternative, you could change the subdestination type to percentage routing. Alternative routing can be chosen by giving 'A' instead of percent-age value.

This sets the subdestination type to alternative routing.

g If you want to use alternative routing for the subdestinations, don't define new sub-destination type and percentages (by RMM). Alternative routing is the default routing policy.

g The sum of all the percentage values entered for subdestinations must be 100.

ZRMM:NDEST=<destination name>:SELO=<selection order>,CHECK=<check associated analyses>:SPERC0=<percentage value of subdestination 0>,SPERC1=<percentage value of subdestination 1>,SPERC2=<percentage value of subdestination 2>,SPERC3=<percentage value of subdestination 3>,SPERC4=<percentage value of subdestination 4>;

Example: Create routing objects and digit analysis for Iur interface with percent-age routingIn the following example routing objects and digit analysis with several subdestinations are created. The example also describes how traffic flow over several subdestinations can be manipulated with percentage routing and alternative routing.


Integrating RNC

Id:0900d805805de8c8

1. Create an AAL type 2 route. The route number is 11, the protocol is Message Transfer part 3, the signalling network is NA0, the signalling point code is 701, and the identifier of the AAL type 2 destination node is AAL2MFR1.ZRRC:ROU=11,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=701,ANI=AAL2MFR1;

2. Check that there is a free VCLtp.ZLCI:<interface id>,VC:<VPI>:FREE;Note that you can check all the VPIs available. All the VCIs with service category CBR in both directions can be used in the next step.

3. Create an endpoint of VC level (VCCep) under route 11 created in the first step. AAL type 2 path is 5. It is based on the TPI with interface id 2, VPI 1, and VCI 33. The current network element owns the AAL type 2 path. The AAL type 2 loss ratio is 10–

3 and the AAL type 2 multiplexing delay is 10 ms.ZLJC:11,5:2,1,33:LOCAL:3,100:;

g You must create a corresponding routing structure (steps 1-3) in the remote (PEER) network element before you can proceed to step 4. The ownership property of a certain AAL type 2 path must be different in both ends of the con-nection; if one end of the connection has LOCAL ownership value, the other end must have PEER ownership value and vice versa. The AAL type 2 path identifier must have the same value at both ends of a certain connection.

4. Unblock the AAL type 2 path 5 in RNC. The ANI is AAL2MFR1 and the allowed waiting time for the execution of the blocking commands is 18 seconds.ZLSU:AAL2MFR1:5:18;

g You must also unblock the AAL type 2 path in the remote RNC.5. Create three subdestinations, 'MAYFAIR1', 'CAMDEN' and 'NOTTINGHILL' leading

to outside routes:ZRDE:NSDEST=MAYFAIR1:ROU=11;ZRDE:NSDEST=CAMDEN:ROU=2;ZRDE:NSDEST=NOTTINGHILL:ROU=3;

g In this example, it is assumed that routes 2 and 3 have been created separately by following steps 1 to 4 above.

6. Create the destination SOHO, define three subdestinations for it and define MAYFAIR1 as the primary routing subdestination, CAMDEN as the first alternative and NOTTINGHILL as the second alternative:ZRDE:NDEST=SOHO,ALT=0:NSDEST=MAYFAIR1;ZRDE:NDEST=SOHO,ALT=1:NSDEST=CAMDEN;ZRDE:NDEST=SOHO,ALT=2:NSDEST=NOTTINGHILL;

7. Create digit analysis for the digit sequence 4535840114 in analysis tree 55.ZRDC:DIG=4535840114,TREE=55:NDEST=SOHO;

8. Create the subdestination selection order and percentage call distribution.Define the selection order and percentage call distribution values of routing alterna-tives so that the primary subdestination uses alternative routing and the first and the second alternatives use percentage routing. The overflow traffic of the primary alter-native is shared out between the first and the second alternatives:ZRMM:NDEST=SOHO:SELO=A-P,CHECK=Y:SPERC0=A,SPERC1=50,SPERC2=50;

Once you have created subdestinations and defined percentage call distribution or alter-native routing for these, you can modify these settings with the RMM command.


113

Integrating RNC Creating Iur interface (RNC-RNC) for IP

Id:0900d805805de8cd

10 Creating Iur interface (RNC-RNC) for IP




Steps









Integrating RNC

Id:0900d805805de8cd

Creating Iur interface (RNC-RNC) for IP













115

Integrating RNC Creating Iur interface (RNC-RNC) for IP

Id:0900d805805de8cd


















Integrating RNC

Id:0900d805805de8cd

Creating Iur interface (RNC-RNC) for IP

















117

Integrating RNC

Id:0900d805805de8b9









Steps







Integrating RNC

Id:0900d805805de8b9









SIGU 0

EL0 131.228.40.10

EL1 131.228.41.10

SIGU 1

EL0 131.228.40.11

EL1 131.228.41.11


ICSU 0

AA511 132.228.45.4

AA511 132.228.46.4


119

Integrating RNC

Id:0900d805805de8b9

ICSU 1

AA511 132.228.45.5

AA511 132.228.46.5


NPGE 0

IFGE0 132.228.45.40

IFGE1 132.228.46.40



















Integrating RNC

Id:0900d805805de8bc



121

Integrating RNC Creating Iu-PS interface (RNC-SGSN) for ATM

Id:0900d805805de8d2

11 Creating Iu-PS interface (RNC-SGSN) for ATM



Integrating RNC

Id:0900d805805de893



123

Integrating RNC

Id:0900d805805de899








Integrating RNC

Id:0900d805805de8c2

11.4 Configuring signalling channelsSee Sections Configuring ATM-based signalling channels, and for IP, see Planning site configuration for signalling and Creating M3UA configuration.


125

Integrating RNC

Id:0900d80580621e9c

11.5 Configuring IP for Iu-PS user plane with NPS1(P)PurposeThe NPS1(P) unit can be used for IP over ATM (IPoA) connections between two network elements such as RNC and SGSN.

Before you startCheck that the LAN cables are correctly attached to the NPS1(P) unit. For more infor-mation, see Cable Lists in Site documentation.

Steps

1 Interrogate external IP over ATM interfaces (QMI)ZQMI:[<unit type>],[<unit index>],[<logical connection type>]:[<IP interface>]:[<ATM interface>],[<VPI>],[<VCI>]:[<encapsulation method>]:[<state>];

2 Create external IP over ATM interfaces (QMF)ZQMF:<unit type>,[<unit index>],<logical connection type>:<IP interface>:<ATM interface>,<VPI number>,<VCI number>:[<encapsulation method>], [<usage | IPCONN def>];

3 Assign IP addresses to ATM interfaces (QRN)ZQRN:<unit type>,[<unit index>]:<interface name>,[<point to point interface type>]:<IP address>,[<IP address type> ]:[<netmask_length>]:[<destination IP address>]:[<MTU>]:[<state>];

g The IP addresses must be assigned from different sub networks.

g NPS1(P) does not support the fragmentation/defragmentation at all. The MTU value must be set big enough in the network interfaces towards NPS1(P) where IP frag-mentation may happen.

4 Assign an IP address to the loopback interface, if necessary (QRN)Details see instructions in Configuring IP parameters and addresses of interfaces.

For IPv4:


5 Configure IP based routeSet up the IP based route identifier list and designate the committed bandwidth as well as committed signalling bandwidth, then configure the IP based route according to the identifier list. For details, refer to WCDMA RAN04 Parameter Dictionary.

The IP based route should be bound to the correct Iu-PS interface with the RNC RNW Object Browser before taking it into use, for details, refer to chapter Configuring Iu-PS parameters of RNC.


Integrating RNC

Id:0900d80580621e9c

ZQRU:<action mode>:<[ip_based_route_id],[ip_based_route_name]>:[ip_based_route_bandwidth]:[committed_bandwidth]:[committed_signal_bandwidth]:[committed_dcn_bandwidth]:OFF;

g If the 'committed_bandwith', 'committed_signal_bandwidth' and 'committed_dcn_bandwidth' are all zero, it means no CAC is done in this IP based route. In the ADD mod, the ip_based_route_name is obligotary, the default values for 'ip_based_route_bandwidth', 'committed_bandwith', 'committed_signal_bandwidth', and 'committed_dcn_bandwidth' are zero. The IP flow control can not be supported on the Iu-PS interface, so the ‘ifc_option’ should be set to OFF. In the MOD mode, the ip_based_route_id is obligatory.

ZQRC:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<IPV4>]=<IP ADDRESS>:<ID/NAME>=<IP BASED ROUTE ID/”IP BASED ROUTE NAME”>;

If an IP based route is attached to more than one IP address, it means load sharing needs to be done for this IP based route.

g The IP based route CAC can not work in load sharing mode.

6 Create Static Routes if needed (QKC)ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>,[<local IP address>]:[<route type>]:[<route preference>];

7 Create OSPF configuration, if necessaryCurrently, OSPF only supports IPv4 and is licence based. If you want to use OSPF routing on the Iu-PS interface, create the configuration as follows:

a) Set the IP address for loopbackZQRN:<unit type>,<unit index>:<interface name>:<IP address>;

b) Configure the OSPF to inform other OSPF routers of the loopback addressZQKU:<unit type>,<unit index>:<redistribute type and identification>:<metric>;

c) Configure the area(s) that include also the neighbouring routersZQKE:<unit type>,<unit index>:<area identification>:<stub area>,[<stub area route cost>],<totally stubby area>;

d) Configure an interface for that areaZQKF:<unit type>,<unit index>:<interface specification>:<area identification>:[<hello interval>]:[<router dead interval>]:[<ospf cost>]:[<election priority>]:[<passive>]: [<authentication> | <authentication>,<password>];

8 Create the user defined DSPM profile (optional)Besides the default mapping profile, you can create the DSCP to PHB mapping profile. For more information, see Configuring DSCP to PHB mapping profile.



127

Integrating RNC

Id:0900d80580621e9c

ZQ8B:<MODE>:[<PROFILE ID>]:[<PROFILE NAME>]:[<DATA TYPE>]:[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>",[<PHB>]="<DSCP>...<DSCP>";

9 Create the user defined PHB profile (optional)You can create the PHB mapping profile. For more information, see Configuring PHB profile.


ZQ8V:<MODE|CR/MO>:<[PROFILE ID]:[PROFILE NAME]>:<PHB VALUE>:[QUEUE WEIGHT],[MIN THRESHOLD],[MAX THRESHOLD],[WRED MAX DROP PROBABILITY],[XPONENTIAL WEIGHT FACTOR],[VLAN PRIORITY];

10 Assign the DSPM and PHB profile for NPS1(P) (optional)See instructions in Configuring and interrogating IP interface QoS parameters.

ZQ8S:<UNIT>,<INDEX>:<IP INTERFACE NAME>:[<ENABLED/DISABLED>]:[<ID1=DSPM PROFILE ID>/<NAME=”DSPM ROFILE NAME”>]:[<ID2=PHB PROFILE ID>/<NAME2=”PHB PROFILE AME”>];

Example: IP configuration for Iu-PS with one IP based route with single NPS1The following example shows how to configure NPS1P to connect to SGSN with IP over ATM connection. One endpoint address is used in SGSN: 10.3.0.1 in GPLC-1.

The ATM AAL5 connection should be configured properly beforehand.

Figure 8 ATM virtual channel connections and IP addresses with NPS1 connected to GPLC unit

1. Create ATM resourcesCreate the following ATM configuration (for instructions, see Creating ATM resources in RNC in ATM Resource Management): • STM-1 ATM interface (with interface ID 1) • In ATM interface 1, one VPLtp with VPI=0 • In ATM interface 1, two VCLtps with VPI=0 and VCI=40

2. Create IP over ATM interfaces to all NPS1ZQMF:NPS1,0,L:IFAE0:1,0,40:1,IPCONN;

3. Assign IP addresses to the network interfacesZQRN:NPS1,0:IFAE0:10.1.1.1,P:32:10.1.1.2;

4. Configure IP based route to NPS1 for different IP NetworksZQRU:ADD:20,"IPROUTE":11000:10000:100:100:OFF;ZQRC:NPS1,0:IFAE0:IPV4=10.1.1.1:ID=20;

10.1.1.1 -> 10.1.1.2IFAE0

VPI=0, VCI=40

STM-1 line #1

NPS1 GPLC110.1.1.2

10.3.0.1


Integrating RNC

Id:0900d80580621e9c

5. Create static routes for NPS1Configure a subnet route to SGSN via IFAE0ZQKC:NPS1,0:10.3.0.1,32:10.1.1.2:PHY;

Example: IP configuration for Iu-PS with multiple IP based routes with single NPS1

Figure 9 ATM virtual channel connections and IP addresses with one NPS1 con-nected to different SGSNs

This example shows how to configure the Iu-PS interface between the RNC and SGSNs using one NPS1 connected to different SGSN. In this example, one endpoint address is used in each SGSN.

• 10.3.0.1 in SGSN1 • 10.3.0.2 in SGSN2

The Iu-PS objects of RNC RNW database corresponding to the PS CN element are con-figured to contain the IP based route id references for the given SGSN destination user plane sub nets.

Iu-PS object for the SGSN1:

Iu-PS - DestIPAddrListPS, 1st entry

• DestIPPrefixPS --> 10.3.0.1/32 • IPBasedRouteIdPS --> 20

Iu-PS object for the SGSN2:

Iu-PS - DestIPAddrListPS, 1st entry

• DestIPPrefixPS --> 10.3.0.2/32 • IPBasedRouteIdPS --> 21

Two IP base routes are configured on two IP addresses to handle the Packet Switched Radio Access Bearers (RAB) originated from different SGSN in the RNC. When the RNC receives the RAB assignment with IP address 10.3.0.1, 10.1.1.1 will be selected as the local IP address. Similarly, when the RAB assignment with IP address 10.3.0.2 is received, 10.1.2.1 will be selected as the local IP address.

1. Create ATM resourcesCreate the following ATM configuration (for instructions, see Creating ATM resources in RNC in ATM Resource Management): • STM-1 ATM interface (with interface ID 1)

IFAE0

NPS1

IFAE1

10.1.1.1 -> 10.2.1.1

10.1.2.1 -> 10.2.1.2

10.2.1.1

10.3.0.1

10.2.1.2

10.3.0.2

VPI=0, VCI=40

VPI=0, VCI=41

STM-1 line #1

STM-1 line #2

SGSN1

SGSN2


129

Integrating RNC

Id:0900d80580621e9c

• In ATM interface 1, one VPLtp with VPI=0 • In ATM interface 1, two VCLtps with VPI=0 and VCI=40 • STM-2 ATM interface (with interface ID 2) • In ATM interface 2, one VPLtp with VPI=0 • In ATM interface 2, two VCLtps with VPI=0 and VCI=41

2. Create IP over ATM interfaces to all NPS1ZQMF:NPS1,0,L:IFAE0:1,0,40:1,IPCONN;ZQMF:NPS1,0,L:IFAE1:2,0,41:1,IPCONN;

3. Assign IP addresses to the network interfacesZQRN:NPS1,0:IFAE0:10.1.1.1,P:32:10.2.1.1;ZQRN:NPS1,0:IFAE1:10.1.2.1,P:32:10.2.1.2;

4. Configure IP based route to NPS1 for different IP NetworksZQRU:ADD:20,"IPROUTE":11000:10000:100:100:OFF;ZQRC:NPS1,0:IFAE0:IPV4=10.1.1.1:ID=20;ZQRU:ADD:21,"IPROUTE":11000:10000:100:100:OFF;ZQRC:NPS1,0:IFAE1:IPV4=10.1.2.1:ID=21;

5. Create the static routes for NPS1Configure the subnet routes to SGSN via IFAE0 and IFAE1ZQKC:NPS1,0:10.3.0.1,32:10.2.1.1:PHY;ZQKC:NPS1,0:10.3.0.2,32:10.2.1.2:PHY;


Integrating RNC

Id:0900d805805de8d4

Creating Iu-PS interface (RNC-SGSN) for IP

12 Creating Iu-PS interface (RNC-SGSN) for IP




Steps









131

Integrating RNC Creating Iu-PS interface (RNC-SGSN) for IP

Id:0900d805805de8d4













Integrating RNC

Id:0900d805805de8d4

Creating Iu-PS interface (RNC-SGSN) for IP


















133

Integrating RNC Creating Iu-PS interface (RNC-SGSN) for IP

Id:0900d805805de8d4

















Integrating RNC

Id:0900d805805de8b9









Steps







135

Integrating RNC

Id:0900d805805de8b9









SIGU 0

EL0 131.228.40.10

EL1 131.228.41.10

SIGU 1

EL0 131.228.40.11

EL1 131.228.41.11


ICSU 0

AA511 132.228.45.4

AA511 132.228.46.4


Integrating RNC

Id:0900d805805de8b9

ICSU 1

AA511 132.228.45.5

AA511 132.228.46.5


NPGE 0

IFGE0 132.228.45.40

IFGE1 132.228.46.40



















137

Integrating RNC

Id:0900d805805de8bc



Integrating RNC

Id:0900d805805de8df

Creating Iub interface (RNC-BTS) for ATM

13 Creating Iub interface (RNC-BTS) for ATM



139

Integrating RNC

Id:0900d805805de893



Integrating RNC

Id:0900d805805de8d6

13.3 Creating radio network connection configuration (ATM, Dual Iub)PurposeA new logical connection configuration object (COCO) is created in order to reserve local transmission resources for WCDMA BTS (WBTS). The COCO object displays the transmission resources in the Iub interface but not the actual network topology.

IPNB (IP Node-B) and COCO objects are alternative to each other, and only one can be used to connect to a certain WBTS.

For information Dual Iub, see RAN1449: Dual Iub for Flexi WCDMA BTS in WCDMA RAN, Rel. RU10, Feature Descriptions.

g It is possible to create a COCO without relating it to a WBTS. In such a case, only the ATM layer is configured.

Before you startThe ATM interface should be created along with an access profile. For information on creating the ATM resources, see Creating ATM resources in RNC.

Steps

1 Start creating connection configuration.

a) Select Object → New → ATM Iub → Iub Connection configuration.b) In the RNW Connection Configuration dialogue, set the following parameters:

• identifier for the COCO (Connection Configuration ID) • ATM interface identifier (Interface ID) • virtual path identifier (VPI)

OrAlternatively, connection configuration can be created using an existing connec-tion configuration as reference.

a) Select the connection configuration whose structure and parameters should be used in the new connection configuration.

b) Select Object → Use as reference.c) In the RNW Connection Configuration dialogue, set an identifier for the new COCO

(Connection configuration id).

2 Fill in parameters for each link category.For more information on connection configuration, see Radio Network Configuration in WCDMA RAN Direct Configuration Operations.

For more information on parameters, see WCDMA Radio Network Configuration Param-eters.


141

Integrating RNC

Id:0900d805805de8d6

3 Click OK in the parameter dialogue to confirm the operation.

Expected outcomeThe data is sent to the RNC RNW database. The data is stored in the RNC RNW database and the ATM layer is created into the system. Control and user plane-related resources are created into the system if the COCO object was related to the WBTS.

4 Check the outcome of the operation and click OK.

Expected outcomeThe COCO object and the corresponding ATM layer configuration is found in the system. If the COCO creation was successful and the WBTS that the user wanted to relate to the COCO was found, the system relates the COCO and the WBTS objects.

The WBTS object does not have to be created before the COCO object is created. Also when the WBTS object is created afterwards, the system relates the objects to each other in the same way that it does if the WBTS already exists when the COCO object is created. Once the COCO and the WBTS have been related in the RNC RNW database, the Control/User plane configuration is done.

Unexpected outcomeAny errors are displayed in the Operation Information dialogue. If the creation fails, continue modifying the COCO or delete the failed COCO and start again with step 1.

Further information

g If the ATM layer is created with MML commands, make sure that the administrative state of the VP/VC Link termination points is unlocked. The usage information of the related ATM termination points should be free. If you use the automatic ATM config-uration option, the termination points are created unlocked by default.

For further information, see Creating ATM resources in RNC and Digit analysis and routing in RNC.


Integrating RNC

Id:0900d805805de8d9

13.4 Creating ATM termination point for IP over ATM connec-tionPurposeA new ATM termination point is created in order to configure ATM layer for IP over ATM (IPoA) connection. Please note that the RNC RNW Object Browser provides online help to assist you in carrying out the tasks. You can access the online help via the Help menu in the main window or by clicking the Help button in the dialogue windows.

These instructions refer to the configuration with the RNC RNW Object Browser GUI. In addition to the GUI-based ATM termination point configuration for the IP over ATM con-nection, the MML interface and the ATM plan interface towards the NetAct can also be used.

Before you start

g With ATM Iub the IP over ATM configuration has to be completed with the commands defined in Creating and modifying internal IP over ATM interfaces and Creating and modifying external IP over ATM interfaces in IP Connection Configu-ration.

If the connection configuration object (COCO) and IPoA have the same VPLtp, the COCO has to be created first. This is to ensure that the underlying VPLtp is created for CBR traffic class.

Steps

1 Select Object → New → ATM Iub → IP over ATM TP.

2 Set the ATM interface identifier, VPI and VCI values.

3 Set the wanted PCR value for defining the desired bandwidth for IPoA connection.

4 Click OK to confirm operation.

Expected outcomeThe progression of the operation is displayed.

Expected outcomeAn ATM layer configured to handle an IP over ATM connection is created in the system. The IPoA link is not, however, working as a result of this.

Unexpected outcomeAny errors are displayed in the Operation Information dialogue. If the creation fails, try again by starting from step 1.


143

Integrating RNC

Id:0900d805805c5b40

13.5 Configuring IP for BTS O&M (RNC-BTS/AXC) via ATMPurposeThe purpose of this procedure is to configure IP for BTS O&M (RNC-BTS/AXC and RNC-FlexiBTS). The alternative ways to configure IP for BTS O&M are detailed below:

• tree topology ATM layer for O&M network to BTS, or • star topology ATM layer for O&M network to BTS.

By using star topology, O&M connections can use the same VPI as control plane traffic. The VPI connection must then be configured as CBR class. This also means that if the O&M VCI is configured to UBR class, it can use the same maximum capacity that is the bit rate for VPI.

You should use the dedicated VPI for O&M traffic in the tree model so that the O&M con-nection can use the free capacity of the link more easily.

g Currently, FlexiBTS does not support ATM cross-connecting. Therefore, a FlexiBTS can be configured only in a star topology or as the last BTS in a tree topology.

For more information on the topologies, see the Nokia Siemens Networks WCDMA RAN System Information Set in NOLS.

You can use either static routing or dynamic routing (OSPF) for BTS O&M. If you use OSPF, you do not need to configure static routes towards the BTSs. When you create the OSPF configuration, the routes are automatically created after the configuration.

With OSPF, you must use unnumbered interfaces towards the BTS, because the AXC only supports unnumbered interfaces. If you have numbered point-to-point interfaces with static routing in use and you want to activate OSPF also to these interfaces, you must modify the interface type. For instructions on how to modify point-to-point inter-faces, see Configuring IP parameters and addresses of interfaces in IP Connection Configuration for RNC.

g Currently, FlexiBTS does not support dynamic (OSPF) routing and numbered IP interfaces. Therefore, only static routing must be used towards a FlexiBTS and the IP interface type must be unnumbered.

Before you startYou can configure O&M network towards BTS via the ATM interfaces on OMU or NPS1(P).


Integrating RNC

Id:0900d805805c5b40

Figure 10 Configuring O&M network towards BTS via the ATM interface on OMU

In the above figure, the external IPoA interface is configured in OMU. NPS1 is used in the same way as NIP1 and NIS1.

Figure 11 Configuring O&M network towards BTS via the ATM interface on NPS1(P)

The above configuration supports to connect to BTS via the two function units (OMU and NPS1(P)) together.

IFFE0 interface's MTU is permanent 1500 and NPS1 unit can not support fragmentation. To support the topology like above figure, you should make sure that the MTU of IPoA interface between NPS1 and BTS is 1500.

You need to create ATM resources for the Iub interface before starting this procedure. When using tree topology, the VPI/VCI termination point with default 0/32 must be created for the O&M connection in OMU or NPS1(P).

When using star topology, you need to create VPI/VCI termination point for O&M con-nection for dedicated BTS in OMU or NPS1(P). Check if the VPI/VCI termination point is already created for the control plane. By default, the same VPI termination point is used as the control plane traffic for BTS. The VPI is configured as CBR class.

O&M

IP over ATM

virtual

connection

RNC

Computer with

Element Manager

OMU

NPS1 ESA24

BTSOMS


145

Integrating RNC

Id:0900d805805c5b40

You also should have ATM plans available for the tree or star model DCN for O&M. For more information, see Creating ATM resources in RNC in ATM Resource Management.

Steps


2 Create an IP over ATM interface towards BTS in OMU or NPS1(P)It is recommended to use unnumbered interfaces towards BTS because point-to-point links do not need IP subnets specified for the link. This also helps in planning and con-figuring the IP network when IP subnets are not used with point-to-point links.

For instructions, see Creating and modifying internal IP over ATM interfaces and Creating and modifying external IP over ATM interfaces.

3 If you are using static routing

Then

Create static route for BTS O&MFor O&M connections towards BTS, configure the route from OMU to the IP address of the gateway that is on the other side of the point-to-point ATM connections (AXC address of BTS site).

ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>,[<local IP address>]:[<route type>]:[<route preference>];

g The parameter local IP address is only valid for local IP address based default routes. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes.

4 If you are using OSPF

Then

Configure OSPF area parameters and interfaces

a) Define the OSPF parameters of an OSPF router.The area identification specifies the area ID for a new OSPF. The area ID is entered as a dotted-quad. The IP network number of a subnetted network may be used as the area ID. It is recommended that all OSPF areas except the backbone be config-ured as totally stubby areas.ZQKE:<unit type>,<unit index>:<area identification>:<stub area>,[<stub area route cost>],<totally stubby area>;

b) Define the OSPF interface parameters of an OSPF router.The default value for router dead interval parameter in AXC is 120. Because the value must be the same in both AXC and RNC, change the value of the router dead interval parameter to 120 in RNC.ZQKF:<unit type>,<unit index>:<interface specification>:<area identification>:[<hello interval>]:[<router dead interval>]:[<ospf cost>]:[<election


Integrating RNC

Id:0900d805805c5b40

priority>]:[<passive>]:[<authentication> | <authentication>,<password>];

Further information

Example: Configuring IP for BTS O&M using star topology ATM layerThis example presents IP for BTS O&M configuration in RNC when star topology ATM layer and dynamic routing (OSPF) is used.

Figure 12 Example of IP configuration for BTS O&M when star topology and OSPF are used

1. Create IP interfaces towards every BTS in OMU.Assign logical IP addresses to the unnumbered point-to-point network interfaces of the OMU unit, with MTU value 1500. g Unnumbered IP address should be the same as IP address of EL interface. If

you do not know what IP address is in use on EL interface, check the configura-tion first by QRI command, for example:

OMS

RNC

RNC Element

Manager

EL0 10.1.1.2/28 (logical)

AA1 10.1.1.2/32

unnumbered lines

RAN BTS sites

address range

10.1.3.0/29

O&M

backbone

AA2 10.1.1.2/32

OMU

RAN BTS sites

address range

10.1.2.0/29

RNC LAN

10.1.1.0/28

ESA12/ESA24


147

Integrating RNC

Id:0900d805805c5b40

ZQRI:OMU:EL0;ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP;ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP;...ZQRN:OMU:AA31,U:10.1.1.2,L::10.1.32.1:1500:UP;ZQRN:OMU:AA32,U:10.1.1.2,L::10.1.33.1:1500:UP;

2. Create an IP over ATM interface between the IP interface and the ATM termination point.Configure an IP over ATM interface with network interface names AA1...AA32 using the same VPI as control plane traffic, and with VCI 32.ZQMF:OMU,,L:AA1:1,1,32;ZQMF:OMU,,L:AA2:2,2,32;...ZQMF:OMU,,L:AA31:1,31,32;ZQMF:OMU,,L:AA32:2,32,32;

3. Configure OSPF area parameters of an OSPF router for the BTS branch.ZQKE:OMU,0:10.1.2.0:Y,,Y;ZQKE:OMU,1:10.1.2.0:Y,,Y;

4. Configure the OSPF interface parameters of an OSPF router.ZQKF:OMU,0:AA1:10.1.2.0::120;ZQKF:OMU,1:AA1:10.1.2.0::120;ZQKF:OMU,0:AA2:10.1.2.0::120;ZQKF:OMU,1:AA2:10.1.2.0::120;...ZQKF:OMU,0:AA31:10.1.2.0::120;ZQKF:OMU,1:AA31:10.1.2.0::120;ZQKF:OMU,0:AA32:10.1.2.0::120;ZQKF:OMU,1:AA32:10.1.2.0::120;

Example: Configuring IP for BTS O&M using tree topology ATM layerThis example presents IP for BTS O&M configuration in RNC when tree topology ATM layer and static routing are used.

1. Create IP interfaces towards the BTS in OMU.Assign logical IP addresses and destination IP addresses to the unnumbered point-to-point network interfaces of the OMU unit, with MTU value 1500, and accept default values for the rest of the parameters.ZQRN:OMU:AA1,U:10.1.1.2,L::10.1.2.1:1500:UP;ZQRN:OMU:AA2,U:10.1.1.2,L::10.1.3.1:1500:UP;

2. Create an IP over ATM interface between the IP interface and the ATM termination point.Configure a TCP/IP ATM interface with network interface names AA1 (to OMU from ATM interface 1) and AA2 (to OMU from ATM interface 2) using VPI 0 and VCI 32 and accept default values for the rest of the parameters.ZQMF:OMU,,L:AA1:1,0,32;ZQMF:OMU,,L:AA2:2,0,32;

3. Create static routes for the BTS branch.Create static routes for OMU to the IP subnetworks 10.1.2.0/24 and 10.1.3.0/24 via the router with IP addresses 10.1.2.1 and 10.1.3.1.ZQKC:OMU,0:10.1.2.0,24:10.1.2.1,:LOG;ZQKC:OMU,0:10.1.3.0,24:10.1.3.1,:LOG;


Integrating RNC

Id:0900d805805de8e4

Creating Iub interface (RNC-BTS) for IP

14 Creating Iub interface (RNC-BTS) for IP

14.1 Configuring IP resources for Iub control plane (RNC-BTS/AXC)PurposeThe purpose of this procedure is to prepare and configure IP resources for Iub control plane.


Steps


2 Connect RNC to BTS/AXC via NPGE(P)The NPGE(P) unit is used for Ethernet connection to the external IP network. In Iub, only IPv4 is supported for the control plane.

Check that the LAN cables are correctly attached to the NPGE(P) unit. For more infor-mation, see Cable Lists in Site documentation.

a) Interrogate the states of the units in the system (USI)Check that the units for which you are going to create network interfaces are in working state (WO-EX). Enter the name of the unit for the unit type parameter.ZUSI:<unit type>;

b) Assign an IP address to the external Ethernet interface of NPGE(P) (QRN)See instructions in Configuring IP parameters and addresses of interfaces.ZQRN:<unit type>,<unit index>:<interface name>:<IP address>,:<netmask length>:::; g The external IP interface addresses must be configured in different sub-nets.

3 Configure the default static routes for NPGE(P)Create the default static routes from NPGE(P) to the external destination (for example, a router). See instructions in Creating and modifying static routes.

g 2N redundant units (NPGEP) must have logical static routes for IPv4.

You can have several NPGE(P) interfaces to the same destination network. To enable load sharing in the NPGE(P) units, configure default routes through more than one NPGE(P) interfaces.

4 Configure IP based route in NPGE(P)IP based route ID is used by ICSU to select a right NPGE(P), through which signalling traffic is routed. For detailed instructions, refer to chapter IP based route configration.


149

Integrating RNC Creating Iub interface (RNC-BTS) for IP

Id:0900d805805de8e4

5 Configure local IP sub-net for Iub control planeSystem selects ICSU for NBAP links based on load sharing algorithm. So all ICSUs' AAx interfaces used for internal IPoA connections between ICSU and NPGE(P) shall have one IP address from the same IP sub-net configured.

a) Interrogate the states of internal IPoA connections created by the system (QMQ)Check that all ICSUs have internal IPoA connections to all NPGE(P). The range of interface names on ICSU side is from AA450 to AA511. The range of interface name on NPGE(P) side is from IFAI30 to IFAI79. The interface name for the unit is allo-cated by the unit logical address statically.ZQMQ:ICSU;

b) Configure local IP sub-net address for Iub control plane (QMN)ZQMN:1:<IPV4 address>,<netmask length>:;

c) Check the local IP sub-net and IP address configurationThe IP address for all the reserved internal IPoA is configured. The range of the IP address is from the sub-net IP address to the sub-net IP address plus 63. The IP address for the ICSU unit is allocated by the unit logical address statically, while the IP address for the NPGE(P) unit is allocated by unit address dynamically. This means the IP address for the NPGE(P) unit may be changed if the NPGE(P) is changed from WO-EX to SE-NH and then from SE-NH to WO-EX.ZQML;ZQRI:<unit_type>,<unit_index>;

6 Modify local IP sub-net for Iub control planeBefore deleting the local IP sub-net, make sure that there are no NBAP links in the sub-net. The RNW object browser should be used to check these links and all the links should be deleted before the local IP sub-net is deleted. Otherwise, even the sub-net is recreated with the same sub-net address, some links will not recover. In that case, the RNW object browser is used to remove these dead links.


Integrating RNC

Id:0900d805805de8bc



151

Integrating RNC

Id:0900d805805c5b43

14.3 Configuring IP for BTS O&M (RNC-BTS/AXC) via EthernetPurposeThe purpose of this procedure is to configure IP for BTS O&M (RNC-BTS/AXC and RNC-FlexiBTS) via Ethernet.

You can use either static routing or dynamic routing (OSPF) for BTS O&M. If you use OSPF, you do not need to configure static routes towards the BTSs. When you create the OSPF configuration, the routes are automatically created after the configuration.

Figure 13 Configuring IP for BTS O&M (RNC-BTS) via Ethernet, case A

Figure 14 Configuring IP for BTS O&M (RNC-BTS) via Ethernet, case B

g The second connection in case B is used only when there is no ESA24 for the con-nection between OMU and NPGE(P), or NPGE(P) and ESA12 do not match.

O&M

Ethernet

connection

RNC

Computer with

Element Manager

OMU

NPGE ESA24

BTSOMS

O&M

Ethernet

connection

RNC

OMU

NPGE ESA12

BTSOMS

Computer with

Element Manager

Internal IPoA

connection


Integrating RNC

Id:0900d805805c5b43

Steps


2 Create an IP over Ethernet interface towards BTS in NPGE(P)

3 If you are using static routing

Then

Create static route for BTS O&MFor O&M connections towards BTS, normally you can set the site router as the default gateway.

ZQKC:<unit type>,<unit index>:[<destination IP address>],[<netmask length>]:<gateway IP address>,[<local IP address>]:[<route type>]:[<route preference>];

g The parameter local IP address is only valid for local IP address based default routes. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes.

4 If you are using OSPF

Then

Configure OSPF area parameters and interfaces

a) Define the OSPF parameters of an OSPF router.The area identification specifies the area ID for a new OSPF. The area ID is entered as a dotted-quad. The IP network number of a sub-netted network may be used as the area ID. It is recommended that all OSPF areas except the backbone are con-figured as totally stubby areas.ZQKE:<unit type>,<unit index>:<area identification>:<stub area>,[<stub area route cost>],<totally stubby area>;

b) Define the OSPF interface parameters of an OSPF router.ZQKF:<unit type>,<unit index>:<interface specification>:<area identification>:[<hello interval>]:[<router dead interval>]:[<ospf cost>]:[<election priority>]:[<passive>]:[<authentication> | <authentication>,<password>];


153

Integrating RNC Creating Iub interface (RNC-BTS) for dual-Iub

Id:0900d805805de8e6

15 Creating Iub interface (RNC-BTS) for dual-IubPurposeIub interface is created for dual-Iub.

Note that:

• O&M is either native IP or IP over ATM • Control Plane is always over ATM • The following User Plane is always over ATM: Common channels, SRB, RT-DCH • The following User Plane can be either over ATM or over IP: NRT-DCH, HSDPA,

HSUPA

Steps

1 Configure O&M either as IP over ATM (as in ATM-based Iub) or over native IP (as in IP-based Iub) but not both. For more information, see Configuring physical interface and synchronisation, Creating phyTTP and ATM resources, Configuring IP for BTS O&M (RNC-BTS/AXC) (for ATM), and Configuring IP for BTS O&M (RNC-BTS/AXC) via Ethernet (for IP).

2 Configure ATM resources exactly as for Control Plane and User Plane of ATM-based Iub.For more information, see Configuring physical interface and synchronisation, Creating phyTTP and ATM resources, and Creating radio network connection configuration (ATM, Dual Iub).

3 Configure IP resources exactly as for User Plane of IP-based Iub.For more information, see Configuring IP for User Plane with NPGE(P).

4 Configure which User Plane services (of NRT-DCH, NRT&RT HSDPA, NRT&RT HSUPA) use IP and which use ATM.This is configured in RNW configuration BTS object. See Creating a WCDMA BTS site.


Integrating RNC

Id:0900d805805de908

Configuring radio network objects

16 Configuring radio network objects








155

Integrating RNC

Id:0900d805805de8ea

16.2 Creating frequency measurement controlPurposeA new logical frequency measurement control (FMC) object (FMCS, FMCI, FMCG (optional)) is created so that its parameters can be utilised in WCDMA cell definitions.

Steps

1 Select Object → New → Freq. Meas. Control → intra-freq./inter-freq./inter-system.

2 Fill in parameters.For information on parameters, see WCDMA Radio Network Configuration Parameters.


Expected outcomeThe data is sent to the RNC RNW database. An Operation Information dialogue appears indicating the status of the operation and possible errors.

4 Check the outcome of the operation and click OK to close the Operation Informa-tion dialogue.

Expected outcomeA new FMC object is created.

Unexpected outcomeAny errors are displayed in the Operation Information dialogue. If the creation fails, you are asked if you want to return to the creation dialogue to modify the parameters and try again. You can also click Cancel to cancel the operation.


Integrating RNC

Id:0900d805805de8ed

16.3 Creating handover pathPurposeA new logical handover path object (HOPS, HOPI, HOPG (optional)) is created so that its parameters can be utilised in adjacent WCDMA cell definitions.

Steps

1 Select Object → New → Handover Path → intra-freq./inter-freq./inter-system.



Expected outcomeThe data is sent to the RNC RNW database.

An Operation Information dialogue appears indicating the status of the operation and possible errors.


Expected outcomeA new handover path object is created.



157

Integrating RNC

Id:0900d805805de8f0

16.4 Creating a WCDMA BTS sitePurposeA new logical WBTS object is created in order to manage a physical WCDMA BTS (WBTS) site and to increase the system capacity.

Before you startThere are two ways of creating a WCDMA BTS site: one is to use system defaults and the other is to use a reference site. The step-by-step instructions below apply to both kinds of creation procedures.

1. Creating a WCDMA BTS site using system defaults:System defaults refer to a range of predefined values which are used in order to speed up the WBTS creation procedure. You still have to fill in identification informa-tion for the WCDMA BTS and other required parameters for which there are no default values. You are not limited to default values; once a parameter has been given a default value, you can change it if necessary.

2. Creating a WCDMA BTS site using a reference site: • To use a reference WCDMA BTS site to aid you in the creation of a WBTS, click

the Site References button. A dialogue with a list of existing WCDMA BTS sites will appear.

• Select the WCDMA BTS that you want to use from the list.When you use a reference site, all possible parameters are copied from the ref-erence site to the new one. You still have to fill in values for those required parameters which could not be copied from the reference WBTS. You are not limited to the copied values; once a parameter value has been copied from the reference WBTS, you can change it if necessary. When you use a reference WBTS site to set up a new site, the topology of the reference site (WCDMA cells and their parameters) is also copied to the new site as an initial configuration. The new site does not have to have the same number of cells as the reference site, that is, you may add and delete cells as needed.

g The logical objects in the RNC RNW database are hierarchically related to each other, and the hierarchy dictates the order in which it is possible to create new objects. WCEL objects are always created under a certain WBTS object, never inde-pendently. However, you do not have to create all WCEL objects that should belong to a WBTS at once; it is possible to change the configuration at a later stage, for example by adding WCEL objects to a WBTS object.

g A frequency measurement control (FMC) object has to be created in advance, if WCDMA cells are created in the WBTS creation procedure.

Steps

1 Select Object → New → WCDMA BTS.

Expected outcomeA New WBTS Site dialogue appears.

2 If you want to, select a reference WBTS site.


Integrating RNC

Id:0900d805805de8f0


g Identify the transmission resources by giving the desired COCO or IPNB identifica-tion or the ATM interface/VPI/C-NBAP VCI triplet. If a COCO or IPNB object is found in the system, the WBTS is connected to it during the creation procedure. COCO or IPNB object can also be created later on and the reference can also be left empty.

The COCO object is created for the Iub connections with ATM transport or with RAN1449: Dual Iub feature configuration. With full IP based Iub (RAN74 IP Based Iub for Flexi WCDMA BTS or RAN1634 IP Based Iub for UltraSite WCDMA BTS) the IPNB object needs to be created. Either COCO or IPNB can be related to the WBTS.

4 If you want to add a WCDMA cellThen

Click Add WCEL.Fill in parameters. For information on parameters, see WCDMA Radio Network Config-uration Parameters.

g If you add WCDMA cells in a locked state, the WCDMA BTS is not taken into active traffic before the WCDMA cell states are changed to an unlocked state. For more information, see Section Locking and unlocking a WCDMA cell in Modifying Radio Network Managed Objects.

5 If you want to remove a WCDMA cell

Then

Select WCEL from the WBTS Site tree.Click Remove WCEL.



A Site Creation Confirmation dialogue appears.


Expected outcomeThe new WBTS site is created. The WCDMA BTS can be taken into active traffic once it has been successfully connected to the logical COCO object. IPNB is alternative for COCO.

Unexpected outcomeIf you give a reference to a COCO or IPNB object, the reference should only point to a object which is not in use at the time. In other words, no reference to a COCO or IPNB object which is already related to a WBTS will be made.


159

Integrating RNC

Id:0900d805805de8f0

Any errors are displayed in the Operation Information dialogue. The parameter window where the error occurred is displayed, and you can either modify the parameters and try again or cancel the operation.


Integrating RNC

Id:0900d80580612b7d

16.5 Creating a virtual WCDMA BTS sitePurposeA new VBTS object is created in to manage a virtual WCDMA BTS (VBTS) site and to increase the system capacity.

Before you startThe VBTS object can be created only when feature RAN1759: Support for I-HSPA sharing and Iur mobility enhancements has been installed in the RNC. Only one VBTS is allowed under one RNC object.

Steps

1 Select Object → New → VBTS

2 Fill in the parameters.

Further informationFor information on parameters, see WCDMA Radio Network Configuration Parameters.

3 Click OK in the parameter dialog to confirm the operation.

Expected outcomeThe data is sent to the RNC RNW database. An Operation Information dialog appears, indicating the status of the operation and possible errors.

4 Check the outcome of the operation and click OK to close the Operation Informa-tion dialog.

Expected outcomeA new VBTS object is created.

Unexpected outcomeAny errors are displayed in the Operation Information dialog. If the creation fails, you are asked if you want to return to the creation dialog to modify the parameters and try again. You can also click Cancel to cancel the operation.


161

Integrating RNC

Id:0900d805805de8f5

16.6 Creating a WCDMA cellPurposeA new WCDMA cell is created in order to change the configuration of the WCDMA BTS (WBTS) site.

Before you startWCEL objects can only be created under a WBTS. The WCDMA cell remains locked and is not used in active traffic until you have changed its state to unlocked.

Steps

1 Start creating the WCDMA cell.

a) Select a parent WCDMA BTS for the WCDMA cell.b) Select Object → New → WCDMA cell.

OrAlternatively, the WCDMA cell can be created using an existing WCDMA cell as reference.

a) Select the WCDMA cell whose parameters should be used in the new cell.b) Select Object → Use as reference.c) Select the WCDMA BTS to which the WCDMA cell should be created.

2 Fill in parameters.

a) Browse through the parameter tabs and fill in every mandatory parameter.b) Specify FMCS, FMCI and FMCG for real-time, non-real time HSDPA, HSDPA for

AMR multi-services, and HSUPA separately on the HC tab. Note that FMCG can only be defined if the inter-system handover feature is activated, and HSDPA or HSUPA FMCs only if the HSDPA or HSUPA feature has been activated.

For information on parameters, see WCDMA Radio Network Configuration Parameters.


4 Select Yes from Automatic Unlock Confirmation dialogue, if you want to create the cell unlocked.




Expected outcomeA new WCDMA cell is created.


Integrating RNC

Id:0900d805805de8f5



163

Integrating RNC

Id:0900d80580612b7e

16.7 Creating a virtual WCDMA cell objectPurposeA new virtual WCDMA cell (VCEL) is created to change the configuration of the virtual WCDMA BTS (VBTS) site.

Before you startVCEL objects can only be created under a VBTS. Only one VCEL object is allowed under one VBTS.

Steps

1 Select Object → New → VCEL


Further informationFor information on parameters, see WCDMA radio network configuration parameters.

3 Click OK in the parameter dialog to confirm the operation.

Expected outcomeThe data is sent to the RNC RNW database. An Operation Information dialog appears, indicating the status of the operation and possible errors.

4 Check the outcome of the operation and click OK to close the Operation Informa-tion dialog.

Expected outcomeA new VCEL object is created.

Unexpected outcomeAny errors are displayed in the Operation Information dialog. If the creation fails, you are asked if you want to return to the creation dialog to modify the parameters and try again. You can also click Cancel to cancel the operation.


Integrating RNC

Id:0900d805805de8f8

16.8 Creating an internal adjacency for a WCDMA cellPurposeA new logical adjacency object [ADJS/ADJD/ADJI] for WCDMA cell is created to define a new neighbouring cell. Adjacencies for cells controlled by the same RNC are called internal adjacencies.

Before you start

g The ADJG object can only act as an external adjacency.

g The ADJD object can only be configured when RAN1266: Soft Handover Based on Detected Set Reporting feature has been installed.

g There is a limitation in sending neighbour cell information in system information block (SIB) type 11, 11bis, and 12. SIB11, SIB11bis, and SIB12 messages can contain information on a maximum of 96 cells, but the physical size of SIB data (no more than 3552 bits) has capacity only for 47 cells when all optional information elements in SIB11 are in use and 35 cells if HCS is used. HCS is controlled with the useofHCS parameter.

If the system information data exceeds 3552 bits, the scheduling of the system infor-mation blocks fails. The cell is blocked by the system and alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Steps

1 Select a parent WCDMA cell for the adjacent WCDMA cell.

2 Select Object → New → Adjacency → intra-freq./additional intra-freq./inter-freq.

Expected outcomeA New ADJS/ADJD/ADJI dialogue appears.


Steps

a Select the target WCDMA cell from the Available cells list.Target UTRAN cell identity and other target cell related parameters are automati-cally defined. You can also insert Target UTRAN Cell identity of the target cell as well as identification parameters for the RNC manually.

b Specify whether the adjacency should be bidirectional or not.The default value is outgoing. The selected WCDMA cell is acting as source cell in case of adjacencies.

c Specify handover paths for real time, non-real time, HSDPA and HSDPA for AMR multi-services separately.

g HSDPA HOPS for AMR multi-service can be specified only if RAN827: HSDPA with Simultaneous AMR Voice Call feature is activated.


165

Integrating RNC

Id:0900d805805de8f8

d Specify whether the adjacency should be included in the system information messages or not.All adjacent cells are used in measurement control even if the adjacency is not included in the system information.

g Additional intra-frequency adjacencies (ADJDs) cannot be included in the system information messages.

Further informationFor more information on parameters, see WCDMA Radio Network Configuration Param-eters.





Expected outcomeIf you chose to create a bidirectional adjacency, both an outgoing and an incoming adja-cency are created; otherwise only an outgoing adjacency is created.



Integrating RNC

Id:0900d805805de8fe

16.9 Creating an external adjacency for a WCDMA cellPurposeA new logical adjacency object [ADJS/ADJD/ADJI/ADJG (optional)] for WCDMA cell is created to define a new neighbouring cell. External adjacencies refer to adjacency relationships between cells controlled by different RNCs.

Before you start

g The ADJD object can only be configured when RAN1266: Soft Handover Based on Detected Set Reporting feature has been installed.

g There is a limitation in sending neighbour cell information in system information block (SIB) type 11 and 12. SIB11 and SIB12 messages can contain information on a maximum of 96 cells, but the physical size of SIB data (no more than 3552 bits) has capacity only for 47 cells when all used optional information elements in SIB11 are in use and 35 cells if HCS is used.

3GPP R6 introduces System Information Block type 11bis (SIB11bis) which provides extension segment for SIB11. SIB11bis doubles the maximum number of neighbour cells in the SIB from 47/35 to 94/70 cells without/with HCS respectively.

If the system information data exceeds 3552 bits, the scheduling of the system infor-mation blocks fails. The cell is blocked by the system and an alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

Steps

1 Select a parent WCDMA cell for the adjacent WCDMA cell.

2 Select Object → New → Adjacency → intra-freq./additional intra-freq./inter-freq./inter-system.

Expected outcomeA New ADJS/ADJD/ADJI/ADJG (optional) dialogue appears.


Steps

a Insert the Target Cell identity of the target cell as well as identification param-eters for the external RNC manually.

b For external adjacencies, define only the outgoing adjacencies.

c Specify handover paths.

g HSDPA HOPS for AMR multi-service can be specified only if RAN827: HSDPA with Simultaneous AMR Voice Call feature is activated.

d Specify whether the adjacency should be included in the system information messages or not.All adjacent cells are used in measurement control even if the adjacency is not included in the system information.


167

Integrating RNC

Id:0900d805805de8fe

g Additional intra-frequency adjacencies (ADJDs) cannot be included in the system information messages.

Further informationFor more information on parameters, see WCDMA Radio Network Configuration Param-eters.





Expected outcomeAn outgoing adjacency is created.



Integrating RNC

Id:0900d805805de8d6

16.10 Creating radio network connection configuration (ATM, Dual Iub)PurposeA new logical connection configuration object (COCO) is created in order to reserve local transmission resources for WCDMA BTS (WBTS). The COCO object displays the transmission resources in the Iub interface but not the actual network topology.

IPNB (IP Node-B) and COCO objects are alternative to each other, and only one can be used to connect to a certain WBTS.

For information Dual Iub, see RAN1449: Dual Iub for Flexi WCDMA BTS in WCDMA RAN, Rel. RU10, Feature Descriptions.

g It is possible to create a COCO without relating it to a WBTS. In such a case, only the ATM layer is configured.

Before you startThe ATM interface should be created along with an access profile. For information on creating the ATM resources, see Creating ATM resources in RNC.

Steps

1 Start creating connection configuration.

a) Select Object → New → ATM Iub → Iub Connection configuration.b) In the RNW Connection Configuration dialogue, set the following parameters:

• identifier for the COCO (Connection Configuration ID) • ATM interface identifier (Interface ID) • virtual path identifier (VPI)

OrAlternatively, connection configuration can be created using an existing connec-tion configuration as reference.

a) Select the connection configuration whose structure and parameters should be used in the new connection configuration.

b) Select Object → Use as reference.c) In the RNW Connection Configuration dialogue, set an identifier for the new COCO

(Connection configuration id).

2 Fill in parameters for each link category.For more information on connection configuration, see Radio Network Configuration in WCDMA RAN Direct Configuration Operations.

For more information on parameters, see WCDMA Radio Network Configuration Param-eters.


169

Integrating RNC

Id:0900d805805de8d6


Expected outcomeThe data is sent to the RNC RNW database. The data is stored in the RNC RNW database and the ATM layer is created into the system. Control and user plane-related resources are created into the system if the COCO object was related to the WBTS.

4 Check the outcome of the operation and click OK.

Expected outcomeThe COCO object and the corresponding ATM layer configuration is found in the system. If the COCO creation was successful and the WBTS that the user wanted to relate to the COCO was found, the system relates the COCO and the WBTS objects.

The WBTS object does not have to be created before the COCO object is created. Also when the WBTS object is created afterwards, the system relates the objects to each other in the same way that it does if the WBTS already exists when the COCO object is created. Once the COCO and the WBTS have been related in the RNC RNW database, the Control/User plane configuration is done.

Unexpected outcomeAny errors are displayed in the Operation Information dialogue. If the creation fails, continue modifying the COCO or delete the failed COCO and start again with step 1.

Further information

g If the ATM layer is created with MML commands, make sure that the administrative state of the VP/VC Link termination points is unlocked. The usage information of the related ATM termination points should be free. If you use the automatic ATM config-uration option, the termination points are created unlocked by default.

For further information, see Creating ATM resources in RNC and Digit analysis and routing in RNC.


Integrating RNC

Id:0900d805805de905

16.11 Creating IPNB objectPurposeA new IPNB (IP Node-B) object is created.

IPNB and COCO objects are alternative to each other, and only one can be used to connect to a certain WBTS.

Before you startCreate the IPQM object if not created already. For more information, see Creating IPQM object.

Steps

1 Select Object → New → IP Iub → IPNB.


a) Give BTS IP as a Destination Address.b) Give the same IP Based Route ID.c) In the DNBAP list enter '1' for the Comm.Control Port ID, the DSCP and SCTP Port

is automatically calculated.

For information on parameters, see RAN74: IP based Iub for Flexi WCDMA BTS in WCDMA RAN, Rel. RU10, Feature Descriptions and WCDMA Radio Network Configu-ration Parameters.




Unexpected outcomeErrors are displayed in the Operation Information dialogue. If the creation fails, you are asked if you want to return to the creation dialogue to modify the parameters and try again. You can also click Cancel to cancel the operation.


171

Integrating RNC Printing alarms

Id:0900d805805de911

17 Printing alarms

17.1 Printing alarms using LPD protocolBefore you startTo print out the alarms, you must first configure the LPD printers and define their TCP/IP address.

Steps

1 Check that the needed LPD printers have been created (INI)If the desired LPD can be found from the printout, check that the settings are correct. IP address should be set and the functional state should be NORMAL.

If the LPD is not shown in the printout, continue to step 2. If the settings are not correct, continue to step 4. If the settings are correct, continue to step 6.

g Check that the index number of the VPP is the same as the index number of the LPD given when configuring the printers.

It is recommended to direct the alarms to the VPP devices whose index is less than 50.

ZINI;

2 LPD not shown in printoutIf the LPD is not shown in the printout

Then

Create the LPD deviceFor instructions, see Creating a printer.

3 Check that the printer state, the LPD index and the IP address are correct (INI)The field FUNCTIONAL STATE in the printout shows the printer state. The printer state in the execution printout should be NORMAL.

The LPD index number should be the same as the VPP index number.

ZINI;

4 Printer state not NORMALIf the printer state is not NORMAL

Then

Change the printer state to NORMAL (INS)ZINS:<device index>:NORMAL;

5 Settings not correctIf the settings are not correct


Integrating RNC

Id:0900d805805de911

Printing alarms

Then

Modify the printer settings (INM)ZINM:<device index>:;

6 Connect the logical file to the desired I/O device (IIS)After connecting the logical file, the alarms are printed out to the desired I/O device.

To print out all the alarms to the desired I/O device, connect the logical file ALARMS to the I/O device. To print out only a certain kind of alarms to the desired I/O device, connect the suitable logical files to the I/O device. For more information on the logical files used with alarms, see Alarm printing and its management.

If you are directing the alarms to VPP, pay special attention that the VPP index in the command is the same as the LPD index given when configuring the printers.

g To print out the alarms via LPD, it is recommended to direct the alarms to the VPP devices whose index is less than 50.

ZIIS:,:<logical file name>,:DEV=<current object identification>:DEV=<new object identification>;

Example: Printing out the alarms to the desired I/O deviceIn this example, two- and three-star communications alarms are directed to VPP-1. This example assumes that:

• The printers are configured, • The TCP/IP addresses of the printers are configured, and • VPP-99 has been connected to logical file ALACOMM1(IIS).

1. Display the printer state and check that the value of the field FUNCTIONAL STATE in the printout is NORMAL.

2. Check that the TCP/IP address is correct.3. As you want to direct the alarms to VPP-1, check that the index number of LPD is 1.4. Connect ALACOMM1 to the correct alarm output device.

The alarm system writes two- and three-star communications alarms to the logical file ALACOMM1. When giving the command, pay special attention to the correct index number.ZIIS:,:ALACOMM1,:DEV=VPP-99:DEV=VPP-1;


173

Integrating RNC

Id:0900d805805de90e

17.2 Printing alarms via Telnet terminal or Web browserPurposeYou can display the alarms on a Telnet terminal or in a Web browser. This is a conve-nient way to continuously monitor alarms on the computer screen over TCP/IP.

Before you startTo display the alarms on a Telnet terminal or in a Web browser, you need to be familiar with the logical files used with alarms, and their tasks.

Steps

1 Check that the IP address of the computer unit has been defined (QRI)ZQRI;

If the IP connection is not defined, see Creating and modifying IP interfaces.

2 Check that the logical files used in printing out alarms are connected to correct VPP devices (IID)To ensure that all alarms are printed out via a Telnet terminal or a Web browser, check the connection between each of the logical files and the desired VPP device. For more information on logical files, see Alarm printing and its management.

ZIID::<logical file name>,:;

If all the logical files listed above are connected to at least VPP-99, go to step 4.

If the logical files are not connected to VPP-99, VPP-98, VPP-97, VPP-96 or VPP-95, go to step 3.

g If all logical files are connected to VPP-99, one remote session for alarm printing can be established. If the logical files are connected to two VPPs, for example, VPP-99 and VPP-98, two simultaneous sessions for alarm printing can be established.

VPP-99 serves the first connection that is established and VPP-98 serves the second connection and so on.

3 Connect the logical files used in printing out alarms to correct VPP devices (IIS)If you want to print out all the alarms to the same window, connect VPP-99 to every alarm-related logical file.

If you want to print out only certain alarms, for example, two- and three-star alarms, connect the logical files used with these alarms and the correct VPP devices (VPP-99, VPP-98, VPP-97, VPP-96 or VPP-95). Note that a logical file can have a maximum of four targets.

If you want to replace the existing I/O device with a new one, use the parameter IND=<current object index>. If this parameter is not given, the new I/O device is simply added but does not replace the previous I/O device.

ZIIS::<logical file name>::DEV=VPP-<I/O device index>;

ZIIS::<logical file name>:IND=<current object index>:DEV=VPP-<I/O device index>;


Integrating RNC

Id:0900d805805de90e

Note that after connecting the logical files associated with alarms to the correct devices, you do not need to change these connections during the lifetime of the software build. You can print out the alarms as described in step 4.

4 Establish a Telnet or HTTP connection to OMU IP address, port 11111If you are using a Telnet terminal, press the ENTER key once, after you have connected to the correct address and port.

If you are using a Web browser, connect to the correct address and port; no extra key-strokes are needed.

Expected outcomeThe alarms that occur in the network element from that moment on are displayed on the Telnet terminal or on the Web browser.

5 Check the state of corresponding VPP devices (IHI)The connection for alarm printing is established, if the working state of the VPP devices corresponding to the Telnet or HTTP sessions is WO-EX.

The working state of the VPP devices not reserved for any connection is BL-EX.

ZIHI::VPP;

In either of the following cases, alarms will not be printed via Telnet/HTTP:

• The VPP device which you connected is not in the WO-EX state. • The connection for alarm printing is not established, or it is disconnected.

To re-establish the connection for alarm printing via Telnet or HTTP, start a new con-nection to OMU, port 11111 from a Telnet terminal or Web browser.

6 End the session when you are readyYou can stop the printing of alarms via Telnet or HTTP by closing the Telnet terminal or the Web browser.


175

Integrating RNC Related information

Id:

Related informationConfiguring PDH for ATM transport

DescriptionsATM over PDH

PDH supervision

Creating IMA group

DescriptionsIMA, Inverse Multiplexing for ATM

Configuring SDH for ATM transport

DescriptionsATM over SDH

SDH supervision

Creating SDH protection group

DescriptionsATM over SDH

Creating phyTTP for ATM

DescriptionsPhysical layer Trail Termination Point (phyTTP)

Creating and modifying VLAN interfaces

InstructionsModifying IP parameters

Configuring IP parameters and addresses of interfaces

InstructionsModifying IP parameters

Configuring IP for user plane with NPGE(P)

InstructionsIP configuration for Iu-PS interface

Creating local signalling configuration for RNC

InstructionsCreating remote MTP configuration

Creating remote SCCP configuration

Creating remote MTP configuration

InstructionsCreating local signalling configuration for RNC


Integrating RNC

Id:

Related information

Setting MTP level signalling traffic load sharing

Activating MTP configuration

Activating MTP configuration


Setting MTP level signalling traffic load sharing



InstructionsCreating local signalling configuration

Activating SCCP configuration

Activating SCCP configuration

InstructionsCreating local signalling configuration


Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface

InstructionsCreating routing objects and digit analysis for Iu interface in RNC

Creating routing objects and digit analysis for Iur interface in RNC

Creating routing objects and digit analysis for Iur interface in RNC

InstructionsCreating routing objects and digit analysis for Iu interface in RNC

Creating routing objects and digit analysis with subdestinations and routing policy for Iur interface

InstructionsCreating routing objects and digit analysis for Iur interface in RNC

Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface

Configuring IP for Iu-PS user plane with NPS1(P)

InstructionsIP configuration for Iu-PS interface


177

Integrating RNC Related information

Id:

Configuring IP for BTS O&M (RNC-BTS/AXC) via ATM

InstructionsIP connection configuration for RNC

Configuring IP for BTS O&M (RNC-BTS/AXC) via Ethernet

InstructionsIP connection configuration for RNC