AirScale BSC 19, Operating

Documentation, Issue 03

Configuring IP interfaces
DN194299879
Issue 03
Approval Date 2019-01-25
 Configuring IP interfaces

The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).

This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.

Copyright © 2019 Nokia. All rights reserved.

f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.

2 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces

Table of Contents
This document has 80 pages

Summary of changes..................................................................... 7

1 Configuring SIGTRAN for the A interface...................................... 8

1.1 Signaling overview......................................................................... 8
1.1.1 SIGTRAN architecture................................................................... 8
1.1.1.1 SIGTRAN protocol stack................................................................ 8
1.2 Activating, testing, and deactivating SIGTRAN..............................9
1.2.1 Activating SIGTRAN for the A interface....................................... 10
1.2.2 Testing SIGTRAN in the A interface.............................................15
1.2.3 Deactivating SIGTRAN in the A interface.................................... 17

2 Configuring Packet Abis ..............................................................19

2.1 Packet Abis overview................................................................... 19
2.2 Activating Packet Abis..................................................................19

3 Configuring the Gb interface........................................................ 23

3.1 Creating and activating the Gb interface over IP......................... 23
3.2 Testing the activation of Gb over IP............................................. 27
3.3 Modifying the remote IP endpoint signaling and data weight.......28
3.4 Modifying the NS-VL name.......................................................... 29
3.5 Deactivating and testing Gb over IP.............................................29

4 Configuring the NTP interface......................................................32

4.1 Overview...................................................................................... 32
4.2 Configuring NTP...........................................................................32

5 Configuring the optional interfaces...............................................35

5.1 Configuring the BSC-BSC interface............................................. 35
5.1.1 Activating the BSC-BSC interface................................................35
5.1.1.1 Creating and activating the IP configuration................................ 36
5.1.1.2 Creating and activating M3UA configuration................................36
5.1.1.3 Creating and activating the SCCP configuration..........................39
5.1.2 Defining LAC-to-SPC mapping table............................................44
5.1.3 Testing the BSC-BSC interface.................................................... 44
5.1.4 Solving BSC-BSC interface activation failures.............................45
5.1.5 Deactivating the BSC-BSC interface............................................45
5.1.5.1 Deactivating the BSC-BSC interface............................................45
5.1.5.1.1 Deactivating and removing the SCCP configuration.................... 46
5.1.5.1.2 Deactivating and removing the M3UA configuration.................... 47
5.2 Configuring the BSC-CBC interface.............................................49
5.2.1 Overview of BSC-CBC integration............................................... 49
5.2.2 Preliminary tasks in CBC integration............................................49
5.2.3 Setting up the OSI subnetwork.................................................... 50

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 3

 Configuring IP interfaces

5.2.3.1 Creating network services............................................................50

5.2.3.1.1 Enabling OSI over TCP/IP network service................................. 50
5.2.3.1.2 Creating OSI over TCP/IP network service (CONS).................... 51
5.2.3.2 Creating NSAP addresses........................................................... 51
5.2.3.2.1 Creating CONS NSAPs................................................................51
5.2.3.2.2 Creating CLNS NSAPs ............................................................... 52
5.2.3.2.3 Creating OSI over TCP/IP NSAPs............................................... 52
5.2.3.3 Creating network addresses........................................................ 53
5.2.3.4 Attaching NSAPs to network addresses...................................... 53
5.2.3.5 Creating OSI applications............................................................ 54
5.2.4 Activating and testing the CBC connection.................................. 55
5.2.5 Deactivating the CBC connection................................................ 56
5.3 Configuring the Lb interface......................................................... 57
5.3.1 Activating and testing the Lb interface to AirScale BSC.............. 57
5.3.1.1 Configuring the network before activating the Lb interface to
AirScale BSC............................................................................... 57
5.3.1.2 Activating the standard Lb interface.............................................61
5.3.1.3 Activating the standard Lb interface and Support for Uplink Time
Difference of Arrival......................................................................62
5.3.2 Activating and configuring geo-redundant SMLC over multi-homed
Lb interface.................................................................................. 62
5.3.3 Testing Lb interface to AirScale BSC........................................... 66
5.3.4 Deactivating and testing the Lb interface to BSC.........................67
5.4 Configuring the VNP interface......................................................69
5.4.1 Activating SIGTRAN for the AirScale BSC-VNP interface........... 70
5.4.2 Testing SIGTRAN for the AirScale BSC-VNP interface............... 76
5.4.3 Deactivating SIGTRAN in the AirScale BSC-VNP interface........ 78

4 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces

List of Figures
Figure 1 SIGTRAN protocol stack...................................................................... 8
Figure 2 Example configuration of SIGTRAN for the A interface......................10
Figure 3 IP connection between the AirScale BSC and the SGSN.................. 23
Figure 4 NTP server overview.......................................................................... 32
Figure 5 Protocol stack of the BSC-BSC interface........................................... 35
Figure 6 Protocol stack in the VNP interface.................................................... 70
Figure 7 Signaling point and IP addressing for a sample configuration network..
70

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 5

 Configuring IP interfaces

List of Tables
Table 1 SIGTRAN protocol stack...................................................................... 9
Table 2 SCTP association status.................................................................... 15
Table 3 Broadcast group types used in SCCP broadcast status handling...... 43
Table 4 SCTP layer status...............................................................................76

6 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Summary of changes

Summary of changes
Describes the changes between releases.

Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issues 03 AirScale BSC 19 and 02 AirScale BSC 19
Creating and activating the Gb interface over IP

• Added note related to local UDP port number under NSE creation using both static
and dynamic IP configurations.

Changes between issues 01 AirScale BSC 19 and 02 AirScale BSC 19

Overview

• Updated the figure NTP server overview based on the PCUM synchronization
architecture change. Made a connection between NTP server and PCUMs. Also
removed connection between MCUM and PCUMs.

Configuring NTP

• Added a step to configure IP routes towards NTP server from PCUM (QKC).

Activating SIGTRAN for the A interface

• Added a note related to OMUSIG in step 5.

Activating Packet Abis

• Added a note related to OMUSIG and TRXSIG.

Creating and activating the Gb interface over IP

• Removed reference to DNS. Also, removed a reference to RHOST.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 7

Configuring SIGTRAN for the A interface Configuring IP interfaces

1 Configuring SIGTRAN for the A interface

Configuration steps for the A interface.

1.1 Signaling overview

Overview of Signaling transport (SIGTRAN), which is used to transport SS7 signals over
the internet.

Signaling transport (SIGTRAN) is the standard telephony protocol used to transport SS7
signals over the internet. The SS7 signals consist of commands for handling a telephone
call. An operator transmits the SS7 signals to a signaling gateway and the gateway
converts the signals to SIGTRAN packets for transmission over IP. The SIGTRAN
protocol is made up of several components (a protocol stack)—standard IP, a common
signaling transport protocol such as Stream Control Transport Protocol (SCTP), and user
adaptation layers such as the MTP3 User Adaptation Layer (M3UA) and the Q.921 User
Adaptation (IUA) layer.
SIGTRAN is configured with resilience functionality like SCTP multi-homing together with
heartbeat mechanism. Usage of redundant routes and duplicated backbone elements
provide resilience for QoS aware IP network. Signaling is assigned to high priority class
for IP routers and sufficient amount of transmission capacity is ensured for the high
priority class.

1.1.1 SIGTRAN architecture

Describes the SIGTRAN architecture.

This section describes the various protocols, which constitute a SIGTRAN stack.

1.1.1.1 SIGTRAN protocol stack

Protocols used in a SIGTRAN stack.

The Figure 1: SIGTRAN protocol stack illustrates the SIGTRAN protocol stack.

Figure 1 SIGTRAN protocol stack

8 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring SIGTRAN for the A interface

Table 1: SIGTRAN protocol stack describes the protocols and adaptation layers used in
the SIGTRAN protocol stack.
Table 1 SIGTRAN protocol stack
Protocol/adaptation layer Description
IP Internet Protocol
Stream Control Transmission Protocol (SCTP) SCTP is a message-oriented protocol and
ensures reliable, in-sequence transport of
messages. Provides multi-homing and
redundant paths to increase resiliency and
reliability.
M3UA It supports the transport of any SS7 MTP3-user
signaling over IP, using the services of the
SCTP. The protocol is used to communicate
between a signaling gateway (SG) and a media
gateway controller (MGC) or IP-resident
database.
Signaling Connection Control Part (SCCP) The SCCP layer of the SS7 stack provides
connectionless and connection-oriented
network services above MTP Level 3. The
connection-oriented service is used for virtual
connections between network elements, and it
provides the procedures for establishing and
releasing of those virtual connections. The
connectionless service enables non-call-related
communication between network elements,
which have to exchange information only for
short periods. Furthermore, the connectionless
service provides a global title translation
function that enables communication with
network elements in other signaling networks.

1.2 Activating, testing, and deactivating SIGTRAN

Activating, testing, and deactivating SIGTRAN for the A interface.

SIGTRAN for the A interface is activated in the AirScale BSC. Because of signaling
capacity and redundancy requirements, the SIGTRAN association must be configured in
at least two Base Station Control Units (BCXU) in the AirScale Base Station Controller
(BSC).
The Figure 2: Example configuration of SIGTRAN for the A interface illustrates the IP
addressing details for a sample configuration with symmetric network layout. The two
BCXU-AirScale BSC pair configurations are only examples. Create SIGTRAN
associations for at least two BCXUs and for as many BCXUs as needed for signaling
capacity.

g Note: A BCXU which has SIGTRAN associations cannot be removed in the scale-in
operation. Therefore, it is recommended that SIGTRAN associations will not be created
for all BCXUs if a need for scaling-in is foreseen.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 9

Configuring SIGTRAN for the A interface Configuring IP interfaces

Figure 2 Example configuration of SIGTRAN for the A interface

ASBSC MSS/MSC
Signalingrouteset
DToRswitchesand
EgdeRouters
ath Int-1
Signalingroute ryp
ma
Pri Association1
Signalinglinkset
IP Backbone Int-2
ry path
Signalinglink Seconda
Computenode
BCXU-0 Prim
Associationset ary
EL 6 Se path
Association1 co
EL 7
nd
ar Int-1
yp
ath Association2

Computenode Int-2
BCXU-1
Gateway IP address
EL 6 ForPrimarypath 10.1.3.33
Association2 ForSecondarypath 10.1.3.49
EL 7

IP path IP address
IP Path Interface IP Address Primary 10.16.143.71/28
Primary BCXU-0EL 6 10.1.3.36/28 10.16.143.72/28
10.1.3.37/28 Secondary 10.16.143.135/28
BCXU-1EL 6
10.16.143.136/28
Secondary BCXU-0EL 7 10.1.3.52/28
BCXU-1EL 7 10.1.3.53/28

1.2.1 Activating SIGTRAN for the A interface

SIGTRAN activation in the AirScale BSC.

Procedure

1 Create logical IP addresses for the BCXUs (QRN) using the following commands.

Assign an IP address to each available Ethernet interface. Multi-homing requires the

allocation of IP addresses from separate subnets in the BCXU.
If a BCXU already has an IP address for the BSC-BSC interface, the same address
can be used at the A interface.
ZQRN:BCXU,0::EL6,:"10.1.3.36",28,L::;
ZQRN:BCXU,0::EL7,:"10.1.3.52",28,L::;
ZQRN:BCXU,1::EL6,:"10.1.3.37",28,L::;
ZQRN:BCXU,1::EL7,:"10.1.3.53",28,L::;

2 Define the local IP address based default gateway (QKM).

Configure a default route as default gateway configuration with a local IP address

(QKM).
As default gateway configuration with a local IP address:
ZQKM:BCXU,0::"10.1.3.36":"10.1.3.33":LOG:;
ZQKM:BCXU,1::”10.1.3.37”:”10.1.3.33”:LOG:;
ZQKM:BCXU,0::”10.1.3.52”:”10.1.3.49”:LOG:;
ZQKM:BCXU,1::”10.1.3.53”:”10.1.3.49”:LOG:;

10 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring SIGTRAN for the A interface

g Note: IP configurations for all functional units are done during VNF instantiation
using CBAM except for SIGTRAN and OMUSIG interfaces in BCXU. See
Instantiating, configuring and integrating AirScale BSC for details.
.

3 Create an association set between the AirScale BSC and the MSS (OYC) using the
following command.

Create an association set for the A interface connection to the MSS. In the
association, the AirScale BSC is the client. The AirScale BSC starts negotiating for
an association and the MSS waits for the negotiation.
ZOYC:AMSS1:C::;

4 Add associations to the AMSS1 association set (OYA) using the following command.

Create associations in the AMSS1 association set. The controlling units of the
association (BCXU-0 and BCXU-1) are in the WO-EX state. The name of the
parameter set is SS7.
ZOYA:AMSS1:BCXU,0:SS7:;
ZOYA:AMSS1:BCXU,1:SS7:;
Check the associations that have been added using the OYI command.

5 Add the SCTP transport addresses to the associations (OYP) using the following
commands.

Add the IP addresses of the sources and destinations to the primary and secondary
IP paths.
ZOYP
:M3UA:AMSS1,0:"10.1.3.36","10.1.3.52",:"10.16.143.71",26,"1
0.16.143.135",26,:;
ZOYP
:M3UA:AMSS1,1:"10.1.3.37","10.1.3.53",:"10.16.143.72",26,"1
0.16.143.136",26,:;

6 Activate the associations (OYS) using the following commands.

Set the associations to the ACT state.

ZOYS:M3UA:AMSS1,0:ACT:;
ZOYS:M3UA:AMSS1,1:ACT:;

7 Create a local signaling point (NRP) using the following command.

ZNRP:NA0,1326,LOCAL:::;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 11

Configuring SIGTRAN for the A interface Configuring IP interfaces

8 Create the IP signaling link set (NSP) using the following command.

Create the signaling link set to the NA0 network. The destination (DX MSS1)
signaling point code is 201 and the link ID is 91.
ZNSP:NA0,201,AMSS1:91:AMSS1:;

9 Create the signaling route set (NRC) using the following command.

Create the signaling route set with the M3UA parameter set (6 IETF M3UA) and
use the highest priority setting (7) for the primary route.
ZNRC:NA0,201,AMSS1,6,,:,,,7::::;

10 Allow the activation of signaling link 91 (NLA) using the following command.

ZNLA:91:;

11 Allow the activation of the signaling route (NVA) using the following command.

ZNVA:NA0,201:;

12 Activate signaling link 91 (NLC) using the following command.

ZNLC:91,ACT:;

13 Activate the signaling route (NVC) using the following command.

ZNVC:NA0,201:,:ACT:;

14 Create the SCCP service (NPC) using the following command.

ZNPC:NA0,3,SCCP:Y:Y,,:;

15 Add the SCCP and the BSSAP subsystems (FE) to the AirScale BSC using the following
commands.

ZNFD:NA0,1326,1:FE,BSSAP,1,:;
ZNFD:NA0,201,1:FE,,1,:;

16 Verify the existing SCCP broadcast and subsystem using the following commands.

For local broadcast:

ZOBL;

12 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring SIGTRAN for the A interface

ZOBH:I:ALBG;
For the signaling point broadcast:
ZOBI;
ZOBH:I:ASBG;
ZOBH:I:CSBG;
If the group ID was not used, reuse it if all of the subsystems and SPCs are fit. If
some exceptional subsystems or SPCs are there in the group, remove it or create a
new group ID.
If the group ID was used, do not reuse it even if all of the subsystems and SPCs are
fit.

17 Configure SCCP broadcast groups (OBH) using the following commands.

Use the following command to configure local broadcast groups:

ZOBH:M:ALBG,1:NA0,201:FE:;
Use the following commands to configure signaling point broadcast groups:
ZOBH:M:ASBG,1:NA0,1326:FE:;
ZOBH:M:ASBG,1:NA0,1326:1:;
ZOBH:M:CSBG,1:NA0,201:;

g Note: ALBG groups are used for local broadcast. If the affected remote signaling
points in the related ALBG group are changed, SCCP broadcasts it to concerned
local subsystems. ASBG and CSBG groups are used for signaling points
broadcast. If the subsystems in the ASBG group are changed, SCCP broadcasts
it to remote signaling points in the CSBG group.

18 Set the local broadcast status of the SCCP subsystem (OBC) using the following
command.

ZOBC:1:NA0,D'254:Y:;

19 Set the broadcast status of the signaling points (OBM).

ZOBM:1:1:Y:;
The broadcast group number is freely chosen when configuring for the first time.
During software upgrades, if the affected subsystem changes, locate the subsystem
first, locate the related ASBG, and then the CSBG is found. Send the notification to
the related signaling points.
Before the modification, always check if there are existing broadcast groups with
specific numbers so that the operator can check if the new one could be added to the
existing groups. Perform the following steps:
a) Find which broadcast group contains the affected subsystem.
ZOBH:I:ASBG;
The execution printout is as follows:

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 13

Configuring SIGTRAN for the A interface Configuring IP interfaces

MEMBERS IN BROADCAST GROUPS OF AFFECTED SUBSYSTEMS FOR SP

BROADCAST

BROADCAST GROUP 1 NETWORK NA0 SUBSYSTEM 01 (H)

------------------------------------------------------------------
------------
1326

BROADCAST GROUP 1 NETWORK NA0 SUBSYSTEM FE (H)

------------------------------------------------------------------
------------
1326

COMMAND EXECUTED
b) Find which broadcast group contains the concerned signaling point.
ZOBH:I:CSBG;
The execution printout is as follows:
MEMBERS IN BROADCAST GROUPS OF CONCERNED SIGNALING POINTS FOR SP
BROADCAST

BROADCAST GROUP 1 NETWORK NA0

------------------------------------------------------------------
------------
0201

COMMAND EXECUTED
c) Find the mapping relation.
ZOBI;

If the operator finds that the subsystems and signaling points in the ASBG and
CSBG groups are the ones needed, reuse the groups. If there are some others that
the operator does not need in the groups, use commands ZOBH:M:ASBG and
ZOBH:M:CSBG to allocate new group numbers.
ZOBH:M:ASBG,2:NA0,1326,FE;
ZOBH:M:CSBG,2:NA0,201;

g Note: For the existing group number, find whether the mapping relation exists or
not. If the mapping relation exists, do nothing. Otherwise, create a new mapping
relation with the command ZOBM:2:2:Y;. For the new group number, create
the new mapping relation with the same command.

20 Change the value of the SCCP fault tolerant timer (OCM) using the following commands.

Set the value of the SSP_FILTER_TIMER parameter to 11 seconds (110 ms) and
the value of the Q714_T_STAT_1ST parameter to 5 seconds (50 ms) taking into
account that the filter transport break lasts at most 6 seconds. The formula for
masking the breaks is the following:
transport break + Q714_T_STAT_1ST < SSP_FILTER_TIMER.
ZOCM:1:25,110;
ZOCM:1:8:50;

14 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring SIGTRAN for the A interface

21 Activate the SCCP (NGC) using the following command.

ZNGC:NA0,201:ACT:;

22 Activate the AirScale BSC subsystems (NHC) using the following command.

ZNHC:NA0,1326:FE:ACT:;

23 Activate the MSC subsystems (NHC) using the following command.

ZNHC:NA0,201:FE:ACT:;

1.2.2 Testing SIGTRAN in the A interface

Testing the configuration state of SIGTRAN in the A interface.

Procedure

1 Check the status of the SCTP layer (OYI).

ZOYI::A;

Table 2 SCTP association status

Association state Explanation Further information
DOWN-BY-USER The initial state of an The operator can
association after it has deactivate this state after
been created with the OYA the last system restart with
command. the OYS command.

SCTP-DOWN • State after system

restart: the MTP
management has not
activated the M3UA
link that corresponds
to the association, and
the M3UA link could
be in the UA-AD state
(activation denied).
• The association has
not been activated
with the OYS
command.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 15

Configuring SIGTRAN for the A interface Configuring IP interfaces

Table 2 SCTP association status (Cont.)

Association state Explanation Further information
• At the server side, the
SCTP-DOWN state can
also mean that there is
a problem in the IP
connection, so the
SCTP association
cannot be activated.
Check the IP
connection with the
QRX ping command.

UP-PROCEEDING The negotiation of the Check the IP connection

SCTP association is with the QRX ping
ongoing. There might be command.
some problems with the IP
connection, so the SCTP
association cannot be
activated.

ASP-DOWN The association is up at -

the SCTP level but down
at the M3UA level. That is,
an ASP management
message exchange is
ongoing. ASPUP (at the
server) or ASPUP ACK (at
the client) has not been
received yet. The M3UA
link is not active.

ASP-INACTIVE-USR If the association is -

inactivated by the operator
(OYS MML), or
association state is
changed by message
interface.

ASP-INACTIVE-SYS If the association is -

inactivated by the system.
ASP-ACTIVE The association is up at -
both the SCTP and the
M3UA levels. The M3UA
link is active.

2 Check the states of the signaling links of the M3UA layer (NLI).

ZNLI;

16 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring SIGTRAN for the A interface

The signaling link should be in the AV-EX state.

3 To interrogate the states of all signaling routes in a given signaling network, execute the
following command.

ZNVI:NA0;
The signaling route should be in the AV-EX state.

4 Use the following command to interrogate all SCCP signaling points data if there is no
signaling network.

ZNFI:NA0:A;
The AirScale BSC and MSC Service Control Points (SCP) should be in the AV-EX
state.

Result

SIGTRAN has been successfully configured for the A interface.

1.2.3 Deactivating SIGTRAN in the A interface

Deactivating SIGTRAN in the A interface.

Purpose
This section describes how to deactivate SIGTRAN (IP transport) in the A interface. Use
the MML commands to execute the steps.

Procedure

1 Deactivate the MSC subsystem (NHC).

ZNHC:NA0,201:FE:INA:;

2 Deactivate the AirScale BSC subsystems (NHC).

ZNHC:NA0,1326:FE:INA:;

3 Deactivate the SCCP states (NGC).

ZNGC:NA0,201:INA;
ZNGC:NA0,1326:INA;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 17

Configuring SIGTRAN for the A interface Configuring IP interfaces

4 Remove SCCP from signaling points (NFR).

ZNFR:NA0,201;
ZNFR:NA0,1326;

5 Deactivate the signaling route (NVC).

ZNVC:NA0,201::INA;

6 Deny the activation of the signaling route set (NVD).

ZNVD::NA0,201;

7 Deactivate the signaling link (NLC).

ZNLC:91,INA;

8 Deny the activation of the signaling link (NLD).

ZNLD:91;

9 Delete the signaling route set (NRD).

ZNRD:NA0,201,AMSC1;

10 Delete the IP signaling link set (NSD).

ZNSD:NA0,201,AMSC1;

11 Delete the local signaling point (NRP).

ZNRP:NA0,1326,LOCAL,DEL;

12 Delete the association set (OYD).

ZOYD:AMSC1;

18 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring Packet Abis

2 Configuring Packet Abis

An efficient way of packet switched transmission.

Packet Abis introduces an efficient way of packet switched based transmission between
the BTS and the AirScale BSC. It enables the transport of Abis information using native
IP over Ethernet networks.

2.1 Packet Abis overview

An short overview of packet abis overview.

The operator is able to employ Packet Switched Network (PSN) to provide the transport
backhaul for the Abis traffic, offering significant OPEX savings because of the cost
effective physical media (Ethernet) and the simplified operation and maintenance of the
network that can then be derived. In addition to the physical media benefit, Packet Abis
also offers significant bandwidth savings compared to Pseudo Wire Emulation (PWE)
based packet transport because it introduces a very efficient and fully integrated Abis
optimization capability. The integrated Abis optimization also facilitates the introduction of
high bandwidth features such as Optical Supervisory Channel (OSC) without necessarily
increasing the backhaul bandwidth requirement. Bandwidth can be shared by CS, PS,
and signaling traffic. There are no predefined limitations except the total available
bandwidth provided by the physical link.
Abis bandwidth benefits are achieved by performing the following:

• Removing the unnecessary bits and header information from TRAU/PCUM frames
• Unreserving bandwidth reserved for unused channels
• Pooling all traffic to the same bandwidth (multiplexing gain)
• RTP multiplexing of CS and PS traffic
• Aggregation

2.2 Activating Packet Abis

Activating and configuring the Packet Abis signaling.

Before you start

Ensure the following:

• The IUA feature must be ON to create the association set to OMUSIG and TRXSIG.
The feature code is 899.
• IPv4 addresses and subnets are planned.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 19

Configuring Packet Abis Configuring IP interfaces

Procedure

1 Check the license state of the features with the W7I command.

Execute the following command for Packet Abis over Ethernet:

ZW7I:FEA:FEA=1533,;
Execute the following command for IUA:
ZW7I:FEA:FEA=899,;

2 Enter the following command to activate the license if the license is not active.

ZW7M:FEA=<featurecode>:ON;

3 Configure the OMUSIG IP and the TRXSIG IP endpoints to the BCXUs.

CBAM configures the interfaces for OMUSIG (EL4) and TRXSIG (EL5) in BCXU
FUs. CBAM also configures IP address, gateway address, and tag for TRXSIG
interfaces. The user can configure IP address, gateway address, and tag for
OMUSIG interfaces.

g Note:
• The OMUSIG IP address is the same as configured in the BCF SCF, see
parameter mPlaneRemoteIpAddress in step 5.
• A BCXU which has OMUSIG interface cannot be removed in the scale-in
operation. Therefore, it is recommended that OMUSIG interfaces are not
created for all BCXUs if a need for scaling-in is foreseen.

Sub-steps

a) Configure OMUSIG DIffServ.

By default, the OMUSIG packet has DSCP value 0 meaning Best Effort. Based
on Quality of Service policy, the DSCP value may have to be changed. The
change is done with the CONFIGURE PORT-BASED CLASSIFICATION AND
MARKING command Q8N.
ZQ8N:PROTOCOL:<PORT NUMBER SOURCE>: <PORT NUMBER
DESTINATION>:DSCP VALUE;

g Note: Default DSCP values for OMUSIG and TRXSIG are used when BCF and
TRX are created. ASBSC creates OMUSIG and TRXSIG automatically when
BCF/TRX is created. The DSCP mapping configuration for OMUSIG or TRXSIG
can be modified by the user as currently with ZQ8N MML command, if needed.

Step example

The DSCP value of SCTP traffic between Source and Destination port 49152 is
changed to AF11 (001010) (10 decimal):
ZQ8N:132:49152,:49152,:10;

20 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring Packet Abis

g Note: Each protocol is identified by a number in the MML interface. By entering

“?”, the protocol mapping is displayed. In the example above, “132” stands for
SCTP. The DSCP value should be defined for the SCTP port used for OMUSIG.
To enable the DiffServ in the BCF also, the AirScale BSC level TRAFFIC TO
DSCP MAPPING parameters ACP, AMP, CLKS, SS have to be configured.
Example:
ZEEY:ACP=46;

b) Create the SCTP association.

g Note: The SCTP association is created automatically during BCF and TRX
creations.

c) Create logical IP address for OMUSIG in BCXU FUs.

Step example

ZQRN:BCXU,0::EL4:"10.55.85.167",26,L;

d) Create tag for OMUSIG interface.

Step example

ZQRP:BCXU,0::EL4:"10.55.85.167":TAG,"OMUSIG":;

e) Define the local IP address based default gateway.

Step example

ZQKM:BCXU,0::"10.55.85.167":"10.55.85.129":LOG;

4 Configure the ETME Abis u-plane interface.

This step is executed only once when the packet Abis interface is created.

Sub-steps

a) Configure the u-plane UDP port.

ZEEY:<CS UDP MUX PORT>,<PS UDP MUX PORT>;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 21

Configuring Packet Abis Configuring IP interfaces

The CS and PS u-plane packets are differentiated with the AirScale BSC level
UDP port numbers. The CS and PS UDP ports must be different.

Step example

ZEEY:CSUMP=49152,PSUMP=49154;

b) Configure the u-plane Diffserv.

The u-plane DiffServ is configured with the AirScale BSC level TRAFFIC TO
DSCP MAPPING parameters ABIS U-PLANE CS TO DSCP MAPPING
(AUCS) or ABIS U-PLANE PS TO DSCP MAPPING (AUPS).

Step example

ZEEY:AUCS=46;

5 Configure Packet Abis over Ethernet related BCF SCF parameters.

• mPlaneLocalIpAddress: Provides the BTS IPv4 address used for m-plane.

• mPlaneRemoteIpAddress: Provides the m-plane IPv4 address of AirScale
BSC.
• mPlaneGatewayIpAddress: If the m-plane destination IP address belongs to
another subnet, this IP address specifies the address that is used to route the m-
plane traffic to the destination. It is also named as next hop IP address.
• mPlaneSubnetMask: Provides the subnet mask related to the BTS IPv4
address for m-plane. The value specifies the amount of bits that are set in the
mask value; for example, 255.255.255.0 leads to a value of 24.
• cuPlaneGatewayIpAddress: If the cu-plane destination IP address belongs
to another subnet, this IP address specifies the address that is used to route the
cu-plane traffic to the destination. It is also named as next hop IP address.
• minSctpPort: Specifies the start of the local SCTP port space that can be
used for each instance of the Abis interface. This SCTP port is used for
OMUSIG, and the SCTP ports for TRXSIG are in the following order:
a) TRXSIG1 minSctpPort+1
b) TRXSIG2 minSctpPort+2
c) TRXSIG3 minSctpPort+3

• SCTP parameters for the OMUSIG: minRTO, maxRTO, initRTO,

periodSACK, hbInterval, maxRetransPath, maxRetrans Assoc,
ackTimerIUA, and bundlingEnabled.

g Note: When the Packet Abis interface is configured, the user can create BCFs
and other radio network objects. See the
Administering Radio Network for AirScale BSC document for details.

22 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the Gb interface

3 Configuring the Gb interface

Steps to configure the Gb interface.

3.1 Creating and activating the Gb interface over IP

Steps to activate the Gb interface.

Purpose
The Gb interface between the AirScale BSC and SGSN is established in three phases:
configuring the IP address, configuring the network service (NS) layer, and enabling
GPRS. The system builds the base station system GPRS protocol (BSSGP) virtual
connections automatically when GPRS is enabled on cell level. Figure 3: IP connection
between the AirScale BSC and the SGSN illustrates this concept.

Figure 3 IP connection between the AirScale BSC and the SGSN

Before you start

• In static IP configuration, it does not matter which end of the interface is configured
first.
In dynamic IP configuration, first configure the SGSN end of the interface. This is
because the AirScale BSC attempts to run the size and configuration procedures
immediately after creating the IP network service virtual link (NS-VL).
• Configuration of the PCUM IP stack is handled with the commands of command
group QR.
• If the operator wants to activate EQoS/EC-GSM IOT MODE/eDRX in the AirScale
BSC, activate it before creating the Gb interface. If the operator wants to activate Gb
over IP first, reset the network service entities (NSEs) manually. The system resets
the NSEs when EQoS/EC-GSM IOT MODE/eDRX is deactivated.
• No separate activation is required for Gb over IP for Satellite Connection; but to use
it, set the TGB_RESUME parameter to the value 3C using the MML command WOC.
Otherwise the GPRS resume does not work properly, and the MS has to initiate the
Routing Area Update Request procedure to the SGSN after every dedicated
connection (a CS call, an SMS) to finish the GPRS suspension procedure. Note that
the parameter change takes effect in the whole AirScale BSC.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 23

Configuring the Gb interface Configuring IP interfaces

• It is recommended to set the TNS-test Timer (NTT) parameter value to

maximum 10 seconds at SGSN.

Procedure

1 Check the Gb over IP feature state (W7I) using the following command.

ZW7I:FEA:FEA=7,;

2 Set the Gb over IP feature state to ON if needed (W7M) using the following command.

ZW7M:FEA=7:ON;

3 Check that the feature state change of Gb over IP succeeded (W7I) using the following
command.

ZW7I:FEA:FEA=7,;

4 Create network interfaces (QRA) using the following command.

Interfaces must be created to all PCUMs (also spare units).

ZQRA :<unit type>,<unit index>::<interface name>::;

Step example

ZQRA:PCUM,0::EL4:;

g Note: CBAM creates the interface but the user configures IP address and
routing.

5 Configure IP addresses (QRN) using the following command.

g Note: The user does not give this MML command because the interface is
created by CBAM.
Use logical IP addresses in both dynamic and static configuration.
ZQRN :<unit type>,<unit index>::<interface name>:"<IP
address>",<netmask length>,<L/P>::;

Step example

ZQRN :PCUM,0::EL4:"10.1.2.11",28,L;
ZQRN :PCUM,0::EL4:"5000::1",64,L;

24 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the Gb interface

6 Create source based route(s) (QKM) using the following command.

ZQKM :<unit type>,<unit index>::"<Source IP

address>",:"<gateway IP address>":<route type>:;

Step example

ZQKM :PCUM,1::"10.8.149.252":"10.8.149.1":LOG:;

Step example

7 Check the IP configuration (QRI) (optional) using the following command.

ZQRI :<unit type>,<unit index>::<interface name>:<ip addr

family>:<display unit's attached interfaces>;

8 Create a packet service entity (PSE) (FXA) using the following command.

ZFXA :PSEI=<packet service entity identifier>, PCU=<packet

control unit>;

Step example

ZFXA :PSEI=0,PCU=0,:;

9 To implement this step, choose one of the following alternatives:

Sub-steps

a) Create the network service virtual link (NS-VL) using a dynamic IP configuration
(FXK).

Note that the network service entity identifier (NSEI) must be the same at both
ends of the Gb interface. Also, remote end parameters (NSEI and IP address) in
the AirScale BSC Gb interface configuration must match the corresponding local
parameters of the SGSN. In the dynamic configuration, the UDP port is
preconfigured in the SGSN BSS interface parameters. This parameter must also
match with the parameter in the AirScale BSC.
ZFXK :NSVLI=<network service virtual link
identifier>,NAME=<network service virtual link
name>,NSEI=<network service entity
identifier>,PSEI=<packet service entity
identifier>:LPNBR=<local UDP port
number>,PRE=Y:RIP=<remote IP address>,RPNBR=<remote UDP
port number>;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 25

Configuring the Gb interface Configuring IP interfaces

Create only one NS-VL per NSE in the AirScale BSC. The maximum number of
local endpoints is one per NSE and PCUM. The maximum number of remote
endpoints is 32 with single PCUM.
Note that the remote IP address (RIP) parameter determines the local IP
address type. The remote and local ends of the NS-VL must use the same
address type. Both address types can be simultaneously configured to the
PCUM.

g Note: The local UDP port number should be unique when the Multipoint Gb
feature is enabled while configuring multiple NSEs on a PCUM or a PSE.

b) Create the network service virtual link (NS-VL) using a static IP configuration
(FXK).

Note that the NSEI must be the same at both ends of the Gb interface. Also
remote end parameters (NSEI, IP address, and UDP port) in the AirScale BSC
Gb interface configuration must match the corresponding local parameters of the
SGSN.
ZFXK :NSVLI=<network service virtual link
identifier>,NAME=<network service virtual link
name>,NSEI=<network service entity
identifier>,PSEI=<packet service entity
identifier>:LPNBR=<local UDP port
number>,PRE=N:RIP=<remote IP address>,RPNBR=<remote UDP
port number>,RDW=<remote data weight>,RSW=<remote
signaling weight>;
To use load balancing between remote IP endpoints (NS-VLs), or to use different
IP endpoints for signaling and data traffic, create more remote IP endpoints (NS-
VLs) with the FXK command. The maximum number of local endpoints is one per
NSE and PCUM. The maximum number of remote endpoints is 32 with single
PCUM.

g Note: The local UDP port number should be unique when the Multipoint Gb
feature is enabled while configuring multiple NSEs on a PCUM or a PSE.

10 Check the creation and state of the NS-VL (FXI) using the following command.

ZFXI :NSVLI=<network service virtual link identifier>;

11 Enable GPRS in the segments for the PSE (EQV) using the following command.

The BSSGP layer is created for the Gb interface when GPRS is enabled in the
segments.
ZEQV :SEG=<SEG identification>:GENA=Y:PSEI=<packet service
entity identifier>;

Further information
Example:

26 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the Gb interface

Dynamic configuration (IPv4):

ZW7I :FEA:FEA=7,;
ZQRA :PCUM,1::EL4:;
ZQRN :PCUM,1::EL4:"10.8.149.252",24,L;
ZQKM :PCUM,1::"10.8.149.252":"10.8.149.1":LOG:;
ZQRI :PCUM,1:;
ZFXA ::PSEI=20,PCU=1,:;
ZFXK
:NSVLI=2,NAME=MAIN_CH_02,NSEI=1,PSEI=20:LPNBR=50000,PRE=Y:R
IP=”192.168.0.2”,RPNBR=50000;
ZFXI :NSVLI=2;
ZEQV :SEG=100:GENA=Y:PSEI=20;
Example:
Static configuration (IPv4):
ZW7I :FEA:FEA=7,;
ZQRA :PCUM,1::EL4:;
ZQRN :PCUM,1::EL4:"10.8.149.252",24,L;
ZQKM :PCUM,1::"10.8.149.252":"10.8.149.1":LOG:;
ZQRI :PCUM,1:;
ZFXA :PSEI=20,PCU=1,:;
ZFXK
:NSVLI=2,NAME=MAIN_CH_02,NSEI=1,PSEI=24:LPNBR=50000,PRE=N:R
IP=”192.168.0.2”,RPNBR=50000,RDW=1,RSW=1;
ZFXI :NSVLI=2;
ZEQV :SEG=102:GENA=Y:PSEI=24;

3.2 Testing the activation of Gb over IP

Testing the activation steps of Gb over IP.

Purpose
Monitor the Gb over IP performance with 98 Gb over IP Measurement.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 27

Configuring the Gb interface Configuring IP interfaces

Procedure

1 Create the measurement (TPM) using the following command.

If the measurement is not already defined, create definitions and schedules for it.
ZTPM:GPRS,GBIP:<measurement day>,<measurement
interval>,<output interval>;

2 Start the measurement (TPS) using the following command.

ZTPS:GPRS,GBIP;

3 Verify the success of the activation.

At the end of the measurement period, check the measurement data in NetAct or
using the MEFICO tool.

Step result

Counters 098000 NS_ALIVE MSG SENT BY PCUM and 098001 NS_ALIVE_ACK

MSGS FROM SGSN are updated.
Counter 098002 NS_ALIVE MSGS SENT BY PCUM RETRY is updated.

4 Stop the measurement (TPE) using the following command.

ZTPE:GPRS,GBIP;

3.3 Modifying the remote IP endpoint signaling and

data weight
Modification of remote IP endpoint signaling

Procedure

1 Modify the signaling and data weights of the remote IP endpoint (FXJ) using the
following command.

The operator can only modify the signaling and data weights of the static
configuration.
ZFXJ:NSVLI=<network service virtual link
identifier>::NEWRDW=<new remote data weight>,NEWRSW=<new
remote signaling weight>::;

28 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the Gb interface

2 Check the creation and state (FXI) using the following command.

ZFXI:NSVLI=<network service virtual link identifier>;

Step example

ZFXJ:NSVLI=2::NEWRDW=5,NEWRSW=2::;
ZFXI:NSVLI=2;

3.4 Modifying the NS-VL name

Step to modify the NS-VL name.

• Modify the NS-VL name (FXJ) using the following command.

ZFXJ:NSVLI=<network service virtual link

identifier>::NEWNAME=<new network service virtual
connection name>::;

Step example

ZFXJ:NSVLI=2::NEWNAME=LINK::;

3.5 Deactivating and testing Gb over IP

Deactivation steps of Gb over IP.

Before you start

Before deactivating Gb over IP, disable GPRS on cell level.

Procedure

1 Delete the network service virtual link (NS-VL) (FXH) using the following command.

Note that the operator cannot delete an NS-VL if it is the only one in a certain
network service entity (NSE) and the NS-VL has cells connected to it.
ZFXH:NSVLI=<network service virtual link identifier>;
In the static configuration, the operator must delete every NS-VL separately.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 29

Configuring the Gb interface Configuring IP interfaces

When the operator deletes the last NS-VL of the NSE, the NSE is deleted
automatically.

2 Check the deletion of NS-VLs (FXI) using the following command.

ZFXI:NSVLI=<network service virtual link identifier>;

3 Delete the Packet Service Entity (FXE) using the following command.

The deletion is not allowed if there is an NSE configured to the PSE.

ZFXE:PSEI=<packet service entity identifier>;
Note that the steps from step 4 onwards are only necessary if you want to disconnect
the PCUM.

4 Delete source based routes (QKP) using the following command.

ZQKP:<route number>:;

Step example

ZQKP:1:;

5 Remove the network interface (QRG) using the following command.

ZQRG:<unit type>,<unit index>::<interface name>:"<ip

address of network interface>":;

Step example

ZQRG:PCUM,0::EL4:"10.4.5.6":;

g Note: The above two steps (deleting source based routes and removing the
network interface) are done by CBAM.

6 Check the deactivation (QRI) using the following command.

ZQRI:<unit type>,<unit index>:<plug-in unit type>,<plug-in

unit index>:<interface name>:<display unit's attached
network interfaces>;

7 To disable the use of Gb over IP altogether, turn the feature state to OFF (W7M).

ZW7M:FEA=7:OFF;

30 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the Gb interface

Step example

ZFXH:NSVLI=3;
ZFXI:NSVLI=3;
ZFXE:PSEI=20;
ZQKP:1:;
ZQRG:PCUM,0::EL4:"10.4.5.6":;
ZQRI:PCUM,2:;

Step result

After the operator turns the feature state parameter to OFF, the Gb over IP related
parameters and commands are no longer visible in the MML command interface.
The operator can verify this by trying to use, for example, the FXL command.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 31

Configuring the NTP interface Configuring IP interfaces

4 Configuring the NTP interface

Steps to configure the NTP interface.

4.1 Overview
Overview of the Network Time Protocol.

Network Time Protocol (NTP) is a protocol to synchronize time between server and
clients. NTP can provide high precision time adjusting, and prevent time wrapping back.
The use of Network Time Protocol (NTP) is strongly recommended and in the simplest
form the NTP is configured by assigning the IP addresses of the external NTP servers to
the system. CBAM does NTP configuration in instantiation. User can modify
configuration with MMLs. For example, external server IPs. For redundancy, up to three
external NTP servers can be used by the system.

Figure 4 NTP server overview

NTP server

ASBSC

MCMU(SP) MCMU(WO)

Anyotherunit Anyotherunit PCUM PCUM

4.2 Configuring NTP

Steps to configure NTP.

Before you start

• NTP server is ready.
• All the IP addresses for NTP communication are configured.

g Note: NTP configuration is taken care by CBAM.

32 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the NTP interface

Procedure

1 Configure the NTP server by using the DCJ MML command:

ZDCJ:<hex_number> , <"IP-address" | "host name"> , [min

poll], [max poll];
<hex_number> can be one of the following:
1 ... PRIMARY NTP SERVER ADDRESS
2 ... SECONDARY NTP SERVER ADDRESS
3 ... TERTIARY NTP SERVER ADDRESS
L ... LOCAL NTP SERVER IP ADDRESS -- MCMU,0::EL0 // ntp net and mask
A ... LOCAL COMMUNICATION IP ADDRESS -- MCMU,0::EL4 // oam net(ext NTP)

g Note:
• If 'min poll' and 'max poll' are not given, default values are used in AirScale
BSC.
• The local NTP server address is the local NTP server address, which is used
by other units for synchronizing with MCMU. It is the EL0 address in MCMU.
The local communication IP address is the local address, which is used when
the MCMU is synchronizing with external NTP server. It is the EL4 address in
MCMU.
.

Step example

ZDCJ:1,"testntpserver1.testzone",32,128;
ZDCJ:2,"testntpserver2.testzone",32,128;
ZDCJ:3,"testntpserver3.testzone",32,128;

2 Configure local NTP server IP address by using the DCJ MML command:

ZDCJ:<hex_number> , <"IP-address" | "host name"> , [min

poll], [max poll];
ZDCJ:L,"10.20.98.1":24:;

3 Configure local communication IP address by using the DCJ MML command:

ZDCJ:A,"10.56.120.66":;

4 Set safety limit by using the DCK MML command:

ZDCK:2000:;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 33

Configuring the NTP interface Configuring IP interfaces

5 Check NTP configuration and status by using the DCH and DCI MML commands.

6 Activate the NTP feature by using the following MML command:

ZWOA:2,2308,A;

7 Configure IP routes towards NTP server from PCUM (QKC).

ZQKC:<unit type> , <unit index> ::"<NTP server IP-1>":"<

Gateway IP of EL1 interface>":PHY:;

g Note: Similarly, routes to be added to all NTP servers present from all PCUMs.

Step example

ZQKC:PCUM,0::"10.20.98.2":"10.2.180.3":PHY:;

34 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

5 Configuring the optional interfaces

Describes the configuration and testing of optional interfaces of AirScale BSC.

5.1 Configuring the BSC-BSC interface

Activating and deactivating of the BSC-BSC interface.

5.1.1 Activating the BSC-BSC interface

Activating the BSC-BSC interface.

Before you start

Before creating the virtual signaling channels, the IP configuration must be created.
Every BCXU configured for BSC-BSC interface must have two individual IP addresses:
one for the EL6 interface (Ethernet port) and another for the EL7 interface (Ethernet
port). These IP addresses should belong to different sub-networks. It is recommended
that IP addresses are created for at least two BCXUs in every AirScale BSC. Logical IP
addresses should be used to enable BCXU switchovers.

Figure 5 Protocol stack of the BSC-BSC interface

RANAPP+ RANAPP+
SCCP SCCP
M3UA M3UA
SCIP SCIP
IP IP
Ethernet Ethernet

AirScaleBSC BSC

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 35

Configuring the optional interfaces Configuring IP interfaces

5.1.1.1 Creating and activating the IP configuration

Creating and activating the IP configuration.

Procedure

1 Check whether IP addresses are configured (QRI).

ZQRI:<unit type>,<unit index>::<interface name>:<ip addr

family>:<display unit's attached interfaces>;

Step example

ZQRI:BCXU,0::EL6:ALL:NO:;

2 Create the IP configuration for the client and server side (QRN), if not configured.

ZQRN:<unit type>,<unit index>::<interface name>:"<IP

address>",<netmask lenght>,<L/P>::;

Step example

client EL6: 10.16.32.78

client EL7: 10.16.32.41
server EL6: 10.16.32.83
server EL7: 10.16.32.40
ZQRN:BCXU,0::EL6,:"10.16.32.83",26,L::;
ZQRN::BCXU,0::EL7,:"10.16.32.40",26,L::;

3 Configure IP routes (QKM).

ZQKM:<unit type>,<unit index>::"<source IP

address>":"<gateway IP address>":LOG;

Step example

ZQKM:BCXU,0::"10.103.142.17":"10.103.142.1":LOG;

5.1.1.2 Creating and activating M3UA configuration

M3UA creation and activation.

36 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Procedure

1 Create association sets for both AirScale BSCs (OYC).

Create association sets for both AirScale BSCs and define one association set to be
a server and the other to be a client.
An association set is an individual set for one BSC-BSC connection between two
BSCs. When several remote AirScale BSCs are connected to an AirScale BSC, the
operator has to create association sets for every BSC-BSC connection.
ZOYC:<association set name>:<role>:<sctp user|M3UA def>;

Step example

ZOYC:BSC1TOBSC2:S:M3UA;
ZOYC:BSC2TOBSC1:C:M3UA;

2 Modify the association set (OYM).

Set the identifier of the first data stream number to 1.

ZOYM:<association set name>:FIRST=<identifier of first data
stream number>:;

Step example

ZOYM:BSC1TOBSC2:FIRST=1:;

3 Add associations to the association set (OYA).

It is recommended that at least two associations are added for each BCXU in an
association set.
ZOYA:<association set name>:<unit type>,<unit
index>:<parameter set name>;

Step example

ZOYA:BSC1TOBSC2:BCXU,0:IETF:;

4 Configure the association IP addresses (OYP) using the following command.

ZOYP:<SCTP user>:<association set name>, <association

index>:"<source address 1>", ["<source address
2>"],[<source port>]:"<primary destination address>",
[<netmask/prefix>],["<secondary destination
address>"],[<netmask/prefix>],<destination port>;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 37

Configuring the optional interfaces Configuring IP interfaces

Step example

ZOYP:M3UA:BSC1TOBSC2,0:"10.16.32.83","10.16.32.40",:
"10.16.32.78",26,"10.16.32.41",26,:;

5 Activate the associations (OYS) using the following command.

ZOYS:<SCTP user>:<association set name>, <association

index>:ACT;

Step example

ZOYS:M3UA:BSC1TOBSC2,0:ACT;

6 Define own Signaling Point Code (SPC) using the following command.

ZNRP:<signaling network>,<signaling point code>,<signaling

point name>,<OWN signaling point handling>:<SS7
standard>:<number of SPC subfields>:<SPC subfield length>;

Step example

ZNRP:NA0,3B1,ASBSC,STAND=:::;

7 Create the IP signaling link set (NSP).

Use the Signaling Point Code of the remote AirScale BSC. Check the SPC of the
remote AirScale BSC with the ZNVI or ZNET command.
ZNSP:<signaling network>,<signaling link point
code>,<signaling link set name>:<signaling link
number>:<association set>;

Step example

ZNSP:NA1,122B,BBI02:9:BSC1TOBSC2;

8 Create the signaling route set (NRC) using the following command.

ZNRC:<signaling network>,<signaling link point

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

38 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Step example

ZNRC:NA1,122B,BBI02,6,,:,,,7;

9 Allow the activation of the signaling links (NLA) using the following command.

ZNLA:<signaling link numbers>;

Step example

ZNLA:9;

10 Activate the signaling links (NLC) using the following command.

ZNLC:<signaling link numbers>,ACT;

Step example

ZNLC:9,ACT;

11 Allow the activation of the signaling routes (NVA) using the following command.

ZNVA:<signaling network>,<signaling point code>:<signaling

transfer point network>,<signaling transfer point code>;

Step example

ZNVA:NA1,122B:;

12 Activate the signaling routes (NVC) using the following command.

ZNVC:<signaling network>,<signaling point code>:<signaling

transfer point network>,<signaling transfer point
code>:ACT;

Step example

ZNVC:NA1,122B::ACT;

5.1.1.3 Creating and activating the SCCP configuration

Steps to activate SCCP.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 39

Configuring the optional interfaces Configuring IP interfaces

Procedure

1 Define the SCCP for signaling point (NFD) and the RNSAP subsystem.

It is recommended to use signaling point parameter set number two.

ZNFD:<signaling network>,<signaling point code>,<signaling
point parameter set>:8F,RNSAP,<subsystem parameter set
number>,<subsystem status test>;

Step example

ZNFD:NA1,122B,2:8F,RNSAP,0,;

2 Check and modify the signaling parameter set used for SCCP (OCI, OCM).

Check the parameter values with the following command:

ZOCI:<signaling point parameter set>;
Example:
ZOCI:2;
Modify the parameter values with the following command:
ZOCM:<signaling point parameter set>:<parameter
number>,<parameter value>:;
Due to the size of the DFCA BSC-BSC messages the segmentation parameter
CO_SEGM_USED has to be set ON. After this, the AirScale BSC is able to split the
messages to several parts when needed.
ZOCM:<signaling point parameter set>:27,1;
Change the value of the timer SSP_FILTER_TIMER from 10 to 110 (11 seconds).
ZOCM:<signaling point parameter set>:25,110;
Change the value of the timer Q714_T_STAT_1ST from 600 to 50 (5 seconds).
ZOCM:<signaling point parameter set>:8,50;
Check also that value of the Q714_T_IAR parameter is more than two times the
value of Q714_T_IAS parameter in both local and remote AirScale BSCs.

3 Add remote SCCP subsystems to signaling points (NFB).

Before creating the signaling point or its subsystem, check the Signaling Point Code
(SPC) of the AirScale BSC's own signaling point with the NFI command.
ZNFB:[<signaling network>],<signaling point
codes>:<subsystem number>,<subsystem name>,<subsystem
parameter set number>,[<subsystem status test>];

Step example

ZNFB:NA1,132C:8F,RNSAP,0;

40 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

4 Change SCCP state for the remote SPC (NGC) using the following command.

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

Step example

ZNGC:NA1,122B:ACT;

5 Activate local and remote SCCP subsystems (NHC) using the following command.

ZNHC:<signaling network>,<signaling point

codes>:<subsystem>:ACT;

Step example

ZNHC:NA1,132C:8F:ACT;
ZNHC:NA1,122B:8F:ACT;

6 Interrogate broadcast status of SCCP signaling points (OBI).

Sub-steps

a) Execute the following command:

ZOBI:<broadcast group of affected subsystems for sp

broadcast>:<broadcast group of concerned signaling points
for sp broadcast>:<mode>;

Step example

ZOBI:::A;

b) Interrogate members of certain broadcast groups (OBH).

Use the I function mode to interrogate the members of the signaling points
broadcast groups.
The operator can limit the output by specifying the network, and in the case of
ALBG and ASBG groups by specifying the subsystem number.
ZOBH:I:ASBG,<broadcast group number>:<signaling
network>:<subsystem>;
ZOBH:I:CSBG,<broadcast group number>:<signaling network>;

g Note: ASBG and CSBG groups are used for signaling points broadcast. If the
subsystems in the ASBG group are changed, SCCP will broadcast it to remote
signaling points in the CSBG group.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 41

Configuring the optional interfaces Configuring IP interfaces

Step example

ZOBH:I:ASBG,:NA0:D'122:;
ZOBH:I:CSBG,:NA0:;

c) Interrogate local subsystem broadcast status (OBL).

ZOBL:<broadcast group of affected subsystems for local

broadcast>:<network of local subsystem>,<local subsystem
number>:<mode>;

Step example

ZOBL::NA0,:A;

d) Interrogate members of certain broadcast groups (OBH).

Use the I function mode to interrogate the members of the local broadcast
groups.
The operator can limit the output by specifying the network, and in the case of
ALBG and ASBG groups by specifying the subsystem number.
ZOBH:I:ALBG,<broadcast group number>:<signaling
network>:<subsystem>;

Step example

ZOBH:I:ALBG:NA0;

7 Set broadcast status if needed (OBC, OBM).

There are two different types of broadcasts the operator can set:
• local broadcast status (OBC command): used to inform the subsystems of the
own signaling point about changes in the subsystems of the remote signaling
points.
• broadcast status (OBM command): used to inform other signaling points about
changes in the subsystems of the own signaling point or the subsystems of the
signaling points connected to the own signaling point.
Before setting the broadcasts, the operator needs to assign subsystems or signaling
points to broadcast groups between which the broadcasts are defined. In SCCP
broadcast handling, three different types of broadcast groups are used (see Table 3:
Broadcast group types used in SCCP broadcast status handling). Within each
broadcast group type, a subsystem or signaling point belongs to only one group.
When a new subsystem or signaling point is created, it is assigned to group number
0 in each broadcast group type.

42 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Table 3 Broadcast group types used in SCCP broadcast status handling

Broadcast type Broadcast Broadcast group definition Group

group type number

Local broadcast ALBG Broadcast group of affected 1-49

status (OBC subsystems for local broadcast
command)

Broadcast status ASBG Broadcast group of affected 1-49

(OBM command) subsystems for SP broadcast

CSBG Broadcast group of concerned 1-49

signaling points for SP broadcast

Local broadcast status is defined between broadcast groups of affected subsystems

for local broadcast (ALBG) and individual local subsystems. Broadcast status is
defined between broadcast groups of affected subsystems for SP broadcast (ASBG)
and broadcast groups of concerned signaling points for SP broadcast (CSBG).When
the operator sets local broadcasts, the remote network elements have to be
configured in such a way that the network elements send the status data to the
network element of the operator.

g Note: When setting the broadcasts, consider what broadcasts are needed.
Incorrect or unnecessary broadcasts can cause problems and unnecessary
traffic in the signaling network. Note that the broadcasts that are set affect all the
subsystems or signaling points that are members of the broadcast groups given
in the command.

Modify the broadcast groups if needed. According to the broadcast type, assign the
affected subsystems to an ALBG or ASBG group. In remote broadcast, assign the
concerned signaling points to a CSBG group using the following commands.
ZOBH:M:ALBG,<broadcast group number>:<signaling
network>,<signaling point code>:<subsystem>;
ZOBC:<broadcast group of affected subsystems for local
broadcast>:<network of local subsystem>,<local subsystem
number>:<status>;
ZOBH:M:ASBG,<broadcast group type>:<signaling
network>,<signaling point code>:<subsystem>;
ZOBH:M:CSBG,<broadcast group type>:<signaling
network>,<signaling point code>:;
ZOBM:<broadcast group of affected subsystems for sp
broadcast>:<broadcast group of concerned signaling points
for sp broadcast>:<status>;
Example:
ZOBH:M:ALBG,1:NA1,122B:8F;
ZOBC:1:NA1,8F:Y:;
ZOBH:M:ASBG,1:NA0,1326:FE:;
ZOBH:M:CSBG,1:NA0,201:;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 43

Configuring the optional interfaces Configuring IP interfaces

ZOBM:10:20:Y;

5.1.2 Defining LAC-to-SPC mapping table

Step to create LAC-to-SPC mapping table.

• Create LAC to SPC mapping for all LACs that are under neighbor AirScale BSCs (EEC).

Give the SPC addresses of the neighbor AirScale BSCs, which have cells with this
particular LAC.
ZEEC :LAC=<location area code>:SPC=<signaling point code>;

Step example

ZEEC :LAC=20:SPC=122B;

5.1.3 Testing the BSC-BSC interface

Steps to test the BSC-BSC configuration steps.

• To test the BSC-BSC interface, check that the related counters are updated.

The activation of the BSC-BSC interface can be verified with the following counters
of the BSC-BSC measurement:
– 102000 BSC-BSC DELAY
– 102002 BSC-BSC PEAK DELAY
The DFCA activity on the BSC-BSC interface starts as soon as the DFCA algorithm
in the serving AirScale BSC detects inter-AirScale BSC neighbor cells that can
possibly interfere with the DFCA cells of the serving AirScale BSC. With the default
DFCA settings, this takes place 60 minutes after DFCA has been switched on in a
cell. This also requires that there are DFCA cells among the detected inter-AirScale
BSC neighbor cells. To have the activity on the BSC-BSC interface started sooner
than 60 minutes after the DFCA activation, modify the BIM (background interference
matrix) update parameter with the EEH command. The minimum value for the
parameter is 10 minutes.
Using the following command the BIM update period is modified to 10 minutes.
ZEEH :BUP=10;
With continuous traffic under the DFCA cells, the related measurement counters start
to be updated with one-minute intervals after the first background interference matrix
update.
To display the counters, use the service terminal extension BSC Measurement
Counters Displaying and Updating Program.

44 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

5.1.4 Solving BSC-BSC interface activation failures

Troubleshooting interface activation failures.

Procedure

1 Check for active alarms (AHO).

If the alarm 3260 UNKNOWN POTENTIALLY INTERFERING CELL FOR DFCA is

active, see the alarm instructions document.

2 Check that the LAC to SPC mapping table is filled correctly (EES).

All the LACs in the neighbor BSCs should be introduced with correct neighbor BSC
SPC.

5.1.5 Deactivating the BSC-BSC interface

BSC-BSC interface deactivation.

5.1.5.1 Deactivating the BSC-BSC interface

Steps to deactivate the BSC-BSC interface

Before you start

Before carrying out this procedure, the opeartor should know the signaling point code of
the local or remote signaling point and the name of the local or remote subsystem to be
removed.

Procedure

1 Delete the information in the LAC to SPC mapping table (EED) using the following
command.

ZEED:LAC=<location area code>;

2 Check that the related counters are not updated to test the deactivation.

During the DFCA activity, the DFCA algorithm updates the following counters in one-
minute intervals:
• 102000 BSC-BSC DELAY
• 102002 BSC-BSC PEAK DELAY

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 45

Configuring the optional interfaces Configuring IP interfaces

After deactivating the BSC-BSC interface, the related counters are not updated
anymore. The counter values that were reached by that time remain in the DFCA
algorithm for a short period of time after the deactivation, but, within 15 minutes the
counters are finally cleared. This takes place as the centralized part of the
performance monitoring and collects the counter values from the DFCA algorithm.

5.1.5.1.1 Deactivating and removing the SCCP configuration

SCCP deactivation steps.

Procedure

1 Remove the SCCP signaling point in both network elements.

Sub-steps

a) Check existing SCCP signaling points and subsystems (NFI, NFJ) using the
following commands.

To output the defined SCCP signaling point, use the following command:
ZNFI:;
To output the defined SCCP subsystems, use the following command:
ZNFJ:;

b) Deactivate the local and remote SCCP subsystems (NHC) using the following
command.

ZNHC:<signaling network>,<signaling point

codes>:<subsystem>: INA;

Step example

ZNHC:NA1,122B:8F:INA;
ZNHC:NA1,132C:8F:INA;

c) Remove local and remote subsystems from the signaling point (NFT) using the
following command.

ZNFT:<signaling network>,<signaling point

codes>:<subsystem number>;

Step example

ZNFT::NA1,122B:8F;

46 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

ZNFT:NA1,132C:8F;

d) Deactivate the remote SCCP signaling point (NGC) using the following
command.

Deactivate all subsystems before the operator can deactivate the SCCP
signaling point.
ZNGC:<signaling network>,<signaling point codes>: INA;

Step example

ZNGC:NA0,122B:INA:;
ZNGC:NA0,132C:INA:;

e) Remove the remote SCCP signaling point from the own signaling point (NFR)
using the following command.

ZNFR:<signaling network>,<signaling point codes>;

Step example

ZNFR:NA1,122B;

5.1.5.1.2 Deactivating and removing the M3UA configuration

M3UA deactivation steps.

Procedure

1 Deactivate the signaling route (NVC) using the following command.

ZNVC:<signaling network>,<signaling point code>:<signaling

transfer point network>,<signaling transfer point
code>:INA;

Step example

ZNVC:NA1,122B::INA;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 47

Configuring the optional interfaces Configuring IP interfaces

2 Deny the activation of the signaling route (NVD) using the following command.

ZNVD:<signaling network>,<signaling point code>;

Step example

ZNVD:NA1,122B;

3 Deactivate the signaling links (NLC) using the following command.

ZNLC:<signaling link numbers>,INA;

Step example

ZNLC:9,INA;

4 Deny the activation of signaling links (NLD) using the following command.

ZNLD:<signaling link number>;

Step example

ZNLD:9;

5 Delete signaling route set (NRD) using the following command.

ZNRD:<signaling network>,<signaling point code>,<signaling

point name>;

Step example

ZNRD:NA1,122B,BSC02;

6 Delete IP signaling links (NSD) using the following command.

ZNSD:<signaling network>,<signaling point code>,<signaling

link set name>;
ZNSD:NA0,D’8592,MSS:;

48 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

7 Remove the unused association set in both network elements (OYD) using the following
command.

ZOYD:<association set name>;

ZOYD:BSC02;

8 Delete the source IP addresses from the units (OYG) using the following command.

ZOYG:<unit type>,<unit index>,<displaying type>;

Step example

ZOYG:BCXU,0:IPV4:;
ZOYG:MCMU,0:IPV4:;

5.2 Configuring the BSC-CBC interface

Configuring the BSC-CBC interface.

5.2.1 Overview of BSC-CBC integration

Provides an overview of the BSC and CBC interface integration.

CBC integration represents a logical series of ordered tasks for connecting the cell
broadcast centre (CBC) to the base station controller (BSC).
The following determine the exact procedure for CBC integration:

• The network topology (direct or indirect).

• Service type: connectionless network service (CLNS), or connection-oriented
network service (CONS).
• The connection type: OSI over TCP/IP.

The OSI over TCP/IP needs an IP address for a connection to the endpoint. Therefore, a
network service access point (NSAP) type that includes an IP address and a port is
needed.

5.2.2 Preliminary tasks in CBC integration

Describes the initial steps to integrate the CBC integration.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 49

Configuring the optional interfaces Configuring IP interfaces

Procedure

1 Check that MBCCB channels are configured for relevant cells (EEI).

ZEEI;

Further information
The cell broadcast channel (CBCH) is included in the MBCCB.

2 Check that the parameter SMS CB used is set to ON (EQO).

ZEQO:BTS=<BTS:ID>:MIS;

3 Ensure that the data communication network (DCN) has been configured correctly and
that the protocols used between CBC and BSC are supported.

4 Check that the network supports CBC (WOI).

Note that CBC is an application software product.

ZWOI:10,44:;

5.2.3 Setting up the OSI subnetwork

Describes the steps to set up subnetwork.

5.2.3.1 Creating network services

Steps to create network services.

5.2.3.1.1 Enabling OSI over TCP/IP network service

Steps to enable OSI over TCP/IP network service.

Purpose
The TCP/IP interface has to be configured to the OMU.
The OSI over TCP/IP feature state needs to be in the ON state.

50 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Procedure

1 Check the OSI over TCP/IP feature state.

ZW7I:FEA:FEA=1242:;

2 Activate the licence (W7M).

ZW7M:FEA=1242:ON:;

5.2.3.1.2 Creating OSI over TCP/IP network service (CONS)

Steps to create OSI over TCP/IP network service.

Procedure

1 Activate the licence.

ZW7M:FEA=1242:ON:;

2 Configure the NSAP addresses.

3 Create OSI applications.

5.2.3.2 Creating NSAP addresses

Steps to create NSAP addresses.

5.2.3.2.1 Creating CONS NSAPs

Steps to create CONS NSAPs.

Procedure

1 Create a local NSAP for each service (QBN).

ZQBN:<NSAP number>:L:<NSAP type>:DTE=<DTE-

number>,SPI=<subsequent protocol identifier>;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 51

Configuring the optional interfaces Configuring IP interfaces

2 Create a remote NSAP for each service (QBN).

ZQBN:<NSAP number>:R:<NSAP type>:DTE=<DTE-

number>,SPI=<subsequent protocol identifier>,CHG=<X.25
channel group name>;

5.2.3.2.2 Creating CLNS NSAPs

Steps to create CLNS NSAPs.

Procedure

1 Create a local NSAP (QBN).

ZQBN:<NSAP number>:L:<NSAP type>:NSEL=<n-selector>;

Step example

ZQBN::L:4:NSEL=01,:

2 Create a remote NSAP (QBN).

ZQBN:<NSAP number>:R:<NSAP type>:NSEL=<n-selector>;

Step example

ZQBN::R:5:NSEL=01,END=123456789E1E,:

5.2.3.2.3 Creating OSI over TCP/IP NSAPs

Steps to create OSI over TCP/IP NSAPs.

Procedure

1 Create a local NSAP (QBN).

ZQBN:<NSAP number>:L:6:IPV4="<own_OMU_ip_address>";

52 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Step example

ZQBN::L:6:IP="10.45.67.8",;

2 Create a remote NSAP (QBN).

ZQBN:<NSAP
number>:R:6:IPV4=<remote_end_ip_address>,PORT=<port_number>
;

Step example

ZQBN::R:6:IP="10.35.67.9",PORT=102,:

5.2.3.3 Creating network addresses

The following steps apply to both CONS and CLNS.

Procedure

1 Create a local network address for each service (QBC).

ZQBC:LOCALCBC:L;

2 Create a remote network address for each service (QBC).

ZQBC:REMCBC:R;

5.2.3.4 Attaching NSAPs to network addresses

The following steps apply to both CONS and CLNS.

Procedure

1 Attach the local NSAP to a network address (QBT).

ZQBT:LOCALCBC:<NSAP>;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 53

Configuring the optional interfaces Configuring IP interfaces

2 Attach the remote NSAP to the remote network address (QBT).

ZQBT:REMCBC:<NSAP>,<priority>;

3 Unlock NSAP (QBG).

ZQBG:<NSAP number>,UNL;

4 Interrogate network address data (QBI).

ZQBI;
Make sure that the local network address is set to LOCALCBC and the remote
network address to REMCBC.

5.2.3.5 Creating OSI applications

The following steps apply to both CONS and CLNS.

Procedure

1 Create a local application in the BSC (QDL).

Note that the T-selector value must match at both ends. The family id must be 038C.
The application entity name (AE name) always begins with BSC and ends with CBC,
for example BSC098765CBC. The number in between is the BSC's number, which
varies. The P- and S-selectors written in the syntax of the QDL command are not
used.
ZQDL :<AE-name>:::UNL:<unit type>:<application
type>:<network address name>:<P-selector>:<S-selector>:<T-
selector>;

2 Interrogate the OSI application data (QDI).

ZQDI ::;
Ensure that all states are set to UNL-ENA.

3 Create a remote OSI application (QDR).

Note that the AE name CBCREMOTEAPPL must be exactly as given. The T-selector
value must match at both ends. The P- and S-selectors written in the syntax of the
QDR command are not used.
ZQDR :CBCREMOTEAPPL:::UNL;<application type>:<network
address name>:<P_sel>:<S_sel>: <T_selector>;

54 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

4 Interrogate the OSI application data (QDI).

ZQDI :APL=<appl location>:[<output format]>;

Ensure that all states are set to UNL-ENA

5.2.4 Activating and testing the CBC connection

Steps to activate and deactivate the CBC connection.

Purpose
After the connection has been created, switch the support for the CBC interface to ON
with the software-specific control parameter SMS_CBC_USD_IN_BSC.

Before you start

Check also that the CBCH channels are configured for the relevant cells and that the CB
Facility is set to ON in the BSC.

Procedure

1 Activate the CBC connection (WOC).

ZWOC :10,44,FF;

2 Wait for 5 minutes for the SMS_CBC_USD_IN_BSC parameter to become valid.

3 Check that the CB-related parameters have default values (WOI).

Other CB-related control parameters, SMSCB_INDEPEN_MULTIPAGE and

SMSCB_LAST_BLOCK_INFO (parameter class 002) and
CBC_INDIC_FILT_TIMER (parameter class 009) must have their default values
during the testing of the CBC interface. Check the default values from PRFILE and
FIFILE Parameter List.
ZWOI;

4 Test the CBC connection by checking the load of the cell from the CBC with the Status-
CBCH-Query procedure.

Expected outcome
The procedure is confirmed with status-CBC-query response/confirm.

Unexpected outcome

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 55

Configuring the optional interfaces Configuring IP interfaces

If the CBC integration fails, follow these individual steps to clear possible
communication problems between the BSC and CBC. The process does not
necessarily have to follow the given order.
• Monitor the data flow.
Use the OMU's O23MTSGX service terminal extension to monitor the data flow.
Z<char>AL:0,3,DTE,1where 3 is the PIU index.
If there is no data coming in, check the CBC settings (BSC address) from the
CBC.
• Check the NSAPs in the BSC (QBL, QBI).
If data is coming in but the CBC does not get a connection acknowledgement,
check the NSAPs in the BSC. Only one NSAP should point to the CBC.
ZQBL;
ZQBI;
• In the BTS, check that the appropriate channels are available and that CB is
supported (ERO, EQO).
ZERO :BTS=<BTS_number>;
ZEQO :BTS=<BTS_number>;
• Check that the messages information is ON in the MS.
ZECP :BTS=<BTS id>;

5 List the messages (ECP).

ZECP :BTS=<BTS id>;

5.2.5 Deactivating the CBC connection

Steps to deactivate the CBC connection.

Before you start

Switch OFF the support for the CBC interface using the software-specific control
parameter SMS_CBC_USD_IN_BSC.

Procedure

1 Deactivate the CBC connection (WOC).

ZWOC:10,44,0;

2 Wait for 5 minutes for the SMS_CBC_USD_IN_BSC parameter to become valid.

3 Test the deactivation by checking the load of the cell from the CBC with the Status-
CBCH-Query procedure.

56 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

5.3 Configuring the Lb interface

Lb interface configuration.

5.3.1 Activating and testing the Lb interface to AirScale BSC

Activating the Lb interface.

Purpose
The following are the instructions for the activation, testing, and deactivation of the Lb
interface to AirScale BSC, including instructions for implementing the standard Lb
interface with the Support for Uplink Time Difference of Arrival.

Before you start

The commercial location services over the Lb interface and commercial location requests
in the AirScale BSC-internal serving mobile location centre SMLC are licensed. Make
sure that you have the necessary licences installed. The licences are based on capacity;
that is, the number of LCS events in the Lb interface per minute and location requests in
an internal SMLC per second.
After the software update, the parameters are always in the OFF state. Remember to set
them to ON.
The SMLC object-related parameters can be modified after the activation. This is done
with the EXN command. The SMLC object includes SMLC response time and load rate
observation-related information. When modifying the load rate parameters, note that
PBS half rate limit (PHF) is the lowest limit, PBS stop limit (PSL) is the middle limit, and
LCS ignore limit (LIL) is the highest limit.
Before performing the following procedures, the IP configuration must be created to the
MCMU units, which control the link that is created.

5.3.1.1 Configuring the network before activating the Lb interface to

AirScale BSC

Steps to configure the network before activating the Lb interface.

Procedure

1 Create a logical IP address to the MCMU (QRN).

Assign an IP address to each available Ethernet interface. The operator can select
the configuration according to SMLC multi-homing capability.
ZQRA:MCMU,0::EL5::UP:
ZQRA:MCMU,1::EL5::UP:;
ZQRA:MCMU,0::EL6::UP:;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 57

Configuring the optional interfaces Configuring IP interfaces

ZQRA:MCMU,1::EL6::UP:;
Without using multi-homing:
ZQRN:MCMU,0::EL5,:"10.255.242.94",28,L;
ZQRN:MCMU,1::EL5,:"10.255.242.94",28,L;
Using multi-homing:
ZQRN:MCMU,0::EL5,:"10.255.242.94",28,L;
ZQRN:MCMU,0::EL6,:"10.255.243.110",28,L;

g Note: The multi-homing requires the allocation of IP addresses from separate

subnets in the MCMU.

2 Define a default route for the logical IP address (QKM).

Select the configuration according to SMLC multi-homing capability.

Without using multi-homing:
ZQKM:MCMU,0::"10.255.242.94":"10.255.242.81":LOG:;
Using multi-homing:
ZQKM:MCMU,0::"10.255.242.94":"10.255.242.81":LOG:;
ZQKM:MCMU,0::"10.255.243.110":"10.255.243.97":LOG:;

3 Create the M3UA association set (OYC) using the following command.

The name of the association set is SMLC. The role of the AirScale BSC is CLIENT
and the role of the stand-alone SMLC is SERVER.
ZOYC:SMLC:C:M3UA:;

4 Add an association to the association set (OYA).

Create associations for the SMLC association set. The controlling unit of the
association is the WO-EX MCMU. The name of the parameter set is SS7.
The operator can check the parameter sets using the following MML command:
ZOYO:;
Add the association with the following MML command:
ZOYA:SMLC:MCMU,0:SS7:;

5 Configure the association IP address (OYP).

Create associations for the SMLC association set.

Without using multi-homing:
ZOYP:M3UA:SMLC,0:"10.255.242.94":"10.8.154.88",28:;
Using multi-homing:

58 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

ZOYP
:M3UA:SMLC,0:"10.255.242.94","10.255.243.110",:"10.8.154.88
",28,"10.8.155.94",28,:

6 Create the IP signaling link set (NSP).

The IP signaling link set is created to the NA0 network. The destination (stand-alone
SMLC) signaling point code is 7. The name of the signaling link set and the
association set is SMLC, and the link number is 10.
ZNSP:NA0,7,SMLC:10:SMLC:;

7 Create the signaling route set (NRC).

The route set is created in the same network and using the same signaling point
code as in the IP signaling link set creation. The route set parameter number is 6
(IETF M3UA).
ZNRC:NA0,7,SMLC,6,,:,,,0:;

8 Set on the application server process (ASP) messages (OYM) using the following
command.

ZOYM:SMLC:ASP=Y;

9 Set off the dynamic routing key registration (OYM) using the following command.

ZOYM:SMLC:REG=N;

10 Set the ASP_MESSAGES_IN_IPSP parameter on (OYM).

ZOYM:SMLC:IPSP=Y;

11 Check the network appearance.

The network appearance must be the same in both the AirScale BSC and the SMLC.
Check the network appearance from the SMLC and copy it to the AirScale BSC
ZOYM:SMLC:NETWORK=1:; or vice versa.

12 Create the signaling point parameter set (OCC) using the following command.

ZOCC:3,EXMPL:;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 59

Configuring the optional interfaces Configuring IP interfaces

13 Create the signaling connection control part (SCCP) subsystem parameter set (OCA)
using the following command.

ZOCA:2,PAKKE:;

14 Modify the association state (OYS) using the following command.

ZOYS:M3UA:SMLC,0:ACT;

15 Allow the activation of the signaling link 10 (NLA) using the following command.

ZNLA:10:;

16 Activate the signaling link 10 (NLC) using the following command.

ZNLC:10,ACT:;

17 Allow the activation of the signaling route (NVA) using the following command.

ZNVA:NA0,7;

18 Activate the signaling route (NVC) using the following command.

ZNVC:NA0,7:,:ACT;

19 Add the BSS LE AirScale BSC subsystem (FA) to the own signaling point (NFB) using
the following command.

ZNFB:NA0,3B1:FA,SMLE,2,;
The operator can check the subsystem states using the following MML command:
ZNHI:NA0;

20 Add the BSS LE SMLC subsystem (FC) to the stand-alone SMLC signaling point (NFD)
using the following command.

ZNFD:NA0,7,3:FC,BSSLE,2,:;
The operator can interrogate the subsystem state using the following MML
command:
ZNHI:NA0,7:; where the signaling network is NA0 and the signaling point is 7.
,

60 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

21 Enable the local broadcast status of SCCP subsystem BSS LE SMLC (FC) using the
following commands.

ZOBH:M:ALBG,1:NA0,7:FC;
ZOBC:1:NA0,FA:Y;
ZOBH:M:ALBG,2:NA0,7:1;
ZOBC:2::Y;

22 Activate the SCCP (NGC) using the following command.

ZNGC:NA0,7:ACT;

23 Modify the signaling point parameter set (OCM).

Sub-steps

a) Set the SCCP to use X-UDT using the following command.

ZOCM:3:14,1;

b) Set the SCCP to use WHITE_BOOK_MGMT using the following command.

ZOCM:3:12,1:;
Use the following command to interrogate the signaling point parameter set:
ZOCI;

24 Set the SCCP subsystem to use IMMEDIATE_STATE_INFO using the following

command.

ZOCN:2:14,1;
Use the following command to interrogate the SCCP subsystem parameter set.
ZOCJ;

5.3.1.2 Activating the standard Lb interface

To activate the standard Lb interface.

Procedure

1 Activate the LB_USAGE parameter (WOA) using the following command.

ZWOA:2,749,A;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 61

Configuring the optional interfaces Configuring IP interfaces

2 Activate the subsystems (NHC) using the following command.

ZNHC:NA0,3B1:FA:ACT;
ZNHC:NA0,7:FC:ACT;

5.3.1.3 Activating the standard Lb interface and Support for Uplink Time
Difference of Arrival

Support for Uplink time difference of arrival.

Procedure

1 Activate the LB_USAGE parameter (WOA) using the following command.

ZWOA:2,749,A;

2 Activate the subsystems (NHC) using the following commands.

ZNHC:NA0,3B1:FA:ACT;
ZNHC:NA0,7:FC:ACT;

3 Activate the UTDOA_SUPPORT parameter (WOA) using the following command.

ZWOA:2,905,A;

4 Activate the UTDOA_COMMERCIAL parameterr to use the Commercial U-TDOA method

(WOA) using the following command.

ZWOA:2,1006,A;

5.3.2 Activating and configuring geo-redundant SMLC over

multi-homed Lb interface
Activating geo-redundant SMLC over multi-homed Lb interface.

62 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Procedure

1 Activate feature BSS21498: Geo-Redundant SMLC over Multi-Homed Lb-Interface

(W7M) using the following command.

ZW7M:FEA=1472:ON;

2 Create a new SCTP association set (OYC) using the following command.

ZOYC:PCAP:C:;

3 Set the value of the traffic mode to override (OYM) using the following command.

ZOYM:PCAP:TRAFFIC=1:;

4 Add an SCTP association, which points to the primary S/A SMLC to the SCTP
association set (OYA) using the following command.

ZOYA:PCAP:MCMU,0:SS7:HIGH;

5 Add an SCTP association, which points to the secondary S/A SMLC, to the SCTP
association set (OYA) using the following commands.

ZOYA:PCAP:MCMU,0:SS7:NORMAL;

6 Set the value of the first datastream number as '1' (OYM) using the following command.

ZOYM:PCAP:FIRST=1:;

7 Set the value of the routing context as '1' (OYM) using the following command.

ZOYM:PCAP:ROUTING=1:;

8 Configure IP addresses for the SCTP association set, which points to the primary S/A
SMLC (OYP) using the following command.

ZOYP
:M3UA:PCAP,0:"10.10.1.2","10.10.2.2",49152:"10.10.3.2",24,"
10.10.4.2",24,;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 63

Configuring the optional interfaces Configuring IP interfaces

9 Configure IP addresses for the SCTP association set, which points to the secondary S/A
SMLC (OYP) using the following command.

ZOYP
:M3UA:PCAP,1:"10.10.1.2","10.10.2.2",49153:"10.10.5.2",24,"
10.10.6.2",24,;

10 Activate the SCTP association, which points to the primary S/A SMLC (OYS) using the
following command.

ZOYS:M3UA:PCAP,0:ACT;

11 Activate the SCTP association, which points to the secondary S/A SMLC (OYS) using
the following command.

ZOYS:M3UA:PCAP,1:ACT;

12 Create the IP signaling link set (NSP) using the following command.

ZNSP:NA0,222,PCAP:20:PCAP:;

13 Create the signaling route set (NRC) using the following command.

ZNRC:NA0,PCAP,PCAP,6,,:,,,0:;

14 Set the value of the network appearance as '1' (OYM) using the following command.

ZOYM:PCAP:NETWORK=1:;

15 Create a new SCCP signaling point parameter set (OCC) using the following command.

ZOCC:3,PCAP;

16 Modify the signaling point parameter set (OCM).

Sub-steps

a) Set the SCCP to use X-UDT using the following command.

ZOCM:3:14,1;

b) Set the SCCP to use WHITE_BOOK_MGMT using the following command.

ZOCM:3:12,1:;

64 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

c) Set the connection-oriented segmentation using the following command.

ZOCM:3:27,1:;
The operator can interrogate the signaling point parameter set with the following
MML command:
ZOCI;

17 Create a new SCCP subsystem parameter set (OCA) using the following command.

ZOCA:2,PCAP;

18 Enable immediate sending of subsystem state information (OCN) using the following
command.

ZOCN:2:14,1;

19 Allow the activation of the signaling link (NLA) using the following command.

ZNLA:20:;

20 Activate the signaling link (NLC) using the following command.

ZNLC:20,ACT:;

21 Allow the activation of the signaling route (NVA) using the following command.

ZNVA:NA0,222;

22 Activate the signaling route (NVC) using the following command.

ZNVC:NA0,222::ACT;

23 Add a new subsystem to BSC's own signaling point (NFB) using the following command.

ZNFB:NA0,111:F9,PCAP,2,;

24 Add a new subsystem to S/A SMLC's signaling point (NFD) using the following
command.

ZNFD:NA0,222,3:F9,PCAP,2,;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 65

Configuring the optional interfaces Configuring IP interfaces

25 Allow broadcasting of subsystem states to the local subsystem (OBC) using the following
commands.

ZOBH:M:ALBG,3:NA0,222:F9;
ZOBC:3:NA0,F9:Y;

26 Activate SCCP (NGC) using the following commands.

ZNGC:NA0,111:ACT;
ZNGC:NA0,222:ACT;

27 Activate the LB_USAGE parameter (WOA) using the following command.

ZWOA:2,749,A;
If the UTDOA method is in use, activate UTDOA_SUPPORT and
UTDOA_COMMERCIAL.
ZWOA:2,905,A;
ZWOA:2,1006,A;

28 Activate the subsystems (NHC) using the following command.

ZNHC:NA0,111:F9:ACT;
ZNHC:NA0,222:F9:ACT;

5.3.3 Testing Lb interface to AirScale BSC

Steps to test the Lb interface.

Before you start

Make sure that the following network elements and mobile stations are available:

• One MSS
• One HLR
• One AirScale BSC with a stand-alone SMLC
• One MS
• One GMLC or iGMLC, if needed.

To test the location services, activate the Lb interface.

In addition to the AirScale BSC, all other network elements must be configured to
support the location services.

66 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Procedure

1 Make sure that the Position Based Services measurement is in UNLOCKED and
ENABLED state (TPI).

ZTPI :MEASUR,PBS:;

Step example

Set the measurement time period.

ZTPM :MEASUR,PBS:FRI,8-30-9-30,15;
Set the measurement activation time.
ZTPS :MEASUR,PBS:2003-10-17,2003-10-17:;

2 Generate an emergency call.

An emergency call triggers a network-initiated location request in the MSC.

3 Check the measurement data.

At the end of the measurement period, check the measurement data in NetAct or
using the MEFICO tool. Check that there is data and that it is correct.

5.3.4 Deactivating and testing the Lb interface to BSC

Testing the Lb interface.

Procedure

1 Stop the Position Based Services measurement, if started (TPE) using the following
command.

ZTPE:MEASUR,PBS;
Do not stop the measurement if the operator wants to keep it active for the internal
SMLC.

2 Deactivate the UTDOA_COMMERCIAL parameter if it has been activated (WOA) using

the following command.

ZWOA:2,1006,D;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 67

Configuring the optional interfaces Configuring IP interfaces

3 Deactivate the UTDOA_SUPPORT parameter if it has been activated (WOA) using the
following command.

ZWOA:2,905,D;

4 Deactivate the LB_USAGE parameter (WOA) using the following command.

ZWOA:2,749,D;

5 Make sure that the parameters have been deactivated (WOS) using the following
command.

ZWOS:2;

6 Change the states of the subsystems to inactive (NHC) using the following commands.

ZNHC:NA0,7:FC:INA:;
ZNHC:NA0,3B1:FA:INA;

7 Change the state of the SCCP to inactive (NGC) using the following command.

ZNGC:NA0,7:INA:;

8 Remove the SCCP from the signaling point (NFR) using the following command.

ZNFR:NA0,7:;

9 Change the state of the signaling route to inactive (NVC) using the following command.

ZNVC:NA0,7:,:INA;

10 Deny the activation of the signaling route (NVD) using the following command.

ZNVD:NA0,7:;

11 Change the state of the signaling link to inactive (NLC) using the following command.

ZNLC:10,INA;

12 Deny the activation of the signaling link (NLD) using the following command.

ZNLD:10:;

68 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

13 Delete the signaling route set (NRD) using the following command.

ZNRD:NA0,7,SMLC:;

14 Delete the signaling link set (NSD) using the following command.

ZNSD:NA0,7,SMLC:;

15 Remove the subsystems from the local signaling point (NFT) using the following
command.

ZNFT:NA0,3B1:FA:;

16 Delete the association from the association set (OYR) using the following command.

ZOYR:SMLC:0:;

17 Delete the association set (OYD) using the following command.

ZOYD:SMLC:;

18 Delete the signaling point and the SCCP signaling parameter sets (OCD, OCK) using the
following commands.

ZOCD:3,EXMPL:;
ZOCK:2,PAKKE:;

19 Change the feature state to OFF (W7M) using the following commands.

The MML command for commercial location requests in open Lb interface:

ZW7M:FEA=16:OFF;
The MML command for commercial MS-based positioning requests in open Lb
interface:
ZW7M:FEA=19:OFF;
The MML command for commercial U-TDOA requests in open Lb interface:
ZW7M:FEA=20:OFF;

5.4 Configuring the VNP interface

Steps to configure the VNP interface.

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 69

Configuring the optional interfaces Configuring IP interfaces

5.4.1 Activating SIGTRAN for the AirScale BSC-VNP interface

Real-time Road Traffic Information is activated in the AirScale BSC. First, activate
SIGTRAN for the interface between the AirScale BSC and the Vendor Network Probe
server (VNP), and then set the feature state on.

Purpose
Real-time Road Traffic Information is licence key controlled.
Figure 6 Protocol stack in the VNP interface

The SIGTRAN interface is activated in the AirScale BSC and the VNP.
The SIGTRAN IP transport complies with the following standards:

• IETF RFC 2719: Framework Architecture for Signaling Transport

• IETF RFC 2960: Stream Control Transmission Protocol
• IETF RFC 4666: Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User
Adaptation Layer (M3UA)

Figure 7: Signaling point and IP addressing for a sample configuration network illustrates
the signaling point and IP addressing details for a sample configuration with symmetric
network layout. SIGTRAN multi homing is configured to AirScale BSC and VNP servers.
The AirScale BSC application level uses the replication parameter to determine the
primary and secondary VNP:

Figure 7 Signaling point and IP addressing for a sample configuration network

10.16.161.242/28

70 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Before you start

Make sure that the following procedures have been completed before activating
SIGTRAN for the AirScale BSC-VNP interfaces:

1. The VNP hardware is correctly installed and the interfaces have been created.
2. The interfaces have been created.

Procedure

1 Create a logical IP address to the MCMU (QRA, QRN).

Assign an IP address to each available Ethernet interface (EL5 and EL6).

Multi-homing requires the allocation of IP addresses from separate subnets in the
MCMU.
Cases where MCMU includes two physical LAN connections:
ZQRA:MCMU,0::EL5::UP:;
ZQRA:MCMU,0::EL6::UP:;
ZQRA:MCMU,1::EL5::UP:;
ZQRA:MCMU,1::EL6::UP:;

2 Define a default route for the logical IP address (QKM) using the following commands.

The logical routes are updated to both MCMU units even though the command
requires selecting a unit.
ZQKM:MCMU,0::”10.16.153.94”:”10.16.153.81”:LOG:;
ZQKM:MCMU,0::”10.16.153.110”:”10.16.153.97”:LOG:;

3 Create the M3UA association set (OYC) using the following commands.

Create an association set for the VNP interface connection to the primary VNP and
secondary VNP servers. AirScale BSC is the client (C) and hence it starts
negotiating for the association sets (VNP1 and VNP2) while the VNP servers wait for
the negotiation request.
ZOYC:VNP1:C::;
ZOYC:VNP2:C::;

4 Add an association to the association set (OYA) using the following commands.

Create associations to the VNP1 and VNP2 association set. The controlling unit of
the associations (MCMU) is in the WO-EX state. The name of the parameter set is
SS7.
ZOYA:VNP1:MCMU,0:SS7:;
ZOYA:VNP2:MCMU,0:SS7:;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 71

Configuring the optional interfaces Configuring IP interfaces

5 Configure the association IP address (OYP) using the following commands.

Add the IP addresses of the sources and destinations to the primary and secondary
IP paths.
ZOYP:M3UA:VNP1,0:"10.16.153.94","10.16.153.110",:
"10.16.161.226",28,"10.16.161.242",28,:;
ZOYP:M3UA:VNP2,0:"10.16.153.94","10.16.153.110",:
"10.16.161.227",28,"10.16.161.243",28,:;

6 Create the IP signaling link set (NSP) using the following commands.

The IP signaling link sets are created to the NA0 network. The destination (VNPs)
signaling point codes are 501 and 502. The name of the signaling link set and the
association set is VNP1 and VNP2, and the link numbers are 81 and 82.
ZNSP:NA0,501,VNP1:81:VNP1:;
ZNSP:NA0,502,VNP1:82:VNP2:;

7 Create the signaling route set (NRC) using the following commands.

The route set is created in the same network and using the same signaling point
code as in the IP signaling link set creation. The route set parameter number is 6
(IETF M3UA).
ZNRC:NA0,501,VNP1,6,,:,,,0:;
ZNRC:NA0,502,VNP2,6,,:,,,0:;

8 Set off the dynamic routing key registration (OYM) using the following commands.

ZOYM:VNP1:REG=N;
ZOYM:VNP2:REG=N;

9 Set the ASP_MESSAGES_IN_IPSP parameter on (OYM) using the following

commands.

ZOYM:VNP1:IPSP=Y;
ZOYM:VNP2:IPSP=Y;

10 Check the network appearance (OYM).

The network appearance must be the same in both the AirScale BSC and the VNPs.
ZOYM:VNP1:NETWORK=1:;
ZOYM:VNP2:NETWORK=1:;

72 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

11 Create the signaling point parameter set (OCC) using the following command.

ZOCC:5,VNP:;

12 Modify the association state (OYS) using the following commands.

ZOYS:M3UA:VNP1,0:ACT;
ZOYS:M3UA:VNP2,0:ACT;

13 Allow the activation of the signaling links 81 and 82 (NLA) using the following
commands.

ZNLA:81:;
ZNLA:82:;

14 Activate the signaling links 81 and 82 (NLC) using the following commands.

ZNLC:81,ACT:;
ZNLC:82,ACT:;

15 Allow the activation of the signaling route (NVA) using the following commands.

ZNVA:NA0,501;
ZNVA:NA0,502;

16 Activate the signaling route (NVC) using the following commands.

ZNVC:NA0,501:,:ACT;
ZNVC:NA0,502:,:ACT;

17 Add the BSSTS subsystem (10) to the own signaling point and activate it (NFB, NHC)
using the following commands.

ZNFB:NA0,1221:10,BSSTS,0,;
ZNHC:NA0,1221:10:ACT;
The operator can check the subsystem states with the following MML command:
ZNHI:NA0;

18 Add the BSSTS subsystem (10) to the VNP signaling points (NFD) using the following
commands.

ZNFD:NA0,501,5:10,BSSTS,0,Y:;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 73

Configuring the optional interfaces Configuring IP interfaces

ZNFD:NA0,502,5:10,BSSTS,0,Y:;

19 Add the primary VNP signaling point for BSSTS (NFD) using the following commands.

Allow the replication for VNP signaling points and set signaling point 501 to dominant
role (DR).
ZNFC:NA0,501:10,NA0,502,DR;
ZNHD:NA0,501:10:OFA;

20 Enable the local broadcast status of the SCCP subsystem BSS TS (10) (OBC).

ZOBH:M:ALBG,1:NA0,501:10;
ZOBC:1:NA0,10:Y;

21 Enable the local broadcast status of SCCP subsystem to inform if A interface goes down
(OBC) using the following commands.

ZOBH:M:ALBG,1:NA0,203:FE;
ZOBC:1:NA0,10:Y;

g Note: Do not activate this step if the Multipoint A-interface feature is in use. The
AirScale BSC-VNP reset calls procedure does not work correctly if the Multipoint
A-interface feature is in use.

22 Activate the SCCP (NGC) using the following commands.

ZNGC:NA0,501:ACT;
ZNGC:NA0,502:ACT;

23 Activate the primary and the secondary VNP subsystems (NHC) using the following
commands.

ZNHC:NA0,501:10:ACT;
ZNHC:NA0,502:10:ACT;

24 Change the value of the SCCP signaling point parameter (OCM).

Set the value of the ADD_DPC_IF_RI_SSN parameter to 1 (YES) to insert

destination point code addition to destination address.
ZOCM:5:19:1;
Set the value of the WHITE_BOOK_MGMT parameter to 1 (YES) to use white book
management procedures.
ZOCM:5:12,1:;

74 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Set the SCCP to use XUDT.

ZOCM:5:14,1;
The operator can interrogate the signaling point parameter set using the following
MML command:
ZOCI;

25 Change the value of the SCCP fault tolerant timer (OCM) using the following commands.

Set the value of the SSP_FILTER_TIMER parameter to 15 seconds (150

deciseconds) and the value of the Q714_T_STAT_1ST parameter to 5 seconds (50
deciseconds) taking into account that the filter transport break lasts at most 10
seconds. The formula for masking the breaks is the following:
transport break + Q714_T_STAT_1ST < SSP_FILTER_TIMER.
ZOCM:5:25,150;
ZOCM:5:8:50;

26 Make sure that Common ID is supported in the MSC.

The Common ID message must be activated in MSC so that IMSI is available in all
cases.
Use the following command in the MSC:
ZEDT:VER=<current BSSAP version>:F,54,1;
The operator can check the BSSAP version with the ZEDO:; command.
If the Common ID support is not activated, an UTPFIL parameter change is needed
to allow AirScale BSC to initiate additional identity request procedure.

g Note: The Common ID (IMSI identifier) is always the preferred solution and
UTPFIL (IMEI or IMEISV identifier) patching is needed only if Common ID is not
available in MSC.

For example, the value of the id_req_allowed parameter is patched to UTPFIL

with process id 9B9, parameter id 3 and parameter value 0x1 using the MML
command:
ZDFS:MCMU,0:5AC006A,0,,W:;
DO YOU WANT THESE SUBSTITUTIONS TO BE UPDATED ON DISK ?
( Y = YES, N = NO ): Y
DO YOU WANT THESE SUBSTITUTIONS TO BE DISTRIBUTED ?
( Y = YES, N = NO ): Y
MCMU-0 FILE N:O 05AC006B RECORD N:O 00000000 DISPLACEMENT
00000000
0000-09B9 0000-3 0000-1 0000-0000
DO YOU WANT THIS SUBSTITUTION TO BE MADE ?
( Y = YES, N = NO ): Y
RECORD/STRING SUBSTITUTED

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 75

Configuring the optional interfaces Configuring IP interfaces

DISTRIBUTION IS STARTING
DISTRIBUTION DONE
DISK HAS BEEN UPDATED
END_OF_FILE
COMMAND EXECUTED

27 Check the Real-time Road Traffic Information feature state (W7I) using the following
command.

ZW7I:FEA:FEA=1376,;

28 Turn the Real-time Road Traffic Information feature state to ON if needed (W7M).

ZW7M:FEA=1376:ON;

5.4.2 Testing SIGTRAN for the AirScale BSC-VNP interface

Steps to test the configuration state in the VNP interface.

Purpose
This procedure describes how to test the configuration state in the VNP interface.

Procedure

1 Check the status of the SCTP layer (OYI) using the following command.

ZOYI::A;

Table 4 SCTP layer status

Association Explanation Further information

state

DOWN-BY- The initial state of an The operator can

USER association after it has been deactivate this state
created with the OYA after the last system
command. restart with the OYS
command.

76 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

Table 4 SCTP layer status (Cont.)

Association Explanation Further information

state

SCTP-DOWN • State after system restart: -

the MTP management has
not activated the M3UA
link that corresponds to the
association and the M3UA
link could be in the UA-AD
state (activation denied).
• The association has not
been activated with the
OYS command.
• At the server side, the
SCTP-DOWN state can
also mean that there is a
problem in the IP
connection, so the SCTP
association cannot be
activated. Check the IP
connection with the QRX
ping command.

UP- The negotiation of the SCTP Check the IP

PROCEEDING association is ongoing. There connection with the
might be some problems with QRX ping command.
the IP connection, so the
SCTP association cannot be
activated.

ASP-DOWN The association is up at the -

SCTP level but down at the
M3UA level. That is, an ASP
management message
exchange is ongoing. ASPUP
(at the server) or ASPUP ACK
(at the client) has not been
received yet. The M3UA link is
not active.

ASP- If the association is inactivated -

INACTIVE- by the operator (OYS MML), or
USR association state is changed
by message interface.

ASP- If the association is inactivated

INACTIVE- by the system.
SYS

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 77

Configuring the optional interfaces Configuring IP interfaces

Table 4 SCTP layer status (Cont.)

Association Explanation Further information

state

ASP-ACTIVE The association is up at both -

the SCTP and the M3UA level.
The M3UA link is active.

2 Check the status of the M3UA layer (NLI) using the following command.

ZNLI;
The signaling link should be in the AV-EX state.

3 Check the status of the signaling route (NVI) using the following command.

ZNVI:NA0;
The signaling route should be in the AV-EX state.

4 Check the status of the SCCP layer (NFI) using the following command.

ZNFI:NA0:A;
The AirScale BSC and the VNP SPs should be in the AV-EX state and replication
configured for VNP signaling points.

5.4.3 Deactivating SIGTRAN in the AirScale BSC-VNP interface

Steps to deactivate the AirScale BSC-VNP interface.

Purpose
Describes how Real-time Road Traffic Information is deactivated in the AirScale BSC.

Procedure

1 Turn the Real-time Road Traffic Information feature state OFF (W7M) using the following
command.

ZW7M:FEA=1376:OFF;

78 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03

Configuring IP interfaces Configuring the optional interfaces

2 Deactivate the VNP subsystems (NHC) using the following commands.

ZNHC:NA0,501:10:INA:;
ZNHC:NA0,502:10:INA:;

3 Deactivate the AirScale BSC subsystems (NHC) using the following command.

ZNHC:NA0,1221:10:INA:;

4 Deactivate the signaling points (NGC) using the following commands.

ZNGC:NA0,501:INA;
ZNGC:NA0,502:INA;

5 Delete the SCCP and subsystems (NFR, NFT) using the following command.

ZNFR:NA0,501;
ZNFR:NA0,502;
ZNFT:NA0,1221:10;

6 Deactivate the signaling route (NVC) using the following commands.

ZNVC:NA0,501::INA;
ZNVC:NA0,502::INA;

7 Deny the activation of the signaling route set (NVD) using the following commands.

ZNVD:NA0,501;
ZNVD:NA0,502;

8 Deactivate the signaling link (NLC) using the following commands.

ZNLC:81,INA;
ZNLC:82,INA;

9 Deny the activation of the signaling link (NLD) using the following commands.

ZNLD:81;
ZNLD:82;

DN194299879 Issue: 03 © 2019 Nokia. Nokia confidential. 79

Configuring the optional interfaces Configuring IP interfaces

10 Delete the signaling route set (NRD) using the following commands.

ZNRD:NA0,501,VNP1;
ZNRD:NA0,502,VNP2;

11 Delete the IP signaling link set (NSD) using the following commands.

ZNSD:NA0,501,VNP1;
ZNSD:NA0,502,VNP2;

12 Delete the association set (OYD) using the following commands.

ZOYD:VNP1;
ZOYD:VNP2;

80 © 2019 Nokia. Nokia confidential. DN194299879 Issue: 03