411-2831-010.18.05 GSM / UMTS HLR100 Product Guidewillowcherry.com/wp-content/uploads/2013/12/411-2831-010.18.05.pdfGSM / UMTS HLR100 Product Guide ... (CCN HLR) Product Guide for

GSM / UMTS

HLR100Product Guide

GSM18 / UMTS04 Standard 18.05 April 2006

411-2831-010

test

GSM / UMTS

HLR100Product Guide

Document number: 411-2831-010Product release: GSM18 / UMTS04Document version: Standard 18.05 Date: April 2006

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright © 1993–2006 Nortel, All Rights Reserved

Printed in the United States of America

NORTEL CONFIDENTIAL

The information contained herein is the property of Nortel and is strictly confidential. Except as expressly authorized in writing by Nortel, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel, the holder is granted no rights to use the information contained herein.

Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant.

* Nortel, the Nortel logo, and the Globemark are trademarks of Nortel. DMS, DMS-HLR, DMS-MSC, MAP, and SuperNode are trademarks of Nortel.GSM is a trademark of GSM MOU Association. Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.

iiNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

iiiNortel Confidential Copyright © 1993–2006 Nortel

GSM / UMTS HLR100 Product Guide GSM18 / UMTS04

Publication historyThis publication contains a high level listing of updates and changes to this product documentation for this release cycle. If a detailed list of all changes for GSM18 release is required, see the GSM / UMTS VCN CS/HLR OAM Software Delta, NTP 411-2231-190. For any release prior to GSM17, see product documentation GSM / UMTS VCN HLR100/200 Software Delta, NTP 411-2831-199.

April 2006

GSM18/UMTS04, 18.05: Standard release

October 2005

GSM18/UMTS04, 18.04: Standard release

GSM18/UMTS04, 18.03: first Preliminary release - updated with minor editorial changes.

March 2005

GSM18/UMTS04, 18.02 Preliminary release This preliminary release has been updated from reviewer comments.

February 2005

GSM18/UMTS04, 18.02 Draft release This draft release has been updated from reviewer comments.

December 2004

GSM18/UMTS04, 18.01 Draft release 1. This draft release has been updated with 43 feature documents.

October 2004

GSM17/UMTS03, 17.09 Standard release 2.

September 2004

GSM17/UMTS03, 17.08 Standard release.

iv Publication historyNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

April 2004

GSM17/UMTS03. Preliminary Release 17.07. Up-issued this document for the 17.1 maintenance release which includes BICC functionality and incorporated CRs.

February 2004

GSM17/UMTS03. Release 17.06. This Standard release is created for Global System for Mobile Communications (GSM) users to document the GSM NSS/ UMTS UCC Product Guide for Release GSM17/UMTS03.

November 2003

GSM17/UMTS03. Release 17.05. This Preliminary release is created for Global System for Mobile Communications (GSM) users to document the GSM NSS/ UMTS UCC Product Guide for Release GSM17/UMTS03.

September 2003


September 2003


June 2003

GSM17/UMTS03. Release 17.02. This Preliminary release is created for Global System for Mobile Communications (GSM)/Universal Mobile Telecommunications System (UMTS) to document the GSM NSS/ UMTS Circuit Core Networks Home Location Register (UCC HLR) Product Guide for Release UMTS03.

April 2003

GSM17/UMTS03. Release 17.01. This Draft release is created for Global System for Mobile Communications (GSM)/Universal Mobile Telecommunications System (UMTS) to document the UMTS Circuit Core Networks Home Location Register (UCC HLR) Product Guide for Release UMTS03.

April 2003

GSM16/UMTS03. Release 16.03. This Standard release is created for Universal Mobile Telecommunications System (UMTS) to document the

Publication history vNortel Confidential Copyright © 1993–2006 Nortel


UMTS Circuit Core Networks Home Location Register (UCC HLR) Product Guide for Release UMTS03.

October 2002

GSM16/UMTS03. Release 16.02. This Preliminary release is created for Universal Mobile Telecommunications System (UMTS) to document UMTS Circuit Core Networks Home Location Register (UCC HLR) Product Guide for Release UMTS03.

July 2002

GSM16/UMTS03. Release 16.01. This Draft release is created for Universal Mobile Telecommunications System (UMTS) to document UMTS Circuit Core Networks Home Location Register (UCC HLR) Product Guide for Release UMTS03.

Significant updates in this release include introduction of Univity HLR support with the USP platform.

July 2002

GSM15/UMTS02. Release 15.03. This Standard release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release UMTS02.

April 2002

GSM15/UMTS02. Release 15.02. This preliminary release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release UMTS02.

November 2001

GSM15/UMTS02. Release 15.01. This draft release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release UMTS02.

The following functionality has been added to the HLR:

• Call Intercept support for Packet Switch (PS)

• Location Services (LCS)

• HLR mated pair Service Synchronization

• HLR One-Night Process (ONP)

• HLR Support For Multiple Point Codes

vi Publication historyNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

• HLR Send Routing Information (SRI) Location Information

• HLR Roamer Intercept Related Information (IRI)

• HLR Support for North American Equal Access Preferred Carrier Identifier

• HLR support for CAMEL Phase 3 database

• HLR Operational Measurements (OM) and tools support for CAMEL Phase 3

• HLR Any Time Interrogation (ATI), Send Routing Information (SRI), and Provide Subscriber Information (PSI) for CAMEL Phase 3

• HLR Short Message Service for CAMEL Phase 3 Subscription Information (SMS-CSI)

• HLR General Packet Radio System for CAMEL Phase 3 Subscription Information (GPRS-CSI)

• HLR Compliancy for Supplementary Service for CAMEL Phase 3 Subscription Information (SS-CSI), Originating-CAMEL Subscription Information (O-CSI), Terminating-CAMEL Subscription Information (T-CSI), and related Trigger Detection Point (TDP) Criteria

• HLR CAMEL for Translation Information Flag for CAMEL Phase 2 and Phase 3 Subscription Information (TIF-CSI) enhancements

• Follow Me (FM) for Global System for Mobile Communications-Railways (GSM-R)

• Voice Group Services (VBS) and Voice Group Call Service (VGCS) for Global System for Mobile Communications-Railways (GSM-R)

• enhanced Multi-Level Precedence and Pre-emption service (eMLPP) stage and User-to-User Signalling, Type 1 (UUS1) service for Global System for Mobile Communications-Railways (GSM-R)

• HLR mated pair Propagation for Global System for Mobile Communications (GSM-GSM-RR)

November 2001

NSS14/UMTS01—This standard 1.2 release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release NSS14/UMTS01.

October 2001

NSS14/UMTS01—This standard 1.1 release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release NSS14/UMTS01.

Publication history viiNortel Confidential Copyright © 1993–2006 Nortel


June 2001

NSS14/UMTS01—This preliminary 1.1 release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release NSS14/UMTS01.

May 2001

NSS14/UMTS01—This preliminary 1.0 release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release NSS14/UMTS01.

April 2001

NSS14/UMTS01, 01.01—This draft release is created for Universal Mobile Telecommunications System (UMTS) to document Circuit Core Networks Home Location Register (CCN HLR) Product Guide for Release UMTS01.

Information has been added about the following topics:

• UMTS Extensive Quality of Service (Ext QoS)

• UMTS Security Enhancements

• UMTS authentication algorithm with Milenage/Rijndael framework

UMTS is the 3rd-generation migration from GSM.

March 2001

GSM13, 13.04—This Standard release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM13.

March 2001

GSM13, 13.03—This Preliminary release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM13.

GSM13 introduces support for Extended Architecture Core (XA-Core) 3+1. GSM12 (full multiprocessor) supports XA-Core 1+1.

Information has been added about the following topics:

• 911 and Location Measurement Unit (LMU)

• DMS-HLR mated pair Service Synchronization support

• DMS-HLR One Night Process (ONP) support

• Upgraded HLRTRACE tool

viii Publication historyNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

• DMS-HLR Extended Architecture Core (XA-C) support

• -HLR Interface with LM Ericsson-VLR

• Short Message Server (SMS) phase 2+ operates within General Packet Radio Service (GPRS) networks

March 2001


September 2000

GSM13, 13.01—This Draft release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM12. The DMS-HLR Network Switching Subsystem chapter was updated.

July 2000

GSM12, 12.02—This Preliminary release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM12. The DMS-HLR Hardware chapter was updated to include XA-Core hardware information.

April 2000

GSM12, 12.01—This Draft release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM12.

February 2000


October 1999


August 1999

GSM10, 10.03—This Standard release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM10.

Publication history ixNortel Confidential Copyright © 1993–2006 Nortel


February 1999


September 1998


November 1998

GSM09, 09.03—This standard release is created for Global System for Mobile (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM09.

August 1998

GSM09, 09.02—This preliminary release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM09.

March 1998

GSM09, 09.01—This draft release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM09.

November 1997

GSM08, 08.02—This standard release is created for Global System for Mobile Communications (GSM) to document Digital Multiplex Systems-Home Location Register (DMS-HLR) Product Guide for Release GSM08.

August 1997

GSM08, 08.01—This Preliminary publication is updated to reflect GSM08 information. No new information was added.

April 1997

GSM08, 08.01—This Draft document is updated to include GSM08 information. Changes are as follows:

• In the “DMS-HLR functions” chapter:

— New information is added to Table 3-3, “Other Services.”

— Additional User control of Supplementary Services information is added concerning Operator Determine Barring of Conditional Call Forwarding Subscriber Management (0DBBCCFMGT)

x Publication historyNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

— Additional Data services information is added concerning V.42bis Data Compression

— Extension service support information is added

January 1997

GSM07, 07.02—This Standard document is up-issued from the Preliminary version.

October 1996

GSM07, 07.01—This Preliminary document is created to include GSM07 information.

June 1996

• GSM06, 06.02—This Standard document is created to include GSM06 information. Changes are as follows:

• Added GSM overview section to “Introduction” chapter.

• New “Network and Switching Subsystem” chapter is added.


— New information is added to Table 3-3, “Other Services”.

— New information is added to Table 3-4, “Data Services supported by DMS-HLR”.

• In the “Related documentation” chapter the related documentation lists have been updated.

• New “List of Terms” chapter is added.

December 1995

GSM05, 05.01—This Standard document is created to include GSM05 information. Changes are as follows:


— New information is added to Table 2-2, “Call Barring and Related Supplementary Services.”

— Hot Billing information is added to Table 3-3, “Other Services,” in the Supplementary Services support section.

— Data services added for GSM05 are included in Table 3-4, “Data Services supported by DMS-HLR.”

• In the “Authentication Center functions” chapter, the functionality of the Authentication Center is updated.

• The “DMS-HLR software” chapter is reorganized to reflect the GSM05 evolution from feature packages to functional groups.

Publication history xiNortel Confidential Copyright © 1993–2006 Nortel


• In the “Related documentation” chapter, Table 7-1, “Related 411-2831 product documentation,” is updated to reflect GSM05 document information.

April 1995

GSM04, 04.01—This standard release of the document is updated to include GSM04 final information. Changes are as follows:


— These four sections are added: “Call routing support,” “Inter-PLMN roaming,” “Supplementary Services support,” and “Data services support.”

— Four tables are added to expand on Supplementary Services and Data services support.

• In “DMS-HLR hardware,” descriptions of the dual shelf network (DSN) modules and the Cabinetized Dual Shelf Network (CDSN) cabinet are removed to reflect the removal of these from the GSM04 DMS-HLR product offering.

• In the “DMS-HLR software” chapter:

— The table showing DMS-HLR software categories is replaced with a graphic.

— The “Required DMS base software” section is replaced with the “DMS-100 software” section to more accurately reflect the provisioning of software on the DMS-HLR.

— Additional graphics are added to clarify software layers.

— Tables showing software packages are updated to show software made available in GSM04.

• A chapter entitled “Other DMS products for GSM” is added to introduce the DMS-Mobile-services Switching Center (DMS-MSC) and the DMS-MSC/HLR

July 1994

GSM03, 03.01 - This standard document is updated to reflect changes in software for the GSM03 load.

November 1993

GSM02A, 02.01—This preliminary document is updated to reflect the following:

• availability of DMS-HLR hardware on the DMS SuperNode SE platform

• availability of the BRISC processor in the DMS-HLR computing module

• editing revisions

xii Publication historyNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

This version of the Product Guide includes GSM02 final information and GSM02A draft information.

May 1993

GSM02, 01.01—This preliminary document is updated to reflect changes in software for the GSM02 load.

February 1993

BCS35+, Release 00.01—This preliminary document is created for Global System for Mobile Communications.

xiiiNortel Confidential Copyright © 1993–2006 Nortel


Contents 1

About this document xixAudience for this document xixOrganization of this document xixSoftware release applicability xx

GSM18/UMTS04 Product Computing Module Loads xxIndication of hypertext links xxiRelated documents xxi

VCN HLR100 hardware 1-1Chapter organization 1-1HLR cabinets 1-1

Cabinet dimensions 1-2Example HLR cabinet lineups 1-2

Common cabinets 1-4Message switch in HLR with XA-Core base 1-4Enhanced Network in HLR with XA-Core base 1-5Link Peripheral Processor 1-7Equipment common to all Home Location Registers 1-9Cabinetized Integrated Services Module Equipment 1-10Input/output equipment 1-11Cabinetized Power Distribution Center cabinet 1-12

eXtended Architecture Core 1-12Home Location Register (HLR) with eXtended Architecture Core base 1-12Home Location Register eXtended Architecture Core hardware overview 1-12HLR XA-Core platform on XA-Core base 1-15

Third-party core memory extension 1-17HLR 100 Provisioning Server 1-18

HLR100 Basic Services 2-1Teleservices 2-1

Telephony 2-1Emergency 2-1Auxiliary speech 2-1Fax 2-2Short Message Service 2-2Voice Group Services 2-2

Bearer Services 2-3Circuit Data Asynchronous 2-5

xiv ContentsNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

Circuit Data Synchronous 2-5Dual data services 2-5General Bearer Services using CDAGBS/CDSGBS 2-6V.42bis data compression 2-6

HLR Supplementary Services 3-1User control of Supplementary Services 3-1Call forwarding 3-1

Call Forward Unconditional 3-1Call Forward Busy 3-1Call Forward No Reply 3-2Call Forward Not Reachable 3-2

Call barring 3-2Barring of All Outgoing Calls 3-2Barring of Outgoing International Calls 3-2Barring of Outgoing International Call - except Home Country 3-2Barring of All Incoming Calls 3-2Barring of All Incoming Calls when Roaming 3-2

Line ID services 3-3Calling Line Identification Presentation 3-3Calling Line Identification Restriction 3-3Connected Line Identification Presentation 3-3Connected Line Identification Restriction 3-3

Call offer 3-3Call completion 3-3

Call Wait 3-3Call Hold 3-3

Multiparty services 3-4Community of interest 3-4Information transfer 3-4Charging 3-5

Advice of charge information 3-5Advice of charge charging 3-5

Call priority 3-5Wireless Priority Service 3-7

Public Land Mobile Network-specific Supplementary Services 3-8Hot billing 3-8Calling Name Display 3-8Malicious Call Trace 3-8Account Code 3-8Class of Service 3-9Local Calls Only 3-9

Extension services 3-9Anonymous Call Reject 3-9Functional addressing–Follow Me 3-9Operator Determined Barring 3-11

Outgoing flavors (Class 1) 3-11Incoming flavors (Class 2) 3-12Roaming types (Class 3) 3-12Premium-rate types (Class 4) 3-12

Contents xvNortel Confidential Copyright © 1993–2006 Nortel


Home Public Land Mobile Network-specific flavors (Class 5) 3-13CISS management (Class 6) 3-13Explicit Call Transfer types (Class 8) 3-14Conditional Call Forwarding registration (Proprietary) 3-14

HLR functionality description 4-1Roaming and regional subscription 4-1

General roaming description 4-1Regional Subscription Zone Identifier (RSZI) 4-1

Application context negotiation 4-4Call routing 4-4

SRI/PRN 4-4SRI/PSI 4-4Prepaging support 4-5

Equal access 4-6North American IS-41 PIC (V2) 4-6GSM standardized NAEA-PCI (V3) 4-7

Default call forwarding 4-7Call Independent Supplementary Services 4-8

RegSS/EraSS 4-8ActSS/DeactSS 4-8IntSS 4-8RegPwd/GetPwd 4-9

Unstructured Supplementary Services data 4-9Home Subscriber Trace 4-10

Mechanism using datafill 4-10CAMEL and IN 4-10

CAMEL screening 4-11Location services and E911 4-12

LCS privacy classes 4-13MO-LR 4-14LCS capabilities added in GSM18 4-14

Call intercept 4-15General Packet Radio Service 4-16GPRS push service support 4-16Mated Pair 4-17

Monitoring of the HLR mated pair 4-18Synchronization of subscriber data 4-18Cross Release Mating 4-19

One Night Process 4-20Dump and Restore 4-20PreSWACT 4-21SWACT 4-21AbortSWACT 4-21Fast ONP 4-21

Authentication 4-21Multiple point codes 4-22HLR-PS/HLR-PM Service Sync for NSS18 4-24

GSM18 Service Synchronization 4-25Standardized Supercharger 4-25

xvi ContentsNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

Trinode HLR Subscriber Limit 4-26VLR robustness 4-27

Introduction to UMTS 5-1UMTS Public Land Mobile Networks 5-2

UMTS PLMN services 5-2Numbering in UMTS PLMNs 5-3

Major UMTS components and interfaces 5-4User Equipment 5-5UMTS Terrestrial Radio Access Network 5-6Core Network 5-8Unified network architecture 5-8Components of the Voice Core Network 5-9Example of mobile-terminating call setup 5-13Communication among VCN components 5-14UMTS core network signaling interfaces 5-15MAP Application Entities 5-16MAP Application Service Elements 5-16UMTS core network signaling protocols 5-19

VCN HLR100 software 6-1UMTS market specific 6-3Proprietary services 6-3

SIM replacement 6-3Supplementary Services 6-3Operator services 6-3Alternate line service 6-3One night process 6-3

UMTS services 6-3Supplementary Services 6-3Short message service 6-4Data service 6-4Speech 6-4

UMTS base 6-4Call routing support 6-4Equal access support 6-5Operator determined barring 6-5Intelligent network support 6-5Inter-PLMN roaming support 6-5Subscriber database management 6-5Authentication 6-5Messaging and signaling 6-5

VCN HLR100/AuC interfaces 6-5Home location register 6-6Authentication Center 6-7

Shared layer 6-7Telecom layer 6-7Base layer 6-7

Contents xviiNortel Confidential Copyright © 1993–2006 Nortel


List of terms A-1

FiguresFigure 1-1 VCN HLR100 basic cabinets 1-2Figure 1-2 HLR cabinet lineup with XA-Core base 1-3Figure 1-3 DPCC cabinet 1-5Figure 1-4 ENET cabinet 1-6Figure 1-5 LPP interconnections 1-8Figure 1-6 Link Peripheral Processor cabinet 1-9Figure 1-7 Cabinetized Trunk Module Equipment cabinet 1-11Figure 1-8 XA-Core multiprocessor architecture with XAI midplane 1-14Figure 1-9 XA-Core cabinet layout 1-16Figure 1-10 3PC memory extension for Univity 1-17Figure 1-11 Example HLR 100 Provisioning Server Architecture 1-19Figure 3-1 USSD Message Diagram for Follow Me Registration Management 3-

11Figure 4-1 VLR area showing LACs 4-2Figure 4-2 A PLMN divided into three regional subscription zones (RSZs) 4-3Figure 4-3 Example system-level transactions in an SRI/PSI sequence 4-5Figure 4-4 Example system level transactions in an ATI/PSI sequence 4-11Figure 4-5 Simplified LCS network overview 4-13Figure 4-6 Signaling link capacity bottleneck 4-22Figure 4-7 SS7 network with VCN HLR100 MPC switch 4-24Figure 5-1 UMTS PLMN and UE, PSTN, ISDN, and other UMTS PLMN 5-2Figure 5-2 Numbers used in UMTS 5-3Figure 5-3 UMTS major components and interfaces 5-4Figure 5-4 UMTS UE components 5-5Figure 5-5 UMTS UTRAN components and interfaces 5-6Figure 5-6 Example of UMTS PLMN coverage area 5-7Figure 5-7 UMTS networking architecture 5-8Figure 5-8 Components of VCN 5-9Figure 5-9 Call Server transmission paths 5-11Figure 5-10 UMTS mobile-to-land call set-up (part 1) 5-13Figure 5-11 UMTS mobile-to-land call set-up (part 2) 5-13Figure 5-12 Application Service Element requestor and provider 5-17Figure 5-13 Communication between Application Entities 5-18Figure 6-1 VCN HLR100 Software Structure 6-2Figure 6-2 HLR/AuC 6-6

TablesTable 2-1 Data Services supported by VCN HLR100 2-4Table 5-1 UMTS signaling interfaces 5-15

xviii ContentsNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

xixNortel Confidential Copyright © 1993–2006 Nortel


About this document 1This publication introduces readers to the GSM/UMTS Voice Core Network Home Location Register 100 (VCN HLR100). It provides a basic understanding of the VCN HLR100 and integrated Authentication Center (AUC) functions, hardware and software, interfaces to other nodes, and sources of additional information about the VCN HLR100. This publication also introduces two other VCN products, the VCN Call Server (VCN CS) and the VCN CS/HLR that offers CS and HLR functions on one platform.

This publication applies to the GSM/UMTS Home Location Register 100 (GSM/UMTS HLR100). It also applies to the 3G UMTS Voice Core Networks Home Location Register 100 (VCN HLR100).

Audience for this document 1This publication is written as an introduction to the VCN HLR100, for any person involved in the planning, engineering, administration, or maintenance of a VCN HLR100.

Organization of this document 1This publication consists of the following sections:

• “VCN HLR100 hardware” describes the cabinetized system used by the VCN HLR100, and briefly describes the hardware used in the VCN HLR100.

• “HLR100 Basic Services” provides an overview of the basic services supported by the VCN HLR100.

• “HLR Supplementary Services” describes the Supplementary Services supported by the VCN HLR100.

• “HLR functionality description” provides an overview of the major functions performed by VCN HLR100 in a UMTS network.

• “Introduction to UMTS” provides an introduction to the Universal Mobile Telecommunications System.

• “VCN HLR100 software” lists and briefly describes the software required to operate the VCN HLR100.

xx About this documentNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

• Appendix A, “List of terms” provides a list of terminology used in this document.

Software release applicability 1Nortel software releases for the Wireless product are developed and identified by the product lines. The GSM product line software is identified by the letters GSM and a 2-digit number, such as GSM18, signifying the current release in the GSM software stream.

This publication is applicable to the GSM/UMTS MSC Family offices that have the GSM NSS18/UMTS VCN04 software release. Unless this publication is revised, it also applies to offices that have software releases greater than GSM NSS18/UMTS VCN04. In the GSM market, 3GPP R99 and R4 are supported in NSS18. In the UMTS market, only 3GPP R99 is supported in NSS18.

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.

For more information about the new features contained in the GSM NSS18/UMTS VCN04 software release, refer to the GSM / UMTS MSC Software Delta, 411-2231-199, and the GSM / UMTS HLR100/200 Software Delta, 411-2831-199.

GSM18/UMTS04 Product Computing Module LoadsThe NSS18 software load consists of GSM18 (MSC & HLR), GEM18 (SDM & CEM), and MG18 (Media Gateway) software.

Before GSM05, software loads were package-based loads. GSM05 was the first GSM/UMTS MSC Product Computing Module Load (PCL). PCLs are composed of layers of software, or Delivery Receivable Units (DRUs).

The following PCLs comprise the NSS18 software load:

• GSM/UMTS CSP20 (BASE21, TL20, SHR20)

• XPM20

• CBM18

• USP10.0

• SN07

• Passport v3.7• SP20 (North America market)• SP17.2 (International market)

About this document xxiNortel Confidential Copyright © 1993–2006 Nortel


• Media Gateway (MG) PCR6.1• GSM18/UMTS04 DRUs

Indication of hypertext links 1Hypertext links in this document are indicated in blue. If viewing a PDF version of this document, click on the blue text to jump to the associated section or page.

Related documents 1Some publications of the VCN family contain information that may relate to the subjects in this publication. For a current listing of VCN Nortel Technical Publications (NTPs), refer to the GSM NSS/UMTS VCN GSM / UMTS Voice Core Network Product Documentation Directory, 411-2231-001, and the GSM / UMTS MSC-100 Family Guide to Northern Telecom Publications.

xxii About this documentNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

1-1Nortel Confidential Copyright © 1993–2006 Nortel


VCN HLR100 hardware 1This chapter introduces GSM/UMTS Voice Core Network (VCN) Home Location Register 100 (HLR100) hardware. The base of GSM/UMTS VCN HLR100 hardware consists of either XA-Core or XA-Core SE, depending on the configuration. This chapter describes both options and other hardware components included with the GSM/UMTS VCN HLR100.

Chapter organization 1This chapter is organized as follows:

• HLR cabinets

• Common cabinets

— Message switch in HLR with XA-Core base

— Enhanced Network (ENET) in HLR with XA-Core base

— Equipment common to all HLRs

• XA-Core

— HLR with XA-Core base

— HLR XA-Core hardware overview

• Third-party Core (3PC) memory extension - HLR 200

• Universal Signaling Point (USP) platform) - HLR 200

— Replacement for LPP/FLPP functionality

HLR cabinets 1HLR hardware is implemented in unified steel structure cabinets. The top of the cabinet contains a Frame Supervisory Panel (FSP), which is used for alarm monitoring and reset control for power converters. The bottom of the cabinet contains the integral cooling unit (for applications that require cooling), which provides forced air ventilation for the cabinet. Inter-cabinet cabling can be routed within the Electromagnetic Interference (EMI) shield horizontally between the cabinets. The cabinets have two center-open doors in the front and back.

1-2 VCN HLR100 hardwareNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

Cabinet dimensionsAll HLR cabinets are 1829 mm (72 inches) high and support four shelves that are each 330 mm (13 inches) high and 660 mm (26 inches) deep. The cabinets are one of two different widths, depending on the cabinet:

• Dual Plane Combined Core (DPCC) and Enhanced Network (ENET) cabinets are 1067 mm (42 inches) wide.

• Cabinetized Trunk Mobile Equipment (CTME) and Cabinetized Power Distributed Center (CPDC) cabinets are 711 mm (28 inches) wide.

Figure 1-1 shows the basic layout of both cabinet sizes.

Figure 1-1VCN HLR100 basic cabinets

Example HLR cabinet lineupsFigure 1-2 shows the HLR cabinet lineup with XA-Core base.

Frame Supervisory Panel

Cooling unit

1067 mm (42 inches) 711 mm (28 inches)

(FSP)Shelf 00

Shelf 01

Shelf 02

Shelf 03

Shelf 00

Shelf 01

Shelf 02

Shelf 03

DPCC CTME

CPDC

Cabinets: Cabinets:

widewide

1829 mm (72 inches) high

ENET

VCN HLR100 hardware 1-3Nortel Confidential Copyright © 1993–2006 Nortel


Figure 1-2HLR cabinet lineup with XA-Core base

Enhanced Network(ENET) equipment

CabinetizedPowerDistribution

Dual-planecombined core(DPCC)

CabinetizedTrunk ModuleEquipment

Note: The cabinetsillustrated in thisgraphic are shown withfront panels removed,to reveal the equipment.

Center

Message Switch

Filler

XA-Core

Timeswitch

Timeswitch

Timeswitch

TimeswitchAlarmCrossConnect/OfficeAlarm

AlarmCrossConnect/OfficeAlarm

Local MessageSwitch

LIU7

LIU7

LIU7

Link PeripheralProcessor (LPP)


411-2831-010 Standard 18.05 April 2006

Common cabinets 1This section describes the common cabinets and other hardware components included with the GSM/UMTS VCN HLR100.

Message switch in HLR with XA-Core baseThe following describe the message switch:

• provides high-speed transactions that concentrate and distribute messages, allowing other system components to communicate directly with each other

• acts as a hub for communications between system peripheral modules, devices, and processors such as the core

• houses the system clocks that provide general clocking and timing functions

Message switch shelvesThe message switch occupies the top two shelves of the DPCC cabinet and consists of two message switches (MS0 and MS1). Each message switch is controlled by a Motorola 68000 series 32-bit microprocessor and occupies one shelf.

The message switch access ports are configured as DS512 fiber optic interfaces.

XA-Core uses the OC-3 optical interface card.

To further ensure reliability, each message switch is connected to each computing module plane in the Core by DS512 links. Figure 1-3 shows the DPCC cabinet.



Figure 1-3DPCC cabinet

Enhanced Network in HLR with XA-Core baseThe Enhanced Network (ENET) is a nonblocking, single-staged, matrix timeswitch. The ENET connects office alarms within the HLR, and provides access to link interface units for CCS7 (LIU7s).

Enhanced Network cabinet and shelvesThe dual-plane ENET cabinet has four shelves and terminates 64 DS512 fiber links. Each shelf receives 128K channels from external sources and transmits 128K channels to external sources. Figure 1-4 shows an ENET cabinet.

Message switchplane 0

Message switchplane 1

Computing

plane 0 plane 1

System load

Cooling unit

VCN-bus

VCN core



411-2831-010 Standard 18.05 April 2006

Figure 1-4ENET cabinet

Each ENET shelf consists of the following functional systems:

• processor and memory

• clock and messaging

• crosspoint

• transmission and interface

• power

Processor and memory The processor and memory provide operational and diagnostic control for the ENET shelf. The Central Processing Unit (CPU) card holds 16Mbyte of Random-Access Memory (RAM), which holds the operating software of the ENET. It also contains 128K of Read-Only Memory (ROM) firmware for bootloading and initialization procedures.

128K x 32K

Cooling unit

128K x 32K

128K x 32K

128K x 32K


Plane 0

Plane 1



Clock and messaging system The clock and messaging system consists of the clock and message card, which provides input/output control and the clock source for the ENET shelf. It also contains a DS512 fiber interface paddle board that provides channelized fiber links to the message switch for messaging. One of the links provides the clock source for synchronization with the message switch.

Crosspoint system The crosspoint system consists of cards that form the switching matrix. The cards are connected to other cards on the same shelf, as well as cards on other shelves in the ENET cabinet.

Transmission and interface system The transmission and interface system consists of the transmit and receive interfaces between the Peripheral Modules and the crosspoint cards of ENET. The interfaces supported are fiber (DS512) and copper (DS30).

Power system The power is provided by two +5V, 80-A power converters and two -5V, 20-A power converters. One of each type is located at each end of an ENET shelf and provides power for one-half of the shelf.

Link Peripheral Processor The Link Peripheral Processor (LPP) provides the signaling interface between the HLR and the CCS7 signaling network. The Link Peripheral Processor cabinet equipment provides the signaling link between the HLR and the VLR and CS using the CCS7 protocols, as shown in Figure 1-5. The signaling connection occurs through link interface units for CCS7 (LIU7s) in the LPP cabinet.

The following pages describe the Link Peripheral Processor cabinet and its contents, which include duplicated local message switches and link interface units (LIU7s). Figure 1-6 shows the LPP cabinet.


411-2831-010 Standard 18.05 April 2006

Figure 1-5LPP interconnections

Link Peripheral Processor shelvesFigure 1-6 shows the LPP cabinet, which contains the following components:

• The Local Message Switch (LMS) shelf consists of two LMS units and frame bus hardware. The frame bus provides connections within the Link Peripheral Processor cabinet.

• Three Link Interface Shelves (LIS) each contain up to 12 application specific units (ASUs), which are configured as link interface units for CCS7 (LIU7s). The LPP provides the following interfaces:

– DS0A

– V.35

– Channelized Network Interface Unit (NIU)

Local Message Switches are high-capacity communication hubs that control messaging among the LIU7s, and messaging between the LIU7s and the message switch. Each LIU7 is connected to each LMS by an F-bus.

The purpose of the LIU7s is to provide the physical interface between external signaling links and the internal signal processing functions of the HLR. LIU7s perform the necessary routing functions on the signaling messages, thereby relieving the Core of this function. LIU7s also process CCS7 signaling messages that arrive from other nodes in the network.

VCN core

Message switch

MTM

I/O Equip

Network

LPPVLR

CS



Figure 1-6Link Peripheral Processor cabinet

Equipment common to all Home Location RegistersThis section describes additional components:

• The Cabinetized Trunk Module Equipment (CTME) cabinet contains maintenance trunk modules configured as Office Alarm Units.

• The input/output equipment, including the Maintenance and Administration Position

• The Cabinetized Power Distribution Center (CPDC) cabinet provides direct current power distribution and protection to the other cabinets in the VCN HLR100 lineup.

Cabinetized Trunk Module EquipmentThe Cabinetized Trunk Module Equipment (CTME) cabinet holds office alarm units (OAUs) and Alarm Cross connect Unit (AXUs). Office alarm

Link interface units

Cooling unit


Localmessage

Localmessage

Link interface shelf



for CCS7


411-2831-010 Standard 18.05 April 2006

units contain alarm circuits and control circuits. Alarm cross connect units (AXUs) connect the OAU and the alarm display panel.

Cabinet and shelvesThe CTME cabinet is 711 mm (28 inches) wide and contains four shelves. The cabinet contains a combination of OAUs and AXUs.

When combined with the AXU, a primary alarm Maintenance Trunk Module (MTM) serves as an OAU, and the two create a functional pair that must be mounted together in the same cabinet. The abbreviated name for this pair of shelves is AXU/OAU. Figure 1-7 shows a CTME cabinet with two AXU/OAU pairs.

Cabinetized Integrated Services Module EquipmentCabinetized Integrated Services Module (CISME) cabinets hold items that are required for trunk testing and maintenance, tone generation, and digital recorded announcements. The CISME replaces the CTME in new installations and is downward compatible with CTME modules.



Figure 1-7Cabinetized Trunk Module Equipment cabinet

Input/output equipmentHLR input/output system acts as a communications network with the message switch as the hub. This structure relieves the control component Core of real-time intensive functions such as scanning, supervision, and digit collection. It also moves terminal-specific functions to the peripheral modules, which frees Core to deal with the higher-level functions.

HLR input/output system includes the Maintenance and Administration Position (MAP).

Maintenance and Administration PositionThe Maintenance and Administration Position (MAP) provides an interface between service provider personnel and the HLR stored data. MAP equipment communicates with HLR through a card on the input/output controller shelf (described in this section).

Cooling unit

Alarmcross connectunit (AXU)

Office alarmunit (OAU)


Alarmcross connectunit (AXU)

Office alarmunit (OAU)


411-2831-010 Standard 18.05 April 2006

Cabinetized Power Distribution Center cabinetThe Cabinetized Power Distribution Center (CPDC) cabinet provides direct current power distribution and protection to the other cabinets in the HLR lineup.

The CPDC also serves as the interface between equipment lineups and the office alarm unit, which is located in the Cabinetized Trunk Module Equipment (CTME) cabinet. The CPDC offers electromagnetic interference (EMI) compliance at the system level for all power distribution, and at the cabinet level for all input power cabling.

eXtended Architecture Core 1As with all multiprocessing systems, the key is to choose an efficient method of dividing up the work load among processors such that real gains in processing capacity can be realized. In addition, eXtended Architecture Core (XA-Core) is required to run most legacy application software without modification. The following sections describe the process in detail.

Home Location Register (HLR) with eXtended Architecture Core base HLR includes the following equipment when eXtended Architecture Core (XA-Core) is the base:

• Message switch

• Enhanced Network

• Core

Each of these equipment types are described in the following sections.

Note: Figure 1-2 shows an example HLR cabinet lineup with XA-Core as the base.

Home Location Register eXtended Architecture Core hardware overview XA-Core is designed as a next generation replacement for the computing module (CM) and System Load Module (SLM) within GSM/UMTS VCN systems. XA-Core is designed as a direct replacement for the CM/SLM and, as such, fits cleanly into the NSS/VCN architecture.

To allow a clean fit into existing NSS/VCN frames, XA-Core is incorporated into a single shelf of the same height and form-factor as existing NSS/VCN shelves. To allow circuit packs to fit into both front and rear slots, a midplane shelf design has been adopted that provides for 18 slots in the front and 14 slots in the rear.



The XA-Core is comprised of a single shelf containing the following three types of cards (referred to as packs):

• Processor Element (PE)

— RHINO

— ATLAS

• Input/Output Processor (IOP) packs

• Shared Memory (SM) packs

Together, these packs form a high-performance, multiprocessing computing engine that is completely scalable in terms of processing, memory, and I/O capability. Adjusting the capacity of the system or adding another interface is as simple as plugging in a new pack.

The operation of XA-Core is based on multiple packs (PE packs and IOP packs) operating on a single, large, shared memory system. This memory system, comprised of multiple shared memory (SM) packs and simply referred to as “shared memory,” contains all data store for XA-Core, while all program store is stored locally in cache on every processor pack.

To achieve this, XA-Core divides up the work load based on processes. When a processor becomes free, it runs the scheduler to get the next process waiting to run, and then executes it until swapped out by the scheduler.

To meet the demands that the XA-Core architecture places on inter-card connectivity, a point-to-point midplane technology called eXtended Architecture Interconnect (XAI) is employed. As shown in Figure 1-8, XAI provides individual point-to-point connections between PE packs and IOP packs via the SM packs. All transmitted links out of a PE or IOP are monitored by all SM packs, and all return links (transmit out of the SM) are monitored by all PE and IOP packs. An address field in every transaction allows each pack to determine if that transaction is destined for it or not. All links are bit-serial, gigabit links with noncontact connections at the receive ports. This allows packs to be live-inserted, and also prevents a failed receive port from potentially disabling a link that is still being shared by other packs.


411-2831-010 Standard 18.05 April 2006

Figure 1-8XA-Core multiprocessor architecture with XAI midplane

The PE pack is based on the PowerPC series of microprocessors. Instead of having two processor cards running in lock-step sync (as in XA-Core release 1), XA-Core release 2 (GSM15/UMTS02 onwards) uses a variable number of processor packs with each one executing completely independently. Fault detection on the PE pack is provided by running two processors in sync on each PE pack and matching all bus transactions. A symmetric multiprocessing architecture was chosen, meaning that there is no permanently assigned “master” PE pack. All PE packs are treated identically such that any PE pack can and does run all code. As long as at least one PE pack is operating without a fault, the system will operate.



The SM pack provides for the mutual exclusion of data necessary to allow multiple processors to execute simultaneously. This mutual exclusion is based on the concept of ownership of data. Once a PE accesses a piece of data, it owns that data until it is done with it. If a second processor attempts to access that data before it has been released by the first, the shared memory pack will send a collision notification to the second processor, telling it to terminate the data access. This blocking will cause the second processor to abort its execution and notify shared memory to return all of the data changed by the aborted task to their previous values. This is termed a process rollback. The processor then re-runs the scheduler so that it can be attempted later.

XA-Core input/output (I/O) and mass storage requirements are addressed with a generic IOP pack and a set of small daughter cards (termed packlets) that insert into the IOP pack. Each packlet provides some type of I/O or storage service, and each IOP pack can accept up to two packlets. Services are provided by population XA-Core with an appropriate number or IOP packs and, in turn, populating each IOP pack with the required packlets. The following packlets are available:

• SCSI tape (transportable mass storage)

• SCSI disk (nontransportable mass storage)

• RS-232C/422 reset terminal interface (RTIF) link

• OC-3 core to message switch interconnect (CMIC) link

Most data transfers between PE packs and IOP packs will take place via queues in shared memory. Because IOP packs do not have matched processors like PE packs do, they do not have the fault detection required to be allowed to access shared memory unchecked. To provide the necessary protection, IOP packs are only allowed to write to special areas in shared memory called staging areas. These areas are set up specifically to provide a region in which to locate queues that need to be written into by the IOP. Any IOP write access outside of these areas will be faulted. This restriction does not apply to read accesses, so IOP packs are allowed global read access to any data they may need.

HLR XA-Core platform on XA-Core base

The XA-Core cabinet contains a frame supervisory panel (FSP), two message switch shelves, one filler shelf, a standard XA-Core shelf, and a high capacity cooling unit.

Figure 1-9 shows the configuration of the XA-Core cabinet.


411-2831-010 Standard 18.05 April 2006

Figure 1-9XA-Core cabinet layout

The frame supervisory panel (FSP) performs supervisory, alarm, and maintenance functions. The FSP installs in the top shelf position of the cabinet.

The message switch shelf concentrates and distributes all internal messages flowing into and out of the XA-Core shelf.

The pair of message switches operate in load sharing mode so that either message switch can continue operating alone on a full message load without message loss or service degradation. This arrangement ensures system reliability.



Third-party core memory extension 1The HLR Memory Extension program (HMEM) increases HLR subscriber capacity as part of the HLR 200. This is achieved by augmenting the memory of the XA-Core node with the additional memory of third-party core (3PC) nodes external to the XA-Core, and distributing subscriber data across the system.

To make the transition to the memory-extended HLR as smooth as possible, existing unified interactive interfaces including Subscriber Table Control and other Command Interfaces are preserved on the XA-Core.

Figure 1-10 shows the basic organization of the 3PC Memory Extension for HLR 200. In (a) all subscriber data is in the Core’s on-board memory. In (b) subscriber data is split across multiple discrete SOS nodes connected by an IP network, realizing increased datafill capacity.

Figure 1-103PC memory extension for Univity

XA-Core XA-Core

3PC 3PC 3PC 3PC

(a) (b)


411-2831-010 Standard 18.05 April 2006

HLR 100 Provisioning Server 1The HLR 100 Provisioning Server is resident on an SDM, and uses Table Control as the HLR-Core access method. This version can connect to either a GSM16, GSM17 or GSM18 HLR-Core. See Figure 1-11.

This activity provides the following for the HLR 100 Provisioning Server variant:

• Documentation used to install, upgrade and decommission HLR 100 PS applications

• Software used to package, install, upgrade and decommission HLR 100 PS applications

• Software used to verify the success of installation and commissioning of HLR 100 PS applications and to assist with troubleshooting

• Rebranding of HLR-PS Table Control version to Nortel HLR 100 Provisioning Server.



Figure 1-11Example HLR 100 Provisioning Server Architecture

CustomerProvisioningSystems

DS

512

SDM

CEM

SDM Base

Other SDMApplications

HLR 100Provisioning

Server

HLR-Core

Telco LAN


411-2831-010 Standard 18.05 April 2006



HLR100 Basic Services 2Basic Services are services that offer a “calling facility” to the subscriber for speech, data and fax calls as well as SMS. Each basic service is associated with an MSISDN. A subscriber can be provisioned with many basic services and potentially have more than one MSISDN. Basic Services are grouped in Basic Service Groups (BSGs).

Teleservices 2A teleservice is characterized by the full set of attributes, referring to the layers 1–7 of the OSI reference model. It provides the complete capability— including terminal equipment functions—for communications between users. The following teleservices are supported:

• “Telephony”

• “Emergency”

• “Auxiliary speech”

• “Fax”

• “Short Message Service”

• “Voice Group Services”

TelephonyThe speech service Telephony is considered to be the most important service in the UMTS system. It provides the capability of basic communications between the mobile user and network, or mobile user to mobile user.

EmergencyEmergency call service provides the capability for the mobile to connect to an emergency center in the specific UMTS PLMN.

Auxiliary speechThis is also known as the Alternate Line Service. It is a proprietary service which associates a second telephony MSISDN with a subscriber for telephony calls. The two lines have separate Supplementary Service profiles and are billed separately.

2-2 HLR100 Basic ServicesNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

FaxFax3This services allows the connection of CCITT group 3 fax apparatus to and from a mobile station. Data rates for the Fax service can be up to 14.4 kbps at MAP version 3 and higher.

Alternate speech/faxThis service provides the services of speech and fax alternately within the same call controlled by the handset. Data rates for the Fax portion of the call can be up to 14.4 kbps.

Short Message ServiceShort Message Service (SMS) is a service that provides the means of sending messages of a limited size to and from user equipment. The VCN HLR100 supports Mobile-Terminated and Mobile-Originated SMS.

Note: SMS applies to the VCN HLR100 and the Third Generation Serving General Packet Radio Service (GPRS) Tunneling Protocol (GTP) Support Nodes (3G SGSN).

Short Message Mobile TerminatedFor Mobile-Terminated SMS (SMMT), the VCN HLR100 provides the Short Message Service Gateway Mobile-services Switching Center with routing information for user equipment so that a short message can be dispatched to that user equipment.

Short Message Mobile OriginatedFor Mobile-Originated SMS (SMMO), the VCN HLR100 is responsible for the provisioning and deprovisioning of the service and propagating the subscription changes to the VLR and the SGSN.

Voice Group ServicesVoice Broadcast Service (VBS) and Voice Group Call Service (VGCS) constitute the basic service group Voice Group Services (VGS).

VBS allows the distribution of speech generated by a VBS subscriber to the members of a predefined group in a geographical area that is defined in the GCR of the VLR.

VGCS allows speech conversation of a predefined group of subscribers in a geographical area. The concept of VGCS is similar to that of VBS. In addition, VGCS provides the possibility of dynamically changing the talking user.

HLR100 Basic Services 2-3Nortel Confidential Copyright © 1993–2006 Nortel


Voice Group Services (VGS) have the following functions:

• Stores data associated with VBS or VGCS used by service applications

— The Group IDs against the International Mobile Subscriber Identities (IMSIs) of the authorized VBS or VGCS subscribers

— Call initiation permission in case of roaming out-of-HPLMN on a VBS or VGCS subscriber basis

— Call initiation entitlement of a VBS subscriber regarding the authorization of each group

— Supplementary Services (SS) information of a VBS or VGCS subscriber

— The VBS or VGCS group IDs used by a VBS or VGCS subscriber roaming out of the HPLMN

• Provides up-to-date service provisioning data to the VLR through messaging

— Embedded ISD or Embedded multiple ISD

— DSD

— Standalone ISD or Standalone multiple ISD

Bearer Services 2The VCN HLR100 supports Mobile-originated and Mobile-terminated data services, that are provisioned at the VCN HLR100. VCN HLR100 supports the data services shown in Table 2-1. The User Equipment (UE) can have more than one Bearer Service or Teleservice provisioned.


411-2831-010 Standard 18.05 April 2006

Circuit Data AsynchronousThis service provides the capability to send and receive asynchronous data. This service can be provisioned as an individual speed or as a group of speeds:

• CDA300

• CDA1200

• CDA1200/75

Table 2-1Data Services supported by VCN HLR100

Bearer Service or Teleservice Group name Service name

Bearer Service Groups:

Circuit Duplex Asynchronous General Bearer Service (CDAGBS)

Data CDA 300 bpsData CDA 1200 bpsData CDA 1200/75 bpsData CDA 2400 bpsData CDA 4800 bpsData CDA 9600 bpsData CDA 14.4 Kbps

Circuit Duplex Synchronous General Bearer Service (CDSGBS)

Data CDS 1200 bpsData CDS 2400 bpsData CDS 4800 bpsData CDS 9600 bpsData CDA 14.4 Kbps

Unrestricted Digital Information (UDI) Data CDA 300 bpsData CDA 1200 bpsData CDA 2400 bpsData CDA 4800 bpsData CDA 9600 bps

Unrestricted Digital Information (UDI) Data CDS 1200 bpsData CDS 2400 bpsData CDS 4800 bpsData CDS 9600 bps

Dual data services Alternate Speech and Data

Speech followed by Data

Teleservices Group:

Speech Telephony

Emergency calls

Aux Speech

Short Messages

Aux Telephony

Mobile terminated

Mobile originated

Facsimile Automatic facsimile group 3

Alternate Speech/Fax 3

HLR100 Basic Services 2-5Nortel Confidential Copyright © 1993–2006 Nortel


• CDA2400

• CDA4800

• CDA9600

When the group is provisioned, all six individual services are sent in an ISD. When the group is deprovisioned, all six individual services are sent in a DSD.

Circuit Data SynchronousThis service provides the capability to send and receive synchronous data.This service can be provisioned as an individual speed or as a group of speeds:

• CDS1200

• CDS2400

• CDS4800

• CDS9600

When the group is provisioned, all four individual services are sent in an ISD. When the group is deprovisioned, all four individual services are sent in a DSD.

Dual data servicesThe dual data services are as follows:

• “Alternate speech data”

• “Speech followed by data”

Alternate speech dataThis service provides the capability to swap between speech and data during a call. The Alternate Speech CDA (ALTSPCDA) service belongs to the CDA BSG and the Alternate Speech CDS (ALTSPCDS) service belongs to the CDS BSG.

Speech followed by dataThis service provides a speech connection first and then at some time while the call is in progress, the user can switch to a data connection. The user cannot switch back to speech after the data portion.The Speech followed by CDA (SPCHCDA) service belongs to the CDA BSG and the Speech followed by CDS (SPCHCDS) service belongs to the CDS BSG.

General Bearer Services using CDAGBS/CDSGBSCircuit Data Asynchronous General Bearer Service (CDAGBS) and Circuit Data Synchronous General Bearer Service (CDSGBS) support transmission of data above 9.6 kbps (14.4 kbps and above) as well as providing the lower speeds (in the CDA/CDS groups above). A subscription to a General Bearer


411-2831-010 Standard 18.05 April 2006

Service comprises subscription to all individual single services of its group. These services belong to the CDA and CDS GBSs respectively. These services are mutually exclusive with the lower speed CDA and CDS group services.

V.42bis data compressionThe transfer rate of data to and from the user equipment is increased through V.42bis Data Compression. V.42bis is only applicable to nontransparent Circuit Data Asynchronous (CDA) data calls, including the CDA data phase of dual data calls. It provides VCN HLR100 support for routing of mobile terminated data calls using V.42bis data compression.

V.42bis data compression uses encoding of character oriented data to reduce the actual amount of data transferred over the air interface and thus increases the throughput of the communications link. Supporting V.42bis at the VCN HLR100 requires an enhancement to the existing mobile terminated data services functionality to support the use of higher user rates over the air interface.



HLR Supplementary Services 3The VCN HLR100 provisions, controls, and manages Supplementary Services information. All Supplementary Services are provisioned through the VCN HLR100 that stores Supplementary Services information of the User Equipment (UE), determines its applicability to calls, and manages interaction among the different Supplementary Services. The VCN HLR100 allows Supplementary Services to be provisioned against individuals International Mobile Subscriber Identities (IMSIs) and against Basic Service Groups.

User control of Supplementary Services 3The VCN HLR100 supports the UE control of some Supplementary Services. For some Supplementary Services, such as Call Barring, the VCN HLR100 requires the UE to use a password to activate or deactivate the service. The VCN HLR100 manages the password of the UE and prompts the UE to supply the password when necessary. User control of Call Waiting (CW) does not require a password for activation or deactivation.

The VCN HLR100 also supports user interrogation of Supplementary Services. This allows a UE to inquire if a Supplementary Service is provisioned and applicable.

Call forwarding 3The Call Forwarding functions have a mechanism to limit parallel Call Forwarding invocations by a subscriber at the MSC beyond a predefined limit (maximum subscriber limit of 2048).

Call Forward UnconditionalCall Forward Unconditional (CFU) forwards all incoming calls to a specified destination address regardless of the current status of the Call Forwarding Mobile Station.

Call Forward BusyCall Forward Busy (CFB) forwards incoming calls to a specified destination address when the Call Forwarding Mobile Station is busy.

3-2 HLR Supplementary ServicesNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

Call Forward No ReplyCall Forward No Reply (CFNRy) forwards an incoming call to a given destination address when the call is not answered by the Call Forwarding Mobile Station within a specified period of time.

Call Forward Not ReachableCall Forward Not Reachable (CFNRc) forwards incoming calls to a specified destination when the Call Forwarding Mobile Station is not registered, is experiencing radio congestion, or is not responding to the page.

Call barring 3The call barring functions are as follows:

• “Barring of All Outgoing Calls”

• “Barring of Outgoing International Calls”

• “Barring of Outgoing International Call - except Home Country”

• “Barring of All Incoming Calls”

• “Barring of All Incoming Calls when Roaming”

Barring of All Outgoing CallsPrevents the UE that has activated Barring of All Outgoing Calls (BAOC) from making any outgoing calls, except emergency calls.

Barring of Outgoing International CallsAllows the UE with Barring of Outgoing International Calls (BOIC) to call only subscribers of any PLMN or fixed network in the country that the user equipment with BOIC is currently roaming.

Barring of Outgoing International Call - except Home CountryAllows the UE with Barring of Outgoing International Calls - except Home Country (BOICEXHC) to internationally call only subscribers of its home PLMN country. The UE with BOIC-exHC can also call subscribers locally within the visited PLMN where it is currently roaming.

Barring of All Incoming CallsBarring of All Incoming Calls (BAIC) prevents the UE from receiving any incoming calls.

Barring of All Incoming Calls when RoamingBarring of Incoming Calls when Roaming (BAICROAM) prevents the UE from receiving any incoming calls if the UE is roaming outside of the Home PLMN country of the UE.

HLR Supplementary Services 3-3Nortel Confidential Copyright © 1993–2006 Nortel


Line ID services 3The line ID services are as follows:

• “Calling Line Identification Presentation”

• “Calling Line Identification Restriction”

• “Connected Line Identification Presentation”

• “Connected Line Identification Restriction”

Calling Line Identification PresentationCalling Line Identification Presentation (CLIP) provides the called UE with identification information about the calling party.

Calling Line Identification RestrictionCalling Line Identification Restriction (CLIR) restricts the display of identification information about the calling UE to the called party. The UE can choose to apply CLIR to all calls or only selected calls

Connected Line Identification PresentationConnected Line Identification Presentation (COLP) allows the calling party to be presented with the Connected Line Identification (CoLI) of the connected party.

Connected Line Identification RestrictionConnected Line Identification Restriction (COLR) provides the connected party the ability to block the presentation of the Connected Party Number (COPN) to the origination party.

Call offer 3Explicit Call Transfer (ECT) allows a UE to transfer an established held call to a second that is either active or ringing.

Call completion 3Call completion are as follows:

• “Call Wait”

• “Call Hold”

Call WaitCall Wait allows the UE to be notified of an incoming call (the called UE answers, rejects, or ignores) while the called UE is in the busy state.

Call HoldCall Hold allows the UE to place an active call on hold or retrieve a currently held call.


411-2831-010 Standard 18.05 April 2006

Multiparty services 3Allows the UE with MPTY Service to make up to six-way conference calls by joining a held and an active call into one conference call using a conference bridge.

Community of interest 3Closed user group (CUG) enables the UE to form a user group to and from which access is controlled. A specific user can be a member of one or more CUGs (10 CUGs maximum).

Information transfer 3User-to-user signaling, type 1 (UUS1) is a UMTS-defined Supplementary Service supported at the MAP. The UUS1 is provisioned against the International Mobile Subscriber Identity (IMSI) in table GHLRSSOP.

The UUS1 Supplementary Service allows the subscriber to send or receive a limited amount of subscriber generated information to or from another user in association with a call to the user.

The VCN HLR100 supports UUS1:

• The UUS1 Supplementary Service is activated by the service provider as a result of provisioning table GHLRSSOP. The VCN HLR100 supports provisioning for each prescribers.

• The UUS1 Supplementary Service is deactivated by the service provider as a result of removal from table GHLRSSOP. The VCN HLR100 supports the removal of UUS1 for each persubscriber.

• The VCN HLR100 supports the propagation of UUS1 service information to the Visitor Location Register (VLR):

— When the UUS1 service is added or changed for the subscriber, this information is sent in a standalone Insert Subscriber Data (ISD) message.

— If the UUS1 is deleted from the subscriber, UUS1 service information is removed from the VLR by a Delete Subscriber Data (DSD) message.

— sent during Update Location (UL) or Restore Data (RD) using ISD

• The VCN HLR100 supports the screening:

— The VCN HLR100 holds screening information concerning UUS1, against VLRs of a specific CLASS and VERSION in table GHLRNDSC. This allows the screening out of UUS1 information when the UE is at a VLR that does not support it.

— QVLR command is updated due to screening changes for UUS1.



• This activity provides subscriber database support for the following.

— Adds Supplementary Service UUS1 to the table GHLRSSOP.

— Enhance GHLRADM3 OM group to cover UUS1 functionality

• Supported tools are the HLRADMIN commands QIMSI or QMSISDN that display UUS1 SS information.

• CISS is not supported for UUS1.

Charging 3Charging services are as follows:

• “Advice of charge information”

• “Advice of charge charging”

Advice of charge information AOCI is the Supplementary Service that allows a UE to display the cost of a call in real-time.

Advice of charge chargingAOCC is the Supplementary Service that allows a UE to be charged in real-time for a call.

Call priority 3The enhanced Multi-Level Precedence and Preemption (eMLPP) Supplementary Service provides various levels of precedence for call setup and call continuity in case of handover. The UUS1 Supplementary Service provides the ability to transfer limited amounts of user-generated information between end users. These services are activated by the service provider as a result of provisioning. The provisioning information is propagated to the VLR by stand alone ISD, DSD, and embedded ISD during update Update Location (UL) or Restore Data (RD).

The administrative interface to the VCN HLR100 Database is supported through VCN Table Control. This activity extends a VCN HLR100 table and does not create a new table.

eMLPP is a UMTS-defined Supplementary Service supported at the MAP according to the UMTS 29.002 V 3.8.0. The eMLPP is provisioned against an International Mobile Subscriber Identity (IMSI). This Supplementary Service is defined by the UMTS 29.002 V 3.8.0, UMTS 03.67 V 5.1.1.

The eMLPP Service provides different call priorities in combination with fast call set-up and preemption for different applications.


411-2831-010 Standard 18.05 April 2006

The default and maximum precedence levels of a subscriber are set at the subscription time by the service provider, based on the subscribers need. The subscriber can have a precedence level up to and including the maximum precedence level subscribed to, on a per call basis.

There are 7 priority levels provisioned on the VCN HLR100. These seven priority levels are offered for subscription and can be applied globally, for example, on interswitch trunks, if supported by all related network elements, and also for interworking with ISDN MLPP service.

These seven priority levels are compliant with European Telecommunications Standards Institute (ETSI) Priority Levels.

• A—Subscription, highest

• B—Subscription

• 0—Subscription





The VCN HLR100 supports the eMLPP:

• eMLPP Supplementary Service is activated by the service provider as a result of provisioning table GHLRSSOP. The VCN HLR100 supports provisioning for each persubscriber.

• eMLPP Supplementary Service is deactivated by the service provider as a result of removal table GHLRSSOP. The VCN HLR100 supports removal of eMLPP for each persubscriber.

• VCN HLR100 supports the propagation of eMLPP service information to the VLR:

— When the eMLPP service is added to the subscriber or when the priority level is changed using table control, this information is sent using a standalone ISD.

— If the eMLPP is deleted from the subscriber, eMLPP service information is removed from using DSD.

— It is sent during Update Location (UL) or Restore Data (RD) using ISD.

• The VCN HLR100 supports the screening:

— The VCN HLR100 holds screening information concerning eMLPP, against VLRs of a specific CLASS and VERSION in table



GHLRNDSC. This allows the screening out of eMLPP information when the UE is at a VLR that does not support it.

— QVLR command is updated due to screening enhancements for eMLPP.

• CISS procedures are not supported for eMLPP.

• VCN HLR100 provides subscriber database support.

— This support adds Supplementary Service, eMLPP, with a maximum and default priority level to the table GHLRSSOP.

— Enhanced GHLRADM3 OM group to cover the eMLPP functionality

• Supported tools are the HLRADMIN commands, QIMSI or QMSISDN, that display eMLPP SS information.

Wireless Priority ServiceWireless Priority Service (WPS) is a subscription service that provides authorized users to obtain priority access to the network during call setup and maintain end-to-end priority treatment based on their subscribed priority level in situations when network congestion is blocking call attempts (for example, during a national emergency).

Subscribers wanting to use WPS must dial the WPS access code followed by the destination number. WPS provides priority access to the network but does not guarantee service.

WPS data is not processed in the HLR but is sent to the VLR as part of the ISD message. Support for WPS is provided by reusing the existing support for the Enhanced Multi Level Precedence and Priority (eMLPP) service.

WPS can be provisioned for 2G or 3G subscribers. WPS is not supported in the Packet Switched (PS) domain.

The HLR can be configured to support either WPS or eMLPP. Support for WPS or eMLPP is mutually exclusive.


411-2831-010 Standard 18.05 April 2006

Public Land Mobile Network-specific Supplementary Services 3The Public Land Mobile Network (PLMN) services are as follows:

• “Hot billing”

• “Calling Name Display”

• “Malicious Call Trace”

• “Account Code”

• “Class of Service”

• “Local Calls Only”

Hot billingHot billing provides the capability to indicate, on a per-subscriber basis, if a subscriber’s billing records are to be classified as hot. Hot-billed records are processed ahead of normal records.

Calling Name DisplayCalling Name Display (CNAM) allows the name of the calling party to be displayed on the user equipment of the terminator.

Malicious Call TraceMalicious Call Trace (MCT) provides the UE with the ability to invoke a log report of the last incoming call. Can be invoked at any point in the call and also immediately following termination of the call.

Account CodeThe Account Code functionality enables the wireless operator to provide subscribers with the Account Codes feature commonly provided by the wireline operators.

Account Code functionality can be divided into three categories.

• Account Code Voluntary (ACV)

— Account Code Voluntary feature allows subscribers to enter Account Codes of any length. Failure to enter an Account Code does not cause the call to be released.

• Verified Account Code Required (ACR)

— Subscriber must enter the Account Code of correct length. Failure to input an Account Code of correct length will cause the call to be released.

• Nonverified Account Code Required (ACR)

— Subscriber must enter the Account Code, but the exact length of the Account Code is not verified by the GSM/UMTS MSC.



The Account Code feature enables subscribers to dial a specific number (account code) in the dialing sequence. This number is captured in the billing record to be charged to different persons or accounts. This feature supports the capability of allowing the subscriber to include an Account Code before the call origination is completed. The format is as follows:

Called Number + # + Account Code

Account Code is applicable to all basic services except Emergency Calls. Account Code is provisioned and activated on a per subscriber basis and is applicable to all basic service groups.

Class of ServiceClass of Service (COS) provides Customer Group (CUSTGRP) and Network Class of Service (NCOS) classifications to the UE within a user group. These classifications allow a community of subscribers to have uniform and group-specific services.

Applications of COS include Hotline Routing and Private Numbering Plan.

Local Calls OnlyLocal Calls Only (LCO) allows the UE to call only to a specific set of local destination numbers. LCO subscribers cannot call beyond the local source area in which they are roaming.

Extension services 3Extension services allow the subscriber or Extension service pilot to associate with a group of Dialed Numbers (DNs) and/or MSISDNs representing Extension service members. When an incoming call is received for the pilot, the members are alerted either simultaneously or sequentially or in a predefined combination of the two.

Anonymous Call Reject 3ACRJ allows a subscriber to reject calls from a number having its calling line identification number presentation set to restricted. Can only be provisioned when CLIP Override is not provisioned.

Functional addressing–Follow Me 3Follow Me (FM) is the UMTS feature that allows users to call with their Functional Numbers (FN) rather than MSISDN, where FNs identify both functions and applications.


411-2831-010 Standard 18.05 April 2006

VCN HLR100 functionality for FM is to pass:

• any request relative to FM from a mobile to the FM Functional Node (FFN) with VLR with MSISDN if the subscription and functional checking are confirmed. The functional checking covers Basic Service (BS) and Class Of Registration (COR) checks.

• the result of the request back from FFN to the mobile with VLR transparently

A UE that wants to use the FM feature has to subscribe to the FM Supplementary Service (SS). No ISD and DSD messages are needed for FM SS.

This activity is based on related ETSI specifications and uses Unstructured Supplementary Service Data (USSD).

FM is a UMTS service that allows a call to be setup based on the function of the call originator and call terminator, instead of the MSISDN. FM consists of two distinct parts in a UMTS network:

• FM Registration Management (registration, deregistration, interrogation, and forced erasure)

• Call Setup

Intended usage of FM is for operators. Internal numbers and parameters are operator specific.

The FM Registration Management is performed by using USSD messaging. The responsibility is divided into two logical parts:

• Home Location Register (HLR) — As the VCN HLR100 stores all subscriber based data, all registration related requests initiated by a mobile come first to the VCN HLR100 for verification based on the subscribers subscription data. These requests come to the VCN HLR100 with the VLR, using USSD messaging.

• Follow-Me Functional Node (FFN) — If no error is encountered in the VCN HLR100, it passes the request with the MSISDN to the FFN to be processed. The FFN provides registration, deregistration, interrogation or forced erasure, based on the request type and sends the result back to the mobile with the VCN HLR100 and VLR.

See Figure 3-1 for a sample Follow-Me USSD message diagram.



Figure 3-1USSD Message Diagram for Follow Me Registration Management

For call setup, requests from the VLR are processed by the FFN that provides the VLR the MSISDN that corresponds to the FN. The VCN HLR100 is not involved in FM call setup.

Operator Determined Barring 3Operator Determined Barring (ODB) is a GSM-defined service which allows the network operator or service provider to regulate access by the subscribers to GSM services, by barring certain categories of outgoing or incoming calls or of roaming. One application of ODB might be to those subscribers who have not promptly paid their bills.

Outgoing flavors (Class 1)Outgoing ODB-flavors are mutually exclusive and consist of the following:

• Barring of all outgoing calls (ODB-BAOC). This ODB category, when provisioned and active, bars the MS from making all outgoing calls.

• Barring of all outgoing international calls (ODB-BOIC). This ODB category, when provisioned and active, bars the MS from making outgoing international calls.

• Barring of all outgoing international calls not to the home country (ODB-BOICexHC). This ODB category, when provisioned and active, bars the MS from making outgoing international calls which are not towards the Home Country.

• Barring of all outgoing calls when roaming outside the HPLMN country (ODB-BAOCROAM). This ODB category, when provisioned and active, bars the MS from making outgoing calls when roaming outside his HPLMN country.

MSC/VLR HLR FFN

PUSSR Indication

PUSSR Request

PUSSR Confirmation

PUSSR Response


411-2831-010 Standard 18.05 April 2006

The VCN HLR100 allows the use of the ODB in a Phase 1 network by allowing the following ODB-categories to be mapped to the equivalent SS barring categories:

• ODB BOIC is mapped to Supplementary Service Barring of Outgoing International Calls (SS BOIC).

• ODB BOICEXHC is mapped to Supplementary Service Barring of Outgoing International Calls Except those directed to the Home PLMN Country (SS BOICEXHC).

Mapping is done according to the screening mechanism of VCN HLR100. The screening mechanism depends on the GHLRNDSC screening table.

Incoming flavors (Class 2)Incoming ODB-flavors are mutually exclusive and consist of the following:

• Barring of all incoming calls - ODB BAIC, when provisioned, bars the subscriber from receiving any incoming calls and mobile terminated short messages.

• Barring of all incoming calls when roaming outside the HPLMN country - This ODB category, when provisioned and active, bars the MS from receiving any incoming calls and mobile terminated short messages when roaming outside his HPLMN country.

Roaming types (Class 3)The Roaming ODB-types consist of:

• Barring of Roaming Outside the HPLMN - The subscriber is barred from roaming outside of the HPLMN

• Barring of Roaming Outside the HPLMN Country - The subscriber is barred from roaming outside of the HPLMN country.

The VCN HLR100 recognizes these ODB-types as per the Roaming tables on the HLR. This ODB Class is not provisionable to the subscriber.

Premium-rate types (Class 4)When provisioned premium-rate ODB types bar the subscriber from making outgoing calls which are classified as premium rate. The following categories are supported:

• ODB of Outgoing Premium Rate Calls For Information - for example: a regional weather line.

• ODB of Outgoing Premium Rate Calls For Entertainment - for example: an astrology call up line.

Premium rate ODB restrictions at the HLR are based upon dialed digits at call forward registration. The responsibility of the VCN HLR100 is to process the



call forwarding digits at call forwarding registration time to ensure that call forwarding registration to Premium Rate numbers are denied. Barred numbers for Premium Rate categories are operator definable in the VCN HLR100.

Home Public Land Mobile Network-specific flavors (Class 5)HPLMN-specific ODB flavors are only applicable when the subscriber is located in the HPLMN. When the subscriber roams outside the HPLMN, these ODB flavors are suppressed.

The following HPLMN-specific ODB barrings are supported on the VCN HLR100:

• Operator Specific Barring Type 1




This form of ODB-barring is operator definable. The Nortel VCN HLR100 has chosen to implement ODB-HPLMN specific barring based upon dialed digits (similar to that for Premium rate ODB). HPLMN-specific ODB restrictions at the HLR are based upon dialed digits at call forward registration. The responsibility of the VCN HLR100 is to process the call forwarding digits at call forwarding registration time to ensure that call forwarding registration to chosen numbers are denied. Barred numbers for HPLMN-specific categories are operator definable in the VCN HLR100.

CISS management (Class 6)A provisioned ODB CISS, bars the MS from using CISS management operations.The VCN HLR100 handles barring of management of the following call independent Supplementary Service operations:

• activation

• deactivation

• registration

• erasure

• password registration

• interrogation

• processing unstructured SS data

ODB CISS does not affect the invocation of a currently activated Supplementary Service. Active call forwarding programs are not affected.


411-2831-010 Standard 18.05 April 2006

Explicit Call Transfer types (Class 8)Operator Determined Barring for Explicit Call Transfer (ODBECT) is a GSM-defined phase 2+ service supported at version 3. It allows the network operator or service provider to regulate access by the subscribers to ECT services, by barring certain categories of outgoing or incoming calls. The following categories are supported by the VCN HLR100:

• Barring of invocation of call transfer (BAECT-allECT-Barred).

• Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber (BCHDECT-chargeableECT-barred).

• Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country (BINTECT-internationalECT-Barred).

• Barring of invocation of call transfer where both calls are charged to the served subscriber (BDBCECT-doublyChargeableECT-Barred).

Note: BAECT, BCHDECT and BINTECT are mutually exclusive, only one of these options can be provisioned at any one time. BDBCECT, however, can be provisioned with one of the other three categories or independently.

Conditional Call Forwarding registration (Proprietary)UMTS subscribers can be configured so that they are only allowed to change or cancel unconditional call forward. It eliminates the possibility that a subscriber cancels the conditional call forward to a voice mail service. The service provider can remove the subscribers control of these services through the use of Operator Determined Barring of Conditional Call Forwarding Subscriber Management (ODBBCCFMGT).Operator Determine Barring of Conditional Call Forwarding Subscriber Management allows service providers to prohibit subscribers from erasing, deactivating, and reregistering conditional call forwarded numbers of Supplementary Services.



HLR functionality description 4This chapter introduces UMTS Voice Core Network Home Location Register 100 (VCN HLR100) functionality.

Roaming and regional subscription 4The roaming and regional subscriptions are as follows:

• “General roaming description”

• “Regional Subscription Zone Identifier (RSZI)”

General roaming descriptionVCN HLR100 supports user equipment in roaming to other Public Land Mobile Networks (PLMNs), both within and outside of the home country of the user equipment. It allows user equipment to receive incoming and place outgoing calls while outside of the home PLMN. The VCN HLR100 offers the flexibility of a Roaming Restriction mechanism that allows the VCN HLR100 operator to specify, for each subscriber, what VLR areas and PLMNs a UE can and cannot roam.

VCN HLR100 uses a Service Screening mechanism to control the level of services available to a UE. Service Screening can either prevent a UE from roaming to a PLMN that does not support particular services, or restrict particular services while the UE roams. Service Screening details are determined by the VCN HLR100 operator.

Regional Subscription Zone Identifier (RSZI)As of GSM16, NortelNortels’ HLR supports the UMTS-defined Regional Subscription service. This feature also adds support for Zone Codes (ZC) in Version 2 and Version 3 Insert Subscriber Data (ISD) and Delete Subscriber Data (DSD) MAP messages.

Previously, the UMTS operator specified the roaming entitlement of a mobile subscriber solely in terms of PLMN, national, and international roaming.

The Regional Subscription service now allows UMTS operators the capability to further refine the network service area into Regional

4-2 HLR functionality descriptionNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

Subscription Areas (RSA) and to restrict a subscriber’s roaming area to an assigned RSA.

RSAs are defined at the HLR and are associated with subscribers through the existing VCN HLR100 roaming tables. Regional Subscription information is sent to VLRs as appropriate and the VLRs are responsible for evaluating the subscribers Regional Subscription entitlement.

Regional Subscription is an optional service and does not affect the existing inter-PLMN roaming functionality of the VCN HLR100.

Regional Subscription Area (RSA)A Regional Subscription Area (RSA) is a subset of the service area of an unrestricted MS. It may be contained within a single PLMN, or may lie within the service areas of two or more PLMNs. Each RSA consists of one or more Regional Subscription Zones (RSZ). Each RSZ is contained within the service area of a PLMN.

The following diagrams show how a RSA is constructed. illustrates how a VLR is made up of one or more LACs.

Figure 4-1 shows how a PLMN made up of four VLRs can be divided up into several RSZs. Each RSZ is a collection of LACs, some comprising entire VLRs.

Figure 4-1VLR area showing LACs

Note that the same PLMN can be divided into different RSZs for different subscriber requirements, the smallest unit of an RSZ being the LAC. The Regional Subscription Zone is defined by the Regional Subscription Zone Identifier (RSZI).

HLR functionality description 4-3Nortel Confidential Copyright © 1993–2006 Nortel


Figure 4-2 shows how several RSZs can be combined to give a subscriber’s RSA. Note that the RSA illustrated in straddles two PLMNs.

Figure 4-2A PLMN divided into three regional subscription zones (RSZs)


411-2831-010 Standard 18.05 April 2006

Application context negotiation 4The VCN HLR100 supports Mobile Application Part (MAP) Application Context (AC) negotiations. Application Context negotiation allows the highest supported AC version to be used in a mixed-phase Public Land Mobile Network (PLMN).

It allows the VCN HLR100 to negotiate with another entity, such as a VLR, in a Public Land Mobile Network (PLMN) to determine the highest common version of an AC supported by both entities.

For example, when the VCN HLR100 initiates a dialog with a VLR, the VCN HLR100 sends the highest version of the AC supported by the VCN HLR100. If the VLR supports that AC version, it responds to the VCN HLR100 that the version is accepted and proceeds with the dialog.

However, if the VLR only supports a lower version, it aborts the dialog and rejects the version requested by the VCN HLR100. Optionally, the VLR indicates the version it supports as part of the abort message. The VCN HLR100 attempts to reinitiate a dialog using a lower AC version. The dialog can be repeated several times until the VCN HLR100 and the VLR have found a common AC version that they both support.

Call routing 4The types of call routing are as follows:

• “SRI/PRN”

• “SRI/PSI”

SRI/PRNWhen a MAP Version 3 SRI message with the Alerting Pattern parameter is received at the VCN HLR100, and if a PRN is invoked by the VCN HLR100, the optional parameter Alerting Pattern is passed transparently in the PRN message to the VLR.

SRI/PSIThe SRI operation is used by the GMSC to request routing information from the VCN HLR100 for a specific subscriber in a mobile terminating call.

Upon receiving an SRI request, the VCN HLR100 can respond immediately with an SRI acknowledgement or start a dialog with the subscribers VLR by sending a PSI or Provide Roaming Number (PRN) request. When a PSI/PRN is invoked, the information returned by the VLR as a PSI/PRN acknowledgement is passed to the GMSC in the SRI acknowledgement.



The response of the VCN HLR100 to a specific SRI request depends on the parameters included in that request and the subscribers subscription information.

Figure 4-3 represents a typical SRI/PSI sequence.

Figure 4-3Example system-level transactions in an SRI/PSI sequence

Prepaging supportIn a GSM mobile terminated call, the called mobile station is not paged until after the SRI/PRN procedure is completed and the Mobile Subscriber Roaming Number (MSRN) call leg is received. This results in a call path being set up through the network between the GMSC and the VMSC before the mobile station has been paged. In some circumstances, this call path can turn out to be unnecessary if the mobile station does not accept the call, for example, due to out of coverage or radio congestion. This represents an inefficient usage of network resources.

The prepaging mechanism is a means of using network resources in a more efficient manner. In this context, prepaging in GSM network refers to the case where the called mobile is paged during the SRI/PRN procedure, that is before the VMSC/VLR returns the PRN Response to the HLR. In case the paging process is unsuccessful, (for example, mobile not responding) the call attempt can be terminated before it is extended to the serving network entity.

This function provides the prepaging support in HLRs. This feature supports the prepaging Supported parameter in MAP version 3 SRI and PRN messages.

SRI (........) ;

GMSC HLR VLR

PSI (.........._____requestedInfo....);

SRI Ack (....... PSI Ack (......________subscriberInfo);________subscriberInfo);


411-2831-010 Standard 18.05 April 2006

Upon receiving an SRI message, either version 1, 2 or 3, HLR then checks for the following conditions to decide whether to perform Prepaging by adding the prepaging Supported parameter in the outgoing version 3 PRN message:

• the value of the PRE_PAGE_ON parameter

• the value of the PRE_PAGE_MODE parameter

• the presence of the prepaging Supported parameter in the incoming SRI message

• the result of the screening of the GMSC address against table GHLRGMSC

• the result of the screening of the VLR address against the value of the VLR_MODE parameter

When all the above conditions are met and V3 PRN message is supported in the VLR, the HLR sends out a V3 PRN message with the prepaging Supported parameter, regardless of the version of the incoming SRI message received from the GMSC.

This feature can be broken down into the following functional components:

• Prepaging Feature Control

• GMSC Screening

• VLR Screening

• Support of prepaging Supported flag in SRI and PRN

• Overriding of the PRN timer

To provide flexible control to customers, two parameters, PRE_PAGE_ON and PRE_PAGE_MODE, are added in table GHLRPARM to allow the customer to control the prepaging functionality.

Equal access 4The types of equal access is as follows:

• “North American IS-41 PIC (V2)”

• “GSM standardized NAEA-PCI (V3)”

North American IS-41 PIC (V2)For the North American marketplace primarily, the VCN HLR100 provides support for Equal Access. Equal Access is defined as the ability of a user to choose an Interexchange Carrier (IC/INC) for call attempts that do not terminate on their network or within a local exchange network directly connected to their network.



Major functions provided by Equal Access include the following:

• It allows the end user to select the default long distance carrier for all long distance calls.

• It allows the end user to override the presubscribed long distance carrier and to use a different long distance carrier.

• All interLATA calls (in whirling case) are subject to equal access calls.

• Interrelate calls are carried by LATA and all nonlegal calls are subject to toll calls.

GSM standardized NAEA-PCI (V3)The existing North American Equal Access (EA) is supported at the VCN HLR100 to allow support for the Preferred Carrier Identifier (PCI) parameter.

This activity does not modify the VCN HLR100 database, and Equal Access is not applicable to GPRS networks.

Support for Equal Access requirementsThe VCN HLR100 stores the NAEA PCI data for each subscriber and propagates the data to the GMSC and VLR, using MAP parameters as defined for the MAP operations ISD and SRI in UMTS specification 29.002.

After the propagation of data to the GMSC and VLR the following support information is provided.

• VCN HLR100 datafill provisions the PCI for each subscriber in table GHLREA, in field PIC

• ISD supports the propagation of the PCI to the VLR in ISD messages, both in stand-alone operation and in framed mode within an Update Locate or Restore Data sequence

• SRI supports propagation of the PCI to the GMSC in SRI Response messages. If a successful SRI response is sent, the PCI is always included if the PCI is provisioned for the subscriber

• Backward compatibility support between the PIC and PCI. The datafill in the PIC field in table GHLREA is encoded and sent by the VCN HLR100 both as a PIC and as a PCI in SRI/ISD. It is the responsibility of the receiving node (GMSC or VLR) to determine which field to use as the carrier of the subscriber.

Default call forwarding 4Default Call Forwarding (DCF) provides the capability on the VCN HLR100 so the operator can supply a default Forward-To-Number (FTN) if a subscriber has been provisioned with Conditional Call Forwarding and fails to register a number for conditional Call Forwarding Flavors (CCF) or if a CCF Forward-To-Number (FTN) is registered but not activated.


411-2831-010 Standard 18.05 April 2006

The HLR also provides the operator with a report mechanism that can be used to analyze the subscriber’s activated Call Forwarding behavior. Information is provided on the number of subscribers with Call Forward Supplementary Services provisioned as well as tracking information on the number of subscribers with an active and unsuppressed FTN.

Call Independent Supplementary Services 4A request for one of the Call Independent Supplementary Services (CISS) procedures is communicated with the VLR to the GSM/UMTS HLR100. Each of the procedures begins with a component specifying the operation requested (Register, Erase, Interrogate) and the necessary input data. The VLR inserts the IMSI and VLR numbers into the dialog portion of the message. The GSM/UMTS HLR100 supports the handling of only one CISS component in the message.

RegSS/EraSSRegistration of a Supplementary Service is the input by the subscriber or the service provider of data required for the operation of the service (for example forwarding data). Registration may imply activation, or the Supplementary Service may already be active. If the service is already active then registration involves the storage of new data (for example new forwarding data). Conversely, erasure is the deletion by the service provider or the subscriber of data stored with respect to a specific service by a previous registration. Erasure implies deactivation of the Supplementary Service. Register/Erase currently only apply to call forward services.

ActSS/DeactSSActivation of a Supplementary Service is an input by the served mobile subscriber or the service provider indicating a desire for the concerned Supplementary Service to be activated.

Deactivation of a Supplementary Service is an input by the served mobile subscriber or the service provider indicating a desire for the concerned Supplementary Service to be deactivated.

IntSSInterrogation is the request by the subscriber to the PLMN to provide information about a specific Supplementary Service. This information request takes one of the following forms:

• Status Check: the provision, registration and activation status of the specified Supplementary Service is returned.

• Data Check (not supported): this function compares the data input by the subscriber during an interrogation procedure with the information in the PLMN. The PLMN signals an appropriate indication (“check is positive” or “check is negative”).



• Data Request: data associated with the specified Supplementary Service is returned. The data request may comprise the status of the service.

RegPwd/GetPwdOn the GSM/UMTS HLR100, Call Barring services are offered to the subscriber with the subscription option of using a password to control the service. When this option is selected every action (related to that Supplementary Service), such as registration, erasure, activation or deactivation is performed by the mobile subscriber with the concurrent entry of the password.

The procedure Register Password provides the served mobile subscriber with the ability to change the password.

An embedded operation GetPassword is provided which may occur within activation or deactivation, with the object of getting the user to input their current password or in the case of password registration input new password.

Unstructured Supplementary Services data 4This feature is related to the MAP message enhancements for the following Unstructured Supplementary Service Data (USSD) messages:

• Process Unstructured Supplementary Service Request (PUSSR)—MS-Initiated USSD Requested Message

• Unstructured Supplementary Service Notify (USSN)—NW-Initiated USSD Notify Message

• Unstructured Supplementary Service Request (USSR)—NW-Initiated USSD Request Message

The VCN HLR100 sends the Mobile Subscriber ISDN (MSISDN) (or International Mobile Subscriber Identity [IMSI], depending on the datafill in the VCN HLR100) of the subscriber in the destination reference parameter when the VCN HLR100 routes the message to a third node.

The USSD enhancement provides the following for network Initiated USSD Messaging (USSR and USSN) in the VCN HLR100:

• handles the optional origination reference parameter

• receives the IMSI or MSISDN of the subscriber in the destination reference parameter for the USSN or USSR messages from a third node

VCN HLR100 sends only IMSI in destination reference parameter and no origination reference when it routes the messages to VLR. VCN HLR100 Datafill is used only to find right VLR to forward the message.


411-2831-010 Standard 18.05 April 2006

Home Subscriber Trace 4The Home Subscriber Trace (HST) monitors the effectiveness of a network, ensures all the features are operating correctly, assesses the usage of features such as call forwarding, and ensures that subscribers are not misusing the network.

The VCN HLR100 keeps a record of which subscribers have Home Subscriber Tracing activated in its database. MAP messages are used to activate and deactivate tracing at the subscribers current VLR/SGSN while they are in the HPLMN.

Mechanism using datafillThis feature allows the HLR to activate and deactivate HST at the subscriber’s current VLR as subscribers roam about within the HPLMN.

Tracing may be activated for any subscriber on the HLR, but while their location is unknown or they are not located at a VLR in the HPLMN, the HLR does not activate Home Subscriber Trace at the serving VLR.

The HLR keeps a record of which subscribers have Home Subscriber Trace activated in its database. MAP Messages are used to activate and deactivate tracing at the subscriber’s current VLR while they are in the HPLMN.

HST is considered active for a subscriber at the HLR if HST is datafilled against the IMSI in the HST table GHLRTRCE.

Home Subscriber Trace uses include monitoring the effectiveness of a new network, ensuring that all features are operating correctly, assessing the usage of features such as call forwarding, or ensuring that subscribers are not misusing the network.

Activation and deactivation of HST for a subscriber can be carried out on the HLR directly by using the GSM/UMTS Table Control Command Interface, or with a Trace Application running on the HLR’s (Supernode Data Manager) SDM or (Core and Billing Manger) CBM, which in turn communicates the details to the HLR.

In order to record occurrences of Home Subscriber Trace traffic and error conditions, the OM group HSTRACET and log GHLR682 are used.

CAMEL and IN 4CAMEL is a network feature that enables the Home Public Land Mobile Network (HPLMN) operator to offer Operator Specific Services (OSSs), not standardized by UMTS specifications, to some or all of its subscribers when roaming to a different Public Land Mobile Network (PLMN). The feature also works when the subscriber is in their own HPLMN.



In a conventional UMTS Network, a subscriber loses proprietary services when roaming outside the HPLMN network. If the switching node in the VPLMN supports CAMEL, the subscriber can communicate with the UMTS Service Control Function (gsmSCF) in the HPLMN, and proprietary services are maintained.

CAMEL call routing (ATI, PSI)The VCN HLR100 receives, processes and sends modified messages in an ATI/PSI or SRI/PSI sequence.

ATI/PSI sequenceThe ATI operation is used by the gsmSCF to request subscriber state and location information or either one separately, from the VCN HLR100 at any desired time. Upon receiving an ATI request, the VCN HLR100 passes the content of the requested information to the subscribers current VLR by generating a PSI request. The information returned by the VLR in the PSI acknowledgement is passed to the gsmSCF as an ATI acknowledgement.

Figure 4-4 represents a typical ATI/PSI sequence.

Figure 4-4Example system level transactions in an ATI/PSI sequence

CAMEL screeningThe HLR informs the Visitor Location Register (VLR) of the subscriber’s CAMEL services by including the CAMEL Subscription Information (CSI) when sending an Insert Subscriber Data Message (ISD) to the VLR. An ISD

ATI (........

gsmSCF HLR VLR

PSI (.........._____requestedInfo....);

ATI Ack (.......

____requestedInfo);

________SubscriberInfo);PSI Ack (......________subscriberInfo);


411-2831-010 Standard 18.05 April 2006

message is either sent standalone, or during the Update Location (UL) and Restore Data (RD) procedure or standalone.

The HLR supports screening of all CAMEL services to a single VLR or range of VLRs. In GSM18, support has been added for screening specific Originating CAMEL Subscription Information (O-CSI) service keys for specific CAMEL phases on a per node basis in the ISD message. This allows operators to provide O-CSI services in the HPLMN only, or the ability to roll-out services gradually following integration testing with roaming partners.

Location services and E911 4This feature provides the enhancements required at the VCN HLR100 to allow it to support Location Services (LCS):

• storage of LCS subscription information for each subscriber

• storage of LCS system data

• sending of location services information in ISD messages to the VLR

• support for the Send-Routing-information-for-LCS (SRL) MAP message

LCS subscription is supported for both 2G and 3G subscribers. Location Services are services that are dependent upon the subscribers location, the subscribers UE to be more precise.

There are four categories of location services:

• Commercial LCS (or value added services) — This category is associated with an application that provides a value added service having knowledge of the subscribers location.

• Internal LCS (or PLMN LCS services) — This will enhance or support certain Operation & Measurement (O&M) related tasks, Supplementary Services, Intelligent network (IN) related services, and UMTS bearer & teleservices.

• Emergency Services LCS — This is used to provide emergency services the location of the subscriber to assist them in locating the caller.

• Lawful Intercept LCS — This uses location information to support various legally required services.

Location Services require additional nodes within the network, refer to figure Figure 4-5.

The LC interface links the Gateway Mobile Location Center (GMLC) to the LCS client. The LCS client is responsible for making location information requests to the GMLC that subsequently requests routing information from the VCN HLR100 of the targeted subscriber if required.



The Lh interface links the VCN HLR100 to the GMLC. The GMLC requests routing information for the targeted subscriber from the VCN HLR100.

Figure 4-5Simplified LCS network overview

LCS privacy classesThe VCN HLR100 stores an LCS subscription that can consist of Privacy or Mobile Originating Location options or both.

The subscribers privacy options in the subscribers privacy profile apply to Mobile Terminating Location Request (MT-LR) and Network Induced Location Requests (NI-LR) and either indicate that no location requests are allowed or define the particular classes of LCS clients for which location requests are allowed.

MT-LR refers to location requests being made by an LCS client. NI-LR refers to location requests that are requested by the network.

VLR/MSC gsmSCF

HLR

Gateway MLC

External LCS Client

Lc

Lh

Lg

Le


411-2831-010 Standard 18.05 April 2006

The privacy classes are:

• Universal class—All LCS clients are allowed to request the subscribers location.

• Call related class—When a subscriber originates a call to an LCS client, the client can request the subscribers location, providing the call is still established.

• Call unrelated class—Identified LCS clients or groups of LCS clients in the UEs privacy profile are able to request the subscribers location. LCS Clients/groups of LCS clients that are not identified are subject to the options in the privacy profile.

• PLMN Operator class—Allows positioning by specific types of clients indicated in the subscribers privacy profile.

MO-LRTo allow the subscriber to make Mobile Originating-Location Requests (MO-LR), the subscriber must subscribe to the correct type of mobile originating class. The mobile originating location class types are:

• Basic Self Location—The subscriber needs to interact with the network for each location request.

• Autonomous Self Location—The subscriber does not need interact with the network for each location request. A single interaction enables the subscriber to obtain multiple-location positions during a predetermined period of time.

• Transfer to Third Party—The subscribers location is transferred to another LCS client.

LCS capabilities added in GSM18In GSM18, the Location Services (LCS) support by the HLR is compliant with Release 4 LCS as described in documents listed below.

• 3GPP TS 22.071 V4.5.1 Location Services (LCS) Stage 1

• 3GPP TS 22.071 V4.5.10.0 Functional Stage 2 description of LCS

• 3GPP TS 29.002 V4.13.0 Mobile Application Part (MAP)

The ISD message on the MAP D interface between the HLR and VLR has been enhanced so it can accept the LCS SS codes under both the following:

• ProvisionedSS IE

• Within the LCS IE that is either of LCS Privacy Exception List and MO-LR List IE

If no LCS SOC is active, then the MSC returns the LCS as unsupported to the HLR.



Call intercept 4Call Intercept support capabilities on the VCN HLR100 are implemented in accordance with the Communications Assistance for Law Enforcements Agencies (CALEA) act.

This functionality is only available and applicable in the North American market Region.

Call Intercept System (CIS) is the Nortel term for the components that specifically provide national security agencies or the service provider (on request from a security agency) to monitor and intercept calls involving target UEs.

The CIS allows the security agency or the service provider (on behalf of the security agency) the ability to provision targeted subscribers for call interception. Every call (either originating from or terminating to) this target subscriber and every noncall mobility event is intercepted by the VCN CS or VCN HLR100 and sent to the Monitoring Center.

The Monitoring Center is the site of the monitoring and/or recording equipment. The Monitoring Center has separate connections for the reception of Call Contents and Call Associated or Non-Call Associated Data. The Monitoring Center is not provided by Nortel.

For call related events, both the call content and the call associated data can be sent to the Monitoring Center. Call Data Records can contain both Call Associated Data and Non Call Associated Data. Call associated data can contain information about a particular event associated with the monitored call. Non Call Associated Data, such as Location Updates, containing information about the event(s), are sent to the Monitoring Center.

CDRs are sent to the Monitoring Center from the VCN CS and the VCN HLR100 with the SuperNode Data Manager (SDM)/Fault Tolerant (FT) or Core and Billing Manager 850 (CBM850) over TCP/IP. The SDM/FT or CBM850 serves as a Mediation Device (MD) between the HLRs or CSs and the provisioning center. The SDM/FT or CBM850 serves as a dedicated multiapplication Operations, Administration & Maintenance (OA&M) processing front end to the VCN, providing capability to support advanced OA&M applications

The role of the VCN HLR100 in the Call Intercept process is to generate proprietary Roaming Call Notification Records (CNRs) for targeted subscribers who perform location updates while inside the HPLMN or when roaming outside the HPLMN. Each CNR is sent to the SDM/FT or CBM850 that formats the information into the CDR format and sends the information to the Monitoring Center.


411-2831-010 Standard 18.05 April 2006

General Packet Radio Service 4The Extensible Quality of Service (Ext-QoS) is a set of parameters provisioned at the VCN HLR100 in accordance with Packet Data Protocol (PDP) context and provided to the Serving General Packet Radio Service (GPRS) Support Node (SGSN) through the Insert Subscriber Data (ISD) message PDP.

This Ext-QoS data is mandatory for UMTS Third Generation (3G) subscribers and optional for 2G subscribers.

The Update GPRS Location (UGL) message, sent from the SGSN to the VCN HLR100, includes an optional parameter, gprsEnhancementSupportIndicator, that indicates if the SGSN supports Ext-QoS. If this parameter is received, the Ext-QoS data is sent as part of the PDP contexts when Ext-QoS exists for the subscribed PDP.

The PDP charging characteristic data is stored as part of the PDP context and sent to the SGSN as part of the ISD message. The possible charging characteristic values are as follows:

• Normal charging

• Prepaid charging

• Charging by hot billing

• Flat rate charging

The maximum number of PDPs of each subscriber is 20.

GPRS push service support 4The HLR allows the operator to offer push services that require the support of network initiated Packet Data Protocol (PDP) context activation capability.

Having an ability to initiate or push data to the mobile subscriber by the wireless network allows the operator to provide information services such as the following:

• Traffic reports

• Stock market information

• Airline departure/arrival status

• Customized advertisements

GPRS is a packet radio access technique that allows the subscriber to send and receive data in an end-to-end packet transfer mode, without utilizing network resources in a circuit-switched mode. It provides access to external Packet Data Networks (PDNs), for example to the Internet.



GPRS Support Nodes (GSN) contain functionality required to support GPRS. GPRS is logically implemented on the GSM structure through the addition of network nodes:

• The Gateway GPRS Support Node (GGSN)

• The Serving GPRS Support Node (SGSN)

The GGSN is the node that is accessed by the Packet Data Network (PDN) to evaluate the Packet Data Protocol (PDP) address. It contains routing information for attached GPRS users.The routing information is used to tunnel Packet Data Units (PDUs) to the Mobile Stations (MS) current point of attachment, that is the SGSN. The GGSN requests location and subscriber service information from the HLR using the Gc interface to operate these services.

Mated Pair 4The VCN HLR100 is a critical component in the UMTS network. As the capacity of the VCN HLR100 product has steadily increased, increasing number of subscribers are now serviced by a single VCN HLR100. This means that the consequences of nodal failures have become more severe.

During a disaster, a total VCN HLR100 failure results in the following:

• loss of all incoming service

• inability to change location

• inability to join network or provide authentication

• inability of subscriber to change subscription information from the handset

• inability to change subscribers services or data at the VCN HLR100

All services, except that of being able to make an outgoing call while remaining at the current VLR is curtailed.

To protect against a disaster that has a major impact to the entire network where a VCN HLR100 is lost, the mated pair functionality is introduced. This allows two geographically separate VCN HLR100s to provide a mutual standby capability.

To provide redundancy, a copy of the subscriber database normally held on a single VCN HLR100 is held on two VCN HLR100s that are connected as a mated pair.

Each of the mated VCN HLR100s are acting as a real-time back-up for the other. In the event of a disaster, the surviving VCN HLR100 has the subscriber data required to take over with minimal loss of service to the network.


411-2831-010 Standard 18.05 April 2006

Mated pair functionality introduces a concept of having a subscriber that is acting on one VCN HLR100 and the same subscriber that is Standby on the other VCN HLR100.

• Acting—these are subscribers that the VCN HLR100 normally provides service to

• Standby—these are subscribers that the VCN HLR100 acts as a backup for. This VCN HLR100 provides service only to standby subscribers in the event of a disaster occurring to its mate VCN HLR100.

In the event of a disaster, the surviving VCN HLR100 treats all its subscribers as acting.

Monitoring of the HLR mated pairHLR mated pair capability ensures that new HLR and DS functionality introduced in the NSS18 release is monitored appropriately.

This covers a variety of OAM changes and enhancements primarily done in response to the HLR and Data Server development and platform changes in NSS18.

Enhancements to the CEM software for the NSS18 allows the operator to have more information about the mated pair relationship.

• There are additional attributes that can be seen on the CEM GUI related to mated pair functionality.

• There is also additional alarms to indicate problems with the mated pair.

In GSM18, a small number of HLR logs are not mapped to the CEM because they are frequently repeated. These repeated logs have been replaced with HLR alarms so that this information can be propagated to the CEM.

Synchronization of subscriber data

When changes to Acting subscribers are made either to the Profile or Location Data, then those changes must also be applied to the Standby subscriber data to maintain synchronization of the databases. The events which trigger the propagation of these changes are as follows:

• Table Control (TC) changes

• Call Independent Supplementary Services (CISS) operations

• Maintenance and Administration Procedures (MAP) operations

The Standby subscriber’s database in the mate HLR is updated as soon as possible after the updates occur in the Acting database. The behavior is symmetrical across the HLR mated pair.



On notification that a change has occurred, a procedure is called to retrieve the changed subscriber data from the database. Once the data has been retrieved it is then packed and transported to the mate HLR. On arrival, the data is unpacked and checked for its validity.

Each release, when any subscriber data is created, modified or deleted, the mated pair service synchronization protocol requires updating to send the data from the Active HLR to the Standby HLR.

For NSS18, the following features impact imsi_based tables and/or subscriber data requiring that the data is synchronized between the Active and Standby HLRs for the following enhancements:

• HLR Location Services R4 compliance

• HLR Standardized Supercharger

• HLR Gc Support

• HLR CAMEL Service Key per Phase Screening

• HLR Subscriber Category Enhancements

Cross Release MatingThe Cross Release Mating (XRM) capability supports a Mated Pair configuration between an NSS18 HLR and an NSS17 HLR. The following Mated Pair functions continue to be available during a Mated Pair software upgrade:

• Synchronization of subscriber profile and location data changes

• Subscriber handover between nodes of an HLR Mated Pair during a Mated pair upgrade

• Single 3PC recovery for HLRs that include 3PC memory extension cards in the configuration

Synchronization of subscriber dataThe NSS18 HLR sends mating data in the NSS17 format when talking to its mate and receives data in the NSS17 format from its mate on NSS17. The XRM conversion occurs on the NSS18 HLR.

Note: Subscriber data fields that have been added, removed or changed between NSS17 and NSS18 are set to default values by the NSS18 HLR.

XRM activationXRM functionality is controlled by the Release field in the Standby tuple in table GHLRPARM. Setting this field to NSS17 causes an NSS18 HLR to use NSS17 as the effective release for sending and receiving Mated Pair messages.


411-2831-010 Standard 18.05 April 2006

One Night Process 4The One Night Process (ONP) is a process used during a software upgrade to transfer all the data from the old release to the new release.

The following ONPs are supported for GSM18 on the XA-Core node:

• GSM16 -> GSM18 (performed using standard GSM/UMTS XA-Core upgrade procedures)

• GSM17 -> GSM18

• GSM18 -> GSM18

• GSM18 LIMITED PRESWACT

The ONP executes during the following phases:

• Dump and Restore

• PreSwitch of Activity (PreSWACT)

• Switch of Activity (SWACT)

• AbortSwitch of Activity (AbortSWACT)

Dump and RestoreThe dump and restore is the process that transfers all the data in the database from the old software release to the new software release. There are two types of data moves:

• External Data Move (EDM)

• Physical Data Move (PDM)

An EDM involves every tuple in a table being read from the dump side and added to the table on the restore side. Every tuple goes through the standard table control ADD operation including all the data integrity validations.

CAUTIONVCN HLR100 does not guarantee integrity of the data

VCN HLR100 does not guarantee integrity of the data in the database if the table control operations ADD, CHANGE, REPLACE, or DELETE are used or if provisioning is running between the data move and synching of the VCN HLR100. The effect of performing any provisioning operation (for example, the creation of subs using table control) during an ONP leads to unpredictable behavior.



In a PDM method, the physical data is transferred directly to the other side and reformatted as it is written to the physical database instead of transferring every tuple individually and passing the tuple through the table control validations.

EDM is used for transferring all VCN HLR100 tables except the subscriber tables. For subscriber tables, PDM is the only supported method.

PreSWACTThe PreSWACT and the Limited PreSWACT (the latter is performed only in case of hardware upgrade) prepare the switch for the SWACT and transfer any NTD and TTD data that has changed since the start of the Dump and Restore to the restore side.

SWACTSWACT switches control to the restore side of the switch that becomes the active side, and the dump side becomes the inactive side. The SWACT process transfers any remaining changes to the NTD and the TTD data.

AbortSWACTAbortSWACT performs another SWACT to go back to the dump side and uses the old version again if something has gone wrong during the ONP. AbortSWACT transfers any NTD and TTD changes that have occurred since the SWACT back from the restore side to the dump side.

Fast ONPBeginning in GSM18, the HLR Fast ONP capability allows the XA-Core HLR to increase the rate at which physical table data is transferred during PreSWACT from the Dump side to the Restore side. Due to the mechanism used to support this capability, speed gains are only seen on core (XA-Core) ONPs. 3PC ONPs do not have this feature.

HLR Fast ONP functionality is supported in the GSM16 and GSM17 releases through software updates.

Authentication 4The Authentication Center (AuC) generates the authentication and ciphering vectors, SRes and Kc, by using the following instances of the A3/A8 algorithm:

• COMP-128

• COMP-128-2

• COMP-128-3

• CAVE38


411-2831-010 Standard 18.05 April 2006

The algorithm is invoked by the GSM/UMTS HLR100 Authentication Center upon request for authentication information (SAI).

Multiple point codes 4UMTS VCN HLR100 supports Multiple Point Code (MPC) on the VCN HLR100 platform: this support allows easier deployment within Signaling Transfer Point (STP) based CCS7 networks, where all network traffic for the VCN HLR100 is funneled through STP nodes. A discussion is presented to illustrate traffic distribution methods and monitoring tools to provide load balancing. This area is essential for the network operator to optimize the increase in capacity provided by the introduction of Multiple Network Appearances.

Multiple Point Code is supported on the UMTS VCN HLR100:

• Network configurations and load balancing

• Multiple VCN HLR100 number data entry

• Effects of having multiple VCN HLR100 numbers on the VCN HLR100 number selection (network layer)

• Log reports & Operational Measurements (OMs)

Since the VCN HLR100 is a central point in the UMTS network, it must process a large number of CCS7 messages. The CCS7 standards (both ANSI and ITU) define a limit to the number of signaling links between two nodes. In a STP based signaling network, this restriction effectively imposes a capacity bottleneck between the VCN HLR100 and the STP. Refer to Figure 4-6.

Figure 4-6Signaling link capacity bottleneck

STP STP

HLR

Capacity Bottleneck



There are various ways of addressing the signaling link capacity problem:

• Signaling network engineering has a direct connection to high capacity nodes

• Use additional linksets between the VCN HLR100 and STP network:

— Multiple STP pairs

— Multiple point codes on STP

— Multiple point codes on VCN HLR100

• Hardware uses high speed links

The VCN HLR100 Multiple Point Code (MPC) feature allows for multiple point codes on the VCN HLR100, resolving an existing link capacity problem. The feature introduces a VCN HLR100 node with multiple SS7 node capability. With this capability, one physical VCN HLR100 node can be datafilled to appear as several CCS7 nodes. Each of these nodes has its own unique point code, routesets, linksets, and links. Essentially, the several CCS7 nodes residing on the physical VCN HLR100 appear as unique Network Appearances to the network.

The following activities made the CCS7 code in the UMTS layer MPC compatible:

• Umbrella Support for MPC

• SCCP Support for MPC

• MTP Support for MPC

• UMTS support for MPC on CS

Figure 4-7 depicts an SS7 network that contains a VCN HLR100 with MPC capability. In these networks, the point codes of each logical node are indicated.


411-2831-010 Standard 18.05 April 2006

Figure 4-7SS7 network with VCN HLR100 MPC switch

An advantage of using MPC on the VCN HLR100 is that it retains existing network architecture as it resolves the link capacity issue. A disadvantage concerns the load sharing development required on VCN HLR100 to optimize the increase in capacity.

HLR-PS/HLR-PM Service Sync for NSS18 4This feature adds the following new functionality for the HLR Provisioning Server (HLR-PS) and the HLR Provisioning Manager (HLR-PM):

• support for MSP v14

• GSM18 service synchronization including provisioning support

— Location Services (LCS) enhancements

— subscriber Category (CAT) enhancements

This activity provides support for GSM18 functionality.

HLR-PS refers to the provisioning capabilities in a stand-alone configuration.

PC=112 PC=111 PC=211 PC=212

STP STP

HLR

MSC/VLR SGSN

Multiple pointcodes at HLR

CCS7 networknodes:MSCVLRSGSNSTP



GSM18 Service SynchronizationA new subscriber table GHLCSECL is added in GSM18 to store up to 40 external LCS clients for the subscriber’s Call/Session Related LCS Privacy Class and up to 35 external LCS clients for the subscriber’s Call/Session Unrelated LCS Privacy Class. For this purpose, three new MSP commands must be introduced. The enhancements will affect the existing LCS command and the changes are as follows:

• CSRECL command allows an operator to provision up to 5 external LCS clients for the subscriber’s Call Related LCS class.

• CSRXECL command allows the operator to provision up to 35 extended external LCS clients for the subscriber’s Call Related LCS class.

• CSUXECL command allows the operator to provision up to 35 extended external LCS clients for the subscriber’s Call Unrelated LCS class.

Also, the CLLRLTD (Call Related Class) field in table GHLRLCS has been enhanced with the addition of the new option LOC_NOT_ALLOW for LCS clients that are not in the subscriber’s external LCS client list. All the remaining data stored within this table remains unchanged.

Note: Addition, deletion, modification and display functions for this data are provided in MSP version 14.

Standardized Supercharger 4The philosophy of the Standardized Supercharger is that the subscriber data does not change as often as the location data, hence it needs only to be sent if it changes. This means that subscribers’ data can be kept in a serving node even after the subscriber has moved location to another serving node. Each serving node (VLR or SGSN) contains data for subscribers who are located as follows:

• Currently located in the serving node

• Not currently located in the serving node but were current at some point in time

Subscriber data integrity is maintained by ensuring that when there is a change to a particular subscriber’s data, each serving node that has an old version of the subscriber’s data receives the latest copy of that subscriber’s data. Apart from the current serving node, all other serving nodes which hold a particular subscriber’s data only get the latest copy when the subscriber next returns at that serving node. The current serving node always receives the latest copy of a subscriber data when a change occurs.

Thus, when a subscriber roams to a serving node which already has that subscriber data, the HLR sends embedded ISD messages as part of the Inter Serving Node Update Location (UL or UGL) request if that subscriber data has changed.


411-2831-010 Standard 18.05 April 2006

The consistency of the data between the serving node and the HLR is maintained using a parameter called Age Indicator:

• The Age Indicator parameters are stored at the HLR persubscriber and describe the age of the subscriber data.

• Each time a modification to the subscriber data occurs, this parameter is incremented.

• The serving node receives the age indicator within the ISD message and includes it in each subsequent UL/UGL to the HLR.

• The HLR compares the age indicator received in the UL/UGL with the one stored, and then knows whether the subscriber data stored at the serving node is up-to-date or not, and therefore, whether the embedded ISD/s messages are required.

Holding a particular subscriber’s data in multiple serving nodes in the network, means that the HLR does not need to send Insert Subscriber Data (ISD) messages when the subscriber roams to one of these serving nodes (provided that the data has not changed in the HLR). Thus, an interserving node UL/UGL request from a serving node that already has a particular subscriber data will not necessarily require embedded ISD messages to be sent from the HLR. Also, the number of SAI messages is reduced, as the authentication data is kept at the serving nodes.

Subscriber information is allowed to remain in previously visited serving nodes by not sending a Cancel Location (CL) message when the subscriber arrives at another serving node.

Moreover, when a subscriber record for the MS is deleted in the serving node, either by MMI interaction or automatically, the Purge MS message is not sent to the HLR.

The main advantage of supercharger is that the amount of traffic in the network decreases since the number of CL, ISD, Purge MS and SAI messages sent is considerably reduced.

Trinode HLR Subscriber Limit 4This feature allows different levels of subscriber capacity to be purchased on a Combined MSC/HLR (formerly known as a Trinode). Subscriber capacities supported are 20 K subscribers, 50 K subscribers, 100 K subscribers and 200 K subscribers on a Combined MSC/HLR. The capacities apply to both the Home Location Register (HLR) and Visitor Location Register (VLR), subject to enough memory being available. The subscriber capacities are provided through a Software Optionality Control (SOC) option.



Combined MSC/HLR subscriber capacity functionality is provided in the NSS16 and NSS17 releases via software updates. The NSS18 release, provides these software updates.

Note: This describes the Combined MSC/HLR subscriber capacity feature as a whole, that is, from both the HLR and VLR perspectives (not just the HLR).

In the NSS16 and NSS17 releases, the contracts between Nortel and some operators restrict the number of mobile subscribers that may be supported. For these Operators, subscriber capacities of 20 K, 50 K, 100 K and 200 K (the maximum for a Combined MSC/HLR) can be purchased. Subscriber capacities apply to HLR subscribers and VLR subscribers (separately, not the total of HLR and VLR subscribers).

In the NSS18 release, the subscriber capacity patches are replaced with a SOC implementation. SOC allows software options to be purchased and activated for use. Options are enabled using a purchased password (also known as a key code). Key codes are unique for each option in each office.

The subscriber capacity feature is only applicable to Combined MSC/HLR offices. The SOC option implementing the subscriber capacities is not available to non-Combined MSC/HLR offices.

VLR robustness 4This activity provides the following enhancements to the Nortel GSM/UMTS MSC Server/Visiting Location Register (VLR):

• VLR data integrity enhancements

— Introducing run time VLR data integrity checks

• VLR Restoration indicators enhancements

— Decoupling the VLR restoration indicator HLRCONF to “Subscriber Data Confirmed by HLR” (HLRCONF) and a new indicator “Location information confirmed in HLR” (LOCCONF)

— QGSMVLR tool enhancements to display the new LOCCONF indicator

• VLR service data store enhancements

— Restructuring the internal VLR data store for CDA, CDS, FAX, SPCH and AUX SPCH to improve the MSC server memory usage efficiency

VLR data corruption was observed during VLR data access (add, delete or search) operation on International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Mobile Subscriber ISDN


411-2831-010 Standard 18.05 April 2006

Number (MSISDN) keys. This feature performs the sanity checks for these keys during add, delete and search operations. Also, this feature improves the existing sanity checks for Temporary Mobile Subscriber Identity (TMSI) key.

Prior to GSM18, the functions of the two flags “Subscriber Data Confirmed by HLR” and “Location Information Confirmed in HLR” were provided by a single flag “HLRCONF” in VLR. This feature enhances HLRCONF to use HLRCONF for “Subscriber Data Confirmed by HLR” scenarios and LOCCONF for “Location Information Confirmed in HLR” scenarios.



Introduction to UMTS 5

International Mobile Telecommunications 2000 (IMT-2000) is the International Telecommunications Union (ITU) vision of global mobile access in the 21st century. IMT-2000 is a strategic priority of ITU. The key features of IMT-2000 are as follows:

• high degree of commonality of design worldwide

• compatibility of services within IMT-2000 and with the fixed network

• high quality and integrity, comparable to the fixed network

• accommodation of a variety of types of terminals including the pocket- sized terminal

• worldwide roaming capability

• capability for multimedia applications and a wide range of services, such as

— video-teleconferencing

— high-speed Internet

— speech

— high data rate (2 Mbit/s)

The Universal Mobile Telecommunications System (UMTS) is an IMT-2000 system incorporating mobile cellular and other functionality. The 3rd Generation Partnership Project (3GPP) is a group of standards organizations that defines UMTS standards and specifications. UMTS specifications are designed to encourage service development so operators can customize their service portfolios and allow independent service providers to use the network.

UMTS provides an open architecture for the UMTS Voice Core Network (VCN) switching that supports:

• better performance at lower cost than GSM

• access to all current local data networks

• worldwide routing ability

5-2 Introduction to UMTSNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

• integration of Intelligent Network (IN) technology

• home network services even while roaming (Virtual Home Environment-- VHE) using standards such as Customized Application for Mobile network Enhanced Logic (CAMEL)

• multimedia

• independent Radio Access and the Core Network to allow UMTS to provide a wide range of applications

• Quality of Service (QoS) options

UMTS Public Land Mobile Networks 5Figure 5-1 shows a UMTS Public Land Mobile network (PLMN), its associated User Equipment (UE) and its relationship to the PSTN, Integrated Services Digital Network (ISDN), and other UMTS PLMNs.

Figure 5-1 UMTS PLMN and UE, PSTN, ISDN, and other UMTS PLMN

UMTS PLMN servicesUMTS PLMNs provide the following types of services:

• Speech–where the information transmitted is voice

• Emergency calling–allows the user of a UMTS Mobile Station to reach a nearby emergency service center

• Data–where the information transmitted is non-voice, such as facsimile

• Short Message Service–in which a one-way message of limited size is transmitted to or from a UMTS user allowing the UMTS UE to act as a telephone and a pager

UMTS PLMN “A”

UE belonging to UMTS PLMN “A”

PSTN

ISDN

Other UMTS PLMN

Introduction to UMTS 5-3Nortel Confidential Copyright © 1993–2006 Nortel


• Supplementary Services–which enable the UMTS user to specify how calls to or from the user are handled under certain conditions - for example, forwarding the call to another number when the user does not answer.

Numbering in UMTS PLMNsUMTS PLMNs use unique numbers to identify and route calls to the UE. Refer to Figure 5-2.

Figure 5-2Numbers used in UMTS

The International Mobile Equipment Identity (IMEI) uniquely identifies the mobile equipment.The Mobile Subscriber Integrated Services Digital Network (MSISDN) number is the unique phone number that consists of Country Code + National Destination Code + Subscriber Number. MSISDNs are allocated according to the CCITT E.164 numbering plan. (Using universal translations, this translates to Access Code + Prefix Code + Country Code + Foreign Area Code + Office Code + Directory Number.)The International Mobile Subscriber Identity (IMSI) is a unique identification of the subscriber. It is stored in the SIM (see below) and Home Location Register (HLR). IMSIs are allocated according to CCITT E.212.The Temporary Mobile Subscriber Identity (TMSI) is a unique identity temporarily allocated to visiting UE. The TMSI identifies the UE within a specific VLR as part of the confidentiality service.

SubscriberIdentityModule (SIM)

The Subscriber Identity Module (SIM) is a credit-card sized card that plugs into any UMTS UE. It contains the IMSI and MSISDN, security functions, and UE information.

The Mobile Subscriber Roaming Number (MSRN) is temporarily assigned to the UE while roaming and is used to terminate calls to the UE.

UMTSnumber portability

When an Integrated Services Digital Network (ISDN) User Part (ISUP) Initial Address Message (IAM) is received, the (gateway or visited) Call Server (CS) sends a database query to the Number Portability Database (NPDB). The NPDB determines if the MSISDN is ported or not ported. If the MSISDN is not ported, the NPDB sends it back to the CS to continue the normal call setup procedure for Mobile Terminated Calls (MTC), optionally providing the routing number. If the MSISDN is ported, the NPDB responds back to the CS with a routing number that points out the subscription network.


411-2831-010 Standard 18.05 April 2006

Major UMTS components and interfaces 5Figure 5-3 shows the major components and interfaces of a UMTS network.

Figure 5-3UMTS major components and interfaces

A UMTS network is composed of four major areas: UE, the access network, a core network packet switched (PS) domain, and a core network circuit switched (CS) domain.

The following sections provide a brief, high-level description of the UE, radio access network, and core network packet-switched domain.

See Table 5-1 for descriptions of the core network signaling interfaces.



User EquipmentThe User Equipment (UE) is composed of three parts:

• USIM card (Universal Subscriber Identity Module-card). The USIM is a smart card that allows identification of any subscriber by the network. In particular, the subscriber can borrow any mobile device without changing anything from the network point of view since they keep the same USIM-card.

• handset, including the radio equipment (receiver-transceiver) and the Man-Machine Interface (MMI). In UMTS, rich multimedia, WAP, and other services are supported by a wide array of handset options.

• battery

See Figure 5-4 for UE components.

Figure 5-4UMTS UE components


411-2831-010 Standard 18.05 April 2006

UMTS Terrestrial Radio Access NetworkUMTS01 supports the UMTS Terrestrial Radio Access Network (UTRAN). The UTRAN of a UMTS PLMN is shown in more detail in the Figure 5-5.

Figure 5-5UMTS UTRAN components and interfaces

A UMTS UTRAN is composed of one or more Radio Network Subsystems (RNSs).

Each RNS is made up of one or more Radio Network Controllers (RNCs). Each RNC controls one or more UMTS Node B Basestation Transceiver Subsystems (BTSs), which communicate to the UE devices.

The core network uses the Iu interface to communicate with the RNCs, including both Iu CS (circuit switched) and Iu PS (packet switched) sessions. The RNCs use the Iub interface to communicate to the radio towers. The radios communicate to UE of the Uu interface.

Coverage area of the UMTS NetworkSeveral area types have been defined in UMTS to handle user mobility.



Location AreaA UMTS Location Area contains a group of cells, with each cell belonging to one Location Area (LA). LAs are used by the Core Network CS domain to get information on the user location when in Idle mode. One LA consists of a number of cells belonging to RNCs that are connected to the same CN node; for example, one Call Server. The mapping between one LA and RNCs is handled within the Call Server owning the LA.

Routing Area A UMTS Routing Area (RA) contains a group of cells, with each cell belonging to one RA. RAs are used by the Core Network PS domain to get information on the user location when in Idle mode. One RA consists of a number of cells belonging to RNCs that are connected to the same CN node; for example, one Call Server. The mapping between one RA and RNCs is handled within the SGSN owning the RA.

The following relationships between LA and RA are possible:

• RA and LA are identical.

• One RA is a subset of one, and only one, LA, meaning that an RA does not span over more than one LA.

See Figure 5-6 for a sample UMTS PLMN coverage area.

Figure 5-6Example of UMTS PLMN coverage area


411-2831-010 Standard 18.05 April 2006

Core NetworkThe UMTS core network is divided into a circuit switched domain and a packet switched domain.

Circuit switched domain (Circuit core network)Traffic arriving over the Iu interface destined for the CS domain is routed from the Wireless Gateway to the Call Server. Following transcoding, the bearer channels are routed to the Call Server using standard 64 kbit/s TDM links. The Radio Access Network Application Part (RANAP) CS signaling is routed to the Call Server over IP, where the call is processed in a ‘traditional’ manner (translations, routing and service invocation). Communication with the SS7 environment is performed utilizing the SS7 capabilities of the Call Server hardware. TDM connectivity to both the Wireless Gateway and the PSTN is provided via the DTC hardware

Packet switched domainTraffic for the PS Domain is processed in the Wireless Gateway in a manner similar to the handling of GSM GPRS data traffic.

The SGSN performs setup and routing of data sessions to the GGSN for access into the Internet or corporate Intranets utilizing GPRS Tunneling Protocol (GTP) tunnels.

Unified network architectureUMTS01 uses an ATM-based packet backbone to interconnect all major nodes in the UMTS network as shown in Figure 5-7.

Figure 5-7UMTS networking architecture



Access to the core network is via dedicated gateways (Wireless, PSTN, Packet). Mobility management has been concentrated in the Wireless Gateway (WG). To access platforms which are using SS7, such as the Universal Announcement Server (UAS) or the HLR, the Call Server uses the services of an Universal Signaling Processor (USP). This architecture allows a variety of access technologies (WCDMA, GSM, GPRS, xDSL, PSTN, IP) to use the Core Network. Voice Core Network overview

The circuit switched domain of the UMTS PLMN is called the UMTS Voice Core Network (VCN). The VCN performs the main circuit switching functions and manages the following:

• communication among UMTS UE

• communication between UMTS UE and users in other networks.

Components of the Voice Core NetworkThe major VCN components are the Wireless Gateway, the Call Server with collocated VLR, and the HLR as shown in Figure 5-8.

Figure 5-8Components of VCN

Wireless GatewayThe Wireless Gateway (WG) is a common Iu interface termination point for PS (Packet) Switched) and CS (Circuit Switched) domains.

The Wireless Gateway provides signaling and bearer services across both Circuit and Packet Domains, as well as communication between the Core and Access Networks. The WG is part of both the 3G-MSC and the 3G-SGSN according to the 3G Standards definitions. Nortel chose to have a single product, the Wireless Gateway, housing the SGSN functionality (PS domain)


411-2831-010 Standard 18.05 April 2006

and the TRAU functionality (CS domain). The WG is located between the RNC and the other Core Network nodes.

The functional elements of the WG are

• 3G-SGSN

• Signaling Gateway (SG)

• Virtual Media Gateway (VMG)

• Aggregation Node (AN)

Transcoder/Rate Adapter UnitThe Transcoder/Rate Adapter Unit (TRAU) is a device that takes UMTS speech packets and converts them into standard ISDN 64 kbps speech packet. In UMTS, this functionality is part of the Core Network.

Some optimization procedures are allowed to pass through the TRAU without transcoding, in the case of UE to UE communication for example, when double-transcoding would be performed. In UMTS the default vocoder is the Adaptive Multi Rate (AMR) vocoder. Its rate varies between 12.2 kbit/s and 4.75 kbit/s.

The rate in the CS domain is still 64 kbit/s.

The TRAU interfaces with

• the RNC through the ATM backbone (AAL-2 layer used for UMTS)

• the Call Server with PCM links

Call ServerThe Call Server (CS) performs all of the switching functions needed for the UE located in its geographical area. Following are the major CS functions:

• mobile subscriber call establishment and routing

• dialed digits translation

• Call Control and signaling

• billing data capture and formatting

• Authentication and Ciphering

• locating and contacting UE for call termination

• management of facilities for calls

• echo control

• Short Message Service support

• Supplementary Services support



Figure 5-9 shows the possible circuit signaling and bearer transmission paths controlled by the UMTS Call Server.

Figure 5-9Call Server transmission paths

Gateway Mobile-services Switching CenterA Gateway Mobile-services Switching Center (GMSC) is capable of interrogating a mobile subscriber’s HLR to obtain the information required to terminate calls to that UE. A GMSC also serves as an interface between UMTS PLMNs or between a UMTS PLMN and another network.

Visitor Location RegisterThe Visitor Location Register (VLR) is a database that holds information pertaining to UE currently registered in the VLR Serving Area. The VLR is collocated with the Call Server. For UE that have currently roamed into a VLR area, the VLR maintains a local copy of a subset of the subscriber’s data. As its name implies, the VLR is concerned only with the information pertaining to UE that are currently visiting the VLR serving area. The VLR obtains this data from the Home Location Register (HLR) of the UE.

The VLR also assigns numbers that are used when a UE is roaming in the UMTS network. These numbers include the Mobile Station Roaming Number (MSRN) and Temporary Mobile Subscriber Identity (TMSI).


411-2831-010 Standard 18.05 April 2006

Home Location RegisterThe Home Location Register (HLR) is a database that contains permanent subscriber data, such as provisioning and service information, and dynamic information, such as the current location of the UE, which it gets from the VLR.

The HLR is a UMTS user’s home base of information—that is, it is the database to query for information about an instance of UE, regardless of that current geographical location of the UE. The HLR supports call routing and controls Supplementary Services.

Authentication CenterThe Authentication Center (AUC) is an integrated part of the HLR that ensures only authorized users have access to the network. The AUC contains subscriber authentication keys and generates security-related parameters.

The Send Authentication Information message is enhanced at map application context version 3 to support additional parameters for UMTS. The algorithm mechanism is enhanced for UMTS and authentication quintuplets are generated for 3G subscribers versus authentication triplets for 2G.

Equipment Identity RegisterThe Equipment Identity Register (EIR) is a database that is used to prevent unapproved, stolen, or faulty UE equipment from accessing the UMTS PLMN. The EIR maintains lists indicating if a UE is valid, barred from using the network, or faulty.

Short Message Service CenterThe Short Message Service-Service Center (SMS-SC) allows mobile subscribers to receive short messages when their UE is not operational and to send short messages to other UE or terminals capable of receiving short messages.

The SMS-SC acts as a storage and forwarding center to which mobile subscribers may send messages destined for other UE. The SMS-SC may also transfer stored short messages to the receiving UE or terminal.

InterWorking FunctionWhen a data communications session is established between subscriber equipment on dissimilar networks, a device known as an InterWorking Function (IWF) must be used in order to provide data interworking between networks. The IWF serves as a translation and conversion point in a digital mobile network. The IWF allows an end-to-end connection between a mobile subscriber and a remote device, such as a dial-up modem. The IWF provides the required rate adaptation, radio link protocol, and modems for interfacing the UE to the PSTN or ISDN.



An IWF works in conjunction with the serving Call Server (CS) and is switched into the call path for circuit-switched data calls originating or terminating to a UMTS UE.

Example of mobile-terminating call setupFigure 5-10 and Figure 5-11 show the steps for setup of a call from a mobile UE to the Public Switched Telephone Network (PSTN). This scenario is only one of several possible types of phone calls within a UMTS network.

Figure 5-10UMTS mobile-to-land call set-up (part 1)

Figure 5-11UMTS mobile-to-land call set-up (part 2)


411-2831-010 Standard 18.05 April 2006

Note that in Figure 5-11, after the circuit has been created, the bearer channel is created over the ATM packet backbone.

Communication among VCN componentsThe following types of information are transferred among the CS, HLR, VLR, and Equipment Identity Register (EIR) using the CCS7 network:

• mobile subscribers

• mobile subscribers’ locations

• mobile subscribers’ options

In order to handle the special information transfer requirements of these types of information, as well as information related to call processing, UMTS uses Mobile Application Part (MAP) protocols. The MAP protocols are a set of signaling functions used specifically for roaming UMTS UE.



UMTS core network signaling interfacesUMTS signaling interfaces are defined by GSM and UMTS specifications. UMTS interface Iu replaces GSM A-Interface between the radio network and the switch. Interfaces B-G are unchanged from GSM and use the Mobile Application Part (MAP) protocols to exchange the data necessary to provide mobile service. Table 5-1 describes the circuit and packet core network signaling interfaces shown in Figure 5-3 (radio subsystem interfaces are not covered).

Table 5-1UMTS signaling interfaces

Diagram Key

Core Network Signaling Interface Description

Iu CS Circuit switched interface between the CS and RNS via the WG.

Iu PS Packet switched interface between the CS and RNS via the WG.

B Interface between the CS and VLR using MAP/TCAP signaling over CCS7 SCCP and MTP. The CS contains both the CS and VLR functionality (that is the CS is co-located with the VLR. Therefore the B-Interface (CS <-> VLR) is an internal interface only.

C Interface between the gateway MSC and HLR using MAP/TCAP signaling over CCS7 SCCP and MTP.

D Interface between the HLR and VLR using MAP/TCAP signaling over CCS7 SCCP and MTP.

E Interface between CSs using MAP/TCAP signaling over CCS7 SCCP and MTP. ISUP or some other Call Control protocol is also exchanged to permit inter–CS calls to be established.

F Interface between CSs and EIR using MAP/TCAP signaling over CCS7 SCCP and MTP.

G Interface between VLRs using MAP/TCAP signaling over CCS7 SCCP and MTP.

Gb The RNS-SGSN interface is used to carry information concerning:

• packet data transmission

• mobility management

The Gb interface is defined in GSM 08.14, 08.16 and 08.18.

—sheet 1 of 2—


411-2831-010 Standard 18.05 April 2006

MAP Application Entities The UMTS MAP defines the CS, HLR, and VLR as separate Application Entities. An Application Entity provides and uses certain services. For example, a CS (an Application Entity) would request routing information for a particular mobile subscriber from an HLR (another Application Entity).

MAP Application Service ElementsThe services provided by Application Entities are called Application Service Elements (ASEs). There is always an ASE requestor and an ASE provider. An example of an ASE is Send Routing Information (SRI), which is a message sent by the CS to the HLR when an MSISDN is dialed. The CS Application Entity uses the Send Routing Information service requestor ASE and the HLR Application Entity uses the SRI service provider ASE. Figure 5-12 shows the Application Service Element’s two components, requestor and provider.

Gr This HLR/SGSN interface used to exchange the data related to the location of the mobile station and management of the subscriber. The main service provided to the mobile subscriber is the capability to transfer packet data within the whole service area. The SGSN informs the HLR of the location of a mobile station managed by the latter. The HLR sends to the SGSN all the data needed to support the service to the mobile subscriber. Exchanges of data may occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription, or when some parameters of the subscription are modified by administrative means. Signaling on this interface uses the Mobile Application Part (MAP), which in turn uses the services of Transaction Capabilities Application Part (TCAP).

Gn, Gp These interfaces are used to support mobility between the SGSN and GGSN. The Gn interface is used when GGSN and SGSN are located inside one PLMN. The Gp-interface is used if GGSN and SGSN are located in different PLMNs. The Gn/Gp interface also includes a part which allows SGSNs to communicate subscriber and user data, when changing SGSN. Signaling on this interface uses the User Datagram Protocol, UDP/IP.

Gi Interface between the GGSN and the Internet.

Table 5-1UMTS signaling interfaces (continued)

Diagram Key

Core Network Signaling Interface Description

—sheet 2 of 2—



Figure 5-12Application Service Element requestor and provider

Every service provided by an Application Entity has a distinct ASE—in this sense—an Application Entity consists of a set of ASEs. A specific ASE may be used by more than one Application Entity depending on the services required by the Application Entity.

CCS7 functional layers in Application EntitiesEach of the Application Entities contains software that corresponds to the CCS7 functional architecture, which uses several layers to describe the interconnection and exchange of information between CCS7 users. The CCS7 layers, which use the physical layer, are as follows:

• Message Transport Part (MTP) Layer

• Signaling Connection Control Part (SCCP) Layer

• Transaction Capabilities Application Part (TCAP) Layer

• Mobile Application Part (MAP) Layer

A layer in one Application Entity logically communicates with its peer layer in another Application Entity. Physically however, each layer communicates only with adjacent layers within its own Application Entity. Figure 5-13 shows the CCS7 software structure of the Application Entities, along with the logical and physical message flow. A brief description of the layers follows the figure.

Send Routing Information (SRI)Application Service Element (ASE)

Requestor Provider

HLRCall Server(SRI Requestor) (SRI Provider)

Send Routing Information

(Provides Routing Information)


411-2831-010 Standard 18.05 April 2006

Figure 5-13 Communication between Application Entities

Message Transfer PartThe Message Transfer Part (MTP) layer of CCS7 serves as a connection-oriented transport system between locations of communicating users. The term “users,” in this case, refers to the Application Entities, which utilize the basic transport capability provided by the Message Transfer Part layer.

Signaling Connection Control PartThe Signaling Connection Control Part (SCCP) layer of CCS7 provides messages routed between users within a telecommunications network. SCCP is used by TCAP (the next higher level) as a message transport mechanism, and uses Global Title Translation (GTT). The SCCP layer recognizes each Application Entity as a separate subsystem.

Transaction Capabilities Application PartThe Transaction Capabilities Application Part (TCAP) is the interface to Mobile Application Part procedures. The Mobile Application procedures interface uses this layer, as well as the lower two layers.

The TCAP consists of functions that control non-circuit-related information transfer between components. The TCAP ensures that units of information to be exchanged are formatted and exchanged properly. It provides encoding and decoding rules for the information exchange.

MAP

TCAP

SCCP

MTP

Physical Layer

VCN CS Other AEs

= Logical message flow= Physical message flow

MAP

TCAP

SCCP

MTP

Physical Layer



The TCAP also associates each TCAP message and the information it contains with a particular type of application process transaction. This transaction association enables the TCAP to link a query with a response and identify the context.

Mobile Application PartThe Mobile Application Part layer uses the MTP, SCCP, and TCAP layers to transfer information among Application Entities. The Mobile Application Part protocols define the following:

• Application Entities

• interfaces between the Application Entities

• signaling functions required for CCS7 which provides voice and non-voice services in the NSS

UMTS core network signaling protocolsThere are several signaling protocols used in the Core Network. The nodes within the network can be addressed with either MTP3 point codes or IP addresses. The main signaling protocols used in the Core Network are:

GPRS Tunneling ProtocolThe GTP protocol used to control IP tunnels between the RNC and the GGSN is a connectionless protocol. As it relates to the IP world, the nodes use IP addresses.

User Datagram ProtocolThe UDP protocol is used to control the connectionless datagram communications.

Radio Access Network Application PartRANAP is used for the Iu-CS and Iu-PS interface. Some of the RANAP procedures are connection oriented and therefore the SCCP layer of SS7 is used.

Transaction Capabilities Application PartTCAP provides dialogue control for CAP/INAP and MAP protocols. These are connection oriented and use the services of SCCP.

ISDN User PartISUP, between the Call Server and the PSTN, may require the services of SCCP for certain types of configuration, but more usually uses MTP3 directly.


411-2831-010 Standard 18.05 April 2006



VCN HLR100 software 6The UMTS Voice Core Network Home Location Register 100 (VCN HLR100) software is developed on the CSP architectural layer for deployment to all UMTS markets. The VCN HLR100 software is broken into discrete functional units which provide for the operation of different functions within the HLR. This set of functions is listed below and described in the following sections:

• UMTS Based-Product Layer

• UMTS Market Specific

• Proprietary Services

• UMTS Services

• UMTS Base

• GSM/UMTS HLR100 Interfaces

• Shared Layer

• Telecom Layer

• Base Layer

These units combine to yield the total functionality of the VCN HLR100, as shown in Figure 6-1. Note that the structure does not necessarily imply inter-relationships.

6-2 VCN HLR100 softwareNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

Figure 6-1VCN HLR100 Software Structure

Base Layer

Telecom Layer

Shared Layer

CSP

Call Routing Intelligent

Inter-PLMNEqual Access

UMTS Base

UMTS Market Specific

Global Services

UMTS

UMTS Based-Product Layer

Short Message

DataSupplementary

Services

Service

UMTS Services

UMTS Interfaces

UM

TS

DR

U

HLR to CSHLR to VLRHLR to AUCHLR to SGSN

Support

Support

NetworkSupport

roamingsupport

Authentication

Messaging&

Signaling

Proprietary Services

Services

Speech

SIMReplacement

SupplementaryServices

ServicesOperator

ALS

OperatorDetermined

Barring

SubscriberDatabase

Management

ONP

CAMEL

VCN HLR100 software 6-3Nortel Confidential Copyright © 1993–2006 Nortel


UMTS market specific 6The UMTS-based product layer contains software specific to a particular VCN HLR100 product such as UMTS. This layer includes software specific to the UMTS markets.

Proprietary services 6Proprietary services are as follows:

• “SIM replacement”

• “Supplementary Services”

• “Operator services”

• “Alternate line service”

• “One night process”

SIM replacementA Subscriber Identity Module (SIM) card is used in identifying any subscriber to a UMTS network. A subscriber’s SIM card has a finite life expectancy and it is necessary to replace the SIM card periodically. This service facilitates the replacement process.

Supplementary ServicesProvides capability to the VCN HLR100 to provide proprietary services, such as Class of Service and number translations.

Operator servicesProvides proprietary network services to mobile network operators.

Alternate line serviceAlternate Line Service (ALS) is a non-UMTS defined service. It associates two MSISDN numbers with a subscriber (IMSI) for telephony calls.

One night processOne Night Process (ONP) is used during a software upgrade to transfer all the data from the old release to the new release.

UMTS services 6This layer contains the software related to UMTS defined services.

Supplementary ServicesProvides capability to the VCN HLR100 to modify or supplement basic telecommunications services, such as call waiting and call barring.


411-2831-010 Standard 18.05 April 2006

Short message serviceThe VCN HLR100 supports the UMTS Short Message Service. This service allows for messages of a limited size to be sent from a Service Center to a mobile (SM MT) and from a mobile to a Service Center (SM MO).

Data serviceThe VCN HLR100 supports the circuit-switched data services.

Upgraded HLRTRACE toolHLRTRACE has been upgraded to allow post-analysis of messages executed within the VCN HLR100. This trace tool is VCN HLR100 specific, allowing the tracing of a single subscriber or a group of up to ten subscribers (multiple subscriber tracing).

The tool causes minimal blocking on XA-Core and minimizes the real-time overhead of tracing.

The system records the messages related to each subscriber in separate capture buffers. This allows the user to display all the messages for a certain subscriber. The tool also records system messages.

The capture buffers provide enough storage for up to 100 messages in total.

SpeechThe VCN HLR100 supports telephony and emergency speech services.

UMTS base 6The UMTS base consists of the following support or services:

• “Call routing support”

• “Equal access support”

• “Operator determined barring”

• “Intelligent network support”

• “Inter-PLMN roaming support”

• “Subscriber database management”

• “Authentication”

• “Messaging and signaling”

Call routing supportThe VCN HLR100 supports call routing to mobile stations by providing the VCN CS with information about the location of mobile stations.



Equal access supportFor the North American marketplace, the VCN HLR100 provides support for equal access. Equal access is defined as the ability of a user to choose an interexchange carrier (IC/INC) for call attempts that do not terminate on their network or within a local exchange network directly connected to their network.

Operator determined barringOperator Determined Barring (ODB) is a service that allows the network operator or service provider to regulate access by the subscribers to UMTS services. These services are regulated by barring certain categories of outgoing or incoming calls or of roaming. One application of ODB might be to those subscribers who have not promptly paid their bills.

Intelligent network supportVCN HLR100 incorporates proprietary extensions to support the implementation of Intelligent Network (IN) support at the VCN CS.

Inter-PLMN roaming supportVCN HLR100 supports Mobile Stations in roaming to other Public Land Mobile Networks (PLMNs), both within and outside of the Mobile Station’s home country.

Subscriber database managementManages the storage of subscriber information.

AuthenticationGenerates security-related parameters used to ensure that only authorized Third Generation (3G) UE have access to the Public Land Mobile Network (PLMN).

Messaging and signalingSupports the following VCN HLR100 functions:

• UMTS-defined Mobile Application Part (MAP) protocols,

• Hybrid protocol stack in addition to standard UMTS stack,

• VCN HLR100 network interface.

VCN HLR100/AuC interfaces 6VCN HLR100 provides the network with facilities for examining permanent data and examining and modifying temporary data. VCN HLR100 handles transactions with the CS and nodes, which either request information from the VCN HLR100, or update the information currently held in VCN HLR100. VCN HLR100 also initiates transactions with the VLR to complete incoming calls and update subscriber data.


411-2831-010 Standard 18.05 April 2006

Network nodes, including VCN HLR100, use Mobile Application Part (MAP) interfaces to communicate. The following are the specific VCN HLR100 MAP interfaces (refer to Figure 6-2):

• CS to HLR/AuC (C-interface)

• HLR to VLR (D-interface)

• The VCN HLR100/AuC to Maintenance and Administration Position interface is the Administrative interface.

• HLR/AuC to 3G SGSN (Gr-interface)

Figure 6-2HLR/AuC

Home location register The Home Location Register (HLR) is a database that holds information about the subscribers. It performs the following functions:

• handling of permanent subscribers data (identification, subscription information, service limitation)

• handling of temporary subscribers data:

3-19Basic UMTS Architecture UMT/TRD/CN/0003 01.05/EN May, 2001

"Con

fiden

tial i

nfor

mat

ion

-- m

ay n

ot b

e co

pied

or d

iscl

osed

with

out p

erm

issi

on".

Core Network Architecture

Home Location Register (HLR)Authentication Center (AuC)

HLR/AuC

VLR

3GSGSN

Gr

3G MSC

Main HLR functions :- Handling of permanent

subscriber data- Handling of temporary

subscriber data- Dialogue with AuC

database

C

D



— current VLR, SGSN addresses where the subscriber roams

— security information

• dialog with the AuC database

Authentication CenterThe Authentication Center (AuC) is a database that contains secret subscriber keys and security algorithms; it generates security information for authentication and ciphering.

For security reasons, the AuC has an internal interface with the HLR. It is up to the HLR to start security algorithms located in the AuC.

Shared layer 6Shared layer contents are obtained from the Shared Library. The Shared Library is a central repository for storage of software features and frameworks utilized by multiple products. This centralized database provides a means for the management of common software allowing market and product independence, allows for the evolution of services, and is a cost-effective structure for software reuse.

Telecom layer 6The Telecom layer includes general purpose utilities and maintenance systems for VCN telecommunications products. These utilities include CCS7, call processing base and run-time support, ENET and JNET maintenance, and basic translations. This layer does not necessarily contain all the functionality required to place calls.

Base layer 6The Base layer contains resource management for system resources, maintenance systems for general purpose computing devices, and operations, administration, and maintenance (OA&M) for the system.


411-2831-010 Standard 18.05 April 2006

A-1Nortel Confidential Copyright © 1993–2006 Nortel


List of terms A2G

Second Generation

3GThird Generation

3G GGSNThird Generation Gateway GPRS Support Node

3G SGSNThird Generation Serving GPRS Support Node

3GPPThird Generation Partnership Project

AbortSWACTAbortSwitch of Activity

A-bis interfaceCommunications interface from the Base Transceiver Station (BTS) to the Base Station Controller (BSC) using Link Access Procedure-D (LAPD) and Q.931 signaling.

A8Algorithm A8. Cryptographic algorithm that produces Cipher Key (Kc) using Random Number (RAND) and Authentication Key (Ki).

ANAccess Network. It is the user access point to the system, and provides to the user the mean of speaking, receiving, or transmitting data.

ACRJAnonymous Call Rejection

A-2 List of termsNortel Confidential Copyright © 1993–2006 Nortel

411-2831-010 Standard 18.05 April 2006

Active-UEActive-User Equipment. A switched-on UE with a Subscriber Identity Module (SIM) module attached.

ADCAdministration Data Center

Administrative InterfaceAn external operator interface to the UMTS Circuit Core Network Home Location Register100 (VCN HLR100) database. This is supported through table control.

Advice of ChargeThe Call-Related Charging Supplementary Service that provides a Mobile Subscriber with information about the cost of a call. AoC comprises two services: Advice of Charge Charging (AoCC) and Advice of Charge Information (AoCI). A Mobile Subscriber may subscribe to only one at a time.

AEApplication Entity. The software framework for providing a set of functions within a UMTS network.

AESAdvanced Encryption Standard

AFRAuthentication Failure Report

AIAge Indicator

ALSAlternate Line Service

Alternate Line ServiceThe Supplementary Service that allows two telephony basic services to be associated with one International Mobile Subscriber Identity (IMSI). A single piece of User Equipment (UE) can have two telephony lines: one normal and one alternate. Each of these lines is associated with a different Mobile Subscriber Integrated Services Digital Network (MSISDN) number, one normal and one auxiliary.

AMFAuthentication Management Field. Part of the Network Authentication Token (AUTN). Input to UMTS authentication algorithm.

List of terms A-3Nortel Confidential Copyright © 1993–2006 Nortel


ANAggregation Node. The aggregation node is responsible for providing connectivity between the Passport nodes providing SG, 3G-SGSN, and VMG functionality, and the external transport networks used for the Iu and Gn interfaces. The AN is a standard Passport 15K product with no Wireless Gateway specific applications. It therefore supports the rich suite of existing Passport 15K services for the Gn and Iu interfaces, as well as for any other required network services.

Anonymous Call RejectionAllows a subscriber to reject calls from a number having its calling line identification number presentation set to restricted.

APIApplication Programming Interface

ASCAlert Service Center is a MAP operation.

ASEApplication Service Element. Corresponds to an individual service provided or requested by a user. Each service has a distinct ASE and an AE consists of a set of ASEs.

ATIAny Time Interrogation

AuCAuthentication Center

AUTNNetwork Authentication Token. Comprised of the Sequence Number (SQN), Authentication Management Field (AMF), and the Milenage Authentication-Algorithm (MAC-A). Output from UMTS authentication algorithm.

Authentication algorithmName given to the UMTS authentication algorithm. The Milenage framework allows many authentication algorithms to be defined by changing the flavor.

Authentication CenterA component of the fixed portion of the PLMN. The AUC generates security-related parameters that are used to ensure that only authorized Mobile Subscribers have access to the PLMN. AUC may be implemented on the Home Location Register (HLR).


411-2831-010 Standard 18.05 April 2006

BInterface between the CS and VLR using MAP/TCAP signaling over CCS7 SCCP and MTP.

BAICBarring of All Incoming Calls

BAIC-roamBarring of All Incoming Calls when roaming outside the home PLMN country

BAOCBarring of All Outgoing Calls

BAOC-roamBarring of All Outgoing Calls when roaming outside the home PLMN country

Barring of All Incoming CallsThe Supplementary Service that makes it possible for the User Equipment (UE) to prevent all incoming calls, or just those calls associated with a basic service.

Barring of All Outgoing CallsThe Supplementary Service that makes it possible for a User Equipment (UE) to prevent all outgoing calls, or just those associated with a basic service.

Basic ServiceA Teleservice or a Bearer Service

Basic Service GroupEither a Bearer Service Group or a Teleservice Group that contains similar Basic Services.

BCSBatch Change Supplement. A Northern Telecom software release identified by a number such as BCS35+.

BCSMBasic Call State Machines

Bearer serviceA type of telecommunication service that provides the capability for the transmission of signals between network access points, characterized by a set of low layer attributes (layers 1 through 3 of the Open Systems Interconnection model). Examples: speech followed by data; and alternate speech or unrestricted digital transmission.



B-interfaceThe Mobile Application Part (MAP) interface between a Call Server (CS) and a Visitor Location Register (VLR).

Barring of All Outgoing CallsPrevents the User Equipment (UE) that has activated BAOC from making any outgoing calls, except emergency calls.

Barring of Outgoing International CallsAllows the Mobile Subscriber with BOIC to call only subscribers of any PLMN or fixed network in the country in which the MS with BOIC is currently roaming.

Barring of Outgoing International Calls (BOIC) except those directed to the HomePLMN Country

Allows the User Equipment (UE) with BOIC-exHC to internationally call only subscribers of its home PLMN country. The UE with BOIC-exHC can also call subscribers locally within the visited PLMN where it is currently roaming.

BHCABusy Hour Completed Attempts (BHCA)

BOICBarring of Outgoing International Calls

BOICEXHCBarring of Outgoing International Calls except those directed to the Home PLMN Country

BRISCBNR (Bell Northern Research) Reduced Instruction Set Computing

BSBSCBase Station Controller. A network component in the PLMN that controls one or more Base Transceiver Stations (BTSs). A BSC is part of a Base Station System (BSS).

It terminates all radio-related messages from the Mobile Stations. It has two components: the BSS central equipment (BCE) and the transcoding equipment (TCE).

BSSBase Station Subsystem. The entity responsible for communicating with Mobile Stations within a certain portion of a service area. A BSS is a system of base station equipment, such as transceivers and controllers. The GSM/UMTS MSC/HLR communicates with a BSS over the A-interface. A BSS may consist of one or more


411-2831-010 Standard 18.05 April 2006

base stations, and the radio equipment of the BSS may cover one or more cells.

BSSAPBase Station System Application Part. A portion of the interface between the BSS and Mobile-services Switching Center/Home Location Register (MSC/HLR) that contains all of the application layer procedures used on the interface. The BSSAP is split into two application sub-parts: the Direct Transfer Application Part (DTAP) and the BSS Management Application Part (BSSMAP).

BSSMAPBase Station System (BSS) Management Application Part (MAP). A category of signaling, using Message Transfer Part (MTP) (layer 2) and Signaling Connection Control Part (SCCP) (layer 3) of Common Channel Signaling 7 (CCS7), between the BSS and the Mobile-services Switching Center/Home Location Register (MSC/HLR) (A-Interface). BSSMAP supports procedures between the Digital Multiplex System-Mobile-service Switching Center (GSM/UMTS MSC/HLR) and BSS related to call processing and resource management. BSSMAP radio resource (RR) control messages are interpreted at the BSS.

BSSOMAPBase Station System Operation and Maintenance Application Part. In GSM communications systems, BSSOMAP messages are used to transfer operation and maintenance information between the Mobile-services Switching Center (MSC) and the Base Station System (BSS).

BTSBase Transceiver Station. A UMTS network component that serves one cell and is controlled by a Radio Network Controller (RNC). A BTS may contain one or more transceivers.

BusyCalled subscriber is call processing busy.

CInterface between the CS and HLR using MAP/TCAP signaling over CCS7 SCCP and MTP.

CALEACommunications Assistance for Law Enforcements Agencies (CALEA)

Call Hold/RetrieveThe Supplementary Service that allows a Mobile Subscriber to place an active call on hold or retrieve a currently held call.



Call processingThe UMTS Voice Core Network (VCN) software system that handles the processes involved in setting up connections through the VCN Call Server/Home Location Register (VCN CS/HLR) network (between calling and called parties).

Call ServerThe Call Server does the following:

• provides basic switching functionality from the ISDN • handles the User Equipment (UE)• sets up call to and from Universal Mobile Telecommunications System

(UMTS) subscribers• performs ticketing on calls for all subscribers based in the area• transfer encryption parameters from the Visitor Location Register (VLR)

to the UMTS Terrestrial Radio Access Network (UTRAN)CAMEL

Customized Application for Mobile network Enhanced Logic

CAPCAMEL Application Part

CASChannel Associated Signaling

CCITTConsultative Committee for International Telephony and Telegraphy. An international organization of communication carriers, especially government telephone monopolies, responsible for developing telecommunication standards by making recommendations.

CCFCall Forwarding Flavors

CCSCommon Channel Signalling System #7

CCS7Common Channel Signaling 7. A functional architecture that uses several layers to describe the interconnection and exchange of information between users.

CDCall Deflection


411-2831-010 Standard 18.05 April 2006

CDACircuit Duplex Asynchronous. The abbreviation is used to refer to the bearer service category Data Circuit Duplex Asynchronous, which refers to the category of data services that provide asynchronous data communication.

CDAGBSCircuit Duplex Asynchronous General Bearer Service

CDRCall Detail Record. Stores specific information about incoming and outgoing calls.

CDSCircuit Duplex Synchronous. The abbreviation used to refer to the bearer service category Data Circuit Duplex Synchronous, which refers to the category of data services that provide synchronous data communication.

CDSGBSCircuit Duplex Synchronous General Bearer Service

CellA locally defined area of radio coverage served by one or more Base Transceiver Stations (BTSs).

CEMCore Element Manager

CFCall Forwarding

CFBCall Forwarding Busy. The Supplementary Service that permits a called Mobile Subscriber to have the network send all or some incoming calls addressed to the called Mobile Subscriber’s directory number and which meet Mobile Subscriber busy criteria to another directory number.

CFNRcCall Forwarding Not Reachable. The Supplementary Service that permits a called Mobile Subscriber to have the network send all or some incoming calls addressed to the called Mobile Subscriber’s directory number but that cannot be reached because of radio congestion, no paging response, or because the subscriber is not registered, to another directory number.

CFNRyCall Forwarding No Reply. The Supplementary Service that permits a called Mobile Subscriber to have the network send all or some incoming calls addressed



to the called Mobile Subscriber’s directory number and which meet no reply to another directory number.

CFUCall Forwarding Unconditional. The Supplementary Service that permits a called Mobile Subscriber to have the network send all or some incoming calls to another directory number.

ChannelA specific portion of the total bandwidth of the transmission medium that serves as a path between two or more stations. A channel may be furnished by wire, radio, or a combination of both. The term channel often implies two channels, with one channel going in an opposite direction from the other.

CICommand Interpreter

C-interfaceThe Mobile Application Part interface between a Call Server (CS) and a Home Location Register (HLR) using MAP/TCAP signaling over CCS7 SCCP and MTP.

CIPCNortel Call Interception Provisioning Center

CircuitA complete electrical path over which telecommunications are provided between terminals.

Circuit Core NetworksA mobile telephone switching system that acts as a key component of the PLMN. The Call Server (CS) performs the functions of switching, routing, and control of the call, charging, accounting, and the interworking with public switched telephone networks.

CKCipher Key. Output from UMTS authentication algorithm.

CLCancel Location


411-2831-010 Standard 18.05 April 2006

Class of ServiceA Supplementary Service that associates a Mobile Subscriber to a Customer Group. When a Mobile Subscriber is associated with a Customer Group, the Mobile Subscriber inherits all of the services assigned to that Customer Group, such as those listed below:• individual and party lines

• flat rate and message rate

• restricted and extended area service

CLIPCalling Line Identification Presentation. A Supplementary Service that provides the called Mobile Subscriber with identification information about the calling party.

CLIRCalling Line Identification Restriction. A Supplementary Service that provides the calling party with the ability to restrict presentation of identification information to the called party.

CM(1) Computing Module. A component of the UMTS Voice Core Network (VCN) SuperNode that performs the processor and memory functions. Each CM consists of a pair of CPUs with associated memory that operate in a synchronous matched mode on two separate planes. Only one plane is active; it maintains overall control of the system while the other plane is on hot standby. (2) Connection Management. A Signaling Layer 3 sublayer that includes the Call Control (CC), Supplementary Services (SS), and Short Message Service (SMS) entities.

CNCore Network. The part of the Universal Mobile Communications System (UMTS) that is independent of the connection technology of the terminal (radio or wired).

CNRCall Notification Records

CNAMCalling Name Display

CoLIConnected Line Identification

COLPConnected Line Identification Presentation



COLRConnected Line Identification Restriction. Provides the connected party with the ability to block the presentation of the Connected Party Number (COPN) to the origination party.

COPNConnected Party Number

CORClass of Registration

COSClass of Service

CPUCentral Processing Unit. A hardware entity within the UMTS Voice Core Network (VCN) switch that contains the central data processor for the system. The CPU uses the programs and data stored in memory modules to respond to incoming messages from the system. It then issues commands to the system to perform the required actions.

CSCall Server. The Packet Switch (PS) and CS domains make up the Core Network (CN).

CS-ACall Server (A). This designates an CS as the primary or controlling CS in which a Mobile Station has either a mobile-originated or a mobile-terminated call.

CS addressAn international Public Switched Telephone Network/Integrated Services Digital Network (PSTN/ISDN) number, required if the Visitor Location Register (VLR) is not co-located with the Call Server (CS).

CS-BCall Server (B). Any CS other than the primary or controlling CS into which a Mobile Station has moved during a call.

CSICAMEL Subscription Information. Data stored in the HLR for each CAMEL subscriber

CS numberThe ISDN number of an CS


411-2831-010 Standard 18.05 April 2006

CSP(1) Carrier Selection information Parameter. (2) Common Software Platform

Customized Application for Mobile network Enhanced LogicA set of recommendations that standardize messages and Detection Points (DPs) for Intelligent Networking (IN) interworking.

CUGClosed User Group

CUSTGRPCustomer Group

CWCall Waiting. The Supplementary Service that offers a Mobile Subscriber the possibility to be notified of an incoming call while the termination is in the busy state. Subsequently, the subscriber can answer, reject, or ignore the incoming call.

DInterface between the HLR and VLR using MAP/TCAP signaling over CCS7 SCCP and MTP.

Data callThe term used to distinguish those telecommunication services that provide data communication capability from those that provide speech communication capability.

DCFDefault Call Forwarding

DDOCDesign Document

DDUDisk Drive Unit. Part of the UMTS Voice Core Network (VCN) Input/Output Device (IOD) subsystem used for storing and retrieving large amounts of information. The DDU stores office images, non-resident commands, Call Detail Recording (CDR), Operational Measurements (OMs), and Journal File (JF) data.

DECTDigital European Cordless Telephony

DESData Encryption Standard



D-interfaceThe Mobile Application Part interface between the HLR and the VLR.

DIRPDevice Independent Recording Package. A UMTS Voice Core Network (VCN) software subsystem that automatically directs data from the various administrative and maintenance facilities to the appropriate recording devices.

DPDetection Point

DP2Collected information for originating triggering calls

DP4Route select failure

DP12Terminating attempt authorized for terminating triggering calls

DP13Mobile terminating busy

DP14Mobile terminating no answer

DRUDeliverable Release Unit

DSData Server

DS30Protocol used as an interface among the components of UMTS Voice Core Network Call Server (VCN CS/HLR) and VCN family switches.

DSDDelete Subscriber Data

DSPROTA VCN support operating system (SOS) memory type that survives all restarts and has hardware write-protection.

GDual-plane combined coreA UMTS Voice Core Network (VCN) SuperNode equipment cabinet that houses


411-2831-010 Standard 18.05 April 2006

VCN bus and VCN core. VCN bus provides the messaging control component for the VCN SuperNode. VCN core performs central processing and is responsible for control of operations, administration, and maintenance.

DTCDigital Trunk Controller. A peripheral that provides the physical interface to E1/T1 digital carriers, allowing termination of a Public Switched Telephone Network (PSTN) or Wireless Gateway (WG) connection.

EAEqual Access

ECTSupplementary Services Explicit Call Transfer

EDMExternal Data Move. An EDM involves every tuple in a table being read from the dump side and added to the table on the restore side. Every tuple goes through the standard table control ADD operation including all the data integrity validations.

E-interfaceInterface between CSs using MAP/TCAP signaling over SS7 MTP and SCCP.

EIREquipment Identity Register. A functional unit that stores International Mobile Equipment Identities (IMEIs) for User Equipment (UE) and is accessed by a Call Server to validate user equipment.

EMIElectromagnetic Interference. The leakage of radiation outside a transmission medium due to high-frequency energy.

eMLPPenhanced multi-Level Precedence and Preemption service

Encryption engineIn the context of Milenage, this is any cryptographic function that takes a 128-bit input key and produces a 128-bit ciphered output. The 128-bit block Rjindael cipher is an example of an encryption engine.

ENETEnhanced Network. A channel-matrix time switch that provides pulse code modulated voice and data connections between peripheral modules (PMs). ENET also provides message paths to the UMTS Voice Core Network (VCN)-bus components.



ETSIEuropean Telecommunications Standards Institute

ExchangeTelephone switching center or a defined area served by a communications common carrier. The carrier furnishes service at the exchange rate under the area regulations as prescribed in the carrier’s filed tariffs.

EXTExtension Service

Ext-QoSExtensible Quality of Service

FInterface between CSs and EIR using Map/TCAP signaling over CCS7 SCCP and MTP.

F-busFrame transport bus

FFNFollow Me (FM) Function Node

FieldThe vertical columns of a UMTS Voice Core Network (VCN) table used to identify the fields of the table. A field has a name and a number associated with it.

FlavorThe flavor of an algorithm is defined by the parameters of the algorithm. In the Milenage authentication algorithm, the flavor is defined by algorithm constant integers values r1, r2, r3, r4, and r5 and 128-bit values c1, c2, c3, c4, and c5.

FMFollow Me. Allows users to call by using by their FN and not the Mobile Subscriber Integrated Services Digital Network (ISDN) Number (MSISDN)

Forwarded To NumberIdentifier that refers to an address where the calls are forwarded.

FSPFrame Supervisory Panel. A UMTS Vocie Core Network (VCN) facility that accepts the frame battery feed and ground return from the power distribution center. The FSP distributes the battery feed, by means of subsidiary fuses and feeds, to the shelves of the frame or bay in which it is mounted. The FSP also contains alarm


411-2831-010 Standard 18.05 April 2006

circuits.

FTAMFile transfer access and management (protocol).

FTNForwarded-To-Number

GInterface between VLRs using MAP/TCAP signaling over CCS7 SCCP and MTP.

GGSNGateway GPRS Support Node

GMSCGateway Mobile-services Switching center. A Mobile-service Switching Center provides an entry point into the Public Land Mobile Network (PLMN) from another network or service. A GMSC is capable of interrogating an HLR for incoming PLMN calls.

Ga The interface between the 3G-SGSN and the Charging Gateway Function (CGF).

GbThe RNS-SGSN interface is used to carry iPacket data transmission and mobility Management information. The Gb interface is defined in GSM 08.14, 08.16 and 08.18.

GIInterface between the GGSN and the internet.

GnThe interface between the 3G-SGSN and GGSN. The transport layer of the Gn interface is based on IP over ATM.

GrThis interface is used to exchange the data related to the location of the mobile station and to the management of the subscriber.

Gp The interface between an 3G-SGSN in one PLMN and a GGSN in a different PLMN. It is also the name of the interface between a 3G-SGSN and a SGSN in a different PLMN.



GPRSGeneral Packet Radio Service

GPRS-CSIGeneral Packet Radio Service-CAMEL Subscription Information

Gr The SS7 interface between the SIG and the HLR.

Group1. Individual UMTS Voice Core Network (VCN) registers with a common application are placed into logical groups. The group name, like the register name, is made up of a maximum of eight alphanumeric characters. It is this group name by which Operational Measurement (OM) data is identified for scheduling and request purposes.

2. A list of members or subgroups which are to be alerted sequentially. Each item (member or subgroup) in the list is associated with a time (indicating for how long alerting is to continue). If there is more than one item in the list a group type (single or multiple) must be specified.

GSMGlobal System for Mobile Communications. A digital cellular mobile telephone system composed of network elements that comply with the European Telecommunications Standards Institute (ETSI) SMG requirements and recommendations.

GSM-RGlobal System for Mobile Communications-Railways.

gsmSCFGSM Service Control Function

GSM/UMTS-coreGlobal System for Mobile Communications/Universal Mobile Communications System core module. The computing portion of GSM/UMTS SuperNode.

GSM/UMTS-MAPGlobal System for Mobile Communications/Universal Mobile Communications System Maintenance and Administration Position. Terminal connected the switch to allow interface to the switch.

GSM/UMTS MSCGlobal System for Mobile Communications/Universal Mobile Communications System Mobile-services Switching Center. A Northern Telecom product that offers


411-2831-010 Standard 18.05 April 2006

all of the functionality of a Mobile-services Switching Center (MSC) in a PLMN. GSM/UMTS-MSC also contains an integrated Visitor Location Register (VLR). See also MSC and VLR.

GSM/UMTS MSC/HLRA Northern Telecom product that offers all of the functionality of a Mobile-services Switching Center (MSC) and a Home Location Register (HLR) in a PLMN. It also includes an integrated Visitor Location Register and Authentication Center. See also MSC, HLR, VLR, and AUC.

GTPGeneral Packet Radio Service (GPRS) Tunneling Protocol. Protocol used to control IP tunnels between the RNC and the GGSN.

GTTGlobal Title Translation. The process that translates an application-specific address into the Common Channel Signaling Number 7 (CCS7) network address, usually that of the appropriate service control point.

GUIGraphical User Interface

HandoverThe process of transferring one user equipment involved in a call to another cell (target cell) in the PLMN. A handover can be initiated for any number of reasons including the degradation of the radio signal quality between the user equipment and the network. A range of handover scenarios exists, from a handover entirely within the same UMTS Terrestrial Radio Access Network (UTRAN) (when the call is transferred between cells in the same UTRAN) to a handover that involves two different Call Server (CS) (involving not only different UTRANs, but different CS).

HLRHome Location Register. A PLMN node that contains permanent subscriber data and dynamic data related to a Mobile Subscriber. The HLR provides a central repository of Mobile Subscriber information, supports call routing, and controls Supplementary Services.

HLR-100A Northern Telecom product that offers all of the functionality of a Home Location Register (HLR) in a PLMN. GSM/UMTS-HLR also contains an integrated Authentication Center (AUC). See also HLR and AUC.

HMEMHLR Memory Extension. An HLR architecture in the form of third party core (3PC) nodes, which enable the HLR subscriber capacity to be increased.



HotLine RoutingA Supplementary Service that directs all calls to a specified destination regardless of the dialed destination number.

HPLMNHome Public Land Mobile Network. The Public Land Mobile Network (PLMN) where a subscription is held and that contains the Home Location Register (HLR) of the subscriber.

IKIntegrity Key. Output from UMTS authentication algorithm.

IMSIInternational Mobile Subscriber Identity. A radio path subscriber identity of up to 15-digits that is used during signaling transactions between the piece of User Equipment (UE) and the fixed network to uniquely identify each UE. The format of an IMSI is: Mobile Country Code (MCC) plus Mobile Network Code (MNC) plus Mobile Subscriber Identity Number (MSIN).

IMEIInternational Mobile Equipment Identity. A unique number allocated to each individual mobile station equipment in the Public Land Mobile Network (PLMN) and implemented by the Mobile Subscriber (MS) manufacturer.

IMTInternational Mobile Telecommunications

IN(1) Intelligent Network. (2) Interrogating Node. A switching node that interrogates an Home Location Register (HLR) to route a call for a Mobile Station to the visited UMTS Voice Core Network Call Server/Home Location Register (VCN CS/HLR).

INAPIntelligent Network Application Part

INCInternational Carrier

Input/output controllerA UMTS Voice Core Network (VCN) equipment shelf that provides an interface between the central message controller and as many as 36 input/output devices. The input/output controller contains a peripheral processor that independently performs local tasks, thus relieving the load on the Central Processing Unit.


411-2831-010 Standard 18.05 April 2006

Integrated Service ModuleA single shelf unit that replaces the existing Trunk Module (TM) Shelves and the Maintenance Trunk Module (MTM) shelves. The ISM shelf provides 18 slots for TM and MTM service Circuit Packs (CPs) or Peripheral Module (PM) CPs.

InterfaceThe common boundary between two associated systems. A translator between unequal and dissimilar objects in a communications hierarchy.

Inter-LATAA general term that describes the services, revenues, and functions relating to telecommunications that originate inside one LATA and terminate either outside that LATA or inside another LATA.

Inter-PLMN roamingThe functionality that allows a Mobile Subscriber to originate and receive calls after it has roamed into a PLMN other than its home PLMN (HPLMN).

Interrogating nodeA switching node that interrogates an HLR to route a call for a user equipment to the visited VCN CS.

InterrogationThe method by which the Mobile Subscriber queries the VLR or VCN HLR100 for Basic Service and Supplementary Service information.

InterworkingThe general term used to describe the inter-operation of networks, services, and Supplementary Services. Interworking enables processes on different systems and networks to interact in a uniform way and carry out their tasks.

IntSSInterrogate Supplementary Service

IOCInput/Output Controller

IPInternet Protocol

IRIIntercept Related Information

ISCInform Service Center. A MAP operation.



ISDInsert Subscriber Data

ISDNIntegrated Services Digital Network. A set of standards developed by the Consultative Committee for International Telephony and Telegraphy (CCITT). These standards establish compatibility between the telephone network and new data terminals and devices, thereby providing an international standard for digital voice, data, and signaling transmissions.

ISMInvocation State Machine

ISUPIntegrated Services Digital Network (ISDN) User Part

ITUInternational Telecommunication Union

lcAn interface that links the Gateway Mobile Location Center (GMLC) to the GSM Service Control Function (gsmSCF) client

leAn interface that links the Gateway Mobile Location Center (GMLC) to the external Location Services (LCS) client

lgAn interface that links the Visiting Location Register (VLR) to the Gateway Mobile Location Center (GMLC)

lhAn interface that links the HLR to the Gateway Mobile Location Center (GMLC)

IuIu interface (Interface UMTS). It is between the Core Network and Access Network. The Core Network can be connected to different Access Networks using it (equivalent to A interface in GSM).

The Iu interface is split up into the following domains:• Iu CS (Circuit Switched) to the Circuit Domain• Iu PS (Packet Switched) to the Packet Domain.

IubIub interface (Interface UMTS Node B). It is between RNC and Node B. It allows


411-2831-010 Standard 18.05 April 2006

to connect RNC and Node B from different manufacturers because it is standardized.

Iu CSCircuit switched interface between the CS and RNS using the WG.

IU PSPacket switched interface between the CS and RNS using the WG.

IurThe Iur interface between two RNCs supports functions without having the Core Network involved.

IWFInnerWorking Function. Provides data interworking between networks.

Journal FileA UMTS Voice Core Networks (VCN) subsystem that provides facilities for recording Data Modification Order (DMO) information on tape or disk so that data tables can be restored if the switch should fail and require a system reload.

Kc64-bit maximum cipher key used to cipher signaling information and data.

KeyEach tuple of a UMTS Voice Core Network (VCN) table (the horizontal row) is identified by a key. The key is the first field name or field number 1.

K128-bit authentication key permanently assigned to the Third Generation (3G) subscriber. Input to UMTS authentication algorithm.

LALocation Area. An LA contains a group of cells with each cell belonging to one LA. LAs are used by the Core Network (CN) domain to get information on the user location when in the idle mode. One LA consists of a number of cells belonging to several Radio Network Controllers (RNCs) that are connected to the same CN node. The mapping between one LA and several RNCs is handled within the Call Server (CS) and the Visitor Location Register (VLR) owning the LA.

LATAA geographic area (known as an exchange or exchange area in the MFJ) where an operating company offers telecommunication services.



LCMLine Concentrating Module

LCSLocation Services

LCOLocal Calls Only. A Supplementary Service that prevents the Mobile Subscriber from making high toll calls. This is accomplished by only allowing the Mobile Subscriber to make calls to a specific set of destination numbers that are considered local. Calls terminating to destination numbers in high rate areas are denied.

LEALaw Enforcement Agencies

Link Peripheral ProcessorA UMTS Voice Core Network Call Server/Home Location Register (VCN CS/HLR) peripheral module (PM) cabinet that provides the signaling interface between the VCN CS/HLR and the Common Channel Signaling 7 (CCS7) signaling network. One Local Message Switch (LMS) shelf consists of two LMS units and frame bus hardware. Three Link Interface Shelves (LIS) each contain as many as 12 application specific units (ASUs), which may be link interface units or network interface units.

LISLink Interface Shelf. A shelf that contains Application Specific Units such as Link Interface Units for Common Channel Signaling 7 (LIU7s) and Network Interface Units (NIUs).

LIULink Interface Unit [part of Link Peripheral Processor (LPP)].

LIU7Link Interface Unit for Common Channel Signaling 7 (CCS7). An Application Specific Unit (ASU) in a Link Peripheral Processor (LPP) that processes messages entering and leaving an LPP through an individual signaling data link. Each LIU7 consists of a set of cards and a paddleboard provisioned in one of the Link Interface Shelves (LISs).

LMELocal Message Ericsson

LMSLocal Message Switch. A high-capacity communications hub that controls messaging between Application Specific Units in a Link Peripheral Processor


411-2831-010 Standard 18.05 April 2006

(LPP). An LMS also controls messaging between the LPP and the UMTS Voice Core Network (VCN)-bus component.

Location areaA subsection of a PLMN consisting of a specific number of adjacent cells. It is identified by its location area code (LAC).

Location area codeA 2-octet representation of a location area. Consists of the CS and MNC.

Log reportA message sent from a UMTS Voice Core Network (VCN) switch whenever a significant event has occurred in the switch or one of its peripherals. A log report includes state and activity reports as well as reports on hardware and software faults, test results, and other events or conditions likely to affect the performance of the switch. A log report can be generated in response to a system or manual action.

LPPLink Peripheral Processor

LTCLine Trunk Controller

MAPMobile Application Part. MAP is a set of CCITT Common Channel Signaling No. 7 (CCS7) protocols used to handle the special information transfer requirements of Mobile Subscribers in a PLMN. MAP defines the interfaces among network nodes.

Maintenance and Administration Position. A terminal that provides the UMTS Voice Core Network (VCN) Man-Machine Interface (MMI) between the wireless system and operating company personnel. The basic components of the MAP include a Visual Display Unit (VDU) with a keyboard, a voice communications module, and printers used in conjunction with the VDU

Mated pair StandbyAllows two geographically separate HLRs to provide mutual standby capability. When subscriber data is created or modified for each release, the mated pair service synchronization protocol requires updating to send the new data from the Active HLR to the Standby HLR.

MCTMalicious Call Trace

MemberOne of the group of subscribers associated with the pilot’s Extension service list. A



member is similar to a forwarded-to-number, and any MSISDN is applicable including that of the pilot.

Message SwitchA high-capacity communications facility that functions as the messaging hub of the UMTS Voice Core Network (VCN) SuperNode switch. The two message switch planes make up the VCN bus.

MIManagement Information

MilenageFramework of an authentication algorithm that is enhanced with the encryption engine, algorithm constants, and OP or OPc values and accepted by 3GPP.

MLCMobile Location Center

MMUMobility Management Unit

MNCMobile network code. A code identifying the home Public Land Mobile Network (PLMN) of the User Equipment (UE). A part of the International Mobile Subscriber Identity (IMSI).

Mobile StationEquipment intended to access a set of Public Land Mobile Network (PLMN) telecommunications services. The access may occur while in motion or during halts at unspecified points.

Mobile SubscriberThe individual or entity who obtains a service from a PLMN operator or an authorized agent and is responsible for payment of all charges and rentals due.

MO-LRMobile Originating-Location Request

MoUMemorandum of Understanding

MPCMultiple Point Code


411-2831-010 Standard 18.05 April 2006

MSCMobile services Switching Center

MSISDNMobile Subscriber Integrated Services Digital Network (ISDN) Number. A unique phone number that consists of the Country Code + National Destination Code + Subscriber Number. An MSISDN is allocated according to the CCITT E.164 numbering plan.

MSMobile Station. The mobile telephone set, including the network termination and user terminal capabilities.

Message switch. Part of GSM/UMTS SuperNode.

MSCMobile-services Switching Center

MSRNMobile Subscriber Roaming Number. A temporary number issued by the Visitor Location Register (VLR), upon demand by the Home Location Register (HLR), to a Mobile Subscriber when the Mobile Station roams into another VLR area. The HLR uses MSRNs to route calls to the Mobile Station. The format of the MSRN is Country Code of the visiting Public Land Mobile Network + National Destination Code (NDC) of the visited area + the code identifying the visited Call Server (CS) + the Subscriber Number allocated by the VLR.

MTCMobile Terminated Calls

MTDMagnetic Tape Drive. A 9-track tape unit used on various UMTS Voice Core Network (VCN) switches to store data.

MTMMaintenance Trunk Module. A peripheral module (PM) that contains special buses to accommodate test and service circuit cards for maintenance. The MTM provides an interface between the switching network and the test and service circuits.

MTPMessage Transfer Part. A connectionless transport system for Common Channel Signaling Number 7 (CCS7) that carries signaling messages between signaling points in the network.



MPT3Message Transfer Part level 3

MPTYMultiparty

MT-LRMobile Termination-Location Request

Multi-Party ServiceA service that allows Mobile Subscribers to make three-way conference calls by joining a held and an active call into one conference call using a conference bridge. Provisioning and Withdrawal of Multi-Party Service are the responsibility of the VCN HLR100.

NCOSNetwork Class of Service

NetworkA set of nodes and links that provides connections between two or more defined points so telecommunications can occur between them.

Network ServicesThe MTP and SCCP collectively.

NI-LRNetwork Induced-Location Request

NIUNetwork Interface Unit

NOANature of Address

No Reply Condition TimeThis identifier refers to a no reply condition time for the Call Forwarding on No Reply Supplementary Service.

NPDBNumber Portability Database. A database where the tillable numbers are independent of the home environment or serving network.

NPINumbering Plan Indicator


411-2831-010 Standard 18.05 April 2006

NSSNetwork and Switching Subsystem

NTPNorthern Telecom Publication. A customer publication that is part of a publication suite. An NTP contains descriptive information about Northern Telecom hardware and software products.

OA&MOperation, Administration, and Maintenance. All the tasks necessary for providing, maintaining, or modifying the services of a switching system. These tasks include provisioning of hardware, creation of service, verification of new service, and trouble recognition and clearance.

OAUOffice Alarm Unit. A peripheral module (PM) that is equipped with circuit cards that provide an interface with various types of office alarm circuits.

O-CSIOriginating-CAMEL Subscription Information

ODBOperator-Determined Call Barring

ODBBCCFMGTOperator-Determined Barring of Conditional Call Forwarding Subscriber Management

ODB BOICOperator-Determined Barring of Outgoing International Calls

OMOperational Measurements

ONPOne Night Process. A dump and restore process that transfers all the data in the database from the old software release to the new software release.

OPOperator Variant Algorithm configuration field. This is used to calculate the subscriber’s OPc values. A single OP value can be use to calculate a group of subscribers’ OPc values or a single subscriber’s OPc value.

OPcThis value is calculated from the OP value and the 3G subscriber’s K value. It is an



extra value to put into the Milenage framework.

Operator-Determined Call BarringA Service that allows network operators or service providers to regulate access to UMTS services by barring user equipment from certain categories of incoming calls, outgoing calls, and roaming.

OSSOperation Support System

O-TDPOriginating Trigger Detection Point

PIndicates that a Supplementary Service is Provisioned.

PCIPreferred Carrier Identifier

PCSProcess Control System

PDPermanent Data

PDMPhysical Data Move. Physical data is transferred to the other side and reformatted as it is written to the physical database instead of transferring every tuple individually and passing the tuple through the table control validations.

PDNPacket Data Networks

PDPPacket Data Protocols

Peripheral moduleA generic term referring to all hardware modules in the UMTS Voice Core Network (VCN) switch that provide interfaces with external line, trunk, or service facilities. A peripheral module contains peripheral processors that perform local routines, which relieve the load on the Central Processing Unit (CPU).

PilotNominated head of the Extension service group whose MSISDN is used to reach the group and holds the list of group members. The pilot may not be a member of


411-2831-010 Standard 18.05 April 2006

his/her own group. If s/he is not a member of his/her own group, s/he cannot receive calls from Nortel gateways supporting the Extension service.

PLMNPublic Land Mobile Network. A network established and operated by an administration or its licensed operator(s) that provides land mobile communications services to the public. A PLMN provides communication possibilities for mobile users; a Universal Mobile Telecommunications System (UMTS) PLMN is one that complies with the UMTS recommendations. Interworking with a fixed network is necessary for communication between mobile and fixed users.

PMPProvisioning Manager Process

PreSWACTPreSwitch of Activity

PRNProvide Roaming Number

ProtocolA strict procedure for communications between objects of equal rank in a communications hierarchy.

PSPacket Switch. The PS and Call Server (CS) domains make up the Core Network (CN).

PSIProvide Subscriber Information

PSTNPublic Switched Telephone Network. The worldwide voice telephone network accessible to all those with telephones and access privileges.

PUSSRProcess Unstructured Supplementary Service Request. This is an Unstructured Supplementary Service Data (USSD) message.

PWIPreside Wireless Interface

QoSQuality of Service



Quality of ServiceThe collective effect of service performances hat determine the degree of satisfaction of a user of a service such as operability, accessibility, retainability, and integrity performance.

RRandom Number. Indicates that a Supplementary Service is Registered.

RARouting Area. Routing Area. An RA contains a group of cells, each cell belonging to one RA. RAs are used by the Core Network Packet Switch domain to get information on the user location when in idle mode. One RA consists of a number of cells belonging to RNCs that are connected to the same CN node, that is. one 3G_SGSN. The mapping between one RA and Radio Network Controllers (RNCs) is handled within the Second Generation Serving GPRS Support Node. (SGSN) owning this RA.

RAIDRedundant Array of Independent (or Inexpensive) Disks

RANAPRadio Access Network Application Part. A portion of the interface between the UTRAN and Call Server/Home Location Register (CS/HLR) that contains all of the application layer procedures used on the interface.

RAND128-bit random number to be used as challenge in a challenge response protocol. Used by encryption algorithms. Input to UMTS authentication algorithm.

RDRestore Data

RDSReport SM-Delivery Status. A MAP operation.

RegisterA register is a software location that stores counts. UMTS Voice Core Network (VCN) register readings may take the form of peg count or usage values. Each register is given a unique name that is a term of up to eight alphanumeric characters.

RegistrationThe process a Mobile Station uses to inform the network of its current location. This process also informs the home switch of the Mobile Subscriber’s location.


411-2831-010 Standard 18.05 April 2006

RegSSRegister Supplementary Service

ReportResponse from either the network or the recipient upon a short message being sent from either a Service Center or a Mobile Station. A report may be a delivery report, which confirms the delivery of the short message to the recipient. It could also be a failure report, which informs the originator that the short message was never delivered and identifies the reason why.

RFSMReady for SM. A MAP operation.

RijndaelThis is the Advanced Encryption Standard (AES) cipher that replaces the Data Encryption Standard (DES) cipher. It is a block-cipher with a 128-bit, block size and is used as part of the Milenage Authentication Algorithm.

RNCRadio Network Controller.The equipment in the RNS in charge of controlling the use and integrity of the radio resources.

RNSRadio Network Subsystem. Either a full network or only the access part of a UTRAN offering the allocation and the release of specific radio resources to establish a way to connect between the User equipment (UE) and the UMTS Terrestrial Radio Access Network (UTRAN).

Roaming RestrictionsThe VCN HLR100 mechanism that allows the operator to define the Visitor Location Registers (and thus the areas and PLMNs) to which a Mobile Subscriber may and may not roam.

RoutesetA logical group of Common Channel Signaling Number 7 (CCS7) signaling paths with the same destination point.

RSRegistration Status. This indicates whether a subscriber has registered for a Supplementary Service.

SIndicates that a Supplementary Service is Suppressed.



SCService Center. A network entity that is responsible for the relaying and store-and-forwarding of a short message between a Short Message Entity and a Mobile Station. The SC is not part of the Public Land Mobile Network.

SCSuper Charger

SCCPSignaling Connection Control Part. A level of Common Channel Signaling Number 7 (CCS7) layered protocol. The main functions of the SCCP include the transfer of signaling units with or without the use of a logical signaling connection and the provisioning of flexible Global Title Translations (GTTs) for different applications.

SCFService Control Function

SCINFOThe "Subscriber Capacity Information" CI command which displays information about the subscriber capacity feature

SCSISmall Computer System Interface. A disk drive control technology.

SDCSystem Data Cache

SDMSupernode Data Manager

SDM/FTSuperNode Data Manager/Fault Tolerant

Service AreaA geographical region that offers (by the definition of the service provider) a homogeneous dial plan for all users within it.

SGSignaling Gateway. The Signaling Gateway processes the protocol layers that are involved in the transport of circuit and packet signaling between the UMTS Access Network and either the 3G-MSC/Call Server or the 3G-SGSN.

The SG provides an Iu signaling link between the Core Network (3G-MSC and 3G-SGSN) and Access networks (RNC). The SG also provides an SS7 interface between the 3G-MSC and SG to relay signaling messages.


411-2831-010 Standard 18.05 April 2006

SGSNServing GPRS Support Node

Signaling networkSS7 Level 3 protocol enabling data messages and control information to be exchanged between non-adjacent signaling points, and any Mobile Subscriber related information that plugs into Mobile Stations.

SIMSubscriber Identity Module. A removable portion of a Mobile Station within the Universal Mobil Telecommunications System (UMTS) architecture. It contains user identity, security, and subscriber information.

SLMSystem Load Module. A mass storage system in a UMTS Voice Core Network (VCN) SuperNode processor that stores office images. From the SLM, new loads or stored images can be booted into the Computing Module (CM).

SOCSoftware Optionality Control

SRLSend Routing Information for Location Service (LCS)

SMShort Message. Information that may be conveyed by means of the Short Message Service.

SMEShort Message Entity. An entity that may send or receive short messages. The SME may be located in a fixed network, a Mobile Station or a Service Center.

SMSShort Message Service. The means of transferring messages in a PLMN. Messages are transferred between Mobile Stations and a short message entity in a service center.

SMS-CSIShort Message Service-CAMEL Subscription Information

SMS-GatewayGateway Call Server (CS) for Short Message Service. A CS capable of receiving a short message from a Service Center, interrogating an HLR for routing information and SMS information, and delivering the short message to the Visited Call Server of the recipient Service Center.



SMS-IWMSCInterworking Call Server (CS) for Short Message Service. A CS capable of receiving a short message from within the Public Land Mobile Network and submitting it to the recipient Service Center.

SMS-SCShort Message Service Center. The entity in a Public Land Mobile Network that acts as a storage and forwarding center for short messages.

SNSEUMTS Voice Core Network (VCN) SuperNode Size Enhanced. The SNSE combines the core elements of the VCN SuperNode architecture in a single cabinet. The two major components of VCN SuperNode are VCN core and VCN bus. VCN bus consists of dual Message Switch shelves; VCN core consists of a Computing Module (CM) shelf and a System Load Module (SLM) shelf.

SQNSequence Number. Input to UMTS authentication algorithm.

SRESSigned Response. Response to a challenge in a challenge response protocol. Used in authentication.

SRISend Routing Information. A MAP operation.

SRI-AckSend Routing Information Acknowledge. A message sent to the GSMC if the terminating triggering criteria are met

SRI-SMSend Routing Information for Short Message. A MAP operation.

SRMSend Routing Information for Short Message. A MAP operation.

SSSupplementary Service

SS BOICSupplementary Services Barring of Outgoing International Calls Except those directed to the Home PLMN Country

SS BOICEXHCSupplementary Services Barring of Outgoing International Calls


411-2831-010 Standard 18.05 April 2006

SS-CSISupplementary Services DATA CAMEL Subscription Information

STPSignaling Transfer Point

SubscriberMobile Subscriber

Subscriber DataThe ASN.1 identifier that exists as part of the Insert Subscriber Data Message and the Send Parameters result message. This identifier refers to all the data attached to a subscriber that have to be known in the VLR.

Sun MCSun Management Center

SuperNodeUMTS Voice Core Network (VCN) SuperNode. A high-capacity switch used in Northern Telecom’s wireless systems. The two major components of VCN SuperNode are VCN core and VCN bus. The VCN bus consists of dual Message Switch shelve. The VCN core consists of a Computing Module (CM) shelf and a System Load Module (SLM) shelf.

Supplementary ServicesA modification of or a supplement to a basic telecommunication service. Examples include call waiting and call barring.

SVR7CCS7 Server (peripheral module)

SWACTSwitch of Activity

TableData associated with UMTS Voice Core Network (VCN) hardware and VCN software systems are stored in tables. Tables are two-dimensional entities consisting of horizontal rows (tuples) and vertical columns that identify fields of tuples.

TCAPTransaction Capabilities Application Part. A service that provides a common protocol for remote operations across the Common Channel Signaling Number 7 (CCS7) network. The protocol consists of message formatting, content rules, and exchange procedures.



T-CSITerminating-CAMEL Subscription Information

TCP/IPTransmission Control Protocol/Internet Protocol

TDTemporary Data

TDPTrigger Detection Point. A particular point in the call on the switch

TDP-RTrigger Detection Point-Request

T-TDPTerminating Trigger Detection Point

TeleserviceA type of telecommunication service that provides the complete capability, including terminal equipment functions, for communication between users according to protocols established by agreement between administrations and service providers. Examples include Teletex, Videotex, and emergency calls.

TIFTranslations Information Flag. Suppresses UMTS checks that are applied to Call Forwarding numbers when the subscriber is provisioned with Originating CAMEL Subscription Information (O-CSI)

TIF-CSITranslations Information Flag-CAMEL Subscription Information

TMSITemporary Mobile Subscriber Identity. A unique identity temporarily allocated to visiting Mobile Subscribers in order to support the subscriber identity confidentiality service. The TMSI has only local significance within a specific Visitor Location Register (VLR) and is used to support subscriber identity confidentiality. It is an abbreviated form of the International Mobile Subscriber Identity (IMSI).

TransceiverA transmitter-receiver unit that handles radio communications for the Base Transceiver Station (BTS). A BTS may contain several transceivers.


411-2831-010 Standard 18.05 April 2006

TranslationThe process in which dialed digits are converted into information that enables a call to be routed to the correct destination by the system.

TRAUTranscoding and Rate Adaptation Unit. A device that takes UMTS speech packets and converts them into standard ISDN 64 kbps speech packet.

TRINODEAn office configuration involving a MSC/VLR, HLR and STP (now known as a Combined MSC/HLR)

TrunkInterconnection of telephone switching centers that contain numerous shared telephone circuits.

TSTechnical Specification

U-CSIsubscriber Unstructured Supplementary Service Data CAMEL Subscription Information. Used to forward PUSSR messages to different nodes on a per subscriber basis

UDIUnrestricted Digital Information

UDPProtocol to control the connectionless datagram communications.

UEUser Equipment. The user access point to the system. Provides the user a method to speak and receive or transmit data.

UG-CSIUSSD General CAMEL Subscription Information. Used to forward PUSSR messages to different nodes on a per HLR basis

UGLUpdate GTP Location message

ULUpdate Location. This operation is invoked from the VLR to the VCN HLR100 when the Mobile Station moves into a new VLR area or turns on the handset, or after a Reset.



Um interfaceThe radio interface between the Base Station System and the Mobile Station.

UMTSUniversal Mobile Telecommunications System. A digital cellular mobile telephone system composed of network elements that comply with the European Telecommunication Standards Institute (ETSI) SMG requirements and recommendations.

UMTS authentication algorithmA Universal Mobile Communications System (UMTS) algorithm that provides security.

UMTS authentication algorithm with Milenage/Rjindael frameworkA Universal Mobile Communications System (UMTS) algorithm that allows the operator to configure parameters used internally to provide an extra layer of security.

UMTS BCUniversal Mobile Telecommunications System Bearer Capability.

USIMUser Services Identity Module

UUS1User-to-User Signaling, Type 1

USSDUnstructured Supplementary Service Data

USSD CSIUnstructured Supplementary Service Data CAMEL Subscription Information

USSNUnstructured Supplementary Service Notify

USSRUnstructured Supplementary Service Request

UTRANUMTS Terrestrial Radio Access Network

Uu interfaceThis interface is used between Node B and UE. It is dependent from the technology used on the radio (it can be WCDMA or TD/CDMA for example).


411-2831-010 Standard 18.05 April 2006

VBSVoice Broadcast Service

VCHVoice Channel. A Radio Frequency (RF) channel used to transmit cellular voice conversations. The VCH is also an integral part of call setup, handover, and disconnect.

VCN coreUMTS Voice Core Network core module. The computing portion of VCN SuperNode.

VCN CSUMTS Voice Core Network Call Server. A Northern Telecom product that offers all of the functionality of a Call Server (CS) in a PLMN. VCN CS also contains an integrated Visitor Location Register (VLR). See also CS and VLR.

VCN CS/HLRA Northern Telecom product that offers all of the functionality of a Call Server (CS) and a Home Location Register (HLR) in a PLMN. It also includes an integrated Visitor Location Register and Authentication Center.

VCN HLR100UMTS Voice Core Network Home Location Register. A Northern Telecom product that offers all of the functionality of a Home Location Register (HLR) in a PLMN. VCN HLR100 also contains an integrated Authentication Center (AUC). See also HLR and AUC.

VCN MAPUMTS Voice Core Network Maintenance and Administration Position. Terminal connected the switch to allow interface to the switch.

VGCSVoice Group Call Service

Virtual Home EnvironmentA concept for personal service environment portability across network boundaries and between terminals. Uses standards such as Customized Application for Mobile network Enhanced Logic (CAMEL).

Visitor Location RegisterThe location register where all relevant parameters concerning a Mobile Station are stored as long as the Mobile Station is in a location area controlled by this register.



VLRVisitor Location Register

VMGVirtual Media Gateway. The VMG provides the Transcoding and Rate Adaptation Unit (TRAU) and Echo Cancellation functionality for the Core Network Circuit Domain. The VMG also handles the allocation and call setup of the Circuit Domain Bearer Channel because it implements the Q.2630 and Q.2150 protocols.

VPLMNVisited Public Land Mobile Network. A Public Land Mobile Network (PLMN) to which the User Equipment (UE) has roamed and is not the HPLMN of the UE.

WGWireless Gateway. The Wireless Gateway (WG) is a common Iu interface termination point for PS (Packet) Switched) and CS (Circuit Switched) domains.

The Wireless Gateway provides signaling and bearer services across both Circuit Domain and Packet Domains and provides communication between the Core Network (CN) and Access Networks (AN). The WG is actually part of both the 3G-MSC and the 3G-SGSN according to the Third Generation (3G) standards definitions.

The functional elements of the WG are as follows:

3G-SGSN

Signaling Gateway (SG)

Virtual Media Gateway (VMG)

Aggregation Node (AN)

X.25Packet Data Switching Protocol. Defines the interaction between a DTE and a DCE of a packet switching network.

XA-CoreExtended Architecture Core. A new multi-processor, RISC based architecture for the VCN Core SuperNode computing engine. Fully compatible with existing SuperNode and SuperNode SE based products. The XA-Core platform is a direct replacement for the VCN Core CM, SLM, backplane, and like components.

XRESExpected Response. Output from UMTS authentication algorithm.


411-2831-010 Standard 18.05 April 2006

test

Family Product Manual Contacts Copyright Confidentiality Legal

GSM / UMTS

HLR100Product Guide

To order documentation from Nortel Global Wireless Knowledge Services, call (1) (877) 662-5669

To report a problem in this document, call(1) (877) 662-5669or send e-mail from the Nortel Customer Training & Documentation World Wide Web site athttp://www.nortel.com/td

Copyright © 1993–2006 Nortel, All Rights Reserved

NORTEL CONFIDENTIAL

The information contained herein is the property of Nortel and is strictly confidential. Except as expressly authorized in writing by Nortel, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel, the holder is granted no rights to use the information contained herein.

Information is subject to change without notice. Nortel reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant.

GSM is a trademark of GSM MOU Association. Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.Document number: 411-2831-010Product release: GSM18 / UMTS04Document version: Standard 18.05Date: April 2006Printed in the United States of America

Documents

411-2831-010.18.05 GSM / UMTS HLR100 Product Guidewillowcherry.com/wp-content/uploads/2013/12/411-2831-010.18.05.pdfGSM / UMTS HLR100 Product Guide ... (CCN HLR) Product Guide for