ANSI-41 Implementations in C#.NET

Scan QR Code in C#.NET ANSI-41 Implementations

18:

As a centralized node for subscriber signaling traffic, the HLR is able to control certain features for a subscriber on a networkwide basis All feature control requests from throughout the network are directed to the specific HLR serving a particular subscriber A wireless subscriber will be served by only one HLR The HLR is essentially a transaction processor handling network queries and operations It is administered and controlled by the service provider with whom the subscribers have a service agreement The service provider can retain control over the following functionality:

Subscriber validation Subscriber features to maintain a uniform subscriber interface Signaling network access Delivery of incoming calls to a mobile subscriber regardless of location Subscriber roaming Strategic market information, such as subscriber activity and number of database accesses Fraud protection, investigation, and subscriber shutdown (based on authentication) Service offerings

The HLR is the most important network element in the wireless telecommunications network It can be implemented as a standalone function, such as a service control point (SCP) application, or it can be implemented as an integrated function within an MSC complex

The HLR holds all subscriber service profile records, which define the features that have been authorized for each subscriber It is responsible for validating a subscriber to allow it to incur charges while roaming on another system It also tracks the location of all its subscribers so that it can direct incoming calls to the MSC currently serving the subscriber The HLR application is able to perform these functions because of the information it stores in its databases (see Figure 189) The HLR supports the following database tables:

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website

Part 3:

The HLR supports other tables, but these include the most necessary information for the HLR application functionality

Figure 189 The HLR application has access to a large database The interface to the database is proprietary

Application Layer ANSI-41 Mobile Application Part (MAP) subscriber database Transaction Capabilities Application Part (TCAP)

Subscriber Service Profile Record Table The subscriber service profile record table is the HLR database containing the records established for each subscriber This table typically includes the following subscriber information: 1 Identification data: (a) MIN (b) ESN (c) MDN (if applicable) 2 Call profile data: (a) Credit status (eg, paid-up, delinquent account)

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website

18:

5 6

(b) Call origination indicator (eg, local calls only, single NPA-NXXXXXX only) (c) Call restriction digits (eg, by NPA only, NPA-NXX only, or NPA-NXX-XXXX) (d) Call termination restriction (eg, none, all) (e) Preferred interexchange carrier Qualification data (closely related to the authentication procedures) (a) Authorization period (b) Call history count (c) Carrier-requested temporary disconnect (eg, for delinquent accounts) (d) Subscriber-requested temporary disconnect (eg, for vacation) Feature activations (for each feature available) (a) Feature authorized/activated (b) Feature states (c) Feature timers Feature registrations (one example) (a) Call forwarding forward-to-number Location and activity status (a) VLR identification information (eg, MSCID, PC_SSN) (b) Registration status (ie, active, inactive) Fraud protection (eg, subscriber behavior information)

Subscriber Feature Option Table The subscriber feature option table maintains the configurations required for certain features to operate This database information includes:

Allowed feature code values Number of subscriber modifications Feature timer values (eg, message waiting notification) Short-message service options

Served MIN Table The served MIN table defines MIN ranges assigned to a particular HLR The MINs are defined in terms of office codes, thousands groups, or hundreds groups If numbers are allocated individually, a subscriber record is usually created for each number in the list and marked as an unas-

Downloaded from Digital Engineering Library @ McGraw-Hill (wwwdigitalengineeringlibrarycom) Copyright 2004 The McGraw-Hill Companies All rights reserved Any use is subject to the Terms of Use as given at the website