04_02_cn31534en30gla0_flexins3.0 Mme Integration.pdf

Uploaded by: David Fernandez
0
0

April 2020
PDF

Download

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA

Overview

Download & View 04_02_cn31534en30gla0_flexins3.0 Mme Integration.pdf as PDF for free.

More details

Words: 21,792
Pages: 91

Preview
Full text

Flexi Network Server, Rel. 3.0, Operating Documentation, v. 4

Integrating Flexi NS - MME DN70669711 Issue 7-1

Nokia Soutions and Networks 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 Siemens Networks for any additional information.

Integrating Flexi NS - MME

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

The same text in German:

f

Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.

2

Id:0900d80580a499f1 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Table of Contents This document has 91 pages. Changes in Flexi NS - MME Integration. . . . . . . . . . . . . . . . . . . . . . . . . . 7 1

Integrating Flexi NS - MME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 2.1 2.2 2.2.1 2.2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.10.1 2.10.2 2.11 2.11.1 2.11.2 2.12 2.13 2.13.1 2.13.2 2.14 2.14.1 2.14.2 2.14.3 2.14.4 2.14.5 2.15 2.16 2.17 2.18

Configuring interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flexi NS - MME interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying .INI files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XML configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the DNS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the S1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the S11 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the S10 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the S6a interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the S13 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Gn interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGs interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SGs interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating TAI-LAI-VLR configuration files . . . . . . . . . . . . . . . . . . . . . . . . Sv interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Sv interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating LAI - MSS configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SBc interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LCS interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SLs interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SLg interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LI interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the X1_1 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the X2 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring IPSec for lawful interception in MME . . . . . . . . . . . . . . . . . Modifying the X1_1 interface configuration . . . . . . . . . . . . . . . . . . . . . . Modifying the X2 interface configuration . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Flexi NS O&M interface to NetAct . . . . . . . . . . . . . . . . Configuring the Traffica interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring time synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11 11 14 14 16 17 20 23 26 28 31 33 34 34 37 41 41 43 45 47 47 49 51 51 53 54 60 61 62 65 67 70

3 3.1 3.2 3.3

Configuring system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring network and network element specific numbers. . . . . . . . . Configuring PLMN parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating IMSI analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

71 71 73 76

4

Testing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5 5.1 5.2

Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Allowed characters in eNB name information element . . . . . . . . . . . . . 81 Changing or removing unit IP address configuration . . . . . . . . . . . . . . . 82

Id:0900d80580a499f1 DN70669711 Issue 7-1

3

Integrating Flexi NS - MME

4

5.2.1 5.2.1.1 5.2.1.2 5.2.2 5.2.3

General instructions . . . . . . . . Steps for removing a unit . . . . Steps for adding a unit . . . . . . Removing a CPPU unit . . . . . . Adding a CPPU unit . . . . . . . .

....... ....... ....... ....... .......

...... ...... ...... ...... ......

. . . . . . . . . . . . . . . . . . . 82 . . . . . . . . . . . . . . . . . . . 82 . . . . . . . . . . . . . . . . . . . 82 . . . . . . . . . . . . . . . . . . . 84 . . . . . . . . . . . . . . . . . . . 85

6

Flexi NS - MME integration checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Id:0900d80580a499f1 DN70669711 Issue 7-1

Integrating Flexi NS - MME

List of Figures Figure 1 Figure 2

Flexi NS - MME interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 IPSec for LI network layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Id:0900d80580a499f1 DN70669711 Issue 7-1

5

Integrating Flexi NS - MME

List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17

6

Configuration file parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 XML configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 S1 timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 S1AP interface timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 GTP interface timers on the S11 interface . . . . . . . . . . . . . . . . . . . . . . . 23 S11 parameter group (BI MML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 S10 interface timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Parameters for S6a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 S6a interface timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 GTP interface timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 SGs interface timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Public warning system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 E-SMLC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Network and network element specific numbers . . . . . . . . . . . . . . . . . . 71 GUTI reallocation repetition rate parameters . . . . . . . . . . . . . . . . . . . . . 74 PLMN parameters for IMEI check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Allowed characters in Printable String information type . . . . . . . . . . . . . 81

Id:0900d80580a499f1 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Changes in Flexi NS - MME Integration

Changes in Flexi NS - MME Integration Changes in release 3.0, document issue 7-1 Parameter TAI_CHECK_S1HO added in chapter Modifying .INI files. In chapter Configuring the S10 interface, a note has been added: the S10 application IP address cannot be the same as the Gn IP address. In chapter Configuring the S6a interface, impact of redundancy and load balancing mode has been added. In chapter Configuring the Gn interface, the default value of the T3TRAU parameter has been changed to 3 s. Correction in chapter Creating TAI-LAI-VLR configuration files: the managedObject “distName” must be a unique text string. In chapter Configuring IPSec for lawful interception in MME, there are syntax corrections in steps Create rule ’PASSIKEV4’and Create rule ’ESPTNX1’. Command syntaxes have been added to activation steps in both IPSO LIC and IPSO LIB configuration instructions. Ping and output commands have been corrected in the verification instructions. In chapter Activating configuration settings: MCHU restart is required to activate application interface configuration and multihoming changes. Chapter Quick guide for installing a new software build has been removed. Changes between releases 3.0 and 2.2 Chapter

Update

Commissioning

Removed. See Commissioning Flexi Network Server.

Configuring IP addresses for units

Removed. See Site Connectivity Guidelines.

SCTP configuration

Removed. See Flexi NS User Guide.

Modifying .INI files

List of files updated. MSC_IPV4_ADDRESS_REMOTE removed. Added parameters for public warning system and overload control.

XML configuration files

New XML file FXCMSSNX.XML has been added. Configuration files are also activated by system or unit restart.

Configuring the DNS interface

Default value of the PGWRB and SGWRB parameters has been changed to RESEL.

Configuring the S1 interface

S1 parameter configuration updated (BI MML).

Configuring the S11 interface

Configurable Echo Request, GTP and S11 interface parameters added (BI MML).

Id:0900d80580a499f5 DN70669711 Issue 7-1

7

Changes in Flexi NS - MME Integration

Integrating Flexi NS - MME

Chapter

Update

Configuring the S6a interface

Maximum number of remote diameter destinations is 500. Up to 20 connections can be created per destination. Server port parameter added to the OHP command and multi connection mode parameter added to the OHC command. Offline parameters index of the OHC command removed.

Configuring the S13 interface

Up to 20 connections can be created per destination. Server port parameter added to the OHP command and multi connection mode parameter added to the OHC command. Offline parameters index of the OHC command removed.

Configuring the Gn interface

GTP timers updated (BI MML).

Creating TAI-LAI-VLR configuration files

Missing item tags added to the example of a TAI-LAI-VLR configuration file. Configuration files are also activated by system or unit restart.

Configuring the Sv interface

MSS IP address is configured with the BIR command.

Creating LAI-MSS configuration files

New chapter.

Configuring the SBc interface

Step added for delay and list size control parameters.

Configuring the SLs interface

Maximum value of the T3X01 timer has been changed to 120s.

Configuring the SLg interface

Up to 20 connections can be created per destination. Server port parameter added to the OHP command and multi connection mode parameter added to the OHC command. Offline parameters index of the OHC command removed.

LI interface configuration

•

• •

• Configuring the O&M interface to NetAct

8

The MML commands for lawful interception (LI) configuration have been changed from EJ MML to KA MML. Up to five LICs can be connected to the MME. Added chapters Modifying the X1_1 interface configuration and Modifying the X2 interface configuration. Added chapter Configuring IPSec for lawful interception in MME

SGSN/MME information added. PRFILE parameters updated.

Id:0900d80580a499f5 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Changes in Flexi NS - MME Integration

Chapter

Update

Configuring time synchronization

Removed note about system restart after system time change.

Configuring network and network element specific numbers

Single and multiple PLMN configuration supported. MML commands updated.

Configuring PLMN parameters

Step added for configuring the MNC length in E-UTRAN (MNCL) parameter.

Creating IMSI analyses

Longest digit match in IMSI analyses supported.

Changing or removing unit IP address configuration

New chapter.

Testing the configuration

Steps for pinging the LI and Traffica interfaces have been corrected.

Flexi NS - MME integration checklist

New chapter.

Id:0900d80580a499f5 DN70669711 Issue 7-1

9

Integrating Flexi NS - MME

Integrating Flexi NS - MME

1 Integrating Flexi NS - MME This document provides instructions for the integration of Flexi NS - MME. Prerequisites for integration The following tasks have to be completed before proceeding with the integration: • • •

Planning the network Installing and configuring hardware and software Commissioning checks

Complete commissioning tasks as instructed in Commissioning Flexi Network Server. Commissioning contains the software installation tasks and tests that are performed after the hardware of the network element has been installed on the site, but before the network element is connected to the operator’s network. After commissioning, the network element is ready to be integrated with the other elements of the network. Related documents • • • •

Site Connectivity Guidelines MML Command Reference Manuals Flexi NS User Guide Interface descriptions

Integration steps The following are the main steps in integration: • • • •

Configure the external interfaces. Configure the system parameters. Activate the configuration. Test the connections.

Feature and functional descriptions as well as instructions for additional configuration tasks, such as feature activation and timer settings, are provided in Flexi NS User Guide.

10

Id:0900d805809c28f7 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Configuring interfaces

2 Configuring interfaces 2.1

Flexi NS - MME interfaces Flexi NS - MME has the following interfaces towards external network elements: MME

S-GW

GTP-Cv2 UDP IP S11

DNS

S1AP

eNB

SCTP IP

GTP-Cv2 UDP IP

MSS

MSC/VLR

SvAP UDP IP

SGsAP SCTP

S10

Sv

IP SGs

S1

Gn

GTP-Cv1 UDP IP

Diameter SCTP S6a IP MME

UE

NAS S1-AP SCTP IP

NAS S13

X1_1/X2

LIPv2

SOAP* HTTP TCP/IP

TCP IP

LIC/LIB NMS *depending on the O&M function

Figure 1

SBc SBcAP SCTP IP

SLs LCSAP SCTP

CBC

eSMLC

SLg

SGSN

HSS

Diameter SCTP IP Diameter SCTP IP

EIR

GMLC

IP

Flexi NS - MME interfaces

S1-MME/S1-AP interface to the eNB The S1 interface connects the E-UTRAN to the Evolved Packet Core (EPC). It is specified as an open interface that divides the system into radio-specific E-UTRAN and EPC which handles switching, routing and service control. The S1 interface has two different instances: S1-U (S1 user plane) for connecting the eNB and the S-GW and S1-MME (S1 control plane) for connecting the eNB and the MME. Non-access stratum (NAS) interface to the UE, carried inside the S1-MME NAS forms the highest stratum of the control plane between the UE and the MME at the radio interface. The main functions of the NAS interface are supporting the mobility of the UE, supporting the session management procedures, and establishing IP connectivity between the UE and the P-GW. S11 interface to the S-GW The S11 interface is used for control information, such as EPS bearer management. The GPRS tunnelling protocol version 2 (GTPv2) is used in the S11 interface.

Id:0900d80580a499f7 DN70669711 Issue 7-1

11

Configuring interfaces

Integrating Flexi NS - MME

S10 interface to the MME The S10/GPRS tunneling protocol (GTPv2) interface connects one MME to another for inter-MME mobility and handovers. S6a/Diameter interface to the HSS S6a is a Diameter-based interface which enables access authentication and user mobility for LTE/EPC. The S6a interface enables the transfer of subscriber-related data between the MME and the Home Subscriber Server (HSS). S13/Diameter interface to the EIR The S13 interface connects the MME to the Equipment Identity Register (EIR) and is used for IMEI checking of the UE. Gn/GTPv1 interface to Gn SGSN The Gn interface connects LTE networks towards 3GPP Gn-supporting 2G/3G networks. The Gn interface is used in the interworking between the MME and the 2G/3G SGSN to enable the mobility of a subscriber between the EPC and the older 2G/3G systems. Gn interworking makes it possible for the operator to introduce LTE in hotspots without upgrading the entire core network at once, and still enable mobility. SGs/SGsAP interface to the MSC/VLR The SGs interface is used for the mobility management and paging procedures between EPS and Circuit Switched domains. Short message services (SMS) in EPS are also implemented by using this interface. The SGs reference point is used for the delivery of both mobile originating and mobile terminating SMS. Sv interface to the MSC Server The Sv interface is used between the MME and MSC Server that has been enhanced for Single Radio Voice Call Continuity (SRVCC). The interface is used to support InterRAT handover from VoIP/IMS over EPS to CS domain over 3GPP UTRAN/GERAN access. The Sv messages are based on GTPv2. SLg/Diameter interface to the GMLC The SLg/Diameter interface connects the MME to the Gateway Mobile Location Centre (GMLC). It is used to trigger location requests and reports. SLs interface to the eSMLC The SLs interface connects the MME to the Evolved Serving Mobile Location Centre (eSMLC). This is used for location calculation. SBc/SBcAP interface to the CBC The SBc/SBcAP interface connects the MME to the Cell Broadcast Center (CBC). The warning message function of SBcAP provides the means to start, overwrite and stop the broadcasting of Public Warning System (PWS) messages. PWS includes Commercial Mobile Warning System (CMAS) and Earthquake and Tsunami Warning System (ETWS) related messages. DNS client-server interface The domain name system (DNS) is a hierarchical system composed of DNS servers in the form of distributed databases for domain names and IP addresses. In Flexi NS MME, the S-GW, P-GW and SGSN selection is done using the DNS interface. DNS

12

Id:0900d80580a499f7 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Configuring interfaces

clients perform queries on the database for finding out the mapping between a particular domain name and an IP address. X1_1 and X2 interfaces to the Lawful Interception Gateway (LIG) X1_1 interface connects the MME to lawful interception controller (LIC) in LIG. X2 interface connected the MME to lawful interception browser (LIB) in LIG. The X1_1 and X2 interfaces use Nokia Siemens Networks lawful interception protocol version 2 (LIPv2). NE3S WS, Telnet and SSH operating interface to NetAct NE3S WS (Web Services) is the Nokia Siemens Networks' proprietary interface for fault, performance, and security management that supports the SOAP/HTTP transport protocols. NE3S WS is based on SOAP (XML) messages over HTTP which can have O&M data as XML attachments. The NE3S defines concepts for SOAP messaging modes, authentication and authorization, registration, and management operations. Telnet server is part of a TCP/IP protocol suite and it is used for logging into the MMI system across the network from a remote host. The Telnet server waits for an incoming request from a client (remote host). Telnet communication is initiated by the client. Remote disk access over the IP network is based on the FTP server. Reporting interface to Traffica Flexi NS – MME supports reporting interface to Traffica, which is part of the NetAct network and service management product. Flexi NS – MME sends data through the MMDU and MCHU Ethernet interface on top of the UDP/IP to Traffica.

Id:0900d80580a499f7 DN70669711 Issue 7-1

13

Integrating Flexi NS - MME

2.2 2.2.1

Configuration files Modifying .INI files Certain interface parameters and features are defined in configuration (.INI) files, for example the following:

.INI file

Parameters

Interface or function

GTPLBS

DSCP

S11

GTPLBS

GTPLBS_MSC_SERVER_PORT

Sv

MMETRH

FULL_NAME_FOR_NETWORK, SHORT_NAME_FOR_NETWORK

NITZ support in MME

MMETRH

E_NBResponseTimeout

S1

MMETRH

DNSCacheLimit

DNS

DIALBS

Diameter base timers

Diameter

MMESUBSH

MME_PASSIVE_OFFLOAD_ENABLED

MME offloading

MMESBC

CMAS_DELAY_NEW_ENB_TIME

Public Warning System

MMESBC

CMAS_MAX_CELL_ID_LIST_SIZE

Public Warning System

MMESBC

CMAS_MAX_TAI_LIST_SIZE

Public Warning System

MMESBC

CMAS_MAX_EMER_AREA_LIST_SIZE

Public Warning System

MMES1LBS

Rate limiter parameters

S1 overload control

MMES1LBS

FREEZE_TIME

S1

MMESUBSH

TAI_CHECK_S1HO

Target TAI check in S1 handovers

Table 1

Configuration file parameters The files are located on the OMU’s hard disks in the ASWDIR directory of the active SW build. Copy the files for viewing or editing all at once or one by one. If you later want to return the initial values to the .INI files, delete the files from the ASWDIR directory and restart MCHU. For instructions on setting log levels in the .INI files, see Troubleshooting Flexi NS. 1

Start a remote session (DDS). Start a remote session and check that the files exist in the ASWDIR directory: ZDDS; 0000-MAS> ZMXP:W0-ASWDIR/*.INI Example printout: VOLUME W0_OMU .DIR DIRECTORY OF /N3_1_30_0/ASWDIR/ NAME VERSION )

14

EXT VER

CHECKSUM

ID STRING

( D = DEFAULT

Id:0900d80580a59dd4 DN70669711 Issue 7-1

Integrating Flexi NS - MME

MMEPARA MMEDBH MMEDNS DIAHNDLR GTPLBS MMESLSLBS SGLBS MMES1LBS MMESBC DIALBS MMESUBSH MMETRH MMESLSH S1HANDLER MMELIBH

.INI .INI .INI .INI .INI .INI .INI .INI .INI .INI .INI .INI .INI .INI .INI

:01 :01 :01 :01 :01 :01 :01 :01 :01 :01 :01 :01 :01 :01 :02

D: D: D: D: D: D: D: D: D: D: D: D: D: D: D:

NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO

PID PID PID PID PID PID PID PID PID PID PID PID PID PID PID

2

Copy the .INI files to your local PC.

3

Modify the files as needed.

STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING STRING

See the configuration instructions for each interface. 4

After modifying the settings, copy the files back to the ASWDIR directory of the active SW build.

5

Activate the changes. Modifications made in the .INI files must be activated. To do this, restart the working MCHU unit.

Id:0900d80580a59dd4 DN70669711 Issue 7-1

15

Integrating Flexi NS - MME

2.2.2

XML configuration files Some functions of Flexi NS - MME are configurable using xml-format files. These files are located in the active software build’s LFILES directory on OMU’s disk and can be copied from there for editing. Once the edited files are loaded back into the LFILES directory and activated, the MME starts using the settings in the files. The following table shows the files, the related features, and the MML commands used for activation.

Filename

Purpose

Activate command

MML parameter

T4ILAINX.XML

Creating TAI-LAI-VLR configuration files (SGs interface)

B6L

TAMAP

TA1LSTNX.XML

Creating tracking area lists (Flexi NS User Guide)

B6L

TALIST

FXCTZONX.XML

Creating TA - time zone mapping (Flexi NS User Guide)

B6L

TZ

FXCMSSNX.XML Creating LAI - MSS configuration files (Sv interface)

B6L

LAMAP

FXCRRTNX.XML

KAX

RRT

Table 2

Creating Realm Routing Table (RRT) (Flexi NS User Guide)

XML configuration files Also system and unit restart activate the configuration files.

16

Id:0900d80580a43a4e DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.3

Configuring the DNS interface To enable node selection based on DNS lookups, configure the DNS interface as instructed below. The DNS server is implemented in the IPDU unit, and the CPPU sends requests to the internal DNS server hosted on the IPDU. The CPPU uses the configured IPDUINT association IP address as a destination address in the internal DNS query.The DNS server hosted on IPDU may not have all the answers, in which case it will send the request to an external DNS server. Configure the DNS application in the IPDU unit and the IP addresses of the external DNS server using the KA command group. See KA - Application Configuration Handling. Configure the DNS parameters, such as use of topological closeness and colocation and the blacklisting functionality, using the BI command group. See BI - Interface Configuration Handling.

g

1

Also ensure that • •

DNS server is configured according to your DNS server configuration guide. S-GW configuration in DNS is in line with the TA list configuration. See Tracking area list management (Flexi NS User Guide)

Create the DNS application interface in the IPDU unit (KAC). Use the ZKAI:; command to interrogate source IP address associations. If the DNS application IP is not created yet, create it in the IPDU (only the working unit). The KAC command creates the query source IP address from the integrated DNS server used for communicating with external DNS servers. ZKAC:IPDU,:APP=DNS:ADDRESS=””; Alternatively, use the INDEX parameter: KAC:IPDU,:APP=DNS:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,0:APP=DNS:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.1 1 ... 10.102.166.10 * System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Configure the external DNS server IP addresses (KAH). Configure the primary (PRIP) and secondary (SEIP) external DNS server IP addresses. ZKAH:PRIP=”<primary DNS server IP address>”,SEIP=”<secondary DNS server IP address>”;

Id:0900d805809d5c13 DN70669711 Issue 7-1

17

Integrating Flexi NS - MME

When more than one external DNS server is configured, queries are sent to the one with the lowest SRTT (Smoothed Round-Trip Time). To interrogate DNS server parameters, use the ZKAJ; command. To delete an external DNS server IP address, use the KAH command, enter the parameter PRIP or SEIP (or both) but leave out the IP address, for example: ZKAH:PRIP=,SEIP=; 3

Configure the DNS parameters (BIM). To interrogate the current DNS parameters, use the ZBII:DNS; command. Configure the DNS parameters using the DNS parameter group of the BIM command. You can configure all parameters at the same time or separately. Example command: ZBIM:DNS:QTIM=150,QRET=3,TOP=ON,COLOC=OFF,HNS=AUTO,SBT=1030,PBT=2-10,SGWRB=RESEL,PGWRB=ALL,NRILEN=2; 1

Configure topological closeness, colocation and host name selection. Configure topological closeness, colocation and host name selection. For detailed information on the impact of the parameter settings, see Gateway selection process (Flexi NS User Guide).

Parameter

Description

Default

Value range

TOP

Defines whether topological closeness OFF of S-GW/P-GW is considered when DNS resolves GW IP addresses.

ON/OFF

COLOC

Defines whether colocation of S-GW/PGW is considered when DNS resolves GW IP addresses.

OFF

ON/OFF

HNS

Allowed options for selecting DNS host name.

AUTO

AUTO

Auto-balanced host name selection

OFF

HNS not in use

FCD

Forced state transition

2

Configure the gateway reselection and blacklisting parameters. For the usage of blacklisting settings, see Blacklisting IP addresses (Flexi NS User Guide).

Parameter SGWRB

18

Description Defines whether reselection or reselection with blacklisting is used when session creation in the gateway fails.

Default RESEL

Value range OFF

Reselection and blacklisting disabled

RESEL

Reselection enabled

ALL

Reselection and blacklisting enabled

Id:0900d805809d5c13 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Parameter PGWRB

Description

Default

Defines whether reselection or reselection with blacklisting is used when session creation in the gateway fails.

RESEL

Value range OFF

Reselection and blacklisting disabled

RESEL

Reselection enabled

ALL

Reselection and blacklisting enabled

SBT

Timer for waiting the S-GW IP addresses to respond before MME blacklists them.

5 min

0 s to 15 min (10 s increments)

PBT

Timer for waiting the P-GW IP addresses to respond before MME blacklists them.

5 min

0 s to 15 min (10 s increments)

3

Configure DNS interface timers. Following are the DNS interface timers:

Parameter

Description

Default

Value range

QTIM

Timer for waiting a response from DNS server to MME.

1000 ms

100 ms - 10 000 ms

QRET

Maximum number of DNS query retries.

2

2 to 5

4

Configure NRI length. For the usage and structure of NRI length, see DNS Interface Description.

Parameter NRILEN

Description

Default

NRI length used as part of logical node name in DNS query during old-node (SGSN) discovery.

0 (NRI not used)

4

Value range 0 to 8

Change the DNS cache limit, if needed. DNS cache limit can be increased by setting the DNSCacheLimit parameter value in MMETRH.INI. For further information, see Gateway selection in case of several equal NAPTR records in Gateway selection process (Flexi NS User Guide). For instructions, see Modifying .INI files.

Id:0900d805809d5c13 DN70669711 Issue 7-1

19

Integrating Flexi NS - MME

2.4

Configuring the S1 interface Configure the S1 (S1-MME/S1AP) interface between the MME and the eNB. For MML information, see KA - Application Configuration Handling, BI - Interface Configuration Handling and B6 - E-UTRAN Configuration Handling.

1

Create the S1 application in the IPDU unit (KAC). In a one-shelf configuration, create the S1 application interfaces (primary and secondary) to IPDU-0: ZKAC:IPDU,0:APP=S1:ADDRESS=”<S1 VLAN IP address>”; ZKAC:IPDU,0:APP=S1SEC:ADDRESS=”<S1 VLAN IP address>”; In a multi-shelf configuration, create the S1 application interfaces to IPDU-2 instead of IPDU-0: ZKAC:IPDU,2:APP=S1:ADDRESS=”<S1 VLAN IP address>”; ZKAC:IPDU,2:APP=S1SEC:ADDRESS=”<S1 VLAN IP address>”; Alternatively, use the INDEX parameter to create the application: ZKAC:IPDU,:APP=S1:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,2:APP=S1:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.10 1 ... 10.102.164.10 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Configure S1 SCTP multihoming (BIM). Enable S1 SCTP multihoming using the S1 parameter group of the BIM command. The default value of the S1MHT parameter is OFF. Enable multihoming with the following command: ZBIM:S1:S1MHT=ON; Multihoming changes must be activated, see Activating configuration settings.

3

Configure the SCTP parameters. 1

Interrogate current SCTP parameter sets (BIH). ZBIH:IF=S1; Print out parameter values in a parameter set (for example, the S1 default set): ZBIH:NAME=S1_DEF:;

20

Id:0900d80580a5a7da DN70669711 Issue 7-1

Integrating Flexi NS - MME

2

If needed, create a custom parameter set (BIE). For example, to change DSCP value to 35: ZBIE:NAME=<custom parameter set name>,SRC=S1_DEF:DSCP=35;

3

Associate the custom parameter set to the S1 interface (BIB). ZBIB:NAME=<custom parameter set name>,IF=S1;

For further information, see SCTP configuration and S1-C SCTP (Flexi NS User Guide). 4

Set the freeze time parameter in MMES1LBS.INI. Fetch the MMES1LBS.INI file from the ASWDIR directory as instructed in Modifying .INI files. The freeze time parameter improves IPDU/CPPU fault tolerance by introducing a buffer time when a CPPU is added or goes down. This prevents interference to ongoing traffic. In the example below, freeze time is set to 50 milliseconds: ######################################################### # Configuration Parameters for IPDU/CPPU Fault Tolerance ######################################################### # Time (in milli sec) for which IPDU stops accepting any # new incoming msg triggering new procedures. FREEZE_TIME=50

Copy the modified MMES1LBS.INI file back to the ASWDIR directory of the active SW build. Changes made in .INI files must be activated, see Activating configuration settings. 5

Configure S1 handover timers (BIM). If needed, modify the timers that control the S1-based handover procedure. The timers belong to the S1 parameter group of the BIM command. For further information, see S1based handover (Flexi NS User Guide). Parameter HRA

Description Starts when S1 Handover Request is sent.

Default

Value range

1s

0.1 s - 2 s

1.5 s

0.1 s - 5 s

0.3 s

0.1 s - 0.5 s

Stops when S1 Handover Request Acknowledge is received. HNO

Starts when MME Status Transfer is sent. Stops when S1 Handover Notify is received.

HST

Starts when S1 Handover Command is sent. Stops when eNB Status Transfer is received.

Table 3

S1 timers

Id:0900d80580a5a7da DN70669711 Issue 7-1

21

Integrating Flexi NS - MME

6

Modify E_NBResponseTimeout in MMETRH.INI. This S1AP interface timer is located in the MMETRH.INI file:

Parameter

Description

E_NBResponseTimeout

Table 4

Retransmission duration for S1AP messages towards eNB (used only if there is no NAS message inside S1AP)

Default

Value range

5000 ms Recommended: 500 ms - 5000 ms

S1AP interface timer If you need to modify this timer, see Modifying .INI files for instructions. 7

Check eNB connection status (B6I). Configuration of radio network is automated in LTE and each eNB sends an S1 Setup message when they connect to the MME. This configuration information is stored in the MME and can be interrogated. For example, use the ZB6I; command to check that SCTP association is established between the MME S1 IP address and the eNB IP address. Instead of printing out all eNBs, you can use the filtering options to specify the eNBs whose connection data you want to print out. You can also select the scope of the output using the relation type parameter.

22

Id:0900d80580a5a7da DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.5

Configuring the S11 interface Configure the S11/GTPv2 interface between the MME and the S-GW. For MML information, see KA - Application Configuration Handling and BI- Interface Configuration Handling.

1

Create the S11 application interface (KAC). Create the S11 application in the IPDU (only the working unit). ZKAC:IPDU,0:APP=S11:ADDRESS=”<S11 VLAN IP address>”; Alternatively, use the INDEX parameter: ZKAC:IPDU,0:APP=S11:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,0:APP=S11:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.1 1 ... 10.102.166.10 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Modify the DSCP value GTPLBS.INI file. Fetch the GTPLBS.INI file from the ASWDIR directory as instructed in Modifying .INI files. Set the DSCP value as follows: #DSCP DSCP = 34 Copy the modified GTPLBS.INI file back to the ASWDIR directory of the active SW build. Changes made in the .INI files must be activated, see Activating configuration settings.

3

Configure GTP interface timers (BIM). If needed, modify the GTP interface timers that control the messaging in the S11 (GTPv2) interface between MME and S-GW. Parameter

Description

Value range

N3REQ

Resending of signalling request messages. 5

1-7

T3RES

Waiting time for a signalling response message.

1 -10 s

Table 5

3s

GTP interface timers on the S11 interface

Id:0900d805809ae736 DN70669711 Issue 7-1

Default

23

Integrating Flexi NS - MME

Parameter HT3

Description Starts when Handover Notify (intra-MME HO) / Forward Relocation Complete Notification (inter-MME HO) is received.

Default 0.5 s

Value range 0.5 - 5 s

When the timer elapses, MME sends UE Context Release Command to the source eNB and releases not needed resources in S-GW. Table 5

GTP interface timers on the S11 interface (Cont.)

For more information, see GTP interface parameters (Flexi NS User Guide). 4

Configure the S11 parameters (BIM). Use the S11 parameter group of the BIM command to configure the following: • •

timers that control the Echo Request messaging between MME and S-GW. For more information, see GTP-level node failure handling (Flexi NS User Guide). S1 handover -related timers and counters. For more information, see S1-based handover (Flexi NS User Guide).

Parameter

Description

Default

Value range

TECHO

Time interval for the path validation procedure. 120 s

60 - 600 s in 30 s steps

T3ECHO

Waiting time for GTP Echo Response message from S-GW.

3s

1 - 10 s

N3ECHO

Counter for retransmissions for the GTP Echo Request messages.

7

1-7

IDFT3

Starts when Create Indirect Data Forwarding Tunnel Request is sent to S-GW.

1s

1 s - 10 s

Stops when Create Indirect Data Forwarding Tunnel Response is received. IDFN3

Controls sending of Create Indirect Data Forwarding Tunnel Request messages.

1

1-7

MBRT3

Starts when Modify Bearer Request is sent.

3s

1 s - 10 s

3

1-7

Stops when Modify Bearer Response is received. MBRN3

Table 6

24

Controls sending of Modify Bearer Request messages. S11 parameter group (BI MML)

Id:0900d805809ae736 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Parameter DSRT3

Description Starts when Delete Session Request is sent.

Default

Value range

1s

1 s - 10 s

Stops when Delete Session Response is received. DSRN3

Controls sending of Delete Session Request messages.

1

1-7

DBCT3

Starts when Delete Bearer Command is sent.

1s

1 s - 10 s

1

1-7

Stops when Delete Bearer Request is received. DBCN3

Table 6

Controls sending of Delete Bearer Command messages. S11 parameter group (BI MML) (Cont.)

Id:0900d805809ae736 DN70669711 Issue 7-1

25

Integrating Flexi NS - MME

2.6

Configuring the S10 interface Configure the S10 interface between the MMEs. For MML command information, see KA - Application Configuration Handling and BI Interface Configuration Handling. DSCP value for S10 is the same as the value for S11.

g 1

The S10 application IP address cannot be the same as the Gn IP address.

Configure the S10 application interface in the IPDU (KAC). Create the S10 application in the IPDU (only the working unit): ZKAC:IPDU,0:APP=S10:ADDRESS=”<S10 VLAN IP address>”; Alternatively, use the INDEX parameter: KAC:IPDU,0:APP=S10:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,0:APP=S10:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.1 1 ... 10.102.166.10 * System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Configure the S10 interface timers (BIM). The S10 interface timers and counters control the messaging between the source MME and target MME. To interrogate the S10 parameters, use the ZBII:S10; command. You can modify the following S10 interface timer values using the BIM command:

Parameter

Default

Value range

CRST3

Context Response timer

1s

0.1 s - 5 s

CRQN3

Context Request counter

2

1-3

CACK

Context Acknowledgement timer

1s

0.1 s - 5 s

IDRT3

Identification Response timer

0.5 s

0.1 s - 2 s

IDRN3

Identification Request counter

2

1-3

FRRT3

Forward Relocation Response timer

0.5 s

0.1 s - 2 s

FRRN3

Forward Relocation Request counter

2

1-3

FRCAC

Forward Relocation Complete Acknowledgement timer

0.5 s

0.1 s - 2 s

Table 7

26

Description

S10 interface timers

Id:0900d80580a59ca2 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Parameter

Description

Default

Value range

RCRT3

Relocation Cancel Response timer

0.5 s

0.1 s - 2 s

RCRN3

Relocation Cancel Request counter

2

1-3

Table 7

S10 interface timers (Cont.) Example command: ZBIM:S10:CRST3=1.5,CRQN3=2,CACK=2.5,IDRT3=1,IDRN3=1,FRRT3=0.5,F RRN3=3,FRCAC=2,RCRT3=0.1,RCRN3=1; For more information about on the messages, see S10 Interface Description.

Id:0900d80580a59ca2 DN70669711 Issue 7-1

27

Integrating Flexi NS - MME

2.7

Configuring the S6a interface Configure the S6a connection to the HSS. The maximum number of remote diameter destinations configured in the MME is 500, and each destination can have up to 20 separate diameter connections. When multiple connections are configured for a destination, the connections are utilized either in redundancy mode or in load balancing mode, according the configurable ‘multi connection mode’ parameter of the destination. • •

If redundancy mode is selected, the first available connection having the smallest destination index will be used to route the requests. If load balancing mode is selected, the connection selected to route the request is selected with round robin algorithm, so that each new request is routed via next available connection.

The following parameters are configured in the procedure: Parameter

Format

origin-host

mmec<MMEC>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

origin-realm

mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

destination-host

.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

destination-realm

epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

Diameter client IP address

IPDU IP address selected for S6a application (see Step 2), for example, "10.102.250.6" .

HSS IP address

For example “10.200.1.220”

Table 8

Parameters for S6a configuration Destination for a subscriber is configured in the IMSI analysis and PLMN parameter configuration. For detailed MML command information, see OH - Diameter Configuration and BI - Interface Configuration Handling. 1

Configure the destination parameters (OHC). When configuring a diameter destination: • • • •

up to 20 connections can be created per destination only one transfer path can be used per connection only client role type (C) is supported multi connection mode can be load balancing (default) or redundancy.

OHC:<destination host>:,[]:,,<destination realm>::<multi connection mode>; Example command: ZOHC:hss1.epc.mnc001.mcc001.3gppnetwork.org:IPDU,0:S6,C,epc.mnc 001.mcc001.3gppnetwork.org:PATH:L;

28

Id:0900d80580a597e2 DN70669711 Issue 7-1

Integrating Flexi NS - MME

2

Configure the transfer path IP address and transfer protocol (OHP). OHP:<destination host>:,<path name number>,<protocol>:SP=<server IP>,[SPORT=<server port>]:[SP=]:CP=,[PORT=]:[CP=]; Example command: ZOHP:hss1.epc.mnc001.mcc001.3gppnetwork.org:1,1,SCTP:SP="10.200 .1.220",::CP="10.102.250.6",PORT=2001; The value of <path name number> is 1. Flexi NS uses only one transfer path per connection. When configuring port numbers: • •

3

Value range for server port (SPORT) is 1024 - 65535, except 2001. The default is 3868. Each connection must use its own client port (PORT). The range is 1024 to 65535, except 3868. Default value is 2001.

Set the origin host and origin realm FQDN for the network element (OHN). ZOHN:::[origin host],[origin realm]; Example command: ZOHN:::mmec12.mmegi32768.mme.epc.mnc001.mcc001.3gppnetwork.org, mme.epc.mnc001.mcc001.3gppnetwork.org;

g

Configuring a separate origin host for a connection is meant for multi-unit configurations, so that it is possible to configure an own host name per unit. Flexi NS - MME uses only one Diameter connectivity unit, IPDU. However, if there is only one connection for a certain application, or multiple dedicated connections, it is possible to configure those connections to use a specific host name. The host name has to be the same for all connections for a certain application. ZOHN:[<destination index>:]:[]; Example command: ZOHN:0:1:MMES6A.epc.mnc001.mcc001.3gppnetwork.org;

4

Connect to the HSS destination host (OHS). OHS:<destination host>::; The value of the parameter can be C or D: use value C to connect and value D to disconnect. Example command: ZOHS:hss1.epc.mnc001.mcc001.3gppnetwork.org:1:C;

g

When a diameter peer connected to MME disconnects due to rebooting or transport failure, the MME tries to reconnect to the disconnected peer. In such cases, the MME tries infinitely until it re-establishes the connection. The timeout value for every retry is 30 seconds, which is defined as “TC timer” in RFC3588 (section 12).

Id:0900d80580a597e2 DN70669711 Issue 7-1

29

Integrating Flexi NS - MME

5

Configure the SCTP parameters. 1

Interrogate current SCTP parameter sets (BIH). ZBIH:IF=DIA; You can also interrogate parameters of a specific Diameter connection: ZBIH:DI=<destination index>; To print out parameter values in a parameter set (for example, DIA default set for all Diameter interfaces): ZBIH:NAME=DIA_DEF:;

2

If needed, create a custom parameter set for the S6a interface (BIE). For example, to change DSCP value to 35, using the default parameter set as the source set: ZBIE:NAME=<custom parameter set name>:SRC=DIA_DEF:DSCP=35;

3

Associate the custom parameter set to the S6a interface (BIB). Associate the custom set to a specific Diameter connection using the DI parameter (for example, destination index 1). You can interrogate destination indexes using the OHI command. ZBIB:NAME=<custom parameter set name>:IF=DIA:DI=1;

For further information, see SCTP configuration (Flexi NS User Guide). 6

Configure the S6a interface timers (EJF). If needed, modify the S6a interface timers that control the authentication information request procedure and the update location procedure between the MME and the HSS. The parameters belong to the S6A parameter group of the EJF command: Parameter

Name

Default

Value range

AIA

Authentication Information Answer timeout 3 s

1 s - 10 s

ULA

Update Location Answer timeout

1 s - 10 s

Table 9

3s

S6a interface timers

Example command: ZEJF:S6A:AIA=3; For more information about procedures between MME and HSS, see S6a Interface Description.

30

Id:0900d80580a597e2 DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.8

Configuring the S13 interface Configure the S13 interface between the Flexi NS - MME and the Equipment Identity Register (EIR) to enable ME identity checking from the EIR. In addition to the S13 interface configuration, you must enable IMEI request in the SMC procedure and define the IMEI status check parameters for PLMNs. For more information about the feature and the required configuration steps, see IMEI check (Flexi NS User Guide). For MML command information, see OH - Diameter Configuration and BI - Interface Configuration Handling.

1

Configure the destination parameters (OHC). When configuring a diameter destination: • • • •

up to 20 connections can be created per destination only one transfer path can be used per connection only client role type (C) is supported. multi connection mode can be load balancing (default) or redundance.

ZOHC:<destination host>:,[]:,,<destination realm>::<multi connection mode>; Example command: ZOHC:eir.epc.mnc001.mcc001.3gppnetwork.org:IPDU,0:S13,C,plmnx_e ir.com:PATH1:L;

g 2

The <destination realm> value must match the EIR destination realm.

Configure the transfer path IP address and transfer protocol (OHP). ZOHP:<destination host>:,<path name number>,<protocol>:SP=<server IP>,[SPORT=<server port>]:[SP=]:CP=,[PORT=]:[CP=]; Example command: ZOHP:eir.epc.mnc001.mcc001.3gppnetwork.org:1,1,SCTP:SP="10.102. 250.101",::CP="10.102.250.6",PORT=2002:; The value of <path name number> is 1. Flexi NS uses only one transfer path per connection. When configuring port numbers: • •

3

Value range for server port (SPORT) is 1024 - 65535, except 2001. The default is 3868. Each connection must use its own client port (PORT). The range is 1024 to 65535, except 3868. Default value is 2001.

Set the origin host and origin realm FDQN for the network element (OHN). ZOHN:::[origin host],[origin realm];

Id:0900d805809d61a6 DN70669711 Issue 7-1

31

Integrating Flexi NS - MME

Example command: ZOHN:::originhost.mme.originrealm.nsn.com,originrealm.nsn.com;

g

Configuring a separate origin host for a connection is meant for multi-unit configurations, so that it is possible to configure an own host name per unit. Flexi NS - MME uses only one Diameter connectivity unit, IPDU. However, if there is only one connection for a certain application, or multiple dedicated connections, it is possible to configure those connections to use a specific host name. The host name has to be the same for all connections for a certain application. ZOHN:[<destination index>:]:[]; Example command: ZOHN:0:1:MMES13.epc.mnc001.mcc001.3gppnetwork.org;

4

Connect to the destination host (OHS). ZOHS:<destination host>::; The value of the parameter can be C or D: use value C to connect and value D to disconnect. Example command: ZOHS:eir.epc.mnc001.mcc001.3gppnetwork.org:1:C;

5

Configure SCTP parameters. 1

Interrogate current SCTP parameter sets (BIH). ZBIH:IF=DIA; You can also interrogate parameters of a specific Diameter connection: ZBIH:DI=<destination index>; To print out parameter values in a parameter set (for example, the DIA default set for all Diameter interfaces): ZBIH:NAME=DIA_DEF:;

2

If needed, create a custom parameter set (BIE). For example, to change DSCP value to 35, using the default parameter set as the source set: ZBIE:NAME=<custom parameter set name>,SRC=DIA_DEF:DSCP=35;

3

Associate the custom parameter set to the S13 interface (BIB). Associate the custom set to a specific Diameter connection using the destination index parameter (for example, destination indexes 1 and 6). ZBIB:NAME=<custom parameter set name>,IF=DIA:DI=1&6; You can interrogate destination indexes using the OHI command.

For further information, see SCTP configuration (Flexi NS User Guide).

32

Id:0900d805809d61a6 DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.9

Configuring the Gn interface Configure the Gn interface between the MME and the SGSN. For MML command information, see KA - Application Configuration Handling and BI Interface Configuration Handling. DSCP value for the Gn interface is the same as the value configured for the S11 interface.

1

Configure the Gn application interface in the IPDU (KAC). Create the Gn application interface in the IPDU (only the working unit). Use the KAC command: ZKAC:IPDU,0:APP=GN:ADDRESS=””; Alternatively, use the INDEX parameter: ZKAC:IPDU,0:APP=GN:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,0:APP=GN:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.1 1 ... 10.102.166.10 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Configure the GTP interface timers (BIM). If needed, modify the GTP interface timers that control the messaging on the Gn (GTPv1) interface between MME and SGSN. Use the GTP parameter group of the BIM command:

Parameter

Description

Default

Value range

N3REQ

Counter for resending of signalling request messages.

5

1-7

T3RES

Waiting time for a signalling response message.

3s

1 s - 10 s

T3TRAU

T3-TUNNEL timer for Gn RAU specified in 3GPP TS 29.060. It controls the time that MME waits in the routing area update procedure before subscriber is set to EMM-DEREGISTERED state and EPS bearer resources are released.

3s

0 s - 60 s

Table 10

GTP interface timers Example command: ZBIM:GTP:N3REQ=5,T3RES=3,T3TRAU=30; For more information, see GTP interface parameters (Flexi NS User Guide) and Gn Interface Description.

Id:0900d80580a5a8a4 DN70669711 Issue 7-1

33

Integrating Flexi NS - MME

2.10 2.10.1

SGs interface configuration Configuring the SGs interface Configure the SGs interface between the MME and the MSC/VLR. For more information, see MSC/VLR selection in CS domain services (Flexi NS User Guide). For detailed MML command information, see KA - Application Configuration Handling and BI - Interface Configuration Handling.

1

Create the SGs application interface in the IPDU unit (KAC). Create the primary and secondary SGsAP interfaces in the IPDU (only the working unit). ZKAC:IPDU,0:APP=SGSPRI:ADDRESS=”<SGs primary VLAN IP address>”; ZKAC:IPDU,0:APP=SGSSEC:ADDRESS=”<SGs secondary VLAN IP address>”; Alternatively, use the INDEX parameter: ZKAC:IPDU,0:APP=SGSPRI:INDEX=:; ZKAC:IPDU,0:APP=SGSSEC:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,0:APP=SGSPRI:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.1 1 ... 10.102.166.10 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Configure the VLR IP addresses and SCTP associations (BIV). 1

Create a new VLR configuration. Use the ADDVLR operation parameter and enter VLR ID, VLR name, primary IP address, secondary IP address (optional), and port number of the VLR connection. Example command: ZBIV:ADDVLR:VLRID=93,NAME=TEST,IPRI=”10.10.10.10”,IPSEC=”10. 10.10.10”,PORT=60000;

2

Create an SCTP association to the VLR. Use the ADDLNK operation parameter and enter the VLR ID or VLR name, ID of the SCTP association, primary IP address, secondary IP address (optional), and port number of the VLR connection. Example command:

34

Id:0900d80580a56629 DN70669711 Issue 7-1

Integrating Flexi NS - MME

ZBIV:ADDLNK:VLRID=12,AID=1,IPPRI="14.12.15.10",IPSEC=”10.10. 10.10”,PORT=60000; To interrogate current VLR parameters, use the ZBIV:INT:; command. The printout shows VLR ID, name, link status and mode of each VLR connection configured in the MME. To print out detailed information on a VLR connection, specify the VLR using VLRID or NAME. Using the BIV command, you can also modify or remove an SCTP association, remove a VLR configuration from the MME, and manage VLR offloading. 3

Configure TAI-LAI-VLR mapping. Configure and load TAI-LAI-VLR mapping. For instructions, see Creating TAI-LAI-VLR configuration files.

4

Enable SCTP multihoming (BIM). SCTP multihoming is OFF by default. Enable SCTP multihoming on the SGs interface: ZBIM:SGS:SGMHT=ON; Multihoming changes must be activated, see Activating configuration settings.

5

Configure the SCTP parameters. 1

Interrogate current SCTP parameter sets (BIH). ZBIH:IF=SGS; You can also interrogate parameter sets associated to a specific SGs connection: ZBIH:VLRI=; To print out parameter values in a parameter set (for example, SGS default set): ZBIH:NAME=SGS_DEF:;

2

If needed, create a custom parameter set for the SGs interface (BIE). For example, to change DSCP value to 35, using the default parameter set as the source set: ZBIE:NAME=<custom parameter set name>,SRC=SGS_DEF:DSCP=35;

3

Associate the custom parameter set to the SGs interface (BIB). The VLR index parameter identifies the MSC/VLR connection where the parameter set will be used (for example, VLR index 1). VLR index is the VLRID value created using the BIV command. ZBIB:NAME=<custom parameter set name>:IF=SGS:VLRI=1;

For further information, see SCTP configuration (Flexi NS User Guide). 6

Configure the SGs interface timers (BIM). To interrogate the SGs parameters, use the ZBII:SGS; command. You can modify the following SGs interface timer values using the BIM command:

Id:0900d80580a56629 DN70669711 Issue 7-1

35

Integrating Flexi NS - MME

Parameter

Description

Default

Value range

TS121

MME reset timer

54 min 8 s

8 s - 384 min 8 s

TS122

MME VLR reset timer

1s

1 s - 120 s

TS61

Location update request timer

10 s

10 s - 90 s

TS8

EPS detach response timer

4s

1 s - 30 s

TS9

IMSI detach response timer

4s

1 s - 30 s

Table 11

SGs interface timers

Example command: ZBIM:SGS:TS121=54-8,TS122=1,TS61=10,TS8=4,TS9=4; The SGs timers are associated with retry counters Ns8 (timers TS61, TS8), Ns9 (timer TS9) and Ns12 (timer TS121), all of which are set to a fixed value (2) in the MMETRH.INI file. For further details about SGs interface timers and retry counters, see SGs Interface Description.

36

Id:0900d80580a56629 DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.10.2

Creating TAI-LAI-VLR configuration files Create TAI-LAI-VLR mapping using the T4ILAINX.XML file located in the LFILES directory on OMU’s disk. The purpose of the file is to map tracking areas to location areas and VLR indices. This mapping is used for MSC/VLR selection in Combined SGs interface procedures (Flexi NS User Guide). To output existing mapping, use the command ZB6O:TAMAP;

g 1

If the tracking area list feature is in use, all tracking areas in tracking area list should be mapped to the same location area. See Tracking area list management (Flexi NS User Guide). Copy the T4ILAINX.XML file using FTP from the OMU/LFILES directory. Copy the file from the LFILES directory of the active software build on OMU’s disk, for example, DW0-/N3_1_30_0/LFILES. You can also download the XML schema files RAML21NX.XSD and RAML21NX.DTD for XML validation.

2

Open and edit the file. Edit the file as follows: In the header part, only the value for the “dateTime” can be manually edited. You can enter the date and time of file modification. The configuration consists of managedObjects, each including a TAC list, LAC list with one LAC, and the list of VLR indices. • •

g

The managedObject “distName” is a freely modifiable unique text string, whereas “class” and “operation” have constant values. Within a managedObject, enter the list of TAIs or TAI ranges. There is no limitation to TAC range size between values 0 and 65535, but observe the following rules: • Overlapping ranges are not acceptable, for example, TAC range 1-100 and also a single TAC 2. • The same TAI cannot be entered in multiple managedObjects. It is possible to enter tracking areas that do not really exist in the radio network, but note that using wide ranges has an impact on the XML configuration activation times and the CPPU memory consumption.

• •

Enter the TAI list values. Only one LAI can be configured in the LAI list. Enter the VLR identifiers in the VLR indices list. These indices refer to the VLRID values configured using the BIV command. Maximum number of VLR identifiers is 50 per managedObject.

The following is an example of a TAI-LAI-VLR configuration file.

Id:0900d80580a5662b DN70669711 Issue 7-1

37

Integrating Flexi NS - MME

<managedObject class="TAILAIVLR" distName="PLMN-PLMN/MME-1/TAILAIVLR-1" operation="create"> <list name="tailist">

262

1-100

262

101

262

102-999

230

262

<list name="laiList">

38

Id:0900d80580a5662b DN70669711 Issue 7-1

Integrating Flexi NS - MME

262

262

102

230

Id:0900d80580a4035b DN70669711 Issue 7-1

43

Integrating Flexi NS - MME

102-200

3

Save the edited file. The format of the xml file is validated using the Radio Access Markup Language schema (RAML21). Validation takes place automatically when the file is loaded in the MME, but it can also be run using any suitable application. The schema files RAML21NX.XSD and RAML21NX.DTD can be found in the OMU/LFILES directory.

4

Using FTP, copy the XML file back into the OMU/LFILES directory.

5

Activate the configuration (B6L). Use the B6L command to activate the modified settings: ZB6L:LAMAP; Even without the MML command, the configuration file will be automatically activated at the next system or unit (CPPU) restart.

6

Check the alarms. Check the live alarms in CPPUs using the ZAHO:CPPU; command. Check alarm history of CPPUs using the ZAHP:CPPU; command. This command also displays notices. Successful activation is indicated by notice 219 XML CONFIGURATION FILE SUCCESSFULLY ACTIVATED If the activation fails, alarm 3789 XML CONFIGURATION FILE ACTIVATION FAILED is raised.

44

Id:0900d80580a4035b DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.12

Configuring the SBc interface Configure the SBc interface between the MME and the CBC to enable warning message delivery. For MML information, see KA - Application Configuration Handling and BI - Interface Configuration Handling.

1

Create the SBC application interface in the IPDU unit (KAC). Create the primary and secondary SBC application interfaces in the IPDU (working unit). ZKAC:IPDU,0:APP=SBCPRI:ADDRESS=”<SBc primary VLAN IP address>”; ZKAC:IPDU,0:APP=SBCSEC:ADDRESS=”<SBc secondary VLAN IP address>”; Alternatively, use the INDEX parameter: ZKAC:IPDU,0:APP=SBCPRI:INDEX=:; ZKAC:IPDU,0:APP=SBCSEC:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,0:APP=SBCPRI:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.1 1 ... 10.102.166.10 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Enable SCTP multihoming for the SBc interface (BIM) Default value of the SBCMHT parameter is OFF. You can interrogate the setting using the ZBII:SBC; command. Enable SCTP multihoming for the interface: ZBIM:SBC:SBCMHT=ON; Multihoming changes must be activated, see Activating configuration settings.

3

Configure SCTP parameters. 1

Interrogate current SCTP parameter sets (BIH). ZBIH:IF=SBC; Print out parameter values of a parameter set (for example, the SBc default set): ZBIH:NAME=SBC_DEF:;

2

If needed, create a custom parameter set (BIE). For example, to change DSCP value to 35:

Id:0900d80580a5a7e8 DN70669711 Issue 7-1

45

Integrating Flexi NS - MME

ZBIE:NAME=<custom parameter set name>,SRC=SBC_DEF:DSCP=35; 3

Associate the custom parameter set to the SBc interface (BIB). ZBIB:NAME=<custom parameter set name>,IF=SBC;

For further information, see SCTP configuration (Flexi NS User Guide). 4

Set public warning system parameters in MMESBC.INI. The following parameters are located in MMESBC.INI and can be used to control the public warning system feature:

Parameter

Description

MME limit

Default

CMAS_DELAY_NEW_ENB_TIME

Delay forwarding of CMAS messaging to a new eNB

-

10 s

CMAS_MAX_CELL_ID_LIST_SIZE

Max cell ID list size

7950

65535

CMAS_MAX_TAI_LIST_SIZE

Max TAI list size

11130

65535

18555

65535

CMAS_MAX_EMER_AREA_LIST_SIZE Max emergency area list size Table 12

Public warning system parameters Fetch the MMESBC.INI file from the ASWDIR directory as instructed in Modifying .INI files and modify the parameter values as needed. For more information about the parameters, see Public warning system (Flexi NS User Guide). Copy the modified .INI file back to the ASWDIR directory of the active SW build. Changes made in the .INI files must be activated, see Activating configuration settings.

46

Id:0900d80580a5a7e8 DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.13 2.13.1

LCS interface configuration Configuring the SLs interface Configure the SLs interface between the MME and the Evolved Serving Mobile Location Center (E-SMLC). The maximum number of E-SMLCs connected to one MME is 5. For more information about the feature, see Location services (LCS) in EPC (Flexi NS User Guide). For MML command information, see KA - Application Configuration Handling and BI - Interface Configuration Handling.

1

Create the SLs application interface in the IPDU unit (KAC). Create the SLs primary and secondary interfaces in the IPDU (only the working unit). ZKAC:IPDU,0:APP=SLSPRI:ADDRESS=”<SLs primary VLAN IP address>”; ZKAC:IPDU,0:APP=SLSSEC:ADDRESS=”<SLs secondary VLAN IP address>”; Alternatively, use the INDEX parameter: ZKAC:IPDU,0:APP=SLSPRI:INDEX=:; ZKAC:IPDU,0:APP=SLSSEC:INDEX=:; To find out possible indexes, press ENTER after ‘index’, for example: ZKAC:IPDU,0:APP=SLSPRI:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.1 1 ... 10.102.166.10 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Enable SCTP multihoming (BIM). Default value of the SLSMHT parameter is OFF. Enable SCTP multihoming on the SLs interface: ZBIM:SLS:SLSMHT=ON; Multihoming changes must be activated, see Activating configuration settings.

3

Configure SCTP parameters. 1

Interrogate current SCTP parameter sets (BIH). ZBIH:IF=SLS; Print out parameter values in a parameter set (for example, the SLs default set):

Id:0900d80580a5a7ea DN70669711 Issue 7-1

47

Integrating Flexi NS - MME

ZBIH:NAME=SLS_DEF:; 2

If needed, create a custom parameter set (BIE). For example, to change DSCP value to 35: ZBIE:NAME=<custom parameter set name>,SRC=SLS_DEF:DSCP=35;

3

Associate the custom parameter set to the SLs interface (BIB). ZBIB:NAME=<custom parameter set name>,IF=SLS;

For further information, see SCTP configuration (Flexi NS User Guide). 4

Configure the E-SMLC (BIS). Use the BIS command to configure the E-SMLC: enter the name of the E-SMLC and primary and secondary IP addresses. E-SMLC parameters:

Parameter operation

Description operation of BIS command

Values ADD

add new E-SMLC configuration

REM

remove E-SMLC configuration

INT

interrogate E-SMLC configuration

NAME

E-SMLC name

max 10 characters

IPPRI

primary E-SMLC IP address

“”

IPSEC

secondary E-SMLC IP address (optional)

“”

Table 13

E-SMLC parameters Command example: ZBIS:ADD:NAME=TEST,IPPRI="10.10.10.10",IPSEC="12.12.12.12"; To interrogate current E-SMLC configuration, use the ZBIS:INT; command. 5

Configure the SLs timer (BIM). Use the SLS parameter group of the BIM command to configure the location request response timer (T3X01). This timer starts when Location Request message is sent and stops when Location Response message is received. The default value is 6 seconds and available value range is 3 to 120 seconds. Command example: ZBIM:SLS:T3X01=5; To interrogate the SLs parameters, use the ZBII:SLS; command.

48

Id:0900d80580a5a7ea DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.13.2

Configuring the SLg interface Configure the SLg interface between the Flexi NS - MME and the Gateway Mobile Location Centre (GMLC) to support the location services in E-UTRAN. For more information about the feature, see Location services (LCS) in EPC (Flexi NS User Guide). For MML command information, see OH - Diameter Configuration and BI - Interface Configuration Handling.

1

Configure the destination parameters (OHC). When configuring a diameter destination: • • • •

up to 20 connections can be created per destination only one transfer path can be used per connection only client role type (C) is supported multi connection mode can be load balancing (default) or redundance.

ZOHC:<destination host>:,[]:,,<destination realm>::<multi connection mode>; Example command: ZOHC:gmlc1.epc.mnc001.mcc001.3gppnetwork.org:IPDU,0:SLG,C,epc.m nc001.mcc01.3gppnetwork.org:PATH:L; 2

Configure the transfer path IP address and transfer protocol (OHP). ZOHP:<destination host>:,<path name number>,<protocol>:SP=<server IP>,[SPORT=<server port>]:[SP=]:CP=,[PORT=]:[CP=]; Example command: ZOHP:gmlc1.epc.mnc001.mcc001.3gppnetwork.org:1,1,SCTP:SP="10.10 2.250.102",::CP="10.102.250.7",PORT=2002:; The value of <path name number> is 1. Flexi NS uses only one transfer path per connection. When configuring port numbers: • •

3

Value range for server port (SPORT) is 1024 - 65535, except 2001. The default is 3868. Each connection must use its own client port (PORT). The range is 1024 to 65535, except 3868. Default value is 2001.

Set the origin host and origin realm FDQN for the network element (OHN). ZOHN:::[origin host],[origin realm]; Example command: ZOHN:::originhost.mme.originrealm.nsn.com,originrealm.nsn.com;

g

Configuring a separate origin host for a connection is meant for multi-unit configurations, so that it is possible to configure an own host name per unit. Flexi NS - MME uses only one Diameter connectivity unit, IPDU. However, if there is only one connection for a

Id:0900d805809d6708 DN70669711 Issue 7-1

49

Integrating Flexi NS - MME

certain application, or multiple dedicated connections, it is possible to configure those connections to use a specific host name. The host name has to be the same for all connections for a certain application. ZOHN:[<destination index>:]:[]; Example command: ZOHN:0:1:MMESLG.epc.mnc001.mcc001.3gppnetwork.org; 4

Connect to the destination host (OHS). ZOHS:<destination host>::; The value of the parameter can be C or D: use value C to connect and value D to disconnect. Example command: ZOHS:gmlc1.epc.mnc001.mcc001.3gppnetwork.org:1:C;

5

Configure SCTP parameters. 1

Interrogate current SCTP parameter sets (BIH). ZBIH:IF=DIA; You can also interrogate parameters of a specific Diameter connection: ZBIH:DI=<destination index>; To print out parameter values in a parameter set (for example, the Diameter default set): ZBIH:NAME=DIA_DEF:;

2

If needed, create a custom parameter set (BIE). For example, to change DSCP value to 35: ZBIE:NAME=<custom parameter set name>,SRC=DIA_DEF:DSCP=35;

3

Associate the custom parameter set to the SLg interface (BIB). The Destination index parameter identifies a specific Diameter-based connection where the parameter set will be used (destination indexes 1 and 6, for example). ZBIB:NAME=<custom parameter set name>,IF=DIA:DI=1&6; You can interrogate destination indexes using the OHI command.

For further information, see SCTP configuration (Flexi NS User Guide).

50

Id:0900d805809d6708 DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.14

LI interface configuration

2.14.1

Configuring the X1_1 interface The X1_1 interface connects the Flexi NS - MME and the lawful interception controller (LIC). Up to five LICs can be connected to the MME. For further information, see • • •

g

KA - Application Configuration Handling Modifying the X1_1 interface configuration Lawful interception (Flexi NS User Guide).

Ensure that the LIG side is configured: For more information, see the operating documentation of Nokia Siemens Networks Lawful Interception Gateway. The X1_1 configuration in the MME must match the configuration in the LIC.

1

Configure the X1_1 application interface (LIC_MME) in the MCHU (KAC). Create the X1_1 application interface in the MCHU (all working units). Use the KAC command: ZKAC:MCHU:APP=LIC_MME:ADDRESS="<X1_1 VLAN IP address>"; Alternatively, use the INDEX parameter: ZKAC:MCHU:APP=LIC_MME:INDEX=:; To find out possible indexes, press ENTER after 'index', for example: ZKAC:MCHU:APP=LIC_MME:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 10.102.113.132 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Configure the X1_1 interface (KAQ). Use the KAQ command to configure one specific LIC connection: ZKAQ:MOD:LIA=MME:LIC=:LICID=,LICIP=,LICPA=<port address of the LIC server>,LIEPA=<port address of the LIE server>,LIACT=; The value of the LIC parameter can be 1-5 (maximum 5 LICs can be configured to an MME). The value for the LIA parameter must be MME. Example command:

Id:0900d80580a5703b DN70669711 Issue 7-1

51

Integrating Flexi NS - MME

ZKAQ:MOD:LIA=MME:LIC=1:LICID=6,LICIP="123.1.1.123",LICPA=50001, LIEPA=33001,LIACT=OFF; 3

Enable LIACT (KAQ). If LIACT is not enabled when other parameters are configured in one specific LIC connection, enable it separately: ZKAQ:MOD:LIA=MME:LIC=:LIACT=;

g

The LIC parameter is used to identify the exact LIC configuration. Example command: ZKAQ:MOD:LIA=MME:LIC=1:LIACT=ON;

4

Wait for LIC initialization. After both the LIG side is configured and the X1_1 interface is configured to the MME, the LIC can start initialization and the LI solution is ready for use.

5

Check the X1_1 configurations (KAQ). To interrogate one specific LIC configuration, use the command: ZKAQ:INT:LIA=MME:LIC=; Example command: ZKAQ:INT:LIA=MME:LIC=1; Example printout: LAWFUL INTERCEPTION PARAMETERS OF MME LIE APPLICATION: 1.LIC PARAMETERS IDENTIFIER.........(LICID) IP ADDRESS.........(LICIP) LIC PORT ADDRESS...(LICPA) LIE PORT ADDRESS...(LIEPA) LIE ACTIVE.........(LIACT)

6 123.1.1.123 50001 33001 OFF

COMMAND EXECUTED To interrogate all LIC configurations, use the command: ZKAQ:INT:LIA=MME::;

52

Id:0900d80580a5703b DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.14.2

Configuring the X2 interface X2 interface connects the Flexi NS - MME and lawful interception browser (LIB). For further information, see • • •

1

KA - Application Configuration Handling Modifying the X2 interface Lawful interception (Flexi NS User Guide)

Configuring the X2 application interface (LIB) in the MMDU (KAC). Create the X2 application interface in the MMDU (all working units). Use the KAC command: ZKAC:MMDU,:APP=LIB:ADDRESS="<X2 VLAN IP address>"; Alternatively, use the INDEX parameter ZKAC:MMDU,:APP=LIB:INDEX=:; To find out possible indexes, press ENTER after 'index', for example: ZKAC:MMDU,0:APP=LIB:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 1

... 169.254.255.7 ... 10.102.113.133

*/ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

Id:0900d805809c40bd DN70669711 Issue 7-1

53

Integrating Flexi NS - MME

2.14.3

Configuring IPSec for lawful interception in MME The instructions below are for a layout where IPSec VPNs are terminated in both Flexi NS - MME and Authority side, to the same IP addresses and devices which also terminate the X1_1 and X2 interfaces. This produces two IPSec VPNs per MME: • •

IPSec VPN for X1_1 interface: between MCHU IP address and LIC IP address. IPSec VPN for X2 interface: between MMDU IP address and LIB IP address.

Before configuring IPSec, configure the external interfaces: • •

Configuring the X1_1 interface Configuring the X2 interface

For more information about IPSec configuration, see • •

Security and User Management Q2 - IPSec Configuration Handling.

Network layout and IP address examples The figure shows the network layout and the IP address values used in the configuration example:

IPSec VPN termination in LIC (IP 10.102.47.28)

IPSec VPN termination in MCHU (IP 12.11.27.196)

IKE pre-shared key authenticated host-to-host VPN for X1_1

X1_1 interface termination in MCHU (IP 12.11.27.196)

X1_1 interface termination in LIC (IP 10.102.47.28)

NSN LIG

Flexi NS - MME

LIE

MCHU

X1_1

IPSec VPN

Operator intranet

MMDU X2 interface termination in MMDU (IP 12.11.27.197)

X2

LIC

Inter-operator IP backbone, Internet..

IPSec VPN

IKE pre-shared key authenticated host-to-host VPN for X2

IPSec VPN termination in MMDU (IP 12.11.27.197)

Figure 2

54

LIB

X2 interface termination in LIB (IP 10.102.47.29) IPSec VPN termination in LIB (IP 10.102.47.29)

IPSec for LI network layout

Id:0900d80580a5703d DN70669711 Issue 7-1

Integrating Flexi NS - MME

In the MME side the IPSec VPNs apply the same redundancy logic as IP addresses and functional units which the VPNs are configured to apply. For example, if an X1-related IP address is configured for MCHU as logical and carrier sense redundant IP address, the X1-related IPSec VPN moves automatically from one Ethernet interface to another and the physical MCHU functional unit blade to another in the same context with the X1-related IP address. The same logic is applied in the MMDU functional unit blades for X2. That is, the IPSec VPN follows the IP address to which it has been configured to. IPSec VPN re-establishments (VPN renegotiations with ISAKMP/IKEv1) take place automatically in functional unit switchovers: when the logical IP address terminating the VPN moves from a physical functional unit blade to another, the logical functional unit also moves from one blade to another. Also the IPSec VPN termination moves from one blade to another in the same context with the logical IP address and logical unit. This causes IPSec VPNs to be automatically re-established since new WO blade lacks the IPSec SA (security association) details related to active IPSec VPNs. 1

Create IKE pre-shared keys to network element key storage (Q4A). Create IKE pre-shared key with the name (network element internal key identification) ‘IKEPSKLI’: ZQ4A:IKEPSKLI,S:K:A:; ENTER KEY (MAX 32 CHARACTERS) <pre-shared-key-value>

2

Create passby rules (Q2C). 1

Create rule ‘PASSV4’. The rule defines passby (plaintext) policy for all IPv4 traffic: ZQ2C:PASSV4,P,BOTH:,"0.0.0.0/0":"0.0.0.0/0":;

2

Create rule ’PASSIKEV4’. The rule defines passby (plaintext) policy for ISAKMP/IKE traffic (IPSec signalling): ZQ2C:PASSIKEV4,P,BOTH:UDP,"0.0.0.0/0",500:"0.0.0.0/0",500:;

3

Create IPSec VPN rules (Q2C). 1

Create rule ’ESPTNX1’. The rule defines IKE pre-shared key authenticated ESP in tunnel mode IPSec VPN for X1 interface purposes: ZQ2C:ESPTNX1,I,TN,"12.11.27.196","10.102.47.28":,"12.11.27.1 96":"10.102.47.28",:2,2,M,1,5,43200,PSK,IKEPSKLI:E,1800,1024 00,1,5:; The command defines IKE pre-shared key authenticated ESP in tunnel mode IPSec VPN policy for IPv4 traffic (all protocols) exchanged between network element X1related IP address (12.11.27.196, assigned for MCHU) and LIC side IP address (value 10.102.47.28). VPN is not active at this point, as activating it requires a rule to be attached to MCHU. This is done later in these instructions.

Id:0900d80580a5703d DN70669711 Issue 7-1

55

Integrating Flexi NS - MME

The rule “ESPTNX1” applies the following IPSec-related details: • • • • • • • • 2

Tunnel endpoints are the same as traffic endpoints: 12.11.27.196 in the MCHU and 10.102.47.28 in the LIC. Main mode is applied in IKE(v1) phase-1. Aggressive mode also possible, if preferred as alternative. Diffie-Hellman mode group 2 is used. Groups 1 and 5 are also possible, if preferred as alternative. PFS (Perfect Forwarding Secrecy) is enabled, and applies mode group 2. Groups 1 and 5 are also possible, if preferred as alternative. 3DES-CBC is applied as IPSec SA and IKE SA cipher. HMAC-SHA1-96 is applied as IPSec SA and IKE SA message digest. IKE SA lifetime is configured to 43200 seconds (12 hours). IPSec SA lifetime is configured to 1800 seconds (0.5 hour).

Create rule ’ESPTNX2’ (Q2C). The rule defines IKE pre-shared key authenticated ESP in tunnel mode IPSec VPN for X2 interface purposes: ZQ2C:ESPTNX2,I,TN,”12.11.27.197”,”10.102.47.29”:,”12.11.27.1 97”:”10.102.47.29”,:2,2,M,1,5,43200,PSK,IKEPSKLI:E,1800,1024 00,1,5:; The command defines IKE pre-shared key authenticated ESP in tunnel mode IPSec VPN policy for IPv4 traffic (all protocols) exchanged between network element X2related IP address (12.11.27.197, assigned for MMDU) and LIB side IP address (value 10.102.47.29).Except the VPN tunnel endpoint and traffic endpoint IP address values, rule “ESPTNX2” applies the same IPSec VPN details as rule “ESPTNX1”.

4

Configure IPSec in IPSO LIC. 1

In the Voyager main configuration page, select IPSec.

2

In the IPSec Tunnel Rules configuration page, define one tunnel rule per MME for X1. Identification example: ’MME-001-X1-rule’ In LIB (example): New Tunnel: MME-001-X1-rule Local address: 10.102.47.28 (IP address terminating X1 in LIC) Remote address: 12.11.27.196 (IP address terminating X1 in MCHU)

3

Create a new Proposal to the tunnel. A proposal is a set of encryption and authentication algorithms that will be offered to the other end of the tunnel. The other end has to configure a similar set of encryption and authentication algorithms. In LIC (example): New Proposal: MME-LI-proposal Type: ESP

56

Id:0900d80580a5703d DN70669711 Issue 7-1

Integrating Flexi NS - MME

Authentication Alg: SHA1 Encryption Alg: 3DES 4

Create a new Policy. Policy defines the use of filters together with a list of IPsec proposals. In general, create one policy item per MME for X1 (identification ’MME-001-X1-pol’).

5

Click on the policy created in previous step to navigate to Configuring Policy page. Identification example ’MME-001-X1-pol’ In the Linked Proposals section, select the proposal that was created in step 5.3 and set Priority number (example:1). In the Authentication Method section, select Pre-Share-Secret and enter the key (example: 1234567890). In sections Lifetime and Diffie-Hellman Groups, insert the values as shown below: Lifetime Seconds: 43200 Lifetime Megabytes: 100 IKE Group: 2 PFS Group: 2

6

In IPSec general configuration page, select tunnel ’MME-001-X1-rule’. The tunnel is created in step 5.2.

7

In the Tunnel configuration page, select policy as ’MME-001-X1-pol’. The policy is created in step 5.4. This will navigate to a new page.

8

Turn ON the Include End-Points in the Filters option. This will automatically select the tunnel end points into filter. Filters will be applied for all the traffic that is sent to the tunnel, so every node that is sending traffic through this tunnel needs to have its own filter.

9

Activate the corresponding configuration in Flexi NS - MME. After the IPSec tunnel configuration, you can see the configured tunnel on the Voyager Interface Configuration page, where the tunnel can be toggled ON/OFF. ZQ2K:MCHU:::::PASSV4:; ZQ2A:MCHU::PASSIKEV4,PASSV4:; ZQ2A:MCHU::ESPTNX1,PASSV4:;

5

Configure IPSec in IPSO LIB. 1

In the Voyager main configuration page, select IPSec.

2

In the IPSec Tunnel Rules configuration page, define one tunnel rule per MME for X2. Identification example: ’MME-001-X2-rule’

Id:0900d80580a5703d DN70669711 Issue 7-1

57

Integrating Flexi NS - MME

In LIB (example): New Tunnel: MME-001-X2-rule Local address: 12.11.27.197 (IP address terminating X2 in LIB) Remote address: 10.102.47.29 (IP address terminating X2 in MMDU) 3

Create a new Proposal to the tunnel. A proposal is a set of encryption and authentication algorithms that will be offered to the other end of the tunnel. The other end has to configure a similar set of encryption and authentication algorithms. In LIB (example): New Proposal: MME-LI-proposal Type: ESP Authentication Alg: SHA1 Encryption Alg: 3DES

4

Create a new Policy. Policy defines the use of filters together with a list of IPSec proposals. In general, create one policy item per MME for X2 (identification ’MME-001-X2-pol’).

5

Click on the policy created in previous step to navigate to Configuring Policy page. Identification ’MME-001-X2-pol’ In the Linked Proposals section, select the proposal that was created in step 4.3 and set Priority number (example:1). In the Authentication Method section, select Pre-Share-Secret and enter the key (example: 1234567890). In sections Lifetime and Diffie-Hellman Groups, insert the values as shown below: Lifetime Seconds: 43200 Lifetime Megabytes: 100 IKE Group: 2 PFS Group: 2

6

In IPSec general configuration page, select tunnel ’MME-001-X2-rule’. The tunnel is created in step 4.2.

7

In the Tunnel configuration page, select policy as ’MME-001-X2-pol’. The policy is created in step 4.4. This will navigate to a new page.

8

Turn ON the Include End-Points in the Filters option. This will automatically select the tunnel end points into filter. Filters will be applied for all the traffic that is sent to the tunnel, so every node that is sending traffic through this tunnel needs to have its own filter.

9

Activate the corresponding configuration in MME. After the IPSec tunnel configuration, you can see the configured tunnel on the Voyager Interface Configuration page, where the tunnel can be toggled ON/OFF.

58

Id:0900d80580a5703d DN70669711 Issue 7-1

Integrating Flexi NS - MME

ZQ2K:MMDU,0:::::PASSV4:; ZQ2A:MMDU,0::PASSIKEV4,PASSV4:; ZQ2A:MMDU,0::ESPTNX2,PASSV4:; 6

Verify IPSec for X1. 1

Check if the tunnel is working. Check the tunnel by using tcpdump in the interface that is configured for using IPSec. If you are connected on LIC, use tcpdump as shown below: >tcpdump –I -s 1500 vlan and host

2

Execute PING command (QRX). ZQRX:MCHU,::PING:IP="10.102.47.29",SRC="12.11.27.196” ,;

3

Display the IPSec statistics (Q2O). Display IPSec statistics from MCHU containing the X1-related IP address: ZQ2O:MCHU,:;

4

Output the MCHU IPSec configurations (Q2L). Q2L:MCHU::;

7

Verify IPSec for X2. 1

Check if the tunnel is working. Check if the tunnel is working by using tcpdump in the interface that is configured for using IPSec. If you are connected on LIB, use tcpdump as shown below: >tcpdump –I -s 1500 vlan and host

2

Execute PING command (QRX). ZQRX:MMDU,::PING:IP="10.102.47.29",SRC="12.11.27.197” ,;

3

Display the IPSec statistics (Q2O). Display IPSec statistics from MMDU containing the X2-related IP address: ZQ2O:MMDU,:;

4

Output the MMDU IPSec configuration (Q2L). ZQ2L:MMDU,:;

Id:0900d80580a5703d DN70669711 Issue 7-1

59

Integrating Flexi NS - MME

2.14.4

Modifying the X1_1 interface configuration In order to modify the X1_1 interface configuration, follow the steps below. For more information about the MML commands, see KA - Application Configuration Handling MML.

g 1

If you want to change the X2 application (unit level) configuration, first disable LIACT and then follow the instructions in Changing unit IP address configuration.

Disable LIACT (KAQ). ZKAQ:MOD:LIA=MME:LIC=:LIACT=OFF; When LIACT is disabled, all interceptions in the identified LIC are deactivated and the connections towards LIBs and LIC are closed. The value of LIC can be 1-5 (maximum 5 LICs configured in an MME).

2

Reconfigure the X1_1 interface (KAQ). Value for the LIC parameter must be the same as the one given in the previous step. For the LICID, LICIP, LICPA, LIEPA and LIACT parameters, at least one need to be given. ZKAQ:MOD:LIA=MME:LIC=:LICID=,LICIP=,LICPA=<port address of the LIC server>,LIEPA=<port address of the LIE server>,LIACT=; Example command: ZKAQ:MOD:LIA=MME:LIC=1:LICID=6,LICIP="123.1.1.123",LICPA=50001, LIEPA=33001,LIACT=OFF;

3

Enable LIACT (KAQ). If LIACT is not enabled in the previous step, enable it separately: ZKAQ:MOD:LIA=MME:LIC=:LIACT=ON;

4

Wait for LIC initialization. After both the LIG side is configured and the X1_1 interface is configured to the MME, the LIC can start initialization and the LI solution is ready for use.

5

Check the X1_1 configurations (KAQ). • •

60

To interrogate one specific LIC configuration, use the command: ZKAQ:INT:LIA=MME:LIC=; To interrogate all LIC configurations, use the command: ZKAQ:INT:LIA=MME::;

Id:0900d805809c40bf DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.14.5

Modifying the X2 interface configuration In order to modify the X2 interface configuration, follow the steps below.

1

Disable LIACT (KAQ). ZKAQ:MOD:LIA=MME:LIC=:LIACT=OFF; When LIACT is disabled, all interceptions in the identified LIC are deactivated and the connections towards LIBs and LIC are closed.

2

Remove the X2 application (unit level) configuration. Follow the instructions in Changing the unit IP address configuration.

3

Reconfigure the X2 application. Configure the X2 application in the MMDU. X2 interface configuration is completed when the X2 application interface and routing are in order (see Configuring the X2 interface.)

Id:0900d805809c40c1 DN70669711 Issue 7-1

61

Integrating Flexi NS - MME

2.15

Configuring the Flexi NS O&M interface to NetAct Integrating the NE3S interface between Flexi NS and NetAct consists of tasks carried out in NetAct and tasks carried out in the Flexi NS. After the connection is configured, fault management (FM) and performance management (PM) data flows from the network element to NetAct. Fault management uses NE3S WS protocol. Performance management uses NE3S WS for platform measurements and XML/FTP for application measurement transfer. Carry out the preliminary tasks and NetAct configuration tasks as instructed in Integrating Flexi NS to NetAct in NetAct operating documentation. In the Flexi NS, configuration tasks consist of configuring the local O&M DNS server, activating SSH for MML, activating measurements, and verifying that the connection works and PM and FM data is transferred from the MME to NetAct. Ports and protocols used by OMU towards NetAct are listed in the appendix in Site Connectivity Guidelines. For instructions on enabling and disabling features with PRFILE parameters, see WOParameter Handling. To find out the Flexi NS OMU IP address, use the command ZQRI:OMU;

1

Configure the DNS server. 1

Log on to the MME. telnet 10.8.xxx.xxx

2

Configure the DNS server. Use the QRK command to activate the local DNS server designated for O&M traffic handling: ZQRK:;

3

Make sure the local O&M DNS server is correctly configured. Check from the named.conf directory of the local DNS server that the DNS root servers are configured to resolve the IP addresses of NetAct’s primary (DS1) and secondary (DS2) DNS servers. For example:

options { listen-on port 53 { any; }; directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; allow-query { any; }; // DNS ROOT SERVERS forwarders {;;;;}; recursion yes;

62

Id:0900d80580a5a23c DN70669711 Issue 7-1

Integrating Flexi NS - MME

};

2

Activate SSH for the MML interface. The command line interface (MML) in the OMU is available through Telnet or SSH. Secure Shell Protocol is recommend for security reasons. Both Flexi NS and NetAct must support SSH and the feature must be configured in both. Activate SSH in the Flexi NS by opening an MML session in NetAct side or in the Flexi NS as instructed in Configuring MMI over SSH server interface for OMU in Security and User Management. For further information about SSH, see Flexi NS Security and TCP/IP Functional Description. SSH is optional and must first be enabled using the FIFILE parameter 058:0002 SSH_SERVER_FEATURE. Use the WOA command to change the activation status. Configure SSH in NetAct as instructed in Integrating Flexi NS to NetAct.

3

Verify the Flexi NS - NetAct interface connection. Use the QRS command to interrogate network status: ZQRS:OMU:::; The printout of the command shows the active interface connections of the unit. Look for the NetAct IP address and its state in the printout. Possible connection states are:

4

LISTEN

Passive open

ESTABLISHED

Data transfer state

TIME_WAIT

Closing

Activate performance measurements. Activate application measurements using the TP command group. Application measurement files are transferred to NetAct using XML/FTP. • • •

In MME and SGSN/MME, XML-format application PM file generation is by default enabled. In SGSN, XML-format application PM file generation must be enabled using PRFILE parameter 050:0004 GST_OUTPUT_XML_ENABLED (value 1). Compression of application XML-format PM files can be enabled using PRFILE parameter 050:0005 GST_OUTPUT_ZIP_ENABLED (value 1).

Activate platform measurements using the T2 command group. Platform measurements are transferred to NetAct using NE3S. • •

Allow XML-format platform PM file generation using PRFILE parameter 050:0001 MEA_REPORT_FORMATS (value 4 to enable XML). Enable the NE3S interface using PRFILE parameter 050:0002 OMES_REPORT_FORMATS (value 1).

Id:0900d80580a5a23c DN70669711 Issue 7-1

63

Integrating Flexi NS - MME

5

Verify that measurement files are generated and transferred to NetAct. Measurement files are stored in two different directories in Flexi NS: • •

•

In MME and SGSN/MME, application measurements are stored in the NSSTAT directory (under the root, at the same level with the SW packet directory). In SGSN, application measurements are stored in the NSSTAT directory (XML) or the SGSTAT directory (binary), depending on the setting of PRFILE parameter 050:0004. SGSTAT is located in MCHU or OMU, depending on the setting of PRFILE parameter 002:1834. Platform measurements in the ESYMAC/PM_QUEUE directory (under the SW packet directory).

Check that there are measurement files in the directories and that the numbers of the files change. For more information about measurement files, see Performance management in Flexi NS (Flexi NS User Guide). Verify performance data transfer on the NetAct side as instructed in Integrating Flexi NS to NetAct. 6

Verify that alarms are transferred to NetAct. Alarm files are transferred from the ESYMAC/FM_QUEUE directory to NetAct after successful NE3S/WS registration. Compare alarms in the Flexi NS and in NetAct. • •

In the Flexi NS, use the command ZAHO; to print out current alarms. In NetAct, check using the Alarm Monitor that the same alarms are shown.

You can also generate an alarm using service terminal and then verify that the alarm is shown in Alarm Monitor. For instructions, see Integrating Flexi NS to NetAct.

64

Id:0900d80580a5a23c DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.16

Configuring the Traffica interface Create the interface between Flexi NS - MME and Traffica: • •

Non-real time (NRT) and heartbeat (HB) signalling interface to MCHU Real-time (RTT) reporting interface to MMDU

The channel through which Traffica sends heartbeat messages to the MCHU unit consists of IP address and port number. Heartbeat listening port is 60000. For MML information, see KA - Application Configuration Handling and EJ - GPRS Network Handling and Traffica (Flexi NS User Guide). 1

Create the application interfaces (KAC). 1. Create the NRT application to MCHU-0 for HB signalling and non-real time reporting: ZKAC:MCHU:APP=NRT:ADDRESS=:; 2. Create the RTT application to all MMDU units for real-time reporting: ZKAC:MMDU,:APP=RTT:ADDRESS=""; Alternatively, use the INDEX parameter to create applications: ZKAC:MCHU:APP=NRT:INDEX=:; ZKAC:MMDU,:APP=RTT:INDEX=""; To find out possible indexes, press ENTER after ‘index’ in the KAC command, for example: ZKAC:MCHU:APP=NRT:INDEX /* IDENTIFY INDEX OF SOURCE IP ADDRESS FOR APPLICATION: POSSIBLE INDEXES: 0 ... 169.254.255.7 1 ... 10.102.113.196 */ System restart is needed to activate application IP address configuration changes. See Activating configuration settings.

2

Create allowed Traffica IP addresses (EJF). After this step, Traffica reports are only sent to allowed Traffica IP addresses. The MCHU unit, when receiving a HB message from a Traffica, verifies that the IP address is included in the allowed Traffica addresses and sends the requested report to the Traffica (unless some other Traffica has reserved the report earlier). If the IP address is not allowed, the report request is discarded. The IP address configuration is optional. If no Traffica IP addresses are defined (the list is empty), all Traffica addresses are allowed. Create allowed Traffica IP:

Id:0900d805809d683e DN70669711 Issue 7-1

65

Integrating Flexi NS - MME

ZEJF:TRAF:ID=,IP=""; Example command: ZEJF:TRAF:ID=3,IP="192.168.1.1"; ZEJF:TRAF:ID=3,IP="AAAA:0000:0000:0000:0000:0000:0000:3333"; To interrogate all Traffica IP addresses, use the command ZEJH:TRAF;. To delete allowed Traffica IP, enter the ID and then value 0 for the IP address: ZEJF:TRAF:ID=,IP="0";

66

Id:0900d805809d683e DN70669711 Issue 7-1

Integrating Flexi NS - MME

2.17

Configuring time synchronization System time management Manual time management is possible using the command line interface. However, the accuracy of time stamps in the system is vital and to preserve a relatively good accuracy network time protocol (NTP) or simple network time protocol (SNTP) can be used. NTP is a protocol designed to synchronize the clocks of computers over a network. NTP version 3 is an internet draft standard, formalized in RFC 1305. NTP version 4 is a significant revision of the NTP standard, and is the current development version, but has not been formalized in an RFC. Simple NTP (SNTP) version 4 is described in RFC 4330. SNTP is provided for the remote time synchronization. Flexi NS - MME can fetch the correct time from a NTP or SNTP server, using the SNTP. Three different NTP or SNTP addresses can be configured on the Flexi NS - MME. Enable SNTP as instructed in the steps below.

g

Adjusting time using DCA/DCS commands should be avoided, as it might cause service disruption. Summer time/standard time To change the clock of the network element to summer time or standard time, use the DCT command (see DC - Clock Handling). Set summer time on: ZDCT:ST=ON:; Example printout: TIME ADJUSTED FORWARDS 1 HOUR TIME UPDATED IN ALL COMPUTER UNITS NEW TIME 2012-07-04 15:27:30 SUMMER TIME IS ON COMMAND EXECUTED To set the clock to standard time (backwards 1 hour), use the same command with value ST = OFF.

1

Enable SNTP (WOA). ZWOA:2,1355,A:;

2

Set NTP server IP address (DCW). There are two types of SNTP related IP addresses: NTP server addresses and local communication IP address. NTP server addresses are defined as calendar time reference for SNTP client of the network element. You can use NTP or SNTP server as the source for the calendar time. Both the IP address format and the host name format are accepted. Optional local communication IP address defines the IP address which SNTP uses in its communication. The need to define this address depends on the IP network configuration. For example, if there are several IP addresses defined for OMU from the same subnet, you might want the SNTP to use only one of them. You can enter one address at time with the DCW command.

Id:0900d805809b8b83 DN70669711 Issue 7-1

67

Integrating Flexi NS - MME

Use the parameters as follows: • • •

•

Use the mandatory address ID () parameter to identify which address you are defining. Use values from 1 to 3 to define NTP server address. You can define from one to three addresses to be used as calendar time reference. Use value A to define local communication IP address for SNTP. In case local communication IP address is not set, all IP addresses defined in OMU are used. Note that this command does not create new IP address, it only binds SNTP to existing one. This means you can use only already existing IP addresses with this parameter value. Use the mandatory IP address parameter to identify the IP address in numerical format or as host name for the calendar time reference and optional local communication IP address. Enter the value between quotation marks

DCW:,<"IP-address">; Example command: ZDCW:1,"10.102.157.4":; 3

Set the local communication IP address (DCW). DCW:,<"IP-address">; The IP address is typically the OMU IP address. Example command: ZDCW:A,"10.102.156.78":;

4

Check the SNTP configuration (DCP). ZDCP:; Example printout: CALENDAR TIME REFERENCE POLLING INTERVAL IN MINUTES: 15 MINIMUM CORRECTED CALENDAR TIME DIFFERENCE IN MILLISECONDS: 100 CALENDAR TIME REFERENCES: 1. * 10.102.157.4 2. 3.

5

Check the active Internet connections of OMU-0 (QRS). ZQRS:OMU,0:; Example printout:

UNIT: OMU-0 Active Internet connections (including servers)

68

Id:0900d805809b8b83 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Proto Recv-Q Send-Q udp 0 0

Local Address Foreign Address 10.102.156.78.ntp *.*

Id:0900d805809b8b83 DN70669711 Issue 7-1

State

69

Integrating Flexi NS - MME

2.18

Activating configuration settings The following configuration changes require activation: • • • •

all modifications made in the .INI files changes in the mobile country code (MCC) and mobile network code (MNC) values (WVS command) application interface configuration (KAC command) SCTP multihoming settings (BIM command).

Restarting the active (WO) MCHU unit activates all settings. MCHU distributes the changes to the other functional units. 1

Restart the active MCHU. Use the USU command. ZUSU:MCHU,:;

70

Id:0900d80580a5a7d8 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Configuring system parameters

3 Configuring system parameters 3.1

Configuring network and network element specific numbers Multiple PLMN support When the multiple PLMN support is enabled with the PRFILE parameter 002:2222 MULTIPLE_PLMN_ENABLED, MCC, MNC, MMEGI and MMEC can be separately configured for each supported PLMN. The maximum number of supported PLMNs in the MME is 32. The MME relative capacity is common for all configured PLMNs. By default, the feature is disabled. When the feature is disabled, only a single PLMN can be configured on the MME. Network and MME identifiers The following numbers are necessary for identification of the network and the MME within the network:

Parameter

Explanation

MCC

Mobile country code: a part of the mobile station identification, identifying uniquely the home country of the mobile station.

MNC

Mobile network code: a combination of digits in the national part of the mobile station identification, identifying uniquely the home PLMN of the mobile station. MNC defines the PLMN for the Flexi NS – MME as a network element. The value is used for the S1 setup, allowing the eNB to connect to the MME.

MMEC

MME code uniquely identifies an MME within an MME pool area.

MMEGI

MME group id is the unique identity of the MME pool within the PLMN.

MMERC

The relative capacity (weight factor) of an MME with respect to other MMEs in the pool in order to load-balance MMEs within a pool.

Table 14

Network and network element specific numbers These numbers are used in the network for the following purposes: •

•

•

The configured MNC, MCC, MMEGI and MMEC values together form the globally unique MME identifier (GUMMEI). With GUMMEI, the eNB can identify an MME logical node. GUMMEI forms a part of the globally unique temporary identity (GUTI), which has two main components: • GUMMEI to uniquely identify the MME which allocated the GUTI • M-TMSI to uniquely identify the UE within the MME that allocated the GUTI. MME identity (MMEI) consists of MMEGI and MMEC. These two values are necessary when S1 flex (MME pooling) is used (see S1 Flex in Flexi NS User Guide). MMEC together with M-TMSI form the S-TMSI which is used for paging the UE. The MNC and MCC values constitute the serving network ID which is used, for example, in security key generation. The MME will accept the connection from the eNB only if the MCC and MNC coming in the S1 setup match this setting.

Id:0900d80580a5a057 DN70669711 Issue 7-1

71

Configuring system parameters

Integrating Flexi NS - MME

Configure the network and network element specific numbers using the WV MML. For more information, see WV – GSM Network and Network Element Specific Number Handling. 1

Create network element specific numbers (WVS). Syntax when multiple PLMN support is enabled: WVS:SPLI=:MCC=<mobile country code>,MNC=<mobile network code>:MMEC=<mme code>:MMEGI=<mme group id>; Example command: ZWVS:SPLI=2:MCC=012,MNC=23,MMEC=12,MMEGI=32768; The MME code uniquely identifies an MME within an MME pool area. The value range of the parameter is 1 - 255 decimal digits. The recommended value range for the MME Group ID in Flexi NS - MME is 32768…65535. (This equals to 0x8000...0xFFFF as hex values. Highest bit indicates the unit is MME).

2

Define the MME relative capacity (WVF). This parameter identifies the relative capacity of an MME with respect to other MMEs in the pool (defined by MMEGI). The value range of the parameter is 0 - 255 decimal digits. For example, load of a newly installed MME can be quickly increased to normal level by using the maximum weight factor. The MME relative capacity is configured only once. If no value is given, the default value 25 is used. WVF:MMERC=<mme relative capacity>); Example command: ZWVF:MMERC=50;

72

Id:0900d80580a5a057 DN70669711 Issue 7-1

Integrating Flexi NS - MME

3.2

Configuring PLMN parameters Create the home PLMN and if needed, roaming PLMNs. The PLMNs also get a destination realm value which defines the HSS connection to be used. You can add a parameter set of their own both for home PLMN subscribers and for each visiting PLMN roaming subscriber. The same parameter set can also be used for several PLMNs. To output PLMN parameters, use the MXP command. For MML command details, see MX – PLMN Parameter Handling.

1

Create home PLMN (MXA). MXA:,Y; The last parameter defines the roaming status of the subscriber. If the parameter value is N (default), the PLMN parameter values apply to a visiting subscriber. Value Y denotes home PLMN. Example command: ZMXA:HOMEPLMN,Y;

2

Add destination realm, host name and subscriber specific HSS address usage to the PLMN (MXN). Define the destination realm and the HSS host name and specify subscriber specific HSS address usage (see HSS selection in Flexi NS User Guide for more information). MXN:,HSS:DEST=<destination_realm>,HOST=, HAU=Y/N; Example command: ZMXN:HOMEPLMN,HSS:DEST=nsn.com,HOST=hss1.nsn.com,HAU=Y; If you want to remove a destination realm or host name, use values DEST=0 or HOST=0.

3

Add AUC destination realm and host name for the home PLMN (MXN). If a separate Authentication Center (AUC) is configured for a PLMN, the Authentication Information Request (AIR) is sent to the AUC, while all other S6a messages are sent to the HSS. The AuC connection is configured as a S6a HSS connection using OH - Diameter Configuration MML. When configuring diameter routing, it should be taken into account that AuC is just like any other S6a connection. It is recommended to use own realm for AuC to avoid misrouting. The AUC parameter group of the MXN command is available only for the home PLMN. MXN:,AUC:AUCDEST=, AUCHOST=; Example command: ZMXN:HOMEPLMN,AUC:AUCDEST=DEST.BEDROCK.COM,AUCHOST=HOST.BEDROCK .COM;

Id:0900d80580a5a058 DN70669711 Issue 7-1

73

Integrating Flexi NS - MME

If you want to remove AUC destination realm or host name, use values AUCDEST=0 or AUCHOST=0. 4

Define roaming for visitor PLMN (MXN). With the roaming control parameter, you can allow only local breakout (LBO), only home routed traffic (HRT), both local breakout and home routed traffic (BOTH), or deny roaming (NOT). For more information, see Roaming (User Guide). MXN:,ROAM:CTRL=; Example command: ZMXN:ROAMINGPLMN,ROAM:CTRL=LBO;

5

Define GUTI reallocation repetition rate parameters (MXN). GUTI reallocation repetition rate can be defined for each of the following procedures separately (it is not subscriber-specific):

Parameter

Explanation

Default

GATT

GUTI reallocation repetition rate for attach

1

GTAU

GUTI reallocation repetition rate for tracking area update

1

GPTAU

GUTI reallocation repetition rate for periodic tracking area update

1

Table 15

GUTI reallocation repetition rate parameters The parameters can get values in the range 0 - 255. Value 0 means that repetition rate is disabled, that is, GUTI reallocation is not done (new GUTI is allocated only in successful attach). Value 1 means that GUTI is reallocated each time the procedure takes place. If repetition rate is set, for example, to value 3 for tracking area update (TAU), then, on average, GUTI is reallocated in every 3rd TAU. However, GUTI allocation is always done if no valid GUTI exists. Default values are recommended. Use the MXN command to define GUTI reallocation repetition rates, for example, for attach (GATT parameter): MXN:,GRRR:GATT=; Example command: ZMXN:HOMEPLMN,GRRR:GATT=1; 6

Define IMEI status check from EIR for a PLMN (MXN). Configure IMEI status check from EIR using the MXN command and the following parameters: Parameter

Default

Value range

EIR

EIR destination realm

-

1 – 49 characters

EIRHOST

EIR host name

-

1 - 110 characters

Table 16

74

Name in MX MML

PLMN parameters for IMEI check

Id:0900d80580a5a058 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Parameter

Name in MX MML

Default

Value range

ABLK

Allow blacklisted equipment

OFF

ON/OFF

AUNK

Allow unknown equipment

OFF

ON/OFF

ICHVT

IMEI check validity timer

0 -0 (OFF)

(0...30)-(0...23) (dd-hh)

Table 16

PLMN parameters for IMEI check (Cont.)

Example command: ZMXN:IPC-VPC-04,IMEICH:EIR=DESTREALM,EIRHOST=HOSTNAME,ABLK=OFF, AUNK=OFF,ICHVT=01-12; By default, blacklisted and unknown equipment are rejected. By choosing the value ON, either or both can be allowed to attach. If you want to remove EIR destination realm or host name, use values EIR=0 or EIRHOST=0. By default, IMEI check validity timer is OFF (value 0-0). To enable IMEI check during service request and TAU, set the ICHVT value to days-hours (dd-hh). For more information, see IMEI check (User Guide). 7

Define MNC length (MXN). Configure MNC length using the MXN command and the MNC length in E-UTRAN (MNCL) parameter. MXN:,MISC:MNCL=; The MNCL parameter defines how many digits from IMSI are taken to form the MNC, when the MME makes APN operator identifier (APN-OI) for subscriber DNS queries. Example command (setting the length to three digits): ZMXN:ETPLMN,MISC:MNCL=LONG; By default, the MNC length in E-UTRAN is two digits (value SHORT).

Id:0900d80580a5a058 DN70669711 Issue 7-1

75

Integrating Flexi NS - MME

3.3

Creating IMSI analyses IMSI is the unique identifier of a particular mobile and consists of the mobile country code, mobile network code, and subscription identifier. IMSI analysis is carried out to identify the network the IMSI belongs to and whether a subscriber from that network may use a given network (other than local subscribers need a roaming agreement for accessing the network). That is, IMSI analysis links the subscriber to the correct PLMN parameter set, and if the analysis does not find a matching PLMN, roaming is not allowed. Flexi NS supports the longest digit match in IMSI analysis feature which means that instead of selecting the first matching result, best match analysis principle is used. You can create analyses of different length, with IMSI numbers longer or shorter than those of the existing analysis, and starting with the same digits. If there are several analyses starting with the same digit sequence, the system compares the analyses to find a best matching analysis for a given number. For example, if you have created an analysis for a digit sequence 1234 (PLMN parameter set A), and another one for a specific digit sequence 1234789 (PLMN parameter set B), and a number 123478911 is brought to analysis, there are two possible results, but 1234789 (returning PLMN parameter set B) is selected, because this is the longest match. Create IMSI analyses using the CF - MSC/VLR Digit Analysis Handling MML: • • •

1

CFC command to create IMSI analyses CFD command to delete IMSI analyses CFI command to interrogate IMSI analyses.

Create IMSI analysis for PLMN (CFC). CFC:IMSI=,PLMN=,; Example command: ZCFC:IMSI=4321,PLMN=HOMEPLMN,;

76

Id:0900d805809ad663 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Testing the configuration

4 Testing the configuration 1

Test that internal routing works. 1

Ping IPDU from CPPU. ZQRX:CPPU,<WO unit index>::PING:IP="";

2

Ping IPDU from MMDU. ZQRX:MMDU,0::PING:IP=""; ZQRX:MMDU,1::PING:IP="";

2

Test that external routing works. Ping the external interfaces.

g

To print out the SRC addresses of the external interfaces, use the ZKAI; command. If multihoming is in use on the interface, ping also the secondary connections. 1

Ping HSS. ZQRX:IPDU,<WO unit index>::PING:IP=",SRC=”";

2

Ping eNB. ZQRX:IPDU,<WO unit index>::PING:IP="<eNB IP>",SRC=”";

3

Ping S-GW. ZQRX:IPDU,<WO unit index>::PING:IP=”<S-GW IP>”,SRC=”";

4

Ping SGSN. ZQRX:IPDU,<WO unit index>::PING:IP=”<SGSN IP>”,SRC=”";

5

Ping MSC/VLR. ZQRX:IPDU,<WO unit index>::PING:IP=”<MSC/VLR SGS PRI IP>”,SRC=”";

6

Ping DNS. ZQRX:IPDU,<WO unit index>::PING:IP=””,SRC=”";

7

Ping LIC. ZQRX:MCHU,<WO unit index>::PING:IP=””,SRC="";

Id:0900d80580a346e1 DN70669711 Issue 7-1

77

Testing the configuration

Integrating Flexi NS - MME

8

Ping LIB. After the X1_1 interface configuration, the LIC starts initialization, during which the LIC informs the MME about the IP addresses of LIB servers. LIB IP addresses may also be included in network plan. ZQRX:MMDU,0::PING:IP=””,SRC="Local LIB IP";

9

Ping Traffica. ZQRX:MCHU,<WO unit index>::PING:IP=””,SRC=”"; ZQRX:MMDU,<WO unit index>::PING:IP=””,SRC=”";

10 Ping EIR. ZQRX:IPDU,<WO unit index>::PING:IP="<EIR IP>,SRC=”"; 11 Ping AuC. ZQRX:IPDU,<WO unit index>::PING:IP=",SRC=”"; 12 Ping MME. ZQRX:IPDU,<WO unit index>::PING:IP="<MME IP>,SRC=”"; 13 Ping MSC server ZQRX:IPDU,<WO unit index>::PING:IP="<MSS IP>,SRC=”"; 14 Ping CBC ZQRX:IPDU,<WO unit index>::PING:IP=",SRC=”"; 15 Ping E-SMLC ZQRX:IPDU,<WO unit index>::PING:IP="<E-SMLC IP>,SRC=”"; 16 Ping GMLC ZQRX:IPDU,<WO unit index>::PING:IP=",SRC=”"; 3

Check that connections are up. 1

Check the HSS connection. ZOHI;

2

Check the eNB connection status. Check that SCTP association is established between the MME S1 IP address and the eNB IP address.

78

Id:0900d80580a346e1 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Testing the configuration

ZB6I; Example printout: ENB: MCC === 234 234 234

MNC === 22 22 22

ENB ID ========== 2 3 13

ENB IP ======================================= 10.102.116.10 10.102.116.18 10.102.116.98

S1 CONN AMOUNT ============== 0 0 0

TOTAL NUMBER OF ENBS: 00003 TOTAL NUMBER OF S1 CONNECTIONS: 00000 COMMAND EXECUTED 3

Check the SCTP association to MSC/VLR and HSS. Check that the SCTP association is established between the MME and the MSC/VLR (MscVlrPort=29118). Check that the SCTP association is established between the MME and the HSS. In this example, MME's local port is 2001 and remote port is 3868. ZQRS:IPDU,0:; Example printout:

Flexi NS

NV-NS-3

UNIT: IPDU-0 Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address tcp 0 0 169.254.255.1:53 0.0.0.0:* tcp 0 0 127.0.0.1:953 0.0.0.0:* udp 0 0 169.254.255.1:53 0.0.0.0:* udp 0 0 169.254.255.1:21004 0.0.0.0:* udp 0 0 169.254.255.1:21011 0.0.0.0:* udp 0 0 127.0.0.1:21021 0.0.0.0:* udp 0 0 127.0.0.1:50009 0.0.0.0:* udp 0 0 0.0.0.0:50010 0.0.0.0:* udp 0 0 169.254.255.1:50021 0.0.0.0:* udp 0 0 127.0.0.1:50031 0.0.0.0:* udp 0 0 127.0.0.1:50036 0.0.0.0:* udp 0 0 127.0.0.1:1112 0.0.0.0:* udp 0 0 10.102.113.76:2123 0.0.0.0:* udp 0 0 10.102.113.68:2123 0.0.0.0:* udp 0 0 169.254.255.1:36415 0.0.0.0:* udp 0 0 ::ffff:127.0.0.1:50006 :::* udp 0 0 :::50037 :::* sctp 127.0.0.1:36412 sctp 0 0 10.102.113.98:57113 10.102.184.11:29118 sctp 0 0 10.102.113.90:2001 10.102.184.16:3868

Id:0900d80580a346e1 DN70669711 Issue 7-1

State LISTEN LISTEN

LISTEN ESTABLISHED ESTABLISHED

79

Testing the configuration

Integrating Flexi NS - MME

10.102.113.94 4

10.255.26.2

Check the NetAct connection. Interrogate network status: ZQRS:OMU,::; Check from the command printout that the NetAct IP address is in the correct state.

80

Id:0900d80580a346e1 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Additional information

5 Additional information 5.1

Allowed characters in eNB name information element The information type of the eNB name information element, used, for example, in S1 Setup Request, is Printable String. This information type comprises a subset of the ASCII character set which does not include, for example, the at sign (@), ampersand (&), or hash mark (#). Allowed characters are: Capital letters

A, B, ..., Z

Small letters

a, b, ..., z

Digits

0, 1, ..., 9

Space

(space)

Apostrophe

'

Parenthesis

()

Plus sign

+

Comma

,

Hyphen

-

Full stop

.

Solidus

/

Colon

:

Equals sign

=

Question mark

?

Table 17

Allowed characters in Printable String information type

The MME only supports the characters listed above. If the eNB name information element contains any other characters, certain operations, such as S1 Setup, may fail.

Id:0900d80580a56522 DN70669711 Issue 7-1

81

Integrating Flexi NS - MME

5.2 5.2.1

Changing or removing unit IP address configuration General instructions If you change or remove the unit IP address configuration, remember to make the same changes in the application associations (KA MML). Removing a functional unit may be needed, for example, because of an error in the configuration process or a unit fault. After the steps presented below, the unit can be removed for maintenance tasks or reconfigured. See Removing a CPPU unit for an example of unit removal. For an example of adding or reconfiguring a unit, see Adding a CPPU unit. For detailed information about unit IP configuration, see Site Connectivity Guidelines. MML command groups used in the procedures: • • • • •

5.2.1.1

KA - Application Configuration Handling QK - IP Routing Data Handling QR - TCP/IP Stack Data Handling US - Working State and Restart Handling WT - Equipment Management

Steps for removing a unit Remove a unit in a controlled manner as follows: 1. Change the unit state to TE (USC). ZUSC:,:TE,; 2. Delete the application IP address (KAD). ZKAD:,:APP=:VER=:; 3. Delete routing (QKP). Delete route by number: ZQKP::; To find out all static routes: ZQKO:; 4. Delete the IP interfaces of the unit (QRG). ZQRG:,:::; 5. Change the unit state to SE-NH (USC). ZUSC:,:SE,; ZUSC:,:SE,;

5.2.1.2

Steps for adding a unit Add or reconfigure a unit as follows: 1. Create the functional unit (WTU). ZWTU:,::MB=<message bus address>:; 2. Create the blade description (WTP). ZWTP:,:,,::;

82

Id:0900d80580a2fbc2 DN70669711 Issue 7-1

Integrating Flexi NS - MME

3. Change the unit state to WO-EX (USC). ZUSC:,:SE; ZUSC:,:TE; ZUSC:,:WO; 4. Create the unit IP interfaces (QRA). ZQRA:,:::; 5. Create the logical carrier sense IP address (QRN). ZQRN:,:: ””,,L::; 6. Create local IP address -based default gateway routing (QKM). ZQKM:,::"":"":; 7. Configure the application interface (KAC). ZKAC:,:APP=:INDEX=:; 8. Activate the IP address configuration (USU). ZUSU:MCHU,:;

Id:0900d80580a2fbc2 DN70669711 Issue 7-1

83

Integrating Flexi NS - MME

5.2.2

Removing a CPPU unit Removing a CPPU unit may be required, for example, if the unit fails to work because of an error in the configuration phase. In that case, remove the unit first as instructed below, then reconfigure it as instructed in Adding a CPPU unit. In this example, CPPU4 is removed. For more information about the MML commands used in the procedure, see the following command reference manuals: If a unit fault is suspected, see Troubleshooting Flexi NS and Maintaining and Troubleshooting Flexi Network Server.

1

Change the CPPU state (USC). Change the unit state to TE: ZUSC:CPPU,4:TE,;

2

Delete the internal application IP address from the CPPU (KAD). Delete CPPUINT application IP address. ZKAD:CPPU,4:APP=CPPUINT:VER=IPV4:;

3

Delete the IP interfaces of the unit (QRG). Delete all the IP interfaces of the unit. For example, to delete the EL0 interface, give the following command: ZQRG:CPPU,4::EL0:; ZQRG:CPPU,4::EL1:;

4

Change the unit state to SE-NH (USC). Change the unit state to separated - no hardware as follows: ZUSC:CPPU,4:SE,; ZUSC:CPPU,4:SE,; The unit is now completely removed from the network element configuration. You can now proceed to hardware maintenance tasks, or reconfigure the unit.

84

Id:0900d80580a2fc4f DN70669711 Issue 7-1

Integrating Flexi NS - MME

5.2.3

Adding a CPPU unit You can add a CPPU unit into the configuration as instructed below. In this example, CPPU-4 is added.

1

Create the CPPU (WTU, WTP). Create the functional unit description and blade description for the CPPU. ZWTU:CPPU,4:1A001-00:MB=46:; ZWTP:CPPU,4:ACPI4_A,0,7::;

2

Change the CPPU state to WO (USC). Change the working state of CPPU-4 into WO-EX. ZUSC:CPPU,4:SE; ZUSC:CPPU,4:TE; ZUSC:CPPU,4:WO;

3

Create the IP interfaces of CPPU (QRA). Create the internal interface for the CPPU. ZQRA:CPPU,4:EL0::; ZQRA:CPPU,4:EL1::;

4

Create the logical carrier sense IP address of the internal interface in the CPPU (QRN). ZQRN:CPPU,4:EL0,EL1:”<EL0/EL1_IP_for_CPPU”,23,L::;

5

Create the internal CPPUINT application interface between IPDU and CPPU (KAC). Configure the CPPUINT application interface. ZKAC:CPPU,4:APP=CPPUINT:INDEX=:;

6

Activate the IP address configuration (USU). Restart the active MCHU to activate the IP address configuration. ZUSU:MCHU,:;

Id:0900d80580a2fc47 DN70669711 Issue 7-1

85

Flexi NS - MME integration checklist

Integrating Flexi NS - MME

6 Flexi NS - MME integration checklist MME specifications Customer: MME name: MME C-number: MME SW level:

Date:

Checked by:

Date:

Approved by: DNS interface

Integration phase

Completed

DNS application to IPDU-0 (KAC)

[]

PRIP and SEIP external DNS server IP addresses (KAH)

[]

Topological closeness (BIM)

[]

Colocation (BIM)

[]

Host name selection (BIM)

[]

S-GW reselection/blacklisting (BIM)

[]

P-GW reselection/blacklisting (BIM)

[]

S-GW blacklisting timeout (BIM)

[]

P-GW blacklisting timeout (BIM)

[]

DNS query timers (BIM)

[]

NRI length (BIM)

[]

MMETRH.INI: DNSCacheLimit=

[]

S1 interface (MME - eNB) Integration phase

Completed

S1 and S1SEC applications to IPDU-x(KAC)

[]

SCTP multihoming (BIM)

[]

SCTP parameter set (BIE, BIB)

[]

S1 handover timers (BIM)

[]

MMES1LBS.INI: FREEZE_TIME=

[]

MMETRH.INI: E_NBResponseTimeout=

[]

86

Id:0900d805809d5b59 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Flexi NS - MME integration checklist

S11 interface (MME - S-GW) Integration phase

Completed

S11 application to IPDU-0(KAC)

[]

S11/GTP interface parameters (BIM)

[]

GTPLBS.INI: DSCP = 34

[]

S10 interface (MME - MME) Integration phase

Completed

S10 application to IPDU-0 (KAC)

[]

S10 timers (BIM)

[] S6a interface (MME - HSS)

Integration phase

Completed

Destination (IPDU-0) (OHC)

[]

Transfer path and protocol(OHP)

[]

Origin host, origin realm (OHN)

[]

HSS destination host (OHS)

[]

SCTP parameter set (BIE, BIB)

[]

S6a timers (EJF)

[] S13 interface (MME - EIR)

Integration phase

Completed

Destination (IPDU-0) (OHC)

[]

Transfer path and protocol (OHP)

[]

Origin host, origin realm (OHN)

[]

EIR destination host (OHS)

[]

SCTP parameter set (BIE, BIB)

[]

Gn interface (MME - SGSN) Integration phase

Completed

GN application to IPDU-0(KAC)

[]

GTP interface timers (BIM)

[]

Id:0900d805809d5b59 DN70669711 Issue 7-1

87

Flexi NS - MME integration checklist

Integrating Flexi NS - MME

SGs interface (MME - MSC/VLR) Integration phase

Completed

SGSPRI and SGSSEC applications to IPDU-0 (KAC)

[]

VLR configuration and SCTP association (BIV)

[]

TAI-LAI-VLR mapping (xml)

[]

Mapping list loaded (B6L)

[]

SCTP multihoming (BIM)

[]

SCTP parameter set (BIE, BIB)

[]

SGs interface timers (BIM)

[]

Sv interface (MME - MSS) Integration phase

Completed

SV application to IPDU-x(KAC)

[]

MSS IP addresses (BIR)

[]

LAI - MSS mapping (xml)

[]

Mapping list loaded (B6L)

[]

GTPLBS.INI: GTPLBS_MSC_SERVER_PORT=2123

[]

SBc interface (MME - CBC) Integration phase

Completed

SBCPRI and SBCSEC applications to IPDU-x (KAC)

[]

SCTP multihoming (BIM)

[]

SCTP parameter set (BIE, BIB)

[]

MMEBSC.INI: Delay and list size parameters

[]

SLs interface (MME - E-SMLC) Integration phase

Completed

SLSPRI and SLSSEC applications to IPDU-x (KAC)

[]

SCTP multihoming (BIM)

[]

SCTP parameter set (BIE, BIB)

[]

E-SMLC configuration (BIS)

[]

SLS timers (BIM)

[]

88

Id:0900d805809d5b59 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Flexi NS - MME integration checklist

SLg interface (MME - GMLC) Integration phase

Completed

Destination (OHC) (IPDU-0)

[]

Transfer path and protocol (OHP)

[]

Origin host, origin realm (OHN)

[]

GMLC destination host (OHS)

[]

SCTP parameter set (BIE, BIB)

[]

X1_1 interface (MME - LIC) Integration phase

Completed

LIC_MME application to MCHU(KAC)

[]

X1_1 interface (KAQ)

[]

LIACT enabled (KAQ)

[]

X2 interface (MME - LIB) Integration phase

Completed

LIB application to MMDU-x (KAC)

[]

O&M interface to NetAct Integration phase

Completed

DNS server (QRK)

[]

SSH activated (WOA)

[]

NetAct interface connection verified (QRS)

[]

NE3S and XML enabled (WOC)

[]

FM and PM data transfer verified

[]

Reporting interface to Traffica Traffica interface

Completed

NRT application to MCHU (KAC)

[]

RTT application to MMDU-x (KAC)

[]

Allowed Traffica IP addresses (EJF)

[]

Id:0900d805809d5b59 DN70669711 Issue 7-1

89

Flexi NS - MME integration checklist

Integrating Flexi NS - MME

MME synchronization Integration phase

Completed

Enable SNTP (WOA)

[]

NTP server IP (DCW)

[]

Local communication IP (DCW)

[]

SNTP configuration verified (DCP)

[]

Active Internet connection in OMU verified (QRS)

[]

System parameters Network and network element numbers

Completed

MCC (WVS)

[]

MNC (WVS)

[]

MMEC (WVS)

[]

MMEGI (WVS)

[]

MMERC (WVF)

[]

PLMN parameters and roaming

Completed

Homeplmn (MXA)

[]

HSS destination realm and host(MXN)

[]

AuC destination realm and host (MXN)

[]

Roaming control(MXN)

[]

GUTI reallocation (MXN)

[]

IMEI status check from EIR (MXN)

[]

MNC length (MXN)

[]

IMSI analysis (CFC)

[]

Activation Integration phase

Completed

Configuration files modified and back in directories

[]

Active MCHU restarted (USU)

[]

Verification Integration phase

Completed

Internal routing CPPU - IPDU (QRX)

[]

Internal routing MMDU - IPDU (QRX)

[]

90

Id:0900d805809d5b59 DN70669711 Issue 7-1

Integrating Flexi NS - MME

Flexi NS - MME integration checklist

Integration phase

Completed

HSS connection (QRX)

[]

eNB connection (QRX)

[]

S-GW connection (QRX)

[]

SGSN connection (QRX)

[]

MSC/VLR connection (QRX)

[]

DNS connection (QRX)

[]

LIC connection (QRX)

[]

LIB connection (QRX)

[]

Traffica connection (QRX)

[]

EIR connection (QRX)

[]

AUC connection (QRX)

[]

MME connection (QRX)

[]

MSS connection (QRX)

[]

CBC connection (QRX)

[]

E-SMLC connection (QRX)

[]

GMLC connection (QRX)

[]

HSS connection up (OHI)

[]

SCTP association (MME S1 - eNB) (B6I)

[]

SCTP association (MME - MSC/VLR, MME - HSS; IPDU-0) (QRS)

[]

NetAct connection (OMU) (QRS)

[]

Id:0900d805809d5b59 DN70669711 Issue 7-1

91

04_02_cn31534en30gla0_flexins3.0 Mme Integration.pdf

Overview

More details

Related Documents

Mme

Mme Koino

04_02_cn31534en30gla0_flexins3.0 Mme Integration.pdf

Pass Mme Lefebvre

Sgsn-mme Roadmap.pdf

2009 Mme @free.fr Fax

More Documents from ""

Ned - Flexi Ns - Mme Hardware Description.pdf

04_02_cn31534en30gla0_flexins3.0 Mme Integration.pdf

I_o System Administration - Mss15.pdf

Omgw_hardware Description.pdf

Maintaining And Troubleshooting Hw - Mss15.pdf

05_cn31535en30gla0_mobility And Bearer Management In Flexi Ns 3.0 Mme.pdf