DESCRIPTION

142/190 46-FAD 104 08 Uen E

HLR Redundancy Abstract

The purpose of this document is to describe the function HLR Redundancy from a data transcript point of view.

Contents
1 2 2.1 2.2 2.3 2.4 2.5 3 3.1 3.2 3.3 3.4 3.5 4 4.1 5 Revision Information Description Abbreviation Concerned Nodes General Technical Solution Traffic Cases Data Transcript Impacts General Subfile 10000 - Size Alteration Events (APT) Subfile 13000 - HLR Exchange Properties Subfile 75500 - SCCP Analysis Subfile 81000 - HLR Number Series Analysis Miscellaneous Information Class Reference List <HRsize=2 width="100%" align=center>

1 Revision Information
Revision A B C D E Impacts Prepared New document ERASNI SCCP analysis updated. ERAPEOJ Updated to SS R8.0. No changes. ERARDPN Some technical clarifications made ERASNI Reviewed for CN 1.5 ERAMDEI Date 98-05-12 98-09-21 00-02-29 00-07-12 01-05-29

2 Description
2.1 Abbreviation

DPC HLR LU MGT

Destination Point Code Home Location Register Location Updating Mobile Global Title

MSISDN Mobile Station ISDN MT SCCP SOG SPR SSN STP SUD TT VLR Mobile Terminating Signalling Connection Control Part Service Order Gateway Signalling Point Relay Subsystem Number Signalling Transfer Point Subscriber Data Translation Type Visitor Location Register

2.2 Concerned Nodes

HLR MSC/VLR

2.3 General
The HLR Redundancy makes it possible for a system to have an HLR failure without any traffic interruption in the cellular network. HLR Redundancy provides protection against disaster situations. At the same time, HLR Redundancy will give protection against signalling failure towards a HLR and will also lower the non availability caused by HLR restarts. The HLR redundancy feature is applicable for LU and MT calls. The DT impact for HLR redundancy will only be covered in this document, and not in the I-module part of the DT Infomodel. That's because the two HLRs must have the same configuration, and that's not the case for the network plan that the I-module DT is based upon. The contents of this document (text, figures and DT) as much as possible relate to the network plan in the DT Infomodel.

2.3.1 2.3.1.1

Concepts Primary Subscribers

These subscribers are defined as redundant in the mated HLR. Under normal operation, the network routes the operations related to the subscribers to the HLR where they are defined as primary. 2.3.1.2 Redundant Subscribers

These subscribers are defined in the HLR (command HGNSI) for redundancy purposes and are defined as primary in the mated HLR. If the HLR where the subscribers are defined as primary has a failure, the network routes the operations related to the subscribers to the HLR where they are defined as redundant. 2.3.1.3 Permanent Subscriber Data

Subscriber data that can only be changed by administrative means. That is for example, IMSI, SS provision status and subscriber category. 2.3.1.4 Temporary Subscriber Data

Subscriber data that is or can be changed in the HLR as a consequence of subscriber activities. 2.3.1.5 Signalling Point Relay

This is the last node in the signalling network, performing routing on an SCCP function level for messages towards the HLR. 2.3.2 2.3.2.1 HLR Main States Normal State

The HLR is in normal state when it is connected to the network and knows that its mated HLR is also connected to it. 2.3.2.2 Separate State

The HLR is in separated state when it is connected to the network but does not know the state of the other node. 2.3.2.3 Single State

The HLR is connected to the network and knows that the mated HLR is disconnected from the network. 2.3.2.4 Halted State

The HLR is in Halted State when the operator orders manual disconnection from the network. 2.3.2.5 Single-Manual State

The HLR is in Single-manual State when it has been informed that the mated HLR is in Halted State. 2.3.2.6 Failure state

The HLR is in failure state when it's disconnected from the network after it detects an initial start, or reload has occurred. Also the HLR is in this state when it's recovering after having been disconnected from the network (e.g the C7 links went down).

2.4 Technical Solution

HLR Redundancy allows an HLR failure to be invisible to the cellular network by introducing a mated HLR that performs redundancy functions. If a direct link exists between the HLR nodes it is recommended that "Update Subscriber Data" messages run through it and "Redundancy Control" messages run through the network. If a direct link does not exist " Update Subscriber Data" and "Redundancy Control" messages run through the network. Traffic message information is depending on the HLR state. "Update Subscriber Data" messages are sent towards the mated HLR when subscribers have modified information such as location updating data, password change, SS changes, or when the MS is purged. HLR number and subscriber IMSI number are always included in the message. A unique Translation Type is used to route these update subscriber data messages between the two HLR's. The value is set by an application parameter in block HRMAPTC. Redundance Control operation is used to coordinate redundancy related actions with the mated HLR, also detects faults by keeping track of the state of the mated HLR. HLR number, HLR own state and control message information are always included in the message. The sending interval for these messages depends on an application parameter, but every ten seconds could be a guiding value. The routing is defined in the STP's or in the MSC to address the HLR 1 number, HLR 1 International IMSI series for primary subscribers, and HLR 1 MSISDN number series for primary subscribers to the HLR 1 as primary route and to the HLR 2 as a secondary route. The routing is also defined to address the HLR 2 number, HLR 2 IMSI series for primary subscribers, and HLR 2 MSISDN number series for primary subscribers to the HLR 2 as primary route and to the HLR 1 as secondary route. New subscriptions have to be defined in both HLRs. That's normally done via the SOG. The same applies for the subscriptions in the AUCs.

Figure 1 shows the HLR Redundancy working in normal operation. During normal operation both HLRs share the traffic load, handling their own primary subscribers and keep the information about the redundant subscribers updated from the mated HLR.

Figure 1

HLR Redundancy during normal operation.

The subscribers defined as redundant subscribers in the HLR are also defined as primary subscribers in the mated HLR. If the HLR where the subscribers are defined as primary fails, the network routes the operations related to these subscribers to the HLR where they are defined as redundant. Figure 2 shows how a HLR failure is handled.

Figure 2

HLR Failure

A mated pair consists of two HLR nodes that in normal operation share subscribers and load, in such a way that when one of them fails, the other handles all the traffic normally routed to its mated pair. Both HLR nodes in the pair must have identical functionality and coordinate their actions. The distribution of the traffic to each HLR is performed by the SCCP routing function of the N. 7 network nodes. It must be ensured that messages are routed to the correct HLR node during normal operations, and that support for a secondary alternative routing to the functioning HLR to be used in case of a " SSN prohibited" or "DPC unavailable" exists.

2.5 Traffic Cases

2.5.1 General

Figure 3 is used to explain a location updating procedure in a mobile network where HLR Redundancy is implemented. Both HLR's must have the same functionality and configuration. For this traffic case, integrated AUCs are used. The subscribers defined as primary in HLR1 have to be defined as redundant in HLR2, and vice versa. In this traffic case, the DT impact in HLR1 and in the MSC/VLR is covered. Subscription and SCCP data in HLR2 and in the AUCs also have to be defined.

Figure 3

Location Updating procedure with Redundancy functionality

When a Mobile Station enters a new MSC/VLR service area, it sends a Location Update request message to the MSC/VLR. One of the information elements included in the message is the IMSI number. Since the subscriber isn't registered in the MSC/VLR service area, the VLR has to ask the HLR for subscriber data. That is done using the MGT (more information about this traffic case is found in the "Location Updating traffic case" description). A location updating message is sent from the MSC/VLR to HLR1 (primary) via the SCCP analysis. Example 1 MML Commands

C7GSI:TT=0, NP=7, NA=4, NS=46 70 751, GTRC=5;

Translation Type Numbering Plan Nature Address Number Series Global Title Routing Case, primary leading to HLR1.

Since the subscriber is defined as "primary" in HLR1, the message shall terminate there. If however HLR1 isn't accessible, a secondary routing alternative to HLR2, where the subscriber is defined as redundant also has to be defined. Example 2 MML Commands

C7GCI:GTRC=5, PSP=2-700, PSSN=6,

Global Title Routing Case Primary Signalling Point Primary SSN (For the HLR)

PTERM, SSP=2-200, SSSN=6, STERM;

Primary TERMinating Secondary Signalling Point Secondary SSN (For the HLR) Secondary TERMinating

If instead the subscriber would have been defined as "primary" in HLR2 (another MGT), the message shall primary terminate in that node. Example 3 MML Commands

C7GSI:TT=0, NP=7, NA=4, NS=46 70 761, GTRC=6;

Translation Type Numbering Plan Nature Address Number Series Global Title Routing Case, primary leading to HLR2. Global Title Routing Case Primary Signalling Point Primary SSN (For the HLR) Primary TERMinating Secondary Signalling Point Secondary SSN (For the HLR) Secondary TERMinating

C7GCI:GTRC=6, PSP=2-200, PSSN=6, PTERM, SSP=2-700, SSSN=6, STERM;

The Subsystem Number 224 is defined in the MSC/VLR for the signalling points 2200 and 2-700, already defined in the SCCP network. Example 4 MML Commands

C7NSI:SP=2-200, C7NSI:SP=2-700,

SSN=224; SSN=224;

HLR1 receives the message from the MSC/VLR, and fetches the subscriber data related to the subscriber. A request for triplet generation for the subscriber is sent to the AUC. Example 5 MML Commands

C7GSI:TT=2, NP=6, NA=4, NS=240 01, GTRC=5; C7GCI:GTRC=5, PSP=OWNSP, PSSN=10;

Translation Type Numbering Plan Nature Address Number Serie (IMSI)

Global Title Routing Case Termination of the message in own node Primary SSN (10 for an integrated AUC)

The AUC generates triplets for the particular subscriber and sends them to HLR1. The message is received with TT=187 and SSN=224. For the operation to become possible, the message must terminate in HLR1 with its own address. Example 6 MML Commands

C7GSI:TT=187, NP=1, NA=4, NS=46 70 75701, GTRC=6; C7GCI:GTRC=6, PSP=OWNSP, PSSN=224;

Translation Type Numbering Plan Nature Address HLR1 own address

Global Title Routing Case Termination of the message in own node Primary SSN (224 for redundancy)

The subscriber data together with the triplets generated, are sent towards the MSC/VLR

3 Data Transcript Impacts

3.1 General
The Data Transcript commands are divided into different chapters depending on where in the loading sequence they belong. The DT impact for HLR redundancy will only be covered in this document, and not in the I-module part of the DT Infomodel. That's because the two HLRs must have the same configuration, and that's not the case for the network plan that the I-module DT is based upon.

3.2 Subfile 10000 - Size Alteration Events (APT)

Example 7 MML Commands

SAAII:SAE=500,

BLOCK=HRUIDAP,

NI=1000;

! Number of task individuals for incoming update subscriber ! ! data operation needed to support the traffic offered. ! ! Typical value: 1000 ! ! ---------------------------------------------------------------- ! SAAII:SAE=500, BLOCK=HRUODAP, NI=1000;

! Number of task individuals for outgoing update subscriber ! ! data operation needed to support the traffic offered. ! ! Typical value: 1000 ! ! ---------------------------------------------------------------- ! SAAII:SAE=500, BLOCK=HRMAPTC, NI=2002;

! Number of task individuals for each Redundancy MAP dialogue ! ! used for incoming and outgoing Redundancy MAP. It is released ! ! when the dialogue is ended. ! ! Guiding value: SAE500(HRUIDAP) + SAE500(HRUODAP) + 2. ! ! Typical value: 2002 ! ! ---------------------------------------------------------------- !

3.3 Subfile 13000 - HLR Exchange Properties

Example 8 MML Commands

HGEPC:PROP=REDINCOMPATA-10; ! REDICOMPDATA subscribers ! alarm ! subscribers. ! ! ! subscribers) ! Optional ! HRSC 1-65535 Threshold to trigger the ! with incompatible data ! It is set in steps of 10 !

Default value: 10 (100 ! Type: ! Involved blocks: !

HGEPC:PROP=REDRATE-10; ! REDRATE be ! ! of 10-300 Number of Kbits per second that can sent to the mated HLR in steps !

! 1Kbit/sec ! ! ! 10 ! Optional ! HRSC HGEPC:PROP=REDFAILNORM-3; ! REDFAILNORM subscribers ! from ! ! state ! ! ! 3 ! Optional ! HRNC 1-20 !

Default value: ! Type: ! Involved blocks: !

Percentage of redundant pending to be updated to transit Failure to Normal !

Default value: ! Type: ! Involved blocks: !

3.4 Subfile 75500 - SCCP Analysis

Subsystem number 224 is defined in the MSC/VLR for the two redundant HLR nodes. Example 9 MML Commands

!*** DEFINITION OF SUBSYSTEM ***! C7NSI:SP=2-700, C7NSI:SP=2-200, SSN=224; SSN=224; ! HLR1 ! HLR2 RED ! RED !

Two Global Title Routing Cases towards the HLR nodes have to be defined in the MSC/VLR. Example 10 MML Commands

!*** GLOBAL TITLE ROUTING CASE DEFINITION ***! C7GCI:GTRC=5,PSP=2-700,PSSN=6,PTERM,SSP=2-200,SSSN=6,STERM; C7GCI:GTRC=6,PSP=2-200,PSSN=6,PTERM,SSP=2-700,SSSN=6,STERM; !*** DEFINITION OF GLOBAL TITLE SERIES IN MSC/VLR FOR LU ***!

C7GSI:TT=0, HLR1 ! C7GSI:TT=0, HLR2 !

NP=7, NP=7,

NA=4, NA=4,

NS=46 70 751, NS=46 70 761,

GTRC=5; ! PRIMARY TO GTRC=6; ! PRIMARY TO

!*** DEFINITION OF GLOBAL TITLE SERIES IN MSC/VLR FOR MT CALLS ***! C7GSI:TT=0, HLR1 ! C7GSI:TT=0, HLR2 ! NP=1, NP=1, NA=4, NA=4, NS=46 70 757 1, NS=46 70 767 1, GTRC=5;! PRIMARY TO GTRC=6;! PRIMARY TO

!*** ACTIVATION OF THE NON-OPERATING GLOBAL TITLE AREA ***! C7TAI; !*** GLOBAL TITLE ROUTING CASE DEFINITION IN HLR1 ***! C7GCI:GTRC=4, ! C7GCI:GTRC=5, REQUEST"! C7GCI:GTRC=6, ANSWER"! AND! !"UPDATE SUBSCRIBER DATA"! !*** DEFINITION OF GLOBAL TITLE SERIES IN HLR1 ***!
"Send parameter" messages towards the AUC. Example 11 MML Commands

PSP=2-200, PSP=OWNSP, PSP=OWNSP,

PTERM, PSSN=10;

PSSN=224;

!HLR2 VIA MSC/VLR !"TRIPLET

PSSN=224;

!"TRIPLET REQUEST !"REDUNDANCY CONTROL"

C7GSI:TT=2,

NP=6,

NA=4,

NS=240 01,

GTRC=5;

Termination of "Send parameter" messages received from the AUC. Example 12 MML Commands

C7GSI:TT=187,

NP=1,

NA=4,

NS=46 70 75701,

GTRC=6;

Sending of "Redundancy control" messages from HLR1 to HLR2. Example 13 MML Commands

C7GSI:TT=187,

NP=1,

NA=4,

NS=46 70 76701,

GTRC=4;

Termination of "Redundancy control" messages in HLR1 from HLR2. Example 14 MML Commands

C7GSI:TT=187,

NP=1,

NA=4,

NS=46 70 75701,

GTRC=6;

Sending of "Update subscriber data" messages from HLR 1 to HLR 2. Example 15 MML Commands

C7GSI:TT=170,

NP=1,

NA=4,

NS=46 70 76701,

GTRC=4;

Termination of "Update subscriber data" messages in HLR 1 from HLR 2. Example 16 MML Commands

C7GSI:TT=170,

NP=1,

NA=4,

NS=46 70 75701,

GTRC=6;

!*** ACTIVATION OF THE NON-OPERATING GLOBAL TITLE AREA ***! C7TAI;

3.5 Subfile 81000 - HLR Number Series Analysis

In HLR1, HLR2 is defined as redundant (using it's the international and national HLR2 address). Example 17 MML Commands

HGRNC:RINT=46 70 7670100,

RNAT=70 7670100;

Define the characteristics of the function REDUN in HLR1. Example 18 MML Commands

!*** NUMBER SERIES ANALYSIS ***!

The Characteristic Redundance is initiated for a number series. If the characteristic value is omitted, value 0, "Primary Subscriber" is assumed. Example 19 MML Commands

HGNSI:ONSA=8,

NS=240 01 76,

CHAR=REDUN;

Pre-number serie analysis for Redundant Condition. Example 20 MML Commands

HGPAI:ONSA=8,

USRF=REDUN,

NAPI=2,

NAI=4;

If the redundant condition for new or already defined subscribers are changed (commands HGNSI, HGNSE) command HGRUC has to be entered in both HLR's in order to execute the change. Example 21 MML Commands

HGRUC; ! *** INITIATE THE REDUNDANCY FUNCTION IN HLR1 *** !

Working mode "ALONE" applies when the function is initiated in a HLR, working with all subscribers and their related information is considered valid. Working mode "NEW" applies when the mated HLR is already working with redundancy initiated. No subscriber info stored in the HLR is considered valid. Working mode "MATED" applies when the redundancy function is going to be initiated for a pair of HLR nodes that were working separately before. Only the primary subscribers data is considered valid. Example 22 MML Commands

HGRFI:WMODE=MATED;

4 Miscellaneous Information
4.1 Class
HLR Redundancy is an optional feature.

5 Reference List
[1] 128 63/FF-APR 101 17/1 Uen PA9. Administration of HLR Redundancy. [2] 139/155 17-ANT 238 01 Uen PB3. HLR Node Redundancy. [3] 2/155 42-CNT 238 0132 Uen A. Mobile Telephony Data: HLR Redundant Condition Change. [4] 12/1091-3/FCPE 146 104/E Uen A. Initiation of HLR Redundancy Function. [5] 1/155 42-CNT 238 0132 Uen A. Mobile Telephony Data, HLR Redundancy Function.