Huawei SinlgeSDB HSS9860-BE Feature Description
Huawei SinlgeSDB HSS9860-BE Feature Description
Issue 1.0
Date 2016-05-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade
names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made between Huawei and
the customer. All or partial products, services and features described in this document may not be within the
purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any
kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation
of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this
document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
Huawei SinlgeSDB HSS9860-BE Feature Description INTERNAL
Contents
This document describes the functions, services, and features provided by the SAE-HSS-BE
in SingleSDB V100R006C00.
Specification
None.
Summary
The USCDB allows a single subscriber to be defined on the PGW Web LMT or multiple
subscribers to be defined by using templates.
Benefits
For carriers
Description
The USCDB supports the following subscriber definition modes:
Defining a single subscriber in the SAE HSS
Defining multiple subscribers in the SAE HSS at a time by using templates
The SAE HSS can be defined with a maximum of 255 subscription templates.
Through subscriber definition, various services can be provided for one or more subscribers.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The USCDB allows a subscriber to be deleted from the SAE HSS.
Benefits
For carriers
The function facilitates subscriber deletion.
For subscribers
None.
Description
The USCDB supports the following subscriber deletion modes:
Deleting a subscriber from the SAE HSS
Deleting multiple subscribers from the SAE HSS at a time
During the subscriber deletion, either the service subscription data or all the data of a
subscriber including the KI data can be deleted.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
This function allows the MSISDN of a subscriber to remain unchanged when the IMSI of the
subscriber is changed.
Benefits
For carriers
This function can prevent the waste of number resources and helps carriers to maintain
the subscriber base and customer loyalty.
For subscribers
This function allows the MSISDN and subscription data of a subscriber to remain
unchanged when the IMSI of the subscriber is changed. Therefore, the communication of
the subscriber is not adversely affected when the SIM card of the subscriber is lost or
damaged.
Description
This function allows the MSISDN and subscription data of a subscriber to remain unchanged
when the IMSI of the subscriber is changed.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
This function allows the IMSI of a subscriber to remain unchanged when the MSISDN of the
subscriber is changed on the SAE HSS.
Benefits
For carriers
The function helps carriers to maintain the subscriber base.
For subscribers
Subscribers can have a new MSISDN without changing their SIM cards.
Description
This function allows the MSISDN of a subscriber to be changed on the SAE HSS while the
subscription data remains unchanged.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The USCDB allows MSISDNs or IMSIs to be queried on the SAE HSS.
Benefits
For carriers
This function facilitates subscriber data management.
For subscribers
None.
Description
This function allows the MSISDN of a subscriber to be queried from the SAE HSS based on
the entered IMSI or allows the IMSI of a subscriber to be queried based on the entered
MSISDN. If a subscriber has multiple MSISDNs, this function allows all the MSISDNs to be
queried.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
This function allows basic services to be configured or queried on the SAE HSS.
Benefits
For carriers
This function facilitates subscriber data management.
For subscribers
None.
Description
This function allows the basic services (including teleservices and bearer services) to be
configured and queried on the SAE HSS.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
This function allows the subscriber dynamic information to be queried on the SAE HSS.
Benefits
For carriers
This function facilitates subscriber data management.
For subscribers
None.
Description
This function allows the dynamic information about a subscriber to be queried on the SAE
HSS. The dynamic information includes the following:
Roaming status of the subscriber
Number of the MME serving the subscriber
Domestic roaming or international roaming
Service capability of the MME
Alternative handling of unsupported services
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The SAE HSS provides common service templates (including subscriber definition template,
CAMEL template, and VLR roaming restriction template) to facilitate service provisioning.
Benefits
For carriers
This function simplifies the service provisioning process.
For subscribers
None.
Description
The SAE HSS provides a series of templates that can be reused. The templates contain the
commonly used service data and are predefined on the provisioning system. When a
subscriber needs to subscribe to one or more services, the predefined template can be used to
provide services for the subscriber. This function simplifies the service provisioning process
and improves operational efficiency.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The SAE HSS supports batch operations.
Benefits
For carriers
This function simplifies the service provisioning process and improves operational
efficiency.
For subscribers
None.
Description
The SAE HSS implements the batch operation by automatically running the file containing all
the to-be-executed MML commands.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The SAE-HSS supports operator management based on the rights assigned to operators.
Benefits
For carriers
This function facilitates subscriber data management.
For subscribers
None.
Enhancement
None.
Description
The rights of an operator are determined by the role of the operator and the number segment
managed by the operator, that is, the operator can only run the specified command to manage
the specified number segment.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
This function allows the subscriber location information (including the VLR number, MSC
number, and the SGSN number) to be modified on the SAE-HSS.
Benefits
For carriers
This function facilitates subscriber data management.
For subscribers
None.
Description
This function allows the location information, including the VLR number and the MSC
number, to be changed through the O&M terminal. Generally, the location information of a
subscriber is changed for the purpose of registering a subscriber with the network forcibly or
inserting the subscriber data. This function improves the maintainability of the system.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The SAE-HSS supports operation log management. An operation log records all operations
performed by an operator. The information in an operation log includes the time when an
operation is performed, IP address of the PC, and executed MML commands.
The operation log helps carriers to learn about the operations performed on the SAE-HSS.
Benefits
For carriers
The log information helps carriers to analyze and identify faults.
For subscribers
None.
Description
The HLR9820 supports the query of the commands that have been executed based on the
specified operator, time, or number segment. In addition, an operator cannot query the
commands executed by other operators. This mechanism effectively protects the security of
information.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The SAE-HSS provides the statistics of subscriber data, for example, the number of
subscribers served by the SAE-HSS and the number of roaming subscribers.
Benefits
For carriers
This function enables carriers to learn about the system operation.
For subscribers
None.
Description
The SAE-HSS can provide the following information:
Statistics of the authentication data
Number of subscribers
Number of subscribers in different roaming status, for example, the number of
subscribers roaming to a VLR
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
None.
Summary
The USCDB provides an MML interface to achieve communication between the HSS and the
provisioning system.
Benefits
For carriers
This feature facilitates subscriber data management.
For subscribers
None.
Description
The USCDB provides an MML interface to achieve communication between the HSS and the
provisioning system. This interface facilitates subscriber data management and future
expansion.
Enhancement
None.
Dependency
The USCDB implements this feature in compliance with standard protocols. There is no
special requirement for other NEs.
Specification
None.
Summary
The USCDB provides an XML/SOAP interface to achieve communication between the HSS
and the provisioning system.
Benefits
For carriers
This feature facilitates subscriber data management.
For subscribers
None.
Description
The USCDB provides an XML/SOAP interface to achieve communication between the HSS
and the provisioning system. This interface facilitates subscriber data management and future
expansion.
Enhancement
None.
Dependency
The USCDB implements this feature in compliance with standard protocols. There is no
special requirement for other NEs.
Specification
None.
Summary
The HSS supports the seamless geographic redundancy solution, which allows the active and
redundancy HSSs to be deployed in different places and the FE and BE to be independently
deployed. When the subscriber data in the active HSS is modified, the updated data is sent to
the redundancy HSS in real time. Therefore, data synchronization between the active and
redundancy HSSs is ensured. In addition, the periodic data check function is enabled to
ensure data consistency between the active and redundancy HSSs.
Benefits
For carriers
This feature enables carriers to ensure higher reliability and security of the HSS. This
reduces the CAPEX and OPEX of carriers and enhances their competitive edge.
For subscribers
None.
Description
The HSS supports three types of seamless geographic redundancy solution:
1+1 active/standby redundancy solution
The FE and the BE are integrated. Data synchronization between the two HSSs is
implemented over the data layer. In normal conditions, the active HSS provides all the
services, and the redundancy HSS does not provide services.
1+1 load-sharing redundancy solution
The FE and the BE are integrated. Data synchronization between the two HSSs is
implemented over the data layer. In this solution, both HSSs provide services and
function as the backup of each other.
Enhancement
None.
Dependency
The USCDB implements this feature independently. There is no special requirement for other
NEs.
Specification
None.
Summary
This function, implemented on the SAE HSS, is applicable to sparsely populated areas. It
enables carriers to reduce investment costs.
Benefits
For carriers
The number of physical SAE HSSs to be used is reduced because the virtual HSS
function allows the subscriber data of different areas to be stored in a physical SAE HSS.
This function can reduce the investment costs of carriers. The virtual HSS function is
applicable to sparsely populated areas or the initially deployed network, which serves a
small number of subscribers but requires wide radio coverage. The virtual HSS function
also allows the data of subscribers with different access network numbers to be stored in
a physical SAE HSS, thereby implementing centralized management and maintenance of
the subscriber data. By using this function, carriers can easily manage subscribers in
different areas based on number segments.
For subscribers
None.
Description
In sparsely populated areas, the performance of each SAE HSS cannot be fully utilized if the
traditional SAE HSS deployment is adopted. To slash investment costs, the virtual HLR
function can be adopted. This function enables the subscriber data of multiple areas to be
stored in a physical SAE HSS, which is then divided into multiple logical HSSs based on the
administrative regions. Each logical HSS is configured so that the operators with the relevant
authority can manage the subscriber data of their areas. The division of the physical SAE HSS
based on the number segments managed by the operators enables carriers to manage the
subscriber data of different areas based on number segment.
Enhancement
None.
Dependency
The USCDB implements this function independently. There is no special requirement for
other NEs.
Specification
3GPP29002.
Summary
The SAE HSS supports the management of KI, OP, and K4.
Benefits
For carriers
The SAE HSS provides the GUI for AuC data management. It facilitates the
management and maintenance of the AuC data.
For subscribers
None.
Description
The SAE HSS supports AuC data management, such as adding, deleting, modifying, checking,
and querying KI, OP, and K4.
Enhancement
None.
Dependency
The USCDB implements this feature independently. There is no special requirement for other
NEs.
Summary
The IMS HSS stores the authentication data of IMS subscribers after encrypting the data, and
allows an IMS subscriber to subscribe to multiple types of authentication data.
Benefits
For carriers
This feature enables carriers to provide multiple terminal access modes and improve
subscriber experience.
For subscribers
This feature facilitates access to the IMS network, so subscribers can enjoy better
services. In addition, the authentication data is stored in the HSS after being encrypted,
which protects subscriber privacy.
Description
The IMS HSS can store a maximum of five authentication data types for an IMPU, including:
IMS AKA authentication data
Early IMS authentication data
HTTP/SIP Digest authentication data
NASS Bundled authentication data
Authentication data of the SIM/USIM card
The preceding authentication data is stored in the IMS HSS database after being encrypted by
using the Advanced Encryption Standard (AES) algorithm. The encryption key is a string of
128 characters. On the IMS HSS, you can set the priority of the authentication modes
provided to a subscriber. This improves the registration success ratio of the subscriber and
reduces signaling procedures.
Enhancement
None.
Dependency
The USCDB implements this feature independently. There is no special requirement for other
NEs.
Specification
3GPP 29.328 and 3GPP 29.329
Summary
The HSS9820 supports the AS-invoked subscription procedure through the Sh interface that
complies with 3GPP TS 29.328 and 3GPP TS 29.329. The HSS can notify the AS of changes
in data to which the AS has previously subscribed.
In addition, the HSS9820 supports the repository data management performed by the AS
through the Sh interface that complies with 3GPP TS 29.328 and 3GPP TS 29.329. Through
the Sh interface, the AS can add the repository data of a specified subscriber to the HSS, and
read, update, or delete the repository data stored in the HSS.
Benefits
For carriers
The subscriber data increases with the diversity of AS services. The development trend
of the AS is to obtain and subscribe to the subscriber data from the HSS. This also
facilitates the deployment of new services.
This feature allows the HSS to store the subscriber data for the AS. Therefore, the AS
does not need to store any subscriber data and the HSS can efficiently function as the
subscriber data center. This accelerates the deployment of new services.
For subscribers
None.
Description
The Sh interface supported by the HSS complies with 3GPP TS 29.328 V5.7.0 and 3GPP TS
29.329 V7.5.0. The following types of data can be modified or subscribed to through the Sh
interface:
RepositoryData
IMSPublicIdentity
IMSUserState
S-CSCFName
InitialFilterCriteria
LocationInformation
UserState
Charging information
MSISDN
PSIActivation
AliasesRepositoryData
This feature enables the HSS9820 to perform the following functions:
Supporting the operations, such as addition, update, deletion, and subscription of alias
repository data, performed by the AS
Supporting the subscription of 64 repository data records for a specified subscriber,
allowing the size of each record to reach 15 KB
Implementing permission-based management for the AS
In HSS9820 V900R006, the Sh interface is enhanced to:
Support alias repository data.
Support the subscription of 64 repository data records for a specified subscriber,
allowing the size of each record to reach 15 KB.
Enhancement
None.
Dependency
None.
Specification
3GPP 29.328 and 3GPP 29.329
Summary
This feature provides enhanced repository data storage and management based on the feature
numbered MI5S0TDSM000.
Benefits
For carriers
Carriers can provide more space for repository data storage, which facilitates service
deployment.
For subscribers
None.
Description
By default, the HSS assigns a space of 5K bytes for repository data storage for each IMPU.
When the repository data of a subscriber exceeds 5K bytes, the subscriber needs to pay for the
extra fee. This feature enables the HSS to provide larger space to store repository data of each
IMPU.
Enhancement
None.
Dependency
None.
Specification
None.
Summary
The HSS9820 can store additional iFC data for a specified subscriber.
Benefits
For carriers
This feature assists the carrier in providing more third-party services for subscribers.
For subscribers
None.
Description
The HSS allows a maximum of 255 iFC records to be defined for an IMPU. By default, each
subscriber is provided with 3.5-KB space for storing the iFC data. If the space is insufficient,
the HSS can provide more space after the subscriber pays additional storage fee. The HSS is
enhanced to allow more iFC records to be defined for an IMPU.
Enhancement
None.
Dependency
None.
Specification
None.
Summary
The HSS9820 supports the management of transparent data over the service provisioning
interface. The transparent data includes both ordinary transparent data and alias transparent
data. The AS can obtain the transparent data from the HSS over the Sh interface.
Benefits
For carriers
The HSS9820 provides a service provisioning interface for transparent data management.
This facilitates data check and collection of statistics in the BOSS by allowing carriers to
query and change transparent data at any time.
For subscribers
None.
Description
The AS stores the transparent data and alias transparent data in the HSS. The AS defines the
data and the HSS only stores the data.
The HSS provides the service provisioning interface and Sh interface for maintenance
operations on the data, such as adding, modifying, and deleting the transparent or alias
transparent data. This enhances the management modes of transparent data.
Enhancement
None.
Dependency
None.