All standardised Supplementary Service Data is located in either the HLR (for GSM networks) and/or the HSS (for IMS networks), and/or in a convergent HLR/HSS.

When accessing Supplementary Service Data from the HSS, the Diameter Sh interface is used. The Supplementary Service Data is stored according to standardized XML schemas within Transparent User Data.

When accessing Supplementary Service Data in the HLR, the GSM MAP protocol is used. Supplementary Service Data is stored according to standardized schemas (often ASN.1 defined).

Supplementary Service Data stored in the HSS

All components that need access to any data from the HSS, including both Transparent and Non-transparent data, access it through the Sh Cache Microservice component. Components that use Supplementary Service Data in the HSS include:

Component Name Purpose

Sentinel Registrar

Cache warming of the Served User’s Supplementary Service Data upon Initial Registration

Sentinel VoLTE MMTel Features

Supplementary Service Data is necessary for many features to operate

XCAP Server

The purpose of the XCAP server is to enable subscribers to query and modify their service settings

Transparent Data editing capability within the Rhino Element Manager

This capability enables an administrator to query and edit the Supplementary Service Data

For more information about the Sh Cache Microservice see Sh Cache Microservice architecture

Supplementary Service Data stored in the HLR

All components that need access to data from the HLR, access it through the CGIN MAP component. Components that use Supplementary Service Data in the HLR include:

  • Sentinel VoLTE MMTel features - Supplementary Service Data is necessary for many features to operate

Previous page Next page