Sie sind auf Seite 1von 201

3G Rel.

Nokia Core

User Plane Resource creation in


MGW

For M12 and U2 release SW and HW Exercises


and Solutions

6-108933Issue 1-0 © Nokia Networks Oy 1 (201)


User Plane Resource creation in MGW

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia's customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be reproduced or transmitted in any form or means without
the prior written permission of Nokia. The document has been prepared to be used by
professional and properly trained personnel, and the customer assumes full responsibility
when using it. Nokia welcomes customer comments as part of the process of continuous
development and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia and the customer. However,
Nokia has made all reasonable efforts to ensure that the instructions contained in the
document are adequate and free of material errors and omissions. Nokia will, if necessary,
explain issues which may not be covered by the document.
Nokia's liability for any errors in the document is limited to the documentary correction of
errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING
MONETARY LOSSES), that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according
to the applicable laws.
NOKIA logo is a registered trademark of Nokia Oyj.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright © Nokia Oyj 2003. All rights reserved.

6-108933Issue 1-0 © Nokia Oyj 2 (201)


User Plane Resource creation in MGW

Contents

1 Objectives.............................................................................................6

2 MGW Rel.4 integration overview.........................................................7


2.1 MGW Rel. 4 Integration Overview.....................................................10
2.2 Required integration planning information for MGW Rel. 4................14

3 Creating MGW Rel. 4 configuration parameters..............................16


3.1 Creating local signalling configuration for MGW Rel. 4......................16
3.2 Creating MGW Rel.4 -specific default parameters.............................18
3.3 Defining user plane parameter sets in MGW Rel.4............................21

4 Configuring signalling connections MGW Rel.4 - MSC Server.......24


4.1 Creating IP signalling configuration...................................................24
4.2 Creating remote SCCP configuration.................................................26
4.3 Activating SCCP configuration...........................................................29

5 Creating interconnecting signalling connections (MGW Rel.4 -


MGW Rel.4)............................................................................31
5.1 Creating remote MTP configuration...................................................31
5.2 Activating MTP configuration.............................................................34
5.3 Setting MTP level signalling traffic load sharing.................................36
5.4 Creating remote SCCP configuration.................................................37
5.5 Activating SCCP configuration...........................................................39

6 Creating Nb interface with ATM backbone (MGW Rel.4 - MGW


Rel.4)......................................................................................42
6.1 Overview of creating Nb interface with ATM backbone (MGW Rel.4 -
MGW Rel.4).............................................................................42
6.2 Configuring PDH for ATM transport...................................................44
6.3 Creating IMA group...........................................................................46
6.4 Configuring SDH for ATM transport...................................................47
6.5 Creating SDH protection group..........................................................49
6.6 Creating phyTTP...............................................................................50
6.7 Creating ATM resources for Nb interface..........................................51
6.8 Creating remote MTP configuration...................................................55
6.9 Activating MTP configuration.............................................................58
6.10 Setting MTP level signalling traffic load sharing...............................60
6.11 Creating routing objects and digit analysis for Nb interface in MGW
(ATM AAL2).............................................................................61
6.12 Creating routing objects and digit analysis with subdestinations and
routing policy for Nb interface..................................................63
6.13 Example: Creating Nb interface with ATM backbone using ATM
AAL2 (MGW Rel.4 - MGW Rel.4)............................................67

6-108933Issue 1-0 © Nokia Oyj 3 (201)


User Plane Resource creation in MGW

7 Creating Nb interface with IP backbone (MGW Rel.4 - MGW Rel.4)69


7.1 Overview of creating Nb interface with IP backbone (MGW Rel.4 -
MGW Rel.4).............................................................................69
7.2 Configuring IP for Nb user plane (MGW Rel.4 _ IP backbone)..........73

8 Creating Nb interface with TDM backbone (MGW Rel.4 - MGW


Rel.4)......................................................................................74
8.1 Overview of creating Nb interface with TDM backbone (MGW Rel.4 -
MGW Rel.4).............................................................................74
8.2 Configuring PDH for TDM transport...................................................76
8.3 Creating routing objects for TDM resources controlled by MSC server
................................................................................................78

9 Creating interconnecting TDM connections (MGW Rel.4 - MSC


Server, MGW Rel.4 - CDS).....................................................81
9.1 Overview of creating interconnecting TDM connections in MGW Rel.4
................................................................................................81
9.2 Configuring PDH for TDM transport...................................................82
9.3 Creating routing objects for IWF/CDS-dedicated TDM connections. .84
9.4 Creating routing objects for TDM resources controlled by MSC server
................................................................................................86
9.5 Example: Creating interconnecting TDM connections (MGW Rel.4 -
MSC Server, MGW Rel.4 - CDS).............................................88

10 Configuring IP for interface control connections (MGW Rel.4 -


MSS, MGW Rel.4 - CDS)........................................................90
10.1 Configuring IP for control plane (MGW Rel.4 _ MSC server/CDS). .90
10.2 Configuring H.248 control protocol (MGW Rel.4 -MSC Server).......91
10.3 Configuring IWF/CDS control protocol (MGW Rel.4_ IWF/CDS).....94

11 Creating Iu-CS interface (MGW Rel.4 - RNC)..................................97


11.1 Configuring PDH for ATM transport.................................................97
11.2 Creating IMA group.........................................................................99
11.3 Configuring SDH for ATM transport...............................................101
11.4 Creating SDH protection group......................................................102
11.5 Creating phyTTP...........................................................................103
11.6 Creating ATM resources for Iu_CS interface.................................104
11.7 Creating remote MTP configuration...............................................110
11.8 Creating remote SCCP configuration.............................................114
11.9 Activating SCCP configuration.......................................................117
11.10 Creating routing objects for lu interface in MGW Rel.4................119
11.11 Example: Creating Iu-CS interface (MGW Rel.4 - RNC)..............121
11.12 Creating semi-permanent cross-connections through ATM network
element..................................................................................122

12 Creating A interface (MGW Rel.4 - BSC).......................................124


12.1 Configuring PDH for TDM transport...............................................124

6-108933Issue 1-0 © Nokia Oyj 4 (201)


User Plane Resource creation in MGW

12.2 Creating remote MTP configuration...............................................126


12.3 Activating MTP configuration.........................................................129
12.4 Creating remote SCCP configuration.............................................131
12.5 Activating SCCP configuration.......................................................134
12.6 Creating routing objects for TDM resources controlled by MSC
server....................................................................................135
12.7 Example: Creating A interface (MGW Rel.4 - BSC).......................138

13 Creating PSTN/PLMN interface (MGWRel.4 - PSTN/PLMN).........140


13.1 Configuring PDH for TDM transport...............................................140
13.2 Activating MTP configuration.........................................................145
13.3 Setting MTP level signalling traffic load sharing.............................147
13.4 Creating remote SCCP configuration.............................................148
13.5 Activating SCCP configuration.......................................................151
13.6 Creating routing objects for TDM resources controlled by MSC
server....................................................................................152

14 Configuring ATM AAL2 nodal switching functionality in MGW


Rel.4......................................................................................155
14.1 Overview of configuring ATM AAL2 nodal switching functionality in
MGW Rel.4............................................................................155
14.2 Creating routing objects and digit analysis for AAL2 nodal switching
functionality in MGW..............................................................159
14.3 Creating routing objects and digit analysis with subdestinations and
routing policy for AAL2 nodal switching functionality in MGW161

15 Integrating NEMU...........................................................................166
15.1 Configuring domain name in Orbix configuration in NEMU............166
15.2 Setting log size and overwriting parameters for NEMU logs..........167
15.3 Supervising NEMU software..........................................................167
15.4 Configuring network element system identifier (systemId) to NEMU
..............................................................................................168
15.5 Configuring Nokia NetAct interface with NEMU.............................169

APPENDIX A: Configuring synchronisation inputs.........................171

APPENDIX B: Printing alarms in MGW Rel.4....................................174

APPENDIX C: Configuring site connectivity for MGW Rel.4...........178

References..........................................................................................201

6-108933Issue 1-0 © Nokia Oyj 5 (201)


User Plane Resource creation in MGW

1 Objectives
By the end of this module you should be able to:
• Describe Nb interface
• Describe Mc and NPI interface
• Describe Iu-Cs and A interface
• Describe MGW-PSTN/PLMN interface
• Describe MGW as a cross-connection network element
• Describe how to construct announcement files in MGW

6-108933Issue 1-0 © Nokia Oyj 6 (201)


User Plane Resource creation in MGW

2 MGW Rel.4 integration overview


You 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 standalone entities.
During the integration 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.

Example network
The MGW Rel.4 integration instructions are based on the following Nokia CS
core network solution example based on 3GPP Rel.4:

6-108933Issue 1-0 © Nokia Oyj 7 (201)


User Plane Resource creation in MGW

Figure 1 Nokia CS core network solution based on 3GPP Rel.4

MGW Rel.4 integration involves the following network elements and


interfaces:
MGW Rel.4 Multimedia Gateway Rel.4, whose main task is to convey the
user plane data from the radio access network to the backbone network and vice
versa.
The following interfaces are used to connect two Rel.4 MGWs:
• ATM backbone (Nb)
• IP backbone (Nb)
• TDM backbone (Nb)
MSS MSC Server, whose main task is to process the control plane of a call.
The MSS can be a standalone MSS, which does not have user plane
connections, or it can be an integrated MSS which is a conventional MSC

6-108933Issue 1-0 © Nokia Oyj 8 (201)


User Plane Resource creation in MGW

upgraded with the actual MSC Server functionalities. In the latter case, the A
interface can be also between BSC and MSS.
The following interfaces are used to connect MSC Server and MGW Rel.4:
• interconnecting TDM interface
• H.248 control interface (Mc)
When interworking function (IWF) is integrated into MSC Server, there is an
additional IWF control interface (Nokia proprietary interface/NPI)between
MSC Server and MGW Rel.4. IWF can also be located in a standalone element
called Circuit-switched Data Server (CDS).
GCS Gateway Control Server. It is similar to MSS, but does not contain
VLR and radio network access functionalities. It is used in association with the
calls which are destined to PSTN network. The H.248 control interface (Mc) is
used to connect Gateway Control Server and MGW Rel.4.
CDS Circuit-switched Data Server, whose main task is to provide an
interworking function (IWF) for circuit switched data calls between the mobile
network and PSTN. IWF can also be integrated into MSC Server.
The following interfaces are used to connect CDS and MGW Rel.4:
• interconnecting TDM interface
• IWF control interface (Nokia proprietary interface/NPI)
BSC Base Station Controller, whose main task is to convey SS7/TDM-
based user plane and control plane traffic between the 2G BSS and core
network. BSC is connected either to MGW Rel.4 or to MSC Server depending
on the operator's network architecture. If BSC is connected to MGW Rel.4, the
user plane traffic (speech and data) is always routed via MGW Rel.4 to the
ATM/IP backbone, while the control plane traffic (BSSAP signalling) is routed
either directly to MSC Server or transparently via MGW Rel.4 to MSC Server.
The A interface is used to connect BSC and MGW Rel.4. RNC Radio Network
Controller, whose main task is to convey circuit switched traffic between 3G
RAN and core network. The Iu-CS interface is used to connect RNC and MGW
Rel.4.

Note
In addition to the circuit switched traffic from the Iu-CS interface, it is also
possible to route the Iur traffic via MGW Rel.4. ATM AAL2 Nodal Function
makes it possible to route the Iur traffic between two adjacent RNCs via MGW
Rel.4 without any control from MSC Server.

SGSN GPRS support node, whose main task is to maintain the 3G packet
switching connection towards 3G RAN.

Note

6-108933Issue 1-0 © Nokia Oyj 9 (201)


User Plane Resource creation in MGW

MGW Rel.4 does not have a direct interface towards SGSN, but the Iu-PS
interface (between SGSN and RNC) can be routed through MGW Rel.4. When
routing the Iu-PS interface, the packet-switched traffic is cross-connected on the
ATM layer inside MGW Rel.4 and routed towards SGSN.

NetAct Nokia NetAct is a part of the total Nokia 3G solution. It provides a


remote operation and maintenace connection towards MGW Rel.4. In addition
to MGW Rel.4, the NetAct system can be used to manage both 2G and 3G
Radio Access Networks (RAN) and the common core networks for 2G and 3G.

2.1 MGW Rel. 4 Integration Overview

MGW Rel.4 integration descriptions


• Required integration planning information for MGW Rel.4
• Overview of configuring site connectivity for MGW Rel.4
• Overview of creating Nb interface with ATM backbone (MGW Rel.4 -
MGW Rel.4)
• Overview of creating Nb interface with IP backbone (MGW Rel.4 -
MGW Rel.4)
• Overview of creating Nokia IP Trunk interface in MGW Rel.4
• Overview of creating Nb interface with TDM backbone (MGW Rel.4 -
MGW Rel.4)
• Overview of creating interconnecting TDM connections in MGW Rel.4
• Overview of configuring ATM AAL2 nodal switching functionality in
MGW Rel.4

MGW Rel.4 integration instructions


Configuring site connectivity for MGW Rel.4
• Creating MMI user profiles and user IDs for remote connections to
NetAct
• Configuring IP stack in functional units of MGW Rel.4
• Configuring internal connections for IP-NIU
• Configuring ESA12
• Configuring NEMU for DCN in MGW Rel.4
• Connecting to O&M backbone via Ethernet
• Connecting MGW Rel.4 to external network via ATM virtual
connections

6-108933Issue 1-0 © Nokia Oyj 10 (201)


User Plane Resource creation in MGW

• Connecting MGW Rel.4 to external network via IP-NIU


• Configuring static routes in MGW Rel.4
• Configuring NEMU to MGW Rel.4

Integrating NEMU
• Configuring domain name in Orbix configuration in NEMU
• Setting log size and overwriting parameters for NEMU logs
• Supervising NEMU software
• Configuring network element system identifier (systemId) to NEMU
• Configuring Nokia NetAct interface with NEMU

Defining external time source for network element


Creating MGW Rel.4 configuration parameters
• Creating local signalling configuration for MGW Rel.4
• Creating MGW Rel.4 -specific default parameters
• Defining user plane parameter sets in MGW Rel.4

Configuring signalling connections (MGW Rel.4 – MSC Server)


• Creating IP signalling configuration
• Creating remote SCCP configuration
• Activating SCCP configuration

Creating Nb interface with ATM backbone (MGW Rel.4 - MGW Rel.4)


• Configuring PDH for ATM transport
• Creating IMA group
• Configuring SDH for ATM transport
• Creating SDH protection group
• Creating phyTTP
• Creating ATM resources for Nb interface
• Creating remote MTP configuration
• Activating MTP configuration
• Setting MTP level signalling traffic load sharing
• Creating routing objects and digit analysis for Nb interface in MGW
(ATM AAL2)

6-108933Issue 1-0 © Nokia Oyj 11 (201)


User Plane Resource creation in MGW

• Creating routing objects and digit analysis with subdestinations and


routing policy for Nb interface
• Example: Creating Nb interface with ATM backbone using ATM AAL2
(MGW Rel.4 - MGW Rel.4)

Creating Nb interface with IP backbone (MGW Rel.4 - MGW Rel.4)


• Configuring IP for Nb user plane (MGW Rel.4 _ IP backbone)

Creating Nokia IP Trunk interface (MGW Rel.4 - MSC)


• Configuring IP for IP Trunk user plane (MGW Rel.4 _MSC)

Creating Nb interface with TDM backbone (MGW Rel.4 -MGW Rel.4)


• Configuring PDH for TDM transport
• Creating routing objects for TDM resources controlled by MSC Server

Creating interconnecting TDM connections (MGW Rel.4 - MSC Server, MGW


Rel.4 - CDS)
• Configuring PDH for TDM transport
• Creating routing objects for IWF-dedicated TDM connections
• Creating routing objects for TDM resources controlled by MSC Server
• Example: Creating interconnecting TDM connections (MGW Rel.4 -
MSC Server, MGW Rel.4 - CDS)

Creating Iu-CS interface (MGW Rel.4 - RNC)


• Configuring PDH for ATM transport
• Creating IMA group
• Configuring SDH for ATM transport
• Creating SDH protection group
• Creating phyTTP
• Creating ATM resources for Iu_CS interface
• Creating remote MTP configuration
• Activating MTP configuration
• Creating remote SCCP configuration
• Activating SCCP configuration
• Creating routing objects for lu interface in MGW Rel.4
• Example: Creating Iu-CS interface (MGW Rel.4 - RNC)

6-108933Issue 1-0 © Nokia Oyj 12 (201)


User Plane Resource creation in MGW

Creating A interface (MGW Rel.4 - BSC)


• Configuring PDH for TDM transport
• Creating remote MTP configuration
• Activating MTP configuration
• Creating remote SCCP configuration
• Activating SCCP configuration
• Creating routing objects for TDM resources controlled by MSC Server
• Example: Creating A interface (MGW Rel.4 - BSC)

Creating PSTN/PLMN interface (MGW Rel.4 - PSTN/PLMN)


• Configuring PDH for TDM transport
• Creating remote MTP configuration
• Activating MTP configuration
• Setting MTP level signalling traffic load sharing
• Creating remote SCCP configuration
• Activating SCCP configuration
• Creating routing objects for TDM resources controlled by MSC Server

Configuring IP for interface control connections (MGW Rel.4 - MSC Server,


MGW Rel.4 - CDS)
• Configuring IP for control plane (MGW Rel.4 _ MSC server/CDS)
• Configuring H.248 control protocol (MGW Rel.4 - MSC Server)
• Configuring IWF/CDS control protocol (MGW Rel.4 _IWF/CDS)

Creating interconnecting signalling connections (MGW Rel.4 - MGW Rel.4)


• Creating remote MTP configuration
• Activating MTP configuration
• Setting MTP level signalling traffic load sharing
• Creating remote SCCP configuration
• Activating SCCP configuration

Creating semi-permanent cross-connections through ATM network


element

6-108933Issue 1-0 © Nokia Oyj 13 (201)


User Plane Resource creation in MGW

Configuring ATM AAL2 nodal switching functionality in MGW Rel.4


• Creating routing objects and digit analysis for AAL2 nodal switching
functionality in MGW
• Creating routing objects and digit analysis with subdestinations and
routing policy for AAL2 nodal switching functionality in MGW

Constructing announcement files in MGW Rel.4

Configuring synchronisation inputs

Printing alarms in MGW Rel.4


• Printing alarms using LPD protocol
• Printing alarms via Telnet terminal or Web browser

2.2 Required integration planning information for


MGW Rel. 4
The network planning process delivers all required information for network
element installation, commissioning and integration. Network planning can be
separated into the following phases: transmission & transport, radio network
and installation planning.
The following planning activities must be accomplished before the integration
phase starts:
1. Radio network planning
2. Transport/transmission network planning
(In Nokia terminology transmission is related to the PDH/SDH network and
transport to the ATM/AAL2 network.)
3. IP network planning
4. SS7/SCCP network planning

Note
If SIGTRAN is not used in MGW Rel.4, the SIGTRAN related IP signalling
configuration between MGW Rel.4 and MSC Server does not have to be
created.
5. DCN network planning
6. E.164 public network addressing planning (AAL2)
7. H.248 (Mc) interface usage planning

6-108933Issue 1-0 © Nokia Oyj 14 (201)


User Plane Resource creation in MGW

8. A interface planning
The A interface (BSC) is connected either to MGW Rel.4 or to MSC Server
depending on the operator's network architecture. If the A interface is connected
to MGW Rel.4, see the configuration procedures under Creating A interface
(MGW Rel.4 - BSC) in Multimedia Gateway Rel.4 Integration.
9. PSTN/PLMN interface planning
The PSTN/PLMN interface is connected either to MGW Rel.4 or to MSC
Server depending on the operator's network architecture. If the PSTN/
PLMN interface is connected to MGW Rel.4, see the configuration
procedures under Creating A interface (MGW Rel.4 - BSC) in Multimedia
Gateway Rel.4 Integration.

6-108933Issue 1-0 © Nokia Oyj 15 (201)


User Plane Resource creation in MGW

3 Creating MGW Rel. 4 configuration


parameters

3.1 Creating local signalling configuration for MGW


Rel. 4

Before you start


Check that the network element has all the necessary equipment and software

Note
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;

Note
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
elsewhere. For example, in Japan, the signalling point code 23_8_115, would be
read as, 115_8_23.

1. Create SS7 services

Before you start


The 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

6-108933Issue 1-0 © Nokia Oyj 16 (201)


User Plane Resource creation in MGW

how the signalling messages coming into the network element are received and
switched.
a. Check that all necessary services exist (NPI)
Check that all needed services exist on the network element by using the NPI
command. The services SNM and SNT usually exist automatically on the
network element.
The needed services depends 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 signalling 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;
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 we 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.

Note

6-108933Issue 1-0 © Nokia Oyj 17 (201)


User Plane Resource creation in MGW

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 is the
Signalling Point Code (SPC) of the system's own signalling point by
using the NRI command.
ZNFD:<signalling network>, <signalling point
code>,<signalling point parameter set>;

Note
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 parameter 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, if necessary


ZNFB:[<signalling network>],<signalling point
codes>...:<subsystem number>,[<subsystem name>],
[<subsystem status test>];
5. Activate local SCCP subsystems (NHC), if necessary
ZNHC:<signalling network>, <signalling point codes>:
<subsystem>:ACT;
To display the subsystem states, use the NHI or NFJ command.
For more information, see States of SCCP subsystems

3.2 Creating MGW Rel.4 -specific default parameters


This procedure provides instructions on how to create Multimedia Gateway
Rel.4_s AAL2 service endpoint address. It also describes how to configure the
IP QoS related PRFILE parameters for control plane and user plane in MGW
Rel.4.
Please note that the MGW Rel.4 -specific default parameters have to be
configured before traffic can be started.

6-108933Issue 1-0 © Nokia Oyj 18 (201)


User Plane Resource creation in MGW

The MGW Rel.4 -specific default parameters are:


" MGW's AAL2 service endpoint address (E.164)

Note
Zero (0) cannot be used as the initial digit when creating the AAL2 service
endpoint address value.
• DSCP value for signalling (PRFILE parameter)
• DSCP value for user plane (PRFILE parameter)
Steps

1. Create MGW Rel.4's AAL2 service endpoint address (WEC)


ZWEC:AAL2:(SEA=<AAL2 service endpoint address>);
2. Configure IP QoS for signalling (WOC)
The IP QoS for signalling applications in MGW Rel.4 can be configured
by using a PRFILE parameter named DSCP_FOR_SIGNALLING
(053:0009). The parameter is used to set the Differentiated Services
codepoint carried in the Type of Service or Traffic Class field in IPv4 and
IPv6 headers. IP forwarding functions use this value for the treatment of
high priority traffic.

The value range for the DSCP_FOR_SIGNALLING (053:0009)


parameter is 0H - 0FFH . The default value is 0H (Best Effort). For
definitions of the diffServ codepoints and respective values, see
RFC2474, RFC2597, and RFC2598.

Note
If the default value is not suitable, you can change it by using the WOC
command

Caution
In order for the new parameter value to become active, MGW Rel.4 requires a
system restart after the value of the DSCP_FOR_SIGNALLING (053:0009)
parameter is changed.
ZWOC:53,9,<value>;

3. Configure IP QoS for user plane (WOC)


The IP QoS for user plane applications in MGW Rel.4 can be configured
by using a PRFILE parameter named DSCP_FOR_USER_PLANE
(002:0817). The parameter is used to set the Differentiated Services
codepoint carried in the Type of Service or Traffic Class field in IPv4 and
IPv6 headers. IP forwarding functions use this value for the treatment of
high priority traffic.

6-108933Issue 1-0 © Nokia Oyj 19 (201)


User Plane Resource creation in MGW

The value range for the DSCP_FOR_USER_PLANE (002:0817)


parameter is 0H - 0FFH. The default value is 0B8H which corresponds to
Expedited Forwarding. For definitions of the diffServ codepoints and
respective values, see RFC2474, RFC2597, and RFC2598.

Note
If the default value is not suitable, you can change it by using the WOC
command.

Caution
In order for the new parameter value to become active, the IP-NIU units must
be restarted after the value of the DSCP_FOR_USER_PLANE (002:0817)
parameter is changed.
ZWOC:2,817,<value>;

Expected outcome
After successful creation of the MGW Rel.4's AAL2 service endpoint address,
the system outputs an execution printout indicating that the specified address
has been created.
After successful configuration of the DSCP_FOR_SIGNALLING/
DSCP_FOR_USER_PLANE parameter value, the system outputs an execution
printout indicating the new parameter value.
Unexpected outcome
If an error occurs when creating MGW Rel.4's AAL2 service endpoint address,
the system outputs a general MML execution error message. MGW Rel.4's
AAL2 service endpoint can be modified by using the WEMcommand and it can
be deleted by using the WED command.

Example 8: Creating MGW Rel.4 -specific default parameters

1. Create MGW Rel.4's AAL2 service endpoint address 35840113.


ZWEC:AAL2:SEA=35840113;
2. Configure IP QoS for signalling by changing the
DSCP_FOR_SIGNALLING (053:0009) parameter value to 0B8H
(Expedited Forwarding).
ZWOC:53,9,B8;
3. Configure IP QoS for user plane by changing the
DSCP_FOR_USER_PLANE (002:0817) parameter value to 0H (Best
Effort).
ZWOC:2,817,0;

6-108933Issue 1-0 © Nokia Oyj 20 (201)


User Plane Resource creation in MGW

3.3 Defining user plane parameter sets in MGW Rel.4


In MGW Rel.4 various user plane settings and functionalities are configured by
using the DSP parameters and DSP parameter pools. The DSP parameters are
set for the following groups of related connections:
• circuit croup (route)
• signal processing service type
The signal processing service types are Iu/Nb interface service, PSTN/A
interface service and IP Trunk service.
This procedure describes how to create DSP parameter pools and how to
interrogate and modify the DSP parameters.
Before you start
The following list specifies the functionalities that are included in the Iu/Nb
interface service, PSTN/A interface service and IP Trunk service:
• Iu/Nb interface service
This service implements the Iu UP and Nb UP protocols for connecting MGW
Rel.4 to RNC or for connecting two Rel.4 MGWs. It includes jitter buffering
(only for IP backbone interfaces), speech transcoding and speech enhancement
functionalities.
• PSTN/A interface service
This service is used for connecting MGW Rel.4 to BSC or PSTN. It includes
echo cancelling, tandem-free operation (TFO), speech Transcoding and speech
enhancement functionalities.
• IP Trunk interface service
This service is used for connecting MGW Rel.4 to Nokia MSC using integrated
IP Trunk interface. It includes jitter buffering, speech transcoding and speech
enhancement functionalities.

1. Create DSP parameter pool (W4C)


ZW4C:[POOL ID | ANY def ], [DEFAULT POOL ID | 0 def ];

Note
A new parameter pool is always created by using the parameter values of an
existing DSP parameter pool. The first DSP parameter pool is created by using
the default parameter values from pool 0. The default values in pool 0 are fixed
and thus cannot be changed.

6-108933Issue 1-0 © Nokia Oyj 21 (201)


User Plane Resource creation in MGW

2. Interrogate DSP parameters (W4I)


Use the W4I command to interrogate all free and reserved DSP
parameter pool identifiers as well as the DSP parameters of a specified
interface service.
ZW4I:[POOL ID | ALL def ], [SERVICE TYPE | ALL def ];

Note
When the default value (ALL) is used for both DSP parameter pool
identifier and service type parameters, the system outputs all free
and reserved pool identifiers

3. Modify DSP parameters (W4M)


Use the W4M command to modify the DSP parameters of a specified
DSP parameter pool and service type.

Note
The original DSP parameter value will remain unchanged if a new value is not
given.

Caution
Note the following in relation to using the jitter / EC echo path predelay
(PREDELAY) parameter:
Echoes with shorter round trip delays than set to the EC echo path predelay are
not cancelled. The default value 0 ms should be used in a standard network
environment. This caution concerns only the PSTN/A with EC interface service.
Setting the jitter predelay to zero is strictly for testing purposes. It will cause
speech quality problems in a real network environment.

Caution
Note the following in relation to using the comfort noise insertion for EC (CNI)
and non-linear processing for EC (NLP) parameters:
It is recommended that the comfort noise insertion for EC and non-linear
processing for ECare always turned on. Turning either one or both of them off
is strictly for testing purposes. Turning these parameters off will cause speech
quality problems in a real network environment.

ZW4M:[POOL ID | ALL def ], [SERVICE TYPE]:


(DTX=<enable/disable>): (AMRALC=<ALC on/off in egress and/or ingress
direction>, EFRALC=<ALC on/off in egress and/or ingress direction>,
FRALC=<ALC on/ off in egress and/or ingress direction>, G711ALC=<ALC

6-108933Issue 1-0 © Nokia Oyj 22 (201)


User Plane Resource creation in MGW

on/off in egress and/or ingress direction>): (MAX=<maximum gain>,


MIN=<minimum gain>, CONST=<constant gain>, TARGET=<target level>,
GAINMODE=<constant/adaptive>): (PREDELAY=<jitter / EC echo path
predelay>): (TFO=<enable/disable>): (EC=<enable/disable>, CNI=<on/off>,
NLP=<on/off>);
Expected outcome
The execution printouts displayed by the system indicate that the commands
have been successful.
Unexpected outcome
If the system outputs error FILE DISTRIBUTION FAILURE (43179) when
creating the DSP parameter pool, remove the pool with the W4R command and
then try to create it again with the W4C command. Repeat the correction
procedure if necessary.
If the system outputs error FILE DISTRIBUTION FAILURE (43179) when
modifying the DSP parameters, repeat the W4M command.

Example 9. Defining user plane parameter sets in MGW Rel.4

1. Create the DSP pool number 1 by using the parameter values in pool number 0 as the default
values.
ZW4C:1,0;
2. Interrogate the DSP parameters of the PSTN/A interface service from the DSP parameter pool
number 1.
ZW4I:1,PSTNA;
3. Modify the PSTN/A interface service with EC of the parameter pool number 1: disable DTX, put
AMR codec ALC on in egress direction, EFR codec ALC on in both egress and ingress
direction, FR codec ALC on in ingress direction, and G711 codec ALC on in egress direction.
Set constant gain to 5 dB, change gain mode to constant, change EC echo path predelay to 0
milliseconds, disable TFO and enable EC.
ZW4M:1,PSTNAEC:DTX=N:AMRALC=EGRON,EFRALC=ON, FRALC=INGON,G71
1ALC=EGRON:CONST=5,GAINMODE=CON: PREDELAY=0:TFO=N:EC=Y;

6-108933Issue 1-0 © Nokia Oyj 23 (201)


User Plane Resource creation in MGW

4 Configuring signalling connections


MGW Rel.4 - MSC Server

4.1 Creating IP signalling configuration


Before you start
Create first the LAN configuration. It is recommended that you configure the
signalling units in a manner which enables multihoming. In that case each
Ethernet port in the signalling unit must have a separate logical IP address.

Note
You should always use the logical IP address of the unit, when possible.
Otherwise there may be problems with unit switchover.

1. Create an association set (OYC)


ZOYC:<association set name>:<role>;
Note
Remember to check that the association set parameters are correct. For more
information, see Modifying association set parameters.
2. Add associations to the association set (OYA)
ZOYA:<association set name>:<unit type>,<unit index>:
[source port number]:<first destination IP address>,
[netmask length]:[second destination IP address,
[netmask length]:<parameter set name>;
3. Check the associations (OYI)
Verify that the associations were created correctly and that they have
correct IP addresses.
ZOYI::;

6-108933Issue 1-0 © Nokia Oyj 24 (201)


User Plane Resource creation in MGW

4. Give IP addresses to own signalling units


Before creating the virtual signalling channels, the IP configuration must
be created. Each signalling unit at both network elements must have an IP
address. For more information, see Planning IP connection
configuration.
5. Add IP addresses for SCTP multihoming (OYN)
ZOYN:<unit type>,<unit index>:<IP address version>:
<primary source IP address>,[secondary source IP
address];

Note
Before you can use the signalling unit in multihoming manner, you must
activate both Ethernet ports. Choose one IP address from EL0 IP address list
and an other one from EL1 IP address list and configure those IP addresses to
the signalling unit. After the configuration, SCTP can use selected IP addresses
for multihoming.

6. Create IP type SS7 signalling link and link set (NSP)


ZNSP:<signalling network>,<signalling link point
code>,<signalling link set name>,<signalling link
number>:<association set>;
7. Make sure that the far end is compatible (NST, NCL)
Note
You will need to do this step only if the far end of the link is another vendor's
product or any of these Nokia products: SCP, SMSC, 3G-SGSN or FlexiServer
based products. In an interoperability case, deny the link testing with the
command NST. Change the link's parameter set value to 7 with the command
NCL, to prevent it from testing in INIT phase.
8. Create signalling route set (NRC)
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>:<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).
Note
Notice that a signalling point cannot be used as an STP unless it is first
equipped with a direct signalling route.

6-108933Issue 1-0 © Nokia Oyj 25 (201)


User Plane Resource creation in MGW

9. Activate the IP configuration


The activation procedure is the same as when you are creating a non-IP
connection. When you activate a 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 interrogate the
states of the associations, use the command OYI. For more information,
see Activating MTP configuration

4.2 Creating remote SCCP configuration


The 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 start


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

Examine the following things:


• Check that the signalling points have been created on the MTP (the NRI
command) and the services are available for the SCCP (the NPI
command).
• Check which parameter set is used, and whether there is need to modify
the values of the 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.

Before you can create the SCCP to the network element, the SCCP service has
to be created first. 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).

6-108933Issue 1-0 © Nokia Oyj 26 (201)


User Plane Resource creation in MGW

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

Note
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 own SCCP signalling point and its subsystems,
you also 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 later add more subsystems to a signalling point by using the
NFB command. The system may need new subsystems for example when
new services are installed, software is upgraded or network 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. 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 signalling 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 alternative routes that will then be taken into service in case 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

6-108933Issue 1-0 © Nokia Oyj 27 (201)


User Plane Resource creation in MGW

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, OBM)

Note
This step is not necessary for MGW-PSTN/PLMN interface. There are two
different kind of broadcasts you can set (it is recommended that you set both of
them): The local broadcast status (the OBC command) is used to inform the
subsystems of the own signalling point about changes in the subsystems of the
remote signalling points. The broadcast status (the OBM command) is used to
inform other signalling points about changes in the subsystems of the own
signalling point or the subsystems of the signalling points connected to the own
signalling point. When you set local broadcasts, remember that also the remote
network elements have to be configured so that they send the status data to your
network element.

Note
When setting the broadcasts, consider carefully what broadcasts are needed.
Incorrect 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:
• BSSAP Base Station System Application Part
• RANAP Radio Access Network Application Part
• RNSAP Radio Network Subsystem Application Part
For example, the local BSSAP of the MSC has to know the status data of the
BSSAP located in the MGWs, and accordingly, the local BSSAP of the MGW
has to know the status data of the BSSAP in the MSC.

Local broadcasts:
ZOBC:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of local subsystem>,<local subsystem number>:<status>;
Remote broadcasts:
ZOBM:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of concerned signalling point>, <concerned signalling point
code>:<status>;

6-108933Issue 1-0 © Nokia Oyj 28 (201)


User Plane Resource creation in MGW

For more information, see SCCP level signalling network.

4.3 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, only remote
SCCP signalling points have to be activated. To check that the signalling
point really is active, use the NFI command. In the command printout,
the state of signalling point should be AV-EX. If the signalling point
assumes state UA-INS, there is a fault on the MTP level. You can display
the states of SCCP signalling points also by using the command NGI.
Notice that if you use the default values in the command, only the
signalling points of network NA0 are shown. For more information, see
States of SCCP signalling points.

Example 10.
When you examine an example system using the NFI or NGI commands, all
signalling points should be in normal state AV-EX. Note that 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 MGW1 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

2. Activate remote SCCP subsystems (NHC)


ZNHC:<signalling network>, <signalling point codes>:
<subsystem>:ACT;
To display the subsystem states, use the NHI or NFJ command. When
remote subsystems are being activated, their status is not checked from
the remote node. The remote subsystem status becomes AV-EX if the

6-108933Issue 1-0 © Nokia Oyj 29 (201)


User Plane Resource creation in MGW

remote node is available, although the actual subsystem may be


unavailable or even missing. The status of the unavailable subsystem will
be corrected with response method as soon as a message is sent to it. Use
the NHI command to check that the subsystems have assumed stateAV-
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.
3. Set the SS7 network statistics, if needed
By setting SS7 network statistics you can monitor the performance of
SS7 network. You do not have to do it in the integration phase but you
can do it later.
For more instructions, see SS7 signalling performance measurements.

6-108933Issue 1-0 © Nokia Oyj 30 (201)


User Plane Resource creation in MGW

5 Creating interconnecting signalling


connections (MGW Rel.4 - MGW Rel.4)

5.1 Creating remote MTP configuration


In most cases the MTP needs to be configured to the network element. Before
configuring 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.
• A interface, between MGWand BSC. The configuration is based on
TDM.
• PSTN/PLMN interface, between MGW and PSTN/PLMN. The
configuration is based on TDM.
• Iu-CS interface, between MGW and RNC. The configuration is based on
ATM.
• Nb interface, between MGW and MGW. The configuration is based on
ATM.
• 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.
• Iu-PS interface, between RNC and SGSN. The configuration is based on
ATM. To configure IP signalling between MGW and MSS, see
instructions in Creating IP signalling configuration
Before you start
Before you start to create signalling links, check that the SS7 services and own
MTP signalling point have been created. For instructions, see Creating local
signalling configuration for MGW Rel.4.

6-108933Issue 1-0 © Nokia Oyj 31 (201)


User Plane Resource creation in MGW

1. Check that the signalling links are distributed evenly between different
ISUs
Use the following command to display the existing signalling links.
ZNCI;
It is recommended that you allocate signalling links between all working
ISU units to distribute the load. Also, it is very important that signalling
links belonging to the same linkset are allocated to different ISU units to
avoid the whole linkset to become unavailable in an ISU switchover.
2. Create signalling links (NCN/NCS)
To create TDM signalling links, give the command
ZNCN:<signalling link number>:<external interface PCM-
TSL>,<link bit rate>:ISU,<unit number>: <parameter set
number>;
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>;

Note
Before creating ATM signalling links, check that there are free VCLtps
available and that they are correctly configured. For instructions, see Create
VCLtps for signalling
Remember to check by using the WFI command that the network element is
adequately equipped before you start creating signalling links.
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.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and functions. If the ready-made parameter packages
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 link. It is advisable to find out if there will be such special situations
before you start configuring the MTP. See Signalling link parameters.
Here are two examples of special situations in TDM signalling links that 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.

6-108933Issue 1-0 © Nokia Oyj 32 (201)


User Plane Resource creation in MGW

Note
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.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and 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 link.

3. Create SS7 signalling link set (NSC)


Create a signalling link set for each destination.
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 signalling route set. You can reserve several
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>,<signalling link priority>;
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 (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
and related matters such as A interface used between the MGW Rel.4 and
MSC. 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. 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>:<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).

6-108933Issue 1-0 © Nokia Oyj 33 (201)


User Plane Resource creation in MGW

Note
Notice that 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.

Note
The parameters load sharing status and restriction status are not necessary
during MGW Rel.4 integration.

5.2 Activating MTP configuration

1. Allow activation of the signalling links (NLA)


Use the following command to allow the activation of 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 in
case 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.

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


NEL.The activation procedure is the same even when you are creating an
IP connection. When you activate a 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 interrogate the
states of the associations, use the command OYI. For more information,
see Association set and associations.
3. Allow activation of the signalling routes (NVA)
Use the following command to allow the activation of previously created
signalling routes:
ZNVA:<signalling network>,<signalling point code>:

6-108933Issue 1-0 © Nokia Oyj 34 (201)


User Plane Resource creation in MGW

<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;
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 state AV-EX if the related link set is active; otherwise it
assumes state UA-INS. A signalling route going through an STP can also
assume 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 52.
In this example, you change the state of a signalling route which is leading to
signalling point 302. The route is defined in 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:

After this, you use the NVC command to activate the route:
ZNVC:NA0,302::ACT;
The execution printout can be as follows:

6-108933Issue 1-0 © Nokia Oyj 35 (201)


User Plane Resource creation in MGW

5.3 Setting MTP level signalling traffic load sharing


With 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 start


Before 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.

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 (for example, for
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 you want to activate the load sharing and in the signalling route set in
question it is not already allowed (output of the NRI command), you
have to change the load sharing status.
ZNRB:<signalling network>,<signalling point codes>:
LOAD=<load sharing status>;

6-108933Issue 1-0 © Nokia Oyj 36 (201)


User Plane Resource creation in MGW

5.4 Creating remote SCCP configuration


The 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 start


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

Examine the following things:


• Check that the signalling points have been created on the MTP (the NRI
command) and the services are available for the SCCP (the NPI
command).
• Check which parameter set is used, and whether there is need to modify
the values of the 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.
Before you can create the SCCP to the network element, the SCCP service has
to be created first. 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).

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

Note
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).

6-108933Issue 1-0 © Nokia Oyj 37 (201)


User Plane Resource creation in MGW

1. Create remote SCCP signalling points and subsystems (NFD)


In addition to creating the own SCCP signalling point and its subsystems,
you also 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 later add more subsystems to a signalling point by using the
NFB command. The system may need new subsystems for example when
new services are installed, software is upgraded or network 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.
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 signalling point. At this stage you have to
decide whether the routing is based on global title (GT) or on subsystem
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 alternative routes that will then be taken into service in case 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, OBM)

Note
This step is not necessary for MGW-PSTN/PLMN interface.
There are two different kind of broadcasts you can set (it is recommended that
you set both of them):
The local broadcast status (the OBC command) is used to inform the

6-108933Issue 1-0 © Nokia Oyj 38 (201)


User Plane Resource creation in MGW

subsystems of the own signalling point about changes in the subsystems of the
remote signalling points.
The remote broadcast status (the OBM command) is used to inform other
signalling points about changes in the subsystems of the own signalling point or
the subsystems of the signalling points connected to the own signalling point.
When you set local broadcasts, remember that also the remote network elements
have to be configured so that they send the status data to your network element.

Note
When setting the broadcasts, consider carefully what broadcasts are needed.
Incorrect 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:
BSSAP Base Station System Application Part
RANAP Radio Access Network Application Part
RNSAP Radio Network Subsystem Application Part
For example, the local BSSAP of the MSC has to know the status data of the
BSSAP located in the MGWs, and accordingly, the local BSSAP of the MGW
has to know the status data of the BSSAP in the MSC.
Local broadcasts:
ZOBC:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of local subsystem>,<local subsystem number>:<status>;
Remote broadcasts:
ZOBM:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of concerned signalling point>, <concerned signalling point
code>:<status>;
For more information, see SCCP level signalling network.

5.5 Activating SCCP configuration

1. Activate remote SCCP signalling points (NGC)


ZNGC:<signalling network>, <signalling point
codes>:ACT;

6-108933Issue 1-0 © Nokia Oyj 39 (201)


User Plane Resource creation in MGW

You do not have to activate the own SCCP signalling point, only remote
SCCP signalling points have to be activated.
To check that the signalling point really is active, use the NFI command.
In the command printout, the state of signalling point should be AV-EX.
If the signalling point assumes state UA-INS, there is a fault on the MTP
level. You can display the states of SCCP signalling points also by using
the command NGI. Notice that if you use the default values in the
command, only the signalling points of network NA0 are shown. For
more information, see States of SCCP signalling points.

Example 53.
When you examine an example system using the NFI or NGI commands, all
signalling points should be in normal state AV-EX. Note that 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:

2. Activate remote SCCP subsystems (NHC)


ZNHC:<signalling network>, <signalling point codes>:
<subsystem>:ACT;
To display the subsystem states, use the NHI or NFJ command. 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 available, although the actual subsystem may be
unavailable or even missing. The status of the unavailable subsystem will
be corrected with 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

6-108933Issue 1-0 © Nokia Oyj 40 (201)


User Plane Resource creation in MGW

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.
3. Set the SS7 network statistics, if needed
By setting SS7 network statistics you can monitor the performance of
SS7 network. You do not have to do it in the integration phase but you
can do it later. For more instructions, see SS7 signalling performance
measurements.

6-108933Issue 1-0 © Nokia Oyj 41 (201)


User Plane Resource creation in MGW

6 Creating Nb interface with ATM


backbone (MGW Rel.4 - MGW Rel.4)

6.1 Overview of creating Nb interface with ATM


backbone (MGW Rel.4 - MGW Rel.4)
The user plane within the ATM backbone (Nb interface) is transported by using
AAL2 over permanent virtual channel (PVC) connections. AAL2 is used on the
user plane to transport compressed speech and data. MGW Rel.4 uses AAL2
PVC connections, but inside the ATM backbone switched virtual channels
(SVC) may be used as well.
In addition to the user plane traffic, the ATM backbone is used to transport the
control plane traffic by using AAL5. AAL5 PVC/SVC is needed to carry
signalling data (such as AAL2 signalling), and IP over ATM (IPoA) connection
is required when control plane traffic has to be carried over the ATM network.
Using IPoA requires AAL5 PVCs, which are used as IP traffic transportation
medium.
The functional units used to establish the ATM backbone connection are NIS1,
NIS1/P, NIS0, NIS0/P and NIP1. The physical connection used with ATM
backbone is either STM-1 (VC-3/VC-4 mapping) or STM-0 (VC-3 mapping).
The figure below gives an example of the ATM backbone solution (including
the control plane traffic) with the NIS1 unit.

6-108933Issue 1-0 © Nokia Oyj 42 (201)


User Plane Resource creation in MGW

Figure 2 Nb interface with ATM backbone via the NIS1 unit

Note
Creating subdestinations for a destination and defining routing policy are
optional when creating the ATM backbone in MGW Rel.4. In general, creating
basic routing and digit analysis are sufficient. Subdestinations and
subdestination routing policy should be used only if there is a definite need
(load sharing) for several subdestinations and routing policy measures.

Note
The Nb interface can be created using ATM backbone, IP backbone or TDM
backbone. However, it is also possible to utilise more than one backbone
solution simultaneously.

6-108933Issue 1-0 © Nokia Oyj 43 (201)


User Plane Resource creation in MGW

6.2 Configuring PDH for ATM transport


This procedure describes how you can configure PDH/ATM interface for the
NIP1 interface unit. The mode of the PDH interface must be the same for all the
exchange terminals 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. When you have configured new
PETs, you may have to modify their functional modes. Choose either E1, ETSI
specific functional modes, or T1, ANSI specificfunctional modes. In a fractional
E1/T1/JT1 you can select the timeslots that are used to carry user data.

Note
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 start


You must have created a functional unit description for the exchange terminals
(PET). For the instructions, refer to Creating and attaching functional
unit in Hardware Configuration Management.

1. Interrogate the PET's current configuration (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. See the instructions in
Restarting functional unit in Recovery and Unit Working State
Administration.
3. Modify E1 functional modes if needed (YEC)
You can first output the ETSI specific frame modes with the command
ZYEI;
If the current frame mode does not match with the frame mode of the

6-108933Issue 1-0 © Nokia Oyj 44 (201)


User Plane Resource creation in MGW

interface unit that is connected to the remote end of this line, you can
modify it with the command ZYEC:<unit type>,<unit
index>:NORM,(DBLF|CRC4);

Note
Double framing does not support SSM. For more information, see Configuring
synchronisation inputs in Synchronisation and Timing.

4. Modify T1 functional modes if needed (YEG)


You can output the ANSI specific T1 functional modes with the
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 the command
ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|
7.5|15|22.5);
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 interrogate PET timeslot usage with the command
ZYAW:<PET index>...:<timeslot number>...,[ON|OFF def];
7. Create an IMA group, if necessary
If you want to use more than one transmission line, you must create an
IMA group for the physical links. Refer to instructions in Creating IMA
group.
8. Create physical layer Trail Termination Point
Refer to instructions in Creating PhyTTP.

Example 11. Configuring PDH for ATM transport

4. Set the interface operation mode of NIP1 with index number 9 to T1.
ZYAE:NIP1,9,T1;
5. Restart the unit.
ZUSU:NIP1,9;
6. Modify the frame alignment mode of the T1 PET with index 2.
ZYEG:PET,2:ESF,B8ZS,0;
7. Configure PETs with indexes between 15 and 20. Disable scrambling and use S a bit number 7 as
a Syncronization Status Message bit.
ZYAM:PET,15&&20:OFF::7;

6-108933Issue 1-0 © Nokia Oyj 45 (201)


User Plane Resource creation in MGW

8. Create a phyTTP with ID 1 of PET with index 10.


ZYDC:1:PET=10;

6.3 Creating IMA group


This procedure describes how you can create an IMA group and add exchange
terminals 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-basedtransmission 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 lines
fails, the ATM interface stays up. The maximum allowed number for each IMA
group is 8 exchange terminals. TheIMA group must be created at both ends of
the physical links.

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

Before you start


You must 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
WFIcommand. 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.

1. Create IMA group (YBC)


ZYBC:[<IMA group id>] | <system select> def:
[<exchange terminal type> | PET def],<exchange
terminal index>...:<minimum number of links>;
Note
If the IMA group is already tied up to an ATM interface, define the minimum
number of links parameter so that the IMA group capacity equals or is greater

6-108933Issue 1-0 © Nokia Oyj 46 (201)


User Plane Resource creation in MGW

than the used capacity of the ATM interface. For more information, see
Creating VP or VC level connection fails.

2. Add other PETs to the IMA group (YBA)


The exchange terminal to be added must belong to the same NIP1
functional unit as the IMA group. It must not be grouped to any other
IMA group or to a phyTTP.
ZYBA:<IMA group id>:<PET index>;
The maximum number of PETs in the group is 8.
3. Create phyTTP for the IMA group
See the instructions in Creating phyTTP.

Further information
You can interrogate IMA groups with the YBI command, modify with the YBM
command, and delete with the YBD command. It is possible to remove
exchange terminals from IMA group with the YBR command.

Example 12. 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 requirednumber 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;
3. Create phyTTP for the IMA group.
ZYDC:2:IMA=3;

6.4 Configuring SDH for ATM transport


You can configure SDH interfaces and modify the SDH exchange terminal
(SET) configuration.
Before you start
You must have created the functional unit description for the SETs. For the
instructions, see Creating and attaching functional unit in Hardware
Configuration Management.

6-108933Issue 1-0 © Nokia Oyj 47 (201)


User Plane Resource creation in MGW

1. Interrogate the SET (YAI)


With this command you can find out if the configured network interface
unit is NIS0 (STM-0) or NIS1 (STM-1).
ZYAI:<SET>,<SET index>;
2. Configure the SET (YAN)
ZYAN:<SDH exchange terminal index>...:[<SES BIP
threshold>]:[<SD BER threshold>]:[<SF BER threshold>]:
[DIA=(ON|OFF)|LINE=(ON|OFF)|LASER=(ON| OFF)]...:[VC3|
VC4]:[SDH|ATMML|SONET];

Note
This step is only necessary if you want to modify the default settings.

3. Set the SDH trace (YAS)


You can set the SDH trace already during integration or later on, if
necessary.
ZYAS:<SET index>,[<VC path number>]:(OUTPATH| EXPPATH|
OUTREG|EXPREG),(RESET|SET1|SET16|SET64), <trace
value>;
4. Create SDH protection group, if necessary
If you want to secure traffic even when a line fails, you need to create an
SDH protection group. Refer to instructions in Creating SDH protection
group.
5. Create phyTTP
Refer to instructions in Creating PhyTTP.
Further information
You can interrogate the incoming SDH traces with the YAT command.

Example 13. Configuring SDH for ATM transport

1. Modify the SES BIP threshold of the SET 1 to 2300 frames per second.
Enable line loopback.
ZYAN:1:2300:::LINE=ON;
2. Modify the outgoing path trace of the VC path 2 of SET 1. Use 16 byte format.
ZYAS:1,2:OUTPATH,SET16,"OUT PATH TRACE";
3. Create SDH protection group.
See the instructions in Creating SDH protection group.

6-108933Issue 1-0 © Nokia Oyj 48 (201)


User Plane Resource creation in MGW

6.5 Creating SDH protection group


You can create a protection group of SDH exchange terminals. The supported
protocols are optimised and compatible Multiplex Section Protection (MSP)
1+1. Multiplex Section 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 required level. Two SDH exchange terminals
can be added to the protection group.
Note
You cannot freely choose the protected pair in NIS0P. The first SET in the unit
is protecting also the second unit's first SET, the second SET is protecting the
second unit's second SET, and so on.

1. Create SDH protection group (YWC)

Note
The MSP compatible with 1:n protocol is supported only by the NIS1/P units.
The NIS0 unit does not support MSP 1+1.
ZYWC:[<protection group id>|<system select> def], [OPT| COM
def]:<Section 1 SDH exchange terminal index>,<Section 2 SDH
exchange terminal index>:[<wait to restore time>|<default>
def];
2. Create phyTTP
See the instructions for creating the physical layer Trail Termination
Point in Creating phyTTP.

Expected outcome
The system generates the 0101 SHD PROTECTION SWITCHING
EXECUTED notice if the protection switch operation succeeds.

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

Further information
You can interrogate the protection group configuration with the YWI
command, modify the configuration with the YWM command and delete the
configuration with the YWD command.

6-108933Issue 1-0 © Nokia Oyj 49 (201)


User Plane Resource creation in MGW

Example 14. Configuring SDH protection group

Create a protection group of SET 7 (section 1) and SET 4 (section 2) with protection group ID 3 and
with 10 minutes (600 seconds) restore time.
ZYWC:3:7,4:600;

6.6 Creating phyTTP


The 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 interface.
You can create a phyTTP for a single PET, an IMA group, a single SDH VC
path, or a VC path of an SDH protection group.

Note
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 start


You must have configured 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, use the YDI command.

1. Create physical layer Trail Termination Point (YDC)


If you created an IMA group, give the ID of the IMA group to the IMA
parameter. If you created an SDH protection group, give the ID of the
protection group to the PROTGROUP parameter.

Note
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

6-108933Issue 1-0 © Nokia Oyj 50 (201)


User Plane Resource creation in MGW

group>):[<VC path number>| <default>def]:[ATM def|PPP],[ON


def|OFF];

Further information
You can delete a phyTTP with the YDD command. After the deletion its
physical resources are free to be used for another phyTTP. The phyTTP cannot
be deletedif it is used by the upper layer, that is, if there is an ATM created to it.
You can use the YDI command to check whether the phyTTP is in use or not.

Example 15. Creating phyTTP for a SET

Create a phyTTP with ID 1 of SET with index 0 and VC path number 1.


ZYDC:1:SET=0:1:;

Example 16. Creating phyTTP for a PET

Create a phyTTP with ID 1 of PET with index 10.


ZYDC:1:PET=10;

Example 17. Creating phyTTP for an IMA group

Create a phyTTP with ID 2 of IMA with index 20.


ZYDC:2:IMA=20;

6.7 Creating ATM resources for Nb interface


This procedure describes creating ATM resources for the Nb interface.
Configure the hardware (including exchange terminals) and the physical
resources. See Physical interfaces in IP/ATM Network.
For creating the access profile, see the information on VPI bits and VCI bits.
When creating termination points of CBR type, see also Basic guideline for
calculating CDVT.

Caution
When defining traffic parameter values, take into account the capacity
limitations of a single ATM interface. If the resources are misconfigured, the

6-108933Issue 1-0 © Nokia Oyj 51 (201)


User Plane Resource creation in MGW

system will reject the creating of VP/VC connections later. See also Creating
VP or VC level connection fails.

1. Create an ATM interface tied up to a physical layer Trail Termination


Point (LAC)
ZLAC:<interface id>:<interface type>,<phyTTP>;

Table 1 Parameters and values for creatng ATM interface tied up to a physical
layer Trail Termination Point

Parameter Value

interface id Select a numerical value.


If you don't set the value manually, the system will choose the next
free numerical value.

interface type NNI

phyTTP identifier of the phyTTP created

2. Create the access profile of the ATM interface (LAF)


ZLAF:<interface id>:<max VPI bits>:<max VCI bits>;

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

Parameter Value

interface id As defined in step 1

max VPI bits Select a suitable value, for example 5, allowing VPI values from 0 to
31 to be used

max VCI bits Select a value equal or greater than 6, for example 7, allowing VCI
values 32-127 to be used

Expected outcome
The system will select the bandwidth to fully use the capacity of the physical
resource underneath. The printout tells the Maximum ingress bandwidth value
and Maximum egress bandwidth value used.
3. Create a VPLtp for O&M (UBR) traffic if needed (LCC)
Depending on how the operation & maintenance network is planned, you
may need to create a separate external VPLtp for O&M traffic (IP over
ATM connection of UBR type).

6-108933Issue 1-0 © Nokia Oyj 52 (201)


User Plane Resource creation in MGW

ZLCC:<interface id>, <tp type>, <VPI>,,<VPL service


level>:<segment endpoint info>,<VP level traffic
shaping>::<egress service category>,,,<egress QOS
class>;

Table 3. Parameters and values for creating a VPLtp for O&M traffic

Parameter Value

tp type VP

VPL service level VC

segment endpoint info Depends on network planning

egress service category U for UBR

egress QoS class U for Unspecified Class

4. Create VPLtps for CBR traffic (LCC)


Create a necessary number o f VPLtps for SS7 signalling and routing
AAL2 user data.
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>;

Table 4. Parameters and values for creating VPLtps for CBR traffic

Parameter Value

tp type VP

VP service level VC

segment endpoint info Depends on network planning

VP level traffic shaping Depends on network planning

egress service category C for CBR

egress QoS class C1

5. Create a VCLtp for O&M (UBR) connection if needed (LCC)


Depending on how the operation & maintenance network is planned, you
may need to create an external VCLtp for O&M traffic (IP over ATM
connection of UBR type) under VPLtp (for UBR traffic):

6-108933Issue 1-0 © Nokia Oyj 53 (201)


User Plane Resource creation in MGW

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>;

Table 5. Parameters and values for creating a VCLtp for O&M (UBR)
connection

Parameter Value

tp type VC

service category U for Unspecified Bit Rate

egress QoS class U

ingress EPD E for O&M connection

ingress PPD E for O&M connection

egress EPD E for O&M connection

egress PPD E for O&M connection

6. Create VCLtps for signalling (CBR traffic) (LCC)


Create a necessary number of VCLtps for SS7 signalling (MTP3SL)
under the VPLtp(s) for CBR traffic.
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>;

Table 6. Parameters and values for creating VCLtps for signalling (CBR traffic)

Parameter Value

tp type VC
service category C for CBR
QoS class C1
ingress EPD E for SS7 signalling
egress EPD E for SS7 signalling
ingress PPD E for SS7 signalling
egress PPD E for SS7 signalling

6-108933Issue 1-0 © Nokia Oyj 54 (201)


User Plane Resource creation in MGW

7. Create VCLtps for routing (CBR traffic) (LCC)


Create a necessary number of VCLtps for routing (for AAL2 user data,
AAL2UD) under the VPLtp(s) for CBR traffic:
ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingress
service category>,,,<ingress QOS class>:<egressservice
category>,,,<egress QOS class>::<ingress PCR>,<ingress
PCR unit>:<egress PCR>,<egress PCR unit>;

Table 7. Parameters and values for creating VCLtps for routing (CBR traffic)

Parameter Value

tp type VC

service category C for CBR

QoS class C1

6.8 Creating remote MTP configuration


In most cases the MTP needs to be configured to the network element. Before
configuring 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.
• A interface, between MGWand BSC. The configuration is based on
TDM.
• PSTN/PLMN interface, between MGW and PSTN/PLMN. The
configuration is based on TDM.
• Iu-CS interface, between MGW and RNC. The configuration is based on
ATM.
• Nb interface, between MGW and MGW. The configuration is based on
ATM.
• 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.
• Iu-PS interface, between RNC and SGSN. The configuration is based on
ATM.

6-108933Issue 1-0 © Nokia Oyj 55 (201)


User Plane Resource creation in MGW

• To configure IP signalling between MGW and MSS, see instructions in


Creating IP signalling configuration
Before you start
Before you start to create signalling links, check that the SS7 services and own
MTP signalling point have been created. For instructions, see Creating local
signalling configuration for MGW Rel.4.

1. Check that the signalling links are distributed evenly between different
ISUs
Use the following command to display the existing signalling links.
ZNCI;
It is recommended that you allocate signalling links between all working
ISU units to distribute the load. Also, it is very important that signalling
links belonging to the same linkset are allocated to different ISU units
toavoid the whole linkset to become unavailable in an ISU switchover.
2. Create signalling links (NCN/NCS)
To create TDM signalling links, give the command
ZNCN:<signalling link number>:<external interface PCM-
TSL>,<link bit rate>:ISU,<unit number>: <parameter set
number>;
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>;

Note
Before creating ATM signalling links, check that there are free VCLtps
available and that they are correctly configured. For instructions, see Create
VCLtps for signalling

Remember to check by using the WFI command that the network element is
adequately equipped before you start creating signalling links. 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 signallinglink set to become unreachable.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and functions. If the ready-made parameter packages
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 link. It is advisable to find out if there will be such special situations
before you start configuring the MTP. See Signalling link parameters. Here are
two examples of special situations in TDM signalling links that require
modifications in the parameter set:

6-108933Issue 1-0 © Nokia Oyj 56 (201)


User Plane Resource creation in MGW

• 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.

Note
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.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and 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 link.

3. Create SS7 signalling link set (NSC)


Create a signalling link set for each destination.
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 signalling route set. You can reserve several
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>,<signalling link priority>; 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 (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
and related matters such as A interface used between the MGW Rel.4 and
MSC. 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. Later you can add signalling
routes to a route set with the NRA command.
ZNRC:<signalling network>,<signalling point

6-108933Issue 1-0 © Nokia Oyj 57 (201)


User Plane Resource creation in MGW

code>,<signalling point name>,<parameter set


number>,<load sharing status>,<restriction
status>:<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 transferpoint (STP).

Note
Notice that 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.

Note
The parameters load sharing status and restriction status
are not necessary during MGW Rel.4 integration.

6.9 Activating MTP configuration

1. Allow activation of the signalling links (NLA)


Use the following command to allow the activation of 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 in
case 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.
To interrogate the states of signalling links, use the commands NLI or
NEL.
The activation procedure is the same even when you are creating an IP
connection. When you activate a SS7 signalling link, the system

6-108933Issue 1-0 © Nokia Oyj 58 (201)


User Plane Resource creation in MGW

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 interrogate the
states of the associations, use the command OYI. For more information,
see Association set and associations.
3. Allow activation of the signalling routes (NVA)
Use the following command to allow the activation of 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;
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 state AV-EX if the related link set is active; otherwise it
assumes state UA-INS. A signalling route going through an STP can also
assume 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 18.

In this example, you change the state of a signalling route which is leading to
signalling point 302. The route is defined in 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:

ALLOWING ACTIVATION OF SIGNALLING ROUTE

DESTINATION: SP ROUTES: SP
NET SP CODE H/D NAME NET SP CODE H/D NAME

NA0 0302/00770 MSS2 NA0 0302/00770 MSS2


ACTIVATION ALLOWED

COMMAND EXECUTED

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

6-108933Issue 1-0 © Nokia Oyj 59 (201)


User Plane Resource creation in MGW

ZNVC:NA0,302::ACT;

The execution printout can be as follows:


CHANGING SIGNALLING ROUTE STATE

DESTINATION: SP ROUTES: SP OLD NEW


NET 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

SIGNALLING ROUTE ACTIVATING FAILED

COMMAND EXECUTED

6.10 Setting MTP level signalling traffic load sharing


With 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 start


Before 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.

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 (for example, for STP
traffic according to the ANSI standards, the load sharing system is
different).
ZNEO:;

6-108933Issue 1-0 © Nokia Oyj 60 (201)


User Plane Resource creation in MGW

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 you want to activate the load sharing and in the signalling route set in
question it is not already allowed (output of the NRI command), you
have to change the load sharing status.
ZNRB:<signalling network>,<signalling point
codes>:LOAD=<load sharing status>;

6.11 Creating routing objects and digit analysis for Nb


interface in MGW (ATM AAL2)
This procedure describes how to create routing objects and digit analysis with
MML commands for the Nb interface using ATMAAL2. The Nb interface is an
interface between two Multimedia Gateways (MGW). Digit analysis is needed
to find the right route to an adjacent node (that is, the route to another MGW).
The number of the analysis tree (the value of the TREE parameter in the RDC
command) must be the same as the tree number set for the desired Virtual
Media Gateway (VMGW) (the value of the A2T parameter in the JVC
command). The associated signalling used is broadband MTP3 signalling. The
routing objects, digit analysis and subdestinations must be created at both ends
of the Nb interface between two network elements before any user plane
connections can be built between them.

Note
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.

Note
Creating subdestinations for a destination and defining routing policy are
optional when creating the ATM backbone in MGW Rel.4. In general, creating
basic routing and digit analysis are sufficient. Subdestinations and
subdestination routing policy should be used only if there is a definite need (for
example load sharing) for several subdestinations and routing policy measures.
For more information on subdestinations and routing policies, see Creating
routing objects and digit analysis with subdestinations and routing policy for

6-108933Issue 1-0 © Nokia Oyj 61 (201)


User Plane Resource creation in MGW

AAL2 nodal switching functionality in MGW.

Before you start


Before 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 analyses and components by using the commands of the RI
command group.

1. Create an AAL2 route (RRC)


ZRRC:ROU=<route number>,TYPE=AAL2,PRO=MTP3:
NET=<signalling network>,SPC=<signalling point
code>,ANI=<AAL2 node identifier>;
2. Create an endpoint group (LIC)
ZLIC:<route number>,<ep group index>:<ingress service
category>, <egress service category>;
The ingress and egress service categories should always be Constant Bit
Rate (CBR).
3. Check that there is a free VCLtp (LCI)
ZLCI:<interface id>,VC:<VPI>:FREE;
Out of these VCIs all those with service category CBR in both directions
can be used in the next step.
4. Create an endpoint (LJC)
ZLJC:<ep type>,<route number>,<connection id>:
<interface id>,<VPI>,<VCI>:<ownership>:[<loss
ratio>,<mux delay>];
The system will automatically assort this endpoint into the endpoint
group of step 2 since their service categories match.
5. Unblock the AAL type 2 path (LSU)
ZLSU:<ANI>:<AAL type 2 path identifier>:<execution
time>;
The execution printout followed by the unblocking should indicate that
both the local end and the remote end of the AAL type 2 path are
unblocked.
Expected outcome
The 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.
Unexpected outcome
The AAL type 2 path is still in blocked state. Repeat the unblocking command.

6-108933Issue 1-0 © Nokia Oyj 62 (201)


User Plane Resource creation in MGW

6. Create digit analysis (RDC)


Create a digit analysis for a specific digit sequence. The specific digit
sequence is the MGWAAL2 Service Endpoint Address of the remote
end. Add number 45 before the digit sequence in order to avoid conflicts
with other number formats.
ZRDC:DIG=<digits>,TREE=<analysistree>:ROU=<route
number>;

Example 19. Create routing objects and digit analysis for Nb interface using ATM AAL2

In the following example, routing objects and digit analysis are created for the
Nb interface using ATM AAL2.

1. Create an AAL2 route between two MGWs. 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 AAL2 destination node is
AAL2MGW1. ZRRC:ROU=11,TYPE=AAL2,PRO=MTP3:NET=NA0,SPC=701,
ANI=AAL2MGW1;
2. Create an endpoint group under route 11. The endpoint group id is automatically selected by the
system. The termination points in this group shall have the Constant Bit Rate service category
for both ingress and egress directions.
ZLIC:11,1:C,C;
3. Check that there is a free VCLtp.
ZLCI:<interface id>,VC:<VPI>:FREE;
Notice, 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.
4. 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 AAL2 type 2 loss ratio is 10_4 and the AAL type 2
multiplexing delay 2 ms.
ZLJC:VC,11,5:2,1,33:LOCAL:4,20;
The system will automatically assort this endpoint into the endpoint group of step 2 since their service
categories match.
5. Unblock the AAL type 2 path 11. The ANI is AAL2MGW1 and the allowed waiting time for the
execution of the blocking command is 18 seconds.
ZLSU:AAL2MGW1:11:18;
6. Create digit analysis for the digit sequence 4535840114 in analysis tree 55.
ZRDC:DIG=4535840114,TREE=55:ROU=11;

6.12 Creating routing objects and digit analysis with


subdestinations and routing policy for Nb interface
This procedure describes how to create routing objects and digit analyses with
subdestinations and routing policy for the Nb interface with MML commands.

6-108933Issue 1-0 © Nokia Oyj 63 (201)


User Plane Resource creation in MGW

Digit analysis is needed in the Nb interface, which connects two MGWs


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

Note
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.
There are two different approaches to creating digit analysis for the Nb
interface:
• creating (basic) digit analysis, where each destination has only one
subdestination
• creating digit analysis, where each destination can have more than one
subdestination.
Creating subdestinations for a destination and defining routing policy (the latter
approach above) are optional features. Generally speaking, creating basic digit
analysis is sufficient, and it is recommended that the latter approach be used
only if there is a definite need for several subdestinations and routing policy
measures.
The routing policy function allows you to utilise percentage call distribution
(also known as load sharing). With percentage call distribution traffic to a
destination can be distributed among two or more subdestinations in predefined
proportions.

Note
Creating subdestinations for a destination and defining routing policy are
optional when creating the ATM backbone in MGW Rel.4. In general, creating
basic routing and digit analysis are sufficient. Subdestinations and
subdestination routing policy should be used only if there is a definite need (for
example load sharing) for several subdestinations and routing policy measures.

Before you start


Before 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 analyses
and components by using the commands of the RI command group.

6-108933Issue 1-0 © Nokia Oyj 64 (201)


User Plane Resource creation in MGW

1. Create an AAL2 route (RRC)


ZRRC:ROU=<route number>,TYPE=AAL2,PRO=<protocol>:
NET=<signalling network>,SPC=<signalling point
code>,ANI=<AAL2 node identifier>;
2. Create an endpoint group (LIC)
ZLIC:<route number>,<ep group index>:<ingress service
category>, <egress service category>; The ingress and
egress service categories should always be Constant
Bit Rate (CBR).
3. Check that there is a free VCLtp (LCI)
ZLCI:<interface id>,VC:<VPI>:FREE; Out of these VCIs
all those with service category CBR in both directions
can be used in the next step.
4. Create an endpoint (LJC)
ZLJC:<ep type>,<route number>,<connection id>:
<interface id>,<VPI>,<VCI>:<ownership>:[<loss
ratio>,<mux delay>];
The system will automatically assort this endpoint into the endpoint
group of step 2 since their service categories match.
5. Unblock the AAL type 2 path (LSU)
ZLSU:<ANI>:<AAL type 2 path identifier>:<execution
time>;
The endpoints must have been created at both ends of the interface before
the AAL type 2 path between them can be unblocked.
Expected outcome
The 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.
Unexpected outcome
The AAL type 2 path is still in blocked state. Repeat the unblocking command.
6. Create subdestinations (RDE)
ZRDE:NSDEST=<name of subdestination>:ROU=<route
number>;

Note
You can create 1 to 5 subdestinations for each destination. Repeat the command
for each subdestination

7. Create a destination (RDE)


ZRDE:NDEST=<name of destination>:NSDEST=<name of
subdestination>;

Note

6-108933Issue 1-0 © Nokia Oyj 65 (201)


User Plane Resource creation in MGW

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

8. Create digit analysis (RDC)


Create a digit analysis for a specific digit sequence. The specific digit
sequence is the MGWAAL2 Service Endpoint Address of the remote
end.
ZRDC:TREE=<analysis tree>,DIG=<digits>:NDEST=<name of
destination>;
9. Define percentage call distribution (RMM)
ZRMM:NDEST=<destination name>::SPERC1=<percentage
value of subdestination 1>,SPERC2=<percentage value of
subdestination 2>,SPERC3=<percentage value of
subdestination 3>,SPERC4=<percentage value of
subdestination 4>;

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

Example 20. Create routing objects and digit analysis for Nb interface with percentage routing

In 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.

1. Create an AAL2 route between two MGWs. 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 AAL2 destination node is
AAL2MGW1. ZRRC:ROU=11,TYPE=AAL2,PRO=MTP3:NET=NA0,SPC=701,
ANI=AAL2MGW1;
2. Create an endpoint group under route 11. The endpoint group id is automatically selected by the
system. The termination points in this group shall have the Constant Bit Rate service category
for both ingress and egress directions.
ZLIC:11,1:C,C;
3. Check that there is a free VCLtp.
ZLCI:<interface id>,VC:<VPI>:FREE;
Notice, 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.
4. 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 AAL2 type 2 loss ratio is 10_4 and the AAL type 2
multiplexing delay 2 ms.
ZLJC:VC,11,5:2,1,33:LOCAL:4,20;

6-108933Issue 1-0 © Nokia Oyj 66 (201)


User Plane Resource creation in MGW

The system will automatically assort this endpoint into the endpoint group of step 2 since their service
categories match.
5. Unblock the AAL type 2 path 2. The ANI is AAL2MGW1 and the allowed waiting time for the
execution of the blocking command is 18 seconds.
ZLSU:AAL2MGW1:5:18;
6. 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;

Note
In this example it is presumed that routes 2 and 3 have been created separately
by following steps 1 to 5 above.

7. Create the destination LONDON, define three subdestinations for it:


ZRDE:NDEST=LONDON:NSDEST=HELSINKI1;
ZRDE:NDEST=LONDON:NSDEST=GOTHENBURG;
ZRDE:NDEST=LONDON:NSDEST=HAMBURG;
8. Create digit analysis for the digit sequence 4535840114 in analysis tree 55.
ZRDC:DIG=4535840114,TREE=55:NDEST=LONDON;
9. Create percentage call distibution.
Define the percentage call distribution values of routing alternatives so that the primary
subdestination covers 60% of traffic, the subdestination equivalent to the first alternative
subdestination 30% of traffic and the third alternative subdestination 10% of traffic:
ZRMM:NDEST=LONDON::SPERC0=60,SPERC1=30,SPERC2=10;
Once you have created subdestinations and defined percentage call distribution for these, you can modify
these settings with the RMM command.

6.13 Example: Creating Nb interface with ATM


backbone using ATM AAL2 (MGW Rel.4 - MGW Rel.4)
This procedure provides an example for creating the Nb interface with ATM
backbone in MGW Rel.4. In this example the Nb interface is created by using
ATM AAL2 connections.

1. Create phyTTP (YDC)


ZYDC:1:SET=0:1;
2. Create ATM resources for Nb interface (LAC, LAF, LCC)

6-108933Issue 1-0 © Nokia Oyj 67 (201)


User Plane Resource creation in MGW

a. Create an ATM interface tied up to a physical layer Trail


Termination Point (LAC)
ZLAC:2:NNI,1;
b. Create the access profile of the ATM interface (LAF)
ZLAF:2:8:8;
c. Create VPLtps for CBR traffic (LCC)
ZLCC:2,VP,1,,VC:::C,,,C1:::150,KCPS:STATE=UNLOCKE
D;
d. Create VCLtps for signalling and routing (CBR traffic) (LCC)
ZLCC:2,VC,1,32::C,E,E,C1:C,E,E,C1::300,CPS:300,CP
S;
ZLCC:2,VC,1,33::C,,,C1:C,,,C1::15,KCPS:15,KCPS;
3. Create MTP configuration (NCS, NRC)
a. Create signalling links (NCS)
ZNCS:3:2,1-32:ISU,0:5;
b. Create ATM signalling link set (NCS)
ZNSC:NA0,701,MGW2:3,2;
c. Create signalling route set (NRC)
ZNRC:NA0,701,MGW2,0,,N:,,,7;
4. Activating MTP configuration (NLA, NLC, NVA, NVC)
a. Allow activation of the signalling links (NLA)
ZNLA:3;
b. Activate the signalling links (NLC)
ZNLC:3,ACT;
c. Allow activation of the signalling routes (NVA)
ZNVA:NA0,701;
d. Activate signalling routes (NVC)
ZNVC:NA0,701:,:ACT;
5. Create routing objects and digit analysis for Nb interface (RRC, LIC,
LJC, LSU, RDC)
a. Create an AAL2 route (RRC)
ZRRC:ROU=11,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=701,AN
I=AAL2MGW1;
b. Create an endpoint group (LIC)
ZLIC:11,1:C,C;
c. Create an endpoint (LJC)
ZLJC:VC,11,5:2,1,33:LOCAL:4,20;
d. Unblock the AAL type 2 path (LSU)
ZLSU:AAL2MGW1:5;
e. Create digit analysis (RDC)
ZRDC:DIG=4535840114,TREE=55:ROU=11;

6-108933Issue 1-0 © Nokia Oyj 68 (201)


User Plane Resource creation in MGW

7 Creating Nb interface with IP backbone


(MGW Rel.4 - MGW Rel.4)

7.1 Overview of creating Nb interface with IP


backbone (MGW Rel.4 - MGW Rel.4)
The user plane traffic within the IP backbone (Nb interface) is conveyed by
using the Real-time Transport Protocol (RTP). RTP provides end-to-end
delivery services for data with real-time characteristics, such as interactive
audio. These services include payload type identification, sequence numbering,
time stamping and delivery monitoring. This makes RTP an ideal protocol for
real-time applications such as voice over IP (VoIP).
When the IP backbone is used to connect two MGW Rel.4 network elements,
there are several options available for the operator to establish the connection.
However, all of the options require a new IP network interface unit (IP-NIU).
The table below lists the available IP-NIU options.

Table 8 IP-NIU options in IP backbone

6-108933Issue 1-0 © Nokia Oyj 69 (201)


User Plane Resource creation in MGW

The key factor which determines the IP backbone solution to be used is whether
the operator wants to separate the control plane traffic from the user plane
traffic. The available IP backbone solutions are described below.

IP backbone with control plane and user plane not separated


By default both control plane (SIGTRAN and H.248 signalling) and user plane
traffic are routed through the same IP-NIU unit using either the Gigabit
Ethernet (1Gbit/s) or Fast Ethernet (100Mbit/s). Gigabit Ethernet with IPGE
functional unit is a typical solution when MSC Server and MGW Rel.4 are on
the same site. The figure below illustrates the Gigabit Ethernet and Fast
Ethernet solutions when control plane and user plane traffic are not separated.

6-108933Issue 1-0 © Nokia Oyj 70 (201)


User Plane Resource creation in MGW

Figure 3 IP backbone with Gigabit Ethernet/Fast Ethernet (control plane and


user plane not separated)

IP backbone with control plane and user plane separated


If the operator decides to use control plane isolation (for security or capacity
reasons), there are two options which enable the encryption of the control plane
traffic with a separate device.
1. When the Gigabit Ethernet physical interface is used for the user plane
traffic, IP-NIU (IPGE/IPGO) cannot be used to separate the control plane
traffic from the user plane traffic. However, it is still possible to isolate
control plane traffic by routing it directly from the ISU units into ESA12
(L2 switch). The new signalling unit CCP10 provides redundant LAN
interface for this purpose. The figure below illustrates the ESA12
solution.

6-108933Issue 1-0 © Nokia Oyj 71 (201)


User Plane Resource creation in MGW

Figure 4. IP backbone with Gigabit Ethernet (control plane and user plane
separated)

2. When the Fast Ethernet physical interface is used, IP-NIU can be used to
separate the control plane traffic from the user plane traffic. The 2N
redundant IP-NIU has 8 Fast Ethernet interfaces, of which one or several
interfaces can be exclusively dedicated to control plane, thus providing a
separate LAN for control plane traffic. The remaining interfaces can be
dedicated to user plane traffic.
The figure below illustrates how the Fast Ethernet interfaces of IP-NIU
(IPFE) are used to separate the control plane traffic from the user plane
traffic.

Figure 5. IP backbone with Fast Ethernet (control plane and user plane
separated)

Note

6-108933Issue 1-0 © Nokia Oyj 72 (201)


User Plane Resource creation in MGW

The Nb interface can be created using ATM backbone, IP backbone or TDM


backbone. However, it is also possible to utilise more than one backbone
solution simultaneously.

7.2 Configuring IP for Nb user plane (MGW Rel.4 _ IP


backbone)
The IP connection for Nb user plane traffic between MGW Rel.4 and the IP
backbone must be configured during integration. User plane traffic is
transported through the IPFE/IPFEP/IPGE/IPGEP/IPGO/IPGOP unit.

Note
If the 1G Ethernet interface (IPGE/IPGEP/IPGO/IPGOP unit) is used for user
plane traffic, it is not possible to isolate SIGTRAN, H248, IWF control and
O&M traffic from user plane traffic into its own physical interface via IP-NIU.
In that case, if you want to separate the control plane traffic, it is possible to use
ESA12 internal Ethernet switches.

1. Configure the IP stack of the TCU unit


Configure the IP stack of the TPG units in TCU according to instructions
in Configuring IP stack in functional units of MGW Rel.4.
Assign physical IP address for the IP interface AI0 of the TPG units and
give the IP address of the IFETH0 interface of the IP-NIU as the
destination IP address. Then, create the default static route between the
TPG units and the IP-NIU.
2. Configure internal connections for IP-NIU
Configure the IPFE/IPFEP/IPGE/IPGEP/IPGO/IPGOP unit according to
instructions in Configuring internal connections for IP-NIU.
3. Configure the external connection
Configure external connection through IP-NIU according to instructions
in Connecting to external network via IP-NIU.

6-108933Issue 1-0 © Nokia Oyj 73 (201)


User Plane Resource creation in MGW

8 Creating Nb interface with TDM


backbone (MGW Rel.4 - MGW Rel.4)

8.1 Overview of creating Nb interface with TDM


backbone (MGW Rel.4 - MGW Rel.4)
TDM backbone can be used to create the Nb interface if the operator has an
existing cost-efficient and high-capacity TDM-based transmission network.
When there is enough capacity and the network is cost-efficient, it is not
necessary to change the existing TDM-based transmission network into a
packet- based network when upgrading to Rel.4 level.
Also, using TDM backbone makes it possible for the operator to reduce the
number of simultaneous changes when upgrading the network to Rel.4 level.
Upgrading to Rel.4 level inevitably requires considerable changes in the
network, such as separating the control plane and user plane traffic. However,
the operators can utilise the existing TDM-based transmission network to
achieve the basic Rel.4 level functionality and thus schedule other changes,
such as upgrading to packet-based network, according to the operator-specific
network evolution plans.
When using the TDM backbone, the control plane traffic is routed via ESA12
unit to MSC Server and user plane traffic is routed via NIWU unit to another
MGW Rel.4. The figure below ilustrates the TDM backbone solution:

6-108933Issue 1-0 © Nokia Oyj 74 (201)


User Plane Resource creation in MGW

Figure 6 Nb interface with TDM backbone

Note
The Nb interface can be created using ATM backbone, IP backbone or TDM
backbone. However, it is also possible to utilise more than one backbone
solution simultaneously.

6-108933Issue 1-0 © Nokia Oyj 75 (201)


User Plane Resource creation in MGW

8.2 Configuring PDH for TDM transport


This procedure describes how you can configure PDH/TDM for the NIWU
interface unit. The mode of the PDH interface must be the same for all the
exchange terminals (ET) in the plug-in unit. That is why the NIWU unit must
begiven as a parameter when the PDH mode is configured.
Usually the existing default values for the PDH supervision are adequate and
youdo not have to change them. If needed, you can configure and modify the
exchange terminal supervision parameters.
The network element provides a synchronisation interface for external timing
reference signals. For information on synchronisation, see Configuring
synchronisation inputs in Synchronisation and Timing.
When you have configured new ETs, you may have to modify their functional
modes. Choose either E1, ETSI specific functional modes, or T1, ANSI specific
functional modes. The default mode for PDH/TDM is E1.

Before you start


You must have created the functional unit description for the ETs. For the
instructions, see Creating and attaching functional unit in Hardware
Configuration Management.

1. Interrogate the ET's current configuration (YAI)


ZYAI:ET;
2. Set the interface operation mode of NIWU (YAE)
Set the operation mode if you want to change it from E1 to T1/JT1 or
from T1/JT1 to E1. The impedance parameter can be given only if the
operation mode given is E1.
ZYAE:NIWU,<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. See the instructions in
Restarting functional unit in Recovery and Unit Working State
Administration.
3. Modify E1 functional modes, if needed (YEC)
You can first output the ETSI specific frame modes with the command
ZYEI;
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 the command
ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);
Note

6-108933Issue 1-0 © Nokia Oyj 76 (201)


User Plane Resource creation in MGW

Double framing does not support SSM. For more information, see Configuring
synchronisation inputs in Synchronisation and Timing.

4. Modify T1 functional modes if needed (YEG)


You can first output the ANSI specific T1 functional modes with the
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 the command
ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|
7.5|15|22.5);

Example 21. Configuring PDH for TDM (ETSI standard /E1)

1. Interrogate the current configuration.


ZYAI:ET;
2. Set the interface operation mode of NIWU with index number 3 to E1 and with impedance 75 ©.
ZYAE:NIWU,3,E1:75;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ETSI-specific functional modes.
ZYEI;
5. Modify E1 functional modes of the ET with index 2.
ZYEC:ET,2:NORM,CRC4;

Example 22. Configuring PDH for TDM (ANSI standard /T1)

1. Interrogate the current configuration.


ZYAI:ET;
2. Set the interface operation mode of NIWU with index number 3 to T1.
ZYAE:NIWU,3,T1;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ANSI-specific functional modes.
ZYEH;
5. Modify T1 functional modes of the ET with index 2.
ZYEC:ET,2:ESF,B8Z2,0;

6-108933Issue 1-0 © Nokia Oyj 77 (201)


User Plane Resource creation in MGW

8.3 Creating routing objects for TDM resources


controlled by MSC server
This procedure describes how to divide TDM resources in a multimedia
gateway (MGW). In other words, this enables you to dedicate TDM resources
of an MGW to different virtual gateways on one physical gateway element.
Dividing TDM resources in a virtual MGW entails first creating a special circuit
group (SPE CGR) with the USE parameter and then adding circuits to this SPE
CGR with 'VMGW' as the USE parameter.
TDM resources in MGW are configured to a Virtual MGW (VMGW) which is
connected to an MSC server over H.248. How these TDM resources are used
(PSTN/PLMN interface, A interface, interconnecting TDM connections etc.)
depends on the signalling attached to them in the MSC server.
In digit analysis, TDM resources are hunted by MSC Server. The TDM
resources in an MGW are divided for virtual MGWs so that resources
controlled by each MSC Server are in their own circuit groups. TDM circuits,
which have different properties, are also in separate circuit groups.

1. Create a special circuit group (SPE CGR) with the USE parameter (RCC)
ZRCC:TYPE=<circuit group type>,NCGR=<circuit group
name>, CGR=<circuit group number>,TYPE=SPE:USE=<use of
the SPE CGR>;
Note
In order to be able to use TDM resources they must be attached to a VMGW.
You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.
For more information on creating a VMGW, see Configuring H.248 control
protocol (MGW Rel.4 - MSC Server).
2. Add TDM circuits to the SPE CGR (RCA)
ZRCA:NCGR=<circuit group name>,CGR=<circuit group
number>: CRCT=<circuit(s)>;
3. Change the state of the circuit group to WO-EX (CIM)
ZCIM:(NCGR=<circuit group name>...|CGR=<circuit group
number>...):(WO|BA);
4. Change the state of the circuits to WO-EX (CIM)
ZCIM:CRCT=<circuit(s)>...:(WO|BA);

6-108933Issue 1-0 © Nokia Oyj 78 (201)


User Plane Resource creation in MGW

Note
The following CGR features can also be modified:
• POOLID
Different kind of user plane properities can be used by dividing circuits to
separate circuit groups and by attaching different User Plane Parameter sets to
those (POOLID). User Plane parameter sets can be defined with the W4-MML
commands. A new User Plane Parameter set can be attached to the CGR with
the RCM command:
ZRCM:CGR=<circuit group number>:POOLID=<POOLID number>;

• ECHO
The echo cancellation feature is needed in traffic between MGW and PSTN.
The echo parameter defines whenever the DSP resources are reserved for the
echo cancellation at the resource reservation phase. By setting the 'Y' value, it
guarantees that DSP resources will be available for the echo cancellation if this
is needed. Moreover, selecting the 'Y' value will also reserve the DSP resources
even when echo cancellation is not needed by the call; in this way, incorrect
configuration can limit the amount of calls that MGW can handle. Notice, also,
that the echo cancellation configurations of TDM circuits should be the same
both in MGWand in MSC Server. If these configurations differ significantly,
DSP capacity is wasted and problems concerning echo may arise. The echo
parameter is set to the 'N' ('not in use') value by default.
The value of the echo parameter can be modified with the RCM command:
ZRCM:CGR=<circuit group number>:ECHO=<Y/N>;

Example 23. Create routing objects for TDM resources

1. Create a special circuit group (CGR) with the VMGW parameter.


ZRCC:NCGR=VMGW1,CGR=1,TYPE=SPE:USE=VMGW;

Note
In order to be able to use TDM resources they must be attached to a VMGW.
You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.

6-108933Issue 1-0 © Nokia Oyj 79 (201)


User Plane Resource creation in MGW

For more information on creating a VMGW, see Configuring H.248 control


protocol (MGW Rel.4 - MSC Server).

2. Add TDM circuits to the CGR.


ZRCA:NCGR=VMGW1:CRCT=1-1&&-31;
3. Change the state of the circuit group to WO-EX.
ZCIM:CGR=1:WO;
4. Change the state of the circuits to WO-EX.
ZCIM:CRCT=1-1&&-31:WO;

6-108933Issue 1-0 © Nokia Oyj 80 (201)


User Plane Resource creation in MGW

9 Creating interconnecting TDM


connections (MGW Rel.4 - MSC Server,
MGW Rel.4 - CDS)

9.1 Overview of creating interconnecting TDM


connections in MGW Rel.4
MGW Rel.4 utilises interconnecting TDM connections to:
• route data calls between MGW Rel.4 and Integrated MSC Server.
Integrated MSC Server contains the interworking function/IWF required
by mobile circuit-switched data calls. The IWF control protocol, handled
via a Nokia proprietary interface, is used to control the interconnecting
TDM connection between MGW Rel.4 and Integrated MSC Server
(IWF). For more information on the IWF control protocol, see
Configuring IWF/CDS control protocol (MGW Rel.4 _ IWF/CDS).
• route data calls between MGW Rel.4 and Circuit-switched Data Server
(CDS). CDS is a standalone network element which contains the IWF.
The IWF control protocol, handled via a Nokia proprietary interface, is
used to control the interconnecting TDM connection between MGW
Rel.4 and CDS. For more information on the IWF control protocol, see
Configuring IWF/CDS control protocol (MGW Rel.4 _ IWF/CDS).
• route normal TDM based user plane traffic between MGW Rel.4 and
MSC Server (for example in a call from 2G BSS to PSTN). In this case
the TDM resources are configured to different Virtual Media Gateways
(VMGW) within a physical MGW Rel.4 network element. The H.248
control protocol is used to control the interconnecting TDM connection
between MGW Rel.4 and MSC Server. For more information on the
H.248 control protocol, see Configuring H.248 control protocol (MGW
Rel.4 - MSC Server).
The following figure illustrates the interconnecting TDM connections in MGW
Rel.4:

6-108933Issue 1-0 © Nokia Oyj 81 (201)


User Plane Resource creation in MGW

Figure 7. Interconnecting TDM connections in MGW Rel.4

9.2 Configuring PDH for TDM transport


This procedure describes how you can configure PDH/TDM for the NIWU
interface unit. The mode of the PDH interface must be the same for all the
exchange terminals (ET) in the plug-in unit. That is why the NIWU unit must be
given as a parameter when the PDH mode is configured.

6-108933Issue 1-0 © Nokia Oyj 82 (201)


User Plane Resource creation in MGW

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.
The network element provides a synchronisation interface for external timing
reference signals. For information on synchronisation, see Configuring
synchronisation inputs in Synchronisation and Timing. When you have
configured new ETs, you may have to modify their functional modes. Choose
either E1, ETSI specific functional modes, or T1, ANSI specific functional
modes. The default mode for PDH/TDM is E1.

Before you start


You must have created the functional unit description for the ETs. For the
instructions, see Creating and attaching functional unit in Hardware
Configuration Management.

1. Interrogate the ET's current configuration (YAI)


ZYAI:ET;
2. Set the interface operation mode of NIWU (YAE)
Set the operation mode if you want to change it from E1 to T1/JT1 or
from T1/JT1 to E1. The impedance parameter can be given only if the
operation mode given is E1.
ZYAE:NIWU,<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. See the instructions in
Restarting functional unit in Recovery and Unit Working State
Administration.
3. Modify E1 functional modes, if needed (YEC)
You can first output the ETSI specific frame modes with the command
ZYEI;
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 the command
ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);

Note
Double framing does not support SSM. For more information, see Configuring
synchronisation inputs in Synchronisation and Timing.

4. Modify T1 functional modes if needed (YEG)


You can first output the ANSI specific T1 functional modes with the
command

6-108933Issue 1-0 © Nokia Oyj 83 (201)


User Plane Resource creation in MGW

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 the command
ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|
7.5|15|22.5);

Example 24. Configuring PDH for TDM (ETSI standard /E1)

1. Interrogate the current configuration.


ZYAI:ET;
2. Set the interface operation mode of NIWU with index number 3 to E1 and with impedance 75 ©.
ZYAE:NIWU,3,E1:75;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ETSI-specific functional modes.
ZYEI;
5. Modify E1 functional modes of the ET with index 2.
ZYEC:ET,2:NORM,CRC4;

Example 25. Configuring PDH for TDM (ANSI standard /T1)

1. Interrogate the current configuration.


ZYAI:ET;
2. Set the interface operation mode of NIWU with index number 3 to T1.
ZYAE:NIWU,3,T1;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ANSI-specific functional modes.
ZYEH;
Modify T1 functional modes of the ET with index 2.
ZYEC:ET,2:ESF,B8Z2,0;

9.3 Creating routing objects for IWF/CDS-dedicated


TDM connections
This procedure describes how to divide TDM resources in a Multimedia
Gateway (MGW) for interconnecting TDM circuits for IWF functionality.
Interconnecting TDM resources are used to direct user plane traffic from an
MSC Server to MGW Rel.4 and to route CS data calls through the interworking
function (IWF) in MSC

6-108933Issue 1-0 © Nokia Oyj 84 (201)


User Plane Resource creation in MGW

Server or a standalone circuit switched data server (CDS). Dividing TDM


resources for this purpose entails first creating a special circuit group and then
adding TDM circuits to this group.

Note
The IWF/CDS-dedicated TDM circuits for data calls must not be attached to a
Virtual Media Gateway (VMGW). That is, the IWF/CDS-dedicated TDM
circuits for data calls must not be connected to circuit groups attached to a
VMGW and thus controlled directly by MSC Server, as the IWF/CDS-
dedicated circuit groups have to be available for all Virtual Media Gateways.

1. Create a special circuit group (SPE CGR) with the USE parameter (RCC)
ZRCC:TYPE=<circuit group type>,NCGR=<circuit group
name>, CGR=<circuit group number>,TYPE=SPE: USE=<use
of the SPE CGR>;
2. Add TDM circuits to the SPE CGR (RCA)
ZRCA:NCGR=<circuit group name>,CGR=<circuit group
number>: CRCT=<circuit(s)>;
3. Change the state of the circuit group to WO-EX (CIM)
ZCIM:(NCGR=<circuit group name>...|CGR=<circuit group
number>...):(WO|BA);
4. Change the state of the circuits to WO-EX (CIM)
ZCIM:CRCT=<circuit(s)>...:(WO|BA);

Example 26. Create routing objects for IWF/CDS-dedicated TDM connections

1. Create a special circuit group (CGR) with the USE parameter:


ZRCC:NCGR=IWF1,CGR=1,TYPE=SPE:USE=VMGW;
2. Add TDM circuits to the CGR:
ZRCA:NCGR=IWF1:CRCT=1-1&&-31;
3. Change the state of the circuit group to WO-EX:
ZCIM:CGR=1:WO;
4. Change the state of the circuits to WO-EX:
ZCIM:CRCT=1-1&&-31:WO;

6-108933Issue 1-0 © Nokia Oyj 85 (201)


User Plane Resource creation in MGW

9.4 Creating routing objects for TDM resources


controlled by MSC server
This procedure describes how to divide TDM resources in a multimedia
gateway (MGW). In other words, this enables you to dedicate TDM resources
of an MGW to different virtual gateways on one physical gateway element.
Dividing TDM resources in a virtual MGW entails first creating a special circuit
group (SPE CGR) with the USE parameter and then adding circuits to this SPE
CGR with 'VMGW' as the USE parameter.
TDM resources in MGW are configured to a Virtual MGW (VMGW) which is
connected to an MSC server over H.248. How these TDM resources are used
(PSTN/PLMN interface, A interface, interconnecting TDM connections etc.)
depends on the signalling attached to them in the MSC server. In digit analysis,
TDM resources are hunted by MSC Server. The TDM resources in an MGW
are divided for virtual MGWs so that resources controlled by each MSC Server
are in their own circuit groups. TDM circuits, which have different properties,
are also in separate circuit groups.

1. Create a special circuit group (SPE CGR) with the USE parameter (RCC)
ZRCC:TYPE=<circuit group type>,NCGR=<circuit group
name>, CGR=<circuit group number>,TYPE=SPE:USE=<use of
the SPE CGR>;

Note
In order to be able to use TDM resources they must be attached to a VMGW.
You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.
For more information on creating a VMGW, see Configuring H.248 control
protocol (MGW Rel.4 - MSC Server).

2. Add TDM circuits to the SPE CGR (RCA)


ZRCA:NCGR=<circuit group name>,CGR=<circuit group
number>: CRCT=<circuit(s)>;
3. Change the state of the circuit group to WO-EX (CIM)
ZCIM:(NCGR=<circuit group name>...|CGR=<circuit group
number>...):(WO|BA);

6-108933Issue 1-0 © Nokia Oyj 86 (201)


User Plane Resource creation in MGW

4. Change the state of the circuits to WO-EX (CIM)


ZCIM:CRCT=<circuit(s)>...:(WO|BA);
Note
The following CGR features can also be modified:
• POOLID
Different kind of user plane properities can be used by dividing circuits to
separate circuit groups and by attaching different User Plane Parameter sets to
those (POOLID). User Plane parameter sets can be defined with the W4-MML
commands. A new User Plane Parameter set can be attached to the CGR with
the RCM command:
ZRCM:CGR=<circuit group number>:POOLID=<POOLID number>;
• ECHO
The echo cancellation feature is needed in traffic between MGWand PSTN.
The echo parameter defines whenever the DSP resources are reserved for the
echo cancellation at the resource reservation phase. By setting the 'Y' value, it
guarantees that DSP resources will be available for the echo cancellation if this
is needed. Moreover, selecting the 'Y' value will also reserve the DSP resources
even when echo cancellation is not needed by the call; in this way, incorrect
configuration can limit the amount of calls that MGW can handle. Notice, also,
that the echo cancellation configurations of TDM circuits should be the same
both in MGWand in MSC Server.
If these configurations differ significantly, DSP capacity is wasted and
problems concerning echo may arise.
The echo parameter is set to the 'N' ('not in use') value by default. The value of
the echo parameter can be modified with the RCM command:
ZRCM:CGR=<circuit group number>:ECHO=<Y/N>;

Example 27. Create routing objects for TDM resources

1. Create a special circuit group (CGR) with the VMGW parameter.


ZRCC:NCGR=VMGW1,CGR=1,TYPE=SPE:USE=VMGW;

Note
In order to be able to use TDM resources they must be attached to a VMGW.
You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.

6-108933Issue 1-0 © Nokia Oyj 87 (201)


User Plane Resource creation in MGW

For more information on creating a VMGW, see Configuring H.248


control protocol (MGW Rel.4 - MSC Server).

2. Add TDM circuits to the CGR.


ZRCA:NCGR=VMGW1:CRCT=1-1&&-31;
3. Change the state of the circuit group to WO-EX.
ZCIM:CGR=1:WO;
4. Change the state of the circuits to WO-EX.
ZCIM:CRCT=1-1&&-31:WO;

9.5 Example: Creating interconnecting TDM


connections (MGW Rel.4 - MSC Server, MGW Rel.4 -
CDS)

1. Configure PDH for TDM transport


a. Interrogate the ET's current configuration (YAI)
ZYAI:ET;
b. Set the interface operation mode of NIWU (YAE)
ZYAE:NIWU,0,E1:120:;
c. Modify E1 functional modes (YEC)
ZYEC:ET,:NORM,DBLF:;
d. Modify T1 functional modes (YEG)
ZYEG:ET,:SF,AMI,15:;
2. Create routing objects for IWF/CDS-dedicated TDM connections
a. Create a special circuit group (SPE CGR) with the USE parameter
(RCC)
ZRCC:TYPE=SPE,NCGR=IWF1,CGR=1:USE=VMGW:;
b. Add TDM circuits to the SPE CGR (RCA)
ZRCA:NCGR=IWF1:CRCT=1-1&&-31:;
c. Change the state of the circuit group to WO-EX (CIM)
ZCIM:CGR=1:WO:;
d. Change the state of the circuits to WO-EX (CIM)
ZCIM:CRCT=1-1&&-31:WO:;
3. Create routing objects for TDM resources controlled by MSC server
a. Create a special circuit group (SPE CGR) with the USE parameter
(RCC)
ZRCC:TYPE=SPE,NCGR=VMGW6,CGR=2:USE=VMGW:;
Note

6-108933Issue 1-0 © Nokia Oyj 88 (201)


User Plane Resource creation in MGW

In order to be able to use TDM resources they must be attached to a VMGW.


You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.
a. Add TDM circuits to the SPE CGR (RCA)
ZRCA:NCGR=VMGW6:CRCT=2-1&&-31:;
b. Change the state of the circuit group to WO-EX (CIM)
ZCIM:CGR=2:WO:;
c. Change the state of the circuits to WO-EX (CIM)
ZCIM:CRCT=2-1&&-31:WO:;

6-108933Issue 1-0 © Nokia Oyj 89 (201)


User Plane Resource creation in MGW

10 Configuring IP for interface control


connections (MGW Rel.4 - MSS, MGW
Rel.4 - CDS)

10.1 Configuring IP for control plane (MGW Rel.4 _


MSC server/CDS)
The IP connection for control plane traffic between MGW Rel.4 and the MSC
server or the CDS must be configured during integration. The protocols used
between MGW Rel.4 and the MSC server are H.248, SIGTRAN and IWF
control. The protocol used between MGW Rel.4 and the CDS is IWF control.
Control plane traffic is transported via the NIS1 or IP-NIU network interface
unit. The IPFE/IPFEP/IPGE/IPGEP/IPGO/IPGOP unit (IP-NIU) is used for
Ethernet connections to IP backbone.
Both control plane and user plane traffic can be routed via the IPFE, IPGE or
IPGO unit using either 100 Mbps or 1G Ethernet interfaces. If 1G Ethernet
interfaces are used, it is not possible to separate control plane traffic into its own
physical interface via IP-NIU.
If you want to separate control plane traffic from user plane traffic, it is possible
to use the Ethernet interfaces of ISU units. In this case, control plane is
connected to site router/switch using two ESA12 internal Ethernet switches.

Before you start


The internal connections must be configured before external ones. If you want
to isolate SIGTRAN, H.248, IWF control and O&M traffic from user plane
traffic, you must first configure the ISU unit and the ESA12 switch. Refer to
instructions in Configuring IP stack in functional units of MGW
Rel.4 and Configuring ESA12.

6-108933Issue 1-0 © Nokia Oyj 90 (201)


User Plane Resource creation in MGW

1. If you want to isolate SIGTRAN, H.248, IWF control and O&M traffic
from user plane traffic then: Connect ESA12 switch to
external network Refer to instructions in Connecting to O&M
backbone via Ethernet.
2. If you do not want to isolate SIGTRAN, H.248, IWF control and O&M
traffic from user plane traffic then: Configure IP-NIU for
external connections Configure the connection to MSC Server
or CDS using Ethernet interfaces of the
IPFE/IPFEP/IPGE/IPGEP/IPGO/IPGOP unit. Refer to instructions in
Connecting to external network via IP-NIU.

10.2 Configuring H.248 control protocol (MGW Rel.4


-MSC Server)
The H.248 control protocol is used in the Mc interface between MGW Rel.4
and MSC Server. MSC Server controls the user plane terminations and contexts
in MGW Rel.4 via the Mc interface. This procedure provides instructions on
how to configure the H.248 control protocol between MGW Rel.4 and MSC
Server.

Note
The H.248 control protocol has to be configured separately for each ISU unit.

1. Assign IP address to network interface (QRN, Q6N)


• In IPv4, give the command
ZQRN:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>: [<IP address>],
[<IP address type> ]:[<netmask length>]:[<destination
IP address>]:[<MTU>]: [<state>];
• In IPv6, give the command
ZQ6N:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>: [<IP address>],
[<IP address type>]:[<prefix length>]:[<destination IP
address>]:[<MTU>]: [<state>];
2. Create Virtual Media Gateway (JVC)
A maximum of five Virtual Media Gateways (VMGW) can be configured
into one ISU unit.

6-108933Issue 1-0 © Nokia Oyj 91 (201)


User Plane Resource creation in MGW

Note
The MSC Server IP addresses (primary and secondary) that are specified to a
particular Virtual Media Gateway must always be located within the same
physical MSC Server network element. However, the different Virtual Media
Gateways of one Multimedia Gateway network element can be connected to
various physical MSC Server network elements.
ZJVC:(VMN=<virtual MGW name>,UINX=<ISU-unit>): (OIP=<own IP
address>,| ODN=<own domain name>,) OPN=<own port number>:
[CGR=<internal circuit group number>, A2T=<analysis tree
number for AAL2>]: [TTY=<transport type> | 1 def,
CTY=<coding type> | 0 def]: [PIP=<primary MSC server IP
address>, | PDN=<primary MSC server domain name>]:
[SIP=<secondary MSC server IP address>, | SDN=<secondary
MSC server domain name>]: [DUR=<duration> | 1 minute def];

Note
The JVC command can be used to specify only one secondary MSC Server IP
address.

3. Modify Virtual Media Gateway (JVM)


If there is a need to specify more than one secondary MSC Server IP
address, use theJVM command. Note that a maximum of 5 secondary
MSC Server IP addresses can be configured into one Virtual Media
Gateway.

Note
The MSC Server IP addresses (primary and secondary) that are specified to a
particular Virtual Media Gateway must always be located within the same
physical MSC Server network element. However, the different Virtual Media
Gateways of one Multimedia Gateway network element can be connected to
various physical MSC Server network elements.
When adding the secondary MSC Server addresses with the JVM command, the
default parameter values can be used for following parameters: internal circuit
group number (CGR), analysis tree number for AAL2 (A2T), transport type
(TTY), coding type (CTY), and duration (DUR).
ZJVM:(VID=<virtual MGW id>, VMN=<virtual MGW name>):
(CGR=<internal circuit group number>, A2T=<analysis tree
number for AAL2>: TTY=<transport type>, CTY=<coding type>:
[PIP=<primary MSC server IP address>, | PDN=<primary MSC
server domain name>]: SNUM=<secondary MSC server number>,
[SIP=<secondary MSC server IP address>, | SDN=<secondary
MSC server domain name>]: DUR=<duration>);

6-108933Issue 1-0 © Nokia Oyj 92 (201)


User Plane Resource creation in MGW

4. Register Virtual Media Gateway (JVR)


ZJVR:(VID=<virtual mgw id>..., | VMN=<virtual mgw
name>): [REGA=<registration allowed> | 0 def,
MET=<method> | 0 def, DEL=<delay>];
5. Interrogate Virtual Media Gateway (JVI)
Use the JVI command to interrogate the Virtual Media Gateway data.
The H.248 control protocol connection is active when the Virtual Media
Gateway registration status is 'registration allowed'.
ZJVI: (VID=<virtual mgw id>..., | VMN=<virtual mgw
name>);
Expected outcome
After successful assignment of the IP address to network interface, the system
outputs an execution printout indicating that the specified IP address has been
created.
After successful creation of the Virtual Media Gateway, the system outputs an
execution printout indicating that the specified Virtual Media Gateway has been
created.
After successful registration of the Virtual Media Gateway, the system outputs
an execution printout indicating that the specified Virtual Media Gateway has
been registered to the primary/secondary MSC Server.
Unexpected outcome
If an error occurs when assigning the IP address to network interface, the
system outputs an error-specific execution error message. The network interface
can be modified and the IP address can be removed by using the QRN
command.
If an error occurs when creating the Virtual Media Gateway, the system outputs
a general MML execution error message. The Virtual Media Gateway can be
modified by using the JVM command and it can be deleted by using the JVD
command.
If an error occurs when registering the Virtual Media Gateway, the system
outputs a general MML execution error message. The registration information
of the Virtual Media Gateway can be updated by using the JVR command.

Example 48. Configuring H.248 control protocol with IPv4

1. Assign a logical IP address 10.33.1.19 to the network interface el0 of ISU-0.


ZQRN:ISU,0:EL0:10.33.1.19,L:24:::UP;
2. Create a Virtual Media Gateway named OULU1, with ISU-unit 0, own IP address 10.33.1.19,
own port number 8009, internal circuit group number 1 and AAL2 analysis tree number 55. The
transport type is TCP (TTY=1), coding type is ASN.1 (CTY=0), primary MSC Server IP address
is 172.23.69.20, secondary MSC Server address is 172.23.69.21 and the duration time before a
new registration is started is one minute.
ZJVC:VMN=OULU1,UINX=0:OIP="10.33.1.19",OPN=8009:

6-108933Issue 1-0 © Nokia Oyj 93 (201)


User Plane Resource creation in MGW

CGR=1,A2T=55:TTY=1,CTY=0:PIP="172.23.69.20":
SIP="172.23.69.21":DUR=00-01-00;
3. Add two additional secondary MSC Server IP addresses into the Virtual Media Gateway named
OULU1.
ZJVM:VMN=OULU1::::SNUM=2,SIP="172.23.69.22",SNUM=3,SIP="172.23.69.23";
4. Register the Virtual Media Gateway named OULU1.
ZJVR:VMN=OULU1:REGA=1;
5. Interrogate Virtual Media Gateway data for Virtual Media Gateway named OULU1.
ZJVI:VMN=OULU1;

Example 49. Configuring H.248 control protocol with IPv6

1. Assign a logical IP address 2001:0490:0FF0:0010:0000:0000:0001:0020 to the network


interface el0 of ISU-0.
ZQRN:ISU,0:EL0:"2001:0490:0FF0:0010:0000:0000:0001:0020",L:24:::UP;
2. Create a Virtual Media Gateway named OULU1, with ISU-unit 0, own IP address
2001:0490:0FF0:0010:0000:0000:0001:0020, own port number 8009, internal circuit group
number 1 and AAL2 analysis tree number 55.
The transport type is TCP (TTY=1), coding type is ASN.1 (CTY=0), primary MSC Server IP address is
2001:490:FF0:5::68:60, secondary MSC Server address is 2001:490:FF0:5::68:61 and the duration time
before a new registration is started is one minute.
ZJVC:VMN=OULU1,UINX=0:
OIP="2001:0490:0FF0:0010:0000:0000:0001:0020",
OPN=8009:CGR=1,A2T=55:TTY=1,CTY=0:PIP="2001:490:
FF0:5::68:60":SIP="2001:490:FF0:5::68:61":DUR=00-01-00;
3. Add two additional secondary MSC Server IP addresses into the Virtual Media Gateway named
OULU1.
ZJVM:VMN=OULU1::::SNUM=2,SIP="2001:490:
FF0:5::68:62",SNUM=3,SIP="2001:490:FF0:5::68:63";
4. Register the Virtual Media Gateway named OULU1.
ZJVR:VMN=OULU1:REGA=1;
5. Interrogate Virtual Media Gateway data for Virtual Media Gateway named OULU1.
ZJVI:VMN=OULU1;

10.3 Configuring IWF/CDS control protocol (MGW


Rel.4_ IWF/CDS)
The IWF/CDS control protocol is used to control the process in which circuit-
switched data from the A or Iu-CS interface is routed through the interworking
function (IWF) towards the existing fixed networks. IWF is used to convert the
userplane data format used in GSM and UMTS circuit-switched data calls so
that it can be used in the the existing fixed networks.

6-108933Issue 1-0 © Nokia Oyj 94 (201)


User Plane Resource creation in MGW

Depending on the call case, the IWF is controlled either by MSC Server
internally or by Multimedia Gateway Rel.4 over TCP/IP connection. The IWF
control interface between MGW Rel.4 and MSC Server enables IWF to be
located basically in any MSC Server. It also makes it possible to detach IWF
from MSC Server to a standalone element called Circuit-switched Data Server
(CDS).
The IWF/CDS control interface is based on a client-server model. MGW Rel.4
acts as the client and IWF/CDS acts as the server. This procedure provides
instructions on how to configure the IWF/CDS control interface in MGW Rel.4.

1. Add IWF entry (JCA)


ZJCA:UINX=<ISU unit ID>, PRIO=<IWF address priority>:
ADDR=<IWF IP address>, PORT=<IWF IP port>;
Expected outcome
After successful addition of the IWF entry, the system outputs an execution
printout indicating that the new IWF entry has been added.
Unexpected outcome
If an error occurs when adding the IWF entry, the system outputs a semantic/
execution error message. The IWF entry can be modified by using the
JCNcommand it can be deleted by using the JCD command.
Verification
The JCI command can be used to verify that the IWF entry has been created
successfully.

ZJCI:[UINX=<ISU unit ID>... ,PRIO=<IWF address


priority>...];

Example 50. Configuring IWF/CDS control protocol (using IPv4)

1. Add a new IWF priority entry whose ISU unit ID is 0, IWF address priority is 1, IWF IP address
version 4 is 123.124.125.126 and IWF IP port is 8014.
ZJCA:UINX=0,PRIO=1:ADDR="123.124.125.126", PORT=8014;
2. Interrogate the IWF priority list with ISU unit ID 0.
ZJCI:UINX=0;

The value of the AVAIL (availability) column in the execution printout indicates the availability of the
connection:

6-108933Issue 1-0 © Nokia Oyj 95 (201)


User Plane Resource creation in MGW

Example 51. Configuring IWF/CDS control protocol (using IPv6)

1. Add a new IWF priority entry whose ISU unit ID is 0, IWF address priority is 1, IWF IP address
version 6 is FA34.AC67.FF33.
ABCD.1234.57CA.32BC.4DB2 and IWF IP port is 8014.
ZJCA:UINX=0,PRIO=1:ADDR="FA34:AC67:FF33:
ABCD:1234:57CA:32BC:4DB2",PORT=8014;
2. Interrogate the IWF priority list with ISU unit ID 0.
ZJCI:UINX=0;
The value of the AVAIL (availability) column in the execution printout
indicates the availability of the connection:

6-108933Issue 1-0 © Nokia Oyj 96 (201)


User Plane Resource creation in MGW

11 Creating Iu-CS interface (MGW Rel.4 -


RNC)

11.1 Configuring PDH for ATM transport


This procedure describes how you can configure PDH/ATM interface for the
NIP1 interface unit. The mode of the PDH interface must be the same for all the
exchange terminals 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.
When you have configured new PETs, 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.
Note
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 start


You must have created a functional unit description for the exchange terminals
(PET). For the instructions, refer to Creating and attaching functional unit in
Hardware Configuration Management.

1. Interrogate the PET's current configuration (YAI)


ZYAI:PET;

6-108933Issue 1-0 © Nokia Oyj 97 (201)


User Plane Resource creation in MGW

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. See the instructions in
Restarting functional unit in Recovery and Unit Working State
Administration.
3. Modify E1 functional modes if needed (YEC)
You can first output the ETSI specific frame modes with the command
ZYEI;
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 the command
ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);
Note
Double framing does not support SSM. For more information, see Configuring
synchronisation inputs in Synchronisation and Timing.
4. Modify T1 functional modes if needed (YEG)
You can output the ANSI specific T1 functional modes with the
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 the command
ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|
7.5|15|22.5);
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 interrogate PET timeslot usage with the command
ZYAW:<PET index>...:<timeslot number>...,[ON|OFFdef];
7. Create an IMA group, if necessary
If you want to use more than one transmission line, you must create an
IMA group for the physical links. Refer to instructions in Creating IMA
group.
8. Create physical layer Trail Termination Point
Refer to instructions in Creating PhyTTP.

6-108933Issue 1-0 © Nokia Oyj 98 (201)


User Plane Resource creation in MGW

Example 28. 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;
3. Modify the frame alignment mode of the T1 PET with index 2.
ZYEG:PET,2:ESF,B8ZS,0;
4. Configure PETs with indexes between 15 and 20. Disable scrambling and use S a bit number 7 as
a Syncronization Status Message bit.
ZYAM:PET,15&&20:OFF::7;
5. Create a phyTTP with ID 1 of PET with index 10.
ZYDC:1:PET=10;

11.2 Creating IMA group


This procedure describes how you can create an IMA group and add exchange
terminals 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
transmission 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 lines 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.

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

Before you start


You must 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
WFI command.
Each PET is identified by its exchange terminal index, which is a system-
wideunique numerical value. In addition, the system assigns a link ID to each
PET.

6-108933Issue 1-0 © Nokia Oyj 99 (201)


User Plane Resource creation in MGW

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

1. Create IMA group (YBC)


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

Note
If the IMA group is already tied up to an ATM interface, define the minimum
number of links parameter so that the IMA group capacity equals or is greater
than the used capacity of the ATM interface. For more information, see
Creating VP or VC level connection fails.

2. Add other PETs to the IMA group (YBA)


The exchange terminal to be added must belong to the same NIP1
functional unit as the IMA group. It must not be grouped to any other
IMA group or to a phyTTP.
ZYBA:<IMA group id>:<PET index>;

The maximum number of PETs in the group is 8.


3. Create phyTTP for the IMA group
See the instructions in Creating phyTTP.
Further information
You can interrogate IMA groups with the YBI command, modify with the YBM
command, and delete with the YBD command. It is possible to remove
exchange terminals from IMA group with the YBR command.

Example 29. 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;
3. Create phyTTP for the IMA group.
ZYDC:2:IMA=3;

6-108933Issue 1-0 © Nokia Oyj 100 (201)


User Plane Resource creation in MGW

11.3 Configuring SDH for ATM transport


You can configure SDH interfaces and modify the SDH exchange terminal
(SET) configuration.

Before you start


You must have created the functional unit description for the SETs. For the
instructions, see Creating and attaching functional unit in Hardware
Configuration Management.

1. Interrogate the SET (YAI)


With this command you can find out if the configured network interface
unit is NIS0 (STM-0) or NIS1 (STM-1).
ZYAI:<SET>,<SET index>;
2. Configure the SET (YAN)
ZYAN:<SDH exchange terminal index>...:[<SES BIP
threshold>]:[<SD BER threshold>]:[<SF BER threshold>]:
[DIA=(ON|OFF)|LINE=(ON|OFF)|LASER=(ON| OFF)]...:[VC3|
VC4]:[SDH|ATMML|SONET];

Note
This step is only necessary if you want to modify the default settings.

3. Set the SDH trace (YAS)


You can set the SDH trace already during integration or later on, if
necessary.
ZYAS:<SET index>,[<VC path number>]:(OUTPATH| EXPPATH|
OUTREG|EXPREG),(RESET|SET1|SET16|SET64), <trace
value>;
4. Create SDH protection group, if necessary
If you want to secure traffic even when a line fails, you need to create an
SDH protection group. Refer to instructions in Creating SDH protection
group.
5. Create phyTTP
Refer to instructions in Creating PhyTTP.
Further information:
You can interrogate the incoming SDH traces with the YAT command.

6-108933Issue 1-0 © Nokia Oyj 101 (201)


User Plane Resource creation in MGW

Example 30. Configuring SDH for ATM transport

1. Modify the SES BIP threshold of the SET 1 to 2300 frames per second. Enable line loopback.
ZYAN:1:2300:::LINE=ON;
2. Modify the outgoing path trace of the VC path 2 of SET 1. Use 16 byte format.
ZYAS:1,2:OUTPATH,SET16,"OUT PATH TRACE";
3. Create SDH protection group.
See the instructions in Creating SDH protection group.

11.4 Creating SDH protection group


You can create a protection group of SDH exchange terminals. The supported
protocols are optimised and compatible Multiplex Section Protection (MSP)
1+1. Multiplex Section 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 required level. Two SDH exchange terminals
can be added to the protection group.

Note
You cannot freely choose the protected pair in NIS0P. The first SET in the unit
is protecting also the second unit's first SET, the second SET is protecting the
second unit's second SET, and so on.

Steps

1. Create SDH protection group (YWC)


Note
The MSP compatible with 1:n protocol is supported only by the NIS1/P units.
The NIS0 unit does not support MSP 1+1.
ZYWC:[<protection group id>|<system select> def], [OPT| COM
def]:<Section 1 SDH exchange terminal index>,<Section 2 SDH
exchange terminal index>:[<wait to restore time>|<default>
def];
2. Create phyTTP
See the instructions for creating the physical layer Trail Termination
Point in Creating phyTTP.
Expected outcome
The system generates the 0101 SHD PROTECTION SWITCHING
EXECUTED notice if the protection switch operation succeeds.

6-108933Issue 1-0 © Nokia Oyj 102 (201)


User Plane Resource creation in MGW

Unexpected outcome
The system generates the 3183 SDH PROTECTION SWITCHING FAILED
alarm if the protection switch operation fails.
Further information
You can interrogate the protection group configuration with the YWI command,
modify the configuration with the YWM command and delete the configuration
with the YWD command.

Example 31. Configuring SDH protection group

Create a protection group of SET 7 (section 1) and SET 4 (section 2) with


protection group ID 3 and with 10 minutes (600 seconds) restore time.
ZYWC:3:7,4:600;

11.5 Creating phyTTP


The 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 interface.
You can create a phyTTP for a single PET, an IMA group, a single SDH VC
path, or a VC path of an SDH protection group.

Note
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 start


You must have configured 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, use the YDI
command.

1. Create physical layer Trail Termination Point (YDC)


If you created an IMA group, give the ID of the IMA group to the IMA

6-108933Issue 1-0 © Nokia Oyj 103 (201)


User Plane Resource creation in MGW

parameter. If you created an SDH protection group, give the ID of the


protection group to the PROTGROUP parameter.
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];

Note
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.

Further information
You can delete a phyTTP with the YDD command. After the deletion its
physical resources are free to be used for another phyTTP. The phyTTP cannot
be deleted if it is used by the upper layer, that is, if there is an ATM created to
it. You can use the YDI command to check whether the phyTTP is in use or not.

Example 32. Creating phyTTP for a SET

Create a phyTTP with ID 1 of SET with index 0 and VC path number 1.


ZYDC:1:SET=0:1:;

Example 33. Creating phyTTP for a PET

Create a phyTTP with ID 1 of PET with index 10.


ZYDC:1:PET=10;

Example 34. Creating phyTTP for an IMA group

Create a phyTTP with ID 2 of IMA with index 20.


ZYDC:2:IMA=20;

11.6 Creating ATM resources for Iu_CS interface


This procedure describes creating ATM resources for the Iu-CS interface.
Configure the hardware (including exchange terminals) and the physical
resources. See Physical interfaces in IP/ATM network.

6-108933Issue 1-0 © Nokia Oyj 104 (201)


User Plane Resource creation in MGW

For creating the access profile, see the information on VPI bits and VCI bits.

Caution
When defining traffic parameter values, take into account the capacity
limitations of a single ATM interface. If the resources are misconfigured, the
system will reject the creating of VP/VC connections later. See also
Reserving ATM resources fails.

1. Create an ATM interface tied up to a physical layer Trail Termination


Point (LAC)
ZLAC:<interface id>:<interface type>,<phyTTP>;

Table 9. Parameters and values for creating an ATM interface tied up to a


physical layer Trail Termination Point

2. Create the access profile of the ATM interface (LAF)


ZLAF:<interface id>:<max VPI bits>:<max VCI bits>;

Table 10. Parameters and values for creating the access profile of the ATM
Interface

6-108933Issue 1-0 © Nokia Oyj 105 (201)


User Plane Resource creation in MGW

3. Create a VPLtp for O&M (UBR) traffic if needed (LCC)


Depending on how the operation & maintenance network is planned, you
may need to create a separate external VPLtp for O&M traffic (IP over
ATM connection of UBR type).
ZLCC:<interface id>, <tp type>, <VPI>,,<VPL service
level>:<segment endpoint info>,<VP level traffic
shaping>::<egress service category>,,,<egress QOS
class>:;

Table 11 Parameters and values for creating a VPLtp for O&M (UBR) traffic

4. Create VPLtps for CBR traffic (LCC)


Create a necessary number o f VPLtps for SS7 signalling and routing
AAL2 user data.
ZLCC:<interface id>, <tp type>, <VPI>,,<VPL service
level>:<segment end point info>,<VP level traffic

6-108933Issue 1-0 © Nokia Oyj 106 (201)


User Plane Resource creation in MGW

shaping>::<egress service category>,,,<egress QOS


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

Table 12. Parameters and values for creating VPLtps for CBR traffic

5. Create a VCLtp for O&M (UBR) connection if needed (LCC)


Depending on how the operation & maintenance network is planned, you
may need to create an external VCLtp for O&M traffic (IP over ATM
connection of UBR type) under VPLtp (for UBR traffic):
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>;

6-108933Issue 1-0 © Nokia Oyj 107 (201)


User Plane Resource creation in MGW

Table 13. Parameters and values for creating VCLtp for O&M (UBR) connection

6. Create VCLtps for signalling (CBR traffic) (LCC)


Create a necessary number of VCLtps for SS7 signalling (MTP3SL)
under the VPLtp(s) for CBR traffic.
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>;

6-108933Issue 1-0 © Nokia Oyj 108 (201)


User Plane Resource creation in MGW

Table 14. Parameters and values for creating VCLtps for signalling (CBR traffic)

7. Create VCLtps for routing (CBR traffic) (LCC)


Create a necessary number of VCLtps for routing (for AAL2 user data,
AAL2UD) under the VPLtp(s) for CBR traffic:
ZLCC:<interface id>,<tp type>,<VPI>,<VCI>::<ingress
service category>,,,<ingress QOS class>:<egress
service category>,,,<egress QOS class>::<ingress
PCR>,<ingress PCR unit>:<egress PCR>,<egress PCR
unit>;

Table 15. Parameters and values for creating VCLtps for routing (CBR traffic)

6-108933Issue 1-0 © Nokia Oyj 109 (201)


User Plane Resource creation in MGW

11.7 Creating remote MTP configuration


In most cases the MTP needs to be configured to the network element. Before
configuring 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.
• A interface, between MGWand BSC. The configuration is based on
TDM.
• PSTN/PLMN interface, between MGW and PSTN/PLMN. The
configuration is based on TDM.
• Iu-CS interface, between MGW and RNC. The configuration is based on
ATM.
• Nb interface, between MGW and MGW. The configuration is based on
ATM.
• 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.
• Iu-PS interface, between RNC and SGSN. The configuration is based on
ATM.
• To configure IP signalling between MGW and MSS, see instructions in
Creating IP signalling configuration
Before you start
Before you start to create signalling links, check that the SS7 services and own
MTP signalling point have been created. For instructions, see Creating local
signalling configuration for MGW Rel.4.

1. Check that the signalling links are distributed evenly between different
ISUs. Use the following command to display the existing signalling links.
ZNCI;
It is recommended that you allocate signalling links between all working
ISU units to distribute the load. Also, it is very important that signalling
links belonging to the same linkset are allocated to different ISU units to
avoid the whole linkset to become unavailable in an ISU switchover.
2. Create signalling links (NCN/NCS)
To create TDM signalling links, give the command
ZNCN:<signalling link number>:<external interface PCM-
TSL>,<link bit rate>:ISU,<unit number>: <parameter set
number>;

To create ATM signalling links, give the command


ZNCS:<signalling link number>:<external interface id

6-108933Issue 1-0 © Nokia Oyj 110 (201)


User Plane Resource creation in MGW

number>,<external VPI-VCI>:<unit type>,<unit


number>:<parameter set number>;

Note
Before creating ATM signalling links, check that there are free VCLtps
available and that they are correctly configured. For instructions, see Create
VCLtps for signalling
Remember to check by using the WFI command that the network element is
adequately equipped before you start creating signalling links. 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. The
parameter set related to the signalling link can be used to handle several of the
signalling link timers and functions. If the ready-made parameter packages do
not cover all occurring situations, you can create more parameter sets, modify
the relevant parameters and then attach thenew 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. Here are two
examples of special situations in TDM signalling links that 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.

Note
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.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and 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 link.

3. Create SS7 signalling link set (NSC)


Create a signalling link set for each destination.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 signalling route set.
You can reserve several 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>,

6-108933Issue 1-0 © Nokia Oyj 111 (201)


User Plane Resource creation in MGW

<signalling link set name>:<signalling link number>,


<signalling link code>,<signalling link priority>;

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 (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
and related matters such as A interface used between the MGW Rel.4 and
MSC. 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 Signallingroute 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. 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>:<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).

Note
Notice that 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.

Note
The parameters load sharing status and restriction status
are not necessary during MGW Rel.4 integration.

11.8 Activating MTP configuration

6-108933Issue 1-0 © Nokia Oyj 112 (201)


User Plane Resource creation in MGW

1. 1. Allow activation of the signalling links (NLA)


Use the following command to allow the activation of 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 in


case 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. To
interrogate the states of signalling links, use the commands NLI or NEL.

The activation procedure is the same even when you are creating an IP
connection. When you activate a 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 interrogate the
states of the associations, use the command OYI. For more information,
see Association set and associations.
3. Allow activation of the signalling routes (NVA)
Use the following command to allow the activation of 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;
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 state AV-EX if the related link set is active; otherwise it
assumes state UA-INS. A signalling route going through an STP can also
assume 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.

6-108933Issue 1-0 © Nokia Oyj 113 (201)


User Plane Resource creation in MGW

Example 35.

In this example, you change the state of a signalling route which is leading to
signalling point 302. The route is defined in signalling point 301 that is located
inthe 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:

After this, you use the NVC command to activate the route:
ZNVC:NA0,302::ACT;

The execution printout can be as follows:

11.8 Creating remote SCCP configuration


The 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 start

6-108933Issue 1-0 © Nokia Oyj 114 (201)


User Plane Resource creation in MGW

Check that the whole network has been carefully planned, all necessary
hardware has been installed on the network element and the Message Transfer
Part (MTP) has already been configured.
Examine the following things:
• Check that the signalling points have been created on the MTP (the NRI
command) and the services are available for the SCCP (the NPI
command).
• Check which parameter set is used, and whether there is need to modify the values of the
existing parameter sets to meet the present conditions andrequirements (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.

Before you can create the SCCP to the network element, the SCCP servicehas
to be created first. 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).

Note
SCCP management subsystem (SCMG) is automatically created when you
create SCCP for signalling point.
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).

1. Create remote SCCP signalling points and subsystems (NFD)

In addition to creating the own SCCP signalling point and its subsystems,
you also 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 later add more subsystems to a
signalling point by using the NFB command. The system may need new
subsystems for example when new services are installed, software is

6-108933Issue 1-0 © Nokia Oyj 115 (201)


User Plane Resource creation in MGW

upgraded or network 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. 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 signalling 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 alternative routes that will then be taken into service in case 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, OBM)

Note
This step is not necessary for MGW-PSTN/PLMN interface.

There are two different kind of broadcasts you can set (it is recommended that you set both of them):
The local broadcast status (the OBC command) is used to inform the subsystems of the own
signalling point about changes in the subsystems of the remote signalling points.
The broadcast status (the OBM command) is used to inform other signalling points about changes in
the subsystems of the own signalling point or thesubsystems of the signalling points connected to the
own signalling point. When you set local broadcasts, remember that also the remote network elements
have to be configured so that they send the status data to your network element.

6-108933Issue 1-0 © Nokia Oyj 116 (201)


User Plane Resource creation in MGW

Note
When setting the broadcasts, consider carefully what broadcasts are needed.
Incorrect or unnecessary broadcasts can cause problems and/or unnecessary
traffic in the signalling network.
Depending on the network element, the subsystems needing the
broadcastfunction are the following:
• BSSAP Base Station System Application Part
• RANAP Radio Access Network Application Part
• RNSAP Radio Network Subsystem Application Part

For example, the local BSSAP of the MSC has to know the status data of the
BSSAP located in the MGWs, and accordingly, the local BSSAP of the MGW
has to know the status data of the BSSAP in the MSC.
Local broadcasts:
ZOBC:<network of affected subsystem>,<signalling point code of affected
subsystem>,<affected subsystemnumber>:<network of local
subsystem>,<localsubsystem number>:<status>;
Remote broadcasts:
ZOBM:<network of affected subsystem>,<signalling point code of affected
subsystem>,<affected subsystem number>:<network of concerned signalling
point>,<concerned signalling point code>:<status>;

For more information, see SCCP level signalling network.

11.9 Activating SCCP configuration

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, only remote
SCCP signalling points have to be activated. To check that the signalling
point really is active, use the NFI command. In the command printout,
the state of signalling point should be AV-EX. If the signalling point
assumes state UA-INS, there is a fault on the MTPlevel. You can display

6-108933Issue 1-0 © Nokia Oyj 117 (201)


User Plane Resource creation in MGW

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

Example 36.

When you examine an example system using the NFI or NGI commands, all
signalling points should be in normal state AV-EX. Note that 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:

2. Activate remote SCCP subsystems (NHC)

ZNHC:<signalling network>, <signalling point


codes>:<subsystem>:ACT;

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

When remote subsystems are being activated, their status is not checked
from the remote node. The remote subsystem status becomes AV-EX if
theremote node is available, although the actual subsystem may be
unavailable or even missing. The status of the unavailable subsystem
willbe corrected with 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.


3. Set the SS7 network statistics, if needed

6-108933Issue 1-0 © Nokia Oyj 118 (201)


User Plane Resource creation in MGW

By setting SS7 network statistics you can monitor the performance of


SS7network. You do not have to do it in the integration phase but you
can do it later.

For more instructions, see SS7 signalling performance measurements.

11.10 Creating routing objects for lu interface in MGW


Rel.4
This 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.

Before you start


Before 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. Furthermore, the route
under which the endpoints are to be created must allow the type of the
endpoints.

1. Create an AAL2 route (RRC)

ZRRC:ROU=<route number>,TYPE=<route type>,


PRO=<protocol>:NET=<signalling network>,
SPC=<signalling point code>,ANI=<aal2 node
identifier>;
2. Create an endpoint group (LIC)

ZLIC:<route number>,<ep group index>:<ingress service


category>, <egress service category>;

The ingress and egress service categories should always be Constant Bit
Rate (CBR).
3. Check that there is a free VCLtp (LCI)

ZLCI:<interface id>,VC:<VPI>:FREE;

6-108933Issue 1-0 © Nokia Oyj 119 (201)


User Plane Resource creation in MGW

Out of these VCIs all those with service category CBR in both directions
can be used in the next step.
4. Create an endpoint (LJC)

ZLJC:<ep type>,<route number>,<connection id>:


<interface id>,<VPI>,<VCI>:<ownership>:[<loss
ratio>,<mux delay>];

The system will automatically assort this endpoint into the endpoint
group of step 2 since their service categories match.
5. 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 outcome
The 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.

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

Example 37. Create routing objects for Iu interface

1. Create an AAL2 route. The route number is 11, the protocol is Message Transfer part 3, the
signalling network is NA0, the signalling point code is701, and AAL2 node identifier is
AAL2MGW1.

ZRRC:ROU=11,TYPE=AAL2,PRO=MTP3:NET=NA0,SPC=701,
ANI=AAL2MGW1;
2. Create an endpoint group under route 11. The endpoint group id is automatically selected by the
system. The termination points in this group shall have the Constant Bit Rate service category
for both ingress and egress directions.

ZLIC:11:C,C;
3. Check that there is a free VCLtp.

ZLCI:<interface id>,VC:<VPI>:FREE;

Notice, 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 nextstep.

6-108933Issue 1-0 © Nokia Oyj 120 (201)


User Plane Resource creation in MGW

4. 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 AAL2 type 2 loss ratio is 10_4 and the AAL type 2
multiplexing delay 2ms.

ZLJC:VC,11,5:2,1,33:LOCAL:4,20;

The system will automatically assort this endpoint into the endpoint group of step 2 since their service
categories match.
5. Unblock the AAL type 2 path 11. The ANI is AAL2MGW1 and theallowed waiting time for the
execution of the blocking command is 18 seconds.

ZLSU:AAL2MGW1:11:18;

11.11 Example: Creating Iu-CS interface (MGW Rel.4 -


RNC)

1. Create phyTTP (YDC)


ZYDC:2:SET=1:1;
2. Create ATM resources for Iu-CS interface (LAC, LAF, LCC)
a. Create an ATM interface tied up to a physical layer Trail
Termination Point (LAC)
ZLAC:3:NNI,2;
b. Create the access profile of the ATM interface (LAF)
ZLAF:2:8:8;
c. Create VPLtps for CBR traffic (LCC)
ZLCC:2,VP,1,,VC:::C,,,C1:::150,KCPS:
STATE=UNLOCKED;
d. Create VCLtps for signalling and routing (CBR traffic) (LCC)
ZLCC:2,VC,1,32::C,E,E,C1:C,E,E,C1::300,CPS:300,CPS;
ZLCC:2,VC,1,33::C,,,C1:C,,,C1::15,KCPS:15,KCPS;

3. Create MTP configuration (NCS, NRC)


a. Create signalling links (NCS)
ZNCS:4:3,1-32:ISU,0:5;
b. Create ATM signalling link set (NCS)
ZNSC:NA0,311,RNC4:4,2;
c. Create signalling route set (NRC)
ZNRC:NA0,311,RNC4,0,,N:,,,7;
4. Activate MTP configuration (NLA, NLC, NVA, NVC)

6-108933Issue 1-0 © Nokia Oyj 121 (201)


User Plane Resource creation in MGW

a. Allow activation of the signalling links (NLA)


ZNLA:4;
b. Activate the signalling links (NLC)
ZNLC:4,ACT;
c. Allow activation of the signalling routes (NVA)
ZNVA:NA0,311;
d. Activate signalling routes (NVC)
ZNVC:NA0,311::ACT;
5. Create remote SCCP configuration (NFD, NAC)
a. Create remote SCCP signalling points and subsystems (NFD)
ZNFD:NA0,311,0:8E,RANAP,0,Y;
b. Create translation results (NAC)
ZNAC:NET=NA0,DPC=311,RI=SSN,SSN=8E;
6. Activate SCCP configuration (NGC, NHC)
a. Activate remote SCCP signalling points (NGC)
ZNGC:NA0,311:ACT;
b. Activate remote SCCP subsystems (NHC)
ZNHC:NA0,311:8E:ACT;
7. Create routing objects and digit analysis for Iu interface (RRC, LIC, LJC,
LSU, RDC)
a. Create an AAL2 route (RRC)
ZRRC:ROU=22,TYPE=AAL2:PRO=MTP3:NET=NA0,SPC=311,AN
I=AAL2RNC4;
b. Create an endpoint group (LIC)
ZLIC:22,1:C,C;
c. Create an endpoint (LJC)
ZLJC:VC,22,6:3,1,33:LOCAL:4,20;
d. Unblock the AAL type 2 path (LSU)
ZLSU:AAL2RNC4:6;

11.12 Creating semi-permanent cross-connections


through ATM network element
You can create a semi-permanent cross-connection either between two VPLtps
or between two VCLtps. Furthermore, you can also create a semi-permanent
cross- connection and one or both of the termination points at the same time.
The following case is an example of creating one semi-permanent cross-
connection between two VPLtps.

6-108933Issue 1-0 © Nokia Oyj 122 (201)


User Plane Resource creation in MGW

When you are creating a semi-permanent cross-connection between two


existing termination points, check first with the command LCI that the service
category and the traffic parameters of the termination points are not
contradictory with each other: tp2_ingress = tp1_egress and tp2_egress =
tp1_ingress. The system rejects the creation if these conditions are not fulfilled.
If you do not succeed with creating a cross-connection, check also that the
existing termination points take into account the capacity limitation of the ATM
interface, and that the parameter values are otherwise correct. For more
information, see Reserving ATM resources fails.

Before you start


The following gives an example of how to create a cross-connection between
two existing tps. There are other possibilities on VP and VC level not included
here.
For more examples, see LB - ATM Semi-permanent Cross-connection
Handling.

1. Create a cross-connection between two existing VP link termination


points (LBC)

This case describes what parameters need to be given to create a cross-


connection between two existing VP link termination points:
ZLBC:<cross connection level>,<connection topology>:<first
interface id>,[<first VPI>], [<first VCI>]:<second interface id>,
[<second VPI>], [<second VCI>];

6-108933Issue 1-0 © Nokia Oyj 123 (201)


User Plane Resource creation in MGW

12 Creating A interface (MGW Rel.4 - BSC)

12.1 Configuring PDH for TDM transport


This procedure describes how you can configure PDH/TDM for the NIWU
interface unit. The mode of the PDH interface must be the same for all the
exchange terminals (ET) in the plug-in unit. That is why the NIWU 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.
The network element provides a synchronisation interface for external timing
reference signals. For information on synchronisation, see Configuring
synchronisation inputs in Synchronisation and Timing.
When you have configured new ETs, you may have to modify their functional
modes. Choose either E1, ETSI specific functional modes, or T1, ANSI specific
functional modes. The default mode for PDH/TDM is E1.

Before you start


You must have created the functional unit description for the ETs. For the
instructions, see Creating and attaching functional unit in Hardware
Configuration Management.

1. Interrogate the ET's current configuration (YAI)


ZYAI:ET;
2. Set the interface operation mode of NIWU (YAE)

Set the operation mode if you want to change it from E1 to T1/JT1 or


from T1/JT1 to E1. The impedance parameter can be given only if the

6-108933Issue 1-0 © Nokia Oyj 124 (201)


User Plane Resource creation in MGW

operation mode given is E1.

ZYAE:NIWU,<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. See the instructions in
Restarting functional unit in Recovery and Unit Working State
Administration.
3. Modify E1 functional modes, if needed (YEC)

You can first output the ETSI specific frame modes with the command
ZYEI;

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 the command
ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);

Note
Double framing does not support SSM. For more information, see
Configuring synchronisation inputs in Synchronisation and Timing.
4. Modify T1 functional modes if needed (YEG)

You can first output the ANSI specific T1 functional modes with the
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 the command
ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|
7.5|15|22.5);

Example 38. Configuring PDH for TDM (ETSI standard /E1)

1. Interrogate the current configuration.


ZYAI:ET;
2. Set the interface operation mode of NIWU with index number 3 to E1 and with impedance 75 ©.
ZYAE:NIWU,3,E1:75;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ETSI-specific functional modes.
ZYEI;

6-108933Issue 1-0 © Nokia Oyj 125 (201)


User Plane Resource creation in MGW

5. Modify E1 functional modes of the ET with index 2.


ZYEC:ET,2:NORM,CRC4;

Example 39. Configuring PDH for TDM (ANSI standard /T1)

1. Interrogate the current configuration.


ZYAI:ET;
2. Set the interface operation mode of NIWU with index number 3 to T1.
ZYAE:NIWU,3,T1;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ANSI-specific functional modes.
ZYEH;
5. Modify T1 functional modes of the ET with index 2.
ZYEC:ET,2:ESF,B8Z2,0;

12.2 Creating remote MTP configuration


In most cases the MTP needs to be configured to the network element. Before
configuring 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.
• A interface, between MGWand BSC. The configuration is based on
TDM.
• PSTN/PLMN interface, between MGW and PSTN/PLMN. The
configuration is based on TDM.
• Iu-CS interface, between MGW and RNC. The configuration is based on
ATM.
• Nb interface, between MGW and MGW. The configuration is based on
ATM.
• 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.
• " Iu-PS interface, between RNC and SGSN. The configuration is based
on ATM.
• To configure IP signalling between MGW and MSS, see instructions in
Creating IP signalling configuration

6-108933Issue 1-0 © Nokia Oyj 126 (201)


User Plane Resource creation in MGW

Before you start


Before you start to create signalling links, check that the SS7 services and own
MTP signalling point have been created. For instructions, see Creating local
signalling configuration for MGW Rel.4.

1. Check that the signalling links are distributed evenly between different
ISUs
Use the following command to display the existing signalling links.
ZNCI;

It is recommended that you allocate signalling links between all working


ISU units to distribute the load. Also, it is very important that signalling
links belonging to the same linkset are allocated to different ISU units to
avoid the whole linkset to become unavailable in an ISU switchover.
2. Create signalling links (NCN/NCS)

To create TDM signalling links, give the command


ZNCN:<signalling link number>:<external interface PCM-
TSL>,<link bit rate>:ISU,<unit number>: <parameter set
number>;

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>;

Note
Before creating ATM signalling links, check that there are free VCLtps
available and that they are correctly configured. For instructions, see Create
VCLtps for signalling.
Remember to check by using the WFI command that the network element is
adequately equipped before you start creating signalling links.
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.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and functions. If the ready-made parameter packages
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 link. It is advisable to find out if there will be such special situations
before you start configuring the MTP. See Signalling link parameters.

6-108933Issue 1-0 © Nokia Oyj 127 (201)


User Plane Resource creation in MGW

Here are two examples of special situations in TDM signalling links that 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.

Note
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.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and functions. If the predefined parameter sets do not
cover all occurring situations, you can create moreparameter sets, modify the
relevant parameters and then attach the new parameter set to the signalling link.

3. Create SS7 signalling link set (NSC)

Create a signalling link set for each destination.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 signalling route set.
You can reserve several 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>,<signalling link priority>;

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 (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
and related matters such as A interface used between the MGW Rel.4 and
MSC. 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

6-108933Issue 1-0 © Nokia Oyj 128 (201)


User Plane Resource creation in MGW

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. 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>:<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).

Note
Notice that 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.

Note
The parameters load sharing status and restriction status
are not necessary during MGW Rel.4 integration.

12.3 Activating MTP configuration

1. Allow activation of the signalling links (NLA)


Use the following command to allow the activation of 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;

6-108933Issue 1-0 © Nokia Oyj 129 (201)


User Plane Resource creation in MGW

The signalling links assume either state AV-EX (active) or UA-INS in case 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.
To interrogate the states of signalling links, use the commands NLI or NEL.
The activation procedure is the same even when you are creating an IP
connection. When you activate a 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 interrogate the states of the associations, use the
command OYI. For more information, see Association set and associations.
3. Allow activation of the signalling routes (NVA)
Use the following command to allow the activation of 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>,<signaling
transfer point code>:ACT;
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 state AV-EX if the related link set is active; otherwise it
assumes state UA-INS. A signalling route going through an STP can also
assume 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 40.

In this example, you change the state of a signalling route which is leading to
signalling point 302. The route is defined in 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:

6-108933Issue 1-0 © Nokia Oyj 130 (201)


User Plane Resource creation in MGW

After this, you use the NVC command to activate the route:
ZNVC:NA0,302::ACT;
The execution printout can be as follows:

12.4 Creating remote SCCP configuration


The 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 start


Check that the whole network has been carefully planned, all necessary
hardware has been installed on the network element and the Message Transfer
Part (MTP) has already been configured.
Examine the following things:
• Check that the signalling points have been created on the MTP (the NRI
command) and the services are available for the SCCP (the NPI
command).
• Check which parameter set is used, and whether there is need to modify
the values of the existing parameter sets to meet the present conditions
and requirements (the OCI command).

6-108933Issue 1-0 © Nokia Oyj 131 (201)


User Plane Resource creation in MGW

• 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.
Before you can create the SCCP to the network element, the SCCP service has
to be created first. 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).

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

Note
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).

1. Create remote SCCP signalling points and subsystems (NFD)


In addition to creating the own SCCP signalling point and its subsystems,
you also 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 later add more subsystems to a signalling point by using the NFB
command. The system may need new subsystems for example when new
services are installed, software is upgraded or network 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. 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 signalling point.
At this stage you have to decide whether the routing is based on global

6-108933Issue 1-0 © Nokia Oyj 132 (201)


User Plane Resource creation in MGW

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 alternative routes that will then be taken into service in case 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, OBM)

Note
This step is not necessary for MGW-PSTN/PLMN interface.

There are two different kind of broadcasts you can set (it is recommended that
you set both of them):
1. The local broadcast status (the OBC command) is used to inform the
subsystems of the own signalling point about changes in the subsystems
of the remote signalling points.
2. The broadcast status (the OBM command) is used to inform other
signalling points about changes in the subsystems of the own signalling
point or the subsystems of the signalling points connected to the own
signalling point.
When you set local broadcasts, remember that also the remote network elements
have to be configured so that they send the status data to your network element.

Note
When setting the broadcasts, consider carefully what broadcasts are needed.
Incorrect 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:
• BSSAP Base Station System Application Part
• RANAP Radio Access Network Application Part

6-108933Issue 1-0 © Nokia Oyj 133 (201)


User Plane Resource creation in MGW

• RNSAP Radio Network Subsystem Application Part


For example, the local BSSAP of the MSC has to know the status data of the
BSSAP located in the MGWs, and accordingly, the local BSSAP of the MGW
has to know the status data of the BSSAP in the MSC.
Local broadcasts:
ZOBC:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of local subsystem>,<local subsystem number>:<status>;
Remote broadcasts:
ZOBM:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of concerned signalling point>, <concerned signalling point
code>:<status>;
For more information, see SCCP level signalling network.

12.5 Activating SCCP configuration

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, only remote
SCCP signalling points have to be activated. To check that the signalling
point really is active, use the NFI command.
In the command printout, the state of signalling point should be AV-EX.
If the signalling point assumes state UA-INS, there is a fault on the MTP
level. You can display the states of SCCP signalling points also by using
the command NGI. Notice that if you use the default values in the
command, only the signalling points of network NA0 are shown. For
more information, see States of SCCP signalling points.

Example 41.

When you examine an example system using the NFI or NGI commands, all
signalling points should be in normal state AV-EX. Note that 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:

6-108933Issue 1-0 © Nokia Oyj 134 (201)


User Plane Resource creation in MGW

2. Activate remote SCCP subsystems (NHC)


ZNHC:<signalling network>, <signalling point codes>:
<subsystem>:ACT;
To display the subsystem states, use the NHI or NFJ command.
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 available, although the actual subsystem may be
unavailable or even missing. The status of the unavailable subsystem will
be corrected with 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.
3. Set the SS7 network statistics, if needed
By setting SS7 network statistics you can monitor the performance of
SS7 network. You do not have to do it in the integration phase but you
can do it later.
For more instructions, see SS7 signalling performance measurements.

12.6 Creating routing objects for TDM resources


controlled by MSC server
This procedure describes how to divide TDM resources in a multimedia
gateway (MGW). In other words, this enables you to dedicate TDM resources
of an MGW to different virtual gateways on one physical gateway element.
Dividing TDM resources in a virtual MGW entails first creating a special circuit
group (SPE CGR) with the USE parameter and then adding circuits to this SPE
CGR with 'VMGW' as the USE parameter.

6-108933Issue 1-0 © Nokia Oyj 135 (201)


User Plane Resource creation in MGW

TDM resources in MGW are configured to a Virtual MGW (VMGW) which is


connected to an MSC server over H.248. How these TDM resources are used
(PSTN/PLMN interface, A interface, interconnecting TDM connections etc.)
depends on the signalling attached to them in the MSC server. In digit analysis,
TDM resources are hunted by MSC Server. The TDM resources in an MGW
are divided for virtual MGWs so that resources controlled by each MSC Server
are in their own circuit groups. TDM circuits, which have different properties,
are also in separate circuit groups.

1. Create a special circuit group (SPE CGR) with the USE parameter (RCC)
ZRCC:TYPE=<circuit group type>,NCGR=<circuit group
name>, CGR=<circuit group number>,TYPE=SPE:USE=<use of
the SPE CGR>;

Note
In order to be able to use TDM resources they must be attached to a VMGW.
You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.
For more information on creating a VMGW, see Configuring H.248 control
protocol (MGW Rel.4 - MSC Server).

2. Add TDM circuits to the SPE CGR (RCA)


ZRCA:NCGR=<circuit group name>,CGR=<circuit group
number>: CRCT=<circuit(s)>;
3. Change the state of the circuit group to WO-EX (CIM)
ZCIM:(NCGR=<circuit group name>...|CGR=<circuit group
number>...):(WO|BA);
4. Change the state of the circuits to WO-EX (CIM)
ZCIM:CRCT=<circuit(s)>...:(WO|BA);

Note
The following CGR features can also be modified:
• POOLID
Different kind of user plane properities can be used by dividing circuits to
separate circuit groups and by attaching different User Plane Parameter sets to
those (POOLID). User Plane parameter sets can be defined with the W4-MML

6-108933Issue 1-0 © Nokia Oyj 136 (201)


User Plane Resource creation in MGW

commands.
A new User Plane Parameter set can be attached to the CGR with the RCM
command:
ZRCM:CGR=<circuit group number>:POOLID=<POOLID number>;

• ECHO
The echo cancellation feature is needed in traffic between MGWand PSTN.
The echo parameter defines whenever the DSP resources are reserved for the
echo cancellation at the resource reservation phase. By setting the 'Y' value, it
guarantees that DSP resources will be available for the echo cancellation if this
is needed. Moreover, selecting the 'Y' value will also reserve the DSP resources
even when echo cancellation is not needed by the call; in this way, incorrect
configuration can limit the amount of calls that MGW can handle. Notice, also,
that the echo cancellation configurations of TDM circuits should be the same
both in MGWand in MSC Server. If these configurations differ significantly,
DSP capacity is wasted and problems concerning echo may arise. The echo
parameter is set to the 'N' ('not in use') value by default. The value of the echo
parameter can be modified with the RCM command:
ZRCM:CGR=<circuit group number>:ECHO=<Y/N>;

Example 42. Create routing objects for TDM resources

1. Create a special circuit group (CGR) with the VMGW parameter.


ZRCC:NCGR=VMGW1,CGR=1,TYPE=SPE:USE=VMGW;

Note
In order to be able to use TDM resources they must be attached to a VMGW.
You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.
For more information on creating a VMGW, see Configuring H.248 control
protocol (MGW Rel.4 - MSC Server).

2. Add TDM circuits to the CGR.


ZRCA:NCGR=VMGW1:CRCT=1-1&&-31;
3. Change the state of the circuit group to WO-EX.
ZCIM:CGR=1:WO;
4. Change the state of the circuits to WO-EX.
ZCIM:CRCT=1-1&&-31:WO;

6-108933Issue 1-0 © Nokia Oyj 137 (201)


User Plane Resource creation in MGW

12.7 Example: Creating A interface (MGW Rel.4 - BSC)

1. Create remote MTP configuration (NCN, NSC, NRC)


a. Create TDM signalling links (NCN)
ZNCN:1:16-1,64:ISU,0;
b. Create SS7 signalling link set (NSC)
ZNSC:NA0,233,BSC2:2,0;
c. Create signalling route set (NRC)
ZNRC:NA0,233,BSC2,0,,N:,,,7;
2. Activate MTP configuration (NLA, NLC, NVA, NVC)
a. Allow activation of the signalling links (NLA)
ZNLA:1;
b. Activate the signalling links (NLC)
ZNLC:1,ACT;
c. Allow activation of the signalling routes (NVA)
ZNVA:NA0,233;
d. Activate signalling routes (NVC)
ZNVC:NA0,233::ACT;
3. Create remote SCCP configuration (NFD, NAC)
a. Create remote SCCP signalling points and subsystems (NFD)
ZNFD:NA0,233,0:FE,BSSAP,1,Y;
b. Create translation results (NAC)
ZNAC:NET=NA0,DPC=233,RI=SSN,SSN=FE;

4. Activate SCCP configuration (NGC, NHC)


a. Activate remote SCCP signalling points (NGC)
ZNGC:NA0,233:ACT;
b. Activate remote SCCP subsystems (NHC)
ZNHC:NA0,233:FE:ACT;
5. Create routing objects for TDM resources controlled by MSC server
(RCC, RCA, CIM)
a. Create a special circuit group (SPE CGR) with the USE parameter
(RCC)
ZRCC:TYPE=SPE,NCGR=BSC2,CGR=1:USE=VMGW;
b. Add TDM circuits to the SPE CGR (RCA)
ZRCA:NCGR=BSC2:CRCT=16-2&&-31;
c. Change the state of the circuit group to WO-EX (CIM)
ZCIM:CGR=1:WO;

6-108933Issue 1-0 © Nokia Oyj 138 (201)


User Plane Resource creation in MGW

d. Change the state of the circuits to WO-EX (CIM)


ZCIM:CRCT=16-2&&-31:WO;

6-108933Issue 1-0 © Nokia Oyj 139 (201)


User Plane Resource creation in MGW

13 Creating PSTN/PLMN interface


(MGWRel.4 - PSTN/PLMN)

13.1 Configuring PDH for TDM transport


This procedure describes how you can configure PDH/TDM for the NIWU
interface unit. The mode of the PDH interface must be the same for all the
exchange terminals (ET) in the plug-in unit. That is why the NIWU 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.
The network element provides a synchronisation interface for external timing
reference signals. For information on synchronisation, see Configuring
synchronisation inputs in Synchronisation and Timing.
When you have configured new ETs, you may have to modify their functional
modes. Choose either E1, ETSI specific functional modes, or T1, ANSI specific
functional modes. The default mode for PDH/TDM is E1.

Before you start


You must have created the functional unit description for the ETs. For the
instructions, see Creating and attaching functional unit in Hardware
Configuration Management.

1. Interrogate the ET's current configuration (YAI)


ZYAI:ET;

2. Set the interface operation mode of NIWU (YAE)


Set the operation mode if you want to change it from E1 to T1/JT1 or
from T1/JT1 to E1. The impedance parameter can be given only if the

6-108933Issue 1-0 © Nokia Oyj 140 (201)


User Plane Resource creation in MGW

operation mode given is E1.


ZYAE:NIWU,<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. See the instructions in
Restarting functional unit in Recovery and Unit Working State
Administration.
3. Modify E1 functional modes, if needed (YEC)
You can first output the ETSI specific frame modes with the command
ZYEI;

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 the command
ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);

Note
Double framing does not support SSM. For more information, see Configuring
synchronisation inputs in Synchronisation and Timing.

4. Modify T1 functional modes if needed (YEG)


You can first output the ANSI specific T1 functional modes with the
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 the command
ZYEG:<unit type>,<unit index>:(ESF|SF),(B8ZS|AMI),(0|
7.5|15|22.5);

Example 43. Configuring PDH for TDM (ETSI standard /E1)

1. Interrogate the current configuration.


ZYAI:ET;
2. 2. Set the interface operation mode of NIWU with index number 3 to E1 and with impedance 75
©.
ZYAE:NIWU,3,E1:75;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ETSI-specific functional modes.
ZYEI;
5. Modify E1 functional modes of the ET with index 2.
ZYEC:ET,2:NORM,CRC4;

6-108933Issue 1-0 © Nokia Oyj 141 (201)


User Plane Resource creation in MGW

Example 44. Configuring PDH for TDM (ANSI standard /T1)

1. Interrogate the current configuration.


ZYAI:ET;
2. Set the interface operation mode of NIWU with index number 3 to T1.
ZYAE:NIWU,3,T1;
3. Restart the unit.
ZUSU:NIWU,3;
4. Output the ANSI-specific functional modes.
ZYEH;
5. Modify T1 functional modes of the ET with index 2.
ZYEC:ET,2:ESF,B8Z2,0;

13.2 Creating remote MTP configuration


In most cases the MTP needs to be configured to the network element. Before
configuring 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.
• A interface, between MGWand BSC. The configuration is based on
TDM.
• PSTN/PLMN interface, between MGW and PSTN/PLMN. The
configuration is based on TDM.
• Iu-CS interface, between MGW and RNC. The configuration is based on
ATM.
• Nb interface, between MGW and MGW. The configuration is based on
ATM.
• 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.
• Iu-PS interface, between RNC and SGSN. The configuration is based on
ATM.
• To configure IP signalling between MGW and MSS, see instructions in
Creating IP signalling configuration.

Before you start


Before you start to create signalling links, check that the SS7 services and own
MTP signalling point have been created. For instructions, see Creating local
signalling configuration for MGW Rel.4.

6-108933Issue 1-0 © Nokia Oyj 142 (201)


User Plane Resource creation in MGW

1. Check that the signalling links are distributed evenly between different
ISUs
Use the following command to display the existing signalling links.
ZNCI;
It is recommended that you allocate signalling links between all working
ISU units to distribute the load. Also, it is very important that signalling
links belonging to the same linkset are allocated to different ISU units to
avoid the whole linkset to become unavailable in an ISU switchover.
2. Create signalling links (NCN/NCS)
To create TDM signalling links, give the command
ZNCN:<signalling link number>:<external interface PCM-
TSL>,<link bit rate>:ISU,<unit number>: <parameter set
number>;

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>;

Note
Before creating ATM signalling links, check that there are free VCLtps
available and that they are correctly configured. For instructions, see Create
VCLtps for signaling

Remember to check by using the WFI command that the network element is
adequately equipped before you start creating signalling links. 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.

The parameter set related to the signalling link can be used to handle several of
the signalling link timers and functions. If the ready-made parameter packages
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 link. It is advisable to find out if there will be such special situations
before you start configuring the MTP. See Signalling link parameters.
Here are two examples of special situations in TDM signalling links that 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.

6-108933Issue 1-0 © Nokia Oyj 143 (201)


User Plane Resource creation in MGW

Note
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.
The parameter set related to the signalling link can be used to handle several of
the signalling link timers and 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 link.
3. Create SS7 signalling link set (NSC)
Create a signalling link set for each destination.
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 signalling route set. You can reserve several
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>,<signalling link priority>;
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 (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
and related matters such as A interface used between the MGW Rel.4 and
MSC. 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. 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>:<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).

6-108933Issue 1-0 © Nokia Oyj 144 (201)


User Plane Resource creation in MGW

Note
Notice that 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.

Note
The parameters load sharing status and restriction status are not
necessary during MGW Rel.4 integration.

13.2 Activating MTP configuration

1. Allow activation of the signalling links (NLA)


Use the following command to allow the activation of 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 in


case 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.
To interrogate the states of signalling links, use the commands NLI or
NEL.
The activation procedure is the same even when you are creating an IP
connection. When you activate a 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 interrogate the
states of the associations, use the command OYI. For more information,
see Association set and associations.
3. Allow activation of the signalling routes (NVA)
Use the following command to allow the activation of previously created
signalling routes:
ZNVA:<signalling network>,<signalling point code>:
<signalling transfer point network>,<signalling
transfer point code>;

6-108933Issue 1-0 © Nokia Oyj 145 (201)


User Plane Resource creation in MGW

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;
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 state AV-EX if the related link set is active; otherwise it
assumes state UA-INS. A signalling route going through an STP can also
assume 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 45.

In this example, you change the state of a signalling route which is leading to
signalling point 302. The route is defined in 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:

After this, you use the NVC command to activate the route:
ZNVC:NA0,302::ACT;

The execution printout can be as follows:

6-108933Issue 1-0 © Nokia Oyj 146 (201)


User Plane Resource creation in MGW

13.3 Setting MTP level signalling traffic load sharing


With 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 start


Before 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.

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
separatelyinterrogate the load sharing data concerning either messages
generated by the own signalling point or STP signalling traffic (for
example, for STP traffic according to the ANSI standards, the load
sharing system is different).
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>;

6-108933Issue 1-0 © Nokia Oyj 147 (201)


User Plane Resource creation in MGW

4. Allow load sharing in the signalling route set, if needed (NRB)


If you want to activate the load sharing and in the signalling route set in
question it is not already allowed (output of the NRI command), you
have to change the load sharing status.
ZNRB:<signalling network>,<signalling point codes>:
LOAD=<load sharing status>;

13.4 Creating remote SCCP configuration


The 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 start


Check that the whole network has been carefully planned, all necessary
hardware has been installed on the network element and the Message Transfer
Part (MTP) has already been configured.
Examine the following things:
• Check that the signalling points have been created on the MTP (the NRI
command) and the services are available for the SCCP (the NPI
command).
• Check which parameter set is used, and whether there is need to modify
the values of the 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.
Before you can create the SCCP to the network element, the SCCP service has
to be created first. 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).

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

6-108933Issue 1-0 © Nokia Oyj 148 (201)


User Plane Resource creation in MGW

Note
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).

1. Create remote SCCP signalling points and subsystems (NFD)


In addition to creating the own SCCP signalling point and its subsystems,
you also 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 later add more subsystems to a signalling point by using the
NFB command. The system may need new subsystems for example when
new services are installed, software is upgraded or network 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.
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 signalling 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
cancreate alternative routes that will then be taken into service in case 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>;

6-108933Issue 1-0 © Nokia Oyj 149 (201)


User Plane Resource creation in MGW

4. Set broadcast status (OBC, OBM)

Note
This step is not necessary for MGW-PSTN/PLMN interface.

There are two different kind of broadcasts you can set (it is recommended that
you set both of them):
The local broadcast status (the OBC command) is used to inform thesubsystems
of the own signalling point about changes in the subsystems of the remote
signalling points.
The broadcast status (the OBM command) is used to inform other signalling
points about changes in the subsystems of the own signalling point or the
subsystems of the signalling points connected to the own signalling point.
When you set local broadcasts, remember that also the remote network elements
have to be configured so that they send the status data to your network element.

Note
When setting the broadcasts, consider carefully what broadcasts are needed.
Incorrect or unnecessary broadcasts can cause problems and/or
unnecessarytraffic in the signalling network. Depending on the network
element, the subsystems needing the broadcast function are the following:
• BSSAP Base Station System Application Part
• RANAP Radio Access Network Application Part
• RNSAP Radio Network Subsystem Application Part
For example, the local BSSAP of the MSC has to know the status data of the
BSSAP located in the MGWs, and accordingly, the local BSSAP of the MGW
has to know the status data of the BSSAP in the MSC.
Local broadcasts:
ZOBC:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of local subsystem>,<local subsystem number>:<status>;
Remote broadcasts:
ZOBM:<network of affected subsystem>,<signalling point code
of affected subsystem>,<affected subsystem number>:<network
of concerned signalling point>, <concerned signalling point
code>:<status>;
For more information, see SCCP level signalling network.

6-108933Issue 1-0 © Nokia Oyj 150 (201)


User Plane Resource creation in MGW

13.5 Activating SCCP configuration

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, only remote SCCP
signalling points have to be activated. To check that the signalling point really
is active, use the NFI command.
In the command printout, the state of signalling point should be AV-EX. If the
signalling point assumes state UA-INS, there is a fault on the MTP level. You
can display the states of SCCP signalling points also by using the command
NGI. Notice that if you use the default values in the command, only the
signalling points of network NA0 are shown. For more information, see States
of SCCP signalling points.

Example 46.

When you examine an example system using the NFI or NGI commands, all
signalling points should be in normal state AV-EX. Note that 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:

2. Activate remote SCCP subsystems (NHC)


ZNHC:<signalling network>, <signalling point codes>:
<subsystem>:ACT;
To display the subsystem states, use the NHI or NFJ command. 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 available, although the actual subsystem may be

6-108933Issue 1-0 © Nokia Oyj 151 (201)


User Plane Resource creation in MGW

unavailable or even missing. The status of the unavailable subsystem will


be corrected with 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.
3. Set the SS7 network statistics, if needed
By setting SS7 network statistics you can monitor the performance of
SS7 network. You do not have to do it in the integration phase but you
can do it later.

For more instructions, see SS7 signalling performance measurements.

13.6 Creating routing objects for TDM resources


controlled by MSC server
This procedure describes how to divide TDM resources in a multimedia
gateway (MGW). In other words, this enables you to dedicate TDM resources
of an MGW to different virtual gateways on one physical gateway element.
Dividing TDM resources in a virtual MGW entails first creating a special circuit
group (SPE CGR) with the USE parameter and then adding circuits to this SPE
CGR with 'VMGW' as the USE parameter.
TDM resources in MGW are configured to a Virtual MGW (VMGW) which is
connected to an MSC server over H.248. How these TDM resources are used
(PSTN/PLMN interface, A interface, interconnecting TDM connections etc.)
depends on the signalling attached to them in the MSC server.
In digit analysis, TDM resources are hunted by MSC Server. The TDM
resources in an MGW are divided for virtual MGWs so that resources
controlled by each MSC Server are in their own circuit groups. TDM circuits,
which have different properties, are also in separate circuit groups.

1. Create a special circuit group (SPE CGR) with the USE parameter (RCC)
ZRCC:TYPE=<circuit group type>,NCGR=<circuit group
name>, CGR=<circuit group number>,TYPE=SPE:USE=<use of
the SPE CGR>;

Note
In order to be able to use TDM resources they must be attached to a VMGW.

6-108933Issue 1-0 © Nokia Oyj 152 (201)


User Plane Resource creation in MGW

You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.
For more information on creating a VMGW, see Configuring H.248 control
protocol (MGW Rel.4 - MSC Server).

2. Add TDM circuits to the SPE CGR (RCA)


ZRCA:NCGR=<circuit group name>,CGR=<circuit group
number>: CRCT=<circuit(s)>;
3. Change the state of the circuit group to WO-EX (CIM)
ZCIM:(NCGR=<circuit group name>...|CGR=<circuit group
number>...):(WO|BA);
4. Change the state of the circuits to WO-EX (CIM)
ZCIM:CRCT=<circuit(s)>...:(WO|BA);

Note
The following CGR features can also be modified:
• POOLID
Different kind of user plane properities can be used by dividing circuits to
separate circuit groups and by attaching different User Plane Parameter sets to
those (POOLID). User Plane parameter sets can be defined with the W4-MML
commands. A new User Plane Parameter set can be attached to the CGR with
the RCM command:
ZRCM:CGR=<circuit group number>:POOLID=<POOLID number>;
• ECHO
The echo cancellation feature is needed in traffic between MGWand PSTN.
The echo parameter defines whenever the DSP resources are reserved for the
echo cancellation at the resource reservation phase. By setting the 'Y' value, it
guarantees that DSP resources will be available for the echo cancellation if this
is needed. Moreover, selecting the 'Y' value will also reserve the DSP resources
even when echo cancellation is not needed by the call; in this way, incorrect
configuration can limit the amount of calls that MGW can handle. Notice, also,
that the echo cancellation configurations of TDM circuits should be the same
both in MGWand in MSC Server. If these configurations differ significantly,
DSP capacity is wasted and problems concerning echo may arise. The echo
parameter is set to the 'N' ('not in use') value by default. The value of the echo
parameter can be modified with the RCM command:
ZRCM:CGR=<circuit group number>:ECHO=<Y/N>;

6-108933Issue 1-0 © Nokia Oyj 153 (201)


User Plane Resource creation in MGW

Example 47. Create routing objects for TDM resources

1. Create a special circuit group (CGR) with the VMGW parameter.


ZRCC:NCGR=VMGW1,CGR=1,TYPE=SPE:USE=VMGW;

Note
In order to be able to use TDM resources they must be attached to a VMGW.
You can use the JVC command to create a new VMGW and add a CGR to it. If
a VMGW already exists, you can use the JVM command to attach a CGR to the
VMGW.
The JVC command can also be used at a later stage in the configuration if, for
example, other configurations need to be made prior to creating a VMGW and
adding a CGR to it.
For more information on creating a VMGW, see Configuring H.248 control
protocol (MGW Rel.4 - MSC Server).

2. Add TDM circuits to the CGR.


ZRCA:NCGR=VMGW1:CRCT=1-1&&-31;
3. Change the state of the circuit group to WO-EX.
ZCIM:CGR=1:WO;
4. Change the state of the circuits to WO-EX.
ZCIM:CRCT=1-1&&-31:WO;

6-108933Issue 1-0 © Nokia Oyj 154 (201)


User Plane Resource creation in MGW

14 Configuring ATM AAL2 nodal switching


functionality in MGW Rel.4

14.1 Overview of configuring ATM AAL2 nodal


switching functionality in MGW Rel.4
The ATM AAL2 nodal switching functionality makes it possible to route any
AAL2-based connection via MGW Rel.4 without MSC Server control. In
MGW Rel.4 the ATM AAL2 nodal switching functionality is used to optimise
the usage of the resources in the network. It makes the implementation of the
signalling network easier and cheaper for the operator because the same ATM
resources can be utilised for Iu, Iur and Nb interfaces.

Routing Iur interface via MGW Rel.4


The ATM AAL2 nodal switching functionality makes it possible to route the Iur
traffic between two adjacent RNCs via MGW Rel.4. When the Iur interface is
routed via Multimedia Gateway, direct connections between the RNCs (and
thus dedicated transmission resources for Iur traffic) are not needed.

6-108933Issue 1-0 © Nokia Oyj 155 (201)


User Plane Resource creation in MGW

Figure 8. AAL2 bearer establishment from RNC1 to RNC2 (Iur)

Routing Iu-CS interface user plane traffic via MGW Rel.4


The ATM AAL2 nodal switching functionality makes it possible to route the Iu-
CS interface user plane traffic without MSC Server control via one MGW Rel.4
(1) to another MGW Rel.4 (2). In this alternative MSC Server may request
AAL2 bearer establishment from RNC 1 directly to MGW 2 (through MGW 1
in the middle).

6-108933Issue 1-0 © Nokia Oyj 156 (201)


User Plane Resource creation in MGW

Figure 9. AAL2 bearer establishment from RNC1 to MGW2 (Iu-Cs)

Routing Nb interface via multiple Rel.4 MGWs


The ATM AAL2 nodal switching functionality makes it possible to route the
Nb interface without MSC Server control from one MGW Rel.4 (1) via another
MGW Rel.4 (2) to a third MGW Rel.4 (3).

6-108933Issue 1-0 © Nokia Oyj 157 (201)


User Plane Resource creation in MGW

Figure 10. AAL2 bearer establishment from MGW1 to MGW3 (Nb)

Note
Creating subdestinations for a destination and defining routing policy are
optional when configuring the ATM AAL2 nodal switching functionality in
MGW Rel.4. In general, creating basic routing and digit analysis are sufficient.
Subdestinations and subdestination routing policy should be used only if there is
a definite need (backup connections, load sharing) for several subdestinations
and routing policy measures.

6-108933Issue 1-0 © Nokia Oyj 158 (201)


User Plane Resource creation in MGW

14.2 Creating routing objects and digit analysis for


AAL2 nodal switching functionality in MGW
This procedure describes how to create routing objects and digit analyses for
AAL2 nodal switching functionality in MGW Rel.4 with MML commands. The
AAL2 nodal function enables connection of the ATM adaptation layer type 2
(AAL2) based Iur interface between two adjacent radio network controllers via
a Multimedia Gateway (MGW). Digit analysis is needed in the Iur interface
when it connects two Radio Network Controllers (RNC) via a Multimedia
Gateway Rel.4 (MGW) to find the right route to an adjacent node (that is, a
route to drift RNC) in the MGW.
In addition to the above, the AAL2 nodal function can also be used for the
following:
• routing Iu-CS (user plane) interface without MSC Server control via one
MGW to another MGW, and
• routing Nb interface without MSC Server control from one MGW via
another MGW to a third MGW.
The number of the analysis tree is set in PRFILE with the following parameter:
AAL2_ANALYSIS_TREE (007:0127)
This parameter determines the digit analysis tree in which the B address is
analysed. The parameter is used in MGW. The nodal function uses this
parameter when searching for an outgoing route to the adjacent node (the RNC
or another MGW). The allowed values are 1D - 1023D.
The associated signalling used is broadband MTP3 signalling. The routing
objects and digit analysis must be created at both ends of the interfaces between
two network elements before any user plane connections can be built between
them.

Note
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.

Before you start


Before 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 analyses and components by using commands of the RI command
group.

6-108933Issue 1-0 © Nokia Oyj 159 (201)


User Plane Resource creation in MGW

1. Create an AAL2 route (RRC)


ZRRC:ROU=<route number>,TYPE=AAL2,PRO=<protocol>:
NET=<signalling network>,SPC=<signalling point
code>,ANI=<AAL2 node identifier>;
2. Create an endpoint group (LIC)
ZLIC:<route number>,<ep group index>:<ingress service
category>,<egress service category>; The ingress and
egress service categories must always be Constant Bit
Rate (CBR).
3. Check that there is a free VCLtp (LCI)
ZLCI:<interface id>,VC:<VPI>:FREE; Out of these VCIs
all those with service category CBR in both directions
can be used in the next step.
4. Create an endpoint (LJC)
ZLJC:<ep type>,<route number>,<connection id>:
<interface id>,<VPI>,<VCI>:<ownership>:[<loss
ratio>,<mux delay>];
The system will automatically assort this endpoint into the endpoint
group of step 2 since their service categories match.
5. Unblock the AAL type 2 path (LSU)
ZLSU:<ANI>:<AAL type 2 path identifier>:<execution
time>;
The endpoints must have been created at both ends of the interface before
the AAL type 2 path between them can be unblocked.

Expected outcome
The 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.

Unexpected outcome
The AAL type 2 path is still in blocked state. Repeat the unblocking command.
6. Create digit analysis (RDC)
Create a digit analysis for a specific digit sequence. Add number 45
before the digit sequence in order to avoid conflicts with other number
formats.
ZRDC:DIG=<digits>,TREE=<analysis tree>:ROU=<route
number>;

Example 54. Create routing objects and digit analysis for AAL2 nodal switching functionality

In the following example, routing objects and digit analysis are created for AAL
nodal switching functionality.

6-108933Issue 1-0 © Nokia Oyj 160 (201)


User Plane Resource creation in MGW

1. Create an AAL2 route between two RNCs via an 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
AAL2 node identifier is AAL2MGW1.
ZRRC:ROU=11,TYPE=AAL2,PRO=MTP3:NET=NA0,SPC=701, ANI=AAL2MGW1;
2. Create an endpoint group under route 11. The endpoint group id is automatically selected by the
system. The termination points in this group shall have the Constant Bit Rate service category
for both ingress and egress directions.
ZLIC:11:C,C;
3. Check that there is a free VCLtp.
ZLCI:<interface id>,VC:<VPI>:FREE;

Notice, 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.
4. Create an endpoint of VC level (VCCep) under the 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 AAL2 type 2 loss ratio is 10_4 and the AAL type 2
multiplexing delay 2 ms.
ZLJC:VC,11,5:2,1,33:LOCAL:4,20;
The system will automatically assort this endpoint into the endpoint group of step 2 since their
service categories match.
5. Unblock the AAL type 2 path 11. The ANI is AAL2MGW1 and the allowed waiting time for the
execution of the blocking command is 18 seconds.
ZLSU:AAL2MGW1:11:18;
6. Create digit analysis for a digit sequence 4535840222 in analysis tree 55.
ZRDC:DIG=4535840222,TREE=55:ROU=11;

14.3 Creating routing objects and digit analysis with


subdestinations and routing policy for AAL2 nodal
switching functionality in MGW
This procedure describes how to create routing objects and digit analyses with
subdestinations and routing policy for AAL2 nodal switching functionality in
MGW Rel.4 with MML commands. The AAL2 nodal function enables
connection of the ATM adaptation layer type 2 (AAL2) based Iur interface
between two adjacent radio network controllers via a Multimedia Gateway
(MGW). Digit analysis is needed in the Iur interface when it connects two
Radio Network Controllers (RNC) via a Multimedia Gateway Rel.4 (MGW) to
find the right route to an adjacent node (i.e. a route to drift RNC) in the MGW.
In addition to the above, the AAL2 nodal function can also be used for the
following:
• routing Iu-CS (user plane) interface without MSC Server control via one
MGW to another MGW, and
• routing Nb interface without MSC Server control from one MGW via
another MGW to a third MGW.

6-108933Issue 1-0 © Nokia Oyj 161 (201)


User Plane Resource creation in MGW

The number of the analysis tree is set in PRFILE with the following parameter:
AAL2_ANALYSIS_TREE (007:0127)
This parameter determines the digit analysis tree in which the B address is
analysed. The parameter is used in MGW. The nodal function uses this
parameter when searching for an outgoing route to the adjacent node (the RNC
or another MGW). The allowed values are 1D - 1023D.
There are two different approaches to creating digit analysis for the AAL2
nodal switching functionality:
• creating (basic) digit analysis, where each destination has only one
subdestination
• creating digit analysis, where each destination can have more than one
subdestination.
Creating subdestinations for a destination and defining routing policy (the latter
approach above) are optional features. Generally speaking, creating basic digit
analysis is sufficient, and it is recommended that the latter approach be used
only if there is a definite need for several subdestinations and routing policy
measures.
The routing policy function allows you to utilise percentage call distribution
(also known as load sharing). With percentage call distribution traffic to a
destination can be distributed among two or more subdestinations in predefined
proportions.

Note
Creating subdestinations for a destination and defining routing policy are
optional when creating the ATM backbone in MGW Rel.4. In general, creating
basic routing and digit analysis are sufficient. Subdestinations and
subdestination routing policy should be used only if there is a definite need (for
example load sharing) for several subdestinations and routing policy measures.

Before you start


Before 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 analyses and components by using using commands of the RI
command group.

1. Create an AAL2 route (RRC)


ZRRC:ROU=<route number>,TYPE=AAL2,PRO=<protocol>:
NET=<signalling network>,SPC=<signalling point
code>,ANI=<AAL2 node identifier>;

6-108933Issue 1-0 © Nokia Oyj 162 (201)


User Plane Resource creation in MGW

2. Create an endpoint group (LIC)


ZLIC:<route number>,<ep group index>:<ingress service
category>, <egress service category>; The ingress and
egress service categories should always be Constant
Bit Rate (CBR).
3. Check that there is a free VCLtp (LCI)
ZLCI:<interface id>,VC:<VPI>:FREE; Out of these VCIs
all those with service category CBR in both directions
can be used in the next step.
4. Create an endpoint (LJC)
ZLJC:<ep type>,<route number>,<connection id>:
<interface id>,<VPI>,<VCI>:<ownership>:[<loss
ratio>,<mux delay>];
The system will automatically assort this endpoint into the endpoint
group of step 2 since their service categories match
5. Unblock the AAL type 2 path (LSU)
ZLSU:<ANI>:<AAL type 2 path identifier>:<execution
time>;
The endpoints must have been created at both ends of the interface before
the AAL type 2 path between them can be unblocked.

Expected outcome
The 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.

Unexpected outcome
The AAL type 2 path is still in blocked state. Repeat the unblocking command.
6. Create subdestinations (RDE)
ZRDE:NSDEST=<name of subdestination>:ROU=<route
number>;

Note
You can create 1 to 5 subdestinations for each destination. Repeat the command
above for each subdestination.

7. Create a destination (RDE)


ZRDE:NDEST=<name of destination>:NSDEST=<name of
subdestination>;

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

8. Create digit analysis (RDC)


Create a digit analysis for a specific digit sequence. The specific digit

6-108933Issue 1-0 © Nokia Oyj 163 (201)


User Plane Resource creation in MGW

sequence is the AAL2 Service Endpoint Address of the adjacent node.


ZRDC:TREE=<analysis tree>,DIG=<digits>:NDEST=<name of
destination>;
9. Define percentage call distribution (RMM)
ZRMM:NDEST=<destination name>::SPERC1=<percentage
value of subdestination 1>,SPERC2=<percentage value of
subdestination 2>,SPERC3=<percentage value of
subdestination 3>,SPERC4=<percentage value of
subdestination 4>;

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

Example 55. Create routing objects and digit analysis for AAL2 nodal switching functionality
with percentage routing

In 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.

1. Create an AAL2 route between two RNCs via an 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
AAL2 node identifier is AAL2MGW1.
ZRRC:ROU=11,TYPE=AAL2,PRO=MTP3:NET=NA0,SPC=701, ANI=AAL2MGW1;
2. Create an endpoint group under route 11. The endpoint group id is automatically selected by the
system. The termination points in this group shall have the Constant Bit Rate service category
for both ingress and egress directions.
ZLIC:11:C,C;
3. Check that there is a free VCLtp.
ZLCI:<interface id>,VC:<VPI>:FREE;

Notice, 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.

4. Create an endpoint of VC level (VCCep) under the 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 AAL2 type 2 loss ratio is 10_4 and the AAL type 2 multiplexing delay 2
ms.
ZLJC:VC,11,5:2,1,33:LOCAL:4,20;
The system will automatically assort this endpoint into the endpoint group of step 2 since their service
categories match.
5. Unblock the AAL type 2 path 11. The ANI is AAL2MGW1 and the allowed waiting time for the
execution of the blocking command is 18 seconds.
ZLSU:AAL2MGW1:11:18;
6. Create three subdestinations, 'HELSINKI1', 'GOTHENBURG' and 'HAMBURG' leading to outside
routes:

6-108933Issue 1-0 © Nokia Oyj 164 (201)


User Plane Resource creation in MGW

ZRDE:NSDEST=HELSINKI1:ROU=11;
ZRDE:NSDEST=GOTHENBURG:ROU=2;
ZRDE:NSDEST=HAMBURG:ROU=3;

Note
In this example it is presumed that routes 2 and 3 have been created separately
by following steps 1 to 5 above.

7. Create the destination LONDON, define three subdestinations for it and define HELSINKI1 as the
primary subdestination:
ZRDE:NDEST=LONDON:NSDEST=HELSINKI1;
ZRDE:NDEST=LONDON:NSDEST=GOTHENBURG;
ZRDE:NDEST=LONDON:NSDEST=HAMBURG;
8. Create digit analysis for a digit sequence 4535840222 in analysis tree 24.
ZRDC:DIG=4535840222,TREE=24:NDEST=LONDON;
9. Create percentage call distibution.
Define the percentage call distribution values of routing alternatives so that the
primary subdestination covers 60% of traffic, the subdestination equivalent to
the first alternative subdestination 30% of traffic and the third alternative
subdestination 10% of traffic:
ZRMM:NDEST=LONDON::SPERC0=60,SPERC1=30,SPERC2=10;
Once you have created subdestinations and defined percentage call distribution
for these, you can modify these settings with the RMM command.

6-108933Issue 1-0 © Nokia Oyj 165 (201)


User Plane Resource creation in MGW

15 Integrating NEMU

15.1 Configuring domain name in Orbix configuration


in NEMU
'IT_LOCAL_DOMAIN' must be configured to be exactly the same as primary
DNS suffix of NEMU.

1. Open file E:\NEMU\NT_CORE\ORBIX\CONFIG\COMMON.CFG in


Notepad for editing
From the Start menu select Run and type NOTEPAD E:\NEMU
\NT_CORE\ORBIX\COMMON.CFG and press ENTER.
2. Configure the 'IT_LOCAL_DOMAIN' according to the IP plan
Edit common.cfg file. Enter the domain name between quotation marks
to line IT_LOCAL_DOMAIN = "";
3. Save file and close notepad
4. Restart 'orbixd' process to activate new parameter value
a. Choose Start -> Programs -> Nemu Platform Manager User
Interface -> pmui
b. Select 'orbixd' from the list of 'Nonstop Processes' and press 'Stop
Process' button
c. Wait until the status of 'orbixd' is 'Stopped'
d. Select 'orbixd' again from the list of 'Nonstop Processes' and press
'Start Process' button
e. Wait until the status of 'orbixd' is 'Running'
f. Close Nemu Platform Manager User Interface

6-108933Issue 1-0 © Nokia Oyj 166 (201)


User Plane Resource creation in MGW

15.2 Setting log size and overwriting parameters for


NEMU logs
The log size is changed using the Windows 2000 Event Log viewer. You can
select whether or not you wish to overwrite the log events. If you choose not to
overwrite the events, the log file will eventually fill up; to avoid this the log
information must be manually cleared every now and then (save the log
information before clearing all events, if you still need the information). You
will also receive error messages if the log file is full and the writing of log
information is therefore interrupted.
You do not have to monitor consumption of the log file space if the log events
are overwritten. However, you should make sure that no important log
information is lost upon overwriting of the events by saving the information you
wish to keep to a file at certain intervals. You can also select that only
information older than a specified number of days is overwritten.
Note that you are recommended to overwrite log events.

1. Set the log size


You can check and change the log size by starting the Windows 2000
Event Viewer from Start -> Settings -> Control Panel -> Administrative
Tools _> Event Viewer, and then selecting Application Log and from the
Action menu selecting Properties. If log settings need to be changed,
enter new size to Maximum log size box.
2. Set the overwriting parameters
You can select the Overwrite Events mode locally from Application Log
Properties of your NEMU Windows 2000 Event Viewer. You must have
administrator rights in order to change the mode.

It is recommended that only information older than seven days is


overwritten.

15.3 Supervising NEMU software


NEMU SW supervision helps to keep SW processes alive and indicates stopped
or jammed applications or processes.
The supervision interval defines the time between checks on the status of
processes. There are two parameters for supervision interval. Both of them have
default settings, but the parameters can be altered.

6-108933Issue 1-0 © Nokia Oyj 167 (201)


User Plane Resource creation in MGW

If the supervision interval is too short, it consumes too much processor time. If
the interval is too long, there is a chance that the jammed state of a process
remains unnoticed for a long time.
Note that if you change the supervision intervals, you need to reboot Windows
2000.

1. Change the interval for recovering stopped processes, change


LooksAliveInterval parameter
Registry address for the parameter is HKEY_LOCAL_MACHINE
\SOFTWARE\Nokia\NEMU\InstalledModules\c_core\NemuSupervision
\NemuSupervisor\CurrentVersion\Settings\LooksAliveInterval The
parameter value is in seconds, with the maximum of two digits.
2. Change the interval for recovering blocked processes, change
IsAliveInterval parameter
Registry address for the parameter is HKEY_LOCAL_MACHINE
\SOFTWARE\Nokia\NEMU\InstalledModules\c_core\NemuSupervision
\NemuSupervisor\CurrentVersion\Settings\IsAliveInterval The parameter
value is in seconds, with the maximum of two digits.

15.4 Configuring network element system identifier


(systemId) to NEMU
This procedure configures the system identifier of the network element to
NEMU if NEMU is used to manage RNC or MGW network elements. If there
is only one network element under NEMU (for example in case of RNC and
MGW), the systemID has to have the same value as the identifier of the network
element (for example systemID = NE-RNC-'rnc_id''). Make sure that the
systemID is the same as the identifier of the network element, otherwise there
can be problems in sending notifications to the Nokia NetAct. Also note that the
SystemId must be unique in the whole network.

Note
This procedure is applied if NEMU is used to manage RNC and MGW network
elements.

Before you start


Ensure that NEMU is available.

6-108933Issue 1-0 © Nokia Oyj 168 (201)


User Plane Resource creation in MGW

1. Open %NEMUWWWROOT%\systemid.txt file to NOTEPAD editor


2. Add value of the systemId to the file
The value could be for example NE-RNC-'rnc_id' or NE-MGW-'c-
number'

Note
Do not press Enter after typing the SystemID.

3. Save file

15.5 Configuring Nokia NetAct interface with NEMU


This procedure instructs you to configure the connection from NEMU to Nokia
NetAct.

1. Check that CORBA/IIOP and Session Manager are running


Open the TaskManager in NEMU from Start - Run - taskmgr (or press
Ctrl +Alt+Delete and click Task Manager). Check that CORBA/IIOP
(orbixd. exe) and Session Manager (Nwi3SessionManager.exe) are up
and running.
2. Define system identifier in NEMU
The system identifier attribute (systemId) has to be defined in the NEMU
commissioning. The systemId attribute has been saved to the text file
whose location is defined in Windows 2000 registry
[HKEY_LOCAL_MACHINE\SOFTWARE\Nokia\NEMU
\InstalledModules\c_services\nemucorbasupserv\NWI3MDCo
rba \CurrentVersion\Settings].
3. Setup the required NetAct parameters to the INI-file (Nwi3MDCorba.ini)
in NEMU
a. Configure the NetAct parameters for NEMU.
i. Open %NEMUPLATFORMDATADIR%\c_services
\nemucorbasupserv\nwi3mdcorba\NWI3MDCORBA.ini file in, for example
NOTEPAD editor.
ii. Add the value of the stringfield IOR to the registrationServiceIOR field.
iii. Add the values of the registrationServiceUsername and
registrationServicePassword.
iv. Add value of takeIntoUseNext parameter. This value must be changed to 1.

6-108933Issue 1-0 © Nokia Oyj 169 (201)


User Plane Resource creation in MGW

v. Save file.
b. Restart the registering service of NEMU to activate new parameter
values. There are two alternative methods to activate parameters.
• Immediate activation:
i. Start Nemu Platform Manager User Interface (Start ->Programs -> Nemu
Platform Manager User Interface ->pmui).
ii. Select 'NemuRegServApp' from the list of 'Nonstop Processes' and press
'Stop Process' button.
iii. Wait until the status of NemuRegServApp is 'Stopped'.
iv. Select again 'NemuRegServApp' from the list of 'Nonstop Processes' and
press 'Start Process' button.
v. Wait until the status of NemuRegServApp is 'Running'.
vi. Close Nemu Platform Manager User Interface.
• Long time activation:
i. The registering service of NEMU makes the registration itself after a variable
period (usually the default random period is approximately 10-20 minutes).
4. Check entries from the registering service of NEMU
Check from the Windows 2000 Event Viewer if there are entries from the
registering service of NEMU (NemuRegServ.dll). If there is a log writing
"NemuRegServ: Getting the IOR of the Registration service failed.", the
registering service of NEMU did not manage to get rsIOR which is
needed for registering in Nokia NetAct.
When the registering service of NEMU is up and running, there is a log
writing "NemuRegServ: Successfully registered to registration service of
NetAct."

6-108933Issue 1-0 © Nokia Oyj 170 (201)


User Plane Resource creation in MGW

APPENDIX A: Configuring synchronisation inputs


You can configure and control synchronisation with MML commands. Usually
synchronisation-related MML commands are used for setting synchronization
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
synchronised operating mode or 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 interrogate 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. 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 references do not affect the forced reference setting.
Whenever a synchronization reference that is used in the synchronization 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, if needed, when taking the network element into use,
after start-up and when testing the network element. Usually this is done
automatically by the system.

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

1. Set parameters for all synchronisation references (DYM)


The highest priority value (PRI) is 1. The highest synchronisation status
message value (SSM) is 1, the lowest 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 synchronisation. 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.

6-108933Issue 1-0 © Nokia Oyj 171 (201)


User Plane Resource creation in MGW

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

Note
The Framing mode for the incoming PDH references must support the transfer
of the SSM values. For instructions about configuring the Framing mode, see
Configuring PDH for TDM transport and Configuring PDH for ATM transport.
If the Framing mode for the incoming PDH references does not support the
transfer of SSM value, the references can be set with the PRI value.

ZDYM:<synchronisation reference>,<reference index>, <mode


of external reference>:PRI=<priority value>, SSM=<ssm
value>;
2. Check the values of the WTR timers for the references (DYI)
ZDYI;
3. 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 command RESET.
ZDYL: <synchronisation reference>, <reference index>:
<action>, <value>;
4. Enable distribution of outgoing synchronisation signal (DYE)
Enable the distribution of outgoing signal if you want to distribute the
signal outside the network element. Give the ENA value for the ACT
parameter.

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

ZDYE:<synchronisation reference>,<reference
index>...:ACT=<action>;
5. Check the automatic synchronisation setting (DYI)
When the parameters for at least one synchronisation reference are set for
the first time during system start-up, the system will
synchroniseautomatically. In this case you do not have to manually set
the operation mode.

6-108933Issue 1-0 © Nokia Oyj 172 (201)


User Plane Resource creation in MGW

ZDYI:<identification of information>, <identification


of reference>;
6. Set operation mode (DYT)
If the system clock has not locked into the reference even though the
reference is available, it can be forced to lock into it by using the DYT
command. This command is not normally used in the commissioning
phase.
ZDYT:MODE=<operation mode>;
7. Use 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. 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 references do not affect the forced
reference setting.
Give the Y value for the ACT parameter.
You can release synchronisation reference as the forced reference of
system clock by giving value N for the ACT parameter.
ZDYS:<synchronisation reference>,<reference
index>:ACT=<action>;
8. Control general settings for synchronisation system (DYR)

Note
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 criterias when the best reference is selected to be
used in the synchronisation 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.

Note
You must enter the parameters for the connected references to make them
available for the system. The PRI value other than PRI=X tells to 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>;

6-108933Issue 1-0 © Nokia Oyj 173 (201)


User Plane Resource creation in MGW

APPENDIX B: Printing alarms in MGW Rel.4

B1) Printing alarms using LPD protocol

Before you start


To print out the alarms, you must first configure the LPD printers and define
their TCP/IP address.

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.

Note
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. If The LPD is not shown in the printout the


Create the LPD device
For 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. If The printer state is not NORMAL then
Change the printer state to NORMAL (INS)
ZINS:<device index>:NORMAL;
5. If The settings are not correct then
Modify the printer settings (INM)
ZINM:<device index>:;

6-108933Issue 1-0 © Nokia Oyj 174 (201)


User Plane Resource creation in MGW

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 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. To print out only certain kind of
alarms to the desired I/O device, connect the suitable logical files to the
I/O device.
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.

Note
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 58. Printing out the alarms to the desired I/O device

In this example, two and three star communications alarms are directed to VPP-
1. This example assumes that the printers are configured and their TCP/IP
address is configured.

1. Display the printer state and check that the value of the field FUNCTIONAL STATE in the
printout is NORMAL. Check that the TCP/ IP address is correct.
As you want to direct the alarms to VPP-1, check that the index number of LPD is 1.
2. The alarm system writes two and three star communications alarms to the logical file
ALACOMM1. Connect ALACOMM1 to the correct alarm output device.
When giving the command, pay special attention to the correct index number.
ZIIS:,:ALACOMM1,:DEV=VPP-99:DEV=VPP-1;

B2) Printing alarms via Telnet terminal or Web browser

You can print out the alarms to a Telnet terminal or to a Web browser. Use a
Telnet terminal or a Web browser, when you want to print out the alarms
instantly on the computer screen over TCP/IP.

Before you start


To print out the alarms via Telnet terminal or a Web browser, you need to be

6-108933Issue 1-0 © Nokia Oyj 175 (201)


User Plane Resource creation in MGW

familiar with the logical files used with alarms, and their tasks.

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.

Note
Note that if all the logical files are connected to VPP-99, one remote session for
alarm printing can be established. If the logical files are connected to two
VPP's, 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 etc.

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 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>;

6-108933Issue 1-0 © Nokia Oyj 176 (201)


User Plane Resource creation in MGW

Note that after connecting the logical files associated with alarms to the correct
devices, you do not need to touch 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 11111

If 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, simply connect to the correct address
and port; no extra keystrokes are needed.

Expected outcome
The 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 (ISI)
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.
ZISI::VPP;

If the VPP device which you connected is not in the WO-EX state, alarms
are not printed via Telnet/HTTP. 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 connection to OMU, port 11111 from a Telnet terminal or
Web browser.
6. End the session when you are ready
You can stop the printing of alarms via Telnet or HTTP by simply
closing the Telnet terminal or the Web browser.

6-108933Issue 1-0 © Nokia Oyj 177 (201)


User Plane Resource creation in MGW

APPENDIX C: Configuring site connectivity for MGW Rel.4

C1) Overview of configuring site connectivity for MGW Rel.4

The purpose of this procedure is to configure site connectivity for Multimedia


Gateway Rel.4. After this, you can use the Element Manager to manage the
MGW remotely.

Note
IP connections from OMU and ISU to ESA12 are optional. They are necessary
only when:
• Gigabit Ethernet (IPGE/IPGEP/IPGO/IPGOP) is used for user plane
traffic
• SIGTRAN, H.248, IWF control and O&M traffic need to be physically
separated into a separate LAN than user plane traffic.

Before you start


Check that:
• you have the IP address plan and IP parameters for the computer unit,
NEMU.
• your computer has the DHCP client, Element Manager and remote
management application for NEMU installed.

If you are connecting MGW to NetAct via ESA12, you also need the IP
parameters for ESA12 and an Ethernet interface connected to a port of ESA12.
The following settings are preconfigured before the delivery:

Table 16. Preconfigured settings for O&M backbone connection of

6-108933Issue 1-0 © Nokia Oyj 178 (201)


User Plane Resource creation in MGW

1. Start the MMI Window from the OMU service terminal port of the local
MGW

Refer to Using EM MMI window in Element Manager Administration for


further instructions.
2. Create MMI user IDs and profiles for the remote connection

Refer to Creating MMI user profiles and user IDs for remote connections
to NetAct for detailed instructions.
3. If you want to isolate SIGTRAN, H.248, IWF control and O&M traffic
from user plane traffic, or if you want to use the NIS1 card for O&M
traffic then
Configure OMU and ESA12
a. Configure the IP stack in OMU according to instructions in
Configuring IP stack in functional units of MGW Rel.4.
b. Configure ESA12 according to instructions in Configuring ESA12.
4. If you do not want to isolate SIGTRAN, H.248, IWF control and O&M
traffic from user plane traffic then
Configure internal connections for IP-NIU
Refer to Configuring internal connections for IP-NIU.
5. Configure NEMU for DCN
Refer to Configuring NEMU for DCN in MGW Rel.4 for detailed
instructions.

6-108933Issue 1-0 © Nokia Oyj 179 (201)


User Plane Resource creation in MGW

6. Configure external IP connections


Configure the connection to NetAct for O&M traffic. There are two ways
to connect the MGW to NetAct:
• by configuring the O&M backbone via Ethernet
Refer to instructions in Connecting to O&M backbone via
Ethernet.
• by configuring the O&M backbone via ATM virtual connections
Refer to instructions in Connecting MGW Rel.4 to external
network via ATM virtual connections.

Note
The recommended way of connecting MGW to NetAct is via Ethernet. The
connection via ATM should only be used as a backup.

If you are not isolating SIGTRAN, H.248, IWF control and O&M traffic from
user plane traffic, configure the IP-NIU according to instructions in Connecting
to external network via IP-NIU.
For interface-specific instructions for configuring external IP connections, see
Configuring IP for Nb user plane (MGW Rel.4 _ IP backbone), Configuring IP
for IP Trunk user plane (MGW Rel.4 _ MSC) and Configuring IP for control
plane (MGW Rel.4 _ MSC server/CDS).
7. Close the MMI Window

C2) Creating MMI user profiles and user IDs for remote connections to NetAct

To enable remote connections from NetAct to the MGW Rel.4, you need to first
connect to the MGW locally and create MMI user profiles and IDs as explained
below.
• NUPADM
The NUPADM profile and user ID are needed by NetAct Service User
Management, which is an application used for creating, modifying, and
controlling users of managed object services.
Service User Management application_s nupmgrmx process uses the
NUPADM user for updating the network elements with the user
information. To enable automatic updating, the NUPADM user must
exist in all the network elements supported by Service User Management.
• NEMUAD
The NEMUAD profile and user are created in the MGW so that NEMU
is able to connect to and perform management functions on the MGW.
• NEMFTP
The NEMFTP user is created to enable FTP connection from the MGW
to NEMU.

6-108933Issue 1-0 © Nokia Oyj 180 (201)


User Plane Resource creation in MGW

Before you start


Before creating the NUPADM profile and user ID, you must obtain the
NUPADM user_s password. If you do not have it, contact your NetAct
administrator.
It is recommended that the name of the user group profile and the ID using the
profile are identical, that is NUPADM profile and NUPADM user ID. Each user
group profile should only be used by one user ID.

1. Open the MMI window from the OMU service terminal


2. Check if the NUPADM profile exists (IAI)
Check if the NUPADM profile is already present and all command class
authorities are defined as 250.
ZIAI:PROFILE=NUPADM;

Expected outcome
The following output is displayed with the applicable data filled in, if the profile
exists.

6-108933Issue 1-0 © Nokia Oyj 181 (201)


User Plane Resource creation in MGW

3. If the NUPADM profile is not found and/or its command class authorities
are not set to 250 then
Create or modify the NUPADM profile (IAA)
ZIAA:NUPADM:ALL=250:VTIME=FOREVER,UNIQUE=YES;
4. Check if the NUPADM user ID exists (IAI)
ZIAI:USERID=NUPADM;

Expected outcome
The following output is displayed with the applicable data filled in, if the user
ID exists.

5. If NUPADM user ID is not found then


Create a new NUPADM user ID (IAH)
ZIAH:NUPADM:NUPADM;

Expected outcome
The system will prompt you for a password. The password must be the same as
used in NetAct. If you do not know the password, contact your NetAct
administrator.

6-108933Issue 1-0 © Nokia Oyj 182 (201)


User Plane Resource creation in MGW

6. Check if the NEMUAD and NEMFTP profiles exist (IAI)


Check if the NEMUAD and NEMFTP profiles are present and all
command class authorities are defined as 250.
ZIAI:PROFILE=NEMUAD;
ZIAI:PROFILE=NEMFTP;

Expected outcome
The following output is displayed with the profile specific data filled in, if the
profile exists.

7. If the NEMUAD or NEMFTP profiles are not found and/or their


command class authorities are not set to 250, then
Create or modify the NEMUAD or NEMFTP profiles (IAA)
ZIAA:NEMUAD:ALL=250:VTIME=FOREVER,UNIQUE=YES;
ZIAA:NEMFTP:ALL=250:VTIME=FOREVER,UNIQUE=YES,:: FTP=W;
8. Check if NEMUAD and NEMFTP user IDs exist (IAI)
ZIAI:USERID=NEMUAD;
ZIAI:USERID=NEMFTP;

6-108933Issue 1-0 © Nokia Oyj 183 (201)


User Plane Resource creation in MGW

Expected outcome
The following output is displayed with the user ID specific data filled in, if the
user ID exists.

9. If the NEMUAD or NEMFTP user IDs are not found then


Create new NEMUAD or NEMFTP user IDs (IAH)
ZIAH:NEMUAD:NEMUAD;
ZIAH:NEMFTP:NEMFTP;

Expected outcome
When creating a new user ID, the system prompts you for a password.The
following output is displayed:

6-108933Issue 1-0 © Nokia Oyj 184 (201)


User Plane Resource creation in MGW

Caution
Ensure the password is 6-16 characters long and contains both numbers and
letters. A poorly chosen password can compromise the security of the network.

C3) Configuring IP stack in functional units of MGW Rel.4

The purpose of this procedure is to configure the OMU, ISU or TCU unit for
DCN (Data Communication Network) and control plane. The OMU unit is used
for O&M backbone between the MGW and NetAct. The ISU unit is used for
control plane traffic between the MGW and the MSC Server or the Circuit
Switched Data Server (CDS). The TCU unit is used for user plane traffic
between two MGWs. Note that a TCU unit contains four TPG units to which
the actual configurations are made.

Note
IP connections from OMU and ISU to ESA12 are optional. They are necessary
only when:
• Gigabit Ethernet (IPGE/IPGEP/IPGO/IPGOP card) is used for user plane
traffic and
• SIGTRAN, H.248, IWF control and O&M traffic need to be physically
separated into a separate LAN than user plane traffic.

Before you start


You must have an open connection to the MMI window of the OMU service
terminal port of the local MGW.

6-108933Issue 1-0 © Nokia Oyj 185 (201)


User Plane Resource creation in MGW

1. Configure DNS parameter data (QRK/Q6K)

Note
This step is not necessary during MGW integration.

Define whether or not the DNS service is utilised in IP data transfer.


• In IPv4, give the command
ZQRK:[<primary DNS server>],[<secondary DNS server>],
[<third DNS server>],[<local domain name>],[<network
sortlist>],[<netmask sortlist>]:[<resolver cache>],
[<round robin>];
• In IPv6, give the command
ZQ6K:[<primary DNS server>],[<secondary DNS server>],
[<third DNS server>],[<local domain name>],[<network
sortlist>],[<prefix sortlist>]:[<resolver cache>],
[<round robin>];
2. Modify IP parameters (QRT/Q6T)

Note
This step is not necessary during MGW integration.

• In IPv4, you set host names, define if the unit forwards IP packets, set the
maximum time-to-live value and define if the subnets are considered to
be local addresses.
ZQRT:<unit type>,[<unit index> | [<unit group>, <unit
index>]]:([HOST=<host name>],[IPF=<IP forwarding>],
[TTL=<IP TTL>],[SNL=<subnets are local>]);
• In IPv6, you define if the unit forwards IP packets, set the maximum hop
count value for IP packets sourced by the system and define if the IP
stack receives router advertisements.
ZQ6T:<unit type>,[<unit index> | [<unit group>, <unit
index>]]:([IPF=<IP forwarding>], [HLIM=<hoplimit>],
[RADV=<router advertisement>]);
3. Remove the preconfigured IP address (QRN/Q6G)
• In IPv4, give the command
ZQRN:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>,: <IP
address>,,DEL;
• In IPv6, give the command
ZQ6G:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...> [<ip address>];

6-108933Issue 1-0 © Nokia Oyj 186 (201)


User Plane Resource creation in MGW

4. Add a new logical IP address to the Ethernet side (QRN/Q6N)


If the MGW is connected both to IPv4 and IPv6 networks, you must add
both addresses.
• In IPv4, give the command
ZQRN:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>, [<point to
point interface type>]:[<IP address>],[<IP address
type> ]:[<netmask length>]:[<destination IP address>]:
[<MTU>]: [<state>];
• In IPv6, give the command
ZQ6N:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>: [<IP address>],
[<IP address type>]:[<prefix length>]:[<destination IP
address>]:[<MTU>]: [<state>];
5. Configure the default static route
Refer to instructions in Configuring static routes in MGW Rel.4. For
O&M connections you must configure the default route from the OMU
Ethernet interface subnetwork to the IP address of the next hop gateway
(NetAct).

Example 1. Configuring OMU during MGW integration

1. Remove the preconfigured IP address.


ZQRN:OMU:EL0:192.168.1.1,,DEL;
2. Add a new IP address to OMU.
OMU is configured as 2N redundant unit, so the logical address is added to the active unit's EL0
interface.
ZQRN:OMU:EL0:10.20.41.130:24;
3. Create the default static route as shown in the example Creating the default static route for
OMU.

Example 2. Adding IP address to ISU during MGW integration

This example shows how to add a new logical IP address to the ISU unit with
index 0 during MGW Rel.4 integration. IPv4 is used. The logical IP address of
EL0 interface is set to 10.33.1.19/24. The state of the interface is set to UP.
ZQRN:ISU,0:EL0:10.33.1.19,L:24:::UP;
ZQRN:ISU,1:EL0:10.33.1.19,L:24:::UP;
Note that the logical IP addresses configured for EL0 and EL1 interfaces of the
ISU unit must be different from each other.

6-108933Issue 1-0 © Nokia Oyj 187 (201)


User Plane Resource creation in MGW

Example 3. Adding IP address to TPG in IPv6

This example shows how to add a new IP address to the TPG-0 unit's Ethernet
interface IFETH0 in IPv6.
ZQ6N:TPG,0:IFETH0:"2001:490:
FF0:0001:0000:0000:0000:0001",:64:::UP:;

C4) Configuring internal connections for IP-NIU

The IPFE/IPFEP/IPGE/IPGEP/IPGO/IPGOP unit is used for Ethernet


connections to IP backbone. Internal ATM resources between units are created
automatically when the unit is set to working state.

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). Give the name of the unit for the unit
type parameter.
ZUSI:<unit type>;
2. Configure logical IP address for Ethernet interface of the unit
(QRN/Q6N)
The Ethernet interface for internal connections is configured for the
IPFE/ IPFEP/IPGE/IPGEP/IPGO/IPGOP unit. Give value IFETH to the
interface name parameter and value L to the IP address
type parameter.
• In IPv4, give the command
ZQRN:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>, [<point to
point interface type>]:[<IP address>],[<IP address
type> ]:[<netmask length>]:[<destination IP address>]:
[<MTU>]: [<state>];
• In IPv6, give the command
ZQ6N:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>: [<IP address>],
[<IP address type>]:[<prefix length>]:[<destination IP
address>]:[<MTU>]: [<state>];
3. Configure the IP stack in the other end
Configure IP addresses for the interfaces of the computer unit which is
connected to the IP-NIU (for example, TPG), if you have not yet
configured them. Refer to instructions in Configuring IP stack in a
functional unit of MGW Rel.4.
You need to create an own AI interface for each TPG. For IPv4, the IP
address of the AI interface must be unnumbered. For IPv6, the IP address

6-108933Issue 1-0 © Nokia Oyj 188 (201)


User Plane Resource creation in MGW

must be the same as IFETH0's address and the destination address must
be the same as the TPG's IP address.
4. Configure the default static route for IP-NIU
If you have not yet configured the default static route from the functional
unit to IP-NIU, configure it now. Refer to instructions in Configuring
static routes in MGW Rel.4.

C5) Configuring ESA12

The purpose of this procedure is to configure the ESA12 Ethernet switch.

1. Establish a telnet connection to ESA12


a. Enter the preconfigured IP address to ESA12 (the default IP
address is 192.168.1.9). telnet <ip address of ESA12>
b. Enter your login ID and password.
The default password is empty, that is, press Enter to continue.
If you have already changed your password during commissioning,
enter your new password.

Expected outcome
The main menu of ESA12 opens:

2. Press 1 to select General Configuration from the menu


The General Configuration menu shows the current settings.

6-108933Issue 1-0 © Nokia Oyj 189 (201)


User Plane Resource creation in MGW

Expected outcome
The General Configuration menu is printed on the command line.

3. Press the number of the parameter you want to change

Expected outcome
The selected parameter row with the current settings is printed below the menu.
4. Use the backspace key to remove the current parameter value
5. Enter the new value for the parameter and press Enter

Expected outcome
The General Configuration menu is printed on the command line. The menu
shows the new settings.

Note
The session is interrupted immediately after you change the IP address. Change
the IP address only after having changed all other parameters.

Example 4. Changing the default gateway in ESA12

This example shows how to change the default gateway in ESA12.


1. Establish a telnet connection to ESA12. In this example, the password
has not been changed yet.
telnet 192.168.1.9
Username:nokia
Password:
2. Press 1 to select General Configuration in the main menu.
3. Press 3 to select Default Gateway. The current address is displayed on the
command line:

6-108933Issue 1-0 © Nokia Oyj 190 (201)


User Plane Resource creation in MGW

Default Gateway : 192.168.1.1


4. Use the backspace key to remove the current parameter value.
5. Enter the new value for the parameter and press Enter:
Default Gateway : 10.1.1.2

The new value is shown in the General Configuration menu:

C6 Configuring NEMU for DCN in MGW Rel.4

The purpose of this procedure is to configure NEMU for DCN (Data


Communication Network).

1. Open the remote management application for NEMU


Enter the preconfigured IP address of the NEMU to target address. Use
the default administrator user IDs and passwords. It is recommended to
change the default user ID and/or password immediately after the first
login, for information security reasons.
2. Define the IP address for NEMU according to the IP plan
The initial IP configuration has to be done locally. You only need to
configure the IP address and the subnetwork mask of NEMU. Initial
configuration can also be done via the remote management application,
when preconfigured IP addresses are in use in NEMU.
Note that you must shut down and restart the computer before the new
settings will take effect.
a. Select Start - Settings - Network and Dial-Up Connections.
b. Open Local Area Connection and click Properties.
c. Select Internet Protocol (TCP/IP) and click Properties.
d. Enter the IP address, subnet mask and default gateway.
e. Click OK - OK - Close to apply the changes.
f. Repeat steps a to e for the second Local Area Connection.
g. When prompted, click YES to restart the computer.
3. Define the DNS name for NEMU
Configure the DNS client data as follows:
a. Select Start - Settings - Network and Dial-Up Connections.
b. Open Local Area Connection and click Properties.

6-108933Issue 1-0 © Nokia Oyj 191 (201)


User Plane Resource creation in MGW

c. Select Internet Protocol (TCP/IP) and click Properties - Advanced -


DNS.
d. Add the address(es) of the DNS server(s) and set the search order,
if necessary.
e. Click OK - OK - Cancel - Close to apply the changes.
f. Repeat steps a to e for the second Local Area Connection.
g. Select Start - Settings - Control Panel.
h. Open System and select Network Identification - Properties.
i. Enter the name of the computer and click More.
j. Enter the primary DNS suffix.
k. Click OK - OK - OK to apply the changes.
l. When prompted, click YES to restart the computer.
4. Close the remote management application
5. Refresh the DHCP client of the computer
Refreshing of the DHCP client of the computer depends on the operating
system:
• In Windows NT/2000:
a. Open the Command Prompt from the Start/Programs menu
b. Enter ipconfig /release and press Enter.
c. Enter ipconfig /renew and press Enter.
• In Windows 95/98:
a. Open the Command Prompt from the Start/Programs menu
b. Enter winipcfg /release_all and press Enter.
c. Enter winipcfg /renew_all and press Enter.
• In other operating systems, refer to the instructions for the system.

Verification
If DHCP is enabled (instead of static IP addresses), you can check the
accessibility of ESA12 after the DHCP client has been refreshed. Open a new
connection to ESA12 using the new address.

C7) Connecting to O&M backbone via Ethernet

This procedure describes how to connect MGW to the external network for
O&M connections using an external router connected to the ESA12 Ethernet
switch.

6-108933Issue 1-0 © Nokia Oyj 192 (201)


User Plane Resource creation in MGW

Figure 11. Ethernet connection for O&M traffic

O&M connections from the MGW to the O&M backbone can also be created
via ATM virtual connections, but Ethernet is the preferred way. The O&M
connection via ATM should only be used as a backup.

Note
Even if the IP over ATM connection has been configured, the O&M traffic does
not automatically switch to using it when the Ethernet connection is down.

Before you start


Because the IP addresses for OMU, ESA12 and NEMU have been
preconfigured in the MGW, you must first change the IP addresses. Several
elements in the network can have the same preconfigured IP addresses, so if
you do not change the preconfigured addresses, there will be problems in the
network.

Steps

6-108933Issue 1-0 © Nokia Oyj 193 (201)


User Plane Resource creation in MGW

1. Connect the network element physically to the external router via ESA12
Ethernet switch
Connect the router to the ESA12 switch.
2. Configure the external router according to instructions provided by the
router vendor

C8) Connecting MGW Rel.4 to external network via ATM virtual connections

Note that for O&M connections the preferred way of connecting to the NetAct
is via Ethernet (see Connecting to O&M backbone via Ethernet). The
connection via ATM should only be used as a backup.

Note
Even if the IP over ATM connection has been configured, the O&M traffic does
not automatically switch to using it when the Ethernet connection is down.

Figure 12. IP over ATM connection for O&M traffic

Before you start

6-108933Issue 1-0 © Nokia Oyj 194 (201)


User Plane Resource creation in MGW

ATM resources for O&M connections need to be created before this procedure
is commenced. For instructions on how to create ATM resources for O&M
connections, refer to Creating ATM resources for Iu-CS interface in ATM
Resource Management for more details.

1. Start the MMI Window from the Element Manager


Refer to Using EM MMI window in Element Manager Administration for
further instructions.
2. Interrogate IP over ATM interfaces (QMI)
Check that the units for which you are going to create network interfaces
are in working state (WO-EX).
ZQMI:[<unit type> | all def],[<unit index> | all def]:
[<logical/physical unit> | both def]:[<IP interface> |
all def]:<ATM interface> | all def],[<VPI> | all def],
[<VCI> | all def]:[<interface type> | all def]:
[<state> | all def];
3. Configure IP over ATM interface to the functional unit (QMF)
ZQMF:<unit type>,[<unit index>],<logical/physical
unit>:<IP interface>:<TPI>:[<encapsulation method>],
[<usage | IPOAM def>];
4. Assign IP addresses to the interfaces (QRN/Q6N)
Defining the destination IP address creates a static route in the routing
table for the IP interface.
• In IPv4, give the command
ZQRN:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>, [<point to
point interface type>]:[<IP address>],[<IP address
type> ]:[<netmask length>]:[<destination IP address>]:
[<MTU>]: [<state>];
• In IPv6, give the command
ZQ6N:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>: [<IP address>],
[<IP address type>]:[<prefix length>]:[<destination IP
address>]:[<MTU>]: [<state>];
5. Configure the default static route
Configure the default route for O&M connections from OMU to the IP
address of the gateway that is on the other side of the point-to-point ATM
connections (NetAct router). Refer to instructions in Configuring static
routes in MGW Rel.4.

C9) Connecting MGW Rel.4 to external network via IP-NIU

The IPFE/IPFEP/IPGE/IPGEP/IPGO/IPGOP unit is used for Ethernet


connections to the IP backbone.

6-108933Issue 1-0 © Nokia Oyj 195 (201)


User Plane Resource creation in MGW

Before you start


The internal connections for IP-NIU must be configured before external
connections. Refer to instructions in Configuring internal connections
for IP-NIU.

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). Give the name of the unit for the unit
type parameter.
ZUSI:<unit type>;
2. Assign IP addresses to the interfaces (QRN/Q6N)
If the MGW is connected both to IPv4 and IPv6 networks, you must add
both addresses.
• In IPv4, give the command
ZQRN:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>, [<point to
point interface type>]:[<IP address>],[<IP address
type> ]:[<netmask length>]:[<destination IP address>]:
[<MTU>]: [<state>];
• In IPv6, the destination IP address must be given for point-to-point links
(AA and AI interfaces).
ZQ6N:<unit type>,[<unit index...> | [<unit group>,
<unit index...>]]:<interface name...>: [<IP address>],
[<IP address type>]:[<prefix length>]:[<destination IP
address>]:[<MTU>]: [<state>];
3. Configure the default static routes for IP-NIU
Create default static routes from IP-NIU to the external destination (for
example, a router). Refer to instructions in Configuring static routes in
MGW Rel.4.

C10) Configuring static routes in MGW Rel.4

Static routes are used when dynamic routing (for example, OSPF) does not
provide any useful functionality over the static routes. In other words, they are
used when configuring a simple static route achieves the same objective as
using the more complicated dynamic routing. Static routes can be used with
dynamic routing when creating a host route to a host that does not run dynamic
routing. Also, default routes are done with static routes.

Before you start


You must create the default static route in the unit to define a default gateway

6-108933Issue 1-0 © Nokia Oyj 196 (201)


User Plane Resource creation in MGW

for IP connections. If the default route cannot be used, you need to delete the
default route and create other routes.

Note
You can only configure one default route for each unit.
In MGW Rel.4 static routes can be configured for the following units:
• OMU
To establish O&M connections.
• ISU
To establish signalling and control connections (SIGTRAN, H.248
control, IWF/CDS control).
• TPG
To establish Nb interface user plane (RTP) connections within the IP backbone
and to establish Nokia IP Trunk user plane connections to the MSC. When
establishing the Nb interface user plane (RTP) connections, static routes must
be configured for all TPG units since TPG units are not differentiated according
to the type of traffic that they handle (ATM/IP traffic).

1. Configure the default static route


2N redundant units must both have the same default static route to the
same IP address. You do not need to specify the destination IP address
for the default route.

Note
If you cannot use the default route, see the next step.

• In IPv4, give the command


ZQRC:<unit type>,[<unit index...> | [<unit
Group>,<unit index...>]]::GW:IP:IP=<IP address>;
• In IPv6, give the command
ZQ6C:<unit type>,[<unit index...> | [<unit
group>,<unit index...>]]:[<destination IP address>],
[<prefix length>]:[<next hop type>]: <address
type>:IP=<ip address>;
2. If the default route cannot be used
Delete the default static routes (QRD/Q6D)
• In IPv4, you can delete the route by identifying it by its route number.
You can obtain the route number with the QRL command.
ZQRD:(<route number>:<unit type>,[<unit index...> |
[<unit group>,<unit index...>]]);

6-108933Issue 1-0 © Nokia Oyj 197 (201)


User Plane Resource creation in MGW

• In IPv6, give the command


ZQ6D:<unit type>,[<unit index...> | [<unit
group>,<unit index...>]]:[<destination IP address>:
(<address type>):IP=<ip address>;
3. Create new static routes (QRC/Q6C)
This step is only required if the default route cannot be used and a new
route has to be created, or if more routes are needed.
• In IPv4, give the command
ZQRC:<unit type>,[<unit index...> | [<unit
group>,<unit index...>]]:[<destination IP address>],
[<netmask length>]:[<next hop type>]: <address
type>:IP=<ip address>;
• In IPv6, give the command
ZQ6C:<unit type>,[<unit index...> | [<unit
group>,<unit index...>]]:[<destination IP address>],
[<prefix length>]:[<next hop type>]: <address
type>:IP=<ip address>;

Example 5. Creating the default static route for ISU

You do not need to give the destination IP address and netmask length when
configuring default routes. Set the next hop type to default, which is GW, and
the address type to IP. The IP address of the gateway is 10.33.1.1.
ZQRC:ISU,0::GW:IP:IP=10.33.1.1;

Example 6. Creating the default static route for OMU

The same default route is used for both OMU-0 and OMU-1.
ZQRC:OMU,0::GW:IP:IP=10.20.41.1;
ZQRC:OMU,1::GW:IP:IP=10.20.41.1;

Example 7. Creating the default static route for TPG in IPv6

This example creates the default static route for the TPG-0 unit.
Q6C:TPG,0::GW:IP="2001:490:
FF0:0001:0000:0000:0000:0001":;

C11) Configuring NEMU to MGW Rel.4

The EMT connection requires that NT registry includes the IP address of OMU
and the user ID and password of the network element. The user ID and

6-108933Issue 1-0 © Nokia Oyj 198 (201)


User Plane Resource creation in MGW

password have been defined in the network element for the EMT connection.
The IP address of the NEMU and the FTP username and password also have to
be defined for measurement bulk data transfer. Any NEMU username and
password can be used for NEMU FTP.

Note
The network element must have a user ID that the EMT connection can use.

Note
If the parameters are changed, you must restart Platform Manager.

1. Change the IP address of OMU


Change the szIPAddress parameter. The registry address for the
parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\OMU
\CurrentVersion\settings\szIPAddress
2. Change the network element username
Change the szEMTUserName parameter. The registry address for the
parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\OMU
\CurrentVersion\settings\szEMTUserName
3. Change the network element password
Change the szEMTPassword parameter. The registry address for the
parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\OMU
\CurrentVersion\settings\szEMTPassword
4. Change the OMU FTP username
Change the szFTPUserName parameter. The registry address for the
parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\OMU\CurrentV
ersion\settings\szFTPUserName
5. Change the OMU FTP passwordChange the szFTPPassword parameter.
The registry address for the parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\OMU
\CurrentVersion\settings\szFTPPassword

6-108933Issue 1-0 © Nokia Oyj 199 (201)


User Plane Resource creation in MGW

6. Change the IP address of NEMU


Change the szIPAddress parameter. The registry address for the
parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\NEMU
\CurrentVersion\settings\szIPAddress
7. Change the NEMU FTP username
Change the szFTPUserName parameter. The registry address for the
parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\NEMU
\CurrentVersion\settings\szFTPUserName
8. Change the NEMU FTP password
Change the szFTPPassword parameter. The registry address for the
parameter is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\NEMU
\CurrentVersion\settings\szFTPPassword
9. Change NEMU hostname in the registry
Change the szNemuID parameter. The registry address for the parameter
is:
HKEY_LOCAL_MACHINE\Software\Nokia\NEMU
\InstalledModules\System\Network\CUAccess\NEMU
\CurrentVersion\settings\szNemuID
10. Restart PlatformManager to activate new parameter values
a. Start the NEMU Platform Manager User Interface from Start
-Programs - Nemu Platform Manager User Interface - pmui.
b. Press Stop PM.
c. Wait until the status of the PM is ''Platform Manager not running'.
d. Press Start PM.
e. Wait until the status of PM is 'Nemu software Running'.
f. Close the NEMU Platform Manager User Interface.

6-108933Issue 1-0 © Nokia Oyj 200 (201)


User Plane Resource creation in MGW

References
• Multimedia Gateway Rel. 4 Integration

6-108933Issue 1-0 © Nokia Oyj 201 (201)