NSS18 Product Definition Document v1.3 - …willowcherry.com/wp-content/uploads/2013/12/NSS18PDD.18.01.pdfNSS18 Product Definition ... Planning Guide. The following table summarizes

Version: v1.3 NSS18 Product Definition

Nortel Networks Confidential i

Wireless Internet Time To Market Product Definition Document (PDD)

NSS18 Voice Core Domain Issue: v1.3

© NORTEL NETWORKS 2005

NORTEL NETWORKS CONFIDENTIAL

The information contained in this document is the property of Nortel Networks and should be considered restricted. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep all information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to all third parties.


Nortel Networks Confidential ii

Revision History

Date of Change

New Version #

Change(s) Made Author of Change

6/11/04 V0.1 Initial draft outline R. Salm

8/24/04 V0.2 Added input from other PLMs R. Salm

9/27/04 V0.3 Updated SOC information B. Smith

10/19/04 V0.4 Updated MSC configurations; included GKS comments

R. Salm

1/17/2005 V1.0 Updated with email comments in preparation for pre-CR review, includes rebranding

R. Salm

2/9/2005 V1.1 Updated with email comments prior to pre-CR review.

R. Salm

3/4/2005 V1.2 Updated with comments from pre-CR review R. Salm

3/30/2005 V1.3 Updated load line-ups R. Salm/B. Smith

Contributors: Sandy Long Thi Nguyen Lou Bono Larry Neyman Susan Martin Jim Willis Maya Roel-Ng Soyeh McCarthy Sajeel Hussain Bruce Mcclean Chin Chiu Barbara Smith Robin Delaney Jason Miller Michaela Scheving Brett Wallis


Nortel Networks Confidential iii

Table of Contents 1.0 INTRODUCTION.................................................................................................................................................... 1

1.1 SCOPE .................................................................................................................................................................... 1 2.0 PRODUCT OVERVIEW ........................................................................................................................................ 2

2.1 NSS18 R4 MSC SERVER AND MEDIA GATEWAY CONTENT OVERVIEW ................................................................ 3 2.1.1 MSC Server support of MGW VSP4 ................................................................................................................. 3 2.1.2 VSP4 Introduction on the MGW....................................................................................................................... 3 2.1.3 MGW Profile Provisioning Extensions............................................................................................................. 3 2.1.4 MSC USP Signaling Evolution ......................................................................................................................... 4 2.1.5 MSC Server IETF SIGTRAN M3UA IP Signaling............................................................................................ 4 2.1.6 MGW Signaling Evolution................................................................................................................................ 4 2.1.7 Introduce NB and BB STP Option in GSM UMTS ........................................................................................... 4 2.1.8 Q.1901 BICC.................................................................................................................................................... 5 2.1.9 R4 BICN UMTS ................................................................................................................................................ 5 2.1.10 R4 UMTS BICN on the MGW ...................................................................................................................... 5 2.1.11 Support of GTT/TTY on MGW ..................................................................................................................... 5 2.1.12 R4 BICN ISUP Trunking Variants............................................................................................................... 5 2.1.13 MGW Tonesets............................................................................................................................................. 5 2.1.14 R4 MSC Server Service Alignment with MGW Evolution............................................................................ 6 2.1.15 Lawful Intercept on the MGW ..................................................................................................................... 6 2.1.16 Conference Calls on the MGW .................................................................................................................... 6 2.1.17 CSD IWF for BICN...................................................................................................................................... 6 2.1.18 Multi-Frequency (MF) Support on MSC ..................................................................................................... 7 2.1.19 NA Multi-Frequency (MF) Support on MGW.............................................................................................. 7 2.1.20 MGW Support for Iden VoCoder Bypass..................................................................................................... 7 2.1.21 MG3.0.2 Support with NSS18 (new MNCL) ................................................................................................ 7

2.2 MG18 MEDIA GATEWAY CONTENT OVERVIEW..................................................................................................... 8 2.2.1 Core Network Voice Compression - Phase 1.................................................................................................... 8 2.2.2 Media Gateway OM Enhancements ................................................................................................................. 8

2.3 NSS18 CORE NETWORK CONTENT OVERVIEW...................................................................................................... 9 2.3.1 (NTLX86VA) VQE and Non VQE Support ....................................................................................................... 9 2.3.2 IN Nature of Address Routing – CAMEL and INAP......................................................................................... 9 2.3.3 Ringback Support for DP12 CAMEL P2 CONNECT Solution......................................................................... 9 2.3.4 MSC/SSP CAMEL Enhancements .................................................................................................................... 9 2.3.5 Backward Call Indicator (BCI) = No Charge Transparency......................................................................... 10 2.3.6 Location Based Services – 3GPP Release 4 Enhancements........................................................................... 10 2.3.7 NSS18 3GPP Circuit Core Change Requests ................................................................................................. 10 2.3.8 MSC Subscriber Category Enhancement ....................................................................................................... 10 2.3.9 Segmentation on MAP level of MO_FSM (Mobile Originated_Forward Short Message)............................. 10 2.3.10 Gs Interface Enhancements for the MSC................................................................................................... 11 2.3.11 AOC (Advice of Charge) Multiple Rate Plan............................................................................................. 11 2.3.12 ETSI PRI Trunk CLI Enhancements .......................................................................................................... 11 2.3.13 Routing Control Enhancements for CSD 64K UDI Data Calls ................................................................. 11 2.3.14 MC09 Billing Enhancement....................................................................................................................... 12 2.3.15 MC09 Billing Module Code Captured on CF Leg for CSD Calls ............................................................. 12 2.3.16 Core and Billing Manager (CBM850)....................................................................................................... 12 2.3.17 Sustaining Electronic FIX (MNCL) Delivery............................................................................................. 12 2.3.18 Port APS Application to Sun Netra 240..................................................................................................... 12 2.3.19 Enhanced Capacity Options for SPM........................................................................................................ 13 2.3.20 MSC Standardized and Proprietary Supercharger.................................................................................... 13 2.3.21 NSS18 XA-Core Memory Increase............................................................................................................. 13 2.3.22 MSC Support for Atlas 9+1 ....................................................................................................................... 13 2.3.23 CEM support for R4 BICN MSC................................................................................................................ 13


Nortel Networks Confidential iv

2.3.24 Core Device Adapter & Plug-in for W-NMS OAM Solution ..................................................................... 13 2.3.25 CEM support for HLR 200......................................................................................................................... 13 2.3.26 CEM Support for MSC with USP Signaling Evolution.............................................................................. 14 2.3.27 Migration to W-NMS ................................................................................................................................. 14

2.4 NSS18 HLR CONTENT OVERVIEW ...................................................................................................................... 15 2.4.1 Mastering of Subscriber Data in Data Server ................................................................................................ 15 2.4.2 Data Server and HLR 200 Provisioning Throughput Increase ...................................................................... 15 2.4.3 HLR Subscriber Information Download......................................................................................................... 15 2.4.4 HLR Bulk Provisioning................................................................................................................................... 15 2.4.5 Improved Handling of SLR Mappings ............................................................................................................ 15 2.4.6 HLR Support for SIGTRAN ............................................................................................................................ 15 2.4.7 HLR Location Services 3GPP Release 4 Compliance.................................................................................... 15 2.4.8 HLR Gc Support ............................................................................................................................................. 15 2.4.9 HLR Standardized Supercharger.................................................................................................................... 16 2.4.10 HLR SMSC-ID in Range Format ............................................................................................................... 16 2.4.11 HLR Immediate Reuse of a Deleted IMSI .................................................................................................. 16 2.4.12 HLR Cross Release Mating........................................................................................................................ 16 2.4.13 HLR Speed Up of Data Transfer during ONP ........................................................................................... 16 2.4.14 HLR Subscriber Category Enhancement ................................................................................................... 16 2.4.15 CAMEL Service Key per Phase Screening ................................................................................................ 16 2.4.16 HLR Call Forward OM Enhancement....................................................................................................... 16

2.5 SOURCING OF FEATURE PATCHES ........................................................................................................................ 17 2.5.1 MSC/HLR Feature Sourcing .......................................................................................................................... 17 2.5.2 MGW Feature Sourcing ................................................................................................................................. 19

2.6 PM FEATURE ID TOACTID MAPPING ................................................................................................................... 20 2.6.1 GSM18 MSC Features.................................................................................................................................... 20 2.6.2 GSM18 HLR Features .................................................................................................................................... 22 2.6.3 GEM18 Features ............................................................................................................................................ 23 2.6.4 MG18 Features............................................................................................................................................... 25

3.0 PRODUCT REQUIREMENTS ............................................................................................................................ 27 3.1 NSS18 CORE NETWORK ...................................................................................................................................... 27

3.1.1 MSC & HLR PCL Configuration.................................................................................................................... 28 3.1.2 NSS18 Software Optionality Controls –SOC.................................................................................................. 30 3.1.3 GSM18 XACore SOC and PARM Configuration Guidelines ......................................................................... 31 3.1.4 Hardware Baselines ....................................................................................................................................... 34 3.1.5 Software Baselines & PM Load Line-Up ....................................................................................................... 41 3.1.6 Supported MSC/HLR Combinations............................................................................................................... 44

3.2 MSC SPECIFIC ATTRIBUTES................................................................................................................................. 45 3.2.1 NSS18 Supported MSC Hardware Configurations......................................................................................... 45 3.2.2 MSC Capacity Expectations ........................................................................................................................... 45 3.2.3 Media Gateway Capacity ............................................................................................................................... 46 3.2.4 Media Gateway Upgrades .............................................................................................................................. 46

3.3 MSC PLATFORMS AND UPGRADES ...................................................................................................................... 48 3.3.1 Supported Upgrades and ONPs ..................................................................................................................... 48

3.4 USP SPECIFIC ATTRIBUTES.................................................................................................................................. 49 3.4.1 USP Use in NSS18 Core Network Configurations ......................................................................................... 50 3.4.2 USP10 Supported Hardware .......................................................................................................................... 51 3.4.3 USP10 Supported Interfaces .......................................................................................................................... 51 3.4.4 USP Supported Configurations ...................................................................................................................... 52 3.4.5 Other Supported USP Components ................................................................................................................ 52 3.4.6 USP Platform (Signaling Server Application) Order Codes .......................................................................... 52 3.4.7 USP SGW Order Codes.................................................................................................................................. 53 3.4.8 USP STP Order Codes ................................................................................................................................... 53 3.4.9 USP UNPM Order Codes............................................................................................................................... 53

3.5 HLR SPECIFIC ATTRIBUTES ................................................................................................................................. 55 3.5.1 NSS18 Supported HLR Hardware Configurations and Upgrades.................................................................. 55


Nortel Networks Confidential v

3.5.2 HLR 200 System Requirements....................................................................................................................... 56 3.5.3 HLR Capacity Targets .................................................................................................................................... 57 3.5.4 Universal Signaling Point for HLR 200 ......................................................................................................... 62 3.5.5 HLR 200 3PC Memory Solution..................................................................................................................... 63 3.5.6 Data Server..................................................................................................................................................... 65 3.5.7 Service Location Register............................................................................................................................... 66 3.5.8 HLR SW Upgrades ......................................................................................................................................... 67

3.6 PASSPORT 8600 SPECIFIC ATTRIBUTES ................................................................................................................ 68 3.6.1 Passport 8600 Hardware Baseline................................................................................................................. 68 3.6.2 Passport 8600 Software Order Code.............................................................................................................. 69 3.6.3 Passport 8600 Engineering Attributes............................................................................................................ 69

3.7 PASSPORT 7000 SPECIFIC ATTRIBUTES ................................................................................................................ 71 3.7.1 Passport 7000 Hardware Baseline................................................................................................................. 71 3.7.2 Passport 7000 Software Order Code.............................................................................................................. 71 3.7.3 Passport 7000 Engineering Attributes............................................................................................................ 71

3.8 GEM SPECIFIC ATTRIBUTES ................................................................................................................................ 73 3.8.1 GEM Order Codes Per Application ............................................................................................................... 73 3.8.2 GEM Billing CD-ROM Order Codes ............................................................................................................. 76 3.8.3 Lawful Intercept interfaces............................................................................................................................. 76 3.8.4 GEM Hardware Baselines.............................................................................................................................. 76 3.8.5 Restrictions/Limitations.................................................................................................................................. 78

3.9 GEM PLATFORMS AND UPGRADES ...................................................................................................................... 78 3.9.1 GEM Upgrade Strategy.................................................................................................................................. 78 3.9.2 GEM Upgrades............................................................................................................................................... 79

3.10 EXTERNAL MUX SUPPORT .................................................................................................................................. 79 4.0 TECHNICAL DOCUMENTATION AND TRAINING..................................................................................... 80

4.1 USER TRAINING ................................................................................................................................................... 80 4.2 USER DOCUMENTATION....................................................................................................................................... 81

5.0 ANNEX A: ACRONYMS...................................................................................................................................... 85 6.0 ANNEX B: GSM18 AND UMTS04 CALL MODELS ........................................................................................ 89


Nortel Networks Confidential page 1

1.0 Introduction 1.1 Scope This document is intended to provide an overview of the NSS18 Voice Core requirements. It identifies new required and optional hardware and software available in NSS18. It also contains information from previous releases, where relevant.

It is not intended that this document be used to size or provision a voice core system. This document is generic and does not consider individual network requirements.

This document assumes that the reader is familiar with Nortel Networks Voice Core architecture and terminology as well as GSM and UMTS industry terminology.

NSS18 is composed of multiple sub-programs that together provide the Network Switching Subsystem requirements. These sub-programs include: MSC, HLR, Media Gateways (MGW) and OA&M components (OMC-S, CEM, CIS, SBA, and HLR-PS). The major deliverables in NSS18 release include R4 Bearer Independent Core Network (BICN) features and Bearer Independent Call Control (BICC) (BICN and BICC for GSM/UMTS ANSI/ETSI), Atlas 9+1 support on MSC (GSM/UMTS), USP for signaling evolution (MSC/HLR), additional CAMEL Ph. 3 functions, Mastering of subscriber data in HLR 200 Data Server, and others.

Key strengths of NSS18 include support of R4 standard interfaces and protocols (e.g. H.248, BICC, and SIGTRAN), higher capacity and memory for both the MSC, and further MSC footprint reduction with the use of MGW (based on Passport 15K hardware – VSP4) and USP (replacing LIU7s for signaling) instead of traditional DMS peripherals.

NSS18 will introduce a new hardware baseline for new MSCs; Core And Billing Manager (CBM850), (NSS18 baseline for new HLRs continue to be SDM-FT). The Core and Billing Manager is the application that consolidates Fault, Configuration, Accounting, Performance, and Security (FCAPS) for wireline and wireless switching networks on a carrier-grade platform. The Core and Billing Manager is a fault tolerant system providing a suite of OAM&P applications through LAN/WAN Ethernet connectivity. SuperNode Data Manager (SDM) applications have been extended to the Core and Billing Manager, which provides scalable billing capacity, improved performance and COT carrier grade SUN/Solaris platform and OS. Additionally, Transition Mode Billing from SDM-FT to CBM850, allows simultaneous billing streams from SDM-FT and CBM850. Once downstream processes are verified, the SDM-FT is decommissioned for permanent cutover to CBM850.

The NSS18 MSC software release supports both GSM and UMTS feature content (a change from the GSM only NSS17 release). The NSS18 MSC software release does not support GSM-R functionality. The following sections give an overview and short description of the NSS18 feature content, but for details the reader is referred to the NSS18 Feature Planning Guide.

The following table summarizes the supported architectures in the NSS18 Core Network:

GSM UMTS

ANSI TDM R4 BICN VoAAL2 ESMR

R99 R4 BICN VoAAL2

ETSI TDM R4 BICN VoAAL2

R99 R4 BICN VoAAL2



2.0 Product Overview The Nortel Networks’ NSS18 Release offers Operators many Advantages and Opportunities:

• Choose from 9 major architecture flavors

• Increase MSC Server Capacity

• Reduce Core Network Footprint

• Realize additional CAPEX and OPEX savings

A general diagram of the NSS18 R4 Network can be viewed below: Note: The Mc Interface between the MGW and the MSC does not traverse the USP.

Nb

Nc

Signaling (not all Signaling I/F are shown)

TDM Bearer

ATM Bearer

ATM Bearer

Signaling (not all Signaling I/F are shown)

TDM Bearer

ATM Bearer

ATM Bearer

General NSS18 R4 Network Diagram

Mc Mc

Nb RNC-2RNC-2

UE-2

Iu

PSTNPSTN

A i/fA i/f

Mc

Nb

McMc

NbRNC-1RNC-1

UE-1

Iu

PSTNPSTN

Mc

Ai/f

ISUP

Nb Nb

Nb

ATM

MGW

MGW

MGW MGW MGW

MGW

Conf/LIMGWConf/LIMGW

MSC-1 ServerMSC-1 Server

MSC-2 ServerMSC-2 Server

Nb

ISUP

GSM BSS

GSM BSS

USPUSP USPUSP



2.1 NSS18 R4 MSC Server and Media Gateway Content Overview New MGW Processor 2.1.1 MSC Server support of MGW VSP4 The MSC Server is enhanced to allow the network to take advantage of the additional processing power available with the new processor on the MGW. The new VSP4 card provides additional MGW processing power and enables the MGW to support services traditionally supported on the MSC server.

2.1.2 VSP4 Introduction on the MGW The VSP4 card provides an evolution path for the VSP2 and VSP2w card, the main voice processing component on the Nortel Networks MGW. This introduction also increases capacity and density of the MGW, while enabling Core Network footprint reduction with less ENET dependency for services. The NSS18 version of the VSP4 card provides one (1) built-in OC3/STM1 fully channelized TDM port, but one 4p OC3 TDM card is still required for AAL1 CES. Enabled by the VSP4 introduction, several voice Quality improvements in the MGW TRAU (Transcoding and Rate Adaptation Unit) are realized with several R4 features described throughout this document.

• Automatic Gain Control (AGC) dynamically adjusts the speech signal volume • Background Noise Reduction (BNR) adaptively filters noisy speech signals that originate in noisy environments • Echo Canceller (ECAN) cancels hybrid echo towards PSTN; supports 128 ms • Mobile Echo Control (MEC) detects and suppresses acoustic echo from the mobile and injects comfort noise in

its place • Background Noise Conditioning (BNC) • Packet Mobile Echo Control (Pkt-MEC) • Packet Automatic Gain Control (Pkt-AGC) • Packet Background Noise Conditioning (Pkt-BNC) • Artifact Concealment for Time Alignment support

2.1.3 MGW Profile Provisioning Extensions Provides a centralized point of reference for the MGW Profile information on a per MSC Server basis benefiting the operator with simplified MGW provisioning resulting in OPEX savings. The MGW Profile is used during call set up to select a particular MGW resource for establishment of bearer.



Signaling Evolution 2.1.4 MSC USP Signaling Evolution This feature will allow GSM/UMTS MSC operators the option of using Nortel Networks Universal Signaling Point (USP) Signaling Gateway (SG) in lieu of the LPP for Access and Network signaling links. The USP serves as the foundation for various next generation signaling and architectural options being planned for both NSS18 and future releases. 2.1.5 MSC Server IETF SIGTRAN M3UA IP Signaling This feature allows GSM UMTS MSC operators, who utilized the USP for signaling, the option of using IP based Signaling, namely 3rd Generation Partnership Project (3GPP) 29.202 required Internet Engineering Task Force (IETF) Signaling Transport (SIGTRAN) Stream Control Transmission Protocol (SCTP)(RFC 2960) and MTP3 User Adaptation Layer (M3UA)(RFC 3332), for some connections to the PSTN, the HLR, and Inter-MSC. 2.1.6 MGW Signaling Evolution This feature provides enhancements to several R4 Media Gateway signaling interfaces, in conjunction with the deployment of the Universal Signaling Platform(USP). These are the A interface, the IuCs RANAP interface, and the ISUP SS7 user payload applications.

• Enable MSC to MGW backhaul of all MTP3 SS7 user payloads (ISUP and A interfaces) over M2UA SIGTRAN embedded in an ATM backbone network.

• Enable MSC to MGW backhaul of all MTP3 and MTP3b SS7 user payloads (ISUP, A, and RANAP) over M2UA SIGTRAN in an IP backbone network.

• Support placement of bSTPs on Nb signaling routes enabling deployment of large numbers of MGWs in a customer’s network without having to provision Nb signaling links in a costly and cumbersome to manage full mesh configuration.

2.1.7 Introduce NB and BB STP Option in GSM UMTS This feature allows for the introduction of a Narrowband (NB) and Broadband (BB) STP on a common platform, the USP. The BB STP option allows wireless operators to avoid implementing a fully meshed network between MGW, i.e. Nb SAAL links. In addition, these are available in stand alone or various configurations on a single platform, including most notably the SG/STP combo. Operators are able to leverage a whole suite of signaling options on a common platform

• NB STP product offerings based on USP platform.

• BB STP to avoid the need to implement a potentially large fully meshed network of Nb Control Links

• Combined SG and STP offering on same USP platform



R4 BICN and BICC 2.1.8 Q.1901 BICC This feature provides a conformant implementation of Capability Set 1 (CS1) Bearer Independent Call Control (BICC) as per ITU-T Q.1901 for the MSC Call Server. BICC is the call control protocol used to manage the call control instance that has been separated from bearer control instance between Call Servers (Nc Interface). BICC enables:

• the reduction of the physical TDM Inter-MSC trunking gateways between MSC nodes • the elimination of the inter-working conversion to TDM between MSCs. (TDM trunks are not required, and as

such there is no Packet to TDM and TDM to Packet conversion) • end to end packet transport. (AAL2 bearer from media gateway to media gateway) • simplified trunk provisioning

2.1.9 R4 BICN UMTS The feature provides UMTS mobility access support in a R4 BICN network for ANSI and ETSI markets. This feature allows existing R99 customers to evolve their R99 UMTS network to a R4 UMTS BICN network. A R4 UMTS BICN Network provides CAPEX and OPEX cost savings for network growth by consolidation of Network resources over an AAL2 network. 2.1.10 R4 UMTS BICN on the MGW Working in conjunction with the R4 BICN UMTS feature on the MSC, the MGW in NSS18 will provide UMTS mobility access support in a R4 BICN network for ANSI and ETSI markets. 2.1.11 Support of GTT/TTY on MGW The FCC requires that a solution be provided to support traditional text telephone standards for UMTS wireless subscribers. This functionality insures that the network can support emergency calls for GTT/TTY users on a 3G network. With the R4 architecture, new functionality is included to support GTT/TTY in the R4 BICN network configuration. This feature provides support for the FCC mandate for U.S. digital wireless service providers for E911 calls on GTT/TTY devices within the UMTS network. It supports hearing or speech impaired wireless subscribers worldwide to transmit speech and text through ordinary speech traffic channels. 2.1.12 R4 BICN ISUP Trunking Variants This activity provides the support for R4 BICN ISUP variants for the following markets: China, Spain, Israel and Romania. This feature allows interconnection to the local network/PSTN via the national ISUP signalling over the Media Gateways. 2.1.13 MGW Tonesets This activity provides the support R4 BICN Tonesets variants for the following markets: China, Spain, Israel and Romania.



Footprint Reduction Continuing with the Core Network footprint reduction initiative, a further reduction in the R4 Core Network footprint is enabled with the MGW supporting services traditionally supported via the ENET, DTCs, etc. 2.1.14 R4 MSC Server Service Alignment with MGW Evolution The evolution of the Media Gateway provides additional capability on the MGW to support services traditionally supported on the MSC Server. The purpose of this feature is to modify to the MSC Server’s role in the support of these services to allow the MGW a more active role in providing service capability for Tones/Announcements, 3/6-way Conference, and LI. In addition, support for Handover is enhanced to conform more closely to the 3GPP R4 standards. With the MGW supporting services traditionally supported via the ENET, DTCs, etc., a further reduction in the R4 Core Network footprint is enabled. This activity is specific to removing the ENET dependency for services, while other activities address signaling, etc. all of which contribute to the overall R4 footprint reduction initiative spanning multiple releases. The reduced footprint provides both an OPEX and CAPEX savings for the Operator. This activity, along with several corresponding FRS documents, identifies the MSC Server and Media Gateway requirements needed to support the addressed services on the MGW. The related NSS18 FRSs are listed below:

• NSS18 22797 ‘GSM/UMTS Lawful Intercept on the MGW’ • NSS18 25084 ‘Conference Calls on the MGW’ • NSS18 25830 ‘MSC Server Support of MGW VSP4’ • NSS18 21740 ‘VSP4 Introduction on the MGW’

2.1.15 Lawful Intercept on the MGW In the Bearer Independent Core Network (BICN) architecture, the CS domain Lawful Intercept has changed significantly. The bearer is separated from the control. The switching component no longer resides in the MSC server as it did in the 2G architecture. All connections between the two ends are now made at the MGW.

As a result of the BICN architecture, the actual bearer interception is now performed by the MGW. The setting of Lawful Intercept targets and the delivery of Lawful Intercept records remain a function of the MSC server. The MGW bearers are managed and manipulated by the MSC server via the Mc interface to provide Lawful Interception. 2.1.16 Conference Calls on the MGW Provides support for voice conference functions on the MGW which replaces the function performed by the R99 hardware devices, i.e. ISM (Integrated Service Module), CTM (Conference Trunk Module), etc

2.1.17 CSD IWF for BICN Feature provides CSD IWF in an R4 BICN configuration via the direct circuit connectivity between the MGW and the GPP IWF. Allows for the reuse of existing IWF HW platform for R4 BICN migration and eliminates the need for legacy TDM equipment thereby reducing system footprint



2.1.18 Multi-Frequency (MF) Support on MSC This feature provides the support of North American Multi-Frequency (NA-MF) Signaling for the R4 BICN solution in ATM bearer networks to support connectivity to the PSAP for E911 calls on the MSC call server. This solution is applicable for both R4 GSM and UMTS systems. Please see 2.1.22 for the support of NA Multi-Frequency (MF) Support on MGW on the MGW. The benefits of this feature are:

• Meets FCC requirements for US UMTS operators • Allows North American carriers to support existing MF capabilities for E911 calls with an R4 BICN network

configuration, without requiring an ENET • OPEX and CAPEX savings due to ENET elimination for E911 MF based calls

2.1.19 NA Multi-Frequency (MF) Support on MGW

This feature provides the North American Multi-Frequency (NA-MF) Signaling for the R4 BICN solution in ATM bearer networks for ANSI GSM and UMTS to support connectivity to the PSAP for E911 calls on the MGW.

NA MF on the MGW provides the support of NA MF for R4 BICN solutions support via MSC Server H.248 control of the Media Gateway. This feature provides connectivity to the North American PSTN and PSAPs via the R4 Media Gateway using NA MF for the R4 BICN solution.

2.1.20 MGW Support for Iden VoCoder Bypass The iDEN network provides Vocoder Bypass mobile-to-mobile telephony to improve audio quality through the elimination of multiple transcoding on a call. Due to this bypass, the audio will be forwarded to destination MGW in a digitally encoded form. To preserve the encoding, this feature enables the MGW to detect vocoder bypass signal during a call, and provide in-path handling of the iDEN encoded bearer. 2.1.21 MG3.0.2 Support with NSS18 (new MNCL) The MG3.02 MNCL provides robustness, survivability, and supportability enhancements to the UMTS R99 Media Gateway platform. MG3.0.2 is not a major release. It is designed to source fixes for issues that are non-patchable. From a customer perspective, this feature enhances the Media Gateway’s handling of overload conditions, enables active calls to survive an MSC warm restart, provides debug level information for Nortel support teams to troubleshoot an SPM crash, and sources many of the fixes identified in the previous releases of 3.0 and 3.0.1.



2.2 MG18 Media Gateway Content Overview Along with the afformentioned features, some additional MGW specific content is introduced in NSS18.

2.2.1 Core Network Voice Compression - Phase 1 This feature provides a solution for compressed voice traffic over the packet backbone for UMTS (and GSM) networks using Out of Band Transcoder Control with BICC, RANAP, H.248 and NbUP/Iu interworking in the spirit of 23.153. A single AMR rate of 12.2kbps shall be supported for mobile and tandem networks over AAL2 packet backbone. The compression on the packet backbone provides bandwidth savings for operators. 2.2.2 Media Gateway OM Enhancements This feature provides the appropriate engineering, performance measurement and fault reporting Operational Measurements (OMs) necessary to support the introduction of the Voice Services Processor v.4 (VSP4) card in this release.



2.3 NSS18 Core Network Content Overview Nortel Networks continues to provide Core Network feature content for existing TDM and UMTS R99 Network Architectures.

In addition, the following features are also applicable to the R4 Architecture, unless stated otherwise.

MSC Server and GEM Features 2.3.1 (NTLX86VA) VQE and Non VQE Support This feature allows GSM UMTS SPM users to utilize the NTLX86VA hardware for two separate integrated echo cancellation applications: Hybrid and Hybrid/Voice Quality Enhancements (VQE).

• Provides PSTN Facing Hybrid Echo Cancellation up to 128ms • Provides Optional Access Facing Voice Quality Enhancement Features

o Acoustic Echo Control o Bi Directional Level Control o Noise Suppression o Conforms to ITU Specifications including G.164,G.165,G.168

2.3.2 IN Nature of Address Routing – CAMEL and INAP This feature expands the existing NOA routing capability on the MSC/SSP to also apply for INAP CS1R and CAMEL protocols, such that NOA routing can be applied to the Called Number received in the following operations:

• INAP: o Connect (NOA of Destination Routing Address), o Establish Temporary Connection o Continue

• CAMEL: o Connect (NOA of Destination Routing Address), o Establish Temporary Connection (NOA of Intelligent Peripheral routing address) o Connect To Resource (NOA of Intelligent Peripheral routing address) o Continue o ContinueWithArguments

For CAMEL, NOA routing is also provided for IN Call Re-origination and Default Call Handling. 2.3.3 Ringback Support for DP12 CAMEL P2 CONNECT Solution Ringback Tone service, also known as Personalized Ringback Tones (PRBT), Customized Ringback Tones or Color Ringback Tones (CRBT), and other brand names, is a service where a Subscriber can choose what tones, announcement or music clip that a calling party hears instead of the regular ringing tone while waiting for the subscriber to answer. Ringback Tone services are typically implemented as either IN services or off-board Service Node solutions. This feature provides the MSC/SSP part of an IN/CAMEL Phase 2 based Ringback Tone service solution, where the SCP indicated to the MSC/SSP in a DP12 Connect message that Ringback tone service shall be invoked for the call. The MSC/SSP sets up a connection to requested Intelligent Peripheral to play the subscribed “tone”, and after an operator configurable delay, in parallel sets up the connection to the terminating party. When terminating party answers the call, it disconnects the connection to the Intelligent Peripheral and bridges the call. For a full Ringback Tone solution, the MSC/SSP functionality must be complemented with the corresponding SCP and Intelligent Peripheral service applications. This feature allows the Operator to offer customized Ringback Tones to their Subscribers as either a standalone Post Paid CAMEL P2 Terminating service or incorporated into a CAMEL P2 PrePaid Terminating service. 2.3.4 MSC/SSP CAMEL Enhancements Nortel Networks continues support for Intelligent Networks with the below CAMEL P2 / P3 and INAP CS1R enhancements.



• Interaction between CAMEL Failure EDPs and MO Call Forward CAMEL IN services, and GSM Optimal Routing at Late Call Forwarding (ORLCF) for both CAMEL P2 / P3

• SCP Communication during SCP Overload alignment with SCCP Q.715 (GPS patch KIC46/KIC48) • Operator option to use Empty-End or Pre-Arranged-End to end a CS1R INAP dialogue (GPS patch BLU22) • Operator option to report NOA of “International” with no international prefix in CF-DP2 Called Party Number

(GPS patch JRG28) • Operator option of IN interaction with Overlapped Outpulsing (STG28/TDS01) • Support of specification change request for CAMEL P3 Initial DPSMS LocationInformationMSC.

Note: Backwards compatibility with pre-NSS18 functionality is not provided. • Support of specification change request for CR 613 on 3GPP 23.078 ‘Handling AC Pending if ETC/CTR fails’.

Note: While this is a CAMEL P4 specification change, this feature also modifies CAMEL P2 and P3 accordingly. Backwards compatibility with Pre-NSS18 functionality is not provided.

2.3.5 Backward Call Indicator (BCI) = No Charge Transparency This feature allows the operator to control the ISUP Backward Call Indicator (BCI) parameter handling with regards to the Charge Indicator for certain call scenarios. The operator control is in particular intended to be used for controlling the Charge Indicator handling for connections to Intelligent Peripherals (IP/IVR) in case of certain CAMEL based IN services such as Prepaid and Ringback Tone Service and for connections to an offboard-IN Service via ANSI ISUP (sourcing of WCD34). 2.3.6 Location Based Services – 3GPP Release 4 Enhancements This feature provides support for LCS capabilities introduced in the Release 4 3GPP standards. New parameters are added and existing parameters are enhanced for both 2G and 3G networks. LCS enhancements include modifications to the PSL and SLR MAP messages, the LRC/LR message and the VLR. Modifications include:

• Support of the positioning method parameter in the PSL and SLR messages • VLR enhancements to support multiple LCS external clients for both call related and call unrelated privacy

classes • Support for the position method in the LR message

2.3.7 NSS18 3GPP Circuit Core Change Requests This feature provides compliancy to 3GPP standards modifications that have been approved during the release development and are considered essential to inherent functionality. It ensures carriers that important changes are incorporated into the release upon approval by the 3GPP standards body. The following Change Requests are addressed by this feature:

• 3GPP 25.413 UTRAN Iu Interface RANAP Signaling o CR 528: SRNS Relocation when the UE is not involved o CR 525: Correction to enable R4 extensions in Location Reporting Procedure

• 3GPP 23.009 Handover Procedures o CR 095: Correct text related to timer expiry for receipt of A-HANDOVER-COMPLETE / Iu-

RELOCATION-COMP • 3GPP 29.002 MAP Specification

o CR 477: Clarifications on Send Identification message • 3GPP 23.078 CAMEL Phase 3, Stage 2 Specification

o R-5. CR 613: on 23.078 – Handling AC Pending if ETC/CTR fails

2.3.8 MSC Subscriber Category Enhancement This feature allows the MSC to support additional subscriber categories (16-255), and translations based on the additional categories and allows the operator to translate Subscription Routing Services (e.g. Hotline routing) in a multi-vendor environment via Calling Party Category routing. 2.3.9 Segmentation on MAP level of MO_FSM (Mobile Originated_Forward Short Message) When a user sends a SMS (Short Message Service) message from his mobile phone and the serving MSC does not have a direct connection to Short Message Service Center, the MSC will convert it into a Mobile Originated Forward Short



Message (MO_FSM) MAP message and transfer the SMS to the Interworking MSC (SMS-IWMSC). On occasion, the total message length on MAP level of the MO_FSM may exceed the maximum allowable MAP message length.

Currently, this has only been seen when the IMSI is included in the MNP message and when GT routing in used, but may also occur for other scenarios where the SMS payload is large and many parameters are included in the MAP message. Because Bluebook SCCP signalling does not provide segmentation on messages, the segmentation must be handled on the application level when Bluebook SCCP messaging is used.

This feature provides segmentation on the MAP level of the MO_FSM according to 3GPP specification 29.002 Section 23.2.1 when the total message length on MAP level of the MO_FSM exceeds the maximum allowable MAP message length (272 bytes in MAPv.3) and Bluebook SCCP is used.

It also provides reassembly of the MO_FSM message according to 3GPP specification 29.002 Section 23.2.1, when a segmented MO_FSM message when a Nortel MSC acting in the role of SMS-IWMSC.

2.3.10 Gs Interface Enhancements for the MSC The Gs interface provides communication protocol between the MSC/VLR and SGSN to allow sharing of location information across GSM/GPRS networks. MSC/VLR support for the BSSAP+ messaging over the Gs interface was implemented in NSS13. Two procedures were listed as exceptions and not included in the initial implementation. Support for these two procedures are added in NSS18 as follows:

• MS information procedure – used by the MSC/VLR to request specific parameters about the MS such as cell ID, location information age or mobile identity.

• MM information procedure – used by the MSC/VLR to inform the mobile device via the Gs interface about such things as the network name and the local time zone of the mobile.

2.3.11 AOC (Advice of Charge) Multiple Rate Plan Subscribers require the flexibility of being able to choose from multiple rate plans when selecting a mobile service provider. It is conceivable that a subscriber may select a rate plan and decide to change to another plan shortly after purchase. In addition, the service provider must be able to change the subscriber’s rate plan in an efficient manner. This feature allows the calling plans to have differentiated charging based on the following variables:

• Time of day • Day of week • Holidays • Location of calling and called party • Free second at beginning of call • Subscriber’s IMSI (one rate plan per customer)

As many different rate plans as possible are supported, with a target of at least 30 different plans per MSC. 2.3.12 ETSI PRI Trunk CLI Enhancements Prior to this feature, the MSC does not provide a default CLI with flexible length on incoming PRI trunks. This feature enhances the current incoming CLI modification capabilities to support a default CLI with flexible length for ETSI ISUP, R1 and MS terminations to comply to current as well as future regulatory and numbering plan requirements. 2.3.13 Routing Control Enhancements for CSD 64K UDI Data Calls This feature provides UMTS Operators with a method to control incoming/outgoing H.324M video calls to/from the Point of Interconnect (POI).This functionality is implemented via a mechanism to allow differentiation in the routing of 3G-H324M 64K UDI video telephony calls at interconnection sites. For outgoing ETSI ISUP variants, the trunk can be chosen depending if the call is a 64K UDI based video call. For incoming calls the operator is able to permit or bar a video call.



Mobile Operators will be able to distinguish between their Interconnection partners to permit or bar 3G-H324M 64K UDI Video Calls to be setup between Operators. The Interconnection partners are the PSTN and National Roaming partners. 2.3.14 MC09 Billing Enhancement This feature allows differentiation of data calls on an interconnection basis by appending “Data Service Information” Module Code MC09 to the GSM Call Detailed Records for incoming and outgoing trunks. This enables different price planning for video telephony calls and other CSD calls.

2.3.15 MC09 Billing Module Code Captured on CF Leg for CSD Calls This feature appends the Data Services information Module (MC09) to the Call Forward leg records for all Circuit Switched Data/Service call types.

• Provides the operator with the ability to identity a CSD call on a forward leg.

• For H.324M Video Telephony calls, MC09 on the CF leg allows differentiation between base 64K CSD calls and H.324M Video Telephony calls to allow accurate and flexible billing

2.3.16 Core and Billing Manager (CBM850) Core and Billing Manager, Model 850, is the latest commercial off the shelf platform, using two Sun Netra 240 servers. The current SDM-FT applications have been ported to the new state of the art platform, for improved performance and reliability. Additionally, Transition Mode Billing from SDM-FT to CBM850, allows simultaneous billing streams from SDM-FT and CBM850. Once downstream processes are verified, the SDM-FT is decommissioned for permanent cutover to CBM850. 2.3.17 Sustaining Electronic FIX (MNCL) Delivery This feature provides sustaining support for electronic fix delivery of SDM MNCLs (patch bundles) enabled in NSS17 release. EFD provides faster fix delivery with improved quality to a customer furnished drop box (server). Once electronic load (NCL) delivery is introduced, fixed media will be offered for an annual fee.

2.3.18 Port APS Application to Sun Netra 240 Beginning with MG18, the APS (Audio Provisioning Server) application will be supported on the Sun Microsystems Netra 240 server. This server will be the only server shipped with the APS application. The APS Server is an optional device deployed on a one or two per customer network basis. The APS application provides the capability for creating, distributing and backup file storage for the digital announcements files resident on the VSP card. The APS application receives standard or custom digital announcement file input and creates the .aud, .idx., and .cat files necessary for storage and playing by the MGW. In the event that the MGW announcement files are corrupted beyond internally restorable status, the operator is able to access the ASP server via their CO LAN and direct the ASP server to FTP a new file set to that specifically affected MGW. The current Sun Microsystems T1400 server has been MD’d and will no longer be shipped. The few T1400 based APS applications currently in service for MG17 will continue to be supported per contract agreement.



MSC Capacity The below items describe the capacity related features for NSS18. For NSS18 MSC capacity estimates, please refer to section 3.2.2. 2.3.19 Enhanced Capacity Options for SPM Supports 2X/3X NTLX82AA(CEM) capacity options on SPM for operators using the NTXL82BA(CEM). With this functionality the SPM will be able to provide greater capacity via the below SOCs.

o Enhanced SOC SPMS0020 o Premium SOC SPMS0028

2.3.20 MSC Standardized and Proprietary Supercharger Feature allows Nortel Networks MSCs to support Supercharger in a network with HLRs that support either the standardized or proprietary Supercharger function. Use of this feature reduces VLR-HLR messaging in networks with highly mobile users and improves capacity of the MSC.

• Support VLR Standardized Supercharger per 3GPP Spec. 23.116 • MSCs will continue to support proprietary SC in NSS18

2.3.21 NSS18 XA-Core Memory Increase This will increase the available memory in the MSC for VLR subscribers and in the HLR for storing subscriber data. The increased memory will be available on all XA-Core configurations for both the MSC and HLR (HLR 200 only) with 10 SM cards (increase is not applicable for any other SM card configurations).

• Memory increase of 192MB through configuration change from 1728MB to 1920MB with 10 shared memory cards.

• Automatically changes 10 SM configuration from 2N+1 to 2N when MSC is upgraded to NSS18.

2.3.22 MSC Support for Atlas 9+1 Increases the MSC capacity by supporting Atlas 9+1 PE configuration (capacity increases are quantified in Section 3.2.2). OAM Features 2.3.23 CEM support for R4 BICN MSC Supports new NE – USP-based SGW, while continuing to support R4 complex’s existing NE & NE’s EMS. Stay in sync w/ latest software release of NE & NE’s EMS – Call Server, MGW, APS, PP8600, MDM, MDP. CEM manages complex directly via CEM Server, or as part of larger W-NMS OAM solution. 2.3.24 Core Device Adapter & Plug-in for W-NMS OAM Solution Faults for voice core nodes, and all MDM-managed nodes are integrated into NSP via the Core DA, built using the latest available Adapter Development Kit (ADK) from Preside. The CEM client is launched from the NSP desktop as a GUI Development Kit (GDK) plug-in. It has the same look & feel as a standalone OMC-S or standalone CEM would have. The CEM client provides subcomponent display, alarm monitoring, and (for MSC and HLR only) OM thresholding/queries every feature developed on CEM is applicable/useable in W-NMS solution 2.3.25 CEM support for HLR 200 The following features are included in the CEM support of the HLR 200 platform:

• Support new NE – Centillion 1200 ATM switch; Sun RAID storage • Continue supporting HLR 200 complex’s existing NE & NE’s EMS; stay in sync w/ their latest software release

– HLR, USP, SLR, DS, SAM21, STORM, PP8600, MDM, SMC • Support more provisioning code ported from SDM/FT to DS • Enable in-context launch of USP GUI • Integrate CEM’s login w/ HLR 200 NEs’ login



2.3.26 CEM Support for MSC with USP Signaling Evolution The following features are included in CEM support of the MSC with USP:

• Represent new SGW as either a Call Server sub-component or a separate Node. • Collect and display fault, performance and configuration information for SGW, with same capabilities and look-

and-feel as for other nodes • Launch USP EM for further management of SGW • NSS18 last release to support Standalone CEM server and OMS-S apps since both will be MDed in NSS19 and

merged into W-NMS 2.3.27 Migration to W-NMS

W-NMS (Wireless Network Management System) becomes EMS Baseline in NSS19 /OAM05 per corporate product roadmap. NSS18 is the last supported release for Standalone CEM and OMC-S and MDed in NSS19 (NOI/MD issued December 2003). All CEM code already resides in W-NMS, so there is no loss of existing functionality. Migrate to W-NMS (formerly PWI) during NSS18.



2.4 NSS18 HLR Content Overview The following HLR features are applicable to both HLR 100 and HLR 200 systems unless stated otherwise. For additional information please refer to the NSS18 Feature Planning Guide.

2.4.1 Mastering of Subscriber Data in Data Server The Data Server functionality is enhanced to maintain the master copy of the subscription data for each subscriber served by an HLR 200 node provisioned via the Data Server. This feature is only applicable to HLR 200 systems using Data Server. 2.4.2 Data Server and HLR 200 Provisioning Throughput Increase This feature increases the Data Server centralized provisioning throughput from 50,000 to 100,000 orders per hour and increases the provisioning throughput of each HLR 200 node from 15,000 to 25,000 orders per hour based on the Nortel standard provisioning services profile. This feature is only applicable to HLR 200 systems using Data Server. 2.4.3 HLR Subscriber Information Download This feature provides the capability on the Data Server to support SQL queries of the subscription data stored in the Data Server database. Operators can use this capability to correlate subscriber data with downstream billing records and to analyze feature penetration. This feature is only applicable to HLR 200 systems using Data Server. 2.4.4 HLR Bulk Provisioning This feature provides the capability of making subscriber provisioning changes on a mass scale by denoting the change to be made and the range of affected subscribers on the Data Server. This feature is only applicable to HLR 200 systems using Data Server. 2.4.5 Improved Handling of SLR Mappings The handling of SLR mappings in the Data Server is modified in order to use the existing SLR memory in a more efficient way. The only mappings that will be stored in the SLR are:

• The IMSI and MSISDN mappings of active subscribers • The IMSI mappings of pre-provisioned subscribers. A pre-provisioned subscriber is a subscriber with IMSI

status set to new or a subscriber with IMSI status set to active who has never registered in the network. This feature is only applicable to HLR 200 systems using Data Server and SLR. 2.4.6 HLR Support for SIGTRAN This feature provides the capability for the HLR 200 nodes to communicate MAP over IP using the 3GPP SIGTRAN (RFC M3UA/ RFC SCTP) 29.202 specification. This capability will only exist on the USP which is the signaling component of the HLR 200 node. This feature is only applicable to HLR 200 nodes. 2.4.7 HLR Location Services 3GPP Release 4 Compliance This feature enhances the Location Services (LCS) capabilities of the HLR to comply with the R4 LCS specifications. Key items are:

• Support LCS functionality for the PS domain. • Support up to 40 external LCS clients for the subscriber’s Call/Session related LCS Privacy Class (PC) and up

to 40 external LCS clients for the subscriber’s Call/Session unrelated LCS PC.

2.4.8 HLR Gc Support This feature implements HLR support for the following MAP messages used in the Gc interface to support push services that require support for Network initiated PDP context activation capabilities:

• Send Routing Information for GPRS



• Failure Report • Note MS Present for GPRS

2.4.9 HLR Standardized Supercharger This feature implements 3GPP Standardized Supercharger functionality on the HLR for CS and PS domain. Both versions of Supercharger (proprietary and standard) will be supported concurrently on the HLR to support backward compatibility with previous MSC SW releases. 2.4.10 HLR SMSC-ID in Range Format This feature allows the operator to specify the supported SMSC addresses in the HLR using address ranges instead of individual addresses. 2.4.11 HLR Immediate Reuse of a Deleted IMSI This feature allows reuse of an IMSI immediately after its deletion if the following conditions are meet:

• There are no pending Cancel Location transactions for the deleted IMSI. • In the case of a mated pair HLR, the synchronization message caused as a result of the IMSI deletion has been

completed successfully. 2.4.12 HLR Cross Release Mating The feature allows for an HLR in release ‘N’ to be mated with an HLR that is in release ‘N+1’. 2.4.13 HLR Speed Up of Data Transfer during ONP The amount of time needed to perform an Over-Night upgrade Process (ONP) software upgrade is increasing as a result of the growth in per subscriber data and an increase in the number of subscribers served by a single HLR node. In order to reduce the ONP data transfer time, the rate at which subscriber data tables are transferred during TABXFR, PreSWACT, and Limited PreSWACT from the active processor to the mate processor is increased using the XA-Core hardware window mechanism during the transfer process. 2.4.14 HLR Subscriber Category Enhancement This feature allows the HLR to support additional subscriber categories to facilitate support of Class of Service routing in a multi-vendor environment. 2.4.15 CAMEL Service Key per Phase Screening This feature allows the operator to screen individual O-CSI Service Keys for a specific CAMEL phase on a per node basis. The screening of O-CSI Service Keys is applied to the MAP message Insert Subscriber Data. 2.4.16 HLR Call Forward OM Enhancement This feature keeps track of the number of subscribers with Supplementary Services CFU, CFB, CFNRC, and CFNRY activated to Forwarded-To-Numbers matching customer pre-defined leading-digits.



2.5 Sourcing of Feature Patches As customers deploy GSM NSS software in different markets and network topologies, custom features are occasionally needed in a fast timeframe. These feature patches are then sourced into the regular software release and available for other customers. Below is a table of the feature patches that will be sourced in NSS18. The first column lists the design activity identifier. The second column lists the Portfolio Manager identifier. The third column lists the patch identifiers of the feature in releases before NSS18. The last column lists the feature name.

2.5.1 MSC/HLR Feature Sourcing

ACTID PMID Patch IDs Feature Name

A00004164 25192 WCD40 Advice of Charge Multiple Rate Plans Enhancements

A00003930 24363 WSF22/WSF23/WSF24/WSF25 Trinode HLR Subscriber Limit

A00004171 24364 WSF22/WSF23/WSF24/WSF25 Trinode VLR Subscriber Limit

A00005590 24689 WCD34

Backward Call Indicator (BCI) = 'No Charge'

Transparency Solution

A00004614 24466 WSF20/WSF28/WSF45

Ringback Support for DP12 CAMEL P2 CONNECT

Solution

A00004176 24506 WSF18 Customization of CAMEL

P2 IN Mechanisms for China region

A00004502 26139 WSF17/JOC71/BRS10/BRS14 Disable EC Bit in SS7 Messages

A00004165 25187 WCD46/WCD56/WCP20 Per Trunk Group LNP Reset

A00004166 23657 WCD47 UK Last Diverting Line Identity (LDLI) Support

A00003924 17592 WSF21 Nortel HLR Support of 3GPP Supercharger

A00004306 22936 WCD50/WCP14/WCP15/WCP16/WCP18

DMS-GSM HLR Cross -Release Mating

A00003928 25171 WCD54/WCD61/WCP19 HLR Speed Up Data Transfer during ONP

A00004067 22662 WGF01/WPP03 HLR SMSC-ID in Range Format

A00004167 25200 WCD52/WMP01 MSC Support for TDOA Positioning using INAP

A00004068 25247 WGF02 HLR Immediate re-add of a deleted IMSI

A00004168 24946 WCD55 UK CLI Presentation Support

A00004169 25834 WSF11

Call Forward Records Enhancement for Location

Information (corrective content)

A00004170 25285 WCD53 ETSI PRI Trunk CLI Enhancements

A00004175 25449 WGF03/WGF05 HLR Call Forward OM Enhancement



A00004583 25903 WCD66 GSM/UMTS SPM STM-1

Perfmon Tool Enh

A00004360 25671 WCD51 RESTMNC Message

Suppression with Emergency Type II Calls

A00004439 25355 WCD64

UDTS msg. No Translation for this Address route to

XLAENTRY 7

A00004440 24947 WCD69

UK ISUP CPC Enhancements for Emergency Calls

A00004127 25986 WCD62/WCD63 DBT PRI & ISUP eMLPP

(Preemption) Across Multiple Trunks

A00004674 26037

WCD68 QGSMVLR tool Support for

TMSI based query

A00004172 25734 WSF29 Segmentation at MAP Level of MO-FSM

A00004361 25736 WCD60 Release Congestion Cause

Parameter A00004698 25976 WSF32 Multiple MSRN Pool

A00004582 26024 WSF30/WSF31/QND32 NTLX86VA VQE and Non-

VQE Support

A00004765 26107 WCD18 E911 Changes for ESMR Phase 1 A-Interface

A00004701 26056 WCD70/WCD78 EIR: IMSI with IMEI A00004613 26031 RXT44 AOCC over PIE A00004900 26336 FFD33/WCD67 Israeli ISUP

A00004244, A00004245, A00004250, A00004252

GSM:26142 GEM:25399 WSF41

GSM/GEM: Mass Query/Update of HLR

Subscriber Tables

A00003639 25721 WCD80 HLR SMS Over GPRS Deactivation Mechanism

A00007441 26965 WSF42

MC09 Billing Module Captured on CF leg for CSD

Calls A00005120, A00007470 26428 WCD76

MSC Paging Enhancements - Expanded Retry Timer

A00007507 26596 FFD47/WCD74 OICK and ST (Subscription

Type) Parameter Routing A00005353, A00007479

26666 WSF36 Calling Party Address in MO CDR

A00007490 26755 WCD81 144 Service (Directory

Assistance Service)

A00007508 26943 WCD73 Allow multiple entries with

same MSISDN in the VLR

A00007478 27019 WCD86 Handling of LCS data in ISD

MAP message A00007373, A00007509, A00007985

27531 WCD91/WCC12 Israeli National Tonesets

A00007929 27781 4 Patches ETSI ISUP for Partner



A00007059 26752 WCD91/WCC12 MO SMS Diversion based

on CAMEL Service Key

A00007903 27490 WCD93 Internal counter for Inter-

Node Call Forward Loops 2.5.2 MGW Feature Sourcing Not applicable



2.6 PM Feature ID toActid Mapping The following table provides a cross reference between the PM identifiers, the feature title, and the ActIDs associated with the feature. The previous section showed features that were delivered to one or more customers using the Fast Feature process and then folded into the NSS18 software stream. This section provides a list of features that are initially offered in NSS18.

2.6.1 GSM18 MSC Features FRS

Feature ID

FRS Feature Title ActIDs

18830 Standardized Supercharger A00004193 23117 LACSAC Table Enhancements A00004856

23226 Gs Interface Enhancements for the DMS-MSC A00004183

23985 Location Based Services - R4 Enhancements A00004084

24051 Datafillable grant tone length and detection time GSMR A00004233

24723 MSC Support for GTT/TTY on UMTS A00004378 24800 R4 3GPP Circuit Core Change Requests A00004379

24945

UK ISUP Enhancement v2 - INR/INF enh to support Natl info indicators, Suspend/Resume to RANAP/DTAP Notify mapping; UK ISUP Enhancement v2 - Support of NOA setting using SETCDN; UK ISUP Enhancement v2 - Support of PCLI and Default CLI; UK ISUP Enhancement A00004083

26661 NSS18 Atlas Capacity Enhancement A00004253 25050 NSS18 Memory Increase A00004929

25106 Sustain CIS functionality in GMSC and VMSC A00004274

25126

R4 BICN ISUP Trunking variants (The focus of this feature is to provide support for BICN ISUP for the ITU-T markets (including the the NT variant). A00004140

25142 R4 BICN UMTS North American & World Trade

A00004142, A00004143, A00004144 A00004145, A00004194

25149 BICN Support on ESMR Interface (Test & Documentation only) A00004072

25196 Sustaining Periphonis IP A00004232

25278 MSC/SSP CAMEL Enhancements A00005075

A00004184, A0004186, A0004187, A0004188 25423 NTEX22CA Support for All ASU in LPP Test Only

25425 NSS18 MSC Supported Configurations and Capacity A00004930

25443 Parmfind Command A00004419

25572 Enhanced Capacity Option for NTLX82BA (SPM) Test Only

25622 Sustaining R4 BICN/BICC field robustness A00004309



25650 R4 MSC Services Decoupling over Mc"

A00004370, A00004371, A00004372, A00004373, A00004374, A00005270,

A00005271, A00005272 25693 R4 NSS16 to R4 NSS18 support Not Required 26749

in MSC-MG list Core Network Voice Compression A00004408 25775 MC09 Billing Enhancement Kapsch A00004147

25789 Routing Control Enhancements for 64K CSD UDI Data Calls Kapsch A00004148

25809 Wireless Priority Service - T7 timer & WNOTRUNK A00004138

25812 MSC-USP Signaling Evolution

A00004105, A0004158,A00004159, A00004161, A00004182

A00005092 25907 MSC Subscriber Category Enhancement A00006555

26006 MSC logging enh to display trouble orig info A00004370, A00004371, A00004372, A00004373, A00004375, A00004417

26016

ITU-T Q1902 BICC (The focus of this feature is to provide support of ITU-T Q.1902 BICC. I've attached the BICC compliance document to the PMID also - which can be used for initial assessment.) A00004407

26017

BICN MTUP (The focus of this feature is to provide support of MTUP in a BICN R4 environment.) A00008344

26035 NSS18 Quality/Robustness A00004370, A00004371, A00004372,

A00004373, A00004376

26042 NSS17.1 ANSI BICC - sourcing to NSS18 A00004242 26358 MGW Profile Provisioning Extensions A00004355 17573 IN NOA Routing A00004192 25830 MSC Support of MG VSP4 A00004380 26049 NSS18 Solution FRS Not Required 25812 RANAP Decoding in the MSC A00004144, A00004143 23891 SPM WPS FOC C7TIMER Compliancy A00001533

26041 MSC IETF Sigtran IP Signaling A00007993, A00008001 26064 Introduce NB,BB,IP STP in GSM UMTS Not Required



2.6.2 GSM18 HLR Features

FRS Feature

ID FRS Feature Title Act IDs

17586 HLR Location Services R4 compliance A00003926: HLR Location Services R4 compliance

22844 HLR Gc support A00003927: HLR Gc Support

23679 CAMEL Service Key per Phase Screening A00003929: HLR CAMEL Service Key per Phase Screening

25237 HLR Subscriber Category Enhancement A00003945: HLR Subscriber Category Enhancements

25429

NSS18 HLR supported configurations

A00003946: NSS18 HLR Mated Pair A00004277: Sustaining 3PC Memory SolutionA00004296: NSS18 HLR ONP A00005290: NSS18 HLR Performance A00006123: NSS18 Software Upgrade Tracking A00006164: NSS18 Remote Software Upgrade Control

25433 HLR Support for SIGTRAN A00005738: HLR200 SIGTRAN Engineering

25723 Custom T-Mo algorithm A00003534: HLR Custom T-Mobile Algorithm

26043 HLR pre-paging support for CMCC TICR improvement A00004778: HLR Pre-Paging Support



2.6.3 GEM18 Features FRS

Feature ID

FRS Feature Title ActIDs

24988 Core and Billing Manager A00006025: Transition Mode Billing from SDM to CBM

25004 Sustain CIS: CNR format, DI, INI 1&2 on SDM and nSDM A00006026: SDM Sustaining

25108 Sustaining OMC-S client & server A00006087: CEM Server Sustaining

25109 Sustaining CEM client & server A00006087: CEM Server Sustaining

25110 Sustaining OMC-S/CEM Client Machine I&C None

25111 Sustaining CEM Server I&C A00006095: CEM Server I&C

25112 Sustaining Core DA & Plug-in for PWI Solution None

25114 CEM support for R4 BICN MSC None

25115 CEM support for HLR 200 A00004272: HLR OAM Development for GEM18 A00005964: GEM18 CBM port/ I&C

25121 Sustaining HLR-PS for service syncronization w/ NSS18 HLR A00004243: HLR-PS/HLR-PM Service Sync for NSS18

25122

Sustaining fast provisioning version of HLR-PS for service syncronization w/ NSS18 uHLR A00004243: HLR-PS/HLR-PM Service Sync for NSS1

25123 Sustaining HLR-PS I&C A00004376: GEM18 HLR-PS & PM Installation and Commissioning

25236 HLR Subscriber Information Download

A00004245: Oracle Development for the GEM18 Data Server

25399 Mastering of subscriber data in Data Server

A00004244: Data Server Base Development for GEM18 A00004245: Oracle Development for the GEM18 Data Server A00004250: Receive Network Triggered Data Changes to the Data Server A00004252: Caching System Tables on the Data Server A00004516: HLR 200 Data Server Deployment A00004517: HLR 200 DS Disaster Handling A00004518: Data Server Application Mgmt Framework A00004520: Mastering of Subscriber Data on the HLR 200 Data Server A00004522: Data Server Audit of Subscriber Data A00004523: Bulk Subscriber Update via the Data Server A00005369: HLR 200 Data Server Upgrade Strategy and Veritas Configuration

25497

Standalone OMC-S and Standalone CEM Capacity Requirements in GEM18 None

25538 Standalone OMC-S and standalone CEM configuration in GEM1 None

25607 NSS18 Data Server Sustaining A00004272: HLR OAM Development for GEM18 A00005370: HLR 200 Data Server I&C



25611 Data Server and HLR 200 provisioning throughput increase

A00004245: Oracle Development for the GEM18 Data Server A00004520: Mastering of Subscriber Data on the HLR 200 Data Server

25613 Improved handling of SLR mappings

A00004250: Receive Network Triggered Data Changes to the Data Server

26124 GEM18 Electronic MNCL and NCL Delivery A00006026: Sustaining SDM

26145 CEM support for MSC with USP Signaling Evolution A00006098: CEM Support for USP



2.6.4 MG18 Features

FRS Feature

ID FRS Feature Title ActIDs

21740 VSP4 Introduction on the MGW

A00004652: UMTS R4 Media Gateway FN A00004658: Port CallTrace tool to VSP4 SPM A00004785: VSP4 Trace to Disk Port A00004863: Port of Blackbox to VSP4 A00006466: Port BICC to VSP4-PDC A00006684: VSP4 Introduction on the MGW A00006918: VSP4 Intro Phase 1 A00006967: Port BICC to VSP4-PDC OA&M A00006968: Port BICC to VSP4-SPM A00006969: Port BICC to VSP4-SSM A00006984: MGW DSP Load Control V3 A00006985: MGW DSP Load A00007046: VSP4 Intro Phase 2

21742 MGW UMTS 1900 Enhancements A00006917: MGW UMTS 1900 Enhancements A00006985: MGW DSP Load

22797 Lawful Intercept on the MGW

A00000617: R4 BICN Call P (PE + BER) A00000618: R4 BICN Umbrella FN A00000834: MGW DSP Support of Multi-Party A00004645: MG Support of Legal Intercept A00004652: UMTS R4 Media Gateway FN A00004791: MGW Conferencing DSP HLD

25084 Conference Call Support on the MGW A00000834: MGW DSP Support of Multi-Party A00006914: Conferencing

25149 BICN support for ESMR interface A00004072: R4 BICN Support for ESMR 25431 MGW OM Enhancements A00006972: MGW Counter Enhancements

25589 CSD IWF for BICN

A00004371: R4 MSC: CSD Service Alignment with MGW A00004652: UMTS R4 Media Gateway FN A00005102: GSM18-FG04 Open Mc, BICN Robustness A00006751: MGW - CSD IWF for BICN A00006985: MGW DSP Load

25631 MGW Signaling Evolution

A00004623: MG18 MTP2 WP A00006457: SIGTRAN A00006458: MTP3 A00007015: M3UA

25633 R4 UMTS BICN on the MGW

A00004652: UMTS R4 Media Gateway FN A00004668: MG18.0 Stage 2 Integration A00006915: Iu Nb VoAtm A00006985: MGW DSP Load A00007047: MG18.0 Stage 3 Integration A00007198: MG18.0 Stage 1 Integration A00007199: MG18.0 Stage 4 Integration

25634 MG18 Configuration and Engineering A00006724: 2pVs (VSP4) Thermal Management A00006971: MGW Installation & Upgrade



25650

R4 MSC Server Service Alignment with MGW Evolution

A00000834: MGW DSP Support of Multi-Party A00004310: R4 MSC: Service Alignment with MGW- HLD A00004370: R4 MSC: LI Service Alignment with MGW A00004372: R4 MSC: CONF Service Alignment with MGWA00004373: R4 MSC: HO Service Alignment with MGW A00004374: R4 MSC: RANN and Tones Service Alignment with MGW A00005102: GSM18-FG04 Open Mc, BICN Robustness A00005270: CHTRIAL: HPBC restructuring A00005271: CHTRIAL: Transparent CSD Service A00005272: CHTRIAL: CONF Service A00005740: CHTRIAL: ANN / Tones Alignment with MGWA00006961: Handover Enhancements A00006985: MGW DSP Load A00007012: MC Interworking

25899 MG18 Design For Serviceability (DFS)

A00006920: Port Null Pointer Detection tool to VSP4 SPM & SSM A00006921: Tracing to Disk Profiling

26017 R4 BICN MTUP No ActID listed

26121 MG Tonesets A00004791: MGW Conferencing DSP HLD A00006919: MGW Tonesets

26230 MG support for Iden Vocoder Bypass A00006962: Iden Vocoder Bypass Support A00006985: MGW DSP Load

26273 China Trial Requirements

A00004627: China Trial - MGW Support of SIGTRAN A00004667: China Trial - MG DSP Load A00005834: China Trial - MGW (Conf) PE A00005835: China Trial - MGW (Conf) CM work package A00005889: China Trial - MGW (Conf) PDC work package A00006746: MG China Trials - Sanity

26749 Core Network Voice Compression

A00004408: Compression on BICN A00005753: CHTRIAL: Backbone Voice Compression A00006916: Backbone Compression A00006985: MGW DSP Load

27154 NA Multi-Frequency (MF) Support on MGW

A00006732: MF Support on MGW A00006734: MF Support on MGW - HLD

27501 MG3.02 MNCL No ActID listed



3.0 Product Requirements Each NSS release has requirements to support the services and functionality offered. The requirements may include hardware upgrades, inter-nodal SW dependencies, activation of optional SW, particular HW configurations, etc. This section describes the dependencies and requirements to support NSS18 functionality.

3.1 NSS18 Core Network The NSS18 core network consists of the MSC, HLR and MGW. The NSS18 software is based on the DMS CSP20 (BASE21, TL20, SHR20), XPM20, CBM18, USP10.0, SN07, Passport v3.7, SP21 (NA), SP17.2 (INTL) platform software. The MG18 SW is based on PCR5.2. As dictated by the CSP, customers must be running on NSS16 or NSS17 before they can upgrade to NSS18.

Since there is no GSM-R support on the MSC in NSS18, customers on GSM-R NSS17 will not upgrade to NSS18. Customers on NSS16/UMTS03 for the MSC, must upgrade to NSS18/UMTS04.



3.1.1 MSC & HLR PCL Configuration NSS18 PCL configuration tables:

Rel Solution

Existing PCL/NCL Ordercode PCL Name PCA DRU's Description

NSS18 MSC GMSO0180 GMSO180

DMSBASE21, DMSTL20, DMSSHR20, GSMBASE18, MSC18 NSS18 MSC

Supported XA-Core Configs: Rhino 3+1, Atlas 2+1, 3+1, 5+1, 7+1, 9+1; For GSM and UMTS markets

USP 10.0 MSC HLR-200 USP00100 USP0100 USP 10.0 NCL

The GSM-R functionality is supported in all HLR loads. However, Nortel can only provide a load that supports GSM MoU and/or 3GPP algorithms to a GSM-R customer if he is authorized to use these algorithms (i.e. customer is a GSM

MoU/3GPP signatory).

HLR-100 GHXO0180 GHXO180

DMSBASE21, DMSTL20, DMSSHR20, GSMBASE18, HLR18

NSS18 HLR 100 (XOR, IDEA)

Supported XA-Core Configs: Rhino 3+1, Atlas 3+1, 7+1; For customers who are not IDEN, GSM MoU, or 3GPP signatories

HLR-100 GHEC0180 GHEC180


NSS18 HLR 100 (XOR, IDEA, Cave 38)

Supported XA-Core Configs: Rhino 3+1, Atlas 3+1, 7+1; For HLR 100 nodes in IDEN (ESMR) markets; Motorola, Nextel

HLR-100 GHMO0180 GHMO180


NSS18 HLR 100 (XOR, IDEA, GSM MoU)

Supported XA-Core Configs: Rhino 3+1, Atlas 3+1, 7+1; For GSM MoU signatories who are not 3GPP signatories

HLR-100 GHUX0180 GHUX180


NSS18 HLR 100 (XOR, IDEA, 3GPP)

Supported XA-Core Configs: Rhino 3+1, Atlas 3+1, 7+1; For 3GPP signatories who are not GSM MoU signatories

HLR-100 GHUM0180 GHUM180


NSS18 HLR 100 (XOR, IDEA, GSM MoU, 3GPP)

Supported XA-Core Configs: Rhino 3+1, Atlas 3+1, 7+1; For GSM MoU signatories who are also 3GPP signatories This is the only HLR 100 load that supports combined GSM/UMTS functionality

HLR-200 GHVC0180 GHVC180


NSS18 HLR 200 (XOR, IDEA, Cave 38)

Supported XA-Core Configs: Rhino 3+1, Atlas 3+1, 7+1; For HLR 200 nodes in IDEN (ESMR) markets; Motorola, Nextel

HLR-200 GHVU0180 GHVU180


NSS18 HLR 200 (XOR, IDEA, GSM MoU, 3GPP)

Supported XA-Core Configs: Rhino 3+1, Atlas 3+1, 7+1; For all HLR 200 nodes except IDEN markets This is the only HLR 200 load that supports combined GSM/UMTS functionality

HLR-200 GHVM0180 GHVM180


NSS18 HLR 200 Memory Extension

Supported XA-Core Configs: Compact SOS; For HLR 200 3PC memory solution. This SW load is only applicable to HLR 200 nodes with PCL GHVC0180 or GHVU0180 which are deploying the optional HLR 200 3PC memory solution.

MSC

HLR

Notes

NSS18

Note: HLR 200 3PC memory solution is only supported on HLR 200 Atlas 3+1 or Atlas 7+1configurations.



Rel Solution

Existing PCL/NCL Ordercode PCL Name PCA DRU's Description

MSC, HLR-100 GMHX0180 GMHX180

DMSBASE21, DMSTL20, DMSSHR20, GSMBASE18, MSC18, HLR18, MSCHLR18

NSS18 MSC/HLR (XOR, IDEA)

Supported XA-Core Configs: Atlas 2+1; For customers who are not IDEN, GSM MoU, or 3GPP signatories

MSC, HLR-100 GMHE0180 GMHE180


NSS18 MSC/HLR (XOR, IDEA, Cave 38)

Supported XA-Core Configs: Atlas 2+1; For IDEN (ESMR) markets; Motorola, Nextel

MSC, HLR-100 GMHM0180 GMHM180


NSS18 MSC/HLR (XOR, IDEA, GSM MoU)

Supported XA-Core Configs: Atlas 2+1; For GSM MoU signatories who are not 3GPP signatories

MSC, HLR-100 GMHU0180 GMHU180


NSS18 MSC/HLR (XOR, IDEA, GSM MoU, 3GPP)

Supported XA-Core Configs: Atlas 2+1; For GSM MoU signatories who are also 3GPP signatories This is the only MSC/HLR load that supports combined GSM/UMTS functionality

MSC/HLR-100

Notes

NSS18

USP 10.0 MSC HLR-200 USP00100 USP0100 USP 10.0 NCL

NSS18HLR-200 MGW18 P86W0180 PP8600W0180

Passport 8600 Rel 3.7.x NCL

Need to ensure that the MSC and HLR use the same Passport load in NSS18

HLR-200 GHVM0180 GHVM180HLR 200 Memory Extension

HLR-200 3PC00070 3PC000703PC RAM DISK Peel/Linux NCL

HLR-200 SAM20070 SAM20070SAM21 Shelf Controller NCL

HLR-200 STRM0006 STRM0006 STORM_IA NCL

SSPFS 7.0 HLR-200 SPFS0070 SSPFS0070 Netra240 NCL

NSS18 HLR-200 CS2M0070 CS2M0070

CS2K management components

Requires NCL SPFS0070. May be co-resident with APS00090 but not with GCBM0180 on the same SPFS0070

HLR-200 SAMM0001SAMM SAM21 EMS

CS2K SAM21 EMS

This is an option within the CS2M0070 NCL that must be ordered.

NSS18 HLR-200 UDBS0020 USDBS0020HLR 200 Database Server NCL

USP 10.0 HLR-200 USP00100 USP0100 USP Rel 10.0 NCL

HLR 200 USP (includes Passport 8600) or MSC USP

HLR 200 3PC Memory Solution

HLR 200 Database Server

HLR 200 SLR

NSS18



3.1.2 NSS18 Software Optionality Controls –SOC New SOCs for NSS18 are shown in the following table:

Feature ID (PMID)

ACTID PCA PRODUCT

NAME

ORDCODE Feature Description

24363, 24364 A00003930, A00004171

GSM MSC-HLR Sub limits

GSM01802 Limits the number of subscribers supported on a Combined MSC/HLR to enable capacity based pricing

25192 A00004164 GSM AOC Multi Rate

Plans

GSM01803 This feature provides functionality that allows CAI elements to be determined on a per subscriber basis with the introduction of multiple rate plans.

26024 A00004582 GSM Access VQE

on SPM

GSM01805 Voice Quality Features for Access facing ports on SPM

24466 A00004614 GSM CAMEL Ringback

GSM01806 Ringback Support for CAMEL DP12 CONNECT solution for GSM and UMTS networks.

23978 A00004054 GSM UUIE in CS1R

GSM01807 This activity covers the following functionalities: 1. User-to-User Information (UUI) received in Call Setup message is passed to SCP (Signaling Control Point) in InitialDP query for IN based calls. 2. Control the above functionality with a new SOC (Software Optionality Control) option.

25986 A00004127 GSM emlpp Multiple Trks

GSM01808 This feature introduces a new algorithm which searcher for the lowest priority calls on all trunks when a pre-emption takes place on a ETSI ISUP or PRI trunk group.

25471 A00004173 GSM BSSAP and ISUP CSE

GSM01810 This feature enhances the existing mechanism to provide more flexible BSSAP and ISUP cause value mapping. This feature also enhances DMS MSC to support non ITU-T Q.850 cause values on a per outgoing trunk basis.

25723 A00003534 GSM HLR SAM ALGORITHM

GSM01811 Custom Authentication Algorithm for T-Mobile USA.

25743 A00007469 GSM HO OMs by LAC

GSM01813 This feature will provide operational measurements to support RF engineers with data to determine the best method of handling handovers or handoffs within their network.

27490 A00007903 GSM Parallel CFVLR Limit

GSM01814 This feature expands the fraud control feature to not only support CFU but to all types of Call Forwarding.

26752 A00007787 GSM MOSMS Diversion

GSM01815 This feature provides a non-standard diversion of MO SMS to an SMSC based on subscriber's CAMEL O-CSI Service Key subscription and MSC datafill, or to a network defined default SMSC when CAMEL is not subscribed, by overriding the SMSC address information received from the MS. The feature



does not provide IN triggering for the MO SMS. DP2 O-CSI triggering for voice call is not impacted by this feature. If the subscriber has CAMEL Ph 3 SMS-CSI, it will override this feature. This feature disables the Nortel proprietary MO SMS triggering based on CS1R/INAP. This feature applies to home subscribers only.

26777 A00007504 GSM UMTS OSB Extensions

GSM01816 This features introduces three new OSB that will enhance the existing barring capabilities in the MSC. The new OSB will be provisioned in the HLR and will be transferred to the MSC as any other subscriber data. This means that the Insert Subscriber Data (ISD) operation will be enhanced to provide full support of this feature in the MAP interface between the VLR and the HLR. The existing parameter will be enhanced to transfer the new OSBs. The internal handling of these new OSBs within the MSC has to be identical to the handling of the existing OSBs categories. Table GVBARDEF size is from 0 to 128 tuples, so there is no need to increment the size of the tables, but the MSC has to be able to associate the new OSBs categories with an entry in the table. The new OSBs will be added to Group 5: § When Registered in the HPLMN, Operator Specific Barring (Type 1) § When Registered in the HPLMN, Operator Specific Barring (Type 2) § When Registered in the HPLMN, Operator Specific Barring (Type 3) § When Registered in the HPLMN, Operator Specific Barring (Type 4) § When Registered in the HPLMN, Operator Specific Barring (Type 5) § When Registered in the HPLMN, Operator Specific Barring (Type 6) § When Registered in the HPLMN, Operator Specific Barring (Type 7)

3.1.3 GSM18 XACore SOC and PARM Configuration Guidelines With the support for multiple XA-Core PE configurations starting with NSS15, two SOC options are available to control the Right To Use (RTU) and allowed In Service PEs for each office, and a Parm is used to inform on-switch tools how to engineer capacity. These items are set during installation for an Initial XA-Core, or a PE extension in an existing XA-Core.

Described below are appropriate settings for the GSM Product Code SOCs and BASE0100, followed by the Rated Power Parm setting.

3.1.3.1 GSM XACore Product Code Tracking SOCs

The Product Code Tracking SOC directly relates to the PE configuration purchased. The GSM XA-Core Product Code SOC is a Track SOC and therefore does not actually “control” the number of PEs in the system, but it does provide information on what has been purchased by the customer (i.e., purchased RTU). This SOC should be changed whenever



the BASE0100 SOC is changed in the office.

GSM18 Product Processor Codes

• GSMX0200 - GSMX XACore 2+1 (new in NSS15) • GSMX0300 - GSMX XACore 3+1 (new in NSS15) • GSMX0500 - GSMX XACore 5+1 (new in NSS15) • GSMX0700 - GSMX XACore 7+1 (new in NSS17 for MSC, introduced in NSS15 for HLR only) • GSMX0900 - GSMX XACore 9+1 (new in NSS18 for MSC only)

3.1.3.2 BASE0100 – Control SOC

BASE0100 is controlled by SOC with a hard usage limit for PE configurations beginning with CSP Release 15. This SOC restricts an office from increasing the number of PEs in the system beyond a limit that has been purchased. For example, if a customer has purchased h/w and s/w for a 2+1 system and wishes to upgrade to 3+1, a new SOC passkey must be generated. This activity is driven by a Purchase Order (PO) from the customer and is tied to the Product Code used for scheduling the job.

The total number of PEs in-service in an office cannot exceed the BASE0100 limit set for that office. Since the limit is set as an upper bound, an office can choose to have fewer PEs in-service than is set by the BASE0100 limit. For instance, if a RTU is purchased for a 3+1 office, the BASE0100 limit is set to 4. A fifth PE would not come into service without increasing the BASE0100 limit. With a limit of 4 however, the office could choose to operate as a 2+1 configuration (or 3 PEs). In this case, with the RTU set for 3+1, the office can upgrade at anytime without requiring a BASE0100 SOC change.

For Initials and CM to XA-Core Conversions, set based on the RTU purchased: o 2+1 – set BASE0100 limit to 3 o 3+1 – set BASE0100 limit to 4 o 5+1 – set BASE0100 limit to 6 o 7+1 – set BASE0100 limit to 8 o 9+1 – set BASE0100 limit to 10

o BASE0100 Threshold Setting = 100% • When the initial keycode is applied for this usage option, the 75% default threshold needs to be

reset to 100%. The on-switch CI command is ‘SOC; ASSIGN THRESHOLD 100 PERCENT TO BASE0100’

• Failure to reset this setting will result in an ‘exceeded threshold’ warning in the SOC logs and in the SOC CI when the option data is viewed.

For PE Extension Upgrade, set in order to allow for the additional RTU purchased o 2+1 to 3+1 – BASE0100 limit changes from 3 to 4 o 3+1 to 5+1 – BASE0100 limit changes from 4 to 6 o Similar setting changes for any additional PE configurations supported

For PE Extension Downgrades – BASE0100 change The ability to reduce the number of PEs in the configuration is acceptable without changing the BASE0100 SOC. Check with the Nortel Account Prime to determine if the RTU for the office will remain with the office. This will dictate a necessary BASE0100 change.

If BASE0100 RTU should be downgraded (RTU moving to a different office):

o 3+1 to 2+1 – BASE0100 limit changes from 4 to 3

o 5+1 to 3+1 – BASE0100 limit changes from 6 to 4



o Similar setting changes for any additional PE configurations supported

If BASE0100 RTU will remain with the office: o No change to BASE0100 is required. The office can always upgrade to the existing limit of BASE0100 at a

later time with no BASE0100 change required.

3.1.3.3 Rated Power Parm

The Rated Power Parm in Table OFCENG tells the on-switch capacity toolset how many PEs are working in the system and are available for engineering. A correct Parm Setting will ensure the office is reporting accurate capacity utilization.

With an n+1 PE configuration, the engineered number of PEs = n. This Parm must always be set when the number of PEs engineered in the system is changed:

For Initials and CM to XA-Core Conversions • 2+1 – set Rated Power as 2

• 3+1 – set Rated Power as 3




• Similar settings for any additional PE configurations supported

For PE Extension Upgrades

• 2+1 to 3+1 – Rated Power changes from 2 to 3




For PE Extension Downgrades



• Similar setting changes for any additional PE configurations supported



3.1.4 Hardware Baselines 3.1.4.1 XA-Core Hardware Baseline

The following table shows the minimum HW versions required on the MSC and HLR to support NSS18. The hardware listed below is not all inclusive. It is intended to reflect recent changes in the primary packs in XA-Core. If an operator needs a list of all the components of a XA-Core, they should contact their Account Manager or Sales Engineer.

NSS18 XA-Core HW baseline

Description PEC QTY NotesRhino Processor Element PPC604/256 MB Module NTLX02CA 4 MD'd, supported for existing systems onlyAtlas Processor Element PPC7410/512 MB Module NTLX02DA 3,4,6,8,10 See note 1I/O Processor 1 - Slot Module NTLX03AB 2 Supported for existing systems only, see note 3I/O Processor 2 - Slot Module NTLX03BB 2 Supported for existing systems only, see note 3HIOP Ethernet I/F NTLX04BA 2 Supported for existing systems only, see note 2HIOP Ethernet I/F NTLX04CA 2 Supported for existing and initials (optional)H-CMIC; Ethernet I/F plus CMIC I/F NTLX17AA 2 All initials should use NTLX17AA OC-3 2-Port I/F Packlet for CMIC links NTLX05AB 2 Supported for existing systems only, see note 3Disk Drive 8.4 GB Packlet NTLX06AB 2 NTLX06AA is not supported in NSS18Disk Drive 34.2 GB Packlet NTLX06AC 2 Optional; AC cannot be mixed with ABDAT Tape Drive Packlet NTLX07AA 2 NTLX07AA supported for existing systemsDAT Tape Drive Packlet NTLX07BA 2 NTLX07BA used for initialsRS232/CL Serial I/F Packlet (RTIF) NTLX08AA 2 Supported for existing systems only, see note 3RS232/CL Serial I/F Packlet (RTIF) NTLX08AB 2 Supported for existing systems only, see note 3Shelf Interface Module NTLX12AA 2Shared Memory 384 MB Module NTLX14CA 7,10

MS CPU, 68020 16 MB 16 MHz PCP NT9X13DG 2 For SN onlyMS CPU, 68020 16 MB 16 MHz PCP NT9X13NB 2 For SNSE only4-Port MS I/F for CMIC NT9X17AD 2,4 2 for SNSE, 4 for SNOC-3 2-Port I/F Paddleboard for CMIC links NT9X63AB 2,4 2 for SNSE, 4 for SN

High Capacity Cooling Unit NTLX10AA 1 Cooling unit includes 3 fan drawers (NTLX11AA).SPM Processor NTLX82BA 2 Optional; Increased capacity over NTLX82AA

Notes:1) All XA-Core initials should use Atlas PEs.The following Atlas XA-Core configurations are supported in NSS18: 2+1: for MSC and MSC/HLR (Trinode).3+1: for MSC and HLR.5+1: for MSC.7+1: for MSC and HLR.9+1: for MSC2) NTLX04CA cannot be mixed with NTLX04AA/BA.See HIOP/HCMIC Provisioning guidelines section for details.3) HIOP CMIC replaces NTLX03AB, NTLX05AB, NTLX08AA/AB for all initial systems.

Required MS Components

Other Components



3.1.4.2 MSC Hardware Changes New MSC HW introduced in NSS18

The following HW is new in GSM/UMTS:

Description PECH-CMIC; Ethernet I/F plus CMIC I/F NTLX17AA

Notes:1) HIOP CMIC replaces NTLX03AB, NTLX05AB, NTLX08AA/AB. NTLX17AA can be combined w/ NTLX04CA to increase Ethernet throughput. 1+1 LX17AA plus 1+1 LX04CA is the only HIOP configuration supported w/ Atlas 9+1. See HIOP/HCMIC Provisioning guidelines section for details.

NSS18 Retired MSC HW

Description PECDisk Drive 4 GB Packlet NTLX06AAHIOP Ethernet I/F NTLX04AA

HW to be upgraded while on NSS18

NSS18 is the last supported release for the following HW:

Description PECNone Identified

Notes

Hardware baseline in NSS18 is NTLX06AB

Optional, Used for Initials (See Note 1)

Notes

The following HW has been retired and is not supported on the MSC in NSS18:

Notes

There should be few, if any, NTLX04AAs in the field

3.1.4.3 SPM Hardware Baseline

In NSS18, the NTLX82BA is used for all new installs. Enhanced capacity is supported in NSS18 via listed SOCs. The NTLX86VA is provided on all new installs and is used for integrated echo cancellation (two mode - vqe/non-vqe).

The following table is provided to detail SPM HW in NSS18.

SPM Hardware Description PECSPME FRAME (DMS) NTLX91BASHELF INTERFACE MODULE (SIM) NTLX61AASPM Processor (CEM) NTLX82AA (Existing)SPM Processor (CEM) NTLX82BA (New Installs)16M DSPR MODULE NTLX65BASPM STM-1 OPTICAL RESOURCE MODULE NTLX99BAOC-3 MODULE NTLX71AAIntegrated ECAN (Optional - Existing) NTLX66BAIntegrated ECAN (Optional - Enhanced VQ) NTLX86VA Notes: 1) Only NTLX66BA and NTLX86VA are supported on SPM for integrated echo cancellation 2) All SPM initials will use NTLX86VA if optional integrated echo cancellation is desired. 3) SPM does not support PTS, PRI or IWF interfaces



3.1.4.4 Media Gateway Hardware

MGW HW is required for BICN support. The following table details these components:

MGW Hardware Description PECDual Shelf Universal Frame CP3/DS1 BITS NTQS20DBDual Shelf Universal Frame CP3/E1 BITS Balanced NTQS20EBDual Shelf Universal Frame CP3/E1 BITS Unbalanced NTQS20FBOne Shelf Universal Frame, CP3/DS1 BITS NTQS10DBOne Shelf Universal Frame, CP3/E1 BITS Balanced NTQS10EBOne Shelf Universal Frame CP3/E1 BITS Unbalanced NTQS10FBSingle Shelf (Upper) Upgrade Kit CP3/DS1 BITS NTQS03DBOne upper shelf upgrade kit for CP3/E1 BITS Balanced NTQS03EBOne upper shelf upgrade kit for CP3/E1 BITS Unbalanced NTQS03FBVoice Service Processor VSP4 NTHW79AA4-port OC3/STM1 TDM FP NTHW70AA4-port OC3C Single-Mode IR ATM FP NTHW15AA4-port OC3C Multimode-Mode IR ATM FP NTHW05AA16-port OC-3/STM-1 Single-mode ATM FP NTHW31AB12-port DS3/E3 ATM FP NTHR23DA2-port General Processor with Disk NTHW10AAModule Filler NTHR64CAModule CP Filler NTPB25AA12 Port DS3 TAF 1:6 Sparing Panel NTHR23xx

Aggregation Node (AN) HW Description PECOne Shelf Universal Frame,CP3/DS1 B NTQS10DBOne Shelf Universal Frame, CP3/E1 BITS Balanced NTQS10EBOne Shelf Universal Frame CP3/E1 BITS Unbalanced NTQS10FBSingle Shelf (Upper) Upgrade Kit CP3/DS1 BITS NTQS03DBOne upper shelf upgrade kit for CP3/E1 BITS Balanced NTQS03EBOne upper shelf upgrade kit for CP3/E1 BITS Unbalanced NTQS03FB4-port OC3/STM1 TDM FP NTHW70AA4-port OC3C Multimode-Mode IR ATM FP NTHW05AA4-port OC3C Single-Mode IR ATM FP NTHW15AA16-port OC-3/STM-1 Single-mode ATM FP NTHW31AB12-port DS3/E3 ATM FP NTHR23DA2-Port General Processor with Disk NTHW10AAModule Filler NTHR64CA12 Port DS3 TAF 1:6 Sparing Panel NTHR23xx

3.1.4.5 Contivity Remote Access Server

Nortel Networks continues to improve customer responsiveness by introducing the Contivity solution for remote access. High speed, secure, internet access will allow Nortel customer service personnel to quickly download NE operations data. This will also reduce patch upload time. The combination will reduce problem resolution time.

For these reasons, the Contivity secure VPN server is a required component in NSS18. Applicable Contivity solutions include CES 600 or CES 1700.

The Contivity Remote Access Server must be engineered to ensure that the number of servers and the configuration of each are appropriate for the network. Nortel Networks customers should contact their account manager or sales engineer to review their needs and order the proper equipment.

Nortel Networks employees that are working with a customer to define remote access requirements should go to



http://ie-projects.ca.nortel.com/cep_message.html, select the button beside “I am working with a Nortel Networks customer and require outbound access from Nortel Networks network to the customer's network to provide product and or services support,” and click “Submit.” Then fill out the form and click “Submit.” Internet engineering will contact the identified prime shortly and work with that prime and the customer to gather the needed information to define and implement the needed connectivity solution.

3.1.4.6 MSC/HLR XA-Core Processor Support Strategy

NSS18 continues to support both the Rhino and Atlas XA-Core PEs. The following information summarizes the processor support strategy.

• All initial XA-Core systems will use Atlas PEs

• New Rhino PEs cannot be ordered.

• Rhino and Atlas PEs in a mixed configuration is not supported.

• Rhino PEs are only supported in a 3+1 configuration for both MSC and HLR

• Atlas PEs are supported in 2+1, 3+1, 5+1, 7+1, and 9+1 configurations for the MSC

• Atlas PEs are supported in 3+1 and 7+1 configurations for the HLR

3.1.4.7 MSC/HLR HIOP and HCMIC Provisioning Guidelines For CMIC/RTIF functionality, HCMIC will be ship baseline for NSS18/CSP20+. Any existing MSC/HLR with IOP/CMIC/RTIF packs upgrading to CSP20 will continue to be supported. However, customers in an R4 MSC configuration or using USP have the option to upgrade to HCMIC to gain Ethernet capacity. HIOP can also be used for Ethernet. Rules on when to use HCMIC for Ethernet and when to use HIOP are noted below. Here are the for Ethernet configuration options:

NTLX17AA HCMIC NTLX04BA/CA HIOP Configurations in order of Ethernet Capacity 2 0 1+1 HCMIC (HCMIC Ethernet capability utilized) 2* 2 1+1 HIOP (HCMIC Ethernet capability not utilized) 2 2 1+1 HCMIC and 1+1 HIOP (HCMIC Ethernet capability utilized)

IOP/CMIC/RTIF combos are also supported for CMIC and RTIF in place of the HCMIC.

GSM/UMTS MSC NSS18 2+1, 3+1, 5+1 Atlas PE 7+1 Atlas PE 9+1 Atlas PE R4 initials Order HCMIC Order HCMIC & HIOP Order HCMIC & HIOP TDM initials Order HCMIC Order HCMIC Order HCMIC Existing XA-Core R4 w/HIOP Continue using HIOP Continue using HIOP Upgrade CMIC to HCMIC &

continue using HIOP Existing XA-Core TDM w/o HIOP

Continue using CMIC Continue using CMIC Continue using CMIC

Existing XA-Core TDM w/o HIOP upgrading to CBM and or USP

Upgrade CMIC to HCMIC

Upgrade CMIC to HCMIC Upgrade CMIC to HCMIC

Existing XA-Core tdm w/o HIOP upgrading to R4

Upgrade CMIC to HCMIC

Upgrade CMIC to HCMIC & add HIOP

Upgrade CMIC to HCMIC & add HIOP

GSM/UMTS HLR NSS18 HLR 100 HLR 200 Initial XA-Core Order HCMIC for CMIC/RTIF Order HCMIC for CMIC/RTIF and HIOP for Ethernet Existing XA-Core No upgrades or adds req’d Keep existing CMIC/RTIF XA-Core packlets and use HIOP

for Ethernet



3.1.4.8 LPP/FLPP Hardware Baseline

A Link Peripheral Processor (LPP) cabinet supports DS30 Local Message Switch – Message Switch (LMS-MS) links while a Fiber Link Peripheral Processor (FLPP) cabinet supports SR128 LMS-MS links. An existing LPP cabinet can be upgraded to FLPP using the NT9X70ZA upgrade kit. While both platforms are supported in NSS18, there are limitations on the use of each.

• The FLPP is NOT supported on the SNSE platform. • Due to the high capacity potential of Atlas, MSC 3+1 and 5+1 Atlas configurations require FLPPs instead of

LPPs for MMU support. The DS-30 links capacity of the LPPs could be a bottleneck for large Atlas MSCs. • All SN MSC initials require FLPPs • LPP/FLPP cabinets are not supported for HLR 200 nodes

LPP cabinets are supported on NSS18 for: • SNSE and SN HLR 100 systems (All HLR initials are SNSE) • SNSE Combined MSC/HLR systems. • Existing Rhino 3+1 MSC without MMU. • Existing Rhino 3+1 MSC with 14 MMU running less than 450k BHCA.

FLPP cabinets are required on NSS18 for: • All SN MSC XA-Core initials. • Atlas 3+1 MSC • Atlas 5+1 MSC • Atlas 7+1 MSC • Atlas 9+1 MSC

The LPP/FLPP is designed to support a maximum of 36 LIU7s running at 0.8 Erlang with no failure conditions. However, there are certain failure conditions (i.e. single MS or LMS failure) that may cause the DS30 links in an LPP to go into overload resulting in message loss. If non-channelized LIU7s are being used the following table shows the maximum number of LIU7s that can be supported per LPP/FLPP to protect against single failures (Simplex Mode):

Maximum number of ASUs Supported per LPP LMS-MS LinksDS30 (LPP) SR128(FLPP)

Traffic Simplex Mode Duplex Mode Simplex Mode Duplex Mode .4E 24 36 36 36.8E 12 24 36 36

Note that only 30 LIU7s are supported per LPP/FLPP when using channelized access as the other 6 slots are used for the NIUs.

SN supports both LPP and FLPP. SNSE supports only LPP. 3.1.4.9 LPP based Mobility Management Unit (MMU) Hardware

The Mobility Management Unit (NTEX22FA) is an MSC capacity enhancing platform introduced in NSS12.

The MMU is: • Optional for MSC XA-Core configurations (including those using USP for signaling) • Not supported on MSC/HLR/STP (trinode) systems. • Not supported on Gateway/Transit MSC systems (i.e. MSC systems that are not connected to the Radio Access

Network.



• Not supported on HLR systems.

MMU engineering/provisioning guidelines 1) MMUs must be evenly distributed across all LPP and FLPP frames in the system. 2) The maximum number MMUs that can be provisioned in a single LPP cabinet is 7. 3) The maximum number of MMUs that can be provisioned in a single FLPP cabinet is 14. If multiple FLPPs are

available, MMUs should be distributed across all FLPPs. 4) On a given LPP/FLPP shelf, MMUs should be provisioned starting from the outside, alternating sides inward.

(i.e. MMUs should be evenly distributed over each half shelf ). The following table summarizes the MMU provisioning rules. Required MMU Distribution No. LPPs/FLPPs 1 2 3 4 5 6 MMUs/LPP or FLPP 14 (FLPP only) 7 5 4 3 3 3.1.4.10 LIU7 Hardware Baseline

For initial systems in NSS18:

The NTEX22CA will be delivered with all initial NSS18 MSC systems for Access (A-Interface) LIU7s and external routers. NTEX22BA/BB will still be supported for all other LIU7s (Access and Network side), NIU, and EIU ASUs including the HLR. For LIU7s only the V.35 and Channel Bus Interface (CBI) options are supported.

For existing systems in NSS18: • Each link set for the A and Iu-CS' interfaces should be provisioned with all NTEX22BBs or all

NTEX22CAs depending on customer need and existing HW. Mixing of BBs and CAs within an A link set is not allowed.

• A mix of NTEX22BBs and NTEX22CAs is acceptable for link sets on the network side.

It is recommended that any new link sets use only NTEX22CAs. The engineering limit of the NTEX22CA is 0.8 Erlangs.

The engineering limit of the NTEX22BB is 0.4 Erlangs for A and Iu-CS' links and 0.8 Erlangs for network side links.

3.1.4.11 LIU7 External Router Hardware Baseline

LIU7 External Routers are used on the MSC to reduce the impact of the large amount of messaging required to inform DTC7s of SS7 routing changes. With LIU7 External Routers, the MTP routing function is disabled in the DTC7s and moved to the LIU7 External Routers. The DTC7s route ISUP traffic to one of the LIU7 External Routers which performs the MTP routing function to select and route the traffic to the appropriate LIU7.

LIU External Routers (8MB or 32MB) are required under the following conditions: • Customer has greater than 58K ISUP trunks • Customer has greater than 140 DTCs • More than 255 route sets are provisioned • Greater than 108 links are provisioned • All USP cutovers regardless of system size

LIU external routers are not used on HLR.

The provisioning guidelines below are only applicable if the conditions above are met; otherwise the External Routers are not required.

LIU7 External Router provisioning guidelines:

• BB and CA (8 MB and 32 MB) LIU External Routers should not be mixed in the system as the 32 MB routers



will scale down to the 8 MB capacity. • The minimum number of LIU7 External Routers that can be provisioned per system is 2. • The maximum number of LIU7 External Routers that can be provisioned per system is 8. • LIU7 External Routers must be evenly distributed over each half shelf in the LPP/FLPP.

The following table provides the minimum number of 8 MB or 32 MB LIU7 External Routers required based on the number of trunks:

Minimum number of 8-Mbyte LIU7 External Routers # of ISUP trunks # of 8 MB LIU7 External Routers

1 - 22500 2

22500 - 45000 4

45000 - 56250 6

56250 - 90000 8

Minimum number #of 32-Mbyte LIU7 External Routers # of ISUP trunks # of 32 MB LIU7 External Routers

1 - 62400 2

62400 - 124800 4

124800 - 156000 6

156000 - 250000 8

The following guidelines should be followed for other ASUs: NIU

o SNSE supports 10 pairs o SN supports 18 pairs

EIU o 4 per LPP o 8 per MSC

3.1.4.12 Peripheral Hardware Baseline

The baseline processor for the DTC02 and the DTCI NA is NTSX05AA. Supported processors in NSS18 are listed below. The DTCO2i is not supported.

DTC/DTCO/DTCI Hardware Description PECDTC (ANSI) NTMX77AA or NTSX05AA DTCI (ANSI) NTSX05AADTCO (ETSI) NTMX77AA or NTSX05AADTCOi (ETSI) NTMX77AADTCO2 (ETSI) NTSX05AA



3.1.5 Software Baselines & PM Load Line-Up

3.1.5.1 XPM, I/O and Test Loads

Load Description Peripheral Filenames

PDTC - XPM Plus offshore PDTC 0 (MX77) odt20CE_040825.XPM20

PDTC - XPM Plus offshore PDTC 1 (SX05) (MSCG use MX77, so ODT19 is loaded)

qdt20CE.XPM20

PDTCi - XPM Plus offshore PDTC 2 (MX77) odi20CE_040825.XPM20

DTC02- XPM Plus offshore PDTC 3 qci20CE.XPM20

DTCI - XPM Plus DTCI 0 (SX05) qli20CE.XPM20

DTC7 - DTC with mx77 ed714bc.XPM14

DTC7 - DTC with sx05 qd717ay1.XPM17

XPM plus firmware load(MX77) upfwnv03.XPM20

XPM plus firmware load(SX05) sxfwak02.XPM20

MTM - Maintenance Trunk Module load mtmka02.s1

MPC - 1984 CCITT compliant X.25 multi protocol

mpc403ac.s1

Enhanced DRAM load - 4 min edrmae11

CTM (Conference Module) mtmka02.s1

Trunk Module 8-Wire btmka02.s1

TM8 (international) tkmtka02.s1

Remote rmtmka01.s1

MPC mpcx33ab.XPM03

Input/Output module IOM7BC01

IOM9BC01

IOMEBC01

IOMRBC01



3.1.5.2 ENET and LPP Loads

Load Description Peripheral FilenamesLIU7 - 8 Meg channelized gar18cd.GSM18LIU7 - 8M Non-channelized LIU glr18cd.GSM18LIU7 - 32M Channelized Basic Load gtc18cd.GSM18Mobility Management ASU Load gmmu18cd.GSM18LIU7 - 32M Non-Channelized Basic Load gts18cd.GSM18ENET - Enhanced network load enc20cq.TL20LIM - Link interface module load lpc20cq.TL20MS - Universal Message

Switch Load muc20cq.TL20NIU - 8M Network interface

unit load nrs20cq.TL20EIU - 8M TCP/IP load (for

IWF) etc20cq.TL20 9X17 firmware Load mpf20cq.TL20

3.1.5.3 XA-Core Firmware

Load Description Peripheral Filenames Rhino PE Firmware xape01ag.TL14 IOP Firmware xaio01ak.TL15 CMIC Firmware pk12ce12.TL16 EDTU dtudab02/ dtudaa01 EDRAM - 16 min ed16aa07 DTU dtubad01.s1 Atlas PE Firmware xape02ab_396.TL17 HIOP(NTLX04BA) XHIO02AA_224_upgr.TL18 HIOP DLL(NTLX04BA,CA) XHIO03AC_143_Idll.TL20 HIOP(NTLX04CA) XHIO02AH_484_upgr.TL19 HCMIC - NTLX17AA XREC01DE_203_pkg.TL20

3.1.5.4 SPM Loads Description NCL Order CodeSPM NA NCL SPM00210SPM Intl NCL SPMW0192



3.1.5.5 SPM Firmware Loads

Description NCL Order CodeSPM NA CEM CEM21XXSPM OC3 OC321XXCoherent ECAN COH0021XXSPM DSP DSP21XXSPM STM-1 CEM CST71XXSTM-1 RM STM71XXCoherent ECAN COH0071XXSPM DSP DSP71XX 3.1.5.6 Aggregation Node (AN) Description OrdercodeAN UAN00052 3.1.5.7 Audio Provisioning Server Software

NSS18 (MG18) will support tones and recorded announcements on the MGW. If an operator desires this optional functionality, the Audio Provisioning Server is used to add and modify the announcements on the MGW. The following software is required to support the APS.

Description Order CodeAPS APS00090

3.1.5.8 Service Builder Compatibility

WIR6.0 WIR6.1

GSM15 √ √

GSM16 √ √

GSM17 √ √

GSM18 √ √

√ = Supported Note: Formal end of life (EOL) of Servicebuilder Wir6/Wir6.1 is Dec 31, 2005.



3.1.6 Supported MSC/HLR Combinations MSC and HLR compatibility across various releases is as shown in the table below:

Note: It is recommended that the same release be used on HLR and MSC to minimize any risk of incompatibility.

HLR Release

NSS18/CSP20

NSS17/CSP19

NSS16/CSP18

NSS15/CSP16

MSC – HLR Compatibility

MSC

Release

NSS18/CSP20

NSS17/CSP19

NSS16/CSP18

NSS15/CSP16

N

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

N

HLR Release

NSS18/CSP20

NSS17/CSP19

NSS16/CSP18

NSS15/CSP16

MSC – HLR Compatibility

MSC

Release

NSS18/CSP20

NSS17/CSP19

NSS16/CSP18

NSS15/CSP16

N

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

N



3.2 MSC Specific Attributes 3.2.1 NSS18 Supported MSC Hardware Configurations

Config # Processor Memory3 Node2 Platform Support1 Rhino 3+1 without MMU 1152 MB (7 SM cards) GSM or UMTS or Combined MSC SNSE Existing 1

2 Rhino 3+1 without MMU 1920 MB (10 SM cards) GSM or UMTS or Combined MSC Supernode Existing3 Rhino 3+1 with 14 MMU 1152 MB (7 SM cards) GSM or UMTS or Combined MSC SNSE Existing 1

4 Rhino 3+1 with 14 MMU 1920 MB (10 SM cards) GSM or UMTS or Combined MSC Supernode Existing

5 Rhino 3+1 without MMU 1152 MB (7 SM cards) Gateway/Transit MSC Supernode Existing

6 Atlas 2+1 without MMU 1152 MB (7 SM cards) GSM or UMTS or Combined MSC/HLR/STP (Trinode) SNSE Existing

7 Atlas 2+1 without MMU 1152 MB (7 SM cards) GSM or UMTS or Combined (Combined MSC/HLR) SNSE Initials

8 Atlas 3+1 without MMU 1152 MB (7 SM cards) Gateway/Transit MSC Supernode Initials & Existing9 Atlas 2+1 without MMU 1152 MB (7 SM cards) GSM or UMTS or Combined MSC SNSE Initials & Existing1

10 Atlas 2+1 without MMU 1920 MB (10 SM cards) GSM or UMTS or Combined MSC Supernode Initials & Existing

11 Atlas 3+1 without MMU 1920 MB (10 SM cards) GSM or UMTS or Combined MSCSupernode,

SNSE5Existing, Initials &

Upgrades

12 Atlas 5+1 Without MMUs 1152 MB (7 SM cards) Gateway/Transit MSC Supernode Existing, Initials & Upgrades



Upgrades



Upgrades

15 Atlas 9+1 without MMU 1920 MB (10 SM cards) GSM or UMTS or Combined MSC Supernode Initials & Upgrades

16 Atlas 2+1 with 14 MMU 1152 MB (7 SM cards) GSM or UMTS or Combined MSC SNSEExisting, Initials &

Upgrades 1

17 Atlas 2+1 with 14 MMU 1920 MB (10 SM cards) GSM or UMTS or Combined MSC Supernode Existing, Initials & Upgrades




21 Atlas 9+1 with 14 MMU 1920 MB (10 SM cards) GSM or UMTS or Combined MSC Supernode Initials & Upgrades

Note 1: This configuration may be memory limited depending on call/services profile.Note 2: BICN/BICC will be supported on all MSC configurations. BICN/BICC will be supported on Trinodes for labs and not-inservice trials only.Note 3: NSS18 introduces a 192MB increase in MSC memory when 10 SM cards are used (1920MB total). The memory increase is not applicable to 7 SM card (1152MB) configurations.Note 4: Atlas 2+1 SNSE (GSM/UMTS or Combined MSC) configuration with fully equipped ENET or LIS supports 10 SM cards (1920MB) if the XA-Core shelf is in an extension cabinet.Note 5: NSS18 introduces support of SNSE configurations greater than 2+1 Atlas and up to 7+1 Atlas with 10 SM cards (1920 MB) if a maximum 8K ENET is provisioned and USP based signaling is used (depopulated LIS and vMMU configuration).

NSS18 Supported MSC Configurations (POR)

NSS18 Supported MSC Configurations

(POR)

SNSE configurations continue to be limited to 3+1 Rhino and 2+1 Atlas with a fully equipped ENET.

SNSE configurations do not support SPMs and do not support FLPPs.

NSS18 will be the last release to support the STP functionality (NSS17 was the last release STP functionality was able to be purchased).

3.2.2 MSC Capacity Expectations NSS18 supports several MSC XA-Core configurations in order to meet the diverse capacity needs of our customers. The following table provides the estimated networked MSC capacity figures for the supported XA-Core configurations. The capacities shown are targets based on Nortel Networks standard GSM or UMTS call models where applicable.

Capacity targets will be verified for the following configurations.



3+1 Rhino w/o MMUs

3+1 Rhino w/ MMUs

2+1 Atlas w/o MMUs

2+1 Atlas w/ MMUs

3+1 Atlas w/o MMUs

3+1 Atlas w/ MMUs

5+1 Atlas w/o MMUs

5+1 Atlas w/ MMUs

7+1 Atlas w/o MMUs

7+1 Atlas w/ MMUs

9+1 Atlas w/o MMUs

9+1 Atlas w/MMUs

GSM Trinode3 N/A N/A 135 N/A N/A N/A N/A N/A N/A N/A N/A N/A TDM GSM MSC (LIU7) 204 359 258 436 385 581 618 823 828 1044 994 1163 TDM GSM MSC (USP) 174 305 220 371 327 494 536 699 704 887 845 989

R4 GSM MSC(VoATM-LIU7)1 141 248 214 340 319 454 512 642 686 815 824 907R4 GSM MSC(VoATM-USP)1 120 211 182 289 271 386 436 546 583 692 700 771

R99 UMTS MSC (LIU7) 174 305 220 371 327 494 526 699 704 887 845 989 R99 UMTS MSC (USP) 148 259 187 315 278 420 447 594 599 754 718 840

R4 UMTS MSC (VoATM)1 90 158 136 216 203 288 326 408 436 518 524 577R99 Gtwy-MSC 540 N/A N/A N/A 950 N/A 1425 N/A N/A N/A N/A N/AR4 Gtwy-MSC 485 N/A N/A N/A 855 N/A 1280 N/A N/A N/A N/A N/A

Note 1: All R4 configurations assume the presence of Signaling Evolution (USP) unless noted, USP is optional in TDM/R99 configurationsNote 2: The potential MSC capacity impact due to signaling evolution and RANAP PER on Core is a preliminary estimate.Note 3: R4 will be supported on Trinodes for labs and not-inservice trials, no live sites. No capacity testing is required for R4 Trinode.Note 4: Rhino PE configuration was Manufacturer Discontinued (MD) in NSS17, therefore only existing sites are supportedNote 5: GSM-R is not supported in NSS18

Configuration4

Technology5 Target BHCA (K)2

3.2.3 Media Gateway Capacity MGW capacity is defined differently from the MSC/ Call Server. The MGW is composed of one or more shelves. Within the shelves different components have an influence on the capacity. The following are the MG18 capacity targets.

Other components such as 4-port FP cards must be provisioned appropriately to support the planned MGW capacity.

VSP2 and VSP2W are not supported in NSS18 and beyond.

3.2.4 Media Gateway Upgrades The Media Gateway is based on Nortel Networks' Passport 15000 platform. It uses the same Passport software upgrade processes already in existence for the Passport 7000, 15000, and 20000 product lines. A brief description of the software upgrade process is as follows:

1) Download the new software to the inactive view on the target Passport shelf (This can be accomplished via either a centralized Software Distribution Server (SDS) or directly from the CDs utilizing a locally connected PC to act as an FTP server.)

VoATM7680960 (VSP2W)ANSI GSM BICNChR 03Q3MG17 4800480UMTS R99NSS18MG 3.0.24800480UMTS R99ChR 04Q1MG 3.0.14800480UMTS R99ChR 03Q1MG03

NotesCapacity per shelf

Capacity per VSP2

ConfigurationRelease Status

Software Release

VoATM7680960 (VSP2W)ANSI GSM BICNChR 03Q3MG17 4800480UMTS R99NSS18MG 3.0.24800480UMTS R99ChR 04Q1MG 3.0.14800480UMTS R99ChR 03Q1MG03

NotesCapacity per shelf

Capacity per VSP2

ConfigurationRelease Status

Software Release

1750

Iu MGW

NSS18MG18(VSP4)

100020002000VoATM Solution GSM/UMTS

Nb MGW

PSTN MGW

A-if MGWConfigurationRelease Status

Software Release

1750

Iu MGW

NSS18MG18(VSP4)

100020002000VoATM Solution GSM/UMTS

Nb MGW

PSTN MGW

A-if MGWConfigurationRelease Status

Software Release



2) Once the new software is downloaded, set the required software packages in the target Passport's "sw available" list.

3) Activate the new software.

4) Once the new load has been verified to be working correctly, confirm and commit the new software.

Please note that the AN must be on release 5.2.2 before starting any MGW upgrades.

A more detailed explanation of the software upgrade process can be found in the following NTP's:

411-2231-331: R4 BICN Media Gateway OAM and Troubleshooting Guide

241-5701-270: Passport 7400, 15000, 20000 Software Installation Guide



3.3 MSC Platforms and Upgrades Shown below are the supported platform upgrades once stability on the NSS18 release is achieved.

Upgrade # Upgrade Type IM Supported

1 SNSE/XA in extension cabinet to SN/XA (2 step) 02-6180 Yes

2 SNSE/XA in single cabinet to SN/XA Not available No

3 Rhino to Atlas 65-6161 Yes 3.3.1 Supported Upgrades and ONPs

Processor Platform Platform

Rhino 3+1 without MMU SNSE > SAME SNSE to Supernode (2 step upgrade) Upgrade to Atlas 3+1

Rhino 3+1 without MMU Supernode > SAME

Rhino 3+1 with 14 MMU Supernode > SAME

Atlas 2+1 without MMU (Trinode) SNSE > SAME

Atlas 2+1 without MMU SNSE > SAME SNSE to Supernode (2 step upgrade)

Upgrade to Atlas 3+1 (Atlas 3+1 requires

Supernode) Atlas 2+1 without MMU Supernode > SAMEAtlas 3+1 without MMU Supernode > SAMEAtlas 5+1 without MMU Supernode > SAMEAtlas 7+1 without MMU Supernode > SAMEAtlas 9+1 without MMU Supernode > SAME

Atlas 2+1 with 14 MMU SNSE > SAME SNSE to Supernode (2 step upgrade)

Upgrade to Atlas 3+1 (Atlas 3+1 requires

Supernode) Atlas 2+1 with 14 MMU Supernode > SAMEAtlas 3+1 without MMU (Gwy/ Tdm) Supernode > SAME

Atlas 5+1 without MMU (Gwy/ Tdm) Supernode > SAME

Atlas 3+1 with 14 MMU Supernode > SAMEAtlas 5+1 with 14 MMU Supernode > SAMEAtlas 7+1 with 14 MMU Supernode > SAME

Atlas 9+1 with 14 MMU Supernode > SAME

Upgrade to Atlas 9+1


No further HW upgrade available

Upgrade to Atlas 5+1Upgrade to Atlas 7+1

Upgrade to Atlas 3+1 with 14 MMU.

No further HW upgrade available. Split MSC & HLR


NSS18 Config (post ONP)


HW Upgrades Available post ONP to NSS18

None, Atlas 9+1 with 14 MMUs is largest supported configuration



Upgrade to Atlas 3+1 with 14 MMU.

Upgrade to Atlas 5+1 without MMU

Add 14 MMUs



3.4 USP Specific Attributes The Universal Signaling Point (USP) provides the platform upon which Nortel’s next generation of signaling applications are based. NSS18 supports the USP10 software release. In this release, the USP provides two main functions for the network:

• Signaling Gateway (SG) – In this configuration, the USP replaces the LIU7s and provides the SS7 interface(s) for the (G)MSC Server or the HLR 200 node. The USP provides a wide variety of SS7 interfaces (Note: Use of the LPP is still required on the MSC for MMUs):

o Narrowband SS7 (MTP3) V.35 links

o Narrowband SS7 (MTP3) on channelized E1/T1 links

o Narrowband SS7 (MTP3) on E1 MTP2 HSLs

o Narrowband SS7(MTP3) on ATM HSL (T1)

o Broadband SS7 (MTP3b) on ATM HSLs (on E1/T1)

o M2UA SIGTRAN links

o M3UA SIGTRAN links

• STP (Signaling Transfer Point) – In this configuration, the USP performs SS7 message routing. While the USP can play the role of a narrowband SS7 STP, the most likely scenarios for STP functionality in this release are for:

o Narrowband STP

o Broadband STP – Only used for ALCAP/MTP3b links on the Nb interface

o IP STP - M3UA/SCTP links on the MAP interfaces, and ISUP/BICC.

A single USP can provide both SG and STP functionalities as long as different point codes are used. IP STP is, however, a standalone product.

The USP uses a modular shelf level structure that is compliant with both the commonly used 19” frame of the datacom/telecom industry and the VME card level standards of the embedded computing/control industry. The USP is a scalable, multi-tasking system, with an easy to use architecture utilizing commercial technologies and ATM switching. The USP uses ATM switching as the internal transport system. The backplane has fully duplicated ATM paths for reliability so that no single failure results in message loss. The USP is based on commercial processors using fault tolerant, high capacity, distributed processing architecture to deliver SS7 functionality.

The shelf is referred to as the Communications Application Module (CAM) shelf. A USP consists of one CAM Control shelf and up to seven CAM extension shelves, depending on the capacity and link requirements. In this release, the USP is productized only in PTE2000 frames and each frame can hold two CAM shelves. Each CAM shelf can host a number of different types of System Nodes:

• CAM Controllers (CCs) System Node – These nodes provide dual internal ATM planes to each CAM shelf, facilitating SS7 and OAM&P data transfer between the cards. The CC System Node also distributes the composite clock to all SS7 Link Nodes on the CAM shelf. The CC System Node consists of a CC mission card in the front slot of the CAM shelf and an OC-3 Transition Module (TM) in the rear slot of the CAM shelf. Each CAM shelf has two CC System Nodes.

• Real-Time Controllers (RTCs) System Node – These nodes provide system boot/recovery/maintenance for of all resident CAM shelf cards. They also provide log, alarm, OM and HMI management. Two RTC System Nodes are required in the CAM Control shelf in an active/standy configuration. Both RTC System Nodes simultaneously process each event and store a complete record of all USP system data for redundancy purposes. The RTC System node consists of a Computing Engine (CE) with a 40GB SCSI disk in the front slot of the CAM shelf and a Power/SCSI/Ethernet Transition Module (PSE TM) in the rear slot of the CAM shelf.

• SS7 Link Nodes – These nodes provide the SS7 interface(s) on behalf of the MSC or HLR 200 node. An SS7 Link Node consists of a Link Engine (LE) mission card (for LSLs or ATM HSLs) or a Computing Engine (CE) card (for IP HSLs) in the front slot of the CAM shelf and a Transition Module (TM) in the rear slot of the CAM



shelf. The TMs provide the physical interface for the SS7 link (V.35, E1, T1 or Ethernet). The USP supports a maximum of 126 cards, although only a total of 680 SS7 links is supported.

• IPS7 Gateway Nodes – These nodes provide the M3UA’/UDP interface between the USP and XA-Core (via the PP8600 or equivalent CO LAN/router – MSC only). They are also used for RFC M3UA network facing links. All SS7 signaling between the XA-Core and USP traverses an IPS7 Gateway Node, regardless of the actual SS7 Link Node type the message is received from or sent to. An IPS7 Gateway Node consists of a CE card in the front slot of the CAM shelf and a PSE TM in the rear slot of the CAM shelf. These nodes are applicable only to USPs playing a SG role. The USP supports a maximum of 16 IPS7 Gateway Nodes, which are deployed in powers of two and spared N+N.

• Filler Cards – These cards provide cooling and air flow for empty CAM slots.

If a USP consists of three or more CAM shelves, they must be connected via two Inter-CAM Communication Modules (ICCMs) as shown in the diagram below. The ICCM is also mounted in a PTE2000 frame that contains USPs. If a USP consists of only two CAM shelves, then the ICCM is optional as the two CAM shelves can be directly connected with each other via the CC System Node’s OC-3 links. The below figure shows USP CAM Shelf Connectivity via ICCMs:

CC

ATMSwitch

CC

ATMSwitch

RTC

RTC

…IPS7 GTWY orSS7 Link Node

IPS7 GTWY orSS7 Link Node

CAM Control Shelf 0

CC

ATMSwitch

CC

ATMSwitch



CAM Extension Shelf 1

CC

ATMSwitch

CC

ATMSwitch



CAM Extension Shelf 2

ICCM 0 ICCM 0

OC-3

OC-3

OC-3 OC-3

OC-3

OC-3

3.4.1 USP Use in NSS18 Core Network Configurations In NSS18, the USP is optional/required in various core network configurations. Listed below are the details concerning these configurations:

MSC configurations

• ANSI/ETSI GSM TDM - USP Optional

• R99 UMTS TDM MG3.02 - USP Optional

• ANSI GSM BICN VoATM - USP Optional



• ETSI GSM BICN VoATM - USP Required

• UMTS BICN VoATM - USP Required

HLR configurations

• HLR 200 node - USP Required

Notes: In NSS18, since coexistence of configurations is supported, i.e. UMTS and GSM, if one configuration requires USP, both configurations will need to use USP. Please note that external routers are required for an LPP/FLPP to USP upgrade on MSC, however they are not required with USP.

3.4.2 USP10 Supported Hardware The following table represents the supported card in NSS18 for the USP NSS18 USP10 Supported Hardware Note: Interfaces in Green/Misc in Orange

Control CAM Extension CAM

System Node/PEC Card Combination PEC Shelf Slot Location Max No.Shelf Slot Location Max No.

Max Total Cards*

RTCRTC (256MB,PP5 CE w 40G PMC disk) NTST11DB 12, 15 2 N/A N/A 2Power/SCSI/Ethernet TM NTST09AC 12R,15R 2 N/A N/A 2

CC CAM Controller NTST02BA 1, 18 2 1,18 2 16NTM81071 OC-3 TM NTST07AB 1R, 18R 2 1R, 18R 2 16

NB SS7 V.35 LinkLink Mission card (LE3 on PP5 w/ 256M RAM) NTST10EA 2-11, 13,14, 16, 17 14 2-17 16 126

V.35 TM NTST58AA2R-11R, 13R, 14R, 16R, 17R 14 2R-17R 16 126

ATM HSL Link(1)Link Mission card (LE3 on PP5 w/ 256M RAM) NTST10EA 2-11, 13,14, 16, 17 14 2-17 16 126

T1/E1 TM NTST81BA2R-11R, 13R, 14R, 16R, 17R 14 2R-17R 16 126

SS7 IP HSL Link(2)Link Mission card (256M PP5 CE) NTST11DA 2-11, 13,14, 16, 17 14 2-17 16 126

PSE TM NTST09AC2R-11R, 13R, 14R, 16R, 17R 14 2R-17R 16 126

IPS7 Gateway NodeLink Mission card (256M PP5 CE) NTST11DA 2-11, 13,14, 16, 17 14 2-17 16 16

PSE TM NTST09AC2R-11R, 13R, 14R, 16R, 17R 14 2R-17R 16 16

NB SS7 Channelized E1/T1(8) Link

Link Mission card (LE4 on PP5 w/ 256M RAM) NTST10FA 2-11, 13,14, 16, 17 14 2-17 16 126

T1-E1 TM NTST81BA2R-11R, 13R, 14R, 16R, 17R 14 2R-17R 16 126

E1 MTP2 HSL LinkLink Mission card (LE4 on PP5 w/ 256M RAM) NTST10FA 2-11, 13,14, 16, 17 14 2-17 16 126

T1-E1 TM NTST81BA2R-11R, 13R, 14R, 16R, 17R 14 2R-17R 16 126

Other Shelf NTS53DAContivity 600 DM1401065/66

Note:1=supports MTP3b,2=support M2UA *Maximum Total Numbers Supported assuming no other cards usedRed Text signifies new cards in this release

3.4.3 USP10 Supported Interfaces



Access ProtocolUSP interface TCAP/MAP CAP MISUP/ISUP BICC Gs MTUP/TUP A Iu-CS Iu-CS' Q.2630(Nb)NB SS7 via V.35 Y Y Y Y N Y N N N NNB SS7 via channelized E1/T1 Y Y Y Y Y Y Y N Y NE1 2M MTP2 HSL Link (Q.703 Appendix A) Y Y Y Y N Y N N N NATM HSL NB (ATM over E1/T1) Y N Y Y N Y N N N NATM HSL BB SS7 (MTP3b/ATM over E1/T1) Y N Y Y N Y N Y N YIP HSL (MTP3/M2UA/SCTP/IP/Ethernet) Y Y Y Y N Y Y N N NIPS7 HSL (M3UA/SCTP/IP/Ethernet) N N N N N N N N N NIP HSL (MTP3b/M2UA/SCTP/IP/Ethernet) N N N N N N N Y N NIPS7 GTWY (M3UA'/UDP/IP/Ethernet) N N N N N N N N N N

Access InterfaceUSP interface to HLR to MSC to PSTN to SCP to SGSN to BSS to RNC to WG to MGNB SS7 via V.35 Y Y Y Y N N N N NNB SS7 via channelized E1/T1 Y Y Y Y Y Y N Y YE1 2M MTP2 HSL Link (Q.703 Appendix A) Y Y Y Y N N N N NATM HSL NB (ATM over E1/T1) Y Y Y N N N N N NATM HSL BB SS7 (MTP3b/ATM over E1/T1) N Y Y N N N Y N YIP HSL (M2UA/SCTP/IP/Ethernet) Y Y Y Y N Y N N YIPS7 HSL (M3UA/SCTP/IP/Ethernet) N N N N N N N N NIP HSL (MTP3b/M2UA/SCTP/IP/Ethernet) N N N N N N Y N NIPS7 GTWY (M3UA'/UDP/IP/Ethernet) N N N N N N N N NNote: H.248 does not go through USP,M3UA'/UDP is internal interface between USP/MSC only

PLMN Protocol

PLMN Interface

MSC IP SIGNALING FRS

Access ProtocolUSP interface TCAP/MAP CAP MISUP/ISUP BICC Gs MTUP/TUP A Iu-CS Iu-CS' Q.2630(Nb)IPS7 HSL (M3UA/SCTP/IP/Ethernet) Y Y Y Y Y Y N N N N

Access InterfaceUSP interface to HLR to MSC to PSTN to SCP to SGSN to BSS to RNC to WG to MGIPS7 HSL (M3UA/SCTP/IP/Ethernet) Y Y Y Y Y N N N N

PLMN Protocol

PLMN Interface

3.4.4 USP Supported Configurations The following configurations are supported in NSS18/USP10:

• USP SGW

• USP NB STP

• USP IP STP

• USP SGW/NB STP

• USP SGW/NB STP/BB STP

• USP NB STP/BB STP

• USP SGW/BB STP

3.4.5 Other Supported USP Components A number of other components might also be required with the USP:

• E1 Timing Signal Generator (TSG) – This component derives independent primary and secondary composite clock outputs from an E1 signal reference and feeds a composite timing signal to the two CAM Controllers in each CAM Shelf. The TSG can be used for the following SS7 Link Nodes.

• Balun Converter – This line and impedance converter is required for European markets requiring coax cabling terminations. For more information, please refer to the USP10 Product Specification.

3.4.6 USP Platform (Signaling Server Application) Order Codes • SSAS0001 Basic Signaling Server Platform always required



• SSAS0002 Basic OAM&P GUI requires SSAS0001

• SSAS0003 ATM High-speed Link requires SSAS0001

• SSAS0004 IP High-speed Link (M2PA) requires SSAS0001

• SSAS0005 Special Studies OMs requires SSAS0001

• SSAS0007 GUI Workstation Continuation requires SSAS0002

• SSAS0008 GTT Continuation (60K – 100K) requires SSAS0001



• SSAS0011 Routeset Continuation (256 – 511) requires SSAS0001

• SSAS0012 Routeset Continuation (512 – 767) requires SSAS0011

• SSAS0013 Routeset Continuation (768 – 1,023) requires SSAS0012

• SSAS0014 Routeset Continuation (1,024 – 1,279) requires SSAS0013





• SSAS0019 ITU/China High Speed Link requires SSAS0001

• SSAS0021 OSS Electronic CLI requires SSAS0001

• SSAS0023 GR-310 Configuration Mgmt. requires SSAS0001

3.4.7 USP SGW Order Codes • USP00100 USP10 Base Order Code

• USP00701 Basic Signaling Gateway Appl. requires SSAS0001 and SSAS0002

• USP00703 RouteMaster Signaling Mediation requires USP00701

• USP00704 IN-SIP Application SSAS0001 and SSAS0002

• BSTP0711 Basic STP Application requires SSAS0001 and SSAS0002

• UNPM0001 Basic Number Portability Appl. requires SSAS0001 and SSAS0002

• UNPM0074 SLR Application requires SSAS0001 and SSAS0002

3.4.8 USP STP Order Codes • BSTP0711 BSTP Basic

• BSTP0012 STP NRC Items

• BSTP0015 Network Indicator Inter-working

• BSTP0304 Multiple Replicated Subsystem

3.4.9 USP UNPM Order Codes • UNPM0001 Basic NP

• UNPM0002 600 to 1,200 qps

• UNPM0003 1,200 to 2,400 qps

• UNPM0004 2,400 to 3,600 qps

• UNPM0005 3,600 to 5,000 qps



• UNPM0006 5,000 to 7,500 qps

• UNPM0007 7,500 to 10,000 qps

• UNPM0008 10,000 to 12,500 qps

• UNPM0030 NP Capacity Upgrade (2 mil to 5 mil)


• UNPM0033 NP Mobile SRF Non-call

• UNPM0034 NP Mobile SRF Call Related

• UNPM0036 NP ITU HEX Digit Support, INAP

• UNPM0037 NP ITU HEX Digit Support, SCCP

• UNPM0052 Tarrif Non-Transparency

• UNPM0053 Flexible Number Routing

• UNPM0056 SS7 NP Database Bulk Load


• UNPM0071 NP Capacity Upgrade (20 ml to 30 mil)


• UNPM0073 NP/SLR Capacity Upgrade (40 mil to 80 mil)

• UNPM0074 SLR Application (12,500 QPS, 50M records)



3.5 HLR Specific Attributes

3.5.1 NSS18 Supported HLR Hardware Configurations and Upgrades The following table shows the NSS18 supported HLR node configurations and the supported HW upgrades:

Notes:

a. Rhino PEs are only supported for existing HLR nodes. All new HLR nodes use Atlas PEs. b. SNSE platform is recommended for all HLR 100 and HLR 200 initials. c. Each HLR 200 node consists of the following HW:

HLR 200 node HW component

Notes

XA-Core (mandatory HLR 200 node component)

Rhino 3+1, Atlas 3+1, or Atlas 7+1 without LPP cabinets. SDM-FT required.

HIOP (mandatory HLR 200 node component)

Two NTLX04BA or NTLX04CA HIOP cards residing in the XA-Core shelf. All initial HLR 200 nodes use NTLX04CA HIOP cards.

Universal Signaling Point with Passport 8600 (8010co chassis) (mandatory HLR 200 node component)

One per HLR 200 node. Two PTE2000 cabinets are required: one contains the Passport (NTPZ90AA), the other contains two USP CAM shelves (NTPZ91AA + NTPZ91KA).

HLR 200 3PC memory solution (optional HLR 200 node component)

The 3PC memory solution is only supported on Atlas HLR 200 nodes that are in a mated pair configuration. One NTRX51RA is required for each HLR 200 node to host this memory solution.

Configuration Number HLR node type XA-Core

processorXA-Core memory Platform

HW upgrades available post ONP to NSS18

1

HLR 100

Rhino 3+1

1728 MB (10 SM cards, 2N+1 sparing)

Supernodeor SNSE

Upgrade to Atlas 3+1, Upgrade to HLR 200 w/o 3PC memory solution.

2

HLR 100

Atlas 3+1


Supernode or SNSE

Upgrade to Atlas 7+1, Upgrade to HLR 200 w/o 3PC memory solution.

3

HLR 100

Atlas 7+1


Supernode or SNSE

Upgrade to HLR 200 w/o 3PC memory solution.

4

HLR 200 w/o 3PC memory solution

Rhino 3+1

1728 MB (10 SM cards, 2N sparing)

Supernode or SNSE

Upgrade to Atlas 3+1, Introduction of 3PC memory solution.

5


Atlas 3+1


Supernode or SNSE

Upgrade to Atlas 7+1, Introduction of 3PC memory solution.

6


Atlas 7+1


Supernode or SNSE

Introduction of 3PC memory solution.

7

HLR 200 with 3PC memory solution

Atlas 3+1


Supernode or SNSE

Upgrade to Atlas 7+1.

8


Atlas 7+1


Supernode or SNSE

None.



d. In the HLR 200 node configurations, the additional 192 MB of memory provided by the use of 2N

sparing is reserved for HLR system use. e. NSS18 HLR nodes should comply with the NSS18 XA-Core HW and SW baselines defined in

this document prior to the ONP to NSS18.

3.5.2 HLR 200 System Requirements In NSS18 an HLR 200 system is composed of:

• One or more HLR 200 nodes. The following chart shows the HW components of each HLR 200 node.

HLR 200 node HW component

Notes

XA-Core (mandatory HLR 200 node component)

Rhino 3+1, Atlas 3+1, or Atlas 7+1 without LPP cabinets. SDM-FT required.

HIOP (mandatory HLR 200 node component)

Two NTLX04BA or NTLX04CA HIOP cards residing in the XA-Core shelf. All initial HLR 200 nodes use NTLX04CA HIOP cards.

Universal Signaling Point with Passport 8600 (8010co chassis) (mandatory HLR 200 node component)

One per HLR 200 node. Two PTE2000 cabinets are required: one contains the Passport (NTPZ90AA), the other contains two USP CAM shelves (NTPZ91AA + NTPZ91KA).

HLR 200 3PC memory solution (optional HLR 200 node component)

The 3PC memory solution is only supported on Atlas HLR 200 nodes that are in a mated pair configuration. One NTRX51RA is required for each HLR 200 node to host this memory solution.

• A pair of Data Servers per network (optional)

Provides centralized provisioning for all HLR 200 nodes in the network Auto-provisions the IMSI/MSISDN to HLR mappings in the Service Location Register

(SLR). Note: Data Server is mandatory in networks with SLR. Supports mastering of the subscription data for all the subscribers residing on HLR 200

nodes in the network.

• A pair of Service Location Registers per network (optional) Provide flexible MSISDN/IMSI numbering for all the subscribers residing on HLR 200

nodes in the network.

• CEM server and client(s) or PWI server and client(s) for HLR 200 system OAM (required)



3.5.3 HLR Capacity Targets The active subscriber capacity of an HLR node is dependant on the HLR XA-Core configuration and on the specific datafill and transaction profiles.

These are the Nortel HLR reference datafill services profiles:

GSM (HMMC-S) UMTS (HMMC-UMTS)

Basic Services TPHNY: 100% 100% SMMT: 100% 100% SMMO: 0% 100% CDA: 10% 0% CDS9600: 0% 100% Miscellaneous Services

MSISDNs: 1.10 1.10 CAMEL: 0% 100% OCSI / TCSI pairs 0.00 2.00

GPRSs: 0% 100% PDPs per sub 0 3 Supplementary Services

CFU 100% 100% CFB 100% 100% CFNRY 100% 100% CFNRCH 100% 100% BAOIC 100% 100% CW 100% 100% CH 100% 100% MPTY 100% 100%



These are the Nortel HLR reference transaction profiles:

HMMC-S HMMC-UMTS SRI-PRN 0.2800 0.2800 SRI (CFU) 0.0100 0.0100 SRI-SM 0.0900 0.0900 SRI (CAMEL) 0.0000 0.0000 UL-ISD-CL 0.0244 0.0244 UL (SuperCharged) 0.5856 0.5856 Standalone ISD 0.0000 0.0000 SAI triplets (off-board) 0.0000 0.0000 SAI triplets (comp-128) 0.1900 0.0000 SAI triplets (Rijndael) 0.0000 0.0000 SAI quintuplets (off-board) 0.0000 0.0000 SAI quintuplets (Rijndael) 0.0000 1.2600 UGL-ISD-CL 0.0000 0.6100 UGL (SuperCharged) 0.0000 0.0000 ASC 0.0000 0.0000 NMP 0.0000 0.0000 SMWD 0.0000 0.0000 RegSS 0.0000 0.0000 EraSS 0.0000 0.0000 ATI-PSI 0.0000 0.0000 SRI-PSI 0.0000 0.0000 PUSSR 0.0000 0.0000 USSN 0.0000 0.0000 transactions/sub/busy hour 1.180 2.608 natural mobility rate 0.610 0.610 natural authentication rate 0.190 0.630 ratio of SAI to UL 0.31 1.03 SuperCharger CS profile effectiveness: 96% 96% SuperCharger PS profile effectiveness: 0% 0% SuperCharger authentication effectiveness:

0% 0%

% of subs attached to CS domain 100% 100% % of subs attached to PS domain 0% 100% % of subs with Rjindael alg. 0% 100% % of triplet vs. quintuplet auth requests 100% 0% % of CAMEL subscribers 0% 0% triplets per hour 0.190 0.000 quintuplets per hour 0.000 1.260 SAI quintuplet ratio 0% 100%



The NSS18 HLR capacity targets based on the Nortel HLR reference datafill and transaction profiles are as follows:

Configuration Number HLR node type XA-Core

processor XA-Core Memory

GSM capacity (HMMC-S)

UMTS capacity (HMMC-UMTS)

1

HLR 100

Rhino 3+1


2M Subs Datafill limited

330k Subs Realtime limited

2

HLR 100

Atlas 3+1




3

HLR 100

Atlas 7+1



1.3M Subs Datafill limited Note: Datafill optimizations are not applicable to HLR 100 SNSE LPP signaling is bottle neck at ~700k subs.

4


Rhino 3+1


2.6M Subs Realtime limited


5


Atlas 3+1




6


Atlas 7+1



1.7M Subs Datafill limited

7


Atlas 3+1


3.75M active + 3M pre-provisioned Realtime limited

800k active + 2M pre-provisioned. Realtime limited

8


Atlas 7+1


5M active + 3M pre-provisioned. XA-Core memory limited

2.25M active + 2M pre-provisioned XA-Core memory limited



The HLR provisioning capacity is dependant on the HLR configuration and on the specific provisioning profile.

This is the Nortel HLR reference Provisioning Service Profile:

Index MSP Data ID Service Service Type 1. TS11 Telephony Basic service 2. TS21 Short message MT/PP Basic service 3. TS22 Short message MO/PP Basic service 4. AOCC Advice of charge Supplementary service 5. CLIP Calling line identification

presentation Supplementary service

6. CLIR Calling line identification restricted Supplementary service 7. HOLD Call hold Supplementary service 8. MPTY Multiparty Supplementary service 9. CW Call waiting BSG-based

supplementary service 10. CFNRY Call forwarding on no reply BSG-based

supplementary service 11. CFNRC Call forwarding not reachable BSG-based

supplementary service 12. CFB Call forwarding busy BSG-based

supplementary service 13. CFU Call forwarding unconditional BSG-based

supplementary service 14. BAOC Barring of all outgoing calls BSG-based

supplementary service 15. BOIC Barring of all outgoing international

calls BSG-based supplementary service

16. BOICEXHC Barring of outgoing international calls except to home country

BSG-based supplementary service

17. BAIC Barring of all incoming calls BSG-based supplementary service

18. BICROAM Barring of incoming calls while roaming outside of home country

BSG-based supplementary service

Provisioning command mix:

BSP MSP Create 20% 0% Modify 40% 25% Activate 20% 25% Display (without location data)

0% 50%

Deactivate 0% 0% Delserv 10% 0% Delsub 10% 0%



The NSS18 provisioning capacity targets based on the Nortel HLR reference provisioning profile are:

25,000 orders/hrHLR 200

Provisioning Capacity

100,000 orders/hrData Server



Provisioning Capacity

100,000 orders/hrData Server




3.5.4 Universal Signaling Point for HLR 200 HW Frame Codes for USP

USP is a required HW component for each HLR 200 node. The starting USP configuration for HLR 200 nodes consists of bay 0 and bay 1. Bay 2 is only needed if more links than what is supported with two USP shelves are required.

• Bay 0 (NTPZ90AA)

Includes one PTE2000 frame, one 8010co BIP, and one Passport 8010co.

• Bay 1 (NTPZ91AA and NTPZ91KA) NTPX91AA includes one PTE2000 frame, one EBIP, and one USP CAM shelf. NTPZ91KA includes one USP extension CAM shelf. NTPZ91AA and NTPZ91KA are both required for the HLR 200 USP. OA&M PC is required HW associated with bay 1. Contivity 600 is a provisionable item associated with bay 1. One or more Contivity 600s are required at a system level to access NSS18 HLR 200 components. USP links in bay 1 are provisionable.

• Bay 2 (NTPZ91AA, NTPZ91KA, and NTPZ91KB)

NTPX91AA includes one PTE2000 frame, one EBIP, and one USP CAM shelf. NTPZ91KA includes one USP extension CAM shelf. NTPZ91KB includes two ICCMs. NTPZ91AA and NTPZ91KB are required for bay 2. NTPZ91KA is optional. USP links in bay 2 are provisionable.

Please refer to EG5401 for further details.

SW Order Codes for USP and Passport

Please refer to section 3.1.1 for relevant SW information.



3.5.5 HLR 200 3PC Memory Solution

HW for HLR 200 3PC Memory Solution Frame

The 3PC memory solution is an optional component of an HLR 200 node. The 3PC memory solution is only supported on Atlas HLR 200 nodes that are in a mated pair configuration. No more than 6 pairs of 3PC cards are supported for HLR200 configuration and hence should not be ordered. It is anticipated that up to a maximum of 6 pairs of 3PC cards are needed to satisfy NSS17 or 18 HLR200 capacity commitments. Any exception to this rule needs to be agreed upon with HLR PLM. The frame level PEC code for the 3PC memory solution is NTRX51RA. This frame will include as shown below:

• Two SAM21 Chassis with up to 6 3PC cards in each • Two PDS Intel Processor Server Chassis • Breaker Interface Panel at top for power distribution and alarm collection

SAM21 Chassis SM21-00

SAM21 Chassis SM21-01

Blank Panel

BIP

PDS-00

PDS-01



The 3PC memory solution also requires a Netra 240 for OAM.

• Specifications of Netra 240 for HLR 200 3PC Memory Solution:

– Two (2) processors – 2G RAM – 73GB hot swappable Disk Drives – mirrored – One (1) DVD RW Drive

• DVD RW is part of the NSS18 Netra 240 hardware baseline. • Starting in NSS18, new HLR 200 3PC memory solutions are shipped with Netra

240 DVD RW drives. • Existing NSS17 HLR 200 nodes with 3PC memory solution must replace the Netra

240 DVD ROM drive and install the Netra 240 DVD RW unit while on NSS17 before ONP to NSS18.

– Four (4) Ethernet ports

The Netra 240 is provisioned in the USP bay 0 of the HLR 200 node as illustrated in the figure below:

One additional Netra 240 spare server is required per site to obtain recommended level of hardware support.


Bay 0 Bay1

Netra 240



SW Order Codes for HLR 200 3PC Memory Solution


3.5.6 Data Server HW for Data Server Frame The Data Server is an optional HW component for the HLR 200 system. The frame level code for the Data Server is NTPZ94AA.

The Data Server is deployed in pairs to provide geographical redundancy.

Each Data Server must be co-located with an HLR 200 node. Note: The Data Server uses the Passport 8600 (HLR 200 USP bay 0) for communication with other nodes.

In NSS18, the Data Server frame includes the following HW:

• One Power Distribution Panel

• One Netra1280 with the following HW components: Netra 1280 for Univity Data Server

1 Netra 1280 DC w/4x1.2GHz,8GB,2x73GB, DVD 1 DDS-4 tape drive (20GB)

2

Quad Fast Ethernet QFE/P Location: PCI Bridge #0, PCI slot #1 PCI Bridge #1, PCI slot #2

2

SCSI LVD 160/320 Location: PCI Bridge #0, PCI slot #0 PCI Bridge #1, PCI slot #4

1 Cable Arm , sm all, power and IO cables

• One Sun StorEdge 3310 SCSI Array with 12 73GB 10K RPM disks. • The SCSI disk array is part of the Data Server hardware baseline. • Starting in NSS18, new Data Servers are shipped with the SCSI disk array. • Existing NSS17 Data Servers must install the SCSI disk array while on NSS17

before ONP to NSS18. Please refer to EG5401 for further details.

SW Order Codes for Data Server




3.5.7 Service Location Register HW Frame Codes for SLR

The SLR is an optional HW component for the HLR 200 system. Note: The Data Server is a required component if using SLR.

SLRs are deployed in pairs to provide geographical redundancy.

The starting SLR configuration consists of bay 1. Bay 2 is only needed if more links than what is supported with two USP shelves are required.

• Bay 1 (NTPZ91AA and NTPZ91KA)

NTPX91AA includes one PTE2000 frame, one EBIP, and one USP CAM shelf. NTPZ91KA includes one USP extension CAM shelf. NTPZ91AA and NTPZ91KA are both required for the HLR 200 SLR. OA&M PC is required HW associated with bay 1. Contivity600 is provisionable item associated with bay1. One or more Contivity600s are required at a system level to access NSS18 HLR 200 components. USP links in bay 1 are provisionable.

• Bay 2 (NTPZ91AA, NTPZ91KA, and NTPZ91KB)

NTPX91AA includes one PTE2000 frame, one EBIP, and one USP CAM shelf. NTPZ91KA includes one USP extension CAM shelf. NTPZ91KB includes two ICCMs. NTPZ91AA and NTPZ91KB are required for bay 2. NTPZ91KA is optional. USP links in bay 2 are provisionable.


SW Order Codes for SLR




3.5.8 HLR SW Upgrades HLR sites must be running at least NSS16 prior to upgrading to NSS18. The following Core HLR SW upgrades are supported in NSS18:

NSS18 HLR 100 SW load


NSS16 HLR 100 SW load Y YNSS16 HLR 200 SW load N YNSS17 HLR 100 SW load Y YNSS17 HLR 200 SW load N YNSS18 HLR 100 SW load Y YNSS18 HLR 200 SW load N Y

To Release

From

Rel

ease



NSS16 HLR 100 SW load Y YNSS16 HLR 200 SW load N YNSS17 HLR 100 SW load Y YNSS17 HLR 200 SW load N YNSS18 HLR 100 SW load Y YNSS18 HLR 200 SW load N Y

To Release

From

Rel

ease



3.6 Passport 8600 Specific Attributes In NSS18, CO LAN/router functionality is provided by utilizing two Nortel Networks Passport 8600s. Dual PP8600 are required to ensure reliability and allow for hitless upgrades. While this functionality maybe provided by utilizing other 3rd party OEM equipment, it is required to support IP connectivity to and from the following:

• XACore HIOPs and/or HCMICs

• USP PSE TMs (used with RTCs, IPS7 Gateway Nodes and IP HSLs)

• Local Passport 15000 CP3 cards

• Local Passport 15000 2p GP Dsk cards

• SDM/FT or CBM

• Local GPP IWFs

The Passport 8600 (PP8600) is a modular product that offers Layer 2 (Ethernet) switching and line-speed Layer 3 (IP) routing functionality in a single chassis. The PP8600 utilizes a 10-slot Passport 8010co chassis. The single chassis plus the Breaker Interface Panel (BIP) reside in a single PTE2000 frame(600mm W X 732mm D and 2125mm H). Other chassis types (8010, 8006, etc.) are not supported.

The supported modules for use in the slots of the PP8600 are:

• 8691SF CPU/Switching Fabric module – This card is the heart of the PP8600, providing the core switching fabric, a CPU subsystem and a real-time clock. The core switching fabric is used to switch all traffic through the other modules. The CPU subsystem manages the switching fabric and all other I/O modules. One of these modules is provisioned in slot 5 of each 8010co chassis. .

• I/O modules – These cards provide 10/100BaseT Ethernet interfaces, Gigabit Ethernet interfaces, or a combination of the two. The number and type of I/O modules depends on the connectivity requirements of the system.

O 8632TXE – This module provides 36 10/100bT Ethernet ports and two bays for Gigabit Interface Converters (GBICs). Two 8632TXE modules are required in each PP8600 as a baseline configuration, providing redundancy for the MLT (Multi-Link Trunking) and VRRP messaging between the dual PP8600s. This leaves 64 10/100bT Ethernet ports and one Gigabit Ethernet port per chassis available for other component connectivity.

O 8648TXE – This module provides 48 10/100bT Ethernet ports. An additional 8648TXE module is provisioned per chassis if/when the operator requires more 10/100bT Ethernet ports than is provided by the current configuration. This module is not part of the baseline configuration.

O 8608GBE – This module provides eight bays for GBICs. An additional 8608GBE module is provisioned per chassis if/when the operator requires more Gigabit Ethernet ports than is provided by the current configuration. This module is not part of the baseline configuration.

3.6.1 Passport 8600 Hardware Baseline The baseline configuration for utilizing PP8600 in NSS18 includes the following

• Two PTE2000 Frames with 8600/BIP

• Each PP8600 will include 2 863TXE, 1 8691SF



Fille

r

1

8632

TXE

Fille

r

Fille

r

2

Fille

r

Fille

r

3

Fille

r

Fille

r

4

Fille

r

Fille

r

5

Fille

r

Fille

r

6

Fille

r

Fille

r

7

Fille

r

Fille

r

8

Fille

r

Fille

r

9

Fille

r

Fille

r

10

Fille

r

8632

TXE

8632

TXE

8632

TXE

.

.

.

.

.

.

.

.

.

.

.

.86

91SF

CPU

/Sw

itch

8691

SF C

PU/S

witc

h

VR

RP

/MLT

VR

RP

/MLT

GBIC

10/100bT port 3.6.2 Passport 8600 Software Order Code The software order code for the PP8600 is P86W0180.

3.6.3 Passport 8600 Engineering Attributes 3.6.3.1 Passport 8600 Memory This PP8600 configuration supports the storage of 32K records, where a record can include:

• A MAC (Media Access Control) entry • A VLAN (Virtual Local Area Network) entry • A multicast entry • An ARP (Address Resolution Protocol) entry • An IP route entry • An IP filter rule • An IPX (Internetwork Packet Exchange) network entry

In the extremely rare scenario where 32K records are not sufficient, the operator has the option of using the PP8600 M-modules (8632TXM, 8648TXM, 8608GBM) and configuring the PP8600 to operate in “M-mode” (extended memory mode). This increases the storage capabilities to 128K records.

Existing PP8600s configured with the original 8691SF (DS1404025) require no changes as this card has the required 128MB of memory for this release. New PP8600s should be configured with the 256MB 8691SF (DS1404090) to provide room for future services.

3.6.3.2 Passport 8600 ATM Limitations It should be noted that this solution does not support an ATM WAN interface on the PP8600, due to the limitations of the PP8600’s ATM MDAs. For ATM Core Networks, the PP8600 provides 10/100bT Ethernet links to a Passport 15000 (Aggregation Node), which in turn provides the ATM WAN interface.



Passport 8600Virtual Router A

Passport 8600Virtual Router B

GigE

ATMFP

ATMFP

2p GP Dsk

2p GP Dsk

2p GP Dsk

2p GP Dsk

100bT

ATMFP

ATMFP

PP15KAggregationNode

100bT

… …To ATM WAN (DS3 or OC-3)

and/orLocal MG Shelf (OC-3)

backplane

… 100bT …

To CO Network Elements (XACore, USP, etc.)

3.6.3.3 Passport 8600 100BaseT Engineering Care must be taken not to exceed the 100m maximum cable length limit of 100bT connections. A maximum of two repeater hubs can be used. The following is a list of NEs that could require one or more 10/100bT terminations on the PP8600s:

• XACore HIOPs and/or HCMICs

• USP PSE TMs (used with RTCs, IPS7 Gateway Nodes and IP HSLs)

• Local Passport 15000 CP3 cards

• Local Passport 15000 2p GP Dsk cards

• SDM/FT or CBM

• Local GPP IWFs

3.6.3.4 R4 BICN Router Requirements

Implementation of R4 BICN requires that LAN connectivity be available at the MSC. The following criteria must be met to ensure proper operation and capacity. Nortel recommends the Passport 8600 to fulfill this need if a customer does not have router equipment that meets the criteria below.

Interfaces • 10/100bT Ethernet required • Redundant CPU, fabric (hot standby), power • Support for inservice software upgrades • NEBS level 3 compliant • Front access of all modules and field replaceable units • DC power and custom BIP • 2 units max in 19” frame Routing • Support for internal L3 routing + switching • Static and ECMP (including # of routes in the list) • MLT



• VRRP (VRRP handover - must be 1 second or less) • Gratuitous ARP • Support for VLANs for traffic segregation Capacity • Routing done in line cards • Central CPU for routing updates • Filtering done in ASICs • Secure login for OA&M • It is recommended that BICN traffic be separated from corporate traffic (e.g. separate LAN) to avoid congestion

3.7 Passport 7000 Specific Attributes The Passport 7000 (Passport 7000) and its MSA32 FP play two functions in a BICN network, and these are considered separately. The Passport 7000 requires its own shelf; however it is possible to fit a Passport 7000 shelf and Passport 15000 (MGW) shelf into the same frame. This configuration is known as a VSS (Variable Speed Switch) frame. The MSA32 FP is not allowed in a Passport 7000 shelf that hosts the GPP IWF functionality.

The MSA32 is currently a two-slot card and occupies any pair of adjacent slots in the shelf except those reserved for the CP3 card (slots 0 and 1). The MSA32 has 32 channelized DS1 or E1 ports plus optionally two OC-3 or STM-1 optical ports.

Note: A new single-slot version of the MSA32 will be introduced in the PCR6.1 timeframe (NTNQ93BA (E1) or NTNQ94BA (DS1)). This card is identical in functionality to the two-slot MSA32 except that it does not have the optioncal OC-3/STM-1 ports.

3.7.1 Passport 7000 Hardware Baseline As described above, below is a listing of the required and optional hardware for the Passport 7000 in NSS18:

Passport 7000 Hardware Description PECPASSPORT CABINET NTJS65DBMULTIPLEXER DS1-DS3 (M13)-48V PWRD NTPV02AACONTROL PROCESSOR NTNQ01AA32p E1 NTNQ69AA32p E1 + STM-1 MMF NTNQ71AA32p E1 + STM-1 SMF NTNQ73AA32p DS1 NTNQ74AA32p DS1 + OC-3 MMF NTNQ76AA32p DS1 + OC-3 SMF NTNQ78AA 3.7.2 Passport 7000 Software Order Code The software load for the Passport 7000 is PCR5 2.3/PCR6.1, the order code is TBD.

3.7.3 Passport 7000 Engineering Attributes 3.7.3.1 DS0 Grooming With the legacy DMS-MSC, the ENET and NIU were used to strip channelized signaling from E1/DS1/STM-1/OC-3 carriers and deliver it to a Channelized LIU7 (and vice versa). This type of signaling is used on a number of interfaces, such as: • GSM A-interface (BSSAP signaling) • UMTS Iu-CS’ interface (PER-decoded RANAP signaling) • Channelized ISUP/MAP/CAP signaling (market dependent, more common in Europe and Asia) When the LIU7 is replaced by the USP, some other node must now perform this function, which is referred to as DS0 grooming. The only node in the Nortel product portfolio that can do this for both DS1 and E1 carriers is the Passport 7000 and its MSA32 FP.



Specifically, the Basic Structured NxDS0 CES capabilities of the MSA32 FP will be used to strip signaling timeslots from E1/DS1 carriers carrying bearer so that they may be sent to the USP, packing up to eight DS0s of signaling per E1/DS1 to maximize efficiency and reduce the footprint of the USP. The following diagram illustrates how this is done.

S S S

B B B B B

B B B B B

B B B B B

…

…

…

…

…

…

…

… E1/DS1 to 8-link Channelized E1/DS1 card of the USP

Up to 8 signalingDS0s per E1/DS1

E1/DS1 to PDTC or SPM (via MUX)

B B B S B B

B S B B B B

B B B B B S

… …

… …

… …

E1/DS1 to BSCs

(B)earer and (S)ignalingtimeslots

CES instances (AAL1 PVCs)

One or more MSA32

Ingress and egress E1/DS1 can be on the same MSA32 (intra-card PVCs) or different MSA32 (inter-card PVCs)

As such, the number of MSA32 FPs required can be calculated by the following formula, rounding up to the nearest whole number:

(2n + n/8) / 32, where n=the number of channelized signaling links

This formula assumes a maximum of one channelized signaling link per E1/DS1. E1/DS1 carriers that carry only bearer (no signaling) from an SSP (e.g. BSC, R99 MGW) do not need to traverse the MSA32 at all.

In this role, the optical ports of the MSA32 are not used or required, therefore the single-slot MSA32 FPs are an option. The optical ports on the MSA32 are not channelized and thus not capable of DS0 grooming. If channelized signaling is carried within optical carriers (e.g. Iu-CS’ interface between SPMs and the 4p OC-3/STM-1 TDM FP of the PC03 MGW) then a MUX must be used to convert to electrical interfaces before feeding these into the MSA32 FPs.

SPM

ENET

MS

XACoreXACore

SPMSPM

ENETENET

MSMS

XACoreXACoreXACoreXACore

PP8600

USPUSP

Iu-cs’

FLPPMMU

FLPPMMU

HI OPHI OP

MGWPP7K

PP7K

Signaling and bearer on STM-1/OC-3

MUX

MUX

MUX

MUX

Signaling on E1/DS1

Signaling and bearer on E1/DS1

Bearer on E1/DS1

Bearer on STM-1/OC-3



DS0 grooming is expected to be a temporary function in the network. It is needed from the time an operator migrates the first channelized signaling link to the USP up until the time that all channelized signaling is entering a MGW (and thus using M2UA signaling backhaul to reach the USP). Once all channelized signaling is entering the MGW, the Passport 7000 is no longer needed to provide a DS0 grooming function and can be decommissioned.

3.7.3.2 ATM Interface MUX The USP supports a broadband (MTP3b) SS7 interface over ATM high speed links (E1/DS1). The USP does not support an optical interface. Therefore, the USP requires a node that performs ATM switching between electrical (E1/DS1) and optical (STM-1/OC-3) interfaces in the following scenarios:

• If the Iu-CS control plane (i.e. RANAP signaling) is sent to the USP directly without being backhauled via the MGW.

• If the USP is acting as a broadband STP for ALCAP signaling on the Nb interface (ATM core network only).

The MSA32 FP of the Passport 7000 also serves this function via its ATM PNNI service. Unlike the DS0 grooming function, this role requires use of the STM-1 or OC-3 optical ports, which run in a 1+1 configuration with APS protection. Only one STM-1/OC-3 on the MSA32 can be active, the other can only be used as an APS backup. Up to 30 of the E1/DS1 ports can be used in this role, ports #30-31 cannot be used.

The USP’s ATM HSL capacity is quite low – only a single E1/DS1 and a single ATM PVC per card. Each SAAL-NNI link that enters the MSA32 via one of the optical ports (Iu-CS or Nb interface) should be switched to an ATM PVC that leaves the MSA32 via one of the electrical ports, destined for the USP. This switching could occur between optical and electrical ports on the same (intra-card) or different (inter-card) MSA32 FPs.

Because each MSA32 has only a single optical port, PVCs should be aggregated before entering this port to ensure that the card is used in a cost effective manner. To take full advantage of the 30 E1/DS1 ports that can carry ATM traffic towards the USP, the optical port of the MSA32 (as well as the ATM network that feeds it traffic) should be configured to support up to 30 ATM PVCs. This is illustrated in the diagram below:

PP7KSSCF-NNISSCOPAAL5ATM

RANAPSCCPMTP3b

OC-3/STM-1

SSCF-NNISSCOPAAL5ATM

RANAPSCCPMTP3b

OC-3/STM-1


ALCAPMTP3b

OC-3/STM-1


ALCAPMTP3b

OC-3/STM-1

or SSCF-NNISSCOPAAL5ATM

RANAPSCCPMTP3b

DS1/E1


RANAPSCCPMTP3b

DS1/E1


ALCAPMTP3b

DS1/E1


ALCAPMTP3b

DS1/E1

or

MSA32MSA32 Backplane

STM1 or

OC3

E1 or DS1

E1 or DS1


RANAPSCCPMTP3b

DS1/E1


RANAPSCCPMTP3b

DS1/E1


ALCAPMTP3b

DS1/E1


ALCAPMTP3b

DS1/E1

or

orTo RNC or ATM Core Network

To USP’s ATM HSL

To USP’s ATM HSL

AAL5 PVCs

…

3.8 GEM Specific Attributes 3.8.1 GEM Order Codes Per Application

Existing SDM-FT NCLs remain on DAT tape.



New Core and Billing Manager (CBM850) does not contain DAT tape drive, but instead uses RW-DVD, requiring CD media.

CBM850 requires Succession SSPFS base layer for Solaris OS. SSPFS layer will be pre-loaded at system house prior to shipment.

GCBM0180 = wireless creates; after revaulting Wireline base CBM layer. SSPFS_order code SPFS0070 = Succession Server Platform Foundation Software (pre loaded on server) Delivery NCL Right-to-use Description Order code (media) Pricing code MNCL SDM/FT and CBM850 Platforms

Core and Billing Manager (Solaris) GCBM0180 (CD) NTM504AHZA yes SDM/FT Base Software (AIX OS) SDM/FT Install and Upgrade Scripts

FSDN0180 (1-DAT)

FSDNM180 (1-DAT)

HLR-PS Base Application Load NTM504ACSA

optional: HLR-PS Bulk Service Provisioning NTM504ACRA optional: HLR-PS virtual HLR NTM504ACTA

HLR-PS Load Fee NTM504AAGA CIS/CT Base Application Load NTM504AESA SBA Application Load SBA BILLING AUDIT REQUIREMENTS NTM504AATA FTAM Load OMC-S/CEM Base Application Load NTM504ADTA

optional: OMC-S/CEM billing to OM NTM504ADSA optional: OMC-S/CEM online configuration

management NTM504ADWA OMC-S/CEM Load Fee

CGEM0180 (1-DAT)

NTM504AAHA

CGEMM0180 (1-DAT)

HLR 200 fast provisioning application load EGEM0180 (1-DAT) EGEMM0180 (1-DAT)

CEM Server Platform - SunFire V880 CEM on Sun Platform N/A CEM interfaced w/ MDM API N/A CEM Server Load Fee NTM504AAJA

CEM support of GSM18 uHLR NTM504AHKA A0521452

CEM support of MGW NTM504AGPA CEM support of MGW (per sub) NTM504AGQA CEM support of standalone USP

OMSN0180 (1-CD)

NTM504AHHA

OMSNM180 (1-CD)

HLR 200 Data Server -specific: besides GEM software, CEM Server platform needs SMC Server software

SUNS0180 N/A TBD



TPNN SunMC V3up4 (HLR 200 Data Server - Included in SUNS0180; must be ordered to track software royalty)

TPNN0038 TPNN0038

HLR 200-specific: besides GEM software, CEM Server platform needs MDM15.1 (order separately from Enterprise)

NTJ102XX N/A TBD

R4 BICN-specific: besides GEM software, CEM Server platform needs MDM14.2 (order separately)

NTJ102XV N/A TBD

GPP-IWF (Passport 7480 -16 slot PP7400 series device) specific: besides GEM software, CEM Server platform needs MDM14.2 (order separately)

NTJ102XV TBD TBD

OMC-S/CEM Client Platform -

PC (recommended) or Sun workstation OMC-S/CEM Browser EMBN0180 (1-CD) N/A EMBNM180 (1-CD) optional: OMC-S/CEM online documentation OMAD0180 (1- CD) NTM504ADVA OMADM180 (1-CD) HLR 200-specific: besides GEM software, CEM client platform needs to have:

Data Server-specific: SMC client software SUNC0180 N/A TBD

3PC memory solution specific: SAM21 client software (included in SAM21 NCL SAM20070)

3PC memory solution specific: STORM client software (included in STORM NCL STRM0006)

USP10.0 client software (included in USP NCL USP00100)



3.8.2 GEM Billing CD-ROM Order Codes

Billing tape order codes - GSM18 NCL Order code Name Description MNCL Order code Media

GBSN0180 GOSSGBSN0180 GSM18 Billing SDM ANSI GBSNM180 CDROM

GBSW0180 GOSSGBSW0180 GSM18 Billing SDM ETSI GBSWM180 CDROM

3.8.3 Lawful Intercept interfaces

In NSS18 (GEM18) the NGT-LI INI 1 and INI 2 interfaces are supported. 3rd Party H/W vendors for the Administration and Delivery Functions are listed below.

Nortel Release

OEM Release

New H/W Function

GEM18 LIS 3.0.0 SS8 IAF The IAF (Intercept Administration Function) allows the 3rd Party equipment to target subscriber mobiles in the CS (Circuit Switched) domain for Lawful Intercept. This uses the NGT-LI INI 1 interface.

GEM18 LIS 3.0.0 SS8 DF The DF (Delivery Function) allows the 3rd Party equipment to deliver IRI (Intercept Related Information) provided by our SDM/FT to the LEA (Law Enforcement Agency). This uses the NGT-LI INI 2 interface.

GEM18 V 7.9 Verint Systems IAF The IAF (Intercept Administration Function) allows the 3rd Party equipment to target subscriber mobiles in the CS (Circuit Switched) domain for Lawful Intercept. This uses the NGT-LI INI 1 interface.

GEM18 V 7.9 Verint Systems DF The DF (Delivery Function) allows the 3rd Party equipment to deliver IRI (Intercept Related Information) provided by our SDM/FT to the LEA (Law Enforcement Agency). This uses the NGT-LI INI 2 interface.

Note: The SS8 LIS 2.0.0, LIS 2.0.1, and LIS 2.0.2 S/W releases are not supported with NSS18 (GSM18/GEM18).

3.8.4 GEM Hardware Baselines 3.8.4.1 Supernode Data Manager (SDM) SDM Hardware Baseline CPU NTRX50NB

400 MHz/512MB Processor

NTRX50NC – Note 1 9GB/9GB Disk MFIO

Storage

NTRX50ND – Note 1 4MM DAT 9GB Disk MFIO

NTRX50FS – Note 1 Lan I /F PM Mod 10baseT

NTRX50NL (optional) 36GB/36GB disks

NTRX50NM (optional) 4mm DAT/36GB disk



NTRX50NK (optional) 100/10 BaseT LAN personality module

DS512 I/F NTRX50GX Upgrade WSUP

Note 1: NOI-MD # 2004-NOD-081, dated July 6, 2004; posted at

http://eur-livelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=9300599&objAction=browse&sort=name

MDs 9GB components upon last time buy inventory consuption forecasted 12-31-04. Actual Engineering Change will not be implemented until inventory is actually consumed in the Dec04 to 1Q05 timeframe; upon which; 36GB components become baseline.

• Optional 36GB disk should be used ONLY if customer mandates additional billing file retention period. In the event of a disk hardware failure, the data transfer rate of 20 minutes per 1 GB to re-mirror 36GB disks could exceed maintenance window.

• NSS17 was the first release to support mixing of 9GB rootVG disks with 36GB dataVG disks. Mixed configurations are not supported for upgrades from a previous release. Once the SDM has been upgraded to GEM17 existing 9GB data VG disks can be upgraded to 36GB dataVG disks if required.

• Only the rootVG slot requires LAN I/F personality module. If NTRX50ND (9GB disk) is used as root VG, NTRX50FS (10baseT) is required. If NTRX50NM (36GB disk) is used as root VG, NTRX50NK (10/100BaseT) is required.

• If HLR 200 with the 3PC Memory Solution is used, a second LAN interface is required on the SDM.

• Customers with MSCs having traffic levels over 600K BHCA should migrate OMC-S from SDM/FT to CEM.

3.8.4.2 Core and Billing Manager 850 (CBM850) CBM850 replaces proprietary DS-512 fiber-optic with LAN connectivity via HIOP to MSC Core. HIOP or HCMIC Please reference HIOP/HCMIC provisioning section (1) NTRX51LA PTE2000 /COAM frame with BIP (GSM Model # NTM81311) (2) NTRX51LB CBM server (Netra240, with 4GB ram each) (GSM Model #

NTM81316 CBM850 will be Baseline for initial MSCs in NSS18. HLR does not use CBM850 until NSS19 and continues to use SDM-FT in NSS18.

3.8.4.3 SunFire V880 for Standalone CEM Server NSS18 is the last release to support Standalone CEM and OMC-s; since W-NMS becomes EMS baseline, and Standalone CEM and OMC-S will be MDed in NSS19 (NOI-MD notices were issued Dec 2003 and posted on Livelink:). http://eur-livelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=3415656&objAction=browse&sort=name Customers should begin migration plans in NSS17 and migrate to W-NMS in NSS18 CEM software has been embedded in W-NMS with no loss of functionality. Greenfield bids should use W-NMS as baseline. Reference CEM to W-NMS Migration slides on Livelink: http://eur-livelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=3415656&objAction=browse&sort=name The recommended SunFire V880 configuration for GEM18 CEM Server is:

• 4 X 900 MHz UltraSPARC III processors (8 CPU + 16 GB RAM also supported) • 8 GB memory • 6 X 73 GB disks



• 20 FB 4 mm DDS-4 internal tape • Quad Fast Ethernet (QFE) PCI Card • Redundant power supplies & cooling fan trays • Solaris 8

Customer should purchase SunFire V880 w/ Nortel’s recommended configuration directly from Sun Microsystems (http://www.sun.com/servers/entry/880/ or call 1-800-786-0404)

• for 4 CPU + 8G RAM (supports 20 MSC @ 1M BHCA) , follow quote T-US-199781 • for 8 CPU+16G RAM (supports 40 MSC @ 1M BHCA), follow quote T-US-279726 • See Product Bulletin at livelink for details http://eur-

livelink.europe.nortel.com:80/livelink/livelink.exe?func=ll&objId=3415656&objAction=browse&sort=name

Customer should purchase SunFire V880’s support and warranty from Sun (http://www.sun.com/service/support/ or call 1-800-786-0404). SDM/FT hardware should be ordered from Nortel, separately from SunFire V880

Nortel cannot guarantee CEM’s proper operation, if customer deviates from platform, recommended configuration, OS.

3.8.4.4 PC Platforms (recommended platform for OMC-S/CEM client)

Minimum requirements on the PC to run OMC-S client or CEM client are:

Minimum Recommended

Processor 650 MHz Pentium III 2.0 GHz Pentium IV

memory 384 MB 512 MB

Video card VRAM 8 MB 32 MB

Hard drive 10 GB 40 GB

• CD-ROM

• 10/100 BaseT Ethernet card/connection

• Windows NT 4.0 Service Pack 6A; Windows 2000 Service Pack 3; Windows XP

o If Data Server is used, the OMC-S or CEM client must use Windows NT4.0, Service Pack 6A

• Exceed for in-context launch of MDM (applicable to CEM management of uHLR, R4 BICN MSC, IWF)

3.8.5 Restrictions/Limitations SDMs must be split mode ready prior to GEM15 software upgrade. In NSS13 SDM configuration was changed to one disk for data (Data VG) and one disk for OS and applications (Root VG).

3.9 GEM Platforms and Upgrades 3.9.1 GEM Upgrade Strategy Supported upgrades are:

• from GEM16 to GEM18 • from GEM17 to GEM18

Customers with prior to GEM16 releases must upgrade to GEM16 first, before attempting the upgrade to GEM18.

Transition Mode Billing from SDM-FT to CBM850, allows simultaneous billing streams from SDM-FT and CBM850.



Once downstream processes are verified, the SDM-FT is decommissioned for permanent cutover to CBM850.

Both MSC and SDM-FT must be on NSS.GEM18, before cutting over to CBM850, due to CSP20 dependency – cannot upgrade directly from GEM16/17 to CBM850.

3.9.2 GEM Upgrades GEM components should be upgraded in the following order (if utilized).

Platform upgrades occur prior to software upgrades.

1. OMC-S or CEM Client 2. HLR-PS 3. Typically, SDM upgraded in the following order.

3.1. HLR SDM 3.2. MSC SDM 3.3. MSC SDM cutover to CBM850, if applicable

3.10 External MUX Support In NSS18, there is an option for two MUXes, depending on the transport. The Optera Metro 3500 (OM3500) MUX is for SONET, while the Optera Metro 4200 (OM4200) MUX is for SDH. These are Nortel recommendations but the customer can select a third party MUX if required.



4.0 Technical Documentation and Training 4.1 User Training Existing documents are updated to reflect NSS18 (GSM and UMTS) content. The course names and numbers remain as they were in previous releases where applicable.

Course Number Title UM900 UMTS Circuit Core Networks Call Server Intelligent

Networks UM920 GSM HLR200 Solution Overview UM921 GSM HLR200 Operations and Maintenance- DS,

SLR. OAM UM922 GSM HLR200 Overview and System

Maintenance- DS, SLR, HLR Memory Extension OAM

UM930 UMTS Circuit Core Networks Call Server DMS Overview

UM931 GSM NSS /UMTS UCC Overview UM935 UMTS CCN OAM HLR PS UM937 GSM /UMTS Voice Core OAM (includes W-

NMS VCN) UM955 UMTS CCN OAM SDM Maintenance UM957 GSM /UMTS VCN Billing Applications

(contains SBA & CBM) UM956 DMS XA-Core Maintenance UM961 GSM NSS18/UMTS04 VCN Delta (customized-

teachable NTPs) UM969 NSS18 Delta Release UM970 GSM/UMTS Circuit Core Networks Call Server

MSC/VLR Translations UM972 GSM/UMTS Circuit Core Networks HLR

Translations UM974 GSM/UMTS Circuit Core Networks Call Server

CCS7 Translations and Operations UM950 DMS Maintenance Part 1 UM951 DMS Maintenance Part 2 UM980 GSM Media Gateway Overview UM981 GSM Media Gateway Datafill and System

Maintenance



4.2 User Documentation

NSS18 CCN MSC / Call Server and HLR NTPs

NSS18 Nortel Technical Practices

NTP Number, Title

411-2231-001 GSM / UMTS Voice Core Network Product Documentation Directory

411-2231-010 GSM / UMTS MSC Product Guide

411-2231-011 GSM / UMTS MSC Call Intercept Product Guide

411-2231-014 GSM /UMTS R4 MSC Solution Overview

411-2231-199 GSM / UMTS MSC Software Delta

411-2231-303 GSM / UMTS One Night Process Procedures Guide

411-2231-310 GSM / UMTS MSC CCS7 Applications Guide

411-2231-330 GSM /UMTS Media Gateway Operations and Reference Guide

411-2231-331 GSM /UMTS Media Gateway Provisioning and Troubleshooting Guide

411-2231-451 GSM / UMTS MSC Customer Data Schema

411-2231-455 GSM / UMTS MSC Office Parameters Reference Manual



411-2231-510 GSM / UMTS MSC Log Reference Manual

411-2231-599 GSM / UMTS MSC PM Release Document

411-2231-809 GSM / UMTS MSC MAP Commands Reference Manual

411-2231-814 GSM / UMTS MSC Operational Measurements Reference Manual

411-2831-010 GSM / UMTS HLR100 Product Guide

411-2831-014 HLR 200 Solution Overview

411-2831-199 GSM / UMTS HLR100/200 Software Delta

411-2831-451 GSM / UMTS HLR100 Customer Data Schema

411-2831-455 GSM / UMTS HLR100 Office Parameters Reference Manual

411-2831-510 GSM / UMTS HLR100 Log Reference Manual

411-2831-809 GSM / UMTS HLR100 MAP Commands Reference Manual

411-2831-814 GSM / UMTS HLR100 Operational Measurements Reference Manual

211-2831-330 HLR200 Data Server Operations & User Guide

411-2831-331 HLR200 Mobile Subscriber Provisioning Guide

411-2831-332 HLR200 Data Model and Subscriber Validation Guide



411-2831-333 HLR200 System Maintenance, Operations and Troubleshooting Guide

GEM18 CCN OAM NTPs

411-2231-194 GEM Software Delta for Planners

411-4231-301 GSM /UMTS VCN Billing Applications OAM Manual (contains SBA & CBM)

411-4831-550 HLR PS OAM Manual

411-4831-901 GSM / UMTS Subscriber Trace OA&M Manual

411-8111-503 GSM / UMTS VCN OAM Manual

411-8111-937 GSM / UMTS VCN OAM Administration, Maintenance & Troubleshooting Guide

411-8111-803 GSM / UMTS VCN OAM Reference Manual

411-8111-233 GSM / UMTS VCN OAM Upgrades

Wireless CBM NTPs

NN-20000-244 CBM-Wireless Basics

NN-20000-246 CBM-Wireless Configuration

NN-20000-247 CBM-Wireless Accounting

NN-20000-248 CBM-Wireless Security and Administration



NN-20000-249 CBM-Wireless Performance Management

NN-20000-250 CBM-Wireless Fault Management



5.0 Annex A: Acronyms The table below provides a description of the acronyms used in this document.

Acronym Description3GPP 3rd Generation Partnership ProjectAAL ATM Adaptation LayerAC Automatic Callback

ACR Anonymous Call RejectionAGC Automatic Gain ControlAPS Audio Provisioning ServerASIC Application Specific Integrated CircuitBHCA Busy Hour Call AttemptBICC Bearer Independent Call ControlBICN Bearer Independent Core NetworkBOM Billing to OmsBR Business Readiness

BRISC BNR Reduced Instruction Set ComputingBSC Base Station ControllerBSP Bulk Service Provisioning

BSSMAP-LEBase Station Subsystem Mobile Application Part Location Services

ElementCAMEL Customised Applications of Mobile-network Enhanced Logic

CBI Channel Bus InterfaceCCN Circuit Core Network

CDMA Code Division Multiple AccessCD-ROM Compact Disc-Read-Only Memory

CDRs Call Detail RecordsCEM Core Element ManagerCFB Call Forwarding Busy

CFNRY Call Forwarding On No ReplyCFU Call Forwarding UniversalCMIC Computing Module Interface CardCNR Call Notification Record

CORBA Common Object Request Broker ArchitectureCOTS Commercial Off-The-ShelfCPU Central Processing UnitCR Change Request or Customer ReadyCS Call Server or Circuit Switched

CS1R Capability Set 1 - RefinedCSI Called Subscriber IdentificationCSP Communications System PlatformCW Call WaitingDA Device AdapterDF Delivery Function

DMS Digital Multiplex SystemEA Equal Access

ECAN Echo CancellationEIU Ethernet Interface Unit

ENET Enhanced Network



Acronym DescriptionESRD Emergency Services Routing DigitESRK Emergency Services Routing KeyFGD Feature Group DFLPP Fiberized Link Peripheral ProcessorFOC Final Operating CapabilitiesGB Giga-Bytes

GEM GSM Element ManagerGMSC Gateway Mobile Switching CenterGSM Global System for Mobile Communications

GSM-R GSM RailwaysGT Global Title

GTT Global Title TranslationHIOP High Performance Input/Output ProcessorHLR Home Location Register

HLR_PS Home Location Register-Provisioning ServerHO HandoffHST Home Subscriber TraceHW HardwareIAF Intercept Administration FunctionIAM Initial Address MessageIMEI International Mobile Equipment IdentityIMSI International Mobile Subscriber IdentityIN Intelligent Network

INAP Intelligent Network Application PartINI 1 Internal Network Interface 1 (Provisioning of targets)INI 2 Internal Network Interface 2 (Record delivery)IOC Initial Operating CapabilityIRI Intercept Related InformationIRP Interface for Remote Platforms

ISUP ISDN User Part

ITU-TInternational Telecommunication Union-Telecommunication

Standardization SectorLAC Location Area CodeLEA Law Enforcement AgencyLIU Link Interface UnitLMS Local Message Switch (LPP/FLPP)LNP Local Number PortabilityLPP Link Peripheral ProcessorLRN Local Reference NumberLU Location UpdateMB Mega-Bytes

MCC Mobile Country CodeM-CSI Mobility Management-Called Subscriber IdentificationMDM Multiservice Data ManagerMDP Management Data ProviderMEC Mobile Echo ControlMF Multi-Frequency/Mapping FunctionMG Master Group

MGW Media GatewayMMU Mobility Management UnitMNC Mobile Network CodeMPC Multi-Protocol ControllerMS Mobile Station or Message Switch



Acronym DescriptionMSC Mobile Switching Center

MSISDN Mobile Station ISDN NumberMSP Mobile Subscriber ProvisioningMTP Message Transfer PartMTZ Multiple Time Zone Nb Network bearer (interface)

NCAS Network control (interface)NCAS Non-Call-Associated SignalingNGT New Generation TelephonyNITZ Network Identity and TimeZone NIU Network Interface UnitNMS Network Management SystemNOA Nature of AddressNSP Network Service PlatformOAM Operations, Administration, MaintenanceOLI Originating Line Information

OMC-S Operations Management Center-SwitchONP One Night ProcessOSS Operations Support System

PARM ParameterPC Personal Computer

PCIProtocol Control Information/Peripheral Component

Interconnect/Programmable Communications InterfacesPCL Product Computing Module LoadPCR Passport Core ReleasePDP Packet Data Protocol

PLMN Public Land Mobile NetworkPPS Preside Performance Server

PSAP Public Safety Answering PointPSTN Public Switched Telephone NetworkPTS Per-Trunk SignalingPWI Preside Wireless InternetQFE Quad FastEthernetRAM Random Acess Memory

RESTMNC Roaming Restricted Mobile Network CodeROM Read-Only MemoryRTU Right to UseSAM Security Access ManagerSBA Supernode Billing Application

SCCP Signaling Connection Control PartSCP Service Control PointSDC Software Delivery CenterSDM Supernode Data ManagerSIM Subscriber Identification ModuleSLR Server Location Register

SMLC Serving Mobile Location CentreSNSE SuperNode Size EnhancedSOC Software Optionality ControlSRI Send Routing InformationSSP Service Switching Point



Acronym Description STP Signal Transfer Point SW Software

SWACT Switch Activity TCP Transport Control Protocol

TRAU Transcoding and Rate Adaptor Unit UL Underwriters Laboratory

UMTS Universal Mobile Telecommunications Service USP Universal Signaling Point VLR Visitor Location Register

V-MSC Visited MSC VQE Voice Quality Enhanced VSP Voice Services Processor WCD Wireless Custom Development

W-NMS Wireless Network Management System WPS Wireless Priority Service

XA-Core Extended Architecture Core XPM Extended Peripheral Module



6.0 ANNEX B: GSM18 and UMTS04 Call Models The GSM MSC capacity targets identified earlier in this document are based on the following call model.

BHCA per Subscriber 1.00 Mobile to Mobile - Voice 0.06GMSC Calls 0.20

Erlangs per Subscriber 0.025 Successful Traffic Ratio 1.00Avg Voice Successful Holding Time 90 Successful with MSRN 0.85Percentage Voice Calls 1.00 Call Forward Unconditional Successful 0.15Fax / Data 0.00 Unsuccessful Traffic Ratio 0.00Mobile to Land - Voice 0.42 Unsuccessful Calls 1.00Successful Traffic Ratio 1.00 GVMSC Calls 0.80

Answered 0.75 Successful Traffic Ratio 0.85Not Answered 0.25 Answered 0.65

Unsuccessful Traffic Ratio 0.00 Subscriber No Reply to VM 0.00Unreachable 1.00 Subscriber Busy to VM 0.00

Land to Mobile - Voice 0.30 Call Forward Busy Successful 0.11GMSC Calls 0.30 Call Forward No Reply Successful 0.24Successful Traffic Ratio 1.00 Unsuccessful Traffic Ratio 0.15

Successful with MSRN 0.85 Detached to VM 0.00Call Forward Unconditional Successful 0.15 Page Timeout to VM 0.00

Unsuccessful Traffic Ratio 0.00 Page Timeout, CFNRC Successful 0.30Unsuccessful Calls 1.00 Detached, CFNRC Successful 0.70

VMSC Calls 0.15 Land to Land - Successful 0.22Successful Traffic Ratio 0.85 Mobile to VM Retrieval - Direct 0.00

Answered 0.65 Land to VM Retrieval 0.00Subscriber No Reply to VM 0.00 Land to Mobile - Data 0.00Subscriber Busy to VM 0.00 Mobile to Land - Data 0.00Call Forward Busy Successful 0.11 Mobile to Mobile - Data 0.00Call Forward No Reply Successful 0.24

Unsuccessful Traffic Ratio 0.15 Misc. ParametersDetached to VM 0.00 Active Ratio 100%Page Timeout to VM 0.00 Authentication Frequency 5%Page Timeout, CFNRC Successful 0.30 EIR Query Frequency 0%Detached, CFNRC Successful 0.70 Send Parameters Frequency 37%

GVMSC Calls 0.55 Send ID Request (per active sub) 20%

Standard Networked MSC Call Profile

Handover Profile - per Call 1.24 Supplementary Services per Sub 0.018Intra-BSC Handovers 0.80 SS Activation 0.002Inter-BSC Handovers 0.15 SS Deactivation 0.002Inter-MSC Handovers - Incoming 0.15 SS Registration 0.002Inter-MSC Handovers - Outgoing 0.10 SS Erase 0.002Subsequent Handovers - Incoming 0.02 SS Interrogation 0.002Subsequent Handovers - Outgoing 0.02 SS Get Password Attempts 0.002Mobility Profile - Loc. Updates per Sub 1.28 SS Structured Data Request 0.002Periodic Location Update 0.56 SS Process Structured Request 0.002Intra-VLR Location Update 0.37 SS Structured Request 0.002Inter-VLR Location Update - Incoming 0.35 SMS Profile - per Sub 0.16Inter-VLR Location Update - Outgoing 0.00 MT SMS Successful 0.08Attach Subscriber 0.12 MT SMS Unsuccessful 0.03Detach Subscriber 0.08 MO SMS Successful 0.03ISD Requests 0.75 MO SMS Unsuccessful 0.02

Mobility and Services Profile per Active Sub

Handover Profile - per Call 1.24 Supplementary Services per Sub 0.018Intra-BSC Handovers 0.80 SS Activation 0.002Inter-BSC Handovers 0.15 SS Deactivation 0.002Inter-MSC Handovers - Incoming 0.15 SS Registration 0.002Inter-MSC Handovers - Outgoing 0.10 SS Erase 0.002Subsequent Handovers - Incoming 0.02 SS Interrogation 0.002Subsequent Handovers - Outgoing 0.02 SS Get Password Attempts 0.002Mobility Profile - Loc. Updates per Sub 1.28 SS Structured Data Request 0.002Periodic Location Update 0.56 SS Process Structured Request 0.002Intra-VLR Location Update 0.37 SS Structured Request 0.002Inter-VLR Location Update - Incoming 0.35 SMS Profile - per Sub 0.16Inter-VLR Location Update - Outgoing 0.00 MT SMS Successful 0.08Attach Subscriber 0.12 MT SMS Unsuccessful 0.03Detach Subscriber 0.08 MO SMS Successful 0.03ISD Requests 0.75 MO SMS Unsuccessful 0.02

Mobility and Services Profile per Active Sub



The UMTS MSC capacity targets identified earlier in this document are based on the following call model.

BHCA per sub 1.06 Mobile to Mobile - Voice 6%Percentage Voice Calls 99% GMSC Calls 20%Mobile To Land 42% Successful with MSRN 85% Successful 100% Call Forward Unconditional Successful 15% Answered 75% GVMSC Calls 80% Not Answered 25% Successful 85% Unsuccessful 0% Answered 65%Land to Mobile 30% Not Answered 35% GMSC Calls 30% Unsuccessful 15% Successful with MSRN 85% Land to Land 20% Call Forward Unconditional Successful 15% Land to VM Retrieval 2% VMSC Calls 15% Mobile to VM Retrieval 0% Successful 85% Answered 65% Not Answered 35% Unsuccessful 15% MISC - Per Sub GVMSC Calls 55% Authentication Frequency 0.05 Successful 85% EIR Query Frequency 0.00 Answered 65% TMSI Access 0.00 Not Answered 35% Send Auth Params & SAI Responses 0.37 Unsuccessful 15% Send ID & Send Params (IMSI Inquiry) Request 0.20

NUSCM v4.1 Call Profile

GSM HANDOVERS - Per Call LNP/MNP Monitoring - Per CallInter-BSC Handovers 0.00 MNP query attempts 0.00Inter-MSC Handovers - Incoming 0.00 LNP query attempts 0.00Inter-MSC Handovers - Outgoing 0.00 LNP Planning - Per CallSubsequent Incoming Handbacks 0.00 QOHR 0.00Subsequent Handovers 0.00 ML N-1% local calls 0.00

UMTS HANDOVERS - Per Call ML portable calls 0.00Intra MSC SRNS Relocation 0.18 ML ported-in calls 0.00Inter MSC HO incoming : 3G --> 3G 0.12 MM N-1% local calls 0.00Inter MSC HO incoming : 2G --> 3G 0.03 MM calls homed to switch 0.00Inter MSC HO outgoing : 3G --> 3G 0.08 MM portable calls 0.00Inter MSC HO outgoing : 3G --> 2G 0.02 MM ported-in calls 0.00

MOBILITY - Per Sub MM ported-out calls 0.00Periodic Location Updates 0.56 DR/MT % 0.00Intra-VLR Location Updates 0.37 DR/LT % 0.00Inter-VLR Location Update - Incoming 0.35 IN/CAMEL Planning - Per MO/MT CallInter-VLR Location Update - Outgoing 0.00 Virtual Private Network 0.00Attach Subscriber 0.12 Prepaid MO 0.00Detach Subscriber 0.08 Sponsored Cell and Call 0.00ISD Requests 0.75 Enhanced Sponsored Cell and Call 0.00

SMS - Per Sub Home Zone MO 0.00Mobile Terminated SMS 0.11 SMS Prepaid 0.00Mobile Originated SMS 0.05 Prepaid MT 0.00

Supplementary Services - Per Sub Home Zone MT 0.00CISS Event 0.02 Home Zone MT Ported DN 0.00

LCS - Per Call Home Zone MT MSISDN and Classic 0.00LCS penetration 0.00 NI-LR Emergency Calls 0.10 Gs Interface - Per Call Emergency call - PUSH 0.02 Intra VLR LU through Gs I/F 0.31 Emergency call - PULL 0.97 Inter-VLR Location Update through Gs I/F 0.08 Emergency call - PUSH & PULL 0.01 Attach Subscriber using IMSI through Gs I/F 0.08 MO-LR 0.00 Detach attempts through Gs I/F 0.03 MT-LR 0.90 Gs Paging Request 0.00

NUSCM v4.1 Mobility and Services

Documents

NSS18 Product Definition Document v1.3 - …willowcherry.com/wp-content/uploads/2013/12/NSS18PDD.18.01.pdfNSS18 Product Definition ... Planning Guide. The following table summarizes