Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 1 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

PE/HLR/APP/027811

HLR

HLR New in this Release

Release: HLR22

Replaces: NN10300-412
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 2 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

HLR
Release: HLR22
Document number: PE/HLR/APP/027811
Document release date: September 5, 2014 9:57 AM

Copyright © 2014 Kapsch. All Rights Reserved.

The information contained in this document is the property of Kapsch CarrierCom (in the following referred to as
“Kapsch”). Except as specifically authorized in writing by Kapsch, the holder of this document shall keep the information
contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties
and use same for evaluation, operation and maintenance purposes only.

The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Kapsch as to the content or accuracy of the information contained herein,
including but not limited to the suitability and performance of the product or its intended application.

Kapsch and the Kapsch logo are trademarks of Kapsch and/ or its licensors. All other trademarks are the property of
their owners.
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 3 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

Table of contents

1 Introduction ....................................................................................................................................... 4
1.1 Navigation ........................................................................................................................................... 4

2 Overview ............................................................................................................................................ 4
2.1 Solution-level definitions ..................................................................................................................... 4

3 Architecture and platform changes ................................................................................................. 5

3.1 Home Location Register (HLR) ........................................................................................................... 5
3.2 Data Server (DS) ................................................................................................................................. 5

4 New features ...................................................................................................................................... 6

4.1 Navigation ........................................................................................................................................... 6
4.2 HLR support for Camel Phase 4 - SMS-MT CSI ................................................................................. 6
4.3 HLR22 Cross Release Mating (XRM) ................................................................................................. 8
4.4 HLR CT7 Registration .......................................................................................................................10

5 Document changes .........................................................................................................................11

 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 4 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

1 Introduction
The following sections detail what is new in the HLR22 release for the Home Location Register (HLR). It
describes new features introduced on the HLR in this release and in general changes made to the HLR22
solution (architecture, capacity…).

1.1 Navigation
• “Overview” on page 4
• “Architecture and platform changes” on page 5
• “New features” on page 6
• “Document changes” on page 11

2 Overview

NSS22 (MSCS22 and HLR22) is a common release to both generations of MSC-S and HLR platforms
supported in Kapsch CarrierCom Core portfolio for GSM-R. The release applies thus to:

 KAIROS (13U ATCA) MSC-S and HLR

 VSE (12U ATCA) based MSC-S and HLR

For both platforms, the HLR22 release content is built on HLR19 release and is specifically productized
for GSM-R market:

 The HLR22 content aligns HLR functionality with new features introduced on MSC-S in NSS22

 In addition, as the second release for GSM-R VSE based HLR architecture, HLR22 content also
addresses HLR upgrades and associated requirements for this platform
The HLR22 continues supporting Kapsch next generation of wireless networks for GSM-R and maintains
a split architecture composed of:

 A Data Server provisioned in redundant configuration which acts as single point for subscriber
provisioning in the network and central subscriber information database.

 Distributed HLRs that provide transactions capacity required to process network requests and
manage real time subscriber data storage.

2.1 Solution-level definitions

In an HLR22 domain, the overall architecture and hierarchy are described in terms of sites, nodes, and
components.

The HLR service domain is a grouping of nodes that provide the HLR function for the network.

2.1.1 Nodes
The HLR22 solution includes the following types of nodes:
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 5 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

• HLR stores real-time and subscriber profile data, processes network requests, and provides
service to other CCS7 network entities. The HLR is based on carrier grade ATCA hardware.
• Data Server is a subscriber data master and a provisioning and management center.
Nodes are distributed across sites and are defined by a set of mandatory and optional components.

2.1.2 Sites
The characteristics of a site for the HLR22 solution are as follows:

• Sites are geographic locations where nodes are deployed.

• Geographically separate sites provide the basis for geo-redundancy of nodal functions.
• All sites require access to the operator’s Operational SubSystem (OSS) IP network.
• Some sites require access to the operator’s Common Channel Signaling Number 7 (CCS7)
network.
• Connectivity rules determine how some nodes need to be co-located at a site.

3 Architecture and platform changes

3.1 Home Location Register (HLR)

Focusing on GSM-R market, the HLR22 proposed configuration is based Carrier Grade ATCA platform
and on single shelf configuration, allowing up to 1 Million subscribers capacity based on standard profile.
Details on platform architecture supported in this release are provided in HLR fundamentals document,
respectively:

 HLR Fundamentals Volume 1 of 2 (PE/HLR/APP/027809) for VSE MSC-S based HLR (12U
ATCA).

 HLR Fundamentals Volume 1 of 2 (PE/HLR/APP/027896) for new generation KAIROS based

HLR (13U ATCA).

3.2 Data Server (DS)

The Kapsch Data Server (DS) application is a mandatory component and provides a single point of
provisioning and data mining. In HLR22, the Data Server consists of a Network Equipment-Building
System (NEBS) compliant Red Hat Virtual Machines or Solaris Guest Domain running the Red Hat
Enterprise Linux or Solaris Operating System. The Data Server platform also hosts a database, which is
used to store the subscriber mapping and subscriber data required by the HLR provisioning application.
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 6 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

4 New features
This chapter defines the activities pertaining to new functions in HLR22 software release. The following
information is provided for each activity:

• brief description of the feature

• data schema changes
• log changes
• office parameter changes
• operational measurement changes
• user interface changes
• restrictions and limitations
• list of documents affected by the feature

4.1 Navigation
HLR22 introduces the following new features:

 “HLR support for Camel Phase 4 - SMS-MT CSI” on page 6

 “HLR22 Cross Release Mating (XRM)” on page 8
 “HLR CT7 Registration” on page 10

4.2 HLR support for Camel Phase 4 - SMS-MT CSI

In-Step reference F2200005.

This feature implements the HLR support for CAMEL phase 4 MT SMS CSI functionality which is
described in 3GPP standards 23.078 and 29.078.

MT SMS CSI is provisioned by the service provider and stored in HLR. This MT SMS CSI is further
propagated to VLR or SGSN in order to support MT SMS Delivery control functionality via IN logic.

This feature introduces the handling of provisioning messages coming from the Home Location Register
Data Server (HLR-DS), storing MT SMS CSI for each subscriber, synchronizing MT SMS CSI between
mated Standby and Active HLRs and messaging between the HLR and VLR or SGSN in order to provide
MT SMS CSI.

MT SMS CSI functionality which includes MSC and VLR control is accomplished by the activity 1A020678
“MSC support for Camel Phase 4 - SMS-MT CSI”.HLR support for Camel Phase 4 - SMS-MT CSI

4.2.1 Data schema changes

With this feature table GHSMSCSI is enhanced to store Mobile Terminated Camel Subscription
Information (MT SMS CSI) in addition to Mobile Originated Camel Subscription Information (MO SMS
CSI).
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 7 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

4.2.2 Log changes

4.2.2.1 New logs

None

4.2.2.2 Modified logs

GHLR668: indicates the amount of memory being used by the subscribers within the subscriber database
on the HLR. The log also indicates how many subscribers can be added to the database
before the SOS and SLM limits are hit.

GHLR674: is generated and is valid only during the upgrade window. The GSM HLR ONP applications
bind into the three data transfer stages on the upgrade, and a log is generated when GSM
data completes transfer for each of the stages. A log is generated on both the Active and
Inactive processors. The data in the log is for information purposes only. SMSCSI data which
includes both MT SMS and MO SMS CSIs are shown during the GSM HLR ONP.

GHLR683: indicates that a VLR/SGSN has declared conflicting CAMEL Phase capabilities during an
Update Location/Update GPRS Location-Insert Subscriber Data and Restore Data dialogue.

4.2.2.3 Obsolete logs

None

4.2.3 Office parameter changes

None

4.2.4 Operational measurement changes

Existing registers in OM group of HLRCAML2 are enhanced to maintain the number of subscribers having
MO SMS CAMEL Subscription Information. These registers were used to count the number of
subscribers with MO SMS CSI subscribed. New OM Group of HLRCAML3 is defined for MT-SMS-CSI.
New registers in HLRCAML3 counts the number of subscribers provisioned with MT-SMS-CSI.

4.2.5 User interface changes

In directory HLRADMIN the responses of following commands are changed:

 QIMSI: displays additionally the subscriber’s information of Phase 4 CAMEL MT SMS CSI
 QMSISDN: displays additionally the subscriber’s information of Phase 4 CAMEL MT SMS CSI
 PRINT: is enhanced for the following messages.
o UL, UGL, RD :CAMEL Phase 4 for SupportedCamelPhases and MT SMS CSI for
OfferedCamel4CSIs services.
o ISD: MT SMS CSI
o DSD: MT SMS CSI in Specific CSI Withdraw information element.
o Update Location Message : Camel Phase 4 is added for SupportedCamelPhases and
MT SMS CSI is added for OfferedCamel4CSIs.
o Update GPRS Location Message: Camel Phase 4 is added for SupportedCamelPhases
and MT SMS CSI is added for OfferedCamel4CSIs.
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 8 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

o Restore Data Message: Camel Phase 4 is added for SupportedCamelPhases and MT

SMS CSI is added for OfferedCamel4CSIs.
o Insert Subscriber Data Message: MT SMS CAMEL Subscription Info is added.
o Delete Subscriber Data Message: MT SMS CSI indication in Specific CSI Withdraw
information is added.

4.2.6 Restrictions and limitation

None

4.2.7 Documents affected by this feature

 HLR Log Reference (PE/HLR/APP/027815) and Kairos (PE/HLR/APP/027902)

 HLR Performance Management (PE/HLR/APP/027825) and Kairos (PE/HLR/APP/027912)
 HLR MAP Commands (PE/HLR/APP/027822)

4.3 HLR22 Cross Release Mating (XRM)

In-Step reference F2200015.

Cross release mating feature or XRM enhances HLR Mated pair functionality by allowing the mated pair
feature to sustain operation while one of the HLR mates has been upgraded to a new HLR release. The
feature provides synchronization of subscriber data changes (i.e. changes made either to Subscriber
Profile or Subscriber Location Data, including SIMR events) between the nodes of a HLR Mated Pair
during a Mated Pair software upgrade. This saves customer time as data change requests need not be
backlogged until both nodes of the HLR Mated Pair are running same software release.

XRM is provided in HLR22 to support mating between HLR19 and HLR22 software releases. All other
Mated Pair software release configurations are considered invalid.

4.3.1 Data schema changes

4.3.1.1 New data schemas

None

4.3.1.2 Modified data schemas

With this feature MP_VER field of table GHSBYCFG is enhanced to have HLR22 option for supporting
HLR22.

4.3.1.3 Obsolete data schemas

None

4.3.2 Log changes

GHLR812: ‘Standby System Parameter Change’ is generated when MP_VER in GHSBYCFG is changed.
GHLR803: ‘Standby Maintenance Blocked’ is generated when a Incompatible Standby Protocol Version
is used.
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 9 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

GHLR638: ‘Packing Protocol Version Changed’ is generated by the DMS-HLR Application to notify the
operator that the DS release no has changed.

4.3.3 Office parameter changes

4.3.3.1 New office parameters

A new office parameter DSRELNO is used to configure the DS release number on HLR. HLR uses this
parameter while connecting to DS. It specifies the version of DS that the HLR is being provisioned with.

The DSRELNO office parameter is similar to HLRRELNO office parameter, having two fields MAJOR {0
TO 32767} version and MINOR {0 TO 32767} version. DSRELNO must be manually set by the operator
on the HLR if there is a change in the DS release.

The office parameter can be modified only on MRF node and it is a read-only parameter on HLR
applications. It cannot be deleted from table GHLRPARM on either the MRF or HLR applications. The
following message is displayed when attempting to delete the parameter:

4.3.3.2 Modified office parameters

None

4.3.3.3 Obsolete office parameters

None

4.3.4 Operational measurement changes

4.3.4.1 New operational measurements

None

4.3.4.2 Modified operational measurements

None

4.3.4.3 Obsolete operational measurements

None

4.3.5 User interface changes

4.3.5.1 New user interfaces

None

4.3.5.2 Modified user interfaces

None

4.3.5.3 Obsolete user interfaces

None
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 10 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

4.3.6 Restrictions and limitations

 XRM configuration is supported between HLR19/VSE1.1 node and HLR22/VSE1.1 only. It is not
applicable to KAIROS HLR as newly introduced in HLR22.
 Changes to the system tables are not synchronized by XRM.
 It is not intended to enable XRM for extended periods of time (upgrade period). XRM is only to
support software upgrade of a Mated Pair HLR allowing the operator to access all functionalities
introduced by the higher release.
 Subscriber data changes newly introduced, removed or modified in HLR22 are handled as
follows:
• Fields newly introduced in HLR22 are not mated in the HLR22 -> HLR19 direction
• Fields removed in HLR22 are not mated in the HLR19 -> HLR22 direction
• New features on HLR22 may not be available until both systems in the mated Pair are
upgraded.
 The MSP protocol supported by the pair is only the MSP versions that are supported by both
HLR19 and HLR22.
 DS shall send MSP19 protocol to HLR22 and HLR19 until all the HLRs are upgraded to HLR22.

4.3.7 Documents affected by this feature

 HLR Log Reference (PE/HLR/APP/027815) and Kairos (PE/HLR/APP/027902)

 HLR Configuration – Data Schema (PE/HLR/APP/027820)
 HLR Configuration – Office Parameters (PE\HLR\APP\027821)

4.4 HLR CT7 Registration

In-Step reference F2200004.

HLR22 sources the patch ‘HLR CT7 registration’ available since NSS17.
This feature enhances feature ‘HLR Follow-ME (FM)’ to provide registration, deregistration and
interrogation of CT7 (Call Type Seven) Functional Numbers, i.e. Functional Numbers of type "7".
Functional Addressing is used in GSM-R to allow` the calling of users by their Functional Numbers
instead of a MSISDN (Mobile Station ISDN).

It provides the following new functionality to enable support of CT7 Functional Numbers on the HLR:

 Enhanced logic of the PUSSR (Process Unstructured Supplementary Service Request) message
to register, deregister and interrogate CT7 FNs.

4.4.1 Data schema changes

None

4.4.2 Log changes

4.4.2.1 New logs

None
 Kapsch CarrierCom AG

PE/HLR/APP/027811 | HLR New in this Release Page 11 of 11

State released | Version 0.22 | 05.09.2014 CONFIDENTIAL

4.4.2.2 Modified logs

None

4.4.2.3 Obsolete logs

None

4.4.3 Office parameter changes

None

4.4.4 Operational measurement changes

None

4.4.5 User interface changes

None

4.4.5.1 Modified user interfaces

None

4.4.5.2 Obsolete user interfaces

None

4.4.6 Restrictions and limitation.

This feature is controlled by SOC GSM02202.

4.4.7 Documents affected by this feature

None

5 Document changes
All documents applicable to NSS22 (new documents, changed or retired documents) are listed and
detailed in ‘documentation Roadmap’ document. See specifically:

 VSE Documentation Roadmap (PE/MSC/APP/027327) for complete list of NSS22 VSE MSC-S and
HLR NTP.
 Kairos Documentation Roadmap (PE/MSC/APP/027356) for complete list of NSS22 Kairos MSC-S
and HLR NTP.