Vous êtes sur la page 1sur 360

411-2831-332

GSM NSS/UMTS CCN

HLR200
Subscriber Data Model
GSM18/UMTS04 Preliminary 01.02 March 2005

Preliminary
Whats inside...
You will find a comprehensive reference to the HLR Subscriber Data Model, its components and their validations. You will be able to see an overview of the HLR subscriber profile and its components, and look up details of all the components, their dataitem syntax and validations, and also details of all the items in the Oracle subscriber profile database.

test

GSM NSS/UMTS CCN

HLR200
Subscriber Data Model

Document number: 411-2831-332 Product release: GSM18/UMTS04 Document version: Preliminary 01.02 Date: March 2005

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright

19962005 Nortel, All Rights Reserved


NORTEL CONFIDENTIAL

Printed in the United States of America/Canada

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, the Globemark, and Unified Networks are trademarks of Nortel. 3rd Party Trademark A-N Additional 3rd party trademark A-N 3rd Party Trademark O-Z Additional 3rd party trademark O-Z Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.

iv Nortel Confidential

Copyright

19962005 Nortel

The following apply to components or elements used in the GEM load and are used by permission of the respective owners. Copyright notice/license for Perl Preamble The intent of this document is to state the conditions under which a Package may be copied, such that the Copyright Holder maintains some semblance of artistic control over the development of the package, while giving the users of the package the right to use and distribute the Package in a more-or-less customary fashion, plus the right to make reasonable modifications. Definitions: Package refers to the collection of files distributed by the Copyright Holder, and derivatives of that collection of files created through textual modification. Standard Version refers to such a Package if it has not been modified, or has been modified in accordance with the wishes of the Copyright Holder as specified below. Copyright Holder is whoever is named in the copyright or copyrights for the package. You is you, if you're thinking about copying or distributing this Package. Reasonable copying fee is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on. (You will not be required to justify it to the Copyright Holder, but only to the computing community at large as a market that must bear the fee.) Freely Available means that no fee is charged for the item itself, though there may be fees involved in handling the item. It also means that recipients of the item may redistribute it under the same conditions they received it. 1. You may make and give away verbatim copies of the source form of the Standard Version of this Package without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers. 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domain or from the Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

3. You may otherwise modify your copy of this Package in any way, provided that you insert a prominent notice in each changed file stating how and when you changed that file, and provided that you do at least ONE of the following: a. place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site such as uunet.uu.net, or by allowing the Copyright Holder to include your modifications in the Standard Version of the Package. b. use the modified Package only within your corporation or organization. c. rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from the Standard Version. d. make other distribution arrangements with the Copyright Holder. 4. You may distribute the programs of this Package in object code or executable form, provided that you do at least ONE of the following: a. distribute a Standard Version of the executables and library files, together with instructions (in the manual page or equivalent) on where to get the Standard Version. b. accompany the distribution with the machine-readable source of the Package with your modifications. c. give non-standard executables non-standard names, and clearly document the differences in manual pages (or equivalent), together with instructions on where to get the Standard Version. d. make other distribution arrangements with the Copyright Holder. 5. You may charge a reasonable copying fee for any distribution of this Package. You may charge any fee you choose for support of this Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own. You may embed this Package's interpreter within an executable of yours (by linking); this shall be construed as a mere form of aggregation, provided that the complete Standard Version of the interpreter is so embedded.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

vi Nortel Confidential

Copyright

19962005 Nortel

6. The scripts and library files supplied as input to or produced as output from the programs of this Package do not automatically fall under the copyright of this Package, but belong to whoever generated them, and may be sold commercially, and may be aggregated with this Package. If such scripts or library files are aggregated with this Package via the socalled "undump" or "unexec" methods of producing a binary executable image, then distribution of such an image shall neither be construed as a distribution of this Package nor shall it fall under the restrictions of Paragraphs 3 and 4, provided that you do not represent such an executable image as a Standard Version of this Package. 7. C subroutines (or comparably compiled subroutines in other languages) supplied by you and linked into this Package in order to emulate subroutines and variables of the language defined by this Package shall not be considered part of this Package, but are the equivalent of input as in Paragraph 6, provided these subroutines do not change the language in any way that would cause it to fail the regression tests for the language. 8. Aggregation of this Package with a commercial distribution is always permitted provided that the use of this Package is embedded; that is, when no overt attempt is made to make this Package's interfaces visible to the end user of the commercial distribution. Such use shall not be construed as a distribution of this Package. 9. The name of the Copyright Holder may not be used to endorse or promote products derived from this software without specific prior written permission. 10. This package is provided as is and without any express or implied warranties, including, without limitation, the implied warranties of merchantability and fitness for a particular purpose. The standard version of the Perl interpreter is obtained from the following link: http://www.perl.com/pub/a/language/info/software.html Copyright notice/license for Zlib library for data compression (C) 1995-1998 Jean-loup Gailly and Mark Adler This software is provided as-is, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

vii

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly: jloup@gzip.org Mark Adler: madler@alumni.caltech.edu

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

viii Publication history Nortel Confidential

Copyright

19962005 Nortel

Publication history
March 2005 GSM18.0/UMTS04, 01.02. This is the first published version of this document for the preliminary release of Nortel HLR200 solution (NSS18). November 2004 GSM18.0/UMTS04, 01.01. This is the first draft of this document for the preliminary release of the Nortel HLR200 solution (NSS18).

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

ix

Contents
About this document
Definition of audience xiii Document structure xiii How to use this document xiv Key concepts xv Mated pair xv Related documents & references

1
xiii

xv

Chapter 1: Introduction
17 Profile graphical representation 20 Data model and validations 31

17

Chapter 2: Component descriptions


Authentication data 41 Profile control data introduction 44 Barring control 45 Category 46 IMSI Status 49 LMU (Location Measurement Unit) 51 NAM (Network Access Mode) 52 Password 53 Roaming Entitlement 54 SOAPROV 55 Basic Services Introduction 56 ALTSPCDA (Alternate Speech / CDA Data) 59 ALTSPCDS (Alternate Speech / CDS Data) 61 ALTSPFAX (Alternate Speech / Fax Group 3) 63 AUXTPHNY (Auxiliary Telephony) 65 CDA (Circuit Duplex Asynchronous Data) 67 CDA300 (Circuit Duplex Asynchronous Data 300) 68 CDA1200 (Circuit Duplex Asynchronous Data 1200) 70 CDA1275 (Circuit Duplex Asynchronous Data 1275) 72 CDA2400 (Circuit Duplex Asynchronous Data 2400) 74 CDA4800 (Circuit Duplex Asynchronous Data 4800) 76 CDA9600 (Circuit Duplex Asynchronous Data 9600) 78 CDAGBS (Circuit Duplex Asynchronous Data General Bearer Service) GSM NSS/UMTS CCN

41

80

HLR200 Subscriber Data Model GSM18/UMTS04

x Contents Nortel Confidential

Copyright

19962005 Nortel

CDS (Circuit Duplex Synchronous Data) 82 CDS1200 (Circuit Duplex Synchronous Data 1200) 83 CDS2400 (Circuit Duplex Synchronous Data 2400) 85 CDS4800 (Circuit Duplex Synchronous Data 4800) 87 CDS9600 (Circuit Duplex Synchronous Data 9600) 89 CDSGBS (Circuit Duplex Synchronous Data General Bearer Service) 91 FAX3 (Facsimile Group 3) 93 SMMO (Short Message Mobile Originating) 95 SMMT (Short Message Mobile Originating) 97 SPCHCDA (Speech followed by CDA Data) 99 SPCHCDS (Speech followed by CDS Data) 101 TPHNY (Telephony) 103 VBS (Voice Broadcast Service) 105 VGCS (Voice Group Call Service) 106 Supplementary Services introduction 107 ACC (Accounting Codes) 109 ACRJ (Anonymous Call Rejection) 110 AOCC (Advice of Charge Charging) 111 AOCI (Advice of Charge Information) 112 BAIC (Barring of All Incoming Calls) 113 BAOC (Barring of All Outgoing Calls) 115 BICRoam (Barring of Incoming Calls when Roaming outside HPLMN country) 117 BOIC (Barring of Outgoing International Calls) 119 BOICexHC (Barring of Outgoing International Calls except to HPLMN Country) 121 CFB (Call Forward when Busy) 123 CFNRc (Call Forward when Not Reachable) 130 CFNRy (Call Forward when No Reply) 136 CFU (Call Forward Unconditionally) 143 CLIP (Calling Line ID Presentation) 150 CLIR (Calling Line ID Restriction) 151 CNAM (Calling Name Delivery) 152 COLP (Connected Line ID Presentation) 153 COLR (Connected Line ID Restriction) 154 COS (Class of Service) 155 CUG (Closed User Groups) 158 CUG Subscription (Closed User Groups Subscription) 159 CUG Feature (Closed User Groups Feature) 161 CW (Call Waiting) 164 ECT (Explicit Call Transfer) 166 EMLPP (Enhanced Multi Level Precedence & Pre-emption) 167 EXT (Extension Services) 168 FM (Follow Me) 175 HOLD (Call Hold) 177 HOTBILL (Hot Billing) 178 LCO (Local Calls Only) 179 MCT (Malicious Call Trace) 180 MPTY (Multiparty) 181 UUS1 (User to User Signalling stage 1) 182 WPS (Wireless Priority Service) 183 ODBs (Operator Determined Barrings) 184 CAMEL services introduction 186 411-2831-332 Preliminary 01.02 March 2005

Nortel Confidential

Copyright

19962005 Nortel

Contents

xi

D-CSI (Dialled CSI) 187 GPRS-CSI (General Packet Radio Service CSI) 189 M-CSI (Mobility Management CSI) 192 O-CSI (Originating CSI) 193 SMS-CSI (Short Message Service CSI) 201 SS-CSI (Supplementary Service CSI) 203 T-CSI (Terminating CSI) 204 TIF-CSI (Translations Information Flag CSI) 209 USSD-CSI (Unstructured Supplementary Service Data CSI) 210 Location Services (LCS) Introduction 211 LCS Autonomous Self Location 212 LCS Basic Self Location 213 LCS Call Related 214 LCS Call Unrelated 216 LCS GMLCs 218 LCS PLMN Operator 219 LCS Transfer to Third Party 221 LCS Universal 222 GPRS (General Packet Radio Service) 223 Other Services introduction 229 CLIN (Calling Line Identification Replacement Number) 230 EA (Equal Access) 231 Proprietary IN (Proprietary Intelligent Network service) 232 Other components introduction 233 HST (Home Subscriber Trace) 234 SIMR (SIM Replacement) 235

Chapter 3: Suppression States


BICRoam suppression state determination 241 CFB suppression state determination 241 CFNRc suppression state determination 242 CFNRy suppression state determination 242 CFU suppression state determination 243 EXT suppression state determination 244 ODB BICRoam suppression state determination 244 ODB BAOCRoam suppression state determination 245 ODB HPLMN specific sategories suppression state determination 246

239

245

Appendix A: Oracle implementation


Datatypes in Oracle 247 Section Structure 251 Schema tables listing and diagram 252 Guide to table sections 256 Table SUB_AUTH 258 Table SUB_GENERAL 259 Table SUB_ODBS 262 Table SUB_BASIC_SERVICES 264 Table SUB_BAIC 265 Table SUB_BAOC 267

247

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

xii Contents Nortel Confidential Table SUB_BICROAM 269 Table SUB_BOIC 271 Table SUB_BOICEXHC 273 Table SUB_CFB 275 Table SUB_CFNRC 277 Table SUB_CFNRY 279 Table SUB_CFU 281 Table SUB_COS 283 Table SUB_CUG_FEATURE 285 Table SUB_CUG_SUBSCRIPTION 287 Table SUB_CW 289 Table SUB_EXT 291 Table SUB_IMSI_SS 294 Table SUB_DCSI 297 Table SUB_GPRS_CSI 299 Table SUB_MCSI 301 Table SUB_OCSI 302 Table SUB_SMS_CSI 309 Table SUB_SS_CSI 310 Table SUB_TCSI 311 Table SUB_USSD_CSI 315 Table SUB_CLIN 317 Table SUB_EA 318 Table SUB_GPRS_PROV 319 Table SUB_GPRS_PDPS 320 Table SUB_LCS_CALL_RELATED 321 Table SUB_LCS_CALL_UNRELATED 324 Table SUB_LCS_GMLCS 327 Table SUB_LCS_MOBILE_ORIGINATING 329 Table SUB_LCS_PLMN_OPERATOR 331 Table SUB_LCS_UNIVERSAL 333 Table SUB_VBS 334 Table SUB_VGCS 339 Table SUB_SIMR 342 Routing Schema 343

Copyright

19962005 Nortel

Glossary of terms

347

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

xiii

About this document

This document details the HLR subscriber data model, specifically provisionable permanent profile data. The profile is made up of a primary ID and profile components, which may or may not have dataitems. Every dataitem has syntax rules, which must be adhered to. Dataitems within a component may interact with each other, often referred to as intra-component or intra-service validations (the vast majority of components are services). Components or their dataitems may interact with other components or their dataitems; these are often referred to as inter-component or inter-service validations . Some components also interact with system data. Some components also have provisioning side-effects. This document details all of these data model characteristics.

Audience
This publication is written as a detailed guide to the HLR subcriber data model and its validation, including a detailed reference of the Oracle database implementation. It is intended for any person involved in the planning, engineering, administration or maintenance of the HLR.

Document structure

Chapter 1: Introduction, gives a brief introduction to the profile and the section Profile graphical representation on page 1-20 shows the profile components in several figures. The concept of data sets is introduced. The section Data model and validations on page 1-31 introduces the data model and its components. The profile components are listed in full (Table 1-1) and introductions are given to the datatypes and validations. Chapter 2: Component descriptions is the main section in the document, and describes in detail the data model and its validations. It contains a section by section description of the components, including introduction to various component groups (e.g. basic services). Datafill subsections give each components dataitems, their syntax rules and their intra-service interactions. Interactions subsections give system data interactions, service-service interactions and provisioning side-effects.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

xiv About this document Nortel Confidential

Copyright

19962005 Nortel

Chapter 3: Suppression States details suppression state determination for those services that have a suppression state. Such states are not part of the profile, but are determined in part by the profile, so are given here. Appendix A: Oracle implementation is the detailed reference of the Oracle implementation of the subscriber profile. The Oracle schema is introduced, including the implementation of vectors and sets in the relational database. The schema tables are both listed (Table A-4 on page A-252) and given in a diagram (Figure A-1 on page A-255), followed by sections detailing each table in the schema. A guide to these sections is included (section Guide to table sections on page A-256). General table information is given (such as what the primary key is), along with syntax descriptions of each column, with examples. Glossary of terms is a comprehensive glossary of all acronyms and abbreviations used in the profile.

How to use this document


This document is primarily a reference of the data model and its validations, hence is useful for looking up services, their dataitem syntax, validations etc. -- use Chapter 1, Data model and validationsstarting on page 1-31 and then Chapter 2: Component descriptions. The profile components are listed in Table 1-1 on page 1-31.

A reference of the Oracle schema is given in Appendix A: Oracle implementationstarting on page A-247, with a schema table listing in Table A-4 on page A-252. A guide to the schema descriptions is given in Guide to table sections on page A-256 using an example table. The routing schema is given in Routing Schema on page A-343. A graphical representation of the profile is given in Chapter 1, Profile graphical representation starting on page 1-20. This is useful to get an overview of what the profile is; what types of profile components exist, and what they all are. A good starting point is the introduction to profiles in Chapter 1. Various component groups are introduced in Chapter 2: profile control data on page 244, basic services on page 2-56, supplementary services on page 2-107, CAMEL services on page 2-186, location services on page 2-211, other services on page 2-229 and other components on page 2-233.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

About this document xv Copyright 19962005 Nortel

Key concepts
The following definitions are useful to help read the rest of the document.

1
HLR Subscriber Profile: provisionable permanent subscriber data, encompassing profile components such as authentication data and various services. It does not include temporary data such as location data and service suppression states. Profile Components: various components make up the subscriber profile. A profile component is a generic term to describe a logical unit of subscriber data. An example component is authentication data. Many components can be subcategorised; for example, many components are services, which themselves can be subcategorised, into basic services for example. Components are units that are explicitly provisioned, for example the provisioning protocol allow you to provision Service X (you do not provision dataitem Y and dataitem Z). Dataitem: a single piece of data: a text string, a boolean etc. Provisioning: the ability to manage HLR data in terms of adding data, modifying data and deleting data. In the context of this document, provisioning refers to management of subscriber profile data. System Data: that data that is keyed by some entity other than a subscriber ID. For example, the algorithms system table is keyed by an algorithm centre node number.

Mated pair

1
This document does not contain any information relating to HLR mated pair functionality. Note that this functionality adds dataitems to the data model and enforces additional validations. Please refer to the mated pair documentation for details on this functionality.

Related documents & references

The following documents are useful to read or reference in conjunction with this document. GSM18 HLR Customer Data Schema NTP, 411-2831-451 (for reference of system tables only) GSM18 HLR Office Parameters Reference Manual NTP, 411-2831-510

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

xvi About this document Nortel Confidential

Copyright

19962005 Nortel

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

1-17

Chapter 1: Introduction

1
1

The subscriber profile is essentially composed of a primary ID and a collection of profile components. A component is a logical group of data/ functionality. Components may be mandatory or optional, may or may not have datafill, and may be a distinct are of functionality or relate to the profile as a whole (these latter items are called profile control components). A group of optional components called basic services have a secondary ID as one of their dataitems. These IDs can be shared across a subscribers basic services, but cannot be shared across subscribers. A high level view of the profile is given in Figure 1-1 on page 1-18. The top box shows a very general view of the subscriber profile. The second box expands on the type of components that exist. Some components are mandatory, namely Authentication data and Profile Control components. The primary ID is also mandatory, although secondary IDs are optional. All optional components have a provisioned state, to indicate whether they are present or not. This state is not explicitly included in the data syntax tables in Chapter 2: Component descriptions of this document, as this state exists even if the subscriber does not have the component (i.e. it is set to false).

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-18 Chapter 1: Introduction Nortel Confidential

Copyright

19962005 Nortel

Figure 1-1 Subscriber Profile high level view

SUBSCRIBER

ID

The primary ID

PROFILE COMPONENTS

COMPONENT DATAFILL

The subscriber profile is a collection of mandatory and optional components, many have datafill, although not all.

Authentication data is the primary component and defines the existence of a subscriber Profile Control data are distinct mandatory components that help define the subscribers profile. e.g. IMSI Status Service data components are the individual services which have been provisioned to the subscriber. They are all optional. e.g. BAOC A component that doesnt fit into Profile Control or Service categories. e.g. SIMR and HST

SUBSCRIBER

IMSI

PROFILE COMPONENTS

Authentication Data Profile Control Data Service Data

Other Component

The profile components are further detailed in Figure 1-2 on page 1-19. For service data, the different service classifications are given, rather than the individual services. The profile is further described in several figures in the next section. The data model and its validations are given in full detail in Data model and validations starting on page 1-31.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 1: Introduction 1-19 Copyright 19962005 Nortel

Figure 1-2 Subscriber Profile components

AUTHENTICATION DATA

Authentication Data

PROFILE CONTROL DATA

SERVICE DATA

Barring Control Category IMSI Status

ODBs Basic Services Supplementary Services

LMU NAM Password Roaming Entitlement SOAPROV Other Services CAMEL Services Location Services GPRS

OTHER COMPONENTS

SIMR HST

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-20 Chapter 1: Introduction Nortel Confidential

Copyright

19962005 Nortel
1

Profile graphical representation

The subscriber profile encompasses a large number of components. These components are described in detail (see Data model and validations on page 1-31 and Chapter 2: Component descriptions). However, this section provides a graphical representation of the profile components. Each component is given, together with an indication of whether the component is mandatory or optional, and a high-level view of its dataitems. Individual dataitems are not indicated, but instead are grouped into set data and other data (non-set data). Where a component has no dataitems this is indicated. An introduction to the graphical representation is given in Figure 1-4 on page 1-22, with the components illustrated from Figure 1-5 to Figure 1-12. More information on sets is given in Data sets below. Data sets A component is essentially a logical group of dataitems. Within a component there are often further logical groups of data -- these are called sets. A set is usually optional, having a provisioned state much like that of optional components. Not all dataitems belong to a set, these are given the awkward description of non-set data. The syntax tables in Data model and validations on page 1-31 and in Chapter 2: Component descriptions indicate components sets, and the dataitems they contain (sets are named). Note that the optional column has a slightly different meaning for those dataitems in a set. It indicates that the dataitem is optional if the set is provisioned. If the set is not provisioned, then none of the dataitems will be datafilled, so they are all optional in a wider sense. A sets provisioning state is not included in the syntax tables. If a component has a set, it usually has multiple sets. A component with two sets is illustrated in Figure 1-3 on page 1-21. It is quite common for these sets to contain a similar group of dataitems (if not identical).

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 1: Introduction 1-21 Copyright 19962005 Nortel

.
Figure 1-3 Sets illustrated

Some Component Dataitem A Dataitem B Dataitem C Dataitem D Dataitem E Dataitem F Dataitem G Dataitem H Dataitem F, Dataitem G and Dataitem H also logically group to form a set. e.g. AUXPSCH Registration set Dataitem A and Dataitem B are not part of a set (they are non-set data) Dataitem C, Dataitem D and Dataitem E logically group to form a set. The set has a name, e.g. SPCH Registration set

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-22 Chapter 1: Introduction Nortel Confidential Figure 1-4 Subscriber Profile diagram examples

Copyright

19962005 Nortel

EXAMPLES
Profile Component Name

Service X
Data

Indicates whether the component is mandatory (M) or optional (O)

Means the profile component has dataitems that are not part of a set (non-set data)
SPCH Reg

Means the profile component has a data set (its name is given, here is it SPCH Reg). There may be multiple sets.

ODB BAOC
No data

ODB BAOC has no datafill, it is simply provisioned or not provisioned

TPHNY
Data

Telephony has datafill but no sets (non-set data only)

BOIC
SPCH Reg CDA Reg AUXS Reg CDS Reg

O
SMS Reg FAX Reg

BOIC just has six sets, and no other datafill outside of these sets.

CFU
Data SPCH Reg CDA Reg AUXS Reg CDS Reg

FAX Reg

CFU has non-set data and also five sets of registration data. Note that for supplementary services the individual sets are always displayed in the same position (hence the space left where SMS Reg is for BOIC).

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Figure 1-5 Subscriber Profile diagram part I (Auth, Profile Control) )

Chapter 1: Introduction 1-23 Copyright 19962005 Nortel

AUTHENTICATION DATA

AUTH
Data

PROFILE CONTROL DATA

Barring Control
Data

Category
Data

IMSI Status
Data

LMU
Data

NAM
Data

Password
Data

Roaming Entitlement
Data

SOAPROV
Data

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-24 Chapter 1: Introduction Nortel Confidential Figure 1-6 Subscriber Profile diagram part II (ODBs)

Copyright

19962005 Nortel

OPERATOR DETERMINED BARRING SERVICES

ODB BAOC
No data

ODB BAOCRoam
No data

ODB BOIC
No data

ODB BOICexHC
No data

ODB BAIC
No data

ODB BICRoam
No data

ODB PremRate Info


No data

ODB PremRate Ent


No data

ODB HPLMNSpec 1
No data

ODB HPLMNSpec 2
No data

ODB HPLMNSpec 3
No data

ODB HPLMNSpec 4
No data

ODB CISSMGT
No data

ODB CCFMGT
No data

ODB BAECT
No data

ODB BCHDECT
No data

ODB BINTECT
No data

ODB BDBCECT
No data

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Figure 1-7 Subscriber Profile part III (BSs)

Chapter 1: Introduction 1-25 Copyright 19962005 Nortel

BASIC SERVICES
SPCH BSG

TPHNY
Data

AUXSPCH BSG

AUXSPCH
Data

SMS BSG

SMMO
Data

SMMT
Data

FAX BSG

FAX3
Data

ALTSPFAX
Data

CDA BSG

CDA
Data

CDA300
Data

CDA1200
Data

CDA1275
Data

CDA2400
Data

CDA4800
Data

CDA9600
Data

CDAGBS
Data

SPCHCDA
Data

ALTSPCDA
Data

CDS BSG

CDS
Data

CDS1200
Data

CDS2400
Data

CDS4800
Data

CDS9600
Data

CDSGBS
Data

SPCHCDS
Data

ALTSPCDS
Data

VGS BSG

VBS
Data

VGCS
Data

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-26 Chapter 1: Introduction Nortel Confidential Figure 1-8 Subscriber Profile part IV (SSs 1)

Copyright

19962005 Nortel

SUPPLEMENTARY SERVICES Part 1 ACRJ


No data

AOCC
No data

AOCI
No data

CNAM
No data

COLR
No data

ECT
No data

HOLD
No data

HOTBILL
No data

LCO
No data

MCT
No data

UUS1
No data

ACC
Data

CLIP
Data

CLIR
Data

COLP
Data

EMLPP
Data

FM
Data

MPTY
Data

COS
SPCH Reg CDA Reg AUXS Reg CDS Reg

CUG
Data

FAX Reg

SPCH Reg CDA Reg

AUXS Reg CDS Reg AllBSGReg FAX Reg

CW
SPCH Reg CDA Reg AUXS Reg CDS Reg

O EXT
FAX Reg SPCH Reg AUXS Reg

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Figure 1-9 Subscriber Profile part V (SSs 2)

Chapter 1: Introduction 1-27 Copyright 19962005 Nortel

SUPPLEMENTARY SERVICES Part 2

BAIC
SPCH Reg CDA Reg AUXS Reg CDS Reg

O
SMS Reg FAX Reg

BICRoam
SPCH Reg CDA Reg AUXS Reg CDS Reg

O
SMS Reg FAX Reg

BAOC
SPCH Reg CDA Reg VGS Reg AUXS Reg CDS Reg

O
SMS Reg FAX Reg

BOIC
SPCH Reg CDA Reg AUXS Reg CDS Reg

O
SMS Reg FAX Reg

BOICexHC
SPCH Reg CDA Reg AUXS Reg CDS Reg

O
SMS Reg FAX Reg

CFB
Data SPCH Reg CDA Reg AUXS Reg CDS Reg

CFNRc
Data SPCH Reg AUXS Reg CDS Reg

FAX Reg

CDA Reg

FAX Reg

CFNRy
Data SPCH Reg CDA Reg AUXS Reg CDS Reg

CFU
Data SPCH Reg AUXS Reg CDS Reg

FAX Reg

CDA Reg

FAX Reg

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-28 Chapter 1: Introduction Nortel Confidential Figure 1-10 Subscriber Profile part VI (CAMEL)

Copyright

19962005 Nortel

CAMEL SERVICES

D-CSI
Data

M-CSI
Data

SS-CSI
Data

USSD-CSI
Data

GPRS-CSI
Data TDP1 TDP4 TDP2 TDP5 TDP3

O-CSI
Data TDP2 Ph1 TDP4 Ph3 TDP2 Ph2

TDP2 Ph3

SMS-CSI
Data TDP1

T-CSI
Data TDP12 Ph1 TDP13 Ph3 TDP12 Ph2 TDP14 Ph3

TDP12 Ph3

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Figure 1-11 Subscriber Profile part VII (LCS)

Chapter 1: Introduction 1-29 Copyright 19962005 Nortel

LOCATION SERVICES Autonomous Self Location Class


Data

Basic Self Location Class


Data

Call Related Privacy Class


Data

Call Unrelated Privacy Class


Data

GMLCs List
Data

PLMN Operator Privacy Class


Data

Transfer to Third Party Class


Data

Universal Privacy Class


Data

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-30 Chapter 1: Introduction Nortel Confidential Figure 1-12 Subscriber Profile part VIII (Misc.)

Copyright

19962005 Nortel

GPRS, OTHER SERVICES AND OTHER COMPONENTS

GPRS
PDP 1 PDP 6 PDP 11 PDP 16 PDP 2 PDP 7 PDP 12 PDP 17 PDP 3 PDP 8 PDP 13 PDP 18 PDP 4 PDP 9 PDP 14 PDP 19 PDP 5 PDP 10 PDP 15 PDP 20

CLIN
Data

EA
Data

Proprietary IN
Data

HST
Data

SIMR
Data

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 1: Introduction 1-31 Copyright 19962005 Nortel

Data model and validations


This section outlines the data model and the validations associated with provisioning each profile component. Profile components are listed below. Datatypes are introduced on page 1-36, vectors on page 1-36 and the validations on page 1-37. The data model and validations then follow.

Profile components The profile components are listed in Table 1-1. They are ordered primarily by component type, and then alphabetically. Each component is described in detail in Chapter 2: Component descriptions. For an example, see Example component (guide to the following sections) on page 1-38 of this chapter. There are also introductory sections for many of the component types.
Table 1-1 Profile components (5 pages) Short Name Primary Component Auth Data Profile Control Barring Control Category IMSI Status LMU NAM Password Roaming Entitlement SOAPROV Basic Services ALTSPCDA ALTSPCDS ALTSPFAX AUXTPHY CDA Alternate Speech / CDA Data Alternate Speech / CDS Data Alternate Speech / Fax Group 3 Auxiliary Telephony Circuit Duplex Asynchronous Data n/a n/a n/a Location Measurement Unit Network Access Mode n/a n/a Suppression of Announcements provisioning Authentication Data on page 2-41 on page 2-44 on page 2-45 on page 2-46 on page 2-49 on page 2-51 on page 2-52 on page 2-53 on page 2-54 on page 2-55 on page 2-56 on page 2-59 on page 2-61 on page 2-63 on page 2-65 on page 2-67 Expanded Name See Chapter 2

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-32 Chapter 1: Introduction Nortel Confidential Table 1-1 Profile components (5 pages) Short Name CDA 300 CDA 1200 CDA 1275 CDA 2400 CDA 4800 CDA 9600 CDAGBS Expanded Name Circuit Duplex Asynchronous Data 300 Circuit Duplex Asynchronous Data 1200 Circuit Duplex Asynchronous Data 1275 Circuit Duplex Asynchronous Data 2400 Circuit Duplex Asynchronous Data 4800 Circuit Duplex Asynchronous Data 9600

Copyright

19962005 Nortel

See Chapter 2 on page 2-68 on page 2-70 on page 2-72 on page 2-74 on page 2-76 on page 2-78 on page 2-80

Circuit Duplex Asynchronous Data General Bearer Service Circuit Duplex Synchronous Circuit Duplex Synchronous Data 1200 Circuit Duplex Synchronous Data 2400 Circuit Duplex Synchronous Data 4800 Circuit Duplex Synchronous Data 9600 Circuit Duplex Synchronous Data General Bearer Service Facsimile Group 3 Short Message Mobile Originating Short Message Mobile Terminating Speech followed by CDA Data Speech followed by CDS Data Telephony Voice Broadcast Service Voice Group Call Service

CDS CDS 1200 CDS 2400 CDS 4800 CDS 9600 CDSGBS

on page 2-82 on page 2-83 on page 2-85 on page 2-87 on page 2-89 on page 2-91

FAX3 SMMO SMMT SPCHCDA SPCHCDS TPHY VBS VGCS Supplementary Services ACC ACRJ

on page 2-93 on page 2-95 on page 2-97 on page 2-99 on page 2-101 on page 2-103 on page 2-105 on page 2-106 on page 2-107

Accounting Codes Anonymous Call Reject

on page 2-109 on page 2-110

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 1-1 Profile components (5 pages) Short Name AOCC AOCI BAIC BAOC BICRoam BOIC BOICexHC Expanded Name Advice of Charge Charging Advice of Charge Information Bar All Incoming Calls Bar All Outgoing Calls Bar Incoming Calls while Roaming Bar Outgoing International Calls

Chapter 1: Introduction 1-33 Copyright 19962005 Nortel

See Chapter 2 on page 2-111 on page 2-112 on page 2-113 on page 2-115 on page 2-117 on page 2-119 on page 2-121

Bar Outgoing International Call Except to Home Country Call Forward Busy Call Forward Not Reachable Call Forward No Reply Call Forward Unconditional Calling Line Id Presentation Restriction Calling Line Id Restriction Calling Name Delivery Connected Line Id Presentation Connected Line Id Restriction Class Of Service Closed User Groups Call Waiting Explicit Call Transfer Enhanced Multi Level Precedence & Pre-emption Extension Services Follow Me Call Hold Hot billing

CFB CFNRC CFNRY CFU CLIP CLIR CNAM COLP COLR COS CUG CW ECT EMLPP EXT FM HOLD HOTBILL

on page 2-123 on page 2-130 on page 2-136 on page 2-143 on page 2-150 on page 2-151 on page 2-152 on page 2-153 on page 2-154 on page 2-155 on page 2-158 on page 2-164 on page 2-166 on page 2-167 on page 2-168 on page 2-175 on page 2-177 on page 2-178

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-34 Chapter 1: Introduction Nortel Confidential Table 1-1 Profile components (5 pages) Short Name LCO MCT MPTY UUS1 WPS Expanded Name Local Calls Only Malicious Call Trace Multiparty User to User Signalling stage 1 Wireless Priority Service

Copyright

19962005 Nortel

See Chapter 2 on page 2-179 on page 2-180 on page 2-181 on page 2-182 on page 2-183

Operator Determined Barrings All ODBs (incoming, outgoing, ECT, misc) CAMEL Services D-CSI GPRS-CSI Dialled CAMEL Subscription Information General Packet Radio Service CAMEL Subscription Information Mobility Management CAMEL Subscription Information Originating CAMEL Subscription Information Short Message Service CAMEL Subscription Information Supplementary Service CAMEL Subscription Information Terminating CAMEL Subscription Information Translations Information Flag CAMEL Subscription Information Unstructured Supplementary Service Data CAMEL Subscription Information refer to the ODBs section on page 2-184

on page 2-186 on page 2-187 on page 2-189

M-CSI

on page 2-192

O-CSI SMS-CSI

on page 2-193 on page 2-201

SS-CSI

on page 2-203

T-CSI TIF-CSI

on page 2-204 on page 2-209

USSD-CSI

on page 2-210

Location Services (LCS) LCS Autonomous Self Location LCS Basic Self Location LCS Call Related n/a

on page 2-211 on page 2-212

n/a n/a

on page 2-213 on page 2-214

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 1-1 Profile components (5 pages) Short Name LCS Call Unrelated LCS GMLCs LCS PLMN Operator LCS Transfer to Third Party LCS Universal GPRS GPRS Other Services CLIN EA Proprietary IN Other Components HST SIMR Home Subscriber Trace SIM Replacement General Packet Radio Service Expanded Name n/a LCS Gateway Mobile Location Centres n/a n/a

Chapter 1: Introduction 1-35 Copyright 19962005 Nortel

See Chapter 2 on page 2-216 on page 2-218 on page 2-219 on page 2-221

n/a

on page 2-222

on page 2-223 on page 2-229

Calling Line Identification Replacement Number Equal Access Proprietary Intelligent Network service

on page 2-230 on page 2-231 on page 2-232 on page 2-233 on page 2-234 on page 2-235

Proprietary services The following services are Nortel proprietary services. ACC, ACRJ, AUXTPHNY, CLIN, CNAM, COS, EA, EXT, HOTBILL, LCO, MCT, Proprietary IN

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-36 Chapter 1: Introduction Nortel Confidential

Copyright

19962005 Nortel

Datatypes The subscriber profile database is composed of a finite number of datatypes, summarised in Table 1-2. There are three broad types: number, string and enum. Strings can be composed of characters, digits or hex digits. Character strings are usually limited in the particular characters they can use, typically to alphanumeric characters and underscores. Digits strings use (0..9), whereas hex strings use (0..9) and (A..F). Booleans can be viewed as a special type of enum. The Example(s) in Data Syntax Tables column indicates the conventions used in the Data Syntax tables in this document (see Chapter 2: Component descriptions). Note that some dataitems in the database are optional, so null (a blank) would be a valid value, whatever their datatype actually is.
Table 1-2 Primitive datatypes Datatype Number String Format m - n range m - n characters (alphanumeric and underscores unless stated otherwise) Example(s) in Data Syntax Tables number: 0 - 255 1 - 20 characters 1 - 20 characters (alphanumeric, underscores, *, #) 6 - 15 digits 32 hex digits {OPERATOR, USER} Boolean

Digit String Hex String Enumerated Boolean

m - n digits (0..9) m hex digits (0..9, A..Z) {FIRST, SECOND, THIRD, ...} Boolean (i.e. true or false)

Data vectors A vector is a collection of elements of the same type, where a variable number of elements can exist and elements may be added or removed. An abstract example is a names vector; if the vector is datafilled it will contain one or more individual name elements, with a limit being imposed on the maximum number of elements. Elements in vectors are not ordered, and there is no concept of indexes within the vector. Elements are simply added, removed or read from the vector. The database contains two broad types of vector: simple and complex. Simple vectors are a collection containing just one datatype. An example is the names vector mentioned above. A complex vector is different, in that rather than containing a collection of elements, it holds a collection of structures. A structure is composed of two or more elements. An abstract example is a people vector; each item in the vector is a structure of name, age and gender elements.
411-2831-332 Preliminary 01.02 March 2005

Nortel Confidential

Chapter 1: Introduction 1-37 Copyright 19962005 Nortel

In the example in Table 1-3, the simple vector is mandatory, as indicated by the number of elements (1 - 3). The complex vector is optional.
Table 1-3 Vector examples Type Simple Element(s) 1 - 3 strings, each 1 - 20 characters Examples {APPLE} {PEAR, APPLE, PEACH} Complex 0 - 3 structures of -string, 1 - 20 characters -number, 0 - 255 range {{RED, 123}} {{RED, 98}, {GREEN, 240}}

Validations introduction Subsequent component data model sections detail datafill and provisioning validations for each component in the subscriber profile. Operator mode validations are detailed -- i.e. those applicable to operator provisioning updates (validations for network profile updates are not covered by this document). There are three very broad validations areas, given in Table 1-4 below. A profile may be created via provisioning and subsequently deleted via provisioning. Profile modifications are made via provisioning transactions. Such a transaction may add/modify/delete multiple components. A guide to the component data model sections is given in Example component (guide to the following sections) on page 1-38.
Table 1-4 Validation areas Validation Area Profile Creation Profile Deletion Profile Modification See Section(s) on page 1-38 on page 1-38 Transaction validations on page 1-38 Per-Profile Component validations in Chapter 2: Component descriptions

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-38 Chapter 1: Introduction Nortel Confidential

Copyright

19962005 Nortel

Profile creation A profile is created by datafilling authentication data. The current Nortel HLR implementation auto-provisions Profile Control Data with default values (see Chapter 2, Profile control data introduction on page 2-44). The following checks are done: the IMSI must be available for use (i.e. not already in use) the authentication data must be valid (see Chapter 2, Authentication data on page 2-41)

Profile deletion To delete a subscriber profile the following conditions must be met: IMSI Status must be DEACTIVATED no services must be provisioned subscriber must not be involved in a SIMR relationship

Note that a profile with HST can be deleted. Transactional validations These validations apply for all profile modification provisioning actions. if the IMSI Status is set to REPLACEMENT then no updates at all are permitted to the profile

Example component (guide to the following sections) Sections start with a sentence or two to outline the function of the datafill for this component. Please refer to the services documentation for details on functionality. Datafill This subsection details the components datafill. The dataitems and their syntax are detailed in the Data Syntax table, see Table 1-5 on page 1-39 for an example. The example shows one dataitem that is not part of a set, and then two sets, each with two dataitems. Syntax checks describe the format of the dataitem, and do not include any checks resulting from interactions with other dataitems. They describe the checks for validating the dataitem in isolation. Example syntax are checking the dataitem in a string (and of the correct length) or a number (in the correct range) or a boolean. This subsection also includes the intra-component validations in a bullet list. These are validations arising from interactions between the dataitems of this component. An example intra-component interaction is that dataitem X must be greater than dataitem Y.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 1: Introduction 1-39 Copyright 19962005 Nortel

A glossary of shortened/acronym dataitems is given in Glossary of terms on page B-347..


Table 1-5 Example data syntax Dataitem Dataitem name Set name Dataitem name Dataitem name Set name Dataitem name Dataitem name Syntax the syntax is described here for each dataitem; see Datatypes on page 1-36 for examples and help some components have vectors; these will be indicated in this table; see Data vectors on page 1-36 for more help Optional indicates whether each dataitem is optional, including how many entries are optional for vectors

Descriptions for the dataitems, which are also known as fields, are given in the Field Descriptions table (see Table 1-6 for an example).
Table 1-6 Example field descriptions Dataitem Dataitem name Set name Dataitem name Dataitem name Set name Dataitem name Dataitem name Description a concise description is given for each dataitem, including expansion of shortened/acronym enum options

Interactions This subsection details the interactions with other components and system data. Provisioning side-effects are also included. An example interaction with system data is: dataitem X must exist in the YYY field of system table ZZZ

Example interactions with other services are: service A can only be provisioned if service B is also provisioned the syntax of dataitem X of service A depends on dataitem M of service B

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

1-40 Chapter 1: Introduction Nortel Confidential

Copyright

19962005 Nortel

HLR-wide validations This subsection gives those validations that interact with other subscribers and their data. If none exist then this subsection is not included. Some examples of these validations are: the value for a particular dataitem cannot be used by more than one subscriber, i.e. its value must be unique HLR-wide a limit is placed on the number of subscribers that can have a particular service provisioned

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

2-41

Chapter 2: Component descriptions


Authentication data

2
2

Authentication data is mandatory datafill for all subscribers. The Nortel HLR includes authentication centre (AUC) functionality. Datafill Authentication data syntax is detailed in Table 2-1. A 2G subscriber has a GSM algorithm and hence a Ki, whereas a 3G subscriber has a UMTS algorithm and hence a K. The algorithm indirectly indicates whether the subscriber is 2G or 3G (see section for more details). The IMSI is actually composed of three parts: MCC, MNC and MSIN.
Table 2-1 Authentication data syntax Dataitem IMSI Ki (2G) or K (3G) Algorithm OPC syntax 6 - 15 digits 32 hex digits number: 0 - 255 32 hex digits Yes Optional

Authentication data descriptions are given in Table 2-2.


Table 2-2 Authentication data field descriptions Dataitem IMSI Ki (2G) or K (3G) Description International Mobile Subscriber Identity, a unique ID specified by a SIM card key used in authentication; 2G subscribers have a Ki whereas 3G subscribers have a K

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-42 Chapter 2: Component descriptions Nortel Confidential Table 2-2 Authentication data field descriptions Dataitem Algorithm Description

Copyright

19962005 Nortel

this number maps to a 2G/3G authentication algorithm in system table GHLRALG (the relationship is not enforced) also known as AlgSel and algorithm selection Operator variant algorithm Configuration, used by the UMTS milenage algorithm also known as OPc Algorithm Parameter

OPC

Interactions Authentication data interacts with IMSI Status, GPRS, system tables GHLRALG and GHLRPDP and office parameter GHLR_IMSI_MNC. the MNC portion of the IMSI must be valid according to office parameter GHLR_IMSI_MNC (table OFCSTD ). The MNC is the 4th, 5th and possibly the 6th digits of the IMSI. If the parameters MNC_SELECTOR is set to SINGLE then the MNC must match the parameters SINGLE_MNC_VALUE (if SINGLE_MNC_VALUE has 2 digits then the MNC is taken to be the IMSIs 4th and 5th digits, whereas if SINGLE_MNC_VALUE has 3 digits then the MNC is taken to be the IMSIs 4th, 5th and 6th digits). If it is set to MULTIPLE then the IMSIs length must be a minimum of (4 +MULTIPLE_MNC_LENGTH); the 4 originates from the length of the IMSI MCC (3 digits) added to the minimum length of the IMSI MSIN (1 digit min.) the algorithm should map to an entry in the ALGSEL column of system table GHLRALG, but note that this relationship is not enforced if the subscribers IMSI Status is set to REPLACEMENT, the algorithm cannot change from a 2G to a 3G type, or from a 3G to a 2G type. The determination of 2G/3G requires system table GHLRALG as explained in Determination of 2G/3G algorithm on page 2-43 if the algorithm is 3G, then all of the subscribers PDPs (GPRS) must have ExtQoS. A PDP has ExtQoS if its entry in system table GHLRPDP (PDPNAME field) has the EXTQOS field datafilled. The determination of 2G/ 3G requires system table GHLRALG as explained in Determination of 2G/ 3G algorithm on page 2-43 the OPC is only datafilled if the algorithm maps to the milenage UMTS algorithm, for all other algorithms the OPC must not be datafilled. The algorithm is milenage if it maps to an entry in system table GHLRALG (ALGSEL field) whose FLAVOUR.BASE_ALG is set to UMTS_MILENAGE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-43 Copyright 19962005 Nortel

Additional information Determination of 2G/3G algorithm An algorithm is 3G if it maps to an entry in system table GHLRALG (ALGSEL field) whose FLAVOUR.BASE_ALG is UMTS_XOR or UMTS_MILENAGE. All other algorithms (whether they exist in GHLRALG or not) are 2G.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-44 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

Profile control data introduction

Profile control data are mandatory components which help define the subscribers profile, they relate to the profile as a whole. For instance, the IMSI Status defines the status of the subscriber in the network (e.g. activated). Profile control data components are listed in Table 2-3, along with their default values, which are used for blank subscribers (essentially subscribers that only have authentication datafill).
Table 2-3 Profile control data Component Barring Control Dataitem(s) BICCTRL BOCCTRL Category IMSI Status Category IMSI Status Cust Group NCOS LMU (Location Measurement Unit) NAM (Network Access Mode) LMU NAM Default Values OPERATOR OPERATOR ORDINARY DEACTIVATED null null FALSE office parameter NAM_DFLT from table GHLRPARM office parameter PASSDFLT from table GHLRPARM UNKW FALSE on page 2-51 on page 2-52 on page 2-46 on page 2-49 See section on page 2-45

Password

Password

on page 2-53

Roaming Entitlement SOAPROV

Roaming Entitlement SOAPROV

on page 2-54 on page 2-55

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-45 Copyright 19962005 Nortel

Barring control
The Barring Control component is profile control data and is therefore mandatory datafill. It is used to indicate whether the operator or user has control over incoming/outgoing barrings. Datafill Barring Control data syntax is detailed in Table 2-4.
Table 2-4 Barring Control data syntax Dataitem BICCTRL BOCCTRL Syntax {OPERATOR, USER} {OPERATOR, USER] Optional

Barring Control field descriptions are given in Table 2-5.


Table 2-5 Barring Control field descriptions Dataitem BICCTRL BOCCTRL Description control of barring incoming calls: operator or user control of barring outgoing calls: operator or user

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-46 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

Category
The Category component is profile control data and is therefore mandatory datafill. It is used to indicate the subscriber category, which is used for signalling and billing. Datafill Category data syntax is detailed in Table 2-6.
Table 2-6 Category control data syntax (3 pages) Dataitem Category (continued on next page) syntax {ORDINARY, PRIORITY, TEST, PAYPHONE, DATA, ORDNCHRG, PRINCHRG, UNKNOWN, FRENCH, ENGLISH, GERMAN, RUSSIAN, SPANISH, RESERVED, SPARLANG1, SPARLANG2, SPARLANG3, FIXEDACCESS, CHINAIP, CATEGORY14, CATEGORY17, CATEGORY18 CATEGORY19, CATEGORY20, CATEGORY21, CATEGORY22, CATEGORY23, CATEGORY24, CATEGORY25, CATEGORY26, CATEGORY27, CATEGORY28, CATEGORY29, CATEGORY30, CATEGORY31, CATEGORY32, CATEGORY33, CATEGORY34, CATEGORY35, CATEGORY36, CATEGORY37, CATEGORY38, CATEGORY39, CATEGORY40, CATEGORY41, CATEGORY42, CATEGORY43, CATEGORY44, CATEGORY45, CATEGORY46, CATEGORY47, CATEGORY48, CATEGORY49, CATEGORY50, CATEGORY51, CATEGORY52, CATEGORY53, CATEGORY54, CATEGORY55, CATEGORY56, CATEGORY57, CATEGORY58, CATEGORY59, CATEGORY60, CATEGORY61, CATEGORY62, CATEGORY63, CATEGORY64, CATEGORY65, CATEGORY66, CATEGORY67, CATEGORY68, CATEGORY69, CATEGORY70, CATEGORY71, CATEGORY72, CATEGORY73, CATEGORY74, CATEGORY75, CATEGORY76, CATEGORY77, CATEGORY78, CATEGORY79, CATEGORY80, CATEGORY81, CATEGORY82, CATEGORY83, CATEGORY84, CATEGORY85, CATEGORY86, CATEGORY87, CATEGORY88, CATEGORY89, CATEGORY90, CATEGORY91, CATEGORY92, CATEGORY93, CATEGORY94, CATEGORY95, CATEGORY96, CATEGORY97, CATEGORY98, CATEGORY99, CATEGORY100, CATEGORY101, CATEGORY102, CATEGORY103, CATEGORY104, CATEGORY105, Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-6 Category control data syntax (3 pages) Dataitem Category (continued) syntax

Chapter 2: Component descriptions 2-47 Copyright 19962005 Nortel

Optional

CATEGORY106, CATEGORY107, CATEGORY108, CATEGORY109, CATEGORY110, CATEGORY111, CATEGORY112, CATEGORY113, CATEGORY114 CATEGORY115, CATEGORY116, CATEGORY117, CATEGORY118, CATEGORY119, CATEGORY120, CATEGORY121, CATEGORY122, CATEGORY123, CATEGORY124, CATEGORY125, CATEGORY126, CATEGORY127, CATEGORY128, CATEGORY129, CATEGORY130, CATEGORY131, CATEGORY132, CATEGORY133, CATEGORY134, CATEGORY135, CATEGORY136, CATEGORY137, CATEGORY138, CATEGORY139, CATEGORY140, CATEGORY141, CATEGORY142, CATEGORY143, CATEGORY144, CATEGORY145, CATEGORY146, CATEGORY147, CATEGORY148, CATEGORY149, CATEGORY150, CATEGORY151, CATEGORY152, CATEGORY153, CATEGORY154, CATEGORY155, CATEGORY156, CATEGORY157, CATEGORY158, CATEGORY159, CATEGORY160, CATEGORY161, CATEGORY162, CATEGORY163, CATEGORY164, CATEGORY165, CATEGORY166, CATEGORY167, CATEGORY168, CATEGORY169, CATEGORY170, CATEGORY171, CATEGORY172, CATEGORY173, CATEGORY174, CATEGORY175, CATEGORY176, CATEGORY177, CATEGORY178, CATEGORY179, CATEGORY180, CATEGORY181, CATEGORY182, CATEGORY183, CATEGORY184, CATEGORY185, CATEGORY186, CATEGORY187, CATEGORY188, CATEGORY189, CATEGORY190, CATEGORY191, CATEGORY192, CATEGORY193, CATEGORY194, CATEGORY195, CATEGORY196, CATEGORY197, CATEGORY198, CATEGORY199, CATEGORY200, CATEGORY201, CATEGORY202, CATEGORY203, CATEGORY204, CATEGORY205, CATEGORY206, CATEGORY207, CATEGORY208, CATEGORY209, CATEGORY210, CATEGORY211, CATEGORY212, CATEGORY213, CATEGORY214, CATEGORY215, CATEGORY216, CATEGORY217, CATEGORY218, CATEGORY219, CATEGORY220, CATEGORY221, CATEGORY222, CATEGORY223, CATEGORY224, CATEGORY225, CATEGORY226, CATEGORY227, CATEGORY228, CATEGORY229, CATEGORY230, CATEGORY231, CATEGORY232, CATEGORY233, CATEGORY234, CATEGORY235, CATEGORY236, CATEGORY237, CATEGORY238, CATEGORY239, CATEGORY241,

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-48 Chapter 2: Component descriptions Nortel Confidential Table 2-6 Category control data syntax (3 pages) Dataitem Category (continued) syntax

Copyright

19962005 Nortel

Optional

CATEGORY242, CATEGORY243, CATEGORY245, CATEGORY246, CATEGOTY247, CATEGORY248, CATEGORY249, CATEGORY250, CATEGORY 251, CATEGORY252, CATEGORY253, CATEGORY254}

Category field descriptions are given in Table 2-7.


Table 2-7 Category field descriptions Dataitem Category Description the subscriber category, used for signalling and billing

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-49 Copyright 19962005 Nortel

IMSI Status

2
The IMSI Status component is profile control data and is therefore mandatory datafill. It defines the status of the subscriber within the network and hot-line routing (HLR) class of service (COS) information for NEW subscribers (as defined by their IMSI Status dataitem).

Datafill IMSI Status data syntax is detailed in Table 2-8. The following intra-service interactions apply. the IMSI Status cannot be manually set to REPLACEMENT; the IMSI Status is automatically changed to REPLACEMENT when the IMSI is assigned to be the new IMSI in a SIM Replacement (SIMR) relationship if IMSI Status is not NEW then Cust Group and NCOS must not be datafilled if IMSI Status is NEW then Cust Group must be datafilled (NCOS may optionally be datafilled too)

Table 2-8 IMSI status data syntax Dataitem IMSI Status Cust Group NCOS Syntax {ACTIVATED, DEACTIVATED, NEW, REPLACEMENT} number: 0 - 4095 number: 0 - 255 Optional Optional Optional

IMSI Status field descriptions are given in Table 2-9.


Table 2-9 IMSI Status field descriptions Dataitem IMSI Status Description the status of the subscriber within the network: Activated, Deactivated, New or Replacement (the Replacement state is only valid for new IMSIs in a SIMR relationship) also known as IStatus hot line routing customer group for new subscribers defined in system tables GSMCUST and GSMNCOS hot line routing network class of service for new subscribers defined in system table GSMNCOS

Cust Group

NCOS

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-50 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions IMSI Status interacts with all ODBs and system tables GSMCUST and GSMNCOS . if IMSI Status is NEW then no ODBs may be provisioned if IMSI Status is NEW and NCOS has not been datafilled then the Cust Group must be an entry from the GSM_CUSTGRP_KEY field of system table GSMCUST, and this entry must have the USERTYPE and XLT fields datafilled with the USERTYPE option set to HTL if IMSI Status is NEW and NCOS has been datafilled then the Cust Group and NCOS combined must be an entry from the GSM_NCOS_KEY field of system table GSMNCOS, and this entry must have the USERTYPE and XLT fields datafilled with the USERTYPE option set to HTL

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-51 Copyright 19962005 Nortel

LMU (Location Measurement Unit)


The LMU component is profile control data and is therefore mandatory datafill. It is used in E911. Datafill LMU data syntax is detailed in Table 2-10.
Table 2-10 LMU control data syntax Dataitem LMU Syntax Boolean Optional

LMU field descriptions are given in Table 2-11.


Table 2-11 LMU field descriptions Dataitem LMU Description location measurement unit, used in E911

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-52 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

NAM (Network Access Mode)

The NAM component is profile control data and is therefore mandatory datafill. It is used to indicate whether the subscriber is entitled to GSM and/or GPRS service. Datafill NAM data syntax is detailed in Table 2-12.
Table 2-12 NAM control data syntax Dataitem NAM Syntax {MSC_ONLY, SGSN_ONLY, SGSN_AND_MSC} Optional

NAM field descriptions are given in Table 2-13.


Table 2-13 NAM field descriptions Dataitem NAM Description network access mode, indicates whether the subscriber is entitled to only GSM service (MSC_ONLY), only GPRS (SGSN_ONLY) service or both (SGSN_AND_MSC)

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-53 Copyright 19962005 Nortel

Password
The Password component is profile control data and is therefore mandatory datafill. It gives the password for barring supplementary services. Datafill Password data syntax is detailed in Table 2-14.
Table 2-14 Password control data syntax Dataitem Password Syntax 4 digits Optional

Password field descriptions are given in Table 2-15.


Table 2-15 Password field descriptions Dataitem Password Description password for barring supplementary services

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-54 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

Roaming Entitlement
The Roaming Entitlement component is profile control data and is therefore mandatory datafill. Datafill Roaming Entitlement data syntax is detailed in Table 2-16.
Table 2-16 Roaming Entitlement data syntax Dataitem Roaming Entitlement Syntax 1 - 16 characters Optional

Roaming Entitlement field descriptions are given in Table 2-17.


Table 2-17 Roaming Entitlement field descriptions Dataitem Roaming Entitlement Description the subscribers roaming entitlement (can be set to unknown)

Interactions Roaming Entitlement interacts with system table GHLRRMZN. the Roaming Entitlement must either be UNKW or an entry from the ROAM column of system table GHLRRMZN

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-55 Copyright 19962005 Nortel

SOAPROV

2
The SOAPROV component is profile control data and is therefore mandatory datafill. It indicates whether the suppression of announcements (to called party) parameter is sent in PRN v3 message. SOAPROV stands for suppression of announcements provisioning.

Datafill SOAPROV data syntax is detailed in Table 2-18.


Table 2-18 SOAPROV data syntax Dataitem SOAPROV Syntax Boolean Optional

SOAPROV field descriptions are given in Table 2-19.


Table 2-19 SOAPROV field descriptions Dataitem SOAPROV Description indicates whether the suppression of announcements (to called party) parameter is sent in PRN v3 message

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-56 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

Basic Services Introduction

Basic services are teleservices/bearer services in the telecommunications network. Teleservices are end-to-end services between MS handsets or other terminal devices. Service definitions cover all seven layers of the OSI (Open Systems Interconnection) model. Bearer services are point-to-point services between access points. Service definitions only cover layers one to three of the OSI model. Actions at layers four to seven must be specified by user applications; they are not part of the bearer service. The HLR supports the basic services given in Table 2-20. Note that the Emergency Calls service is implicitly provisioned to all subscribers, there is no specific datafill or validations.
Table 2-20 Basic Services (2 pages) Short Name ALTSPCDA ALTSPCDS ALTSPFAX AUXTPHNY CDA CDA300 CDA1200 CDA1275 CDA2400 CDA4800 CDA9600 CDAGBS Expanded Name Alternate Speech / CDA Data Alternate Speech / CDS Data Alternate Speech / Fax Group 3 Auxiliary Telephony Circuit Duplex Asynchronous Data Circuit Duplex Asynchronous Data 300 Circuit Duplex Asynchronous Data 1200 Circuit Duplex Asynchronous Data 1275 Circuit Duplex Asynchronous Data 2400 Circuit Duplex Asynchronous Data 4800 Circuit Duplex Asynchronous Data 9600 Circuit Duplex Asynchronous Data General Bearer Service Circuit Duplex Synchronous Data Circuit Duplex Synchronous Data 1200 Circuit Duplex Synchronous Data 2400 Circuit Duplex Synchronous Data 4800 Circuit Duplex Synchronous Data 9600 Type Bearer Service Bearer Service Teleservice Teleservice Bearer Service Bearer Service Bearer Service Bearer Service Bearer Service Bearer Service Bearer Service Bearer Service See Section on page 2-59 on page 2-61 on page 2-63 on page 2-65 on page 2-67 on page 2-68 on page 2-70 on page 2-72 on page 2-74 on page 2-76 on page 2-78 on page 2-80

CDS CDS1200 CDS2400 CDS4800 CDS9600

Bearer Service Bearer Service Bearer Service Bearer Service Bearer Service

on page 2-82 on page 2-83 on page 2-85 on page 2-87 on page 2-89

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-20 Basic Services (2 pages) Short Name CDSGBS Expanded Name Circuit Duplex Synchronous Data General Bearer Service Emergency Calls

Chapter 2: Component descriptions 2-57 Copyright 19962005 Nortel

Type Bearer Service

See Section on page 2-91

Emergency Calls FAX3 SMMO SMMT SPCHCDA SPCHCDS TPHNY VBS VGCS

Teleservice

see note above

Facsimile Group 3 Short Message Mobile Originating Short Message Mobile Terminating Speech followed by CDA Data Speech followed by CDS Data Telephony Voice Broadcast Service Voice Group Call Service

Teleservice Teleservice Teleservice Bearer Service Bearer Service Teleservice Teleservice Teleservice

on page 2-93 on page 2-95 on page 2-97 on page 2-99 on page 2-101 on page 2-103 on page 2-105 on page 2-106

Each basic service belongs to a basic service group (BSG); these are given in Table 2-21. Note that Emergency Calls is a speech service, although the data model only places TPHNY in the SPCH basic service group.
Table 2-21 Basic Service Groups Basic Service Group SPCH AUXSPCH SMS CDA Basic Services TPHNY AUXTPHNY SMMO, SMMT ALTSPCDA, CDA, CDA300, CDA1200, CDA1275, CDA2400, CDA4800, CDA9600, CDAGBS, SPCHCDA ALTSPCDS, CDS, CDS1200, CDS2400, CDS4800, CDS9600, CDSGBS, SPCHCDS ALTSPFAX, FAX3 VBS, VGCS

CDS

FAX VGS

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-58 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Notes on Basic Service datafill Basic service datafill is composed of an MSISDN and bearer capability index (BCI), with the following exceptions: CDA1275, SMMO and SMMT do not have a BCI VBS and VGCS have entirely different datafill (these two services are GSM Railways (GSMR) specific)

BCI validation BCI validation is rather complex but can be summarised by the following rule, with the given exceptions. If more than one service shares an MSISDN, then all of their BCIs must be null. There are three exceptions: if a service X shares an MSISDN with only SMMO/SMMT/ CDA1275, then X may have a BCI FAX3/CDA/CDS may share an MSISDN, and one of them may have a BCI sister basic services always share an MSISDN, and one of them must have a BCI, the other must not There are two pairs of sister basic services, ALTSPCDA & ALTSPCDS and SPCHCDA & SPCHCDS.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-59 Copyright 19962005 Nortel

ALTSPCDA (Alternate Speech / CDA Data)

ALTSPCDA datafill defines the MSISDN and bearer capability for alternate speech/CDA data. ALTSPCDA belongs to the CDA basic service group (BSG). Datafill ALTSPCDA data syntax is detailed in Table 2-22. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies. the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

Table 2-22 ALTSPCDA data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

ALTSPCDA field descriptions are given in Table 2-23.


Table 2-23 ALTSPCDA field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-60 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions ALTSPCDA interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275/ALTSPCDS then ALTSPCDAs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be ALTSPCDA ALTSPCDA belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU when provisioning ALTSPCDA, a BCI must be supplied unless ALTSPCDS is concurrently provisioned with a BCI upon provisioning ALTSPCDA, ALTSPCDS is automatically provisioned with the same MSISDN and a null BCI (unless explicitly provisioned also) ALTSPCDA and ALTSPCDS must have the same MSISDN. Upon changing the MSISDN of one service, the other services MSISDN is automatically updated to match one of ALTSPCDA/ALTSPCDS must have a BCI, the other must have a null BCI. Upon changing the null BCI to a value, the other services BCI is automatically updated to have a null BCI. It is not valid to change the service with the BCI so that it has a null BCI (as then both services would have a null BCI) upon deprovisioning ALTSPCDA, ALTSPCDS is automatically deprovisioned too

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-61 Copyright 19962005 Nortel

ALTSPCDS (Alternate Speech / CDS Data)


ALTSPCDS datafill defines the MSISDN and bearer capability for alternate speech/CDS data. ALTSPCDS belongs to the CDS basic service group (BSG). Datafill

ALTSPCDS data syntax is detailed in Table 2-24. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies. the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

Table 2-24 ALTSPCDS data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

ALTSPCDS field descriptions are given in Table 2-25.


Table 2-25 ALTSPCDS field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-62 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions ALTSPCDS interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275/ALTSPCDA then ALTSPCDSs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be ALTSPCDS ALTSPCDS belongs to the CDS BSG; at least one basic service from the CDS BSG must be provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU when provisioning ALTSPCDS, a BCI must be supplied unless ALTSPCDA is concurrently provisioned with a BCI upon provisioning ALTSPCDS, ALTSPCDA is automatically provisioned with the same MSISDN and a null BCI (unless explicitly provisioned also) ALTSPCDS and ALTSPCDA must have the same MSISDN. Upon changing the MSISDN of one service, the other services MSISDN is automatically updated to match one of ALTSPCDS/ALTSPCDA must have a BCI, the other must have a null BCI. Upon changing the null BCI to a value, the other services BCI is automatically updated to have a null BCI. It is not valid to change the service with the BCI so that it has a null BCI (as then both services would have a null BCI) upon deprovisioning ALTSPCDS, ALTSPCDA is automatically deprovisioned too

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-63 Copyright 19962005 Nortel

ALTSPFAX (Alternate Speech / Fax Group 3)


ALTSPFAX datafill defines the MSISDN and bearer capability for alternate speech/fax group 3. ALTSPFAX belongs to the FAX basic service group (BSG). Datafill

ALTSPFAX data syntax is detailed in Table 2-26. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies. the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

Table 2-26 ALTSPFAX data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

ALTSPFAX field descriptions are given in Table 2-27.


Table 2-27 ALTSPFAX field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-64 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions ALTSPFAX interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. ALTSPFAX is mutually exclusive with FAX3 the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then ALTSPFAXs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be ALTSPFAX ALTSPFAX belongs to the FAX BSG; at least one basic service from the FAX BSG must be provisioned if any BSG-SS is registered against FAX (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-65 Copyright 19962005 Nortel

AUXTPHNY (Auxiliary Telephony)


AUXTPHNY datafill defines the MSISDN and bearer capability for voice calls on an alternate line. AUXTPHNY is a Nortel proprietary service and belongs to the AUXSPCH basic service group (BSG). Datafill

AUXTPHNY data syntax is detailed in Table 2-28. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies. the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

Table 2-28 AUXTPHNY data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

AUXTPHNY field descriptions are given in Table 2-29.


Table 2-29 AUXTPHNY field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-66 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions AUXTPHNY interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. TPHNY must be provisioned for AUXTPHNY to be provisioned the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then AUXTPHNYs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be AUXTPHNY AUXTPHNY must be provisioned if any BSG-SS is registered against AUXSPCH (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-67 Copyright 19962005 Nortel

CDA (Circuit Duplex Asynchronous Data)

CDA is a special case basic service as provisioning this service is equivalent to provisioning CDA300, CDA1200, CDA1275, CDA2400, CDA4800 and CDA9600, using the datafill specified for CDA. Note that the individual CDAxxx services can be provisioned alongside CDA. For example, a subscriber may have both CDA and CDA300 provisioned. The subscriber profile will actually have all CDAxxx services. The datafill used for CDA300 will be equal to that specified for CDA300, and not equal to the CDA datafill (i.e. the CDA300 datafill takes precedence) If CDA is subsequently deprovisioned, then all CDAxxx services are removed except CDA300, as this is still explicitly provisioned. Please refer to the individual service sections for datafill/interactions details. CDA does have a special case for BCI validation, however: if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDAs BCI must not be datafilled but there is an exception: FAX3/CDA/CDS may share an MSISDN, and one of them may have a BCI if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDA9600

Note that CDA is also the name of a basic service group (BSG). When CDA is used, it typically refers to the BSG, rather than this basic service.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-68 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDA300 (Circuit Duplex Asynchronous Data 300)


CDA300 datafill defines the MSISDN and bearer capability for 300 bits/ second CDA. CDA300 belongs to the CDA basic service group (BSG). Datafill

CDA300 data syntax is detailed in Table 2-30. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-30 CDA300 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDA300 field descriptions are given in Table 2-31.


Table 2-31 CDA300 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-69 Copyright 19962005 Nortel

Interactions CDA300 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDA300 is mutually exclusive with CDAGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDA300s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDA300 CDA300 belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-70 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDA1200 (Circuit Duplex Asynchronous Data 1200)


CDA1200 datafill defines the MSISDN and bearer capability for 1200 bits/ second CDA. CDA1200 belongs to the CDA basic service group (BSG). Datafill CDA1200 data syntax is detailed in Table 2-32. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-32 CDA1200 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDA1200 field descriptions are given in Table 2-33.


Table 2-33 CDA1200 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-71 Copyright 19962005 Nortel

Interactions CDA1200 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDA1200 is mutually exclusive with CDAGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDA1200s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDA1200 CDA1200 belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-72 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDA1275 (Circuit Duplex Asynchronous Data 1275)


CDA1275 datafill defines the MSISDN and bearer capability for 1275 bits/ second CDA. CDA1275 belongs to the CDA basic service group (BSG). Datafill CDA1275 data syntax is detailed in Table 2-34. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-34 CDA1275 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDA1275 field descriptions are given in Table 2-35.


Table 2-35 CDA1275 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-73 Copyright 19962005 Nortel

Interactions CDA1275 interacts with all other basic services and all BSG supplementary services. CDA1275 is mutually exclusive with CDAGBS the MSISDN CC must match all other basic service MSISDN CCs CDA1275 belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-74 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDA2400 (Circuit Duplex Asynchronous Data 2400)


CDA2400 datafill defines the MSISDN and bearer capability for 2400 bits/ second CDA. CDA2400 belongs to the CDA basic service group (BSG). Datafill CDA2400 data syntax is detailed in Table 2-36. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-36 CDA2400 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDA2400 field descriptions are given in Table 2-37.


Table 2-37 CDA2400 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-75 Copyright 19962005 Nortel

Interactions CDA2400 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDA2400 is mutually exclusive with CDAGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDA2400s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDA2400 CDA2400 belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-76 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDA4800 (Circuit Duplex Asynchronous Data 4800)


CDA4800 datafill defines the MSISDN and bearer capability for 4800 bits/ second CDA. CDA4800 belongs to the CDA basic service group (BSG). Datafill CDA4800 data syntax is detailed in Table 2-38. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-38 CDA4800 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDA4800 field descriptions are given in Table 2-39.


Table 2-39 CDA4800 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-77 Copyright 19962005 Nortel

Interactions CDA4800 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDA4800 is mutually exclusive with CDAGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDA4800s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDA4800 CDA4800 belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-78 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDA9600 (Circuit Duplex Asynchronous Data 9600)


CDA9600 datafill defines the MSISDN and bearer capability for 9600 bits/ second CDA. CDA9600 belongs to the CDA basic service group (BSG). Datafill CDA9600 data syntax is detailed in Table 2-40. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-40 CDA9600 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDA9600 field descriptions are given in Table 2-41.


Table 2-41 CDA9600 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-79 Copyright 19962005 Nortel

Interactions CDA9600 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDA9600 is mutually exclusive with CDAGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDA9600s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDA9600 CDA9600 belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-80 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDAGBS (Circuit Duplex Asynchronous Data General Bearer Service)

CDAGBS datafill defines the MSISDN and bearer capability for CDA General Bearer Service, which allows support for all data rates up to and including 64 kbit/second. CDAGBS belongs to the CDA basic service group (BSG). Datafill CDAGBS data syntax is detailed in Table 2-42. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-42 CDAGBS data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDAGBS field descriptions are given in Table 2-43.


Table 2-43 CDAGBS field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-81 Copyright 19962005 Nortel

Interactions CDAGBS interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDAGBS is mutually exclusive with CDA (basic service), CDA300, CDA1200, CDA1275, CDA2400, CDA4800 and CDA9600 the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDAGBSs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDAGBS CDAGBS belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-82 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CDS (Circuit Duplex Synchronous Data)


CDS is a special case basic service as provisioning this service is equivalent to provisioning CDS1200, CDS2400, CDS4800 and CDS9600, using the datafill specified for CDS. Note that the individual CDSxxx services can be provisioned alongside CDS.

For example, a subscriber may have both CDS and CDS1200 provisioned. The subscriber profile will actually have all CDSxxx services. The datafill used for CDS1200 will be equal to that specified for CDS1200, and not equal to the CDS datafill (i.e. the CDS1200 datafill takes precedence) If CDS is subsequently deprovisioned, then all CDSxxx services are removed except CDS1200, as this is still explicitly provisioned. Please refer to the individual service sections for datafill/interactions details. CDS does have a special case for BCI validation, however: if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDSs BCI must not be datafilled but there is an exception: FAX3/CDA/CDS may share an MSISDN, and one of them may have a BCI if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDS9600

Note that CDS is also the name of a basic service group (BSG). When CDS is used, it typically refers to the BSG, rather than this basic service.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-83 Copyright 19962005 Nortel

CDS1200 (Circuit Duplex Synchronous Data 1200)


CDS1200 datafill defines the MSISDN and bearer capability for 1200 bits/ second CDS. CDS1200 belongs to the CDS basic service group (BSG). Datafill

CDS1200 data syntax is detailed in Table 2-44. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-44 CDS1200 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDS1200 field descriptions are given in Table 2-45.


Table 2-45 CDS1200 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-84 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions CDS1200 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDS1200 is mutually exclusive with CDSGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDS1200s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDS1200 CDS1200 belongs to the CDS BSG; at least one basic service from the CDS BSG must be provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-85 Copyright 19962005 Nortel

CDS2400 (Circuit Duplex Synchronous Data 2400)


CDS2400 datafill defines the MSISDN and bearer capability for 2400 bits/ second CDS. CDS2400 belongs to the CDS basic service group (BSG). Datafill

CDS2400 data syntax is detailed in Table 2-46. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-46 CDS2400 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDS2400 field descriptions are given in Table 2-47.


Table 2-47 CDS2400 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-86 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions CDS2400 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDS2400 is mutually exclusive with CDSGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDS2400s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDS2400 CDS2400 belongs to the CDS BSG; at least one basic service from the CDS BSG must be provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-87 Copyright 19962005 Nortel

CDS4800 (Circuit Duplex Synchronous Data 4800)


CDS4800 datafill defines the MSISDN and bearer capability for 4800 bits/ second CDS. CDS4800 belongs to the CDS basic service group (BSG). Datafill

CDS4800 data syntax is detailed in Table 2-48. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-48 CDS4800 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDS4800 field descriptions are given in Table 2-49.


Table 2-49 CDS4800 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-88 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions CDS4800 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDS4800 is mutually exclusive with CDSGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDS4800s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDS4800 CDS4800 belongs to the CDS BSG; at least one basic service from the CDS BSG must be provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-89 Copyright 19962005 Nortel

CDS9600 (Circuit Duplex Synchronous Data 9600)


CDS9600 datafill defines the MSISDN and bearer capability for 9600 bits/ second CDS. CDS9600 belongs to the CDS basic service group (BSG). Datafill

CDS9600 data syntax is detailed in Table 2-50. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-50 CDS9600 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDS9600 field descriptions are given in Table 2-51.


Table 2-51 CDS9600 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-90 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions CDS9600 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDS9600 is mutually exclusive with CDSGBS the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDS9600s BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDS9600 CDS9600 belongs to the CDS BSG; at least one basic service from the CDS BSG must be provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-91 Copyright 19962005 Nortel

CDSGBS (Circuit Duplex Synchronous Data General Bearer Service)


CDSGBS datafill defines the MSISDN and bearer capability for CDS General Bearer Service, which allows support for all data rates up to and including 64 kbit/second. An example use of this service is for support of H.324-M (circuit video calls). CDSGBS belongs to the CDS basic service group (BSG). Datafill

CDSGBS data syntax is detailed in Table 2-52. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-52 CDSGBS data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

CDSGBS field descriptions are given in Table 2-53.


Table 2-53 CDSGBS field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-92 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions CDSGBS interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. CDSGBS is mutually exclusive with CDS (basic service), CDS1200, CDS2400, CDS4800 and CDS9600 the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then CDSGBSs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be CDSGBS CDSGBS belongs to the CDS BSG; at least one basic service from the CDS BSG must be provisioned if any BSG-SS is registered against CDS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-93 Copyright 19962005 Nortel

FAX3 (Facsimile Group 3)


FAX3 datafill defines the MSISDN and bearer capability for fax3. FAX3 belongs to the FAX basic service group (BSG). Datafill FAX3 data syntax is detailed in Table 2-54. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-54 FAX3 data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

FAX3 field descriptions are given in Table 2-55.


Table 2-55 FAX3 field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-94 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions FAX3 interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. ALTSPFAX is mutually exclusive with FAX3 the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275 then FAX3s BCI must not be datafilled but there is an exception: FAX3/CDA/CDS may share an MSISDN, and one of them may have a BCI (refers to CDA/CDS basic services, not BSGs) if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be FAX3 FAX3 belongs to the FAX BSG; at least one basic service from the FAX BSG must be provisioned if any BSG-SS is registered against FAX (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-95 Copyright 19962005 Nortel

SMMO (Short Message Mobile Originating)


SMMO datafill defines the MSISDN and bearer capability for SMMO. SMMO belongs to the SMS basic service group (BSG). Datafill SMMO data syntax is detailed in Table 2-56. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-56 SMMO data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

SMMO field descriptions are given in Table 2-57.


Table 2-57 SMMO field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-96 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions SMMO interacts with all other basic services and all BSG supplementary services. TPHNY, SMMO, and SMMT must have the same MSISDN. If the MSISDN of SMMO is changed then the other two are automatically updated to match the MSISDN CC must match all other basic service MSISDN CCs SMMO belongs to the SMS BSG; at least one basic service from the SMS BSG must be provisioned if any BSG-SS is registered against SMS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-97 Copyright 19962005 Nortel

SMMT (Short Message Mobile Originating)


SMMT datafill defines the MSISDN and bearer capability for SMMT. SMMT belongs to the SMS basic service group (BSG). Datafill SMMT data syntax is detailed in Table 2-58. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-58 SMMT data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

SMMT field descriptions are given in Table 2-59.


Table 2-59 SMMT field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-98 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions SMMT interacts with all other basic services and all BSG supplementary services. TPHNY, SMMO, and SMMT must have the same MSISDN. If the MSISDN of SMMO is changed then the other two are automatically updated to match the MSISDN CC must match all other basic service MSISDN CCs SMMT belongs to the SMS BSG; at least one basic service from the SMS BSG must be provisioned if any BSG-SS is registered against SMS (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-99 Copyright 19962005 Nortel

SPCHCDA (Speech followed by CDA Data)

SPCHCDA datafill defines the MSISDN and bearer capability for speech followed by CDA data. SPCHCDA belongs to the CDA basic service group (BSG). Datafill SPCHCDA data syntax is detailed in Table 2-60. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies. the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

Table 2-60 SPCHCDA data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

SPCHCDA field descriptions are given in Table 2-61.


Table 2-61 SPCHCDA field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-100 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions SPCHCDA interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275/SPCHCDS then SPCHCDAs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be SPCHCDA SPCHCDA belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU when provisioning SPCHCDA, a BCI must be supplied unless SPCHCDS is concurrently provisioned with a BCI upon provisioning SPCHCDA, SPCHCDS is automatically provisioned with the same MSISDN and a null BCI (unless explicitly provisioned also) SPCHCDA and SPCHCDS must have the same MSISDN. Upon changing the MSISDN of one service, the other services MSISDN is automatically updated to match one of SPCHCDA/SPCHCDS must have a BCI, the other must have a null BCI. Upon changing the null BCI to a value, the other services BCI is automatically updated to have a null BCI. It is not valid to change the service with the BCI so that it has a null BCI (as then both services would have a null BCI) upon deprovisioning SPCHCDA, SPCHCDS is automatically deprovisioned too

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-101 Copyright 19962005 Nortel

SPCHCDS (Speech followed by CDS Data)


SPCHCDS datafill defines the MSISDN and bearer capability for speech followed by CDS data. SPCHCDS belongs to the CDS basic service group (BSG). Datafill SPCHCDS data syntax is detailed in Table 2-62. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies. the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

Table 2-62 SPCHCDS data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

SPCHCDS field descriptions are given in Table 2-63.


Table 2-63 SPCHCDS field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-102 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions SPCHCDS interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN of any other basic service except SMMO/SMMT/CDA1275/SPCHCDA then SPCHCDSs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY column of system table GHLRBCA, and the value in the system tables BSVC field must be SPCHCDS SPCHCDS belongs to the CDA BSG; at least one basic service from the CDA BSG must be provisioned if any BSG-SS is registered against CDA (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU when provisioning SPCHCDS, a BCI must be supplied unless SPCHCDA is concurrently provisioned with a BCI upon provisioning SPCHCDS, SPCHCDA is automatically provisioned with the same MSISDN and a null BCI (unless explicitly provisioned also) SPCHCDS and SPCHCDA must have the same MSISDN. Upon changing the MSISDN of one service, the other services MSISDN is automatically updated to match one of SPCHCDS/SPCHCDA must have a BCI, the other must have a null BCI. Upon changing the null BCI to a value, the other services BCI is automatically updated to have a null BCI. It is not valid to change the service with the BCI so that it has a null BCI (as then both services would have a null BCI) upon deprovisioning SPCHCDS, SPCHCDA is automatically deprovisioned too

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-103 Copyright 19962005 Nortel

TPHNY (Telephony)
TPHNY datafill defines the MSISDN and bearer capability for voice calls. TPHNY belongs to the SPCH basic service group (BSG). Datafill

TPHNY data syntax is detailed in Table 2-64. The three MSISDN fields are combined to give the complete MSISDN (i.e. CC + NDC + SN). The following intra-service validation applies.
Table 2-64 TPHNY data syntax Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Syntax 1 to 3 digits, first digit cannot be zero 1 to 13 digits 1 to 13 digits number: 0 - 255 Optional Optional

the length of the complete MSISDN (i.e. CC + NDC + SN) must be 3 to 15 digits

TPHNY field descriptions are given in Table 2-65.


Table 2-65 TPHNY field descriptions Dataitem MSISDN CC MSISDN NDC MSISDN SN BCI Description Mobile Subscriber ISDN, Country Code component Mobile Subscriber ISDN, National Destination Code component Mobile Subscriber ISDN, subscriber number Bearer Capability Index, defined in system table GHLRBCA

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-104 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions TPHNY interacts with all other basic services, all BSG supplementary services and system table GHLRBCA. TPHNY must be provisioned for AUXTPHNY to be provisioned TPHNY, SMMO, and SMMT must have the same MSISDN. If the MSISDN of TPHNY is changed then the other two are automatically updated to match. the MSISDN CC must match all other basic service MSISDN CCs if the MSISDN matches the MSISDN for any other basic service except SMMO/SMMT/CDA1275 then TPHNYs BCI must not be datafilled if datafilled, the BCI must be an entry from the BCAKEY field of system table GHLRBCA, and the value in the system tables BSVC field must be TPHNY TPHNY must be provisioned if any BSG-SS is registered against SPCH (services BAIC, BICRoam, BAOC, BOIC, BOICexHC, CFB, CFNRc, CFNRy, CFU, COS, CUG, CW and EXT) the MSISDN must not match any FTN of CFB, CFNRc, CFNRy or CFU

HLR-wide validations the MSISDN cannot be used by any other subscriber (interacts with all basic services (except VBS/VGCS) for all subscribers)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-105 Copyright 19962005 Nortel

VBS (Voice Broadcast Service)


VBS belongs to the voice group services (VGS) basic service group (BSG). VGS basic services have different datafill to all other basic services. VBS datafill defines groups that the subscriber belongs to for VBS functionality. Datafill VBS data syntax is detailed in Table 2-66. The following intra-service validations apply.

all datafill is optional; however, if Functions outside HPLMN is datafilled then at least one Group must be datafilled (similarly, if at least one Group is datafilled then Functions outside HPLMN must be datafilled) within the Groups vector, duplicate IDs are not permitted

Table 2-66 VBS data syntax Dataitem

Syntax Boolean composed of the two dataitems below 3 digits Boolean

Optional Optional All 50 are Optional as above as above

Functions outside HPLMN Groups Vector (0 - 50) - ID - Origination Entitlement

VBS field descriptions are given in Table 2-67.


Table 2-67 VBS field descriptions Dataitem Functions outside HPLMN Description indicates whether subscriber can use VBS when roaming out of the HPLMN vector of groups a group ID indicates whether the subscriber can originate calls to this group

Groups Vector (0 - 50) - ID - Origination Entitlement

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-106 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

VGCS (Voice Group Call Service)

VGCS belongs to the voice group services (VGS) basic service group (BSG). VGS basic services have different datafill to all other basic services. VGCS datafill defines groups that the subscriber belongs to for VBS functionality. Datafill VGCS data syntax is detailed in Table 2-68. The following intra-service validations apply. all datafill is optional; however, if Functions outside HPLMN is datafilled then at least one Group must be datafilled (similarly, if at least one Group is datafilled then Functions outside HPLMN must be datafilled) within the Groups vector, duplicate IDs are not permitted

Table 2-68 VGCS data syntax Dataitem

Syntax Boolean 3 digits

Optional Optional All 50 are Optional

Functions outside HPLMN Group IDs Vector (0 - 50)

VGCS field descriptions are given in Table 2-69.


Table 2-69 VGCS field descriptions Dataitem Functions outside HPLMN Description indicates whether subscriber can use VBS when roaming out of the HPLMN a group ID

Group ID

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-107 Copyright 19962005 Nortel

Supplementary Services introduction

Supplementary Services (SSs) modify or enhance basic services. Each SS only applies to certain basic service groups (BSGs). There are two major SS groups: IMSI-based and BSG-based. IMSI-based services have datafill that applies to all the basic service groups they apply to. BSG-based services have datafill specific to each basic service group they apply to. BSG-SSs have registration sets, with each set having registered/activated/ suppression states (suppression states are temporary/changeable data that are a result of interactions between the subscribers services and location and are therefore not part of the subscriber profile). IMSI-SSs do not have registration sets, hence simply have a provisioned state. The HLR supports the supplementary services given in Table 2-70. The Group column gives the SS group type as used in the specifications (a proprietary service does not belong to one of these groups and is marked as such). Note that CUG has two separate lots of datafill: CUG Feature data and CUG Subscription data.
Table 2-70 Supplementary Services (2 pages) Short Name ACC ACRJ AOCC AOCI BAIC BAOC BICRoam Expanded Name Group Type See Section

Accounting Codes Anonymous Call Rejection Advice of Charge Charging Advice of Charge Information Barring of all Incoming Calls Barring of all Outgoing Calls Barring of all Incoming Calls when Roaming outside HPLMN country Barring of Outgoing International Calls Barring of Outgoing International Calls except to HPLMN Country Call Forward when Busy

Proprietary Proprietary Charging Charging Barring Barring Barring

IMSI IMSI IMSI IMSI BSG BSG BSG

on page 2-109 on page 2-110 on page 2-111 on page 2-112 on page 2-113 on page 2-115 on page 2-117

BOIC

Barring

BSG

on page 2-119

BOICexHC

Barring

BSG

on page 2-121

CFB

Forwarding

BSG

on page 2-123

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-108 Chapter 2: Component descriptions Nortel Confidential Table 2-70 Supplementary Services (2 pages) Short Name CFNRc Expanded Name Group

Copyright

19962005 Nortel

Type

See Section

Call Forward when Not Reachable Call Forward when No Reply Call Forward Unconditionally Calling Line ID Presentation Calling Line ID Restriction Calling Name Delivery Connected Line ID Presentation Connected Line ID Restriction Class Of Service Closed User Groups

Forwarding

BSG

on page 2-130

CFNRy CFU CLIP CLIR CNAM COLP COLR COS CUG

Forwarding Forwarding Line Identification Line Identification Proprietary Line Identification Line Identification Proprietary Community of Interest Call Completion Call Offering Call Priority

BSG BSG IMSI IMSI IMSI IMSI IMSI BSG BSG

on page 2-136 on page 2-143 on page 2-150 on page 2-151 on page 2-152 on page 2-153 on page 2-154 on page 2-155 on page 2-158

CW ECT EMLPP

Call Waiting Explicit Call Transfer Enhanced Multi Level Precedence & Pre-emption Extension Services Follow Me Call Hold Hot Billing Local Calls Only Malicious Call Trace Multi-Party User to User Signalling stage 1

BSG IMSI IMSI

on page 2-164 on page 2-166 on page 2-167

EXT FM HOLD HOTBILL LCO MCT MPTY UUS1

Proprietary Follow Me Call Completion Proprietary Proprietary Proprietary MultiParty Additional Info Transfer Call Priority

BSG IMSI IMSI IMSI IMSI IMSI IMSI IMSI

on page 2-168 on page 2-175 on page 2-177 on page 2-178 on page 2-179 on page 2-180 on page 2-181 on page 2-182

WPS

Wireless Priority Service

IMSI

on page 2-183

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-109 Copyright 19962005 Nortel

ACC (Accounting Codes)

ACC datafill defines the verification of the account code entered by the subscriber when originating a call. ACC is a Nortel proprietary IMSI-SS and applies to all BSGs except VGS. Datafill ACC data syntax is detailed in Table 2-71. The following intra-service interactions apply.
Table 2-71 ACC data syntax Dataitem Option Verification Length Syntax {VER, NONVER, VOL} number: 1 - 16 Optional Optional

Verification Length must be datafilled if the Option is set to VER; Verification Length must not be datafilled for other Options

ACC field descriptions are given in Table 2-72.


Table 2-72 ACC field descriptions Dataitem Option Description verification of the account code option: verified (VER), non-verified (NONVER), voluntary (VOL) the valid length of the account code (only used with the verified option)

Verification Length

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-110 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

ACRJ (Anonymous Call Rejection)


Provisioning ACRJ enables anonymous call reject functionality for the subscriber (ACRJ rejects anonymous calls, i.e. those where its calling line identification number presentation is set to restricted). ACRJ is a Nortel proprietary IMSI-SS and applies to all BSGs except SMS and VGS. Datafill ACRJ has no dataitems, it is simply provisioned or deprovisioned. Interactions ACRJ interacts with CLIP. for ACRJ to be provisioned, CLIP must be provisioned and have its Override dataitem set to FALSE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-111 Copyright 19962005 Nortel

AOCC (Advice of Charge Charging)

Provisioning AOCC enables advice of charge charging functionality for the subscriber (AOCC allows a subscriber to request charging information; calls are not allowed if this information is not available). AOCC is an IMSI-SS and applies to all BSGs except SMS and VGS. Datafill AOCC has no dataitems, it is simply provisioned or deprovisioned. Interactions AOCC interacts with AOCI. AOCC and AOCI are mutually exclusive

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-112 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

AOCI (Advice of Charge Information)

Provisioning AOCI enables advice of charge information functionality for the subscriber (AOCI allows a subscriber to request charging information; calls are allowed if this information is not available). AOCI is an IMSI-SS and applies to all BSGs except SMS and VGS. Datafill AOCI has no dataitems, it is simply provisioned or deprovisioned. Interactions AOCI interacts with AOCC. AOCI and AOCC are mutually exclusive

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-113 Copyright 19962005 Nortel

BAIC (Barring of All Incoming Calls)


BAIC is a basic service group based supplementary service (BSG-SS), with its datafill defining which BSGs (supported by the service) are barred for incoming calls. Datafill BAIC data syntax is detailed in Table 2-73. Each of the registration sets is optional.
Table 2-73 BAIC data syntax Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Syntax Boolean Boolean Boolean Boolean Boolean Boolean Optional

BAIC field descriptions are given in Table 2-74.


Table 2-74 BAIC field descriptions Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Description indicates whether the SPCH registration is activated indicates whether the AUXSPCH registration is activated indicates whether the SMS registration is activated indicates whether the CDA registration is activated indicates whether the CDS registration is activated indicates whether the FAX registration is activated

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-114 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions BAIC interacts with all basic services (except VBS and VGCS), all call forwards (CFB, CFNRc, CFNRy, CFU) and BICRoam. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except VBS and VGCS) interactions with BSG-SSs are given in Table 2-75 below. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-75 BAIC registration set interactions Validate Against Service CFU State Reg Set Activated BAIC and CFU are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction BAIC and CFB are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction BAIC and CFNRc are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction BAIC and CFNRy are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction the BICRoam reg set is deregistered Interaction

CFB

Reg Set Activated

CFNRc

Reg Set Activated

CFNRy

Reg Set Activated

BICRoam

Reg Set Activated

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-115 Copyright 19962005 Nortel

BAOC (Barring of All Outgoing Calls)

BAOC is a basic service group based supplementary service (BSG-SS), with its datafill defining which BSGs (supported by the service) are barred for outgoing calls. Datafill BAOC data syntax is detailed in Table 2-76. Each of the registration sets is optional.
Table 2-76 BAOC data syntax Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set VGS Reg Set Activated Activated Activated Activated Activated Activated Activated Syntax Boolean Boolean Boolean Boolean Boolean Boolean Boolean Optional

BAOC field descriptions are given in Table 2-77.


Table 2-77 BAOC field descriptions Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set VGS Reg Set Activated Activated Activated Activated Activated Activated Activated Description indicates whether the SPCH registration is activated indicates whether the AUXSPCH registration is activated indicates whether the SMS registration is activated indicates whether the CDA registration is activated indicates whether the CDS registration is activated indicates whether the FAX registration is activated indicates whether the VGS registration is activated

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-116 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions BAOC interacts with all basic services, all call forwards (CFB, CFNRc, CFNRy, CFU), BOIC and BOICexHC. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services) interactions with BSG-SSs are given in Table 2-78 below. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-78 BAIC registration set interactions Validate Against Service CFU State Reg Set Activated BAOC and CFU are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction BAOC and CFB are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction BAOC and CFNRc are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction BAOC and CFNRy are mutually exclusive per-reg set, unless the subscriber has TIF-FTNs (see section ) in which case there is no interaction the BOIC reg set is deregistered the BOICexHC reg set is deregistered Interaction

CFB

Reg Set Activated

CFNRc

Reg Set Activated

CFNRy

Reg Set Activated

BOIC BOICexHC

Reg Set Activated Reg Set Activated

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-117 Copyright 19962005 Nortel

BICRoam (Barring of Incoming Calls when Roaming outside HPLMN country)

BICRoam is a basic service group based supplementary service (BSG-SS), with its datafill defining which BSGs (supported by the service) are barred for incoming calls when the subscriber is roaming outside the HPLMN country. Datafill BICRoam data syntax is detailed in Table 2-79. Each of the registration sets is optional.
Table 2-79 BICRoam data syntax Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Syntax Boolean Boolean Boolean Boolean Boolean Boolean Optional

BICRoam field descriptions are given in Table 2-80.


Table 2-80 BICRoam field descriptions Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Description indicates whether the SPCH registration is activated indicates whether the AUXSPCH registration is activated indicates whether the SMS registration is activated indicates whether the CDA registration is activated indicates whether the CDS registration is activated indicates whether the FAX registration is activated

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-118 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions BICRoam interacts with all basic services (except VBS and VGCS) and BAIC. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except VBS and VGCS) interactions with BSG-SSs are given in Table 2-81 below. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-81 BICRoam registration set interactions Validate Against Service BAIC State Reg Set Activated the BAIC reg set is deregistered unless BAIC is registered in the current transaction, in which case the BICRoam reg set is deregistered Interaction

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-119 Copyright 19962005 Nortel

BOIC (Barring of Outgoing International Calls)


BOIC is a basic service group based supplementary service (BSG-SS), with its datafill defining which BSGs (supported by the service) are barred for outgoing international calls. Datafill BOIC data syntax is detailed in Table 2-82. Each of the registration sets is optional.
Table 2-82 BOIC data syntax Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Syntax Boolean Boolean Boolean Boolean Boolean Boolean Optional

BOIC field descriptions are given in Table 2-83.


Table 2-83 BOIC field descriptions Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Description indicates whether the SPCH registration is activated indicates whether the AUXSPCH registration is activated indicates whether the SMS registration is activated indicates whether the CDA registration is activated indicates whether the CDS registration is activated indicates whether the FAX registration is activated

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-120 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions BOIC interacts with all basic services (except VBS and VGCS), CFU, BAOC, BOICexHC and system table GHLRPCC. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except VBS and VGCS) interactions with BSG-SSs are given in Table 2-84 below. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-84 BOIC registration set interactions Validate Against Service CFU State Reg Set Activated BOIC and CFU are mutually exclusive per-reg set if the subscriber has GSM-FTNs (see section ) and the CFU FTN is international w.r.t. the HPLMN Country (see section , requires system table GHLRPCC) the BAOC reg set is deregistered unless BAOC is registered in the current transaction, in which case the BOIC reg set is deregistered BOICexHC Reg Set Activated the BOICexHC reg set is deregistered Interaction

BAOC

Reg Set Activated

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-121 Copyright 19962005 Nortel

BOICexHC (Barring of Outgoing International Calls except to HPLMN Country)

BOICexHC is a basic service group based supplementary service (BSG-SS), with its datafill defining which BSGs (supported by the service) are barred for outgoing international calls, except those to the HPLMN country. Datafill BOICexHC data syntax is detailed in Table 2-85. Each of the registration sets is optional.
Table 2-85 BOICexHC data syntax Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Syntax Boolean Boolean Boolean Boolean Boolean Boolean Optional

BOICexHC field descriptions are given in Table 2-86.


Table 2-86 BOICexHC field descriptions Dataitem SPCH Reg Set AUXSPCH Reg Set SMS Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Activated Description indicates whether the SPCH registration is activated indicates whether the AUXSPCH registration is activated indicates whether the SMS registration is activated indicates whether the CDA registration is activated indicates whether the CDS registration is activated indicates whether the FAX registration is activated

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-122 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions BOICexHC interacts with all basic services (except VBS and VGCS), CFU, BAOC, BOIC and system table GHLRPCC. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except VBS and VGCS) interactions with BSG-SSs are given in Table 2-87. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-87 BOICexHC registration set interactions Validate Against Service CFU State Reg Set Activated BOICexHC and CFU are mutually exclusive per-reg set if the subscriber has GSM-FTNs (see section ) and the CFU FTN is international w.r.t. the HPLMN Country (see section , requires system table GHLRPCC) the BAOC reg set is deregistered unless BAOC is registered in the current transaction, in which case the BOIC reg set is deregistered BOIC Reg Set Activated the BOIC reg set is deregistered unless BOIC is registered in the current transaction, in which case the BOICexHC reg set is deregistered Interaction

BAOC

Reg Set Activated

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-123 Copyright 19962005 Nortel

CFB (Call Forward when Busy)


CFB is a basic service group based supplementary service (BSG-SS), allowing forward to numbers (FTNs) to be datafilled for call forwarding when busy against the BSGs the service supports. Datafill CFB data syntax is detailed in Table 2-88. Each of the registration sets is optional.

The validation of CFB is complicated by its interaction with ESMR LCO Translations. If these translations are enabled then CFBs FTNs are passed through these translations to normalise the number (i.e convert it to international E164 format) and to determine whether the number is local. The syntax checks in apply to the post-translated number. The syntax check for pre-translated FTNs is that they contain 1 - 15 digits (with no restriction on the first digit). The local indication is required in CFBs interaction with LCO service. Note that if ESMR LCO translations are not enabled, then no translations occur and the FTN defaults to being not local. Meaning of ESMR LCO These are a particular type of translations used to normalise DNs and determine their localness. They are enabled on the HLR if key 1021 is datafilled in system table XLAENTRY and there is associated translations tables datafill. The term ESMR is used due to these translations being particularly used in the north American market.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-124 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

.
Table 2-88 CFB data syntax Dataitem NCP NFP DCF ID SPCH Reg Set Activated NOA NPI FTN AUXSPCH Reg Set Activated NOA NPI FTN CDA Reg Set Activated NOA NPI FTN CDS Reg Set Activated NOA NPI FTN FAX Reg Set Activated NOA NPI FTN Syntax {NONF, NF, NFWN} {NONF, NF, NFWN} 1 - 20 characters Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Optional Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-125 Copyright 19962005 Nortel

CFB field descriptions are given in Table 2-89.


Table 2-89 CFB field descriptions Dataitem NCP Description Notify Calling Party option: No-notification (NONF), Notification (NF), Notification-with-number (NFWN) Notify Forwarding Party option: No-notification (NONF), Notification (NF), Notification-with-number (NFWN) Default Call Forwarding ID, defined in system table GHLRDCF Activated NOA indicates whether the SPCH registration is activated the FTN Nature Of Address for the SPCH registration; options are Unknown (UNKN), International-number (INTL), Nationalsignificant-number (NTL), Network-specific-number (NTWK), Subscriber-number (SUBS) and Abbreviated-number (ABBR) the FTN Number Plan Indicator for the SPCH registration; options are Unknown (UNKN), ISDN/telephony-numberingplan (E164), Data-numbering-plan (X121), Telex-numberingplan (F69), Land-mobile-numbering-plan (E212), Nationalnumbering-plan (NATL) and Private-numbering-plan (PRIV) the Forward To Number for the SPCH registration also known as the call forward number AUXSPCH Reg Set Activated NOA indicates whether the AUXSPCH registration is activated the FTN Nature Of Address for the AUXSPCH registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the AUXSPCH registration; for options see SPCH Reg Set the Forward To Number for the AUXSPCH registration also known as the call forward number

NFP

DCF ID SPCH Reg Set

NPI

FTN

NPI

FTN

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-126 Chapter 2: Component descriptions Nortel Confidential Table 2-89 CFB field descriptions Dataitem CDA Reg Set Activated NOA Description

Copyright

19962005 Nortel

indicates whether the CDA registration is activated the FTN Nature Of Address for the CDA registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDA registration; for options see SPCH Reg Set the Forward To Number for the CDA registration also known as the call forward number

NPI

FTN

CDS Reg Set

Activated NOA

indicates whether the CDS registration is activated the FTN Nature Of Address for the CDS registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDS registration; for options see SPCH Reg Set the Forward To Number for the CDS registration also known as the call forward number

NPI

FTN

FAX Reg Set

Activated NOA

indicates whether the FAX registration is activated the FTN Nature Of Address for the FAX registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the FAX registration; for options see SPCH Reg Set the Forward To Number for the FAX registration also known as the call forward number

NPI

FTN

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-127 Copyright 19962005 Nortel

Interactions CFB interacts with all basic services (except VBS and VGCS), BAOC, BAIC, CFU, LCO, ODB BAIC, ODB BAOC, ODB PremRate categories, O-CSI and system tables GHLRDCF and GHLRODB. Note that CFBs interactions are identical to that of CFNRc and CFNRy. if the DCF ID is datafilled, it must be an entry from the DCFID field of system table GHLRDCF, and the FTNCHECK field must match the subscribers FTN type (depends on O-CSI, see Determining FTN type on page 2-129) for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except SMMO, SMMT, VBS and VGCS) none of the FTNs must match any of the subscribers basic service MSISDNs (interacts with all basic services except VBS and VGCS) the FTN format and NOA/NPI combination is checked against the subscribers FTN-type (interacts with O-CSI (see Determining FTN type on page 2-129): GSM-FTNs: length must have 4 - 15 digits, first digit must not be zero; NOA must be INTL, NPI must be E164 Custom-FTNs: length must have 1 - 15 digits; NOA must be UNKN, NPI must be UNKN TIF-FTNs: length must have 1 - 15 digits; NOA and NPI can take any values, however if NOA/NPI is INTL/E164 then additional checks apply to the FTN format: must be 4 - 15 digits and first digit must not be zero interactions with BSG-SSs and ODBs are given in Table 2-90 on page 2128. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-128 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

.
Table 2-90 CFB registration set interactions Validate Against Service BAIC State Reg Set Activated CFB and BAIC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB and BAOC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after CFU has been registered CFB and LCO are mutually exclusive if (1) the subscriber has GSM FTNs* and (2) any CFB FTN is not local CFB cannot be newly registered after ODB BAIC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after ODB BAOC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after ODB Prem Rate (Ent or Info) is provisioned if (1) the subscriber has GSM FTNs AND (2) the FTN is barred according to its lookup in system table GHRLODB. Interaction

BAOC

Reg Set Activated

CFU

Reg Set Activated

LCO

Provisioned

ODB BAIC

Provisioned

ODB BAOC

Provisioned

ODB Prem Rate categories

Provisioned

* FTN type determination is discussed in Determining FTN type on page 2-129

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-129 Copyright 19962005 Nortel

Additional information Determining FTN type A subscriber may have GSM-FTNs, TIF-FTNs or Custom-FTNs. If the subscriber does not have O-CSI provisioned then they have GSM-FTNs. If the subscriber does have O-CSI provisioned, then their FTN type is determined by the FTN Checks field -- the field can be set to GSM, TIF or Custom. Therefore for instance, a TIF-FTNs subscriber has O-CSI provisioned, with FTN Checks set to TIF. Determining if an FTN is international w.r.t. HPLMN country Whether an FTN is international with respect to the HPLMN Country is important in some interactions with CFB. The following steps are taken in this determination: the subscribers primary MSISDN is determined (requires all basic services except VBS and VGCS) the primary MSISDN CC is mapped to a Pseudo Country Code (PCC) by doing a lookup in the TO/FROM fields of system table GHLRPCC the CFB FTN is also mapped to a PCC by doing a lookup in the TO/FROM fields of system table GHLRPCC if either number does not map to a PCC then it is a translations error, and the datafill is not valid the two PCCs are compared -- the FTN is international w.r.t. the HPLMN Country if they differ

DCF ID activation state determination The DCF ID does have an activation state, but it is not provisionable and is only determined on demand (e.g. when a MAP message to the HLR requests it). It is therefore, strictly speaking, not part of the subscriber profile. For information only, here are details regarding the DCF activation state: For non-TIF-FTN subscribers: DCF is deactivated if the subscriber has BAOC or BAIC. DCF is suppressed if the subscriber has BICRoam (act/ not sup), ODB BAOC, ODB BAOCRoam (act), ODB BAIC or ODB BICRoam (act) If the subscriber has CFU then DCF is always deactivated For GSM-FTN subscribers: DCF is suppressed if the subscriber has LCO (ESMR or non-ESMR), BOIC (act, number intl), BOICexHC (act, number intlexHC), ODB BOIC (number intl), ODB BOICexHC (number intlexHC), ODB PremRate (number barred) or ODB HPLMN Spec (act, number barred)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-130 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CFNRc (Call Forward when Not Reachable)

CFNRc is a basic service group based supplementary service (BSG-SS), allowing forward to numbers (FTNs) to be datafilled for call forwarding when not reachable (i.e. the MS is detached, there is radio congestion or there is no page response/temporarily unavailable) against the BSGs the service supports. Datafill CFNRc data syntax is detailed in Table 2-91 on page 2-131. Each of the registration sets is optional. The validation of CFNRc is complicated by its interaction with ESMR LCO Translations. If these translations are enabled then CFNRcs FTNs are passed through these translations to normalise the number (i.e convert it to international E164 format) and to determine whether the number is local. The syntax checks in apply to the post-translated number. The syntax check for pre-translated FTNs is that they contain 1 - 15 digits (with no restriction on the first digit). The local indication is required in CFNRcs interaction with LCO service. Note that if ESMR LCO translations are not enabled, then no translations occur and the FTN defaults to being not local. Meaning of ESMR LCO These are a particular type of translations used to normalise DNs and determine their localness. They are enabled on the HLR if key 1021 is datafilled in system table XLAENTRY and there is associated translations tables datafill. The term ESMR is used due to these translations being particularly used in the north American market.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-131 Copyright 19962005 Nortel

.
Table 2-91 CFNRc data syntax Dataitem NCP DCF ID SPCH Reg Set Activated NOA NPI FTN AUXSPCH Reg Set Activated NOA NPI FTN CDA Reg Set Activated NOA NPI FTN CDS Reg Set Activated NOA NPI FTN FAX Reg Set Activated NOA NPI FTN Syntax {NONF, NF, NFWN} 1 - 20 characters Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Optional Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-132 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

CFNRc field descriptions are given in Table 2-92.


Table 2-92 CFNRc field descriptions (2 pages) Dataitem NCP Description Notify Calling Party option: No-notification (NONF), Notification (NF), Notification-with-number (NFWN) Default Call Forwarding ID, defined in system table GHLRDCF Activated NOA indicates whether the SPCH registration is activated the FTN Nature Of Address for the SPCH registration; options are Unknown (UNKN), International-number (INTL), Nationalsignificant-number (NTL), Network-specific-number (NTWK), Subscriber-number (SUBS) and Abbreviated-number (ABBR) the FTN Number Plan Indicator for the SPCH registration; options are Unknown (UNKN), ISDN/telephony-numberingplan (E164), Data-numbering-plan (X121), Telex-numberingplan (F69), Land-mobile-numbering-plan (E212), Nationalnumbering-plan (NATL) and Private-numbering-plan (PRIV) the Forward To Number for the SPCH registration also known as the call forward number AUXSPCH Reg Set Activated NOA indicates whether the AUXSPCH registration is activated the FTN Nature Of Address for the AUXSPCH registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the AUXSPCH registration; for options see SPCH Reg Set the Forward To Number for the AUXSPCH registration also known as the call forward number CDA Reg Set Activated NOA indicates whether the CDA registration is activated the FTN Nature Of Address for the CDA registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDA registration; for options see SPCH Reg Set the Forward To Number for the CDA registration also known as the call forward number

DCF ID SPCH Reg Set

NPI

FTN

NPI

FTN

NPI

FTN

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-92 CFNRc field descriptions (2 pages) Dataitem CDS Reg Set Activated NOA Description

Chapter 2: Component descriptions 2-133 Copyright 19962005 Nortel

indicates whether the CDS registration is activated the FTN Nature Of Address for the CDS registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDS registration; for options see SPCH Reg Set the Forward To Number for the CDS registration also known as the call forward number

NPI

FTN

FAX Reg Set

Activated NOA

indicates whether the FAX registration is activated the FTN Nature Of Address for the FAX registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the FAX registration; for options see SPCH Reg Set the Forward To Number for the FAX registration also known as the call forward number

NPI

FTN

Interactions CFNRc interacts with all basic services (except VBS and VGCS), BAOC, BAIC, CFU, LCO, ODB BAIC, ODB BAOC, ODB PremRate categories, O-CSI and system tables GHLRDCF and GHLRODB. Note that CFNRcs interactions are identical to that of CFB and CFNRy. if the DCF ID is datafilled, it must be an entry from the DCFID field of system table GHLRDCF, and the FTNCHECK field must match the subscribers FTN type (depends on O-CSI, see Determining FTN type on page 2-135) for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except SMMO, SMMT, VBS and VGCS) none of the FTNs must match any of the subscribers basic service MSISDNs (interacts with all basic services except VBS and VGCS) the FTN format and NOA/NPI combination is checked against the subscribers FTN-type (interacts with O-CSI (see Determining FTN type on page 2-135):

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-134 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

GSM-FTNs: length must have 4 - 15 digits, first digit must not be zero; NOA must be INTL, NPI must be E164 Custom-FTNs: length must have 1 - 15 digits; NOA must be UNKN, NPI must be UNKN TIF-FTNs: length must have 1 - 15 digits; NOA and NPI can take any values, however if NOA/NPI is INTL/E164 then additional checks apply to the FTN format: must be 4 - 15 digits and first digit must not be zero interactions with BSG-SSs and ODBs are given in Table 2-93 below. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-93 CFNRc registration set interactions Validate Against Service BAIC State Reg Set Activated CFB and BAIC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB and BAOC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after CFU has been registered CFB and LCO are mutually exclusive if (1) the subscriber has GSM FTNs* and (2) any CFB FTN is not local CFB cannot be newly registered after ODB BAIC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after ODB BAOC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after ODB Prem Rate (Ent or Info) is provisioned if (1) the subscriber has GSM FTNs AND (2) the FTN is barred according to its lookup in system table GHRLODB. Interaction

BAOC

Reg Set Activated

CFU

Reg Set Activated

LCO

Provisioned

ODB BAIC

Provisioned

ODB BAOC

Provisioned

ODB Prem Rate categories

Provisioned

* FTN type determination is discussed in Determining FTN type on page 2-135


411-2831-332 Preliminary 01.02 March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-135 Copyright 19962005 Nortel

Additional information Determining FTN type A subscriber may have GSM-FTNs, TIF-FTNs or Custom-FTNs. If the subscriber does not have O-CSI provisioned then they have GSM-FTNs. If the subscriber does have O-CSI provisioned, then their FTN type is determined by the FTN Checks field -- the field can be set to GSM, TIF or Custom. Therefore for instance, a TIF-FTNs subscriber has O-CSI provisioned, with FTN Checks set to TIF. Determining if an FTN is international w.r.t. HPLMN country Whether an FTN is international with respect to the HPLMN Country is important in some interactions with CFB. The following steps are taken in this determination: the subscribers primary MSISDN is determined (requires all basic services except VBS and VGCS) the primary MSISDN CC is mapped to a Pseudo Country Code (PCC) by doing a lookup in the TO/FROM fields of system table GHLRPCC the CFB FTN is also mapped to a PCC by doing a lookup in the TO/FROM fields of system table GHLRPCC if either number does not map to a PCC then it is a translations error, and the datafill is not valid the two PCCs are compared -- the FTN is international w.r.t. the HPLMN Country if they differ

DCF ID activation state determination The DCF ID does have an activation state, but it is not provisionable and is only determined on demand (e.g. when a MAP message to the HLR requests it). It is therefore, strictly speaking, not part of the subscriber profile. For information only, here are details regarding the DCF activation state: For non-TIF-FTN subscribers: DCF is deactivated if the subscriber has BAOC or BAIC. DCF is suppressed if the subscriber has BICRoam (act/ not sup), ODB BAOC, ODB BAOCRoam (act), ODB BAIC or ODB BICRoam (act) If the subscriber has CFU then DCF is always deactivated. For GSM-FTN subscribers: DCF is suppressed if the subscriber has LCO (ESMR or non-ESMR), BOIC (act, number intl), BOICexHC (act, number intlexHC), ODB BOIC (number intl), ODB BOICexHC (number intlexHC), ODB PremRate (number barred) or ODB HPLMN Spec (act, number barred)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-136 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CFNRy (Call Forward when No Reply)

CFNRy is a basic service group based supplementary service (BSG-SS), allowing forward to numbers (FTNs) to be datafilled for call forwarding when no reply within a specified time against the BSGs the service supports. Datafill CFNRy data syntax is detailed in Table 2-94. Each of the registration sets is optional. The validation of CFNRy is complicated by its interaction with ESMR LCO Translations. If these translations are enabled then CFNRys FTNs are passed through these translations to normalise the number (i.e convert it to international E164 format) and to determine whether the number is local. The syntax checks in apply to the post-translated number. The syntax check for pre-translated FTNs is that they contain 1 - 15 digits (with no restriction on the first digit). The local indication is required in CFNRys interaction with LCO service. Note that if ESMR LCO translations are not enabled, then no translations occur and the FTN defaults to being not local. Meaning of ESMR LCO These are a particular type of translations used to normalise DNs and determine their localness. They are enabled on the HLR if key 1021 is datafilled in system table XLAENTRY and there is associated translations tables datafill. The term ESMR is used due to these translations being particularly used in the north American market.
Table 2-94 CFNRy data syntax (2 pages) Dataitem NCP NFP DCF ID SPCH Reg Set Activated NOA NPI FTN No Reply Time Syntax {NONF, NF, NFWN} {NONF, NF, NFWN} 1 - 20 characters Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits number: 5 - 30 (must be a multiple of 5) Optional Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-94 CFNRy data syntax (2 pages) Dataitem AUXSPCH Reg Set Activated NOA NPI FTN No Reply Time CDA Reg Set Activated NOA NPI FTN No Reply Time CDS Reg Set Activated NOA NPI FTN No Reply Time FAX Reg Set Activated NOA NPI FTN No Reply Time Syntax Boolean

Chapter 2: Component descriptions 2-137 Copyright 19962005 Nortel

Optional

{UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits number: 5 - 30 (must be a multiple of 5) Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits number: 5 - 30 (must be a multiple of 5) Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits number: 5 - 30 (must be a multiple of 5) Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits number: 5 - 30 (must be a multiple of 5)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-138 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

CFNRy field descriptions are given in Table 2-95.


Table 2-95 CFNRy field descriptions (2 pages) Dataitem NCP Description Notify Calling Party option: No-notification (NONF), Notification (NF), Notification-with-number (NFWN) Notify Forwarding Party option: No-notification (NONF), Notification (NF), Notification-with-number (NFWN) Default Call Forwarding ID, defined in system table GHLRDCF Activated NOA indicates whether the SPCH registration is activated the FTN Nature Of Address for the SPCH registration; options are Unknown (UNKN), International-number (INTL), National-significant-number (NTL), Network-specificnumber (NTWK), Subscriber-number (SUBS) and Abbreviated-number (ABBR) the FTN Number Plan Indicator for the SPCH registration; options are Unknown (UNKN), ISDN/telephony-numberingplan (E164), Data-numbering-plan (X121), Telexnumbering-plan (F69), Land-mobile-numbering-plan (E212), National-numbering-plan (NATL) and Privatenumbering-plan (PRIV) the Forward To Number for the SPCH registration also known as the call forward number No Reply Time AUXSPCH Reg Set Activated NOA the no-reply time for the SPCH registration indicates whether the AUXSPCH registration is activated the FTN Nature Of Address for the AUXSPCH registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the AUXSPCH registration; for options see SPCH Reg Set the Forward To Number for the AUXSPCH registration also known as the call forward number No Reply Time the no-reply time for the SPCH registration

NFP

DCF ID

SPCH Reg Set

NPI

FTN

NPI

FTN

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-95 CFNRy field descriptions (2 pages) Dataitem CDA Reg Set Activated NOA Description

Chapter 2: Component descriptions 2-139 Copyright 19962005 Nortel

indicates whether the CDA registration is activated the FTN Nature Of Address for the CDA registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDA registration; for options see SPCH Reg Set the Forward To Number for the CDA registration also known as the call forward number

NPI

FTN

No Reply Time CDS Reg Set Activated NOA

the no-reply time for the SPCH registration indicates whether the CDS registration is activated the FTN Nature Of Address for the CDS registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDS registration; for options see SPCH Reg Set the Forward To Number for the CDS registration also known as the call forward number

NPI

FTN

No Reply Time FAX Reg Set Activated NOA

the no-reply time for the SPCH registration indicates whether the FAX registration is activated the FTN Nature Of Address for the FAX registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the FAX registration; for options see SPCH Reg Set the Forward To Number for the FAX registration also known as the call forward number

NPI

FTN

No Reply Time

the no-reply time for the SPCH registration

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-140 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions CFNRy interacts with all basic services (except VBS and VGCS), BAOC, BAIC, CFU, LCO, ODB BAIC, ODB BAOC, ODB PremRate categories, O-CSI and system tables GHLRDCF and GHLRODB. Note that CFNRys interactions are identical to that of CFB and CFNRc. if the DCF ID is datafilled, it must be an entry from the DCFID field of system table GHLRDCF, and the FTNCHECK field must match the subscribers FTN type (depends on O-CSI, see Determining FTN type on page 2-142) for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except SMMO, SMMT, VBS and VGCS) none of the FTNs must match any of the subscribers basic service MSISDNs (interacts with all basic services except VBS and VGCS) the FTN format and NOA/NPI combination is checked against the subscribers FTN-type (interacts with O-CSI (see Determining FTN type on page 2-142): GSM-FTNs: length must have 4 - 15 digits, first digit must not be zero; NOA must be INTL, NPI must be E164 Custom-FTNs: length must have 1 - 15 digits; NOA must be UNKN, NPI must be UNKN TIF-FTNs: length must have 1 - 15 digits; NOA and NPI can take any values, however if NOA/NPI is INTL/E164 then additional checks apply to the FTN format: must be 4 - 15 digits and first digit must not be zero interactions with BSG-SSs and ODBs are given in Table 2-96 on page 2141. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-141 Copyright 19962005 Nortel

Table 2-96 CFNRy registration set interactions Validate Against Service BAIC State Reg Set Activated CFB and BAIC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB and BAOC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after CFU has been registered CFB and LCO are mutually exclusive if (1) the subscriber has GSM FTNs* and (2) any CFB FTN is not local CFB cannot be newly registered after ODB BAIC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after ODB BAOC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFB cannot be newly registered after ODB Prem Rate (Ent or Info) is provisioned if (1) the subscriber has GSM FTNs AND (2) the FTN is barred according to its lookup in system table GHRLODB. Interaction

BAOC

Reg Set Activated

CFU

Reg Set Activated

LCO

Provisioned

ODB BAIC

Provisioned

ODB BAOC

Provisioned

ODB Prem Rate categories

Provisioned

* FTN type determination is discussed in Determining FTN type on page 2-142

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-142 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Additional information Determining FTN type A subscriber may have GSM-FTNs, TIF-FTNs or Custom-FTNs. If the subscriber does not have O-CSI provisioned then they have GSM-FTNs. If the subscriber does have O-CSI provisioned, then their FTN type is determined by the FTN Checks field -- the field can be set to GSM, TIF or Custom. Therefore for instance, a TIF-FTNs subscriber has O-CSI provisioned, with FTN Checks set to TIF. Determining if an FTN is international w.r.t. HPLMN country Whether an FTN is international with respect to the HPLMN Country is important in some interactions with CFB. The following steps are taken in this determination: the subscribers primary MSISDN is determined (requires all basic services except VBS and VGCS) the primary MSISDN CC is mapped to a Pseudo Country Code (PCC) by doing a lookup in the TO/FROM fields of system table GHLRPCC the CFB FTN is also mapped to a PCC by doing a lookup in the TO/FROM fields of system table GHLRPCC if either number does not map to a PCC then it is a translations error, and the datafill is not valid the two PCCs are compared -- the FTN is international w.r.t. the HPLMN Country if they differ

DCF ID activation state determination The DCF ID does have an activation state, but it is not provisionable and is only determined on demand (e.g. when a MAP message to the HLR requests it). It is therefore, strictly speaking, not part of the subscriber profile. For information only, here are details regarding the DCF activation state: For non-TIF-FTN subscribers: DCF is deactivated if the subscriber has BAOC or BAIC. DCF is suppressed if the subscriber has BICRoam (act/ not sup), ODB BAOC, ODB BAOCRoam (act), ODB BAIC or ODB BICRoam (act) If the subscriber has CFU then DCF is always deactivated For GSM-FTN subscribers: DCF is suppressed if the subscriber has LCO (ESMR or non-ESMR), BOIC (act, number intl), BOICexHC (act, number intlexHC), ODB BOIC (number intl), ODB BOICexHC (number intlexHC), ODB PremRate (number barred) or ODB HPLMN Spec (act, number barred)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-143 Copyright 19962005 Nortel

CFU (Call Forward Unconditionally)


CFU is a basic service group based supplementary service (BSG-SS), allowing forward to numbers (FTNs) to be datafilled for call forwarding unconditionally against the BSGs the service supports. Datafill CFU data syntax is detailed in Table 2-97 on page 2-144. Each of the registration sets is optional.

The validation of CFU is complicated by its interaction with ESMR LCO Translations. If these translations are enabled then CFUs FTNs are passed through these translations to normalise the number (i.e convert it to international E164 format) and to determine whether the number is local. The syntax checks in apply to the post-translated number. The syntax check for pre-translated FTNs is that they contain 1 - 15 digits (with no restriction on the first digit). The local indication is required in CFUs interaction with LCO service. Note that if ESMR LCO translations are not enabled, then no translations occur and the FTN defaults to being not local. Meaning of ESMR LCO These are a particular type of translations used to normalise DNs and determine their localness. They are enabled on the HLR if key 1021 is datafilled in system table XLAENTRY and there is associated translations tables datafill. The term ESMR is used due to these translations being particularly used in the north American market.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-144 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Table 2-97 CFU data syntax Dataitem NCP SPCH Reg Set Activated NOA NPI FTN AUXSPCH Reg Set Activated NOA NPI FTN CDA Reg Set Activated NOA NPI FTN CDS Reg Set Activated NOA NPI FTN FAX Reg Set Activated NOA NPI FTN Syntax {NONF, NF, NFWN} Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Boolean {UNKN, INTL, NTL, NTWK, SUBS, ABBR} {UNKN, E164, X121, F69, E212, NATL, PRIV} 1 - 15 digits Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-145 Copyright 19962005 Nortel

CFU field descriptions are given in Table 2-98.


Table 2-98 CFU field descriptions (2 pages) Dataitem NCP Description Notify Calling Party option: No-notification (NONF), Notification (NF), Notification-with-number (NFWN) Activated NOA indicates whether the SPCH registration is activated the FTN Nature Of Address for the SPCH registration; options are Unknown (UNKN), International-number (INTL), Nationalsignificant-number (NTL), Network-specific-number (NTWK), Subscriber-number (SUBS) and Abbreviated-number (ABBR) the FTN Number Plan Indicator for the SPCH registration; options are Unknown (UNKN), ISDN/telephony-numberingplan (E164), Data-numbering-plan (X121), Telex-numberingplan (F69), Land-mobile-numbering-plan (E212), Nationalnumbering-plan (NATL) and Private-numbering-plan (PRIV) the Forward To Number for the SPCH registration also known as the call forward number AUXSPCH Reg Set Activated NOA indicates whether the AUXSPCH registration is activated the FTN Nature Of Address for the AUXSPCH registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the AUXSPCH registration; for options see SPCH Reg Set the Forward To Number for the AUXSPCH registration also known as the call forward number CDA Reg Set Activated NOA indicates whether the CDA registration is activated the FTN Nature Of Address for the CDA registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDA registration; for options see SPCH Reg Set the Forward To Number for the CDA registration also known as the call forward number

SPCH Reg Set

NPI

FTN

NPI

FTN

NPI

FTN

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-146 Chapter 2: Component descriptions Nortel Confidential Table 2-98 CFU field descriptions (2 pages) Dataitem CDS Reg Set Activated NOA Description

Copyright

19962005 Nortel

indicates whether the CDS registration is activated the FTN Nature Of Address for the CDS registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the CDS registration; for options see SPCH Reg Set the Forward To Number for the CDS registration also known as the call forward number

NPI

FTN

FAX Reg Set

Activated NOA

indicates whether the FAX registration is activated the FTN Nature Of Address for the FAX registration; for options see SPCH Reg Set the FTN Number Plan Indicator for the FAX registration; for options see SPCH Reg Set the Forward To Number for the FAX registration also known as the call forward number

NPI

FTN

Interactions CFU interacts with all basic services (except VBS and VGCS), BAOC, BOIC, BOICexHC, BAIC, LCO, ODB BAIC, ODB BAOC, ODB BOIC, ODB BOICexHC, ODB PremRate categories, ODB HPLMN Specific categories, O-CSI and system table GHLRODB. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except SMMO, SMMT, VBS and VGCS) none of the FTNs must match any of the subscribers basic service MSISDNs (interacts with all basic services except VBS and VGCS) the FTN format and NOA/NPI combination is checked against the subscribers FTN-type (interacts with O-CSI (see Determining FTN type on page 2-149): GSM-FTNs: length must have 4 - 15 digits, first digit must not be zero; NOA must be INTL, NPI must be E164 Custom-FTNs: length must have 1 - 15 digits; NOA must be UNKN, NPI must be UNKN

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-147 Copyright 19962005 Nortel

TIF-FTNs: length must have 1 - 15 digits; NOA and NPI can take any values, however if NOA/NPI is INTL/E164 then additional checks apply to the FTN format: must be 4 - 15 digits and first digit must not be zero interactions with BSG-SSs and ODBs are given in Table 2-99 below. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-99 CFU registration set interactions (2 pages) Validate Against Service BAIC State Reg Set Activated CFU and BAIC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFU and BAOC are mutually exclusive per-reg set, unless the subscriber has TIF FTNs*, in which case there is no interaction CFU and BOIC are mutually exclusive per-reg set if (1) the subscriber has GSM FTNs* and (2) the FTN is international with respect to HPLMN country** CFU and BOICexHC are mutually exclusive per-reg set if (1) the subscriber has GSM FTNs* and (2) the FTN is international with respect to HPLMN country** CFU and LCO are mutually exclusive if (1) the subscriber has GSM FTNs* and (2) any CFU FTN is not local CFU cannot be newly registered after ODB BAIC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFU cannot be newly registered after ODB BAOC has been provisioned, unless the subscriber has TIF FTNs*, in which case there is no interaction CFU cannot be newly registered after ODB BOIC has been provisioned if (1) the subscriber has GSM FTNs* and (2) the FTN is international with respect to HPLMN country** Interaction

BAOC

Reg Set Activated

BOIC

Reg Set Activated

BOICexHC

Reg Set Activated

LCO

Provisioned

ODB BAIC

Provisioned

ODB BAOC

Provisioned

ODB BOIC

Provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-148 Chapter 2: Component descriptions Nortel Confidential Table 2-99 CFU registration set interactions (2 pages) Validate Against Service ODB BOICexHC State Provisioned Interaction

Copyright

19962005 Nortel

CFU cannot be newly registered after ODB BOIC has been provisioned if (1) the subscriber has GSM FTNs* and (2) the FTN is international with respect to HPLMN country**

ODB Prem Rate categories

Provisioned

CFU cannot be newly registered after an ODB Premium Rate category has been provisioned if (1) the subscriber has GSM FTNs* and (2) the FTN is barred for that category# CFU cannot be newly registered after an ODB HPLMN Specific category has been provisioned if (1) the subscriber has GSM FTNs* and (2) the FTN is barred for that category#

ODB HPLMN Specific categories

Provisioned

* FTN type determination is discussed in Determining FTN type on page 2-149 ** determination if FTN is international with respect to HPLMN country is discussed in Determining if an FTN is international w.r.t. HPLMN country on page 2-149 # determining whether an FTN is barred for an ODB Premium Rate/ODB HPLMN Specific categories is done via a lookup in digilator system table GHLRODB

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-149 Copyright 19962005 Nortel

Additional information Determining FTN type A subscriber may have GSM-FTNs, TIF-FTNs or Custom-FTNs. If the subscriber does not have O-CSI provisioned then they have GSM-FTNs. If the subscriber does have O-CSI provisioned, then their FTN type is determined by the FTN Checks field -- the field can be set to GSM, TIF or Custom. Therefore for instance, a TIF-FTNs subscriber has O-CSI provisioned, with FTN Checks set to TIF. Determining if an FTN is international w.r.t. HPLMN country Whether an FTN is international with respect to the HPLMN Country is important in some interactions with CFB. The following steps are taken in this determination: the subscribers primary MSISDN is determined (requires all basic services except VBS and VGCS) the primary MSISDN CC is mapped to a Pseudo Country Code (PCC) by doing a lookup in the TO/FROM fields of system table GHLRPCC the CFB FTN is also mapped to a PCC by doing a lookup in the TO/FROM fields of system table GHLRPCC if either number does not map to a PCC then it is a translations error, and the datafill is not valid the two PCCs are compared -- the FTN is international w.r.t. the HPLMN Country if they differ

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-150 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CLIP (Calling Line ID Presentation)

CLIP datafill defines whether a Calling Line Identity Restriction (CLIR) of the calling party is overridden. CLIP is an IMSI-SS and applies to all BSGs except SMS. Datafill CLIP data syntax is detailed in Table 2-100.
Table 2-100 CLIP data syntax Dataitem Override Syntax Boolean Optional

CLIP field descriptions are given in Table 2-101.


Table 2-101 CLIP field descriptions Dataitem Override Description indicates whether CLIP override is in effect

Interactions CLIP interacts with ACRJ and office parameters GSM_CLIP_SUPPORTED and GSM_CLIP_OVR_SUPPORTED . for ACRJ to be provisioned, CLIP must be provisioned and have Override set to FALSE CLIP can only be provisioned if office parameter GSM_CLIP_SUPPORTED (table OFCSTD) is TRUE Override can only be set to TRUE if office parameter GSM_CLIP_OVR_SUPPORTED (table OFCSTD) is TRUE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-151 Copyright 19962005 Nortel

CLIR (Calling Line ID Restriction)


CLIR datafill defines the presentation mode to be used for CLI restriction. CLIR is an IMSI-SS and applies to all BSGs except SMS. Datafill CLIR data syntax is detailed in Table 2-102.
Table 2-102 CLIR data syntax Dataitem Presentation Mode Syntax {P, TRES, TNRES} Optional

CLIR field descriptions are given in Table 2-103.


Table 2-103 CLIR field descriptions Dataitem Presentation Mode Description presentation mode option: permanent-CLI-presentation-restricted (P), temporary-CLI-presentation-restricted (TRES), temporary-CLI-presentationnot-restricted (TNRES)

Interactions CLIR interacts with office parameter GSM_CLIR_SUPPORTED. CLIR can only be provisioned if office parameter GSM_CLIR_SUPPORTED (table OFCSTD) is TRUE

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-152 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CNAM (Calling Name Delivery)

Provisioning CNAM enables Calling Name Delivery functionality for the subscriber (CNAM allows the calling partys name to be displayed on the terminators MS). CNAM is a Nortel proprietary IMSI-SS and applies to all BSGs except SMS and VGS. Datafill CNAM has no dataitems, it is simply provisioned or deprovisioned. Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-153 Copyright 19962005 Nortel

COLP (Connected Line ID Presentation)


COLP datafill specifies whether service COLR on the connected party is overridden. COLP is an IMSI-SS and applies to all BSGs except SMS. Datafill COLP data syntax is detailed in Table 2-104.
Table 2-104 COLP data syntax Dataitem Override Syntax Boolean Optional

COLP field descriptions are given in Table 2-105.


Table 2-105 COLP field descriptions Dataitem Override Description indicates whether COLP override is in effect

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-154 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

COLR (Connected Line ID Restriction)

Provisioning COLR enables explicit connected line ID restriction functionality for the subscriber. COLR is an IMSI-SS and applies to all BSGs except SMS. Datafill COLR has no dataitems, it is simply provisioned or deprovisioned. Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-155 Copyright 19962005 Nortel

COS (Class of Service)

COS is a basic service group based supplementary service (BSG-SS), allowing class of service information to be datafilled against each BSG that is supported by the service. COS is a Nortel proprietary service. Datafill COS data syntax is detailed in Table 2-106. Each of the registration sets is optional.
Table 2-106 COS data syntax Dataitem SPCH Reg Set Activated Customer Group NCOS AUXSPCH Reg Set Activated Customer Group NCOS CDA Reg Set Activated Customer Group NCOS CDS Reg Set Activated Customer Group NCOS FAX Reg Set Activated Customer Group NCOS Syntax Boolean number: 0 - 4095 number: 0 - 255 Boolean number: 0 - 4095 number: 0 - 255 Boolean number: 0 - 4095 number: 0 - 255 Boolean number: 0 - 4095 number: 0 - 255 Boolean number: 0 - 4095 number: 0 - 255 Optional Optional Optional Optional Optional Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-156 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

COS field descriptions are given in Table 2-107.


Table 2-107 COS field descriptions Dataitem SPCH Reg Set Activated Customer Group Description indicates whether the SPCH registration is activated the customer group for the SPCH registration, defined in system table GSMCUST or GSMNCOS the network class of service for the SPCH registration, defined in system table GSMNCOS indicates whether the AUXSPCH registration is activated the customer group for the AUXSPCH registration, defined in system table GSMCUST or GSMNCOS the network class of service for the AUXSPCH registration, defined in system table GSMNCOS indicates whether the CDA registration is activated the customer group for the CDA registration, defined in system table GSMCUST or GSMNCOS the network class of service for the CDA registration, defined in system table GSMNCOS indicates whether the CDS registration is activated the customer group for the CDS registration, defined in system table GSMCUST or GSMNCOS the network class of service for the CDS registration, defined in system table GSMNCOS indicates whether the FAX registration is activated the customer group for the FAX registration, defined in system table GSMCUST or GSMNCOS the network class of service for the FAX registration, defined in system table GSMNCOS

NCOS

AUXSPCH Reg Set

Activated Customer Group

NCOS

CDA Reg Set

Activated Customer Group

NCOS

CDS Reg Set

Activated Customer Group

NCOS

FAX Reg Set

Activated Customer Group

NCOS

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-157 Copyright 19962005 Nortel

Interactions COS interacts with all basic services (except SMMO, SMMT, VBS and VGCS) and system tables GSMCUST and GSMNCOS. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except SMMO, SMMT, VBS and VGCS) for each registration set, if NCOS is datafilled, then Customer Group and NCOS combined must be an entry from column GSM_NCOS_KEY of system table GSMNCOS for each registration set, if NCOS is not datafilled, then Customer Group must be an entry from the GSMCUST_GRP_KEY column of system table
GSMCUST

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-158 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CUG (Closed User Groups)


CUG is a basic service group based supplementary service (BSG-SS), allowing closed user groups information to be datafilled against the BSGs that are supported by the service. CUG is unusual in that it has two separate groups of datafill. One group is mandatory, called CUG Subscription, and the other is optional, called CUG Feature. CUG Subscription is detailed on page 2-159. CUG Feature is detailed on page 2-161.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-159 Copyright 19962005 Nortel

CUG Subscription (Closed User Groups Subscription)


CUG is a basic service group based supplementary service (BSG-SS), allowing closed user groups information to be datafilled against the BSGs that are supported by the service. CUG Subscription is mandatory CUG data, whereas CUG Feature (on page 2-161) is optional CUG data. Datafill CUG Subscription data syntax is detailed in Table 2-108. The following intra-service validations apply. each Interlocks must be unique per subscriber each CUG Index must be unique per subscriber

Table 2-108 CUG Subscription data syntax Dataitem Subscription Dataset vector (1 - 10) - Network ID - Interlock - CUG Index - IntraCUG Restrictions - SPCH Reg - AUXSPCH Reg - FAX Reg - CDA Reg - CDS Reg - All BSG Reg Syntax composed of the following ten dataitems number: 0 - 9999 number: 0 - 65535 number: 0 - 32767 {ICB,OCB} Boolean Boolean Boolean Boolean Boolean Boolean Optional Optional 9 are Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-160 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

CUG Subscription field descriptions are given in Table 2-109.


Table 2-109 CUG Subscription field descriptions Dataitem Subscription Dataset - Network ID - Interlock - CUG Index - IntraCUG Restrictions Description a CUG subscription dataset, composed of the dataitems below network identity interlock code CUG index intra-CUG restrictions; options are incoming-call-barred (ICB) and outgoing-call-barred (OCB) whether this subscription applies to SPCH whether this subscription applies to AUXSPCH whether this subscription applies to FAX whether this subscription applies to CDA whether this subscription applies to CDS whether this subscription applies to all BSGs

- SPCH Reg - AUXSPCH Reg - FAX Reg - CDA Reg - CDS Reg - All BSG Reg

Interactions CUG Subscription interacts with all basic services (except SMMO, SMMT, VBS and VGCS) and CUG Feature CUG Subscription must be provisioned for CUG Feature to be provisioned for each <bsg> Reg set to TRUE, the corresponding BSG must be provisioned (interacts with all basic services except SMMO, SMMT, VBS and VGCS) there are complex interactions with CUG Feature -- see the CUG Feature interactions in section on page 2-163

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-161 Copyright 19962005 Nortel

CUG Feature (Closed User Groups Feature)


CUG is a basic service group based supplementary service (BSG-SS), allowing closed user groups information to be datafilled against each BSG that is supported by the service. CUG Feature is optional CUG data, whereas CUG Subscription (on page 2159) is mandatory CUG data. Datafill

CUG Feature data syntax is detailed in Table 2-110. Each of the registration sets is optional.
Table 2-110 CUG Feature data syntax Dataitem SPCH Reg Set Activated ICA PrefCUG Index AUXSPCH Reg Set Activated ICA PrefCUG Index FAX Reg Set Activated ICA PrefCUG Index CDA Reg Set Activated ICA PrefCUG Index CDS Reg Set Activated ICA PrefCUG Index All BSG Reg Set Activated ICA PrefCUG Index Syntax Boolean {OA, IA, ALL} number: 0 - 32767 Boolean {OA, IA, ALL} number: 0 - 32767 Boolean {OA, IA, ALL} number: 0 - 32767 Boolean {OA, IA, ALL} number: 0 - 32767 Boolean {OA, IA, ALL} number: 0 - 32767 Boolean {OA, IA, ALL} number: 0 - 32767 Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-162 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

CUG Feature field descriptions are given in Table 2-111.


Table 2-111 CUG Feature field descriptions Dataitem SPCH Reg Set Activated ICA Description indicates whether the registration is activated inter-CUG accessibility; options are outgoing-access, incoming-access or all preferred CUG index indicates whether the registration is activated inter-CUG accessibility; options are outgoing-access, incoming-access or all preferred CUG index indicates whether the registration is activated inter-CUG accessibility; options are outgoing-access, incoming-access or all preferred CUG index indicates whether the registration is activated inter-CUG accessibility; options are outgoing-access, incoming-access or all preferred CUG index indicates whether the registration is activated inter-CUG accessibility; options are outgoing-access, incoming-access or all preferred CUG index indicates whether the registration is activated inter-CUG accessibility; options are outgoing-access, incoming-access or all preferred CUG index

PrefCUG Index AUXSPCH Reg Set Activated ICA

PrefCUG Index FAX Reg Set Activated ICA

PrefCUG Index CDA Reg Set Activated ICA

PrefCUG Index CDS Reg Set Activated ICA

PrefCUG Index All BSG Reg Set Activated ICA

PrefCUG Index

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-163 Copyright 19962005 Nortel

Interactions CUG Feature interacts with all basic services (except SMMO, SMMT, VBS and VGCS) and CUG Subscription. CUG Subscription must be provisioned for CUG Feature to be provisioned. for each Reg Set, if a PrefCUG Index is datafilled: the PrefCUG Index must exist at least once in a CUG Subscription as a CUG Index any CUG Subscription dataset whose CUG Index matches the PrefCUG Index must have its <bsg> Reg dataitem set to TRUE (where <bsg> corresponds to the particular CUG Feature Reg Set) and its IntraCUG Restrictions dataitem must not be set to OCB for each Reg Set provisioned except All BSG: the BSG must be provisioned (interacts with all basic services except SMMO, SMMT, VBS and VGCS) at least one <bsg> Reg dataitem of any CUG Subscription dataset must be set to TRUE (where <bsg> corresponds to the particular CUG Feature Reg Set). Note that if any CUG Subscription dataset has its All BSG Reg dataitem set to TRUE then this check will always pass

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-164 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CW (Call Waiting)

CW is a basic service group based supplementary service (BSG-SS), allowing call waiting to be given to the BSGs that are supported by the service. Datafill CW data syntax is detailed in Table 2-112. Each of the registration sets is optional.
Table 2-112 CW data syntax Dataitem SPCH Reg Set AUXSPCH Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Syntax Boolean Boolean Boolean Boolean Boolean Optional

CW field descriptions are given in Table 2-113.


Table 2-113 CW field descriptions Dataitem SPCH Reg Set AUXSPCH Reg Set CDA Reg Set CDS Reg Set FAX Reg Set Activated Activated Activated Activated Activated Description indicates whether the SPCH registration is activated indicates whether the AUXSPCH registration is activated indicates whether the CDA registration is activated indicates whether the CDS registration is activated indicates whether the FAX registration is activated

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-165 Copyright 19962005 Nortel

Interactions CW interacts with all basic services (except VBS and VGCS), BAIC and ODB BAIC. for each registration set provisioned, the BSG must be provisioned (interacts with all basic services except VBS and VGCS) interactions with BSG-SSs and ODBs are given in Table 2-114. Note that these interactions apply to each BSG registration set (and where the interaction is with a BSG-SS, the interaction is with the corresponding BSG in the interacting service). These interactions only apply to activated BSG registrations

Table 2-114 CW registration set interactions Validate Against Service BAIC State Reg Set Activated BAIC can be registered after CW but CW cannot be registered after BAIC; CW and BAIC can be registered together in the same transaction ODB BAIC can be provisioned after CW but CW cannot be registered after ODB BAIC; CW can be registered plus ODB BAIC provisioned in the same transaction Interaction

ODB BAIC

Provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-166 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

ECT (Explicit Call Transfer)


Provisioning ECT enables explicit call transfer functionality for the subscriber. ECT is an IMSI-SS and applies to SPCH and AUXPSCH BSGs only. Datafill ECT has no dataitems, it is simply provisioned or deprovisioned. Interactions ECT interacts with HOLD. HOLD must be provisioned for ECT to be provisioned

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-167 Copyright 19962005 Nortel

EMLPP (Enhanced Multi Level Precedence & Pre-emption)

EMLPP datafill defines priorities for the subscriber, and can be used to set a priority for Wireless Priority Service (WPS). EMLPP is an IMSI-SS and applies to all BSGs except SMS. Datafill EMLPP data syntax is detailed in Table 2-115.
Table 2-115 EMLPP data syntax Dataitem Maximum Priority Default Priority Syntax {A, B, 1, 2, 3, 4} {A, B, 1, 2, 3, 4} Optional

EMLPP field descriptions are given in Table 2-116.


Table 2-116 EMLPP field descriptions Dataitem Maximum Priority Default Priority Description the maximum priority for EMLPP or WPS the default priority for EMLPP or WPS, depending on office parameter CPS_MODE

Interactions EMLPP interacts with office parameter CPS_MODE (table GHLRPARM). if office parameter CPS_MODE is EMLPP then the Default Priority must not be greater than the Maximum Priority (A is highest, 4 is lowest) if office parameter CPS_MODE is WPS then the Default Priority and the Maximum Priority must match, and their range is restricted to {B, 1, 2, 3} if office parameter CPS_MODE is HYBRID then the Maximum Priority range is restricted to {B, 1, 2, 3, 4}. Note that the Maximum Priority represents the WPS setting, while the Default Priority represents the EMLPP setting

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-168 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

EXT (Extension Services)


EXT is a basic service group based supplementary service (BSG-SS), allowing MSISDN groups and timers to be datafilled for simultaneous and sequential altering (also known as flexible altering and mobile hunting respectively) for the BSGs supported by the service. EXT is a Nortel proprietary service. Datafill

EXT data syntax is detailed in Table 2-117 on page 2-169. Each registration set data consists of one to three groups and also an overall registration set. Each group consists of one to three MSISDNs and a timer. For each registration set, only certain combinations of MSISDNs, Timers and Groups are valid; these are given in Table 2-118 on page 2-171. Note that combinations contain a maximum of five MSISDNs. The validation of EXT is complicated by its interaction with ESMR LCO Translations. If these translations are enabled then EXTs MSISDNs are passed through these translations to normalise the number (i.e convert it to international E164 format) and to determine whether the number is local. The syntax checks in apply to the post-translated number. The syntax check for pre-translated MSISDNs is that they contain 1 - 15 digits (with no restriction on the first digit). The local indication is required in EXTs interaction with LCO service. Note that if ESMR LCO translations are not enabled, then no translations occur and the MSISDN defaults to being not local. Meaning of ESMR LCO These are a particular type of translations used to normalise DNs and determine their localness. They are enabled on the HLR if key 1021 is datafilled in system table XLAENTRY and there is associated translations tables datafill. The term ESMR is used due to these translations being particularly used in the north American market.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-169 Copyright 19962005 Nortel

.
Table 2-117 EXT data syntax (2 pages) Dataitem SPCH Reg Set Activated MSISDN 1.1 MSISDN 1.2 MSISDN 1.3 Timer 1 Group 1 MSISDN 2.1 MSISDN 2.2 MSISDN 2.3 Timer 2 Group 2 MSISDN 3.1 MSISDN 3.2 MSISDN 3.3 Timer 3 Group 3 Overall Group Syntax Boolean 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero number: 5 - 90 (multiple of 5) {SINGLE, MULTIPLE} 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero number: 5 - 90 (multiple of 5) {SINGLE, MULTIPLE} 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero number: 5 - 90 (multiple of 5) {SINGLE, MULTIPLE} {SINGLE, MULTIPLE} Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-170 Chapter 2: Component descriptions Nortel Confidential Table 2-117 EXT data syntax (2 pages) Dataitem AUXSPCH Reg Set Activated MSISDN 1.1 MSISDN 1.2 MSISDN 1.3 Timer 1 Group 1 MSISDN 2.1 MSISDN 2.2 MSISDN 2.3 Timer 2 Group 2 MSISDN 3.1 MSISDN 3.2 MSISDN 3.3 Timer 3 Group 3 Overall Group Syntax Boolean

Copyright

19962005 Nortel

Optional

4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero number: 5 - 90 (multiple of 5) {SINGLE, MULTIPLE} 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero number: 5 - 90 (multiple of 5) {SINGLE, MULTIPLE} 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero 4 - 15 digits, cannot start with zero number: 5 - 90 (multiple of 5) {SINGLE, MULTIPLE} {SINGLE, MULTIPLE} Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-171 Copyright 19962005 Nortel

Table 2-118 Valid MSISDN/Timer/Group Combinations Combination Type Simultaneous Sequence MMTG MMMTG Sequential MTMTG MTMTMTG Mix using 5 MSISDNs MMMTGMMTGG MMTGMMMTGG MMMTGMTMTG MTMTMMMTGG MTMMMTGMTG MMTGMMTGMTG MMTGMTMMTGG MTMMTGMMTGG Mix using 4 MSISDNs MMTGMTMTG MTMMTGMTG MTMTMMTGG MMMTGMTG MTMMMTGG MMTGMMTGG Mix using 3 MSISDNs MMTGMTG MTMMTGG Other MT

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-172 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

EXT field descriptions are given in Table 2-119.


Table 2-119 EXT field descriptions (2 pages) Dataitem SPCH Reg Set Activated MSISDN 1.1 MSISDN 1.2 MSISDN 1.3 Timer 1 Group 1 Description indicates whether the SPCH registration is activated first MSISDN of first group for SPCH registration second MSISDN of first group for SPCH registration third MSISDN of first group for SPCH registration timer for first group for SPCH registration first group type for SPCH registration; options are multiple or single user first MSISDN of second group for SPCH registration second MSISDN of second group for SPCH registration third MSISDN of second group for SPCH registration timer for second group for SPCH registration second group type for SPCH registration; options are multiple or single user first MSISDN of third group for SPCH registration second MSISDN of third group for SPCH registration third MSISDN of third group for SPCH registration timer for third group for SPCH registration third group type for SPCH registration; options are multiple or single user overall group type for SPCH registration; options are multiple or single user (applies to the three other groups)

MSISDN 2.1 MSISDN 2.2 MSISDN 2.3 Timer 2 Group 2

MSISDN 3.1 MSISDN 3.2 MSISDN 3.3 Timer 3 Group 3

Overall Group

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-119 EXT field descriptions (2 pages) Dataitem AUXSPCH Reg Set Activated MSISDN 1.1 MSISDN 1.2 MSISDN 1.3 Timer 1 Group 1 Description

Chapter 2: Component descriptions 2-173 Copyright 19962005 Nortel

indicates whether the AUXSPCH registration is activated first MSISDN of first group for AUXSPCH registration second MSISDN of first group for AUXSPCH registration third MSISDN of first group for AUXSPCH registration timer for first group for AUXSPCH registration first group type for AUXSPCH registration; options are multiple or single user first MSISDN of second group for AUXSPCH registration second MSISDN of second group for AUXSPCH registration third MSISDN of second group for AUXSPCH registration timer for second group for AUXSPCH registration second group type for AUXSPCH registration; options are multiple or single user first MSISDN of third group for AUXSPCH registration second MSISDN of third group for AUXSPCH registration third MSISDN of third group for AUXSPCH registration timer for third group for AUXSPCH registration third group type for AUXSPCH registration; options are multiple or single user overall group type for AUXSPCH registration; options are multiple or single user (applies to the three other groups)

MSISDN 2.1 MSISDN 2.2 MSISDN 2.3 Timer 2 Group 2

MSISDN 3.1 MSISDN 3.2 MSISDN 3.3 Timer 3 Group 3

Overall Group

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-174 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Service Interactions EXT interacts with TPHNY, AUXTPHNY and LCO. for each registration set provisioned, the BSG must be provisioned (interacts with TPHNY and AUXTPHNY) the interactions with LCO is given in Table 2-120. Note that this interactions apply to both BSG registration sets. These interactions only apply to activated BSG registrations

Table 2-120 EXT registration set interactions Validate Against Service LCO State Provisioned LCO and EXT registration sets can only co-exist if each MSISDN in the registration set is local Interaction

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-175 Copyright 19962005 Nortel

FM (Follow Me)

FM datafill allows FM class of registrations to be specified. FM in an IMSISS and applies to all BSGs except VGS. Note that this service is also known as Functional Addressing (FA). Datafill FM data syntax is detailed in Table 2-121. The following intra-service interactions apply.
Table 2-121 FM data syntax Dataitem COR A COR B COR C COR D Supervisor COR A Supervisor COR B Supervisor COR C Supervisor COR D Syntax Boolean Boolean Boolean Boolean Boolean Boolean Boolean Boolean Optional

at least one COR value (COR x or Supervisor COR x) must be set to TRUE

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-176 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

FM field descriptions are given in Table 2-122.


Table 2-122 FM field descriptions Dataitem COR A COR B COR C COR D Supervisor COR A Supervisor COR B Supervisor COR C Supervisor COR D Description indicates whether FM Class of Registration A is provisioned indicates whether FM Class of Registration B is provisioned indicates whether FM Class of Registration C is provisioned indicates whether FM Class of Registration D is provisioned indicates whether FM Supervisor Class of Registration A is provisioned indicates whether FM Supervisor Class of Registration B is provisioned indicates whether FM Supervisor Class of Registration C is provisioned indicates whether FM Supervisor Class of Registration D is provisioned

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-177 Copyright 19962005 Nortel

HOLD (Call Hold)

Provisioning HOLD enables call hold functionality for the subscriber. HOLD is an IMSI-SS and applies to SPCH and AUXSPCH BSGs only. Datafill HOLD has no dataitems, it is simply provisioned or deprovisioned. Interactions HOLD interacts with MPTY and ECT. HOLD must be provisioned for MPTY to be provisioned HOLD must be provisioned for ECT to be provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-178 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

HOTBILL (Hot Billing)


Provisioning HOTBILL enables hot billing functionality for the subscriber. HOTBILL is an Nortel proprietary IMSI-SS. Datafill HOTBILL has no dataitems, it is simply provisioned or deprovisioned. Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-179 Copyright 19962005 Nortel

LCO (Local Calls Only)


Provisioning LCO enables local calls only functionality for the subscriber. LCO is an Nortel proprietary IMSI-SS. Datafill LCO has no dataitems, it is simply provisioned or deprovisioned. Interactions LCO interacts with all call forwards and EXT.
Table 2-123 LCO Interactions Validate Against Service CFU State Reg Set Activated LCO and CFU are mutually exclusive unless (1) subscriber does not have GSM FTNs* OR (2) subscriber has GSM FTNs but FTN is local** LCO and CFB are mutually exclusive unless (1) subscriber does not have GSM FTNs* OR (2) subscriber has GSM FTNs but FTN is local** LCO and CFNRc are mutually exclusive unless (1) subscriber does not have GSM FTNs* OR (2) subscriber has GSM FTNs but FTN is local** LCO and CFNRy are mutually exclusive unless (1) subscriber does not have GSM FTNs* OR (2) subscriber has GSM FTNs but FTN is local** LCO and EXT are mutually exclusive unless all EXT MSISDNs are local** Interaction

interactions with BSG-SSs are given in Table 2-123. This interactions apply to every registration set of each BSG-SS listed

CFB

Reg Set Activated

CFNRc

Reg Set Activated

CFNRy

Reg Set Activated

EXT

Reg Set Activated

* for determination of subscriber FTN type see Determining FTN type on page 2-129 ** for more information on CF FTNs/EXT MSISDNs localness see Datafill on page 2-123 / on page 2-168 respectively. Note that if ESMR LCO Translations are not enabled then all FTNs/MSISDNs default to not local, meaning that in this scenario LCO is always mutually exclusive with all call forwards and EXT.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-180 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

MCT (Malicious Call Trace)


Provisioning MCT enables malicious call trace functionality for the subscriber. MCT is an Nortel proprietary IMSI-SS and applies to all BSGs except SMS and VGS. Datafill MCT has no dataitems, it is simply provisioned or deprovisioned. Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-181 Copyright 19962005 Nortel

MPTY (Multiparty)

MPTY datafill defines the maximum number of ports allowed on a multiparty call. MPTY is an IMSI-SS and applies to SPCH and AUXSPCH BSGs only. Datafill MPTY data syntax is detailed in Table 2-124.
Table 2-124 MPTY data syntax Dataitem Option Syntax {M3PORT, M6PORT] Optional

MPTY field descriptions are given in Table 2-125.


Table 2-125 MPTY field descriptions Dataitem Option Description multiparty option: 3-ports or 6-port

Interactions MPTY interacts with HOLD. HOLD must be provisioned for MPTY to be provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-182 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

UUS1 (User to User Signalling stage 1)

Provisioning UUS1 enables user to user signalling stage 1 functionality for the subscriber. UUS1 is an IMSI-SS and applies to all BSGs except SMS and VGS. Datafill UUS1 has no dataitems, it is simply provisioned or deprovisioned. Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-183 Copyright 19962005 Nortel

WPS (Wireless Priority Service)


On the Nortel HLR, service EMLPP is used to provision/datafill WPS (see EMLPP (Enhanced Multi Level Precedence & Pre-emption) on page 2167).

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-184 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

ODBs (Operator Determined Barrings)

ODBs define barrings put in place by the operator. They apply to all basic service groups except VGS (ODB BAOC is an exception in that it applies to VGS too). There are four categories of ODB: incoming, outgoing, ECT and miscellaneous. Incoming ODBs are: ODB BAIC (Barring of All Incoming Calls) ODB BICRoam (Barring of Incoming Calls when Roaming outside HPLMN country)

Outgoing ODBs are: ODB BAOC (Barring of All Outgoing Calls) ODB BAOCRoam (Barring of (All) Outgoing Calls when Roaming outside HPLMN country) ODB BOIC (Barring of Outgoing International Calls) ODB BOICexHC (Barring of Outgoing International Calls except those to HPLMN Country

ECT ODBs are: ODB BAECT (Barring of All Explicit Call Transfer) ODB BCHDECT (Barring of Chargeable Explicit Call Transfer, i.e. when at least one of the calls is charged to the served subscriber) ODB BINTECT (Barring of International Explicit Call Transfer, i.e. when at least one of the calls is charge to the served subscriber at international rates) ODB BDBCECT (Barring of Doubly Chargeable Explicit Call Transfer, i.e. when both of the calls are charged to the served subscriber)

Miscellaneous ODBs are: ODB HPLMN Specific 1 ODB HPLMN Specific 2 ODB HPLMN Specific 3 ODB HPLMN Specific 4 ODB Premium Rate Entertainment ODB Premium Rate Information ODB CCFMGT (Barring of Conditional Call Forwarding Subscriber Management)
01.02 March 2005

411-2831-332

Preliminary

Nortel Confidential

Chapter 2: Component descriptions 2-185 Copyright 19962005 Nortel

Datafill

ODB CISSMGT (Barring of Call Independent Supplementary Services Management)

Each ODB is identical is that they have no dataitems, they are simply provisioned or deprovisioned. Interactions The ECT ODBs interact with each other. ODB BAECT and ODB BCHDECT are mutually exclusive ODB BCHDECT and ODB BINTEXT are mutually exclusive ODB BAECT and ODB BINTECT are mutually exclusive

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-186 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CAMEL services introduction


CAMEL (Customised Applications for Mobile Enhanced network Logic) services are intelligent network (IN) services for the GSM network. The HLR supports several individual CAMEL subscription information (CSI) services as given in Table 2-126.
Table 2-126 CAMEL Services Short Name D-CSI GPRS-CSI M-CSI O-CSI SMS-CSI SS-CSI T-CSI USSD-CSI Expanded Name Dialled CSI GPRS CSI Mobility Management CSI Originating CSI Short Message Service CSI Supplementary Service CSI Terminating CSI Unstructured Supplementary Service Data CSI See Section on page 2-187 on page 2-189 on page 2-192 on page 2-193 on page 2-201 on page 2-203 on page 2-204 on page 2-210

CAMEL is a network feature that enables the HPLMN operator to offer some of its Operator Specific Services (OSSs) that are not standardized by GSM specifications, to some or all of its subscribers when roaming to a different PLMN. The feature can also be used to offer these services while the subscriber is in their HPLMN. Normally, when a subscriber roams to a different PLMN, all OSSs are lost, since the services are not GSM defined and therefore not supported by the VPLMN. However, CAMEL is GSM defined, which means that OSSs provided through CAMEL are available when the subscriber roams to a VPLMN that supports CAMEL.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-187 Copyright 19962005 Nortel

D-CSI (Dialled CSI)


D-CSI datafill defines criteria for the Analysed Information detection point (DP) in the originating Basic Call State Machine (BCSM) for mobile originating and forwarded calls. Datafill D-CSI data syntax is detailed in Table 2-127. The Criteria Names are a vector; at least one Criteria Name must be datafilled (see Chapter 1, Data vectors, on page 1-36 for more information on vectors). The following intra-service interactions apply.
Table 2-127 D-CSI data syntax Dataitem Active Phase UNSPVMSC UNSPGMSC Criteria Names vector (1 - 10) Syntax Boolean {CAP3} {RELEASE, CONTINUE, CONT_HPLMN} {RELEASE, CONTINUE} 1 - 20 characters 9 are Optional Optional

duplicate Criteria Names are not permitted

D-CSI field descriptions are given in Table 2-128.


Table 2-128 D-CSI field descriptions Dataitem Active Phase Description indicates whether the CSI is active the CAMEL Phase which is required at the gsmSCF for the service -- this has to be datafilled as Phase 3 (CAP3) also know as the CAMEL Capability Handler (CCH) UNSPVMSC behaviour if the VLR/MSC does not support Phase 3: release-call, continuecall or continue-call-if-in-HPLMN behaviour if the GMSC does not support Phase 3: release-call or continuecall a criteria name, defined in system table GHLRDSCR

UNSPGMSC

Criteria Name(s)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-188 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions D-CSI interacts with system table GHLRDCSR. each Criteria Name must be an entry from column DPCRNAME of system table GHLRDCSR

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-189 Copyright 19962005 Nortel

GPRS-CSI (General Packet Radio Service CSI)


GPRS-CSI datafill defines trigger information that is required to invoke a CAMEL service for GPRS Sessions and PDP Contexts. Datafill GPRS-CSI data syntax is detailed in Table 2-129. Each of the Trigger DP sets is optional, although at least one must be provisioned. The following intra-service interactions apply. at least one Trigger DP set must be provisioned

Table 2-129 GPRS-CSI data syntax (2 pages) Dataitem Active Phase UNSPSGSN Trigger DP1 Set SCF Name Service Key SCF Unavailable Treatment Trigger DP2 Set SCF Name Service Key SCF Unavailable Treatment Trigger DP11 Set SCF Name Service Key SCF Unavailable Treatment Trigger DP12 Set SCF Name Service Key SCF Unavailable Treatment Syntax Boolean {CAP3} {RELEASE, CONTINUE, CONT_HPLMN} 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE} Optional

1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-190 Chapter 2: Component descriptions Nortel Confidential Table 2-129 GPRS-CSI data syntax (2 pages) Dataitem Trigger DP14 Set SCF Name Service Key SCF Unavailable Treatment Syntax 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

Copyright

19962005 Nortel

Optional

GPRS-CSI field descriptions are given in Table 2-130.


Table 2-130 GPRS-CSI field descriptions (2 pages) Dataitem Active Phase Description indicates whether the CSI is active the CAMEL Phase which is required at the gsmSCF for the service -- this has to be datafilled as Phase 3 (CAP3) also know as the CAMEL Capability Handler (CCH) UNSPSGSN behaviour if the SGSN does not support Phase 3: releasecall, continue-call or continue-call-if-in-HPLMN SCF Name Service Key SCF Unavailable Treatment Trigger DP2 Set SCF Name Service Key SCF Unavailable Treatment Trigger DP11 Set SCF Name Service Key SCF Unavailable Treatment the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the GPRS session/PDP context the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the GPRS session/PDP context the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the GPRS session/PDP context

Trigger DP1 Set

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-130 GPRS-CSI field descriptions (2 pages) Dataitem Trigger DP12 Set SCF Name Service Key SCF Unavailable Treatment Trigger DP14 Set SCF Name Service Key SCF Unavailable Treatment Description

Chapter 2: Component descriptions 2-191 Copyright 19962005 Nortel

the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the GPRS session/PDP context the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the GPRS session/PDP context

Interactions GPRS-CSI interacts with GPRS and system table GHLRSCF. GPRS must be provisioned for GPRS-CSI to be provisioned each SCF Name must be an entry from the SCF_NAME column of system table GHLRSCF

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-192 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

M-CSI (Mobility Management CSI)

M-CSI datafill defines which mobility events trigger a message to be sent to the GSM Service control Function (gsmSCF). Datafill M-CSI data syntax is detailed in Table 2-131.
Table 2-131 M-CSI data syntax Dataitem Active Mobility Trigger Name Suppress M-CSI Syntax Boolean 1 - 20 characters {HC, HPLMN, INTL} Optional Optional

M-CSI field descriptions are given in Table 2-132.


Table 2-132 M-CSI field descriptions Dataitem Active Mobility Trigger Name Suppress M-CSI Description indicates whether the CSI is active the mobility trigger name, defined in system table GHMTRIG indicates when to suppress M-CSI: when located in HPLMN country, in HPLMN, or when international

Interactions M-CSI interacts with system table GHMTRIG. the Mobility Trigger Name must be an entry from the MTNAME field of system table GHMTRIG

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-193 Copyright 19962005 Nortel

O-CSI (Originating CSI)


O-CSI datafill defines subscriber originating trigger information which is used by GSM nodes to determine when to contact the GSM Service Control Function (gsmSCF), which in turn decides how a call proceeds. O-CSI datafill also encompasses TIF-CSI provisioning. Datafill

O-CSI data syntax is detailed in Table 2-133 on page 2-194. Each of the Trigger DP sets is optional, although at least one must be provisioned. TIFCSI is provisioned via the FTN Checks dataitem. The following intra-service interactions apply. at least one Trigger DP set must be provisioned if FTN Checks is CUSTOM then Active must be TRUE, UNSPVMSC must be RELEASE, UNSPGMSC must be RELEASE and QSCFWIHP must be TRUE if FTN Checks is TIF then Active must be TRUE, QSCFWIHP must be TRUE and at least one of these sets must be provisioned: TDP2 Phase2, TDP2 Phase3, TDP4 Phase3 for both the TDP2 Phase2 and TDP2 Phase3 sets: if DNC Matchtype is not datafilled, then no DNC DNs should be datafilled, and no DNC Lengths should be datafilled either for both the TDP2 Phase2 and TDP2 Phase3 sets: if DNC Matchtype is datafilled, then at least one DNC DN or one DNC Length must be datafilled (e.g. it is valid to have just one DNC DN, or just one DNC Length) DNC DNs (i.e. NOA + NPI + DN combined) must be unique persubscriber (includes both vectors) DNC Lengths must be unique per-subscriber (includes both vectors) BS Codes Criteria must be unique per-subscriber (include both vectors) for BS Codes Criteria, if a BSG is datafilled then no BSs belonging to that BSG may also be datafilled Cause Values Criteria must be unique per-subscriber

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-194 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Table 2-133 O-CSI data syntax (3 pages) Dataitem Active FTN Checks UNSPVMSC UNSPGMSC QSCFWIHP Trigger DP2 Phase1 Set SCF Name Service Key SCF Unavailable Treatment Send CCH Syntax Boolean {GSM, CUSTOM, TIF} {RELEASE, CONTINUE, CONT_HPLMN} {RELEASE, CONTINUE} Boolean 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE} Optional

Boolean

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-133 O-CSI data syntax (3 pages) Dataitem Trigger DP2 Phase2 Set SCF Name Service Key SCF Unavailable Treatment DNC Matchtype DNC DNs vector (0 - 10) - NOA - NPI - DN DNC Lengths vector (0 - 3) BS Codes Criteria vector (0 - 5) Syntax 1 - 20 characters

Chapter 2: Component descriptions 2-195 Copyright 19962005 Nortel

Optional

number: 1 - 2147483647 {RELEASE, CONTINUE}

{ENABLING, INHIBITING} composed of the three dataitems below

Optional All 10 are Optional as above as above as above All 3 are Optional All 5 are Optional

{INTL, UNKN} {E164, E212, F69, NATL, PRIV, UNKN, X121} 1 - 15 characters (0..9, *, #, A, B, C) number: 1 - 15

{CDA, CDA300, CDA1200, CDA2400, CDA4800, CDA9600, CDAGBS, ALTSPCDA, SPCHCDA, CDS, CDS1200, CDS2400, CDS4800, CDS9600, CDSGBS, ALTSPCDS, SPCHCDS, SPCH, TPHNY, AUXSPCH, AUXTPHNY, FAX, FAX3, ALTSPFAX} {FWD, NOT_FWD}

Call Type Criteria

Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-196 Chapter 2: Component descriptions Nortel Confidential Table 2-133 O-CSI data syntax (3 pages) Dataitem Trigger DP2 Phase3 Set SCF Name Service Key SCF Unavailable Treatment DNC Matchtype DNC DNs vector (0 - 10) - NOA - NPI - DN DNC Lengths vector (0 - 3) BS Codes Criteria vector (0 - 5) Syntax 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

Copyright

19962005 Nortel

Optional

{ENABLING, INHIBITING} composed of the three dataitems below

Optional All 10 are Optional as above as above as above All 3 are Optional All 5 are Optional

{ABBR, INTL, NATL, NTWK, SUBS, UNKN} {E164, E212, F69, NATL, PRIV, UNKN, X121} 1 - 15 characters (0..9, *, #, A, B, C) number: 1 - 15

{CDA, CDA300, CDA1200, CDA2400, CDA4800, CDA9600, CDAGBS, ALTSPCDA, SPCHCDA, CDS, CDS1200, CDS2400, CDS4800, CDS9600, CDSGBS, ALTSPCDS, SPCHCDS, SPCH, TPHNY, AUXSPCH, AUXTPHNY, FAX, FAX3, ALTSPFAX} {FWD, NOT_FWD} 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

Call Type Criteria Trigger DP4 Phase3 Set SCF Name Service Key SCF Unavailable Treatment Cause Values Criteria vector (0 - 5)

Optional

number: 1 - 127

All 5 are Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-197 Copyright 19962005 Nortel

O-CSI field descriptions are given in Table 2-134.


Table 2-134 O-CSI field descriptions (3 pages) Dataitem Active FTN Checks Description indicates whether the CSI is active whether the subscriber has GSM FTNs, TIF-CSI FTNs (aka TIF FTNs) or custom FTNs; relates to valid NOA/NPI formats. TIF-CSI is provisioned by setting this dataitem to TIF. unsupported VLR/MSC behaviour: release-call, continue-call or continue-call-if-in-HPLMN behaviour if the GMSC does not support the O-CSI phase: release-call or continue-call indicates whether to query the SCF when in HPLMN SCF Name Service Key SCF Unavailable Treatment Send CCH the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call indicates whether to send the CCH (CAP1) to the VLR

UNSPVMSC

UNSPGMSC

QSCFWIHP Trigger DP2 Phase1 Set

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-198 Chapter 2: Component descriptions Nortel Confidential Table 2-134 O-CSI field descriptions (3 pages) Dataitem Trigger DP2 Phase2 Set SCF Name Service Key SCF Unavailable Treatment DNC Matchtype Description

Copyright

19962005 Nortel

the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call indicates whether the Destination Number Criteria is enabling or inhibiting destination-number-criteria destination numbers, each composed of NOA, NPI and DN the DN Nature Of Address; options are International-number (INTL) and Unknown (UNKN) the DN Number Plan Indicator; options are ISDN/telephonynumbering-plan (E164), Land-mobile-numbering-plan (E212), Telex-numbering-plan (F69), National-numbering-plan (NATL), Private-numbering-plan (PRIV), Unknown (UNKN), Datanumbering-plan (X121) the destination number itself destination-number-criteria destination number lengths

DNC DNs vector (0 - 10) - NOA

- NPI

- DN DNC Lengths vector (0 - 3) BS Codes Criteria vector (0 - 5) Call Type Criteria

basic service codes criteria

indicates whether call type criteria is forwarding or not forwarding

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-134 O-CSI field descriptions (3 pages) Dataitem Trigger DP2 Phase3 Set SCF Name Service Key SCF Unavailable Treatment DNC Matchtype Description

Chapter 2: Component descriptions 2-199 Copyright 19962005 Nortel

the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call indicates whether the Destination Number Criteria is enabling or inhibiting destination-number-criteria destination numbers, each composed of NOA, NPI and DN the DN Nature Of Address; options are Abbreviated-number (ABBR), International-number (INTL), National-significantnumber (NATL), Network-specific-number (NTWK), Subscriber-number (SUBS), Unknown (UNKN) the DN Number Plan Indicator; options are ISDN/telephonynumbering-plan (E164), Land-mobile-numbering-plan (E212), Telex-numbering-plan (F69), National-numbering-plan (NATL), Private-numbering-plan (PRIV), Unknown (UNKN), Datanumbering-plan (X121) the destination number itself destination-number-criteria destination number lengths

DNC DNs vector (0 - 10) - NOA

- NPI

- DN DNC Lengths vector (0 - 3) BS Codes Criteria vector (0 - 5) Call Type Criteria Trigger DP4 Phase3 Set SCF Name Service Key SCF Unavailable Treatment Cause Values Criteria vector (0 - 5)

basic service codes criteria

indicates whether call type criteria is forwarding or not forwarding the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call cause values criteria

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-200 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions O-CSI interacts with all call forwards (CFB, CFNRc, CFNRy, CFU) and system table GHLRSCF. Note that the vast majority of interactions relate (directly or indirectly) to TIF-CSI. O-CSI cannot be newly provisioned with FTN Checks as CUSTOM if the subscriber has any call forward FTNs (i.e. any CF registration data) O-CSI cannot be newly provisioned with FTN Checks as TIF if the subscriber has any call forward FTNs (i.e. any CF registration data) O-CSI cannot be deprovisioned if FTN Checks is CUSTOM and the subscriber has any call forward FTNs (i.e. any CF registration data) O-CSI cannot be deprovisioned if FTN Checks is TIF and the subscriber has any call forward FTNs (i.e. any CF registration data) O-CSI cannot be deprovisioned if the subscriber has any call forwards with a DCF ID datafilled FTN Checks cannot be changed if the subscriber has any call forward FTNs (i.e. any CF registration data) FTN Checks cannot be changed if the subscriber has any call forwards with a DCF ID datafilled each SCF Name must be an entry from the SCF_NAME column of system table GHLRSCF

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-201 Copyright 19962005 Nortel

SMS-CSI (Short Message Service CSI)


SMS-CSI datafill defines trigger information required to invoke CAMEL service logic for mobile originating short message (SMMO) submissions. Datafill

SMS-CSI data syntax is detailed in Table 2-135. As there is only one Trigger DP set (i.e. DP1), it must be provisioned. The intra-service validations therefore are:
Table 2-135 SMS-CSI data syntax Dataitem Active Phase UNSPNODE Trigger DP1 Set SCF Name Service Key SCF Unavailable Treatment Syntax Boolean {CAP3} {RELEASE, CONTINUE, CONT_HPLMN} 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE} Optional

the Trigger DP1 Set must be provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-202 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

SMS-CSI field descriptions are given in Table 2-136.


Table 2-136 SMS-CSI field descriptions Dataitem Active Phase Description indicates whether the CSI is active the CAMEL Phase which is required at the gsmSCF for the service -- this has to be datafilled as Phase 3 (CAP3) also know as the CAMEL Capability Handler (CCH) UNSPNODE behaviour if the VLR/MSC or SGSN does not support Phase 3: release-call, continue-call or continue-call-if-inHPLMN SCF Name Service Key SCF Unavailable Treatment the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF in unavailable: release or continue the GPRS session/PDP context

Trigger DP1 Set

Interactions SMS-CSI interacts with system table GHLRSCF. the SCF Name must be an entry from the SCF_NAME column of system table GHLRSCF

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-203 Copyright 19962005 Nortel

SS-CSI (Supplementary Service CSI)


SS-CSI datafill defines supplementary service notification criteria. Datafill SS-CSI data syntax is detailed in Table 2-137. The following intra-service validations apply.
Table 2-137 SS-CSI data syntax Dataitem Active ECT Option MPTY Option SCF Name Syntax Boolean Boolean Boolean 1 - 20 characters Optional

at least one of ECT Option and MPTY Option must be set to TRUE

SS-CSI field descriptions are given in Table 2-138.


Table 2-138 SS-CSI field descriptions Dataitem Active ECT Option MPTY Option SCF Name Description indicates whether the CSI is active indicates whether notifications are sent for ECT indicates whether notifications are sent for MPTY the SCF name, defined in system table GHLRSCF

Interactions SS-CSI interacts with system table GHLRSCF. the SCF Name must be an entry from the SCF_NAME column of system table GHLRSCF

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-204 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

T-CSI (Terminating CSI)


T-CSI datafill defines subscriber terminating trigger information which is used by GSM nodes to determine when to contact the GSM Service Control Function (gsmSCF), which in turn decides how a call proceeds. Datafill T-CSI data syntax is detailed in Table 2-139 on page 2-205. Each of the Trigger DP sets is optional, although at least one must be provisioned. The following intra-service validations apply. at least one Trigger DP set must be provisioned a particular BS Code can only be datafilled once across both the TDP12 Phase2 and Phase3 sets

for each BS Codes vector, if a BSG code is datafilled then a BS belonging to that BSG cannot also be datafilled a particular Cause Value can only be datafilled once across both the TDP13 and TDP14 sets

Note that in the original Nortel HLR O-CSI/T-CSI implementation, QSCFWIHP was shared between these two services, whereas now it is seen as being specific to O-CSI. Also note that the Nortel HLR shares the UNSPGMSC across both T-CSI and O-CSI (i.e. there is a single value, used by both T-CSI and O-CSI).

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-205 Copyright 19962005 Nortel

.
Table 2-139 T-CSI data syntax (2 pages) Dataitem Active Provide Location Info Page for Cell ID Provide Subscriber State Provide Current Location Suppress T-CSI UNSPGMSC Trigger DP12 Phase1 Set SCF Name Service Key SCF Unavailable Treatment Send CCH Trigger DP12 Phase2 Set SCF Name Service Key SCF Unavailable Treatment BS Codes Criteria vector (0 - 5) Syntax Boolean Boolean Boolean Boolean Boolean {HC, HPLMN} {RELEASE, CONTINUE} 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE} Optional Optional

Boolean 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

{CDA, CDA300, CDA1200, CDA2400, CDA4800, CDA9600, CDAGBS, ALTSPCDA, SPCHCDA, CDS, CDS1200, CDS2400, CDS4800, CDS9600, CDSGBS, ALTSPCDS, SPCHCDS, SPCH, TPHNY, AUXSPCH, AUXTPHNY, FAX, FAX3, ALTSPFAX}

All 5 are Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-206 Chapter 2: Component descriptions Nortel Confidential Table 2-139 T-CSI data syntax (2 pages) Dataitem Trigger DP12 Phase3 Set SCF Name Service Key SCF Unavailable Treatment BS Codes Criteria vector (0 - 5) Syntax 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

Copyright

19962005 Nortel

Optional

{CDA, CDA300, CDA1200, CDA2400, CDA4800, CDA9600, CDAGBS, ALTSPCDA, SPCHCDA, CDS, CDS1200, CDS2400, CDS4800, CDS9600, CDSGBS, ALTSPCDS, SPCHCDS, SPCH, TPHNY, AUXSPCH, AUXTPHNY, FAX, FAX3, ALTSPFAX} 1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

All 5 are Optional

Trigger DP13 Phase3 Set

SCF Name Service Key SCF Unavailable Treatment Cause Values Criteria vector (0 - 5)

number: 1 - 127

All 5 are Optional

Trigger DP14 Phase3 Set

SCF Name Service Key SCF Unavailable Treatment Cause Values Criteria vector (0 - 5)

1 - 20 characters number: 1 - 2147483647 {RELEASE, CONTINUE}

number: 1 - 127

All 5 are Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-207 Copyright 19962005 Nortel

T-CSI field descriptions are given in Table 2-140.


Table 2-140 T-CSI field descriptions (2 pages) Dataitem Active Provide Location Info Page for Cell ID Provide Subscriber State Provide Current Location Suppress T-CSI Description indicates whether the CSI is active indicates whether provide location info is in effect indicates whether page for cell ID is in effect indicates whether provide subscriber state is in effect indicates whether provide current location is in effect indicates when T-CSI is to be suppressed: when-located-inHPLMN-country or when-located-in-HPLMN behaviour if the GMSC does not support the T-CSI phase: release-call or continue-call SCF Name Service Key SCF Unavailable Treatment Send CCH Trigger DP12 Phase2 Set SCF Name Service Key SCF Unavailable Treatment BS Codes Criteria vector (0 - 5) Trigger DP12 Phase3 Set SCF Name Service Key SCF Unavailable Treatment BS Codes Criteria vector (0 - 5) the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call indicates whether to send the CCH (CAP1) to the VLR the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call basic service [group] codes criteria

UNSPGMSC

Trigger DP12 Phase1 Set

the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call basic service [group] codes criteria

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-208 Chapter 2: Component descriptions Nortel Confidential Table 2-140 T-CSI field descriptions (2 pages) Dataitem Trigger DP13 Phase3 Set SCF Name Service Key SCF Unavailable Treatment Cause Values Criteria vector (0 - 5) Trigger DP14 Phase3 Set SCF Name Service Key SCF Unavailable Treatment Cause Values Criteria vector (0 - 5) Description

Copyright

19962005 Nortel

the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call cause values criteria

the DP SCF name, defined in system table GHLRSCF the DP service key the behaviour for this DP if the SCF is unavailable: release or continue the call cause values criteria

Interactions T-CSI interacts with system table GHLRSCF. each SCF Name must be an entry from the SCF_NAME column of system table GHLRSCF

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-209 Copyright 19962005 Nortel

TIF-CSI (Translations Information Flag CSI)


TIF-CSI datafill defines that the usual GSM (conformity to E164) number checks on forwarding-to numbers are suppressed.

The Nortel HLR implements TIF-CSI as a dataitem of O-CSI (FTN Checks). Please refer to O-CSI (Originating CSI)on page 2-193.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-210 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

USSD-CSI (Unstructured Supplementary Service Data CSI)


USSD-CSI datafill defines how the PUSSR (Process Unstructured Supplementary Service Request) message is handled. Datafill USSD-CSI data syntax is detailed in Table 2-141. The IDs are a vector; at least one ID must be datafilled (seeData vectors on page 1-36 for more information on vectors). The following intra-service validations apply. duplicate IDs are not permitted

Table 2-141 USSD-CSI data syntax Dataitem IDs vector (1 - 10) Syntax 1 - 10 characters Optional 9 are Optional

USSD-CSI field descriptions are given in Table 2-142.


Table 2-142 USSD-CSI field descriptions Dataitem ID Description an ID, defined in system table GHLRUSSD

Interactions USSD-CSI interacts with system table GHLRUSSD. each ID must be an entry from the USSD_STR.UCSI_ID field of system table GHLRUSSD; also each ID must be from a different USSD_STR from system table GHLRUSSD (note that each USSD_STR can multiple UCSI_IDs)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-211 Copyright 19962005 Nortel

Location Services (LCS) Introduction

Location services provide value-added, vicinity-specific services to the subscriber. They are composed of four privacy classes and three mobile originating (MO) classes, as given in Table 2-143. Privacy classes indicate what type of clients are allowed to make location requests. MO classes indicate whether/how the subscriber can make MO location requests. Each privacy/MO class is treated as a distinct service. LCS datafill is supplemented by a list of Gateway Mobile Location Centres (GMLCs); they are treated as a separate profile component -- see LCS GMLCs on page 2218.
Table 2-143 Location Services classes Class Autonomous Self Location Basic Self Location Call Related Call Unrelated PLMN Operator Transfer to Third Party Universal Type MO MO Privacy Privacy Privacy MO Privacy See Section on page 2-212 on page 2-213 on page 2-214 on page 2-216 on page 2-219 on page 2-221 on page 2-222

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-212 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

LCS Autonomous Self Location

LCS Autonomous Self Location class specifies that the subscriber does not need interact with the network for each location request. A single interaction enables the subscriber to obtain multiple location positionings during a predetermined period of time. Datafill LCS Autonomous Self Location data syntax is detailed in Table 2-144.
Table 2-144 LCS Autonomous Self Location data syntax Dataitem Active Syntax Boolean Optional

LCS Autonomous Self Location field descriptions are given in Table 2-145.
Table 2-145 LCS Autonomous Self Location field descriptions Dataitem Active Description whether this class is active

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-213 Copyright 19962005 Nortel

LCS Basic Self Location


LCS Basic Self Location class specifies that the subscriber needs to interact with the network for each location request. Datafill LCS Basic Self Location data syntax is detailed in Table 2-146.
Table 2-146 LCS Basic Self Location data syntax Dataitem Active Syntax Boolean Optional

LCS Basic Self Location field descriptions are given in Table 2-147.
Table 2-147 LCS Basic Self Location field descriptions Dataitem Active Description whether this class is active

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-214 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

LCS Call Related


LCS Call Related class allows an LCS client to request the subscribers location if the subscriber originated a call to the client and the call is still established. Datafill LCS Call Related data syntax is detailed in Table 2-148. There are two external client name vectors (see Data vectors on page 1-36 for more information on vectors). The following intra-service validations apply. duplicate external client names are not permitted (names from both vectors are pooled together for this check)

Table 2-148 LCS Call Related data syntax Dataitem Active Notification To User Syntax Boolean {LOC_NOT_ALLOW, LOC_ALLOW_WITHOUT_NOTIF, LOC_ALLOW_WITH_NOTIF, NOTIF_PRVCY_LOC_IF_NO_RSP, NOTIF_PRVCY_LOC_REST_IF_NO_RSP} 1 - 8 characters All 5 are Optional Optional

External Client Names vector (0 - 5) Extended External Client Names vector (0 - 35)

1 - 8 characters

All 35 are Optional

LCS Call Related field descriptions are given in Table 2-149.


Table 2-149 LCS Call Related field descriptions Dataitem Active Notification To User External Client Name Extended External Client Name Description whether this class is active the notification to the user external client name, defined in system table GHLRR4EC external client name, defined in system table GHLRR4EC (the term extended is simply used to identify a separate vector of names)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-215 Copyright 19962005 Nortel

Interactions LCS Call Related interacts with GMLCs and LCS Call Unrelated. GMLCs can only be provisioned if at least one of LCS Call Related/LCS Call Unrelated is also provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-216 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

LCS Call Unrelated


LCS Call Unrelated class allows LCS client to be defined that are able to request the subscribers location. Datafill LCS Call Unrelated data syntax is detailed in Table 2-150. There are two external client name vectors (see Data vectors on page 1-36 for more information on vectors). The following intra-service validations apply. duplicate external client names are not permitted (names from both vectors are pooled together for this check)

Table 2-150 LCS Call Unrelated data syntax Dataitem Active Notification To User Syntax Boolean {LOC_NOT_ALLOW, LOC_ALLOW_WITH_NOTIF, NOTIF_PRVCY_LOC_IF_NO_RSP, NOTIF_PRVCY_LOC_REST_IF_NO_RSP} 1 - 20 characters All 5 are Optional Optional

External Client Names vector (0 - 5) Extended External Client Names vector (0 - 35)

1 - 8 characters

All 35 are Optional

LCS Call Unrelated field descriptions are given in Table 2-151.


Table 2-151 LCS Call Unrelated field descriptions Dataitem Active Notification To User External Client Name Extended External Client Name Description whether this class is active the notification to the user external client name, defined in system table GHLRLSEC external client name, defined in system table GHLRR4EC (the term extended is simply used to identify a separate vector of names)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-217 Copyright 19962005 Nortel

Interactions LCS Call Related interacts with GMLCs and LCS Call Related. GMLCs can only be provisioned if at least one of LCS Call Related/LCS Call Unrelated is also provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-218 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

LCS GMLCs

The GMLCs component gives the Gateway Mobile Location Centres used by LCS Call Related and LCS Call Unrelated. Datafill LCS GMLCs data syntax is detailed in Table 2-152. The GMLC Names are a vector (see Data vectors on page 1-36 for more information on vectors). The following intra-service validations apply. at least one GLMC Name must be datafilled duplicate GLMC Names are not permitted

Table 2-152 LCS GMLCs data syntax Dataitem GMLC Names vector (1 - 5) Syntax 1 - 20 characters Optional 4 Are Optional

LCS GMLCs field descriptions are given in Table 2-153.


Table 2-153 LCS GMLCs field descriptions Dataitem GMLC Name Description a gateway mobile location centre name, an entry from system table GHLRGMLC

Interactions LCS GMLCs interacts with LCS Call Related and LCS Call Unrelated. GMLCs can only be provisioned if at least one of LCS Call Related/LCS Call Unrelated is also provisioned

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-219 Copyright 19962005 Nortel

LCS PLMN Operator


LCS PLMN Operator class allows positioning by specific types of clients indicated in the subscriber's privacy profile. Datafill

LCS PLMN Operator data syntax is detailed in Table 2-154. The following dataitems are known as Internal Client IDs (ICIDs): Broadcast, OMH, OMV, Anonymous, Target MS. The following intra-service validations apply. at least one of the ICIDs must be true: Broadcast, OMH, OMV, Anonymous, Target MS

Table 2-154 LCS PLMN Operator data syntax Dataitem Active Broadcast OMH OMV Anonymous Target MS Syntax Boolean Boolean Boolean Boolean Boolean Boolean Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-220 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

LCS PLMN Operator field descriptions are given in Table 2-155.


Table 2-155 LCS PLMN Operator field descriptions Dataitem Active Broadcast Description whether this class is active indicates whether an LCS client broadcasting location related information is allowed to locate the MS indicates whether an O&M LCS client in the HPLMN is allowed to locate the MS indicates whether an O&M LCS client in the VPLMN is allowed to locate the MS indicates whether an LCS client recording anonymous location information is allowed to locate the MS indicates whether an LCS client supporting a bearer service, teleservice or supplementary service to target the MS is allowed to locate the MS

OMH

OMV

Anonymous

Target MS

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-221 Copyright 19962005 Nortel

LCS Transfer to Third Party


LCS Transfer to Third Party class specifies that the subscribers location is transferred to another LCS client. Datafill LCS Transfer to Third Party data syntax is detailed in Table 2-156.
Table 2-156 LCS Transfer to Third Party data syntax Dataitem Active Syntax Boolean Optional

LCS Transfer to Third Party field descriptions are given in Table 2-157.
Table 2-157 LCS Transfer to Third Party field descriptions Dataitem Active Description whether this class is active

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-222 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

LCS Universal
LCS Universal class allows all LCS clients to request the subscribers location. Datafill LCS Universal data syntax is detailed in Table 2-158.
Table 2-158 LCS Universal data syntax Dataitem Active Syntax Boolean Optional

LCS Universal field descriptions are given in Table 2-159.


Table 2-159 LCS Universal field descriptions Dataitem Active Description whether this class is active

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-223 Copyright 19962005 Nortel

GPRS (General Packet Radio Service)

Provisioning GPRS makes the subscriber a GPRS network subscriber. GPRS datafill allows PDP context IDs to be specified for the subscriber. Datafill GPRS data syntax is detailed in Table 2-160. Each of the Context ID sets is optional.
Table 2-160 GPRS data syntax (2 pages) Dataitem Context ID1 Set PDP Name PDP Static Address Context ID2 Set PDP Name PDP Static Address Context ID3 Set PDP Name PDP Static Address Context ID4 Set PDP Name PDP Static Address Context ID5 Set PDP Name PDP Static Address Context ID6 Set PDP Name PDP Static Address Context ID7 Set PDP Name PDP Static Address Context ID8 Set PDP Name PDP Static Address Context ID9 Set PDP Name PDP Static Address Context ID10 Set PDP Name PDP Static Address Syntax 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional Optional

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-224 Chapter 2: Component descriptions Nortel Confidential Table 2-160 GPRS data syntax (2 pages) Dataitem Context ID11 Set PDP Name PDP Static Address Context ID12 Set PDP Name PDP Static Address Context ID13 Set PDP Name PDP Static Address Context ID14 Set PDP Name PDP Static Address Context ID15 Set PDP Name PDP Static Address Context ID16 Set PDP Name PDP Static Address Context ID17 Set PDP Name PDP Static Address Context ID18 Set PDP Name PDP Static Address Context ID19 Set PDP Name PDP Static Address Context ID20 Set PDP Name PDP Static Address Syntax 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot) 1 - 16 characters 1 - 63 characters (0..9, dot)

Copyright

19962005 Nortel

Optional

Optional

Optional

Optional

Optional

Optional

Optional

Optional

Optional

Optional

Optional

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-225 Copyright 19962005 Nortel

GPRS field descriptions are given in Table 2-161.


Table 2-161 GPRS field descriptions (3 pages) Dataitem Context ID1 Set PDP Name Description PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format

PDP Static Address

Context ID2 Set

PDP Name

PDP Static Address

Context ID3 Set

PDP Name

PDP Static Address

Context ID4 Set

PDP Name

PDP Static Address

Context ID5 Set

PDP Name

PDP Static Address

Context ID6 Set

PDP Name

PDP Static Address

Context ID7 Set

PDP Name

PDP Static Address

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-226 Chapter 2: Component descriptions Nortel Confidential Table 2-161 GPRS field descriptions (3 pages) Dataitem Context ID8 Set PDP Name Description

Copyright

19962005 Nortel

PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format

PDP Static Address

Context ID9 Set

PDP Name

PDP Static Address

Context ID10 Set

PDP Name

PDP Static Address

Context ID11 Set

PDP Name

PDP Static Address

Context ID12 Set

PDP Name

PDP Static Address

Context ID13 Set

PDP Name

PDP Static Address

Context ID14 Set

PDP Name

PDP Static Address

Context ID15 Set

PDP Name

PDP Static Address

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table 2-161 GPRS field descriptions (3 pages) Dataitem Context ID16 Set PDP Name Description

Chapter 2: Component descriptions 2-227 Copyright 19962005 Nortel

PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format PDP name for this context ID, defined in system table GHLRPDP PDP static address for this context ID, may be IPv4, IPv6 or X25 format

PDP Static Address

Context ID17 Set

PDP Name

PDP Static Address

Context ID18 Set

PDP Name

PDP Static Address

Context ID19 Set

PDP Name

PDP Static Address

Context ID20 Set

PDP Name

PDP Static Address

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-228 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

Interactions GPRS interacts with Auth data, GPRS-CSI and system tables GHLRPDP and GHLRALG. GPRS must be provisioned for GPRS-CSI to be provisioned for each Static Address datafilled, their format is checked against the PDP type. PDP type is determined by lookup of the PDP Name in system table GHLRPDP, and checking the PDPTYPE (FORMAT) field. for IPv4 types, address must be of format x.x.x.x where x is (0255) for IPv6 types, address must be of format x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x where each of the 16 xs is (0-255) for X25 types, address must be 1 - 14 digits for PPP types, address must not be datafilled if the subscriber is 3G then all PDP Names must have ExtQoS determination of 2G/3G requires Auth data and system table GHLRALG -- see Determination of 2G/3G algorithm on page 2-43 determination of PDP ExtQoS requires lookup of the PDP Name in system table GHLRPDP, and checking whether the EXTQOS field is null or datafilled

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-229 Copyright 19962005 Nortel

Other Services introduction

Other Services are those that do not fit within the following categories: basic services, supplementary services, CAMEL service, Location Services, GPRS. A list of these services is given in Table 2-162.
Table 2-162 Other Services Short Name CLIN EA Proprietary IN Expanded Name Calling Line Identification Replacement Number Equal Access Proprietary Intelligent Network service See Section on page 2-230 on page 2-231 on page 2-232

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-230 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

CLIN (Calling Line Identification Replacement Number)

Provisioning CLIN enables CLI Replacement Number functionality for the subscriber (CLIN allows an alternative number to be used for TPHNYs CLI, i.e. not TPHNYs actual MSISDN). Note that CLIN service is distinct, and quite different from the common use of the word CLIN as calling line ID number. CLIN is a Nortel proprietary service. Datafill CLIN data syntax is detailed in Table 2-163.
Table 2-163 CLIN data syntax Dataitem CLI Syntax 1 - 15 digits Optional

CLIN field descriptions are given in Table 2-164.


Table 2-164 CLIN field descriptions Dataitem CLI Description the replacement calling line identity for telephony

Interactions CLIN interacts with TPHNY. TPHNY must be provisioned for CLIN to be provisioned

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-231 Copyright 19962005 Nortel

EA (Equal Access)
EA datafill allows a primary interexchange carrier to be given to the subscriber. EA is a Nortel proprietary service. Datafill EA data syntax is detailed in Table 2-165.
Table 2-165 EA data syntax Dataitem PIC Syntax 4 digits Optional

EA field descriptions are given in Table 2-166.


Table 2-166 EA field descriptions Dataitem PIC Description Primary Interexchange Carrier

Interactions None

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-232 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

Proprietary IN (Proprietary Intelligent Network service)


This service provides Nortel proprietary IN, allowing an IN platform to be specified for both originating and terminating calls. Datafill Proprietary IN data syntax is detailed in Table 2-167.
Table 2-167 Proprietary IN data syntax Dataitem INORIG INTERM Syntax number: 0 - 1023 number: 0 - 1023 Optional Optional Optional

Proprietary IN field descriptions are given in Table 2-168.


Table 2-168 Proprietary IN field descriptions Dataitem INORIG INTERM Description IN index for IN platform originating calls IN index for IN platform terminating calls

Interactions None

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-233 Copyright 19962005 Nortel

Other components introduction


The concept of other components is introduced in Chapter 1. A list of these components is given in Table 2-169.
Table 2-169 Other Components Short Name HST SIMR Expanded Name Home Subscriber Trace SIM Replacement See Section on page 2-234 on page 2-235

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-234 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel
2

HST (Home Subscriber Trace)


Home Subscriber Trace (HST) is used to track subscribers within the HPLMN. Datafill HST data syntax is detailed in Table 2-170. The following intra-service validations apply.
Table 2-170 HST data syntax Dataitem Trace Reference OMC Destination Trace Type Syntax number: 0 - 65535 0 - 38 digits (0..9) number: 0 - 255 Optional

none of the dataitems can be changed once provisioned (it is possible to deprovision HST, however)

HST field descriptions are given in Table 2-171.


Table 2-171 HST field descriptions Dataitem Trace Reference OMC Destination Trace Type Description trace reference (used as an identifier) Operator Maintenance Centre Destination address identifies the trace type

Interactions None HLR-wide interactions a maximum of 1024 subscribers may be provisioned with HST at any one time

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-235 Copyright 19962005 Nortel

SIMR (SIM Replacement)

A SIM Replacement (SIMR) entry is used to set up a relationship between two IMSIs, whereby one IMSI will replace an old IMSI at a certain date. The Nortel HLR specifies that the New IMSI must exist in the database, thereby placing restrictions on the New IMSIs profile. It is strongly recommended that the SIMR documentation is used to set up SIMR relationships; the information here is provided as a guide only. Datafill SIMR data syntax is detailed in Table 2-172. The following intra-service validations apply.
Table 2-172 SIMR data syntax Dataitem New IMSI Old IMSI Option Invocation Date Activation Date Syntax 6 - 15 digits 6 - 15 digits {FIXED, USER} Date (nearest hour) Date (nearest hour) Optional Optional

the New IMSI must be present in the database the Old IMSI must be present in the database (this is the subscribers current profile) the New IMSI and Old IMSI must be different Activation Date must not be datafilled if Option is FIXED Activation Date must be datafilled if Option is USER if datafilled, the Activation Date must be before the Invocation Date

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-236 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

SIMR field descriptions are given in Table 2-173.


Table 2-173 SIMR field descriptions Dataitem New IMSI Description the new International Mobile Subscriber Identity, the replacement IMSI for the subscriber the old International Mobile Subscriber Identity, the current IMSI for the subscriber how the swapover will occur; fixed option swaps IMSIs on a (fixed) invocation date; the user option swaps IMSIs on activation of the new IMSI (via using new SIM), or on the invocation date if activation has not yet occurred the time the swapover will occur (for user option, this only applies if there was not an update location for the new SIM/IMSI) the time from which a subscriber may use its new SIM (and hence an update location will trigger a SIMR swap)

Old IMSI

Option

Invocation Date

Activation Date

Interactions As the Nortel HLR requires the New IMSI to be present in the database, the following restrictions have to be made to the New IMSI profile: the IMSI Status must not be ACTIVATED if the IMSI Status is DEACTIVATED all profile control data must be set to their defaults (see Profile control data introduction on page 2-44) no services can be provisioned HST cannot be provisioned there are several interactions with mated-pair: the New IMSI must not be SIMR blocked, the acting status for both Old IMSI and New IMSI must match, the maintenance blocked status for Old IMSI and New IMSI must match and partition numbers for Old IMSI and New IMSI must match and not be equal zero

The following requires a check on the Old IMSI. if the New IMSI is 3G (see Determination of 2G/3G algorithm on page 2-43) then the Old IMSIs GPRS PDPs (if any) must all have ExtQoS (see Interactions on page 2-228)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 2: Component descriptions 2-237 Copyright 19962005 Nortel

HLR-wide interactions a maximum of 10,000 SIMR relationships may be set up at any one time the New IMSI cannot be defined as an Old IMSI in an existing SIMR relationship the Old IMSI cannot be defined as an Old IMSI or New IMSI in an existing SIMR relationship

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

2-238 Chapter 2: Component descriptions Nortel Confidential

Copyright

19962005 Nortel

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

3-239

Chapter 3: Suppression States

Each BSG registration set of each BSG-Supplementary Service has a suppression state. These states are used in conjunction with registration and activation states within the network. Suppression states are not part of the subscriber profile and are given here as extra information. Each time a BSG registration set is added or updated, its suppression state must be recalculated -- this may involve interactions with several other services. Note that a suppression state is only applicable to activated registration sets. The following supplementary services have suppression states: BICRoam, CFB, CFNRc, CFNRy and EXT. Some ODBs also have a single suppression state, although this is sometimes called an activation state. Those ODBs are ODB BICRoam, ODB BAOCRoam and ODB HPLMN Specific categories. Suppression state determination is given for each service in their own subsection; Figure 3-1 is a diagram of all suppression interactions.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

3-240 Chapter 3: Suppression States Nortel Confidential Figure 3-1 Service suppressions
In HPLMN Country

Copyright

19962005 Nortel

BICRoam

ODB-BAOCRoam

ODB-BICRoam

BOIC[exHC] 1 1 1 1

CFU

CCFs

EXT

ODB-HPLMNSpec

ODB-BOIC[exHC]

ODB-PremRate Outside HPLMN

ODB-BAOC

ODB-BAIC

KEY 1 Only applies if the


suppressing service is not suppressed

2 Only applies if
ODB-HPLMNSpec is not suppressed

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 3: Suppression States 3-241 Copyright 19962005 Nortel

BICRoam suppression state determination


BICRoam suppression state determination is detailed in Table 3-1..
Table 3-1 Determine BICRoam registration set suppression Suppressed By Service Subscriber Location CFU State N/A location is in HPLMN Country Conditions

Activated and not Suppressed

none

CFB suppression state determination


CFB suppression state determination is detailed in Table 3-2..
Table 3-2 Determine CFB registration set suppression (2 pages) Suppressed By Service CFU BOIC State Activated Activated none (always suppressed) has GSM-FTNs and FTN is international wrt current location has GSM-FTNs and FTN is not in HPLMN and is international wrt current location does not have TIF-FTNs Conditions

BOICexHC

Activated

BICRoam

Activated & Not Suppressed Provisioned Provisioned & Activated Provisioned Provisioned

ODB BAIC ODB BICRoam

does not have TIF-FTNs does not have TIF-FTNs

ODB BAOC ODB BOIC

does not have TIF-FTNs has GSM-FTNs and FTN is international wrt current location has GSM-FTNs and FTN is not in HPLMN and is international wrt current location

ODB BOICexHC

Provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

3-242 Chapter 3: Suppression States Nortel Confidential Table 3-2 Determine CFB registration set suppression (2 pages) Suppressed By Service ODB BAOCRoam State Provisioned & Not Suppressed Provisioned Conditions

Copyright

19962005 Nortel

does not have TIF-FTNs

ODB Prem Rate categories

has GSM-FTNs and FTN is barred for the category in system table GHLRODB has GSM-FTNs and FTN is barred for the category in system table GHLRODB

ODB HPLMN Specific categories

Provisioned & Not Suppressed

CFNRc suppression state determination

CFNRc suppression state determination is identical for that of CFB -- please refer to Table 3-2.

CFNRy suppression state determination

CFNRy suppression state determination is identical for that of CFB -- please refer to Table 3-2.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 3: Suppression States 3-243 Copyright 19962005 Nortel

CFU suppression state determination


CFU suppression state determination is detailed in Table 3-3..
Table 3-3 Determine CFU registration set suppression Suppressed By Service ODB BAOC ODB BOIC State Provisioned Provisioned does not have TIF-FTNs has GSM-FTNs and FTN is international wrt HPLMN Country has GSM-FTNs and FTN is international wrt HPLMN Country does not have TIF-FTNs has GSM-FTNs and FTN is barred for the category in system table GHLRODB has GSM-FTNs and FTN is barred for the category in system table GHLRODB Conditions

ODB BOICexHC

Provisioned

ODB BAIC ODB Prem Rate categories

Provisioned Provisioned

ODB HPLMN Specific categories

Provisioned

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

3-244 Chapter 3: Suppression States Nortel Confidential

Copyright

19962005 Nortel
3

EXT suppression state determination


EXT suppression state determination is detailed in Table 3-4. EXT is a special case in that every MSISDN has a suppression state, rather than each registration set.
Table 3-4 Determine EXT MSISDN suppression Suppressed By Service ODB BAOC State Provisioned all MSISDNs except Pilot MSISDNs are suppressed only if office parameter EXTODBON (GHLRPARM) is true MSISDNs international wrt HPLMN Country are suppressed (note that Pilot MSISDNs will never be suppressed because they are in HPLMN) MSISDNs international wrt HPLMN Country are suppressed (note that Pilot MSISDNs will never be suppressed because they are in HPLMN) all MSISDNs are suppressed MSISDNs that are barred for ODB Prem Rate are suppressed (using system table GHLRODB) MSISDNs that are barred for ODB HPLMN Specific are suppressed (using system table GHLRODB) Conditions

ODB BOIC

Provisioned

ODB BOICexHC

Provisioned

ODB BAIC ODB Prem Rate categories

Provisioned Provisioned

ODB HPLMN Specific categories

Provisioned

ODB BICRoam suppression state determination


ODB BICRoam suppression state determination is detailed in Table 3-5. Note that ODB suppression states may also be called an activation state; therefore not suppressed is equivalent to activated.
Table 3-5 Determine ODB BICRoam suppression Suppressed By Service Subscriber Location State N/A location is in HPLMN Country Conditions

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Chapter 3: Suppression States 3-245 Copyright 19962005 Nortel

ODB BAOCRoam suppression state determination


ODB BAOCRoam suppression state determination is detailed in Table 3-6. Note that ODB suppression states may also be called an activation state; therefore not suppressed is equivalent to activated.
Table 3-6 Determine ODB BAOCRoam suppression Suppressed By Service Subscriber Location State N/A location is in HPLMN Country Conditions

ODB HPLMN specific sategories suppression state determination 3


ODB HPLMN Specific categories suppression state determination is detailed in Table 3-7. Note that ODB suppression states may also be called an activation state; therefore not suppressed is equivalent to activated.
Table 3-7 Determine ODB HPLMN specific categories suppression Suppressed by Service Subscriber Location State N/A location outside HPLMN Conditions

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

3-246 Chapter 3: Suppression States Nortel Confidential

Copyright

19962005 Nortel

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

A-247

Appendix A: Oracle implementation

The subscriber data schema comprises 40 tables and stores authentication data, profile control data, services data and SIMR data. The schema is a logical database composed of Oracle views, based on the actual physical tables. This document uses the term table when referring to the views. The schema tables are listed in Table A-4 on page A-252, and presented in a diagram in Figure A-1 on page A-255. Note that the routing schema is described later in Routing Schema on page A-343. Most tables store just one particular service, and are named sub_<service>. Other tables store more than one service, while some services are actually datafilled across more than one table. Exceptions to the sub_<service> format are as follows: Three tables store more than one service. Table sub_odbs stores all ODBs. Table sub_basic_services stores all basic services. Table sub_imsi_ss stores all IMSI-SSs Three services are split across more than one table. CUG is datafilled in table sub_cug_subscription and table sub_cug_feature. GPRS is datafilled in table sub_gprs_prov and sub_gprs_pdps. LCS can be seen as one service, or a collection of services; it is datafilled in six tables all prefixed with sub_lcs_

Profile control data, along with some service data is grouped into one table, sub_general.

Datatypes in Oracle
The subscriber profile database is composed of a finite number of datatypes. They are listed in Table A-1 below, including their mapping to Oracle types. Note that the x values indicate the maximum length of the particular string/ enum/number. A discussion of datatypes in the data model is given in Datatypes on page 1-36.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-248 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Dataitem syntax is described in the data model section of this document (see Chapter 2: Component descriptions). The schema description in the following sections gives the Oracle types for each dataitem (i.e. column). Note that strings and enum options are always stored in uppercase, as are booleans (TRUE and FALSE). Time dataitems can be to the nearest day or hour and hence have two format types.
Table A-1 Datatypes and their Oracle implementation Data Model Definition Datatype Number String Digit String Hex Digit String Enum Boolean Time Format m - n range m - n characters m - n digits m digits {a, b, c, ..., z} {true, false} to nearest second or hour Oracle Schema Definition Oracle Type number(x) varchar2(x) varchar2(x) varchar2(x) varchar2(x) varchar2(5) varchar2(20) varchar2(17) Syntax number: m - n m - n characters (what chars) m - n digits m hex digits enum: A, B, C, Z boolean DD-Mon-YYYY 24HH:MM:SS DD-Mon-YYYY 24HH:MM

Vectors in Oracle One column is assigned to each possible value, with a number appended to the column name to distinguish the different columns. For example, a nodes vector of one to four elements is represented by columns node1, node2, node3 and node4. The number is simply there to distinguish the columns, it has no other meaning as vectors are not ordered. As elements are datafilled, they use up positions in numerical order (i.e. 1 first, then 2, then 3 and finally 4). If an element is removed, then the elements after that element shift down one position. See Table A-2 on page A-249 for an example of how this works. The initial state shows the vector as not being datafilled. If two elements are added in the same transaction then there is no guarantee of the order in which they are datafilled. It is not possible to provision an element at an explicit position.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-249 Copyright 19962005 Nortel

Table A-2 Datafilling vectors example Column Name node1 node2 node3 node4 Initial State null null null null Add A A null null null Add B A B null null Add C A B C null Remove A B C null null Remove C B null null null

A small number of vectors are complex vectors, i.e. the elements are actually structures, which themselves contain two or more elements. An example of such a vector is given in Table A-3. The vector has 1 - 3 structures, with each structure being composed of elements colour and style.
Table A-3 Complex vector example Column Name colour1 style1 colour2 style2 colour3 style3

A discussion of vectors in the data model is given in Data vectors on page 1-36.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-250 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Sets in Oracle All sets are named, and such names are used to qualify column names belonging to a particular set. For example, a set may be named Code A, and have dataitems activated and option. The column names would be codeA_activated and codeA_option. An additional boolean column is used to indicate whether the set is provisioned or not. It is named <setname>_prov or <setname>_reg. The _reg naming convention is used for services that have registration data (as named by GSM specifications); the _prov convention is used for all other sets. If a set-provisioned column is set to FALSE, then the set dataitems will always be all set to null. Sets are introduced in this document in Chapter 1, Data sets on page 1-20.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-251 Copyright 19962005 Nortel

Section Structure
A schema guide is presented in Guide to table sections on page A-256. A sample table section is given with explanations. There is also an overview of the datatypes used in the subscriber database. Tables are described in detail starting on page A-258. The order of tables is given below. Authentication Data General Data ODBs Basic Services Supplementary Services Barrings Incoming (alphabetical) Outgoing (alphabetical) Call Forwards (alphabetical) Other BSG-SSs (alphabetical) IMSI-SSs CAMEL Services (alphabetical) CLIN EA GPRS LCS GSMR Basic Services SIMR

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-252 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Schema tables listing and diagram


Subscriber profile data schema tables are listed in Table A-4. Indications of any changes in the current release, brief descriptions and page number references are given. Note that in NSS18 all tables are marked as New; this is because they are new to the Oracle subscriber schema, rather than being new tables to the HLR. A diagram of the schema is given in Figure A-1 on page A-255. Services that span multiple tables are indicated.
Table A-4 Subscriber data schema tables (3 pages) Table Name New/ Changed/ Deleted New Description See Section

sub_auth

mandatory table storing authentication data mandatory table storing general data stores ODB provisioning statuses stores all basic service data stores BAIC data stores BAOC data stores BICRoam data stores BOIC data stores BOICexHC data stores CFB data stores CFNRc data stores CFNRy data stores CFU data stores COS data stores CUG feature data stores CUG subscription data stores CW data stores EXT data

on page A-258

sub_general

New

on page A-259

sub_odbs sub_basic_services sub_baic sub_baoc sub_bicroam sub_boic sub_boicexhc sub_cfb sub_cfnrc sub_cfnry sub_cfu sub_cos sub_cug_feature sub_cug_subscription sub_cw sub_ext

New New New New New New New New New New New New New New New New

on page A-262 on page A-264 on page A-265 on page A-267 on page A-269 on page A-271 on page A-273 on page A-275 on page A-277 on page A-279 on page A-281 on page A-283 on page A-285 on page A-287 on page A-289 on page A-291

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-4 Subscriber data schema tables (3 pages) Table Name New/ Changed/ Deleted New New New New New New New New New New New New Description

Appendix A: Oracle implementation A-253 Copyright 19962005 Nortel

See Section

sub_imsi_ss sub_dcsi sub_gprs_csi sub_mcsi sub_ocsi sub_sms_csi sub_ss_csi sub_tcsi sub_ussd_csi sub_clin sub_ea sub_gprs_prov

stores all IMSI-SS data stores D-CSI data stores GPRS-CSI data stores M-CSI data stores O-CSI data stores SMS-CSI data stores SS-CSI data stores T-CSI data stores USSD-CSI data stores CLIN data stores EA data stores GPRS provisioning indications stores GPRS data stores LCS call related privacy class data stores LCS call unrelated privacy class data stores LCS GMLCs stores LCS mobile originating data stores LCS PLMN operator privacy class data stores LCS universal privacy class data stores VBS data stores VGCS data

on page A-294 on page A-297 on page A-299 on page A-301 on page A-302 on page A-309 on page A-310 on page A-311 on page A-315 on page A-317 on page A-318 on page A-319

sub_gprs_pdps sub_lcs_call_related

New New

on page A-320 on page A-321

sub_lcs_call_unrelated

New

on page A-324

sub_lcs_gmlcs sub_lcs_mobile_originating sub_lcs_plmn_operator

New New New

on page A-327 on page A-329 on page A-331

sub_lcs_universal

New

on page A-333

sub_vbs sub_vgcs

New New

on page A-334 on page A-339

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-254 Appendix A: Oracle implementation Nortel Confidential Table A-4 Subscriber data schema tables (3 pages) Table Name New/ Changed/ Deleted New Description

Copyright

19962005 Nortel

See Section

sub_simr

stores SIMR relationships data

on page A-342

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Figure A-1 Oracle Schema diagram

Appendix A: Oracle implementation A-255 Copyright 19962005 Nortel

SUB_AUTH SUB_GENERAL SUB_ODBS

SUB_DCSI SUB_GPRS_CSI SUB_MCSI SUB_OCSI

SUB_BASIC_SERVICES

SUB_SMS_CSI SUB_SS_CSI

SUB_BAIC SUB_TCSI SUB_BAOC SUB_USSD_CSI SUB_BICROAM SUB_BOIC SUB_BOICEXHC SUB_CFB SUB_CFNRC SUB_CFNRY SUB_CFU SUB_COS SUB_CUG_SUBSCRIPTION SUB_CUG_FEATURE SUB_CW SUB_EXT SUB_IMSI_SS

SUB_CLIN SUB_EA SUB_GPRS_PROV SUB_GPRS_PDPS SUB_LCS_UNIVERSAL SUB_LCS_CALL_RELATED SUB_LCS_CALL_UNRELATED SUB_LCS_PLMN_OPERATOR SUB_LCS_GMLCS SUB_LCS_MOBILE_ORIGINATING SUB_VBS SUB_VGCS SUB_SIMR

A B C

Auth data, General data, ODBs Basic Services Supplementary Services

D E

CAMEL Services Other Services

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-256 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Guide to table sections


Case conventions used in this document are outlined in Case conventions below. An example table section with help is given in Table EXAMPLE_TAB on page A-257. The schema tables are each presented in their own section starting on page A-258. Case conventions The table names and column names in Oracle are case-insensitive. This document uses the following conventions for these names, primarily to aid readability. Names are presented in either all uppercase or all lowercase, and never a mix of the two. Note that Oracle internally stores all names as uppercase (this affects SQL select statements for instance). Table names in headings and paragraphs are all uppercase (SUB_GENERAL), in tables they are bold italic lowercase (sub_general). Column names in paragraph text are italic lowercase (imsi_status), in tables they are either lowercase (imsi_status) or all uppercase (IMSI_STATUS). System table names in paragraph text are bold small uppercase ( GHLRDCFB), while system table column names in paragraph text are small uppercase (DCFID).

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-257 Copyright 19962005 Nortel

Table EXAMPLE_TAB An introductory paragraph (or two) gives a brief description of the table, indicating what services the table stores. Information tables (see Table A-5 for an example) contain general information about the table, such as number of columns, rows per subscriber and primary key.
Table A-5 Table EXAMPLE_TAB information Number of Columns Rows per Subscriber the total number of columns in the table, including key columns the range for the number of rows any one subscriber may have, and whether they are mandatory or optional the primary key column(s) foreign key columns and what tables/columns they refer to the indexes on this table used when a service spans multiple tables; lists the other tables

Primary Key Foreign Keys Indexes Also See Table(s)

Field details tables (see Table A-6 for an example) show all column (i.e. field/dataitem) names, with their Oracle type and constraints. Two examples are also given. Note that some tables can have multiple rows per subscriber, but the examples are obviously limited to showing a single row each.
Table A-6 Table EXAMPLE_TAB field details Column Name column_a (this is the primary key identified by the grey background; the primary key may be composed of multiple columns) Oracle Type the Oracle type for this column, examples are varchar2(x), number(x) and date; x indicates the max number of digits/ chars etc. etc. etc. Constraints Oracle constraints, example is "not null", which means the column must be datafilled Example 1 Example datafill Example 2 Alternative set of example datafill

column_b column_c column_d

etc. etc. etc.

etc. etc. etc.

etc. etc. etc.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-258 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_AUTH
This table stores authentication data for both 2G and 3G subscribers. This is the primary subscriber table and denotes a subscribers existence. A row in this table is mandatory for all subscribers. General table information is given in Table A-7.
Table A-7 Table SUB_AUTH information Number of Columns Rows per Subscriber Primary Key Foreign Keys Indexes Also See Table(s) 3 One Mandatory IMSI None IMSI None

Field details for SUB_AUTH are given in Table A-8, along with example values. Field descriptions and validations are given in Chapter 2, Authentication data on page 2-41.
Table A-8 Table SUB_AUTH field details Column Name imsi algorithm opc Oracle Type varchar2(15) number(3) varchar2(32) Constraints not null not null Example 1 456231234567890 2 null Example 2 234109920024844 101 11AB11E111CD21231E1 11544141132A1

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-259 Copyright 19962005 Nortel

Table SUB_GENERAL
This table stores miscellaneous provisioning data, such as profile control data and timestamps. A row in this table is mandatory for all subscribers. General table information is given in Table A-9.
Table A-9 Table SUB_GENERAL information Number of Columns Rows per Subscriber Primary Key Foreign Keys 20 One Mandatory IMSI IMSI to table sub_auth , column IMSI HLR_ID to table hlrs, column ID Indexes Also See Table(s) IMSI None

Field details for SUB_GENERAL are given in Table A-10 on page A-260, along with example values. Field descriptions and validations are given in the following sections: imsi_status, cust_group and ncos, IMSI Status on page 2-49 roaming_ent, Roaming Entitlement on page 2-54 category, Category on page 2-46 bicctrl, bocctrl, Barring control on page 2-45 password, Password on page 2-53 inorig, interm, Proprietary IN (Proprietary Intelligent Network service) on page 2-232 soa_prov, SOAPROV on page 2-55 nam, NAM (Network Access Mode) on page 2-52 lmu, LMU (Location Measurement Unit) on page 2-51

The hlr_id indicates the HLR Core the subscriber resides on (see Table HLRS on page A-343). Column network_active indicates whether the subscriber has had its first network activity.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-260 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

The creation_time is a timestamp for creation of the subscriber in the database. The sub_last_modified is a timestamp for the last modification made to the subscriber's profile in the Oracle database; null change provisioning requests will not update the subscriber's profile in the database and so will not update this timestamp. The imsi_status_last_modified is a timestamp for the last modification to the imsi_status; a null change will not update the timestamp. The imsi_status_last_activated is a timestamp for when the imsi_status was last set to ACTIVATED; a null change will not update the timestamp.
Table A-10 Table SUB_GENERAL field details Column Name imsi imsi_status cust_group ncos hlr_id roaming_ent category bicctrl bocctrl password inorig interm soa_prov nam lmu network_active creation_time Oracle Type varchar2(15) varchar2(11) number(4) number(3) varchar2(10) varchar2(16) varchar2(12) varchar2(8) varchar2(8) varchar2(4) number(4) number(4) varchar2(5) varchar2(12) varchar2(5) varchar2(5) varchar2(20) not null not null not null not null not null not null not null not null not null not null not null Constraints not null not null Example 1 456231234567890 DEACTIVATED null null 1234567890 UNKW ORDINARY OPERATOR OPERATOR 1234 null null FALSE MSC_ONLY FALSE FALSE 25-Dec-2003 21:30:58 25-Dec-2003 23:01:20 Example 2 234109920024844 ACTIVATED null null 1231231234 MYHPLMN ORDINARY USER OPERATOR 1234 567 567 TRUE SGSN_AND_MSC TRUE TRUE 05-Jan-2004 21:30:58 29-Mar-2004 07:31:18

sub_last_modified

varchar2(20)

not null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-10 Table SUB_GENERAL field details Column Name imsi_status_last_ modified imsi_status_last_ activated Oracle Type varchar2(20) Constraints not null

Appendix A: Oracle implementation A-261 Copyright 19962005 Nortel

Example 1 25-Dec-2003 21:30:58 null

Example 2 25-Feb-2004 15:30:00 25-Feb-2004 15:30:00

varchar2(20)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-262 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_ODBS
This table stores Operator Determined Barrings (ODB) provisioning statuses. A row in this table is mandatory for all subscribers. General table information is given in Table A-11.
Table A-11 Table SUB_ODBS information Number of Columns Rows per Subscriber Primary Key Foreign Keys Indexes Also See Table(s) 21 One Mandatory IMSI IMSI to table sub_auth, column IMSI IMSI None

Field details for SUB_ODBS are given in Table A-12 on page A-263, along with example values. ODB validations are discussed in ODBs (Operator Determined Barrings) on page 2-184.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-263 Copyright 19962005 Nortel

Table A-12 Table SUB_ODBS field details Column Name imsi odb_baic_prov odb_bicroam_prov odb_boac_prov odb_boic_prov odb_boicexhc_prov odb_boacroam_prov odb_incoming odb_outgoing odb_baect_prov odb_bchdect_prov odb_bintect_prov odb_bdbcect_prov odb_premrate_info_prov odb_premrate_ent_prov odb_hplmnspec1_prov odb_hplmnspec2_prov odb_hplmnspec3_prov odb_hplmnspec4_prov odb_bcissmgt_prov odb_bccfmgt_prov Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(7) varchar2(8) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null not null not null not null not null not null not null not null Constraints not null not null not null not null not null not null not null Example 1 456231234567890 TRUE FALSE FALSE FALSE FALSE FALSE BAIC null FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE Example 2 234109920024844 FALSE TRUE FALSE FALSE TRUE FALSE BICROAM BOICEXHC FALSE FALSE FALSE FALSE TRUE TRUE TRUE FALSE FALSE FALSE FALSE TRUE

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-264 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_BASIC_SERVICES
This table stores all basic services. One row is datafilled for each provisioned basic service. General table information is given in Table A-13.
Table A-13 Table SUB_BASIC_SERVICES information Number of Columns Rows per Subscriber 7 Zero to 19* One row per basic service Primary Key Foreign Keys Indexes IMSI+BS IMSI to table sub_auth, column IMSI IMSI+BS MSISDN Also See Table(s) None

* theoretical maximum and very unlikely in reality; a typical subscriber would have one to five rows Field details for SUB_BASIC_SERVICES are given in Table A-14, along with example values (show one row only, a subscriber may have multiple rows of course). Field descriptions and validations are given from Basic Services Introduction on page 2-56 to VGCS (Voice Group Call Service) on page 2-106.
Table A-14 Table SUB_BASIC_SERVICES field details Column Name imsi bs msisdn_cc msisdn_ndc msisdn_sn msisdn bci Oracle Type varchar2(15) varchar2(8) varchar2(3) varchar2(13) varchar2(13) varchar2(15) number(3) Constraints not null not null not null not null not null not null Example 1 456231234567890 TPHNY 61 123 555555 61123555555 null Example 2 234109920024844 FAX3 44 7 123456 447123456 123

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-265 Copyright 19962005 Nortel

Table SUB_BAIC
This table stores BAIC data. A row in this table indicates that the subscriber has BAIC provisioned. General table information is given in Table A-15.
Table A-15 Table SUB_BAIC information Number of Columns Rows per Subscriber 13 Zero or One One row if BAIC is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_BAIC are given in Table A-16 on page A-266, along with example values. BAIC datafill is composed of six sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in BAIC (Barring of All Incoming Calls) on page 2-113.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-266 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-16 Table SUB_BAIC field details Column Name imsi spch_reg spch_act auxspch_reg auxspch_act sms_reg sms_act cda_reg cda_act cds_reg cds_act fax_reg fax_act Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null FALSE null FALSE null FALSE null FALSE null FALSE null Example 2 234109920024844 TRUE TRUE FALSE null TRUE FALSE FALSE null FALSE null FALSE null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-267 Copyright 19962005 Nortel

Table SUB_BAOC
This table stores BAOC data. A row in this table indicates that the subscriber has BAOC provisioned. General table information is given in Table A-17.
Table A-17 Table SUB_BAOC information Number of Columns Rows per Subscriber 15 Zero or One One row if BAOC is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_BAOC are given in Table A-18 on page A-268, along with example values. BAOC datafill is composed of seven sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in BAOC (Barring of All Outgoing Calls) on page 2-115.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-268 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-18 Table SUB_BAOC field details Column Name imsi spch_reg spch_act auxspch_reg auxspch_act sms_reg sms_act cda_reg cda_act cds_reg cds_act fax_reg fax_act vgs_reg vgs_act Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null FALSE null FALSE null FALSE null FALSE null FALSE null FALSE null Example 2 234109920024844 TRUE TRUE FALSE null TRUE FALSE FALSE null FALSE null FALSE null TRUE TRUE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-269 Copyright 19962005 Nortel

Table SUB_BICROAM
This table stores BICRoam data. A row in this table indicates that the subscriber has BICRoam provisioned. General table information is given in Table A-19.
Table A-19 Table SUB_BICROAM information Number of Columns Rows per Subscriber 13 Zero or One One row if BICRoam is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_BICROAM are given in Table A-20 on page A-270, along with example values. BICRoam datafill is composed of six sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in BICRoam (Barring of Incoming Calls when Roaming outside HPLMN country) on page 2-117.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-270 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-20 Table SUB_BICROAM field details Column Name imsi spch_reg spch_act auxspch_reg auxspch_act sms_reg sms_act cda_reg cda_act cds_reg cds_act fax_reg fax_act Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null FALSE null FALSE null FALSE null FALSE null FALSE null Example 2 234109920024844 TRUE TRUE FALSE null FALSE null FALSE null FALSE null TRUE FALSE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-271 Copyright 19962005 Nortel

Table SUB_BOIC
This table stores BOIC data. A row in this table indicates that the subscriber has BOIC provisioned. General table information is given in Table A-21.
Table A-21 Table SUB_BOIC information Number of Columns Rows per Subscriber 13 Zero or One One row if BOIC is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_BOIC are given in Table A-22 on page A-272, along with example values. BOIC datafill is composed of six sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in BOIC (Barring of Outgoing International Calls) on page 2-119.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-272 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-22 Table SUB_BOIC field details Column Name imsi spch_reg spch_act auxspch_reg auxspch_act sms_reg sms_act cda_reg cda_act cds_reg cds_act fax_reg fax_act Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null FALSE null FALSE null FALSE null FALSE null FALSE null Example 2 234109920024844 FALSE null FALSE null FALSE null TRUE FALSE FALSE null TRUE TRUE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-273 Copyright 19962005 Nortel

Table SUB_BOICEXHC
This table stores BOICexHC data. A row in this table indicates that the subscriber has BOICexHC provisioned. General table information is given in Table A-23.
Table A-23 Table SUB_BOICEXHC information Number of Columns Rows per Subscriber 13 Zero or One One row if BOICexHC is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_BOICEXHC are given in Table A-24 on page A-274, along with example values. BOICexHC datafill is composed of six sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in BOICexHC (Barring of Outgoing International Calls except to HPLMN Country) on page 2-121.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-274 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-24 Table SUB_BOICEXHC field details Column Name imsi spch_reg spch_act auxspch_reg auxspch_act sms_reg sms_act cda_reg cda_act cds_reg cds_act fax_reg fax_act Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null FALSE null FALSE null FALSE null FALSE null FALSE null Example 2 234109920024844 TRUE TRUE TRUE TRUE FALSE null FALSE null TRUE TRUE TRUE TRUE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-275 Copyright 19962005 Nortel

Table SUB_CFB
This table stores CFB data. A row in this table indicates that the subscriber has CFB provisioned. General table information is given in Table A-25.
Table A-25 Table SUB_CFB information Number of Columns Rows per Subscriber 29 Zero or One One row if CFB is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_CFB are given in Table A-26, along with example values. CFB datafill includes five sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in CFB (Call Forward when Busy) on page 2-123.
Table A-26 Table SUB_CFB field details (2 pages) Column Name imsi ncp nfp dcf_id spch_reg spch_act spch_noa spch_npi spch_ftn auxspch_reg auxspch_act Oracle Type varchar2(15) varchar2(4) varchar2(4) varchar2(20) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) not null not null Constraints not null not null not null Example 1 456231234567890 NONF NONF null FALSE null null null null FALSE null Example 2 234109920024844 NF NFWN DCF_ID1 TRUE TRUE INTL E164 44123888888 TRUE TRUE

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-276 Appendix A: Oracle implementation Nortel Confidential Table A-26 Table SUB_CFB field details (2 pages) Column Name auxspch_noa auxspch_npi auxspch_ftn cda_reg cda_act cda_noa cda_npi cda_ftn cds_reg cds_act cds_noa cds_npi cds_ftn fax_reg fax_act fax_noa fax_npi fax_ftn Oracle Type varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) not null not null not null Constraints Example 1 null null null FALSE null null null null FALSE null null null null FALSE null null null null

Copyright

19962005 Nortel

Example 2 INTL E164 44123888777 FALSE null null null null FALSE null null null null FALSE null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-277 Copyright 19962005 Nortel

Table SUB_CFNRC
This table stores CFNRc data. A row in this table indicates that the subscriber has CFNRc provisioned. General table information is given in Table A-27.
Table A-27 Table SUB_CFNRC information Number of Columns Rows per Subscriber 28 Zero or One One row if CFNRc is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys

Indexes Also See Table(s)

Field details for SUB_CFNRC are given in Table A-28, along with example values. CFNRc datafill includes five sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in CFNRc (Call Forward when Not Reachable) on page 2-130.
Table A-28 Table SUB_CFNRC field details (2 pages) Column Name imsi ncp dcf_id spch_reg spch_act spch_noa spch_npi spch_ftn auxspch_reg auxspch_act Oracle Type varchar2(15) varchar2(4) varchar2(20) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) not null not null Constraints not null not null Example 1 456231234567890 NONF null FALSE null null null null FALSE null Example 2 234109920024844 NF null TRUE TRUE INTL E164 44123888888 TRUE TRUE

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-278 Appendix A: Oracle implementation Nortel Confidential Table A-28 Table SUB_CFNRC field details (2 pages) Column Name auxspch_noa auxspch_npi auxspch_ftn cda_reg cda_act cda_noa cda_npi cda_ftn cds_reg cds_act cds_noa cds_npi cds_ftn fax_reg fax_act fax_noa fax_npi fax_ftn Oracle Type varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) not null not null not null Constraints Example 1 null null null FALSE null null null null FALSE null null null null FALSE null null null null

Copyright

19962005 Nortel

Example 2 INTL E164 44123888777 FALSE null null null null FALSE null null null null FALSE null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-279 Copyright 19962005 Nortel

Table SUB_CFNRY
This table stores CFNRy data. A row in this table indicates that the subscriber has CFNRy provisioned. General table information is given in Table A-29.
Table A-29 Table SUB_CFNRY information Number of Columns Rows per Subscriber 34 Zero or One One row if CFNRy is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_CFNRY are given in Table A-30, along with example values. CFNRy datafill includes five sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in CFNRy (Call Forward when No Reply) on page 2-136.
Table A-30 Table SUB_CFNRY field details (2 pages) Column Name imsi ncp nfp dcf_id spch_reg spch_act spch_noa spch_npi spch_ftn spch_nr_time Oracle Type varchar2(15) varchar2(4) varchar2(4) varchar2(20) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) number(2) not null Constraints not null not null not null Example 1 456231234567890 NONF NONF null TRUE TRUE NTL PRIV 885566 5 Example 2 234109920024844 NF NFWN DCF_ID2 TRUE TRUE INTL E164 44123888888 30

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-280 Appendix A: Oracle implementation Nortel Confidential Table A-30 Table SUB_CFNRY field details (2 pages) Column Name auxspch_reg auxspch_act auxspch_noa auxspch_npi auxspch_ftn auxspch_nr_time cda_reg cda_act cda_noa cda_npi cda_ftn cda_nr_time cds_reg cds_act cds_noa cds_npi cds_ftn cds_nr_time fax_reg fax_act fax_noa fax_npi fax_ftn fax_nr_time Oracle Type varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) number(2) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) number(2) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) number(2) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) number(2) not null not null not null Constraints not null Example 1 FALSE null null null null null TRUE TRUE INTL E164 61123555444 20 FALSE null null null null null FALSE null null null null null

Copyright

19962005 Nortel

Example 2 TRUE TRUE INTL E164 44123888777 25 FALSE null null null null null FALSE null null null null null FALSE null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-281 Copyright 19962005 Nortel

Table SUB_CFU
This table stores CFU data. A row in this table indicates that the subscriber has CFU provisioned. General table information is given in Table A-31.
Table A-31 Table SUB_CFU information Number of Columns Rows per Subscriber 27 Zero or One One row if CFU is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_CFU are given in Table A-32, along with example values. CFU datafill includes five sets, each with a registered status ( _reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in CFU (Call Forward Unconditionally) on page 2-143.
Table A-32 Table SUB_CFU field details (2 pages) Column Name imsi ncp spch_reg spch_act spch_noa spch_npi spch_ftn auxspch_reg auxspch_act auxspch_noa auxspch_npi Oracle Type varchar2(15) varchar2(4) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) not null Constraints not null not null not null Example 1 456231234567890 NONF FALSE null null null null FALSE null null null Example 2 234109920024844 NF TRUE TRUE INTL E164 44123888888 FALSE null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-282 Appendix A: Oracle implementation Nortel Confidential Table A-32 Table SUB_CFU field details (2 pages) Column Name auxspch_ftn cda_reg cda_act cda_noa cda_npi cda_ftn cds_reg cds_act cds_noa cds_npi cds_ftn fax_reg fax_act fax_noa fax_npi fax_ftn Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) varchar2(5) varchar2(5) varchar2(4) varchar2(4) varchar2(15) not null not null not null Constraints Example 1 null FALSE null null null null FALSE null null null null FALSE null null null null

Copyright

19962005 Nortel

Example 2 null FALSE null null null null FALSE null null null null FALSE null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-283 Copyright 19962005 Nortel

Table SUB_COS
This table stores COS data. A row in this table indicates that the subscriber has COS provisioned. General table information is given in Table A-33.
Table A-33 Table SUB_COS information Number of Columns Rows per Subscriber 21 Zero or One One row if COS is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_COS are given in Table A-34 on page A-284, along with example values. COS datafill is composed of five sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in COS (Class of Service) on page 2-155.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-284 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-34 Table SUB_COS field details Column Name imsi spch_reg spch_act spch_cust_group spch_ncos auxspch_reg auxspch_act auxspch_cust_group auxspch_ncos cda_reg cda_act cda_cust_group cda_ncos cds_reg cds_act cds_cust_group cds_ncos fax_reg fax_act fax_cust_group fax_ncos Oracle Type varchar2(15) varchar2(5) varchar2(5) number(4) number(3) varchar2(5) varchar2(5) number(4) number(3) varchar2(5) varchar2(5) number(4) number(3) varchar2(5) varchar2(5) number(4) number(3) varchar2(5) varchar2(5) number(4) number(3) not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null null null FALSE null null null FALSE null null null FALSE null null null FALSE null null null Example 2 234109920024844 TRUE TRUE 1000 null TRUE TRUE 56 45 FALSE null null null FALSE null null null FALSE null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-285 Copyright 19962005 Nortel

Table SUB_CUG_FEATURE
This table stores CUG Feature data. A row in this table indicates that the subscriber has CUG Feature provisioned. General table information is given in Table A-35. Note that CUG Feature is optional CUG data -- mandatory CUG data is CUG Subscription, which is stored in a separate table, SUB_CUG_SUBSCRIPTION (see table on page A-287 ).
Table A-35 Table SUB_CUG_FEATURE information Number of Columns Rows per Subscriber 25 Zero or One One entry if CUG Feature is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI sub_cug_subscription

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_CUG_FEATURE are given in Table A-36, along with example values. CUG Feature is composed of six sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in CUG Feature (Closed User Groups Feature) on page 2-161.
Table A-36 Table SUB_CUG_FEATURE field details (2 pages) Column Name imsi spch_reg spch_act spch_ica spch_prefcug_index auxspch_reg auxspch_act auxspch_ica auxspch_prefcug_index Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(3) number(5) varchar2(5) varchar2(5) varchar2(3) number(5) not null Constraints not null not null Example 1 456231234567890 TRUE TRUE NONE 345 TRUE TRUE ALL null Example 2 234109920024844 FALSE null null null FALSE null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-286 Appendix A: Oracle implementation Nortel Confidential Table A-36 Table SUB_CUG_FEATURE field details (2 pages) Column Name cda_reg cda_act cda_ica cda_prefcug_index cds_reg cds_act cds_ica cds_prefcug_index fax_reg fax_act fax_ica fax_prefcug_index allbsg_prov allbsg_act allbsg_ica allbsg_prefcug_index Oracle Type varchar2(5) varchar2(5) varchar2(3) number(5) varchar2(5) varchar2(5) varchar2(3) number(5) varchar2(5) varchar2(5) varchar2(3) number(5) varchar2(5) varchar2(5) varchar2(3) number(5) not null not null not null Constraints not null Example 1 FALSE null null null FALSE null null null FALSE null null null FALSE null null null

Copyright

19962005 Nortel

Example 2 FALSE null null null FALSE null null null FALSE null null null TRUE TRUE OA null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-287 Copyright 19962005 Nortel

Table SUB_CUG_SUBSCRIPTION
This table stores CUG Subscription data. One or more rows in this table indicates that the subscriber has CUG Subscription provisioned (and hence has CUG provisioned). General table information is given in Table A-37. Note that CUG Feature data (optional CUG data) is stored separately in table SUB_CUG_FEATURE -- see table on page A-285 .
Table A-37 Table SUB_CUG_SUBSCRIPTION information Number of Columns Rows per Subscriber 11 Zero to ten One row for each CUG Subscription dataset provisioned IMSI+NETWORK_ID+INTERLOCK IMSI to table sub_auth, column IMSI IMSI+NETWORK_ID+INTERLOCK sub_cug_feature

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_CUG_SUBSCRIPTION are given in Table A-38 on page A-288, along with example values (note that a subscriber may have multiple rows in this table). Field descriptions and validations are given in CUG Subscription (Closed User Groups Subscription) on page 2-159.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-288 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

.
Table A-38 Table SUB_CUG_SUBSCRIPTION field details Column Name imsi network_id interlock cug_index intracug_restrictions spch_reg auxspch_reg fax_reg cda_reg cds_reg allbsg_reg Oracle Type varchar2(15) varchar2(4) number(5) number(5) varchar2(3) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null not null Constraints not null not null not null not null Example 1 456231234567890 567 17 1234 null TRUE TRUE FALSE FALSE FALSE FALSE Example 2 234109920024844 9800 65000 32000 ICB FALSE FALSE FALSE FALSE FALSE TRUE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-289 Copyright 19962005 Nortel

Table SUB_CW
This table stores CW data. A row in this table indicates that the subscriber has CW provisioned. General table information is given in Table A-39.
Table A-39 Table SUB_CW information Number of Columns Rows per Subscriber 13 Zero or One One row if CW is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_CW are given in Table A-40 on page A-290, along with example values. CW datafill is composed of six sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A-250. Field descriptions and validations are given in CW (Call Waiting) on page 2-164.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-290 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-40 Table SUB_CW field details Column Name imsi spch_reg spch_act auxspch_reg auxspch_act sms_reg sms_act cda_reg cda_act cds_reg cds_act fax_reg fax_act Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null FALSE null FALSE null FALSE null FALSE null FALSE null Example 2 234109920024844 TRUE TRUE FALSE null FALSE null FALSE null FALSE null FALSE null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-291 Copyright 19962005 Nortel

Table SUB_EXT
This table stores EXT data. A row in this table indicates that the subscriber has EXT provisioned. General table information is given in Table A-41.
Table A-41 Table SUB_EXT information Number of Columns Rows per Subscriber 37 Zero or One One row if EXT is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_EXT are given in Table A-42, along with example values. EXT datafill is composed of two sets, each with a registered status (_reg fields); for more information on sets see Sets in Oracle on page A250. Field descriptions and validations are given in EXT (Extension Services) on page 2-168.
Table A-42 Table SUB_EXT field details (3 pages) Column Name imsi spch_reg spch_act spch_msisdn1_1 spch_msisdn1_2 spch_msisdn1_3 spch_timer1 spch_group1 spch_msisdn2_1 spch_msisdn2_2 spch_msisdn2_3 Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(15) varchar2(15) varchar2(15) number(2) varchar2(2) varchar2(15) varchar2(15) varchar2(15) Constraints not null not null Example 1 456231234567890 TRUE TRUE 61123777777 61123777788 null 30 SINGLE null null null Example 2 234109920024844 TRUE TRUE 4477111111 4477222222 null 30 SINGLE 4477333333 null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-292 Appendix A: Oracle implementation Nortel Confidential Table A-42 Table SUB_EXT field details (3 pages) Column Name spch_timer2 spch_group2 spch_msisdn3_1 spch_msisdn3_2 spch_msisdn3_3 spch_timer3 spch_group3 spch_group_overall auxspch_reg auxspch_act auxspch_msisdn1_1 auxspch_msisdn1_2 auxspch_msisdn1_3 auxspch_timer1 auxspch_group1 auxspch_msisdn2_1 auxspch_msisdn2_2 auxspch_msisdn2_3 auxspch_timer2 auxspch_group2 auxspch_msisdn3_1 auxspch_msisdn3_2 auxspch_msisdn3_3 auxspch_timer3 auxspch_group3 Oracle Type number(2) varchar2(2) varchar2(15) varchar2(15) varchar2(15) number(2) varchar2(2) varchar2(2) varchar2(5) varchar2(5) varchar2(15) varchar2(15) varchar2(15) number(2) varchar2(2) varchar2(15) varchar2(15) varchar2(15) number(2) varchar2(2) varchar2(15) varchar2(15) varchar2(15) number(2) varchar2(2) not null Constraints Example 1 null null null null null null null null TRUE TRUE 6112377111 6112377222 6112377333 5 MULTIPLE 6112377444 6112377555 null 20 SINGLE null null null null null

Copyright

19962005 Nortel

Example 2 35 null 4477444444 4477555555 null 40 SINGLE MULTIPLE FALSE null null null null null null null null null null null null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-42 Table SUB_EXT field details (3 pages) Column Name auxspch_group_overall Oracle Type varchar2(2) Constraints

Appendix A: Oracle implementation A-293 Copyright 19962005 Nortel

Example 1 MULTIPLE

Example 2 null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-294 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_IMSI_SS
This table stores all IMSI-Supplementary Services, both provisioning indications and service data. A row in this table is mandatory for all subscribers, even if no IMSI-SSs are provisioned. General table information is given in Table A-43.
Table A-43 Table SUB_IMSI_SS information Number of Columns Rows per Subscriber Primary Key Foreign Keys Indexes Also See Table(s) 35 One Mandatory IMSI IMSI to table sub_auth, column IMSI IMSI None

Field details for SUB_IMSI_SS are given in Table A-44 on page A-295, along with example values. The <service>_prov fields indicate whether the particular service is provisioned. Field descriptions and validations are given in the particular service section in Chapter 2: Component descriptions (see Supplementary Services introduction on page 2-107 for a list of section references.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-295 Copyright 19962005 Nortel

Table A-44 Table SUB_IMSI_SS field details (2 pages) Column Name imsi acc_prov acc_option acc_ver_length acrj_prov aocc_prov aoci_prov clip_prov clip_override clir_prov clir_pm cnam_prov colp_prov colp_override colr_prov ect_prov emlpp_prov emlpp_max_priority emlpp_def_priority fm_prov fm_cor_a fm_cor_b fm_cor_c fm_cor_d Oracle Type varchar2(15) varchar2(5) varchar2(5) number(2) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(4) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(1) varchar2(1) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) not null not null not null not null not null not null not null not null not null not null not null Constraints not null not null Example 1 456231234567890 FALSE null null FALSE FALSE FALSE FALSE null FALSE null FALSE FALSE null FALSE FALSE FALSE null null FALSE null null null null Example 2 234109920024844 TRUE VOL null TRUE TRUE FALSE TRUE FALSE FALSE null FALSE FALSE null FALSE TRUE TRUE B 2 FALSE null null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-296 Appendix A: Oracle implementation Nortel Confidential Table A-44 Table SUB_IMSI_SS field details (2 pages) Column Name fm_sup_cor_a fm_sup_cor_b fm_sup_cor_c fm_sup_cor_d hold_prov hotbill_prov lco_prov mct_prov mpty_prov mpty_option uus1_prov Oracle Type varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(6) varchar2(5) not null not null not null not null not null not null Constraints Example 1 null null null null TRUE FALSE FALSE FALSE TRUE M3PORT FALSE

Copyright

19962005 Nortel

Example 2 null null null null TRUE FALSE TRUE FALSE TRUE M6PORT FALSE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-297 Copyright 19962005 Nortel

Table SUB_DCSI
This table stores D-CSI data. A row in this table indicates that the subscriber has D-CSI provisioned. General table information is given in Table A-45.
Table A-45 Table SUB_DCSI information Number of Columns Rows per Subscriber 15 Zero or One One row if D-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_DCSI are given in Table A-46 on page A-298, along with example values. The criteria_name<x> columns make up the criteria names vector (for more information on vectors see Data vectors on page 136). The criteria names are datafilled in numerical order, as indicated in the examples. Field descriptions and validations are given in D-CSI (Dialled CSI) on page 2-187.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-298 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-46 Table SUB_DCSI field details Column Name imsi active phase unspvmsc unspgmsc criteria_name1 criteria_name2 criteria_name3 criteria_name4 criteria_name5 criteria_name6 criteria_name7 criteria_name8 criteria_name9 criteria_name10 Oracle Type varchar2(15) varchar2(5) varchar2(4) varchar2(10) varchar2(8) varchar2(20) varchar2(20) varchar2(20) varchar2(20) varchar2(20) varchar2(20) varchar2(20) varchar2(20) varchar2(20) varchar2(20) Constraints not null not null not null not null not null not null Example 1 456231234567890 TRUE CAP3 CONT_HPLMN CONTINUE CRIT_NAMEA CRIT_NAMEC CRIT_NAMEB CRIT_NAMEZ null null null null null null Example 2 234109920024844 TRUE CAP3 RELEASE RELEASE CRIT_NAMEZ null null null null null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-299 Copyright 19962005 Nortel

Table SUB_GPRS_CSI
This table stores GPRS-CSI data. A row in this table indicates that the subscriber has GPRS-CSI provisioned. General table information is given in Table A-47.
Table A-47 Table SUB_GPRS_CSI information Number of Columns Rows per Subscriber 24 Zero or One One row if GPRS-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_GPRS_CSI are given in Table A-48 on page A-300, along with example values. GPRS-CSI has five sets, each having a provisioned status (named tdp<x>_prov; for more information on sets see Sets in Oracle on page A-250). Field descriptions and validations are given in GPRS-CSI (General Packet Radio Service CSI) on page 2-189.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-300 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-48 Table SUB_GPRS_CSI field details Column Name imsi active phase unspsgsn tdp1_prov tdp1_scf_name tdp1_service_key tdp1_scf_unavail tdp2_prov tdp2_scf_name tdp2_service_key tdp2_scf_unavail tdp11_prov tdp11_scf_name tdp11_service_key tdp11_scf_unavail tdp12_prov tdp12_scf_name tdp12_service_key tdp12_scf_unavail tdp14_prov tdp14_scf_name tdp14_service_key tdp14_scf_unavail Oracle Type varchar2(15) varchar2(5) varchar2(4) varchar2(10) varchar2(5) varchar2(20) number(10) varchar2(8) varchar2(5) varchar2(20) number(10) varchar2(8) varchar2(5) varchar2(20) number(10) varchar2(8) varchar2(5) varchar2(20) number(10) varchar2(8) varchar2(5) varchar2(20) number(10) varchar2(8) not null not null not null not null Constraints not null not null not null not null not null Example 1 456231234567890 TRUE CAP3 RELEASE TRUE MYSCF1 345345344 RELEASE FALSE null null null FALSE null null null TRUE MYSCF99 423422 CONTINUE FALSE null null null Example 2 234109920024844 TRUE CAP3 CONTINUE TRUE MYSCF1 1113322 RELEASE FALSE null null null FALSE null null null FALSE null null null FALSE null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-301 Copyright 19962005 Nortel

Table SUB_MCSI
This table stores M-CSI data. A row in this table indicates that the subscriber has M-CSI provisioned. General table information is given in Table A-49.
Table A-49 Table SUB_MCSI information Number of Columns Rows per Subscriber 4 Zero or One One row if M-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_MCSI are given in Table A-50, along with example values. Field descriptions and validations are given in M-CSI (Mobility Management CSI) on page 2-192.
Table A-50 Table SUB_MCSI field details Column Name imsi active mobility_trigger_name suppress_mcsi Oracle Type varchar2(15) varchar2(5) varchar2(20) varchar2(5) Constraints not null not null not null Example 1 456231234567890 TRUE TRIGGER_NAMEA null Example 2 234109920024844 FALSE TRIGGER_NAMEZ HC

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-302 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_OCSI
This table stores O-CSI data. A row in this table indicates that the subscriber has O-CSI provisioned. General table information is given in Table A-51.
Table A-51 Table SUB_OCSI information Number of Columns Rows per Subscriber 108 Zero or One One row if O-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_OCSI are given in Table A-52 on page A-303, along with example values. O-CSI has four sets, TDP2 Phase1, TDP2 Phase2, TDP2 Phase3 and TDP4 Phase3. Each has a provisioned status, named tdp<x>_phase<y>_prov. There are several vectors in O-CSI datafill. The simple vectors are destination number length criteria (2 vectors), BS codes criteria (2 vectors) and cause values criteria: tdp2_ph2_dnc_length<x> tdp2_ph2_bs_code_cri<x> tdp2_ph3_dnc_length<x> tdp2_ph3_bs_code_cri<x> tdp4_ph3_cause_value_cri<x>

O-CSI also has two complex vectors for destination number criteria: tdp2_ph2_dnc_dn<x>_noa + tdp2_ph2_dnc_dn<x>_npi + tdp2_ph2_dnc_dn<x> tdp2_ph3_dnc_dn<x>_noa + tdp2_ph3_dnc_dn<x>_npi + tdp2_ph3_dnc_dn<x>

For more information on vectors see Vectors in Oracle on page A-248. Field descriptions and validations are given in O-CSI (Originating CSI) on page 2-193.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-303 Copyright 19962005 Nortel

Table A-52 Table SUB_OCSI field details (6 pages) Column Name imsi active ftn_checks unspvmsc unspgmsc qscfwihp tdp2_ph1_prov tdp2_ph1_scf_name tdp2_ph1_service_key tdp2_ph1_scf_unavail tdp2_ph1_send_cch tdp2_ph2_prov tdp2_ph2_scf_name tdp2_ph2_service_key tdp2_ph2_scf_unavail tdp2_ph2_dnc_match _type tdp2_ph2_dnc_dn1 _noa tdp2_ph2_dnc_dn1_npi tdp2_ph2_dnc_dn1 tdp2_ph2_dnc_dn2 _noa tdp2_ph2_dnc_dn2_npi tdp2_ph2_dnc_dn2 Oracle Type varchar2(15) varchar2(5) varchar2(6) varchar2(10) varchar2(8) varchar2(5) varchar2(5) varchar2(20) number(10) varchar2(8) varchar2(5) varchar2(5) varchar2(20) number(10) varchar2(8) varchar2(10) not null Constraints not null not null not null not null not null not null not null Example 1 456231234567890 TRUE GSM CONTINUE CONTINUE TRUE FALSE null null null null TRUE MYSCF99 1234567 RELEASE null Example 2 234109920024844 TRUE TIF CONT_HPLMN CONTINUE FALSE FALSE null null null null FALSE null null null null

varchar2(4)

null

null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15)

null null

null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-304 Appendix A: Oracle implementation Nortel Confidential Table A-52 Table SUB_OCSI field details (6 pages) Column Name tdp2_ph2_dnc_dn3 _noa tdp2_ph2_dnc_dn3_npi tdp2_ph2_dnc_dn3 tdp2_ph2_dnc_dn4 _noa tdp2_ph2_dnc_dn4_npi tdp2_ph2_dnc_dn4 tdp2_ph2_dnc_dn5 _noa tdp2_ph2_dnc_dn5_npi tdp2_ph2_dnc_dn5 tdp2_ph2_dnc_dn6 _noa tdp2_ph2_dnc_dn6_npi tdp2_ph2_dnc_dn6 tdp2_ph2_dnc_dn7 _noa tdp2_ph2_dnc_dn7_npi tdp2_ph2_dnc_dn7 tdp2_ph2_dnc_dn8 _noa tdp2_ph2_dnc_dn8_npi tdp2_ph2_dnc_dn8 tdp2_ph2_dnc_dn9 _noa tdp2_ph2_dnc_dn9_npi tdp2_ph2_dnc_dn9 Oracle Type varchar2(4) Constraints Example 1 null

Copyright

19962005 Nortel

Example 2 null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15)

null null

null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-52 Table SUB_OCSI field details (6 pages) Column Name tdp2_ph2_dnc_dn10 _noa tdp2_ph2_dnc_dn10 _npi tdp2_ph2_dnc_dn10 tdp2_ph2_dnc_length1 tdp2_ph2_dnc_length2 tdp2_ph2_dnc_length3 tdp2_ph2_bs_code _cri1 tdp2_ph2_bs_code _cri2 tdp2_ph2_bs_code _cri3 tdp2_ph2_bs_code _cri4 tdp2_ph2_bs_code _cri5 tdp2_ph2_call_type_cri tdp2_ph3_prov tdp2_ph3_scf_name tdp2_ph3_service_key tdp2_ph3_scf_unavail tdp2_ph3_dnc_match _type tdp2_ph3_dnc_dn1 _noa tdp2_ph3_dnc_dn1_npi tdp2_ph3_dnc_dn1 Oracle Type varchar2(4) Constraints

Appendix A: Oracle implementation A-305 Copyright 19962005 Nortel

Example 1 null

Example 2 null

varchar2(4)

null

null

varchar2(15) number(2) number(2) number(2) varchar2(8)

null null null null null

null null null null null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(7) varchar2(5) varchar2(20) number(10) varchar2(8) varchar2(10) not null

null TRUE MYSCFA 257 RELEASE null

null TRUE MYSCF1 33221100 CONTINUE ENABLING

varchar2(4)

null

INTL

varchar2(4) varchar2(15)

null null

E164 44789123123123

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-306 Appendix A: Oracle implementation Nortel Confidential Table A-52 Table SUB_OCSI field details (6 pages) Column Name tdp2_ph3_dnc_dn2 _noa tdp2_ph3_dnc_dn2_npi tdp2_ph3_dnc_dn2 tdp2_ph3_dnc_dn3 _noa tdp2_ph3_dnc_dn3_npi tdp2_ph3_dnc_dn3 tdp2_ph3_dnc_dn4 _noa tdp2_ph3_dnc_dn4_npi tdp2_ph3_dnc_dn4 tdp2_ph3_dnc_dn5 _noa tdp2_ph3_dnc_dn5_npi tdp2_ph3_dnc_dn5 tdp2_ph3_dnc_dn6 _noa tdp2_ph3_dnc_dn6_npi tdp2_ph3_dnc_dn6 tdp2_ph3_dnc_dn7 _noa tdp2_ph3_dnc_dn7_npi tdp2_ph3_dnc_dn7 tdp2_ph3_dnc_dn8 _noa tdp2_ph3_dnc_dn8_npi tdp2_ph3_dnc_dn8 Oracle Type varchar2(4) Constraints Example 1 null

Copyright

19962005 Nortel

Example 2 INTL

varchar2(4) varchar2(15) varchar2(4)

null null null

E164 44789333333 INTL

varchar2(4) varchar2(15) varchar2(4)

null null null

E164 4478977778888 INTL

varchar2(4) varchar2(15) varchar2(4)

null null null

E164 4478922112211 null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4) varchar2(15)

null null

null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-52 Table SUB_OCSI field details (6 pages) Column Name tdp2_ph3_dnc_dn9 _noa tdp2_ph3_dnc_dn9_npi tdp2_ph3_dnc_dn9 tdp2_ph3_dnc_dn10 _noa tdp2_ph3_dnc_dn10 _npi tdp2_ph3_dnc_dn10 tdp2_ph3_dnc_length1 tdp2_ph3_dnc_length2 tdp2_ph3_dnc_length3 tdp2_ph3_bs_code _cri1 tdp2_ph3_bs_code _cri2 tdp2_ph3_bs_code _cri3 tdp2_ph3_bs_code _cri4 tdp2_ph3_bs_code _cri5 tdp2_ph3_call_type_cri tdp4_ph3_prov tdp4_ph3_scf_name tdp4_ph3_service_key tdp4_ph3_scf_unavail tdp4_ph3_cause_value _cri1 Oracle Type varchar2(4) Constraints

Appendix A: Oracle implementation A-307 Copyright 19962005 Nortel

Example 1 null

Example 2 null

varchar2(4) varchar2(15) varchar2(4)

null null null

null null null

varchar2(4)

null

null

varchar2(15) number(2) number(2) number(2) varchar2(8)

null null null null TPHNY

null null null null null

varchar2(8)

CDA

null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(7) varchar2(5) varchar2(20) number(10) varchar2(8) number(3) not null

null TRUE MYSCFB 12 CONTINUE null

FWD TRUE MYSCFZ 1234533233 RELEASE 34

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-308 Appendix A: Oracle implementation Nortel Confidential Table A-52 Table SUB_OCSI field details (6 pages) Column Name tdp4_ph3_cause_value _cri2 tdp4_ph3_cause_value _cri3 tdp4_ph3_cause_value _cri4 tdp4_ph3_cause_value _cri5 Oracle Type number(3) Constraints Example 1 null

Copyright

19962005 Nortel

Example 2 123

number(3)

null

number(3)

null

null

number(3)

null

null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-309 Copyright 19962005 Nortel

Table SUB_SMS_CSI
This table stores SMS-CSI data. A row in this table indicates that the subscriber has SMS-CSI provisioned. General table information is given in Table A-53.
Table A-53 Table SUB_SMS_CSI information Number of Columns Rows per Subscriber 8 Zero or One One row if SMS-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys

Indexes Also See Table(s)

Field details for SUB_SMS_CSI are given in Table A-54, along with example values. Field descriptions and validations are given in SMS-CSI (Short Message Service CSI) on page 2-201.
Table A-54 Table SUB_SMS_CSI field details Column Name imsi active phase unspnode tdp1_prov tdp1_scf_name tdp1_service_key tdp1_scf_unavail Oracle Type varchar2(15) varchar2(5) varchar2(4) varchar2(10) varchar2(5) varchar2(20) number(10) varchar2(8) Constraints not null not null not null not null not null Example 1 456231234567890 TRUE CAP3 RELEASE TRUE MYSCF5 12345678 RELEASE Example 2 234109920024844 FALSE CAP3 CONTINUE TRUE MYSCF1 889988441 RELEASE

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-310 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_SS_CSI
This table stores SS-CSI data. A row in this table indicates that the subscriber has SS-CSI provisioned. General table information is given in Table A-55.
Table A-55 Table SUB_SS_CSI information Number of Columns Rows per Subscriber 5 Zero or One One row if SS-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys

Indexes Also See Table(s)

Field details for SUB_SS_CSI are given in Table A-56, along with example values. Field descriptions and validations are given in SS-CSI (Supplementary Service CSI) on page 2-203.
Table A-56 Table SUB_SS_CSI field details Column Name imsi active ect_option mpty_option scf_name Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(20) Constraints not null Example 1 456231234567890 TRUE TRUE FALSE MYSCF99 Example 2 234109920024844 FALSE TRUE TRUE MYSCFA

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-311 Copyright 19962005 Nortel

Table SUB_TCSI
This table stores T-CSI data. A row in this table indicates that the subscriber has T-CSI provisioned. General table information is given in Table A-57.
Table A-57 Table SUB_TCSI information Number of Columns Rows per Subscriber 49 Zero or One One row if T-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_TCSI are given in Table A-58 on page A-312, along with example values. T-CSI has five sets, TDP12 Phase1, TDP12 Phase2, TDP12 Phase3, TDP13 Phase3 and TDP14 Phase3, each having a provisioned status (named tdp<x>_ph<y>_prov; for more information on sets see Sets in Oracle on page A-250). T-CSI has four simple vectors: tdp12_ph2_bs_code<x> tdp12_ph3_bs_code<x> tdp13_ph3_cause_value<x> tdp14_ph3_cause_value<x>

For more information on vectors see Vectors in Oracle on page A-248. Field descriptions and validations are given in T-CSI (Terminating CSI) on page 2-204.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-312 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

.
Table A-58 Table SUB_TCSI field details (3 pages) Column Name imsi active provide_location_info page_for_cell_id provide_subscriber _state provide_current _location suppress_tcsi unspgmsc tdp12_ph1_prov tdp12_ph1_scf_name tdp12_ph1_service _key tdp12_ph1_scf_unavail tdp12_ph1_send_cch tdp12_ph2_prov tdp12_ph2_scf_name tdp12_ph2_service _key tdp12_ph2_scf_unavail tdp12_ph2_bs_code _cri1 tdp12_ph2_bs_code _cri2 tdp12_ph2_bs_code _cri3 Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) Constraints not null not null not null not null not null Example 1 456231234567890 TRUE TRUE TRUE TRUE Example 2 234109920024844 TRUE FALSE FALSE TRUE

varcahr2(5)

not null

TRUE

FALSE

varchar2(5) varchar2(8) varchar2(5) varchar2(20) number(10) not null

null CONTINUE FALSE null null

HC CONTINUE FALSE null null

varchar2(8) varchar2(5) varchar2(5) varchar2(20) number(10) not null

null null TRUE MYSCF1 45111111232

null null FALSE null null

varchar2(8) varchar2(8)

CONTINUE TPHNY

null null

varchar2(8)

FAX

null

varchar2(8)

CDS9600

null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-58 Table SUB_TCSI field details (3 pages) Column Name tdp12_ph2_bs_code _cri4 tdp12_ph2_bs_code _cri5 tdp12_ph3_prov tdp12_ph3_scf_name tdp12_ph3_service _key tdp12_ph3_scf_unavail tdp12_ph3_bs_code _cri1 tdp12_ph3_bs_code _cri2 tdp12_ph3_bs_code _cri3 tdp12_ph3_bs_code _cri4 tdp12_ph3_bs_code _cri5 tdp13_ph3_prov tdp13_ph3_scf_name tdp13_ph3_service _key tdp13_ph3_scf_unavail tdp13_ph3_cause _value_cri1 tdp13_ph3_cause _value_cri2 tdp13_ph3_cause _value_cri3 Oracle Type varchar2(8) Constraints

Appendix A: Oracle implementation A-313 Copyright 19962005 Nortel

Example 1 null

Example 2 null

varchar2(8)

null

null

varchar2(5) varchar2(20) number(10)

not null

FALSE null null

TRUE MYSCF8 122231112

varchar2(8) varchar2(8)

null null

CONTINUE null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(8)

null

null

varchar2(5) varchar2(20) number(10)

not null

FALSE null null

TRUE MYSCF8 567567567

varchar2(8) number(3)

null null

RELEASE 100

number(3)

null

55

number(3)

null

null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-314 Appendix A: Oracle implementation Nortel Confidential Table A-58 Table SUB_TCSI field details (3 pages) Column Name tdp13_ph3_cause _value_cri4 tdp13_ph3_cause _value_cri5 tdp14_ph3_prov tdp14_ph3_scf_name tdp14_ph3_service _key tdp14_ph3_scf_unavail tdp14_ph3_cause _value_cri1 tdp14_ph3_cause _value_cri2 tdp14_ph3_cause _value_cri3 tdp14_ph3_cause _value_cri4 tdp14_ph3_cause _value_cri5 Oracle Type number(3) Constraints Example 1 null

Copyright

19962005 Nortel

Example 2 null

number(3)

null

null

varchar2(5) varchar2(20) number(10)

not null

FALSE null null

TRUE MYSCF8 1551553

varchar2(8) number(3)

null null

RELEASE null

number(3)

null

null

number(3)

null

null

number(3)

null

null

number(3)

null

null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-315 Copyright 19962005 Nortel

Table SUB_USSD_CSI
This table stores USSD-CSI data. A row in this table indicates that the subscriber has USSD-CSI provisioned. General table information is given in Table A-59.
Table A-59 Table SUB_USSD_CSI information Number of Columns Rows per Subscriber 11 Zero or One One row if USSD-CSI is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_USSD_CSI are given in Table A-60 on page A-316, along with example values. USSD-CSI has one simple vector, id<x> (for more information on vectors see Vectors in Oracle on page A-248). The ids are datafilled in numerical order, as indicated in the examples. Field descriptions and validations are given in USSD-CSI (Unstructured Supplementary Service Data CSI) on page 2-210.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-316 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

.
Table A-60 Table SUB_USSD_CSI field details Column Name imsi id1 id2 id3 id4 id5 id6 id7 id8 id9 id10 Oracle Type varchar2(15) varchar2(10) varchar2(10) varchar2(10) varchar2(10) varchar2(10) varchar2(10) varchar2(10) varchar2(10) varchar2(10) varchar2(10) Constraints not null not null Example 1 456231234567890 MYID1 MYIDZ MYIDA MYID99 null null null null null null Example 2 234109920024844 MYIDB MYIDC null null null null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-317 Copyright 19962005 Nortel

Table SUB_CLIN
This table stores CLIN data. A row in this table indicates that the subscriber has CLIN provisioned. General table information is given in Table A-61.
Table A-61 Table SUB_CLIN information Number of Columns Rows per Subscriber 2 Zero or One One row if CLIN is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys

Indexes Also See Table(s)

Field details for SUB_CLIN are given in Table A-62, along with example values. Field descriptions and validations are given in CLIN (Calling Line Identification Replacement Number) on page 2-230..
Table A-62 Table SUB_CLIN field details Column Name imsi cli Oracle Type varchar2(15) varchar2(15) Constraints not null not null Example 1 456231234567890 61123666777 Example 2 234109920024844 44757123123

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-318 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_EA
This table stores EA data. A row in this table indicates that the subscriber has EA provisioned. General table information is given in Table A-63.
Table A-63 Table SUB_EA information Number of Columns Rows per Subscriber 2 Zero or One One row if EA is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys

Indexes Also See Table(s)

Field details for SUB_EA are given in Table A-64, along with example values. Field descriptions and validations are given in EA (Equal Access) on page 2-231.
Table A-64 Table SUB_EA field details Column Name imsi pic Oracle Type varchar2(15) varchar2(4) Constraints not null not null Example 1 456231234567890 1234 Example 2 234109920024844 8888

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-319 Copyright 19962005 Nortel

Table SUB_GPRS_PROV
This table stores GPRS provisioning indications. A row in this table indicates that the subscriber has GPRS provisioned. General table information is given in Table A-65. GPRS datafill (i.e. PDP Conext information) is stored separately in table SUB_GPRS_PDPS -- see Table SUB_GPRS_PDPS on page A-320.
Table A-65 Table SUB_GPRS_PROV information Number of Columns Rows per Subscriber 1 Zero or One One row if GPRS is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI

Primary Key Foreign Keys

Indexes Also See Table(s)

sub_gprs_pdps

Field details for SUB_GPRS_PROV are given in Table A-66.


Table A-66 Table SUB_GPRS_PROV field details Column Name imsi Oracle Type varchar2(15) Constraints not null Example 1 456231234567890 Example 2 234109920024844

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-320 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_GPRS_PDPS
This table stores GPRS PDP context data. One row is datafilled per PDP context for the subscriber. Note that GPRS provisioning indications are stored in table SUB_GPRS_PROV (see Table SUB_GPRS_PROV on page A-319). General table information is given in Table A-67.
Table A-67 Table SUB_GPRS_PDPS information Number of Columns Rows per Subscriber 4 Zero to twenty One row per PDP Context IMSI+CONTEXT_ID IMSI to table sub_auth, column IMSI IMSI+CONTEXT_ID sub_gprs_prov

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_GPRS_PDPS are given in Table A-68, along with example values (for a particular row). GPRS has twenty sets, each set being context_id information. Field descriptions and validations are given in GPRS (General Packet Radio Service) on page 2-223.
Table A-68 Table SUB_GPRS_PDPS field details Column Name imsi context_id name static_address Oracle Type varchar2(15) number(2) varchar2(16) varchar2(63) Constraints not null not null not null Example 1 456231234567890 1 MYPDP1 null Example 2 234109920024844 20 MYPDP99 123.34.55.1

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-321 Copyright 19962005 Nortel

Table SUB_LCS_CALL_RELATED
This table stores LCS Call Related class data. A row in this table indicates that the subscriber has LCS Call Related class provisioned. General table information is given in Table A-69, including the several tables that LCS datafill is spread across.
Table A-69 Table SUB_LCS_CALL_RELATED information Number of Columns Rows per Subscriber 43 Zero or One One row if LCS Call Related is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI

Primary Key Foreign Keys Indexes Also See Table(s)

sub_lcs_universal sub_lcs_call_unrelated sub_lcs_plmn_operator sub_lcs_gmlcs sub_lcs_mobile_originating

Field details for SUB_LCS_CALL_RELATED are given in Table A-70 on page A-322, along with example values. LCS Call Related has two simple vectors, external_client<x> and external_client_ex<x>, the latter being the so-called extended clients vector. For more information on vectors see Vectors in Oracle on page A-248. Field descriptions and validations are given in LCS Call Related on page 2-214.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-322 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-70 Table SUB_LCS_CALL_RELATED field details (2 pages) Column Name imsi active notification_to_user Oracle Type varchar2(15) varchar2(5) varchar2(30) Constraints not null not null not null Example 1 456231234567890 TRUE LOC_NOT _ALLOW CLIENT8 CLIENT7 CLIENT34 CLIENT10 CLIENT11 CLIENT12 CLIENT16 CLIENTAA CLIENT56 CLIENT22 CLIENT17 CLIENT16 CLIENT3 null null null null null null null Example 2 234109920024844 FALSE LOC_ALLOW_WITH _NOTIF CLIENT45 CLIENT12 null null null null null null null null null null null null null null null null null null

external_client1 external_client2 external_client3 external_client4 external_client5 external_client_ex1 external_client_ex2 external_client_ex3 external_client_ex4 external_client_ex5 external_client_ex6 external_client_ex7 external_client_ex8 external_client_ex9 external_client_ex10 external_client_ex11 external_client_ex12 external_client_ex13 external_client_ex14 external_client_ex15

varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-323 Copyright 19962005 Nortel

Table A-70 Table SUB_LCS_CALL_RELATED field details (2 pages) Column Name external_client_ex16 external_client_ex17 external_client_ex18 external_client_ex19 external_client_ex20 external_client_ex21 external_client_ex22 external_client_ex23 external_client_ex24 external_client_ex25 external_client_ex26 external_client_ex27 external_client_ex28 external_client_ex29 external_client_ex30 external_client_ex31 external_client_ex32 external_client_ex33 external_client_ex34 external_client_ex35 Oracle Type varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) Constraints Example 1 null null null null null null null null null null null null null null null null null null null null Example 2 null null null null null null null null null null null null null null null null null null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-324 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_LCS_CALL_UNRELATED
This table stores LCS Call Unrelated class data. A row in this table indicates that the subscriber has LCS Call Unrelated class provisioned. General table information is given in Table A-71, including the several tables that LCS datafill is spread across.
Table A-71 Table SUB_LCS_CALL_UNRELATED information Number of Columns Rows per Subscriber 43 Zero or One One row if LCS Call Unrelated is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI

Primary Key Foreign Keys Indexes Also See Table(s)

sub_lcs_universal sub_lcs_call_related sub_lcs_plmn_operator sub_lcs_gmlcs sub_lcs_mobile_originating

Field details for SUB_LCS_CALL_UNRELATED are given in Table A-72 on page A-325, along with example values. LCS Call Unrelated has two simple vectors, external_client<x> and external_client_ex<x>, the latter being the so-called extended names vector. For more information on vectors see Vectors in Oracle on page A-248. Field descriptions and validations are given in LCS Call Unrelated on page 2-216.

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-325 Copyright 19962005 Nortel

Table A-72 Table SUB_LCS_CALL_UNRELATED field details (3 pages) Column Name imsi active notification_to_user Oracle Type varchar2(15) varchar2(5) varchar2(30) Constraints not null not null not null Example 1 456231234567890 TRUE LOC_NOT_ALLOW Example 2 234109920024844 FALSE LOC_ALLOW_WITH_ NOTIF EXTERNALCLIENT45 EXTERNALCLIENT12 null

external_client1 external_client2 external_client3

varchar2(20) varchar2(20) varchar2(20)

EXTERNALCLIENT8 EXTERNALCLIENT7 EXTERNALCLIENT3 4 EXTERNALCLIENT1 0 EXTERNALCLIENT1 1 CLIENT12 CLIENT16 CLIENTAA CLIENT56 CLIENT22 CLIENT17 CLIENT16 CLIENT3 null null null null null null

external_client4

varchar2(20)

null

external_client5

varchar2(20)

null

external_client_ex1 external_client_ex2 external_client_ex3 external_client_ex4 external_client_ex5 external_client_ex6 external_client_ex7 external_client_ex8 external_client_ex9 external_client_ex10 external_client_ex11 external_client_ex12 external_client_ex13 external_client_ex14

varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8)

null null null null null null null null null null null null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-326 Appendix A: Oracle implementation Nortel Confidential Table A-72 Table SUB_LCS_CALL_UNRELATED field details (3 pages) Column Name external_client_ex15 external_client_ex16 external_client_ex17 external_client_ex18 external_client_ex19 external_client_ex20 external_client_ex21 external_client_ex22 external_client_ex23 external_client_ex24 external_client_ex25 external_client_ex26 external_client_ex27 external_client_ex28 external_client_ex29 external_client_ex30 external_client_ex31 external_client_ex32 external_client_ex33 external_client_ex34 external_client_ex35 Oracle Type varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) varchar2(8) Constraints Example 1 null null null null null null null null null null null null null null null null null null null null null

Copyright

19962005 Nortel

Example 2 null null null null null null null null null null null null null null null null null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-327 Copyright 19962005 Nortel

Table SUB_LCS_GMLCS
This table stores LCS GMLC data. A row in this table indicates that the subscriber has LCS GMLCs provisioned. General table information is given in Table A-73, including the several tables that LCS datafill is spread across.
Table A-73 Table SUB_LCS_GMLCS information Number of Columns Rows per Subscriber 6 Zero or One One row if one or more GLMCs is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI

Primary Key Foreign Keys

Indexes Also See Table(s)

sub_lcs_universal sub_lcs_call_related sub_lcs_call_unrelated sub_lcs_plmn_operator sub_lcs_mobile_originating

Field details for SUB_LCS_GMLCS are given in Table A-74 on page A-328, along with example values. Field descriptions and validations are given in LCS GMLCs on page 2-218.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-328 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-74 Table SUB_LCS_GMLCS field details Column Name imsi gmlc1 gmlc2 gmlc3 gmlc4 gmlc5 Oracle Type varchar2(15) varchar2(20) varchar2(20) varchar2(20) varchar2(20) varchar2(20) Constraints not null not null Example 1 456231234567890 MYGMLC1 MYGMLC5 MYGMLC9 MYGMLC3 null Example 2 234109920024844 MYGMLC9 null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-329 Copyright 19962005 Nortel

Table SUB_LCS_MOBILE_ORIGINATING
This table stores all LCS Mobile Originating data, i.e. all three classes, Basic Self Location, Autonomous Self Location and Transfer to Third Party. A row in this table indicates that the subscriber has at least one mobile originating class provisioned. General table information is given in Table A-75, including the several tables that LCS datafill is spread across.
Table A-75 Table SUB_LCS_MOBILE_ORIGINATING information Number of Columns Rows per Subscriber 7 Zero or one One row if one or more LCS Mobile Originating classes are provisioned IMSI IMSI to table sub_auth, column IMSI IMSI

Primary Key Foreign Keys Indexes Also See Table(s)

sub_lcs_universal sub_lcs_call_related sub_lcs_call_unrelated sub_lcs_plmn_operator sub_lcs_gmlcs

Field details for SUB_LCS_MOBILE_ORIGINATING are given in Table A76 on page A-330, along with example values. Field descriptions and validations are given in LCS Basic Self Location on page 2-213 (basic self location), LCS Autonomous Self Location on page 2-212 (autonomous self location) and LCS Transfer to Third Party on page 2-221 (transfer to third party).

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-330 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table A-76 Table SUB_LCS_MOBILE_ORIGINATING field details Column Name imsi basic_self_loc_prov basic_self_loc_act autonomous_self_loc _prov autonomous_self_loc _act transfer_3rd_party _prov transfer_3rd_party_act Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) not null Constraints not null not null Example 1 456231234567890 TRUE TRUE TRUE Example 2 234109920024844 FALSE null FALSE

varchar2(5)

FALSE

null

varchar2(5)

not null

TRUE

TRUE

varchar2(5)

TRUE

TRUE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-331 Copyright 19962005 Nortel

Table SUB_LCS_PLMN_OPERATOR
This table stores LCS PLMN Operator class data. A row in this table indicates that the subscriber has LCS PLMN Operator class provisioned. General table information is given in Table A-77, including the several tables that LCS datafill is spread across.
Table A-77 Table SUB_LCS_PLMN_OPERATOR information Number of Columns Rows per Subscriber 7 Zero or One One row if LCS PLMN Operator is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI

Primary Key Foreign Keys Indexes Also See Table(s)

sub_lcs_universal sub_lcs_call_related sub_lcs_call_unrelated sub_lcs_gmlcs sub_lcs_mobile_originating

Field details for SUB_LCS_PLMN_OPERATOR are given in Table A-78 on page A-332, along with example values. Field descriptions and validations are given in LCS PLMN Operator on page 2-219.

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-332 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

.
Table A-78 Table SUB_LCS_PLMN_OPERATOR field details Column Name imsi active broadcast omh omv anonymous target_ms Oracle Type varchar2(15) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) varchar2(5) Constraints not null not null not null not null not null not null not null Example 1 456231234567890 TRUE TRUE TRUE FALSE TRUE FALSE Example 2 234109920024844 FALSE FALSE FALSE TRUE FALSE TRUE

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-333 Copyright 19962005 Nortel

Table SUB_LCS_UNIVERSAL
This table stores LCS Universal class data. A row in this table indicates that the subscriber has LCS Universal class provisioned. General table information is given in Table A-79, including the several tables that LCS datafill is spread across.
Table A-79 Table SUB_LCS_UNIVERSAL information Number of Columns Rows per Subscriber 2 Zero or One One row if LCS Universal is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI

Primary Key Foreign Keys Indexes Also See Table(s)

sub_lcs_call_related sub_lcs_call_unrelated sub_lcs_plmn_operator sub_lcs_gmlcs sub_lcs_mobile_originating

Field details for SUB_LCS_UNIVERSAL are given in Table A-80, along with example values. Field descriptions and validations are given in LCS Universal on page 2-222.
Table A-80 Table SUB_LCS_UNIVERSAL field details Column Name imsi active Oracle Type varchar2(15) varchar2(5) Constraints not null not null Example 1 456231234567890 TRUE Example 2 234109920024844 FALSE

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-334 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_VBS
This table stores VBS data. A row in this table indicates that the subscriber has VBS provisioned. General table information is given in Table A-81.
Table A-81 Table SUB_VBS information Number of Columns Rows per Subscriber 102 Zero or One One row if VBS is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys

Indexes Also See Table(s)

Field details for SUB_VBS are given in Table A-82, along with example values. VBS has complex vector of groups, composed of group<x>_id + group<x>_orig_ent. For more information on vectors see Vectors in Oracle on page A-248. Field descriptions and validations are given in VBS (Voice Broadcast Service) on page 2-105.
Table A-82 Table SUB_VBS field details (5 pages) Column Name imsi functions_outside _hplmn group1_id group1_orig_ent group2_id group2_orig_ent group3_id group3_orig_ent group4_id group4_orig_ent Oracle Type varchar2(15) varchar2(5) Constraints not null Example 1 456231234567890 TRUE Example 2 234109920024844 FALSE

varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5)

334 TRUE 783 TRUE 008 TRUE 055 TRUE

567 TRUE 522 TRUE null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-82 Table SUB_VBS field details (5 pages) Column Name group5_id group5_orig_ent group6_id group6_orig_ent group7_id group7_orig_ent group8_id group8_orig_ent group9_id group9_orig_ent group10_id group10_orig_ent group11_id group11_orig_ent group12_id group12_orig_ent group13_id group13_orig_ent group14_id group14_orig_ent group15_id group15_orig_ent group16_id group16_orig_ent group17_id Oracle Type varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) Constraints

Appendix A: Oracle implementation A-335 Copyright 19962005 Nortel

Example 1 100 TRUE 123 TRUE 766 TRUE 523 TRUE 567 TRUE null null null null null null null null null null null null null null null

Example 2 null null null null null null null null null null null null null null null null null null null null null null null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-336 Appendix A: Oracle implementation Nortel Confidential Table A-82 Table SUB_VBS field details (5 pages) Column Name group17_orig_ent group18_id group18_orig_ent group19_id group19_orig_ent group20_id group20_orig_ent group21_id group21_orig_ent group22_id group22_orig_ent group23_id group23_orig_ent group24_id group24_orig_ent group25_id group25_orig_ent group26_id group26_orig_ent group27_id group27_orig_ent group28_id group28_orig_ent group29_id group29_orig_ent Oracle Type varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) Constraints Example 1 null null null null null null null null null null null null null null null null null null null null null null null null null

Copyright

19962005 Nortel

Example 2 null null null null null null null null null null null null null null null null null null null null null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-82 Table SUB_VBS field details (5 pages) Column Name group30_id group30_orig_ent group31_id group31_orig_ent group32_id group32_orig_ent group33_id group33_orig_ent group34_id group34_orig_ent group35_id group35_orig_ent group36_id group36_orig_ent group37_id group37_orig_ent group38_id group38_orig_ent group39_id group39_orig_ent group40_id group40_orig_ent group41_id group41_orig_ent group42_id Oracle Type varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) Constraints

Appendix A: Oracle implementation A-337 Copyright 19962005 Nortel

Example 1 null null null null null null null null null null null null null null null null null null null null null null null null null

Example 2 null null null null null null null null null null null null null null null null null null null null null null null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-338 Appendix A: Oracle implementation Nortel Confidential Table A-82 Table SUB_VBS field details (5 pages) Column Name group42_orig_ent group43_id group43_orig_ent group44_id group44_orig_ent group45_id group45_orig_ent group46_id group46_orig_ent group47_id group47_orig_ent group48_id group48_orig_ent group49_id group49_orig_ent group50_id group50_orig_ent Oracle Type varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) varchar2(3) varchar2(5) Constraints Example 1 null null null null null null null null null null null null null null null null null

Copyright

19962005 Nortel

Example 2 null null null null null null null null null null null null null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-339 Copyright 19962005 Nortel

Table SUB_VGCS
This table stores VGCS data. A row in this table indicates that the subscriber has VGCS provisioned. General table information is given in Table A-83.
Table A-83 Table SUB_VGCS information Number of Columns Rows per Subscriber 52 Zero or One One row if VGCS is provisioned IMSI IMSI to table sub_auth, column IMSI IMSI None

Primary Key Foreign Keys Indexes Also See Table(s)

Field details for SUB_VGCS are given in Table A-84, along with example values. VBS has simple vector of group<x>_id. For more information on vectors see Vectors in Oracle on page A-248. Field descriptions and validations are given in VGCS (Voice Group Call Service) on page 2-106.
Table A-84 Table SUB_VGCS field details (3 pages) Column Name imsi functions_outside _hplmn group1_id group2_id group3_id group4_id group5_id group6_id group7_id group8_id group9_id Oracle Type varchar2(15) varchar2(5) Constraints not null Example 1 456231234567890 TRUE Example 2 234109920024844 FALSE

varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3)

456 123 606 666 999 111 784 334 232

677 233 110 099 875 null null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-340 Appendix A: Oracle implementation Nortel Confidential Table A-84 Table SUB_VGCS field details (3 pages) Column Name group10_id group11_id group12_id group13_id group14_id group15_id group16_id group17_id group18_id group19_id group20_id group21_id group22_id group23_id group24_id group25_id group26_id group27_id group28_id group29_id group30_id group31_id group32_id group33_id group34_id Oracle Type varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) Constraints Example 1 null null null null null null null null null null null null null null null null null null null null null null null null null

Copyright

19962005 Nortel

Example 2 null null null null null null null null null null null null null null null null null null null null null null null null null

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential Table A-84 Table SUB_VGCS field details (3 pages) Column Name group35_id group36_id group37_id group38_id group39_id group40_id group41_id group42_id group43_id group44_id group45_id group46_id group47_id group48_id group49_id group50_id Oracle Type varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) varchar2(3) Constraints

Appendix A: Oracle implementation A-341 Copyright 19962005 Nortel

Example 1 null null null null null null null null null null null null null null null null

Example 2 null null null null null null null null null null null null null null null null

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-342 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SUB_SIMR
This table stores SIMR data. A row in this table indicates that the subscriber is involved in a SIMR relationship (note that the subscribers current IMSI is not the key in this table). General table information is given in Table A-85.
Table A-85 Table SUB_SIMR information Number of Columns Rows per Subscriber 5 Zero or One One row if the subscriber is in a SIMR relationship NEW_IMSI NEW_IMSI to table sub_auth, column IMSI NEW_IMSI OLD_IMSI Also See Table(s) None

Primary Key Foreign Keys

Indexes

Field details for SUB_SIMR are given in Table A-86, along with example values. The current subscriber profile is indicated by the old_imsi field. Field descriptions and validations are given in SIMR (SIM Replacement) on page 2-235.
Table A-86 Table SUB_SIMR field details Column Name new_imsi old_imsi simr_option invocation_time activation_time Oracle Type varchar2(15) varchar2(15) varchar2(5) varchar2(17) varchar2(17) Constraints not null not null not null not null Example 1 456231234567890 456231231231234 FIXED 15-Mar-2004 12:00 null Example 2 234109920024844 231109950005000 USER 15-Mar-2004 15:00 01-Feb-2004 09:00

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-343 Copyright 19962005 Nortel

Routing Schema
The routing schema is composed of three tables, listed in Table A-87. Note that this schema is evolved from the GSM17 Oracle schema. Table HLR denotes the HLR Cores in the system. Table IMSIS and MSISDNS are master copies of the data stored in the SLR node.
Table A-87 Routing Schema Tables Table Name New/ Changed/ Deleted Unchanged Unchanged Unchanged Unchanged Description See page

hlrs imsis msisdns simr

stores all HLR Core IDs stores IMSIs present in SLR database stores MSISDNs present in SLR database stores deadline times for SIMR relationships

Table HLRS This table stores the HLR Cores present in the HLR system. General table information is given in Table A-88.
Table A-88 Table HLRS information Number of Columns Rows per Subscriber 2 Not Applicable (not a subscriber data table) ID None ID None

Primary Key Foreign Keys Indexes Also See Table(s)

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-344 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Field details for table HLRS are given in Table A-89, along with descriptions.
Table A-89 Table HLRS field details Column Name id name Oracle Type varchar2(10) varchar2(50) Constraints not null not null Syntax 10 hex digits 1 - 50 characters Description the HLR Core ID a descriptive name for the HLR Core

Table IMSIS This table stores the master copies of the IMSIs which are present in the SLR database. General table information is given in Table A-90.
Table A-90 Table IMSIS information Number of Columns Rows per Subscriber Primary Key Foreign Keys Indexes Also See Table(s) 2 Zero or One IMSI HLR_ID to table hlrs, column ID IMSI hlrs

Field details for table IMSIS are given in Table A-91, along with descriptions.
Table A-91 Table IMSIS field details Column Name imsi Oracle Type varchar2(15) Constraints not null Syntax 6 - 15 digits Description International Mobile Subscriber Identities present in SLR database HLR ID for this subscriber

hlr_id

varchar2(10)

not null

10 hex digits

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Appendix A: Oracle implementation A-345 Copyright 19962005 Nortel

Table MSISDNS This table stores the master copies of the MSISDNs which are present in the SLR database. General table information is given in Table A-92.
Table A-92 Table MSISDNS information Number of Columns Rows per Subscriber Primary Key Foreign Keys Indexes 2 zero to 19* MSISDN IMSI to table imsis, column IMSI IMSI MSISDN Also See Table(s)

imsis

* theoretical maximum and very unlikely in reality; a typical subscriber would have zero to three rows, depending on whether remastered and whether network active Field details for table MSISDNS are given in Table A-93, along with descriptions.
Table A-93 Table MSISDNS field details Column Name msisdn Oracle Type varchar2(15) Constraints not null Syntax 3 - 15 digits Description Mobile Subscriber ISDN number present in SLR database International Mobile Subscriber Identity (IMSI) which the MSISDN relates to

imsi

varchar2(15)

not null

6 - 15 digits

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

A-346 Appendix A: Oracle implementation Nortel Confidential

Copyright

19962005 Nortel

Table SIMR This table stores deadlines for SIMR relationships, and is redundant once all subscribers have been remastered. Note that the full set of SIMR data is stored in table SUB_SIMR in the subscriber schema (see Table SUB_SIMR on page A-342). General table information is given in Table A94.
Table A-94 Table SIMR information Number of Columns Rows per Subscriber Primary Key Foreign Keys 3 Zero or One NEW_IMSI NEW_IMSI to table imsis, column IMSI OLD_IMSI to table imsis, column IMSI Indexes NEW_IMSI OLD_IMSI Also See Table(s) None

Field details for table SIMR are given in Table A-95, along with descriptions.
Table A-95 Table SIMR field details Column Name Oracle Type Constraint s not null not null Syntax Description

new_imsi old_imsi

varchar2(15) varchar2(15)

6 - 15 digits 6 - 15 digits

new IMSI for subscriber the subscribers old IMSI, the one to be replaced the time at which the SIMR swap is mandatory

deadline

date

not null

date (nearest hour)

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Copyright

19962005 Nortel

B-347

Glossary of terms
This section expands the names of acronym/shortened dataitems and service names.

A
ACC Accounting Codes ACRJ Anonymous Call Rejection ALTSPCDA Alternate Speech / CDA Data ALTSPCDS Alternate Speech / CDS Data ALTSPFAX Alternate Speech / Fax Group 3 AOCC Advice of Charge Charging AOCI Advice of Charge Information AUXSPCH Auxiliary Speech basic service group AUXTPHNY Auxiliary Telephony

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

B-348 Glossary of terms Nortel Confidential

Copyright

19962005 Nortel

B
BAECT Barring of All Explicit Call Transfer BAIC Barring of All Incoming Calls BAOC Barring of All Outgoing Calls BAOCRoam Barring of (All) Outgoing Calls when Roaming outside HPLMN country BCHDECT Barring of Chargeable Explicit Call Transfer BCI Bearer Capability Index BDBCECT Barring of Doubly Chargeable Explicit Call Transfer BICCTRL Control of Barring Incoming Calls BICRoam Barring of Incoming Calls when Roaming BINTECT Barring of International Explicit Call Transfer BOCCTRL Control of Barring Outgoing Calls BOIC Barring of Outgoing International Calls BOIC exHCBarring of Outgoing International Calls except to HPLMN Country BS Basic Service (note that BS Codes also encompass basic service groups) BSG Basic Service Group
411-2831-332 Preliminary 01.02 March 2005

Nortel Confidential

Glossary of terms B-349 Copyright 19962005 Nortel

C
CAMEL Customised Applications for Mobile Enhanced Logic CC Country Code (the MSISDN contains a CC) CCH CAMEL Capability Handler CDA Circuit Duplex Asynchronous Data services or basic service group CDAGBS Circuit Duplex Asynchronous Data General Bearer Service CDS Circuit Duplex Synchronous Data services or basic service group CDSGBS Circuit Duplex Synchronous Data General Bearer Service CFB Call Forward when Busy CFNRc Call Forward when Not Reachable CFNRy Call Forward when no Reply CFU Call Forward Unconditionally CLIN Calling Line Identification replacement Number CLIP Calling Line ID Presentation CLIR Calling Line ID Restriction

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

B-350 Glossary of terms Nortel Confidential

Copyright

19962005 Nortel

CNAM Calling Name Delivery COLP Connected Line ID Presentation COLR Connected Line ID Restriction COR Class Of Registration COS Class Of Service CUG Closed User Groups CW Call Waiting

D
DCF Default Call Forwarding D-CSI Dialled CAMEL Subscription Information DN Destination Number DNC Destination Number Criteria DP Detection Point, also known as a Trigger Detection Point (TDP) on the HLR

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Glossary of terms B-351 Copyright 19962005 Nortel

E
EA Equal Access ECT Explicit Call Transfer EMLPP Enhanced Multi Level Precedence & Pre-emption EXT Extension Services

F
FA Functional Addressing (also known as FM) FAX Facsimile basic service group FAX3 Facsimile group 3 FM Follow Me (also known as FA) FTN Forward To Number

G
GMLC Gateway Mobile Location Center GPRS General Packet Radio Service GPRS-CSI General Packet Radio Service CAMEL Subscription Information

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

B-352 Glossary of terms Nortel Confidential

Copyright

19962005 Nortel

gsmSCF GSM Service Control Function

H
HOLD Call Hold HOTBILL Hot Billing HST Home Subscriber Trace

I
ICA Inter-CUG Accessibility IMSI International Mobile Subscriber Identity IN Intelligent Network INORIG IN index for Originating calls INTERM IN index for Terminating calls

L
LCO Local Calls Only LMU Location Measurement Unit

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Glossary of terms B-353 Copyright 19962005 Nortel

M
MCC Mobile Country Code (part of IMSI) M-CSI Mobility management CAMEL Subscription Information MCT Malicious Call Trace MNC Mobile Network Code (part of IMSI) MPTY Multi-Party MSIN Mobile Subscriber Identification Number (part of IMSI) MSISDN Mobile Subscriber ISDN

N
NAM Network Access Mode NCOS Network Class Of Service NCP Notify Calling Party NDC National Destination Code (part of MSISDN) NFP Notify Forwarding Party NOA Nature Of Address

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

B-354 Glossary of terms Nortel Confidential

Copyright

19962005 Nortel

NPI Number Plan Indicator

O
O-CSI Originating CAMEL Subscription Information ODB Operator Determined Barring OMC DestinationOperator Maintenance Center Destination OMHO&M LCS client in the HPLMN OMVO&M LCS client in the VPLMN OPC Operator variant algorithm Configuration

P
PDP Packet Data Protocol PIC Primary Interexchange Carrier

Q
QSCFWIHP Query SCF When In HPLMN

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Glossary of terms B-355 Copyright 19962005 Nortel

S
SCF Service Control Function, strictly known as a gsmSCF SIMR SIM Replacement SMMO Short Message Mobile Originating SMMT Short Message Mobile Terminating SMS Short Message Service basic service group SMS-CSI Short Message Service CAMEL Subscription Information SN Subscriber Number (part of MSISDN) SOAPROV Suppression Of Announcements Provisioning SPCH Speech basic service group SPCHCDA Speech followed by CDA Data SPCHCDS Speech followed by CDS Data SS-CSI Supplementary Service CAMEL Subscription Information

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

B-356 Glossary of terms Nortel Confidential

Copyright

19962005 Nortel

T
T-CSI Terminating CAMEL Subscription Information TDP Trigger Detection Point, also known as a Detection Point (DP) on the HLR TPHNY Telephony

U
UNSPGMSC Unsupported GMSC behaviour UNSPNODE Unsupported Node behaviour UNSPSGSN Unsupported SGSN behaviour UNSPVMSC Unsupported VMSC behaviour USSD-CSI Unstructured Supplementary Service Data CAMEL Subscription Information UUS1 User to User Signalling stage 1

V
VBS Voice Broadcast Service VGCS Voice Group Call Service VGS Voice Group Service basic service group

411-2831-332

Preliminary

01.02

March 2005

Nortel Confidential

Glossary of terms B-357 Copyright 19962005 Nortel

W
WPS Wireless Priority Service

GSM NSS/UMTS CCN

HLR200 Subscriber Data Model GSM18/UMTS04

B-358 Glossary of terms Nortel Confidential

Copyright

19962005 Nortel

411-2831-332

Preliminary

01.02

March 2005

test

Fam ily Product Manual Contacts Copyright Confidentiality Legal

GSM NSS/UMTS CCN

HLR200
Subscriber Data Model
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-5669 or send e-mail from the Nortel Customer Training & Documentation World Wide Web site at http://www.nortel.com/td Copyright 19962005 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. * Nortel, the Nortel logo, the Globemark, and Unified Networks are trademarks of Nortel. 3rd Party Trademark A-N Additional 3rd party trademark A-N 3rd Party Trademark O-Z Additional 3rd party trademark O-Z Trademarks are acknowledged with an asterisk (*) at their first appearance in the document. Document number: 411-2831-332 Product release: GSM18/UMTS04 Document version: Preliminary 01.02 Date: March 2005 Printed in the United States of America/Canada