Huawei SingleSDB V100R003C01 IMS HSS Feature Description

Huawei SingleSDB V100R003C01 IMS HSS
Feature Description
Issue 1.0
Date 2024-06-17
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Huawei SingleSDB V100R003C01 IMS HSS Feature Description Internal Open
Contents
1 Basic Features.................................................................................................................................4
1.1 WHFD-301000 Basic Software Features of the IMS-HSS-FE.........................................................................4
1.2 WHFD-302000 Basic Software Functions of the HSS....................................................................................26
1.3 WHFD-303000 Basic Software Functions of the SLF....................................................................................42
2 Optional Features........................................................................................................................45
2.1 WHFD-310111 Premium Authentication........................................................................................................45
2.2 WHFD-310211Roaming Awareness................................................................................................................62
2.3 WHFD-310080 Public Service Identities........................................................................................................65
2.4 WHFD-310070 Shared Public User Identities.................................................................................................67
2.5 WHFD-310150 CSCF Data Backup................................................................................................................69
2.6 WHFD-310160 IM-SSF CAMEL subscriber..................................................................................................70
2.7 WHFD-310210 Sh interface supports Notif-Eff featurefeature.......................................................................72
2.8 WHFD-310230 Supporting IPv6.....................................................................................................................73
2.9 WHFD-310240 Geographic Node Redundancy..............................................................................................73
Issue 1.0 (2024-06-17) Huawei Proprietary and Confidential Page 3 of 74

Copyright © Huawei Technologies Co.,
Ltd
Document Title Security Level:
1 Basic Features
1.1 WHFD-301000 Basic Software Features of the

IMS-HSS-FE
The IMS HSS supports the Diameter protocol and complies with IETF RFC
3588, 3GPP TS 29.228, 3GPP TS 29.229, 3GPP TS 29.328, and 3GPP TS
29.329.
The IMS HSS implements routing and addressing based on the IP Multimedia
Private Identity (IMPI) or IP Multimedia Public Identity (IMPU).
The IMS HSS supports the access to the IMS network by using IP addresses
of different formats.
The IMS HSS adopts distributed structure, supports independent service
processing and data storage. The IMS HSS consists of the Front End (FE) and
Back End (BE). The FE processes service logics, and the BE stores subscriber
data and provides the data required by the FE. The FE and BE can be
managed and maintained independently.
The IMS HSS adopts high reliability design. The system availability reaches
99.999%.
The IMS HSS adopts the following redundancy design to ensure reliability:
 Redundancy design of boards and network ports
 Virtual IP address
 Signaling link backup
1.1.1 WHFD-301111 Supporting Diameter over SCTP

Availability
This feature has been available since IMS HSS9820 V900R006.
2024-06-17 HUAWEI Confidential Page4, Total74

Specification
 IETF RFC 3588
 3GPP TS 29.228
 3GPP TS 29.229
 3GPP TS 29.328
 3GPP TS 29.329
Summary
The IMS HSS supports Diameter over Stream Control Transmission Protocol
(SCTP).
Benefits
 For carriers
This feature facilitates networking of the IMS HSS.
 For subscribers
None.
Description
The Diameter protocol is defined as the next-generation Authentication,
Authorization and Accounting (AAA) standard by the AAA working group of
the Internet Engineering Task Force (IETF). The Diameter protocol supports
authentication, authorization, and accounting of the mobile IP, NAS request,
and mobile agent. Similar to the RADIUS protocol, the Diameter protocol is
implemented through Attribute-Value-Pair (AVP), that is, a triplet of Attribute-
Length-Value. The Diameter protocol is a future-proof AAA protocol tailored
for future communication systems.
The IMS HSS can communicate with other NEs using Diameter over SCTP
on the Cx and Sh interfaces.
Dependency
The IMS HSS implements this feature in compliance with standard protocols.
1.1.2 WHFD-301112 Supporting Diameter over TCP

Availability
Specification
 IETF RFC 3588
 3GPP TS 29.228

 3GPP TS 29.229
 3GPP TS 29.328
 3GPP TS 29.329
Summary
The IMS HSS supports Diameter over Transmission Control Protocol (TCP).
Benefits
 For carriers
 For subscribers
None.
Description
The Diameter protocol is defined as the next-generation Authentication,
Authorization and Accounting (AAA) standard by the AAA working group of
the Internet Engineering Task Force (IETF). The Diameter protocol supports
authentication, authorization, and accounting of the mobile IP, NAS request,
and mobile agent. Similar to the RADIUS protocol, the Diameter protocol is
implemented through Attribute-Value-Pair (AVP), that is, a triplet of Attribute-
Length-Value. The Diameter protocol is a future-proof AAA protocol tailored
for future communication systems.
The IMS HSS can communicate with other NEs using Diameter over TCP on
the Cx and Sh interfaces.
Dependency
1.1.3 WHFD-301121 Supporting RADIUS over UDP

Availability
Specification
 IETF RFC 2865
 3GPP TS 29.061
 3GPP 33.978
Summary
The IMS HSS supports RADIUS over User Datagram Protocol (UDP).

Benefits
 For carriers
 For subscribers
None.
Description
The Remote Authentication Dial In User Service (RADIUS) protocol, defined
in RFC2865 and RFC2866, is the most widely used AAA protocol. The
RADIUS protocol provides flexible authentication mechanisms, such as
Password Authentication Protocol (PAP), Challenge-Handshake
Authentication Protocol (CHAP), and UNIX login.
The RADIUS protocol is easy to implement and extend; therefore, it is widely
used in dial-up access, ADSL access, IP phones, Virtual Private Dialup
Networks (VPDN), and mobile phone prepaid services.
The IMS HSS can communicate with other NEs using RADIUS over UDP on
the Gi interface.
Dependency
1.1.4 WHFD-301131 Supporting SIGTRAN over SCTP

Availability
Specification
 3GPP TS23.278
 3GPP TS29.002
Summary
The IMS HSS supports SIGTRAN over SCTP.
Benefits
 For carriers
 For subscribers
None.

Description
Signaling Transport (SIGTRAN), defined by the SIGTRAN working group of
the IETF, is a transport control protocol used to carry PSTN signaling over IP
networks. The SIGTRAN protocol supports standard PSTN primitive
interface and adopts a standard IP transport protocol to transport signaling. It
is widely used in the NGN.
The IMS HSS can communicate with other NEs using SIGTRAN over SCTP
on the Si and MAP interfaces.
Dependency
1.1.5 WHFD-301132 Supporting MAP

Availability
Specification
 3GPP TS23.278
 3GPP TS29.002
Summary
The IMS HSS supports the Mobile Application Part (MAP) protocols.
Benefits
 For carriers
 For subscribers
None.
Description
The IMS HSS supports the MAP protocols, which include MAP Phase 1,
MAP Phase 2, and MAP Phase 2+.
The IMS HSS can communication with other NEs using MAP protocols over
the Si and MAP interfaces.
Dependency

1.1.6 WHFD-301140 Supporting SCTP Multi-Homing

Availability
Specification
RFC2960
Summary
The IMS HSS supports SCTP multi-homing, which improves the reliability of
IP networking.
Benefits
 For carriers
This feature improves the reliability of IP networks and ensures
uninterrupted service processing. It helps to improve customer
satisfaction.
 For subscribers
None.
Description
The SCTP multi-homing function allows two source addresses and two
destination addresses to be configured for each IP link between two SCTP
endpoints (that is, the HSS and the peer device). The source addresses can be
configured on the same board or on different boards, thus implementing
multiple logical links and physical paths. The source addresses and destination
addresses can be configured in different network segments with different
connection priorities and used to connect different network devices.
The SCTP association can eliminate single-point failure on the network, thus
improving the reliability of the IP network.
Dependency
1.1.7 WHFD-301210 IMPI

Availability

Specification
3GPP 23.228
Summary
Each subscription can e configured with multiple IMPIs.
Benefits
 For carriers
This feature helps carriers to provide diversified value-added services,
such as multi-SIM service and e-home service.
 For subscribers
None.
Description
Each IMPI is associated with one physical UE and one security context at the
network side. Each IMS subscriber can have one or more IMPIs. The IMPI
can be used for service registration, authentication, subscriber management,
and charging.
Dependency
1.1.8 WHFD-301211 IMPI in NAI Format

Availability
Specification
RFC 2486
Summary
The IMS HSS supports the IMPIs present in Network Access Identifier (NAI)
format defined in RFC 2486.
Benefits
 For carriers
None.
 For subscribers
None.

Description
The IMS HSS supports the IMPIs present in NAI format (nai = username /
( username "@" realm), for example, hss@ims.huawei.com.
Dependency
1.1.9 WHFD-301221 IMPU in SIP URI format

Availability
Specification
RFC 3261
Summary
The IMS HSS supports the IMPUs present in SIP Uniform Resource Identifier
(URI) format defined in RFC 3261.
Benefits
 For carriers
None.
 For subscribers
None.
Description
The IMS HSS supports the IMPUs present in SIP URI format (SIP-URI =
"sip:" username"@"host:port), for example, sip:hss@ims.huawei.com.
Dependency
1.1.10 WHFD-301222 IMPU in E.164/TEL URI Format

Availability

Specification
RFC 3261
Summary
The IMS HSS supports the IMPUs present in E.164/TEL URI format defined
in RFC 3261.
Benefits
 For carriers
None.
 For subscribers
None.
Description
The IMS HSS supports the IMPUs present in TEL URI format defined by
RFC 3261, that is, telephone-uri="tel:" telephone-subscriber, for example,
tel: +8677998877.
Dependency
1.1.11 WHFD-301310 IPv4

Availability
Specification
RFC 791
Summary
The IMS HSS supports the access to the IMS network using IPv4 addresses.
Benefits
 For carriers
None.
 For subscribers
None.

Description
The Internet adopts the Transmission Control Protocol/Internet Protocol
(TCP/IP) suite. The IP protocol, as the core protocol in the TCP/IP suite, is
used in the network layer. So far, Internet Protocol version 4 (IPv4) has been
used for 30 years. According to IPv4, the IP address is 32 bits long, which
indicates that a maximum of 4,294,967,295 (232-1) can be defined.
The IMS HSS supports the access to the IMS network using the IPv4
addresses.
Dependency
1.1.12 WHFD-301410 Equipment Management

Availability
This function has been available since IMS HSS9820 V900R006.
Specification
None.
Summary
The equipment management function allows you to manage the software and
hardware of the equipment conveniently.
Benefits
 For carriers
This function enables carriers to manage the IMS HSS conveniently and meet
the requirements of routine operation.
 For subscribers
None.
Description
Hardware management involves the following:
 Resetting a board
 Switching over services between boards
 Loading data to a board
 Other related functions
Software management involves the following:

 Loading a patch
 Activating a patch
 Deactivating a patch
 Other related functions
Dependency
The IMS HSS implements this function independently. There is no special
requirement for other NEs.
1.1.13 WHFD-301420 Fault Management

Availability
Specification
None.
Summary
The IMS HSS provides alarm information output. It reports abnormality that
occurs during the system running. The alarms are output to the alarm
maintenance terminal or the alarm box.
Benefits
 For carriers
This function enables carriers to identify the faults in the IMS HSS and adopt
preventive measures accordingly.
 For subscribers
None.
Description
The alarms generated on the IMS HSS can be classified into fault alarms and
event alarms.
The IMS HSS enables carriers to implement the following alarm management
operations:
 Query alarm information at any time, and specify alarm severity, alarm
type, and/or generation time to query alarms.
 Conveniently learn about each alarm based on explanatory information
contained in the alarm. Then, the carrier can take corresponding
measures to clear the alarm.

 Enable or disable alarm shielding manually.

The IMS HSS provides an alarm box. When an alarm is reported, the alarm
box generates siren to alert the maintenance personnel.
Dependency
1.1.14 WHFD-301430 Configuration Management

Availability
Specification
None.
Summary
The configuration management function allows you to configure the system,
boards, and interfaces flexibly.
Benefits
 For carriers
This function enables carriers to configure the IMS HSS flexibly and meet
various data configuration requirements.
 For subscribers
None.
Description
The configuration management function allows you to configure data online
and offline. It allows you to configure the data by using MML commands.
This simplifies data configuration because you need to only compile the data
configuration scripts.
Dependency

1.1.15 WHFD-301440 Performance Management

Availability
Specification
None.
Summary
Performance management involves the activities of measuring the
performance of a device and its network. The measurement activities include
traffic measurement, system resource measurement, signaling procedure
measurement, and failure cause measurement.
Benefits
 For carriers
This function enables carriers to implement various performance
measurement tasks, monitor the running status of the system, and optimize the
network.
 For subscribers
None.
Description
Performance management involves the activities of measuring the
performance of a device and its network. The measurement activities include
traffic measurement, system resource measurement, signaling procedure
measurement, and failure cause measurement. In the HSS, the performance
measurement involves system resource measurement and signaling procedure
measurement.
Dependency
1.1.16 WHFD-301450 Log Management

Availability

Specification
None.
Summary
The IMS HSS provides user operation log and system running log.
Benefits
 For carriers
The log information helps carriers to analyze and identify faults.
 For subscribers
None.
Description
The IMS HSS provides the user operation log and system running log, which
can be viewed directly. The system also provides explanation and analysis for
logs. The system can also filter the system commissioning logs, thus the
maintenance personnel can rectify faults rapidly.
Dependency
1.1.17 WHFD-301460 Pool-Based Network Management

Availability
This function has been available since SDB V100R002.
Specification
None.
Summary
This function allows the NMS to manage the IMS-HSS-FE pools on the
network in a centralized way.
Benefits
 For carriers
This feature enables carriers to query, manage, and maintain the system
information conveniently.
 For subscribers

None.
Description
The pool-based O&M function is as follows:
 The FEs and BEs are present in different pools on the topology view of
the NMS.
 The O&M MML commands of the same format are issued to all the FEs
or BEs in a pool.
 The performance measurement tasks of all the FEs or BEs in a pool are
managed in a centralized way.
Dependency
The implementation of this function requires the cooperation of Huawei
NMS.
1.1.18 WHFD-301510 Automatic or Manual Board

Switchover
Availability
Specification
None.
Summary
When a board is faulty, the services processed by the faulty board can be
manually or automatically switched over to the redundancy board for
processing, ensuring uninterrupted service processing.
Benefits
 For carriers
This function enhances system reliability and reduces system failure
time. It helps to improve customer satisfaction.
 For subscribers
None.
Description
The boards of the IMS HSS work in active/standby mode or load-sharing
mode. When a board is faulty, the services processed by the faulty board can

be manually or automatically switched over to the redundancy board for

processing, ensuring uninterrupted service processing.
Dependency
1.1.19 WHFD-301520 Interface Redundancy

The interfaces of the IMS HSS can be classified into physical interfaces and
logical interfaces. Each type of interface supports active/standby mode.
1.1.20 WHFD-301521 Supporting Multiple IP

Addresses
Availability
Specification
None.
Summary
A Gigabit Ethernet port can be configured with multiple IP addresses.
Benefits
 For carriers
This feature enhances system reliability and reduces system failure time.
It helps to improve customer satisfaction.
 For subscribers
None.
Description
A Gigabit Ethernet port of the IMS HSS can be configured with multiple IP
addresses. Thus, an IP link can be configured with multiple source and
destination addresses. If one of the IP addresses configured for a link becomes
unavailable, the other IP addresses can be used for communication. Thus, the
link is protected against single-point failures, and the reliability of the IP
network is improved.

Dependency
The IMS HSS incorporates this feature internally. The implementation of this
feature, however, requires the cooperation of the peer NEs. There is no special
requirement for the peer NEs.
1.1.21 WHFD-301522 Supporting Multiple Signaling

Links
Availability
Specification
None.
Summary
The IMS HSS supports multiple signaling links.
Benefits
 For carriers
 For subscribers
None.
Description
Multiple signaling links working in load-sharing mode or active/standby
mode can be configured between the IMS HSS and the peer NE. When a link
is faulty, the other link(s) can transmit signaling messages. This feature
improves the system reliability.
Dependency

1.1.22 WHFD-301523 Redundancy of Gigabit Network

Port
Availability
Specification
None.
Summary
The IMS HSS supports the redundancy of Gigabit network ports.
Benefits
 For carriers
 For subscribers
None.
Description
The IMS HSS adopts two Gigabit network ports working in active/standby
mode to communicate with the peer NE. When the active port is faulty, the
system can automatically detect the fault in the active port and uses the
standby port to communicate with the peer NE. Thus, the system reliability is
improved.
Dependency
1.1.23 WHFD-301530 One Logical Port Shared by

Multiple Network Adapters
Availability
Specification
None.

Summary
Multiple network adapters of the IMS HSS can be configured with one logical
port.
Benefits
 For carriers
It helps to improve customer satisfaction
 For subscribers
None.
Description
One IP address can be configured for multiple network adapters of the IMS
HSS. When one network adapter is faulty, the logical link is not adversely
affected. This feature minimizes the adverse effect of the single-point fault
and improves reliability of IP networks.
Dependency
1.1.24 WHFD-301540 One Network Adapter Shared by

Multiple Logical Ports
Availability
Specification
None.
Summary
A network adapter of the IMS HSS can be configured with multiple logical
ports.
Benefits
 For carriers
This feature improves networking flexibility and reduces hardware costs.
 For subscribers
None.

Description
A network adapter of the IMS HSS can be configured with multiple IP
addresses. Thus, multiple logical links can be set up over one physical path.
Generally, only one logical link is configured on a Gigabit network adapter
for communication with the peer NE. This feature allows multiple logical
links to be configured for a Gigabit network adapter when the number of
network adapters cannot meet the requirement.
Dependency
1.1.25 WHFD-301550 Hard Disk Redundancy

Availability
Specification
None.
Summary
The disk array of the IMS HSS is configured with RAID1+RAID0. It
enhances data security and system reliability.
Benefits
 For carriers
This feature enhances data security and system reliability. When a fault
occurs, the data backup can be used to restore data, thus minimizing the
adverse effect on the system. This feature helps to improve customer
satisfaction.
 For subscribers
None.
Description
The IMS HSS supports the redundancy of the hard disk. To secure the
subscriber data, the HSS backs up the subscriber data stored in the board
memory to the disk array. The hard disks in the disk array work in Raid
1+Raid 0 mode, thus enhancing the security of the backup data and the
reliability of the system.

To ensure data security, the subscriber data stored in the board memories is
automatically backed up to the disk array. The disks of the disk array are
configured with RAID1+RAID0, which enhance data security and system
reliability.
Dependency
1.1.26 WHFD-301620 Distributed Structure of Software

Modules
Availability
Specification
None.
Summary
The distributed structure allows multiple functional entities that are identical
in a system to work in load-sharing mode to accomplish a function. The most
distinguished feature of the distributed structure is resource sharing in the
system. When a functional entity is faulty, the load is automatically switched
over to other functional entities. Thus, the service provisioning of the entire
system is not adversely affected.
The software modules of the IMS HSS adopt distributed structure.
Benefits
 For carriers
This feature improves system reliability, ensures uninterrupted service
processing, and helps to improve customer satisfaction.
 For subscribers
None.
Description
The IMS HSS adopts distributed structure. It consists of the following
functional layers:
 Service processing layer
 Data service layer
Each layer adopts distributed structure, as shown in the following figure.

The service processing layer, also called the FE, consists of the HSS signaling
function (HSF) and HSS control function (HCF). The FE processes signaling
and service logics.
The data service layer, also called the BE, consists of the DRU and DSU. The
BE stores and manages subscriber data.
The IMS HSS adopts high-reliable commercialized database management
system. It also uses the disk array to provide permanent storage of subscriber
data. The hard disks of the disk array are configured with RAID and hot spare
disks to ensure the security of subscriber data.
The data service layer, subscriber data management layer, and data storage
layer constitute the BE. The BE stores and manages subscriber data, and also
provides data service for the Front End (FE).
The distributed software architecture protects the system against single-point
faults and improves system reliability.
Dependency
The IMS HSS provides this feature independently. There is no special
1.1.27 WHFD-301650 Automatic Load Balancing

Availability
Specification
None.

Summary
The IMS HSS automatically balances the load among different software
modules.
Benefits
 For carriers
This feature enables carriers to protect the system from being overloaded and
thus prevent system breakdown.
 For subscribers
None.
Description
During the running of the IMS HSS, the load may be unbalanced among
boards due to the diversity of tasks, complexity of signaling processing, and
number of processed messages.
The IMS HSS adopts software technology to implement automatic load
balancing among modules of the same type. This improves system stability
and reliability.
Dependency
The IMS HSS implements this feature independently. There is no special
1.2 WHFD-302000 Basic Software Functions of the

HSS
The IMS HSS provides the following basic software functions:
 Basic protocol support
 Addressing and routing
 Charging
 Subscriber barring
 Subscriber roaming
 Subscription data management
 Definition of subscriptions through templates
 Service provisioning over the SOAP interface
The IMS HSS allows subscribers to access the IMS network through the
GPRS/UMTS, CDMA2000, WiFi, WiMax, xDSL, and LAN.

IMS HSS stores and delivers the IMS subscriber data.

The IMS HSS supports the following interfaces:
 Cx interface (I-CSCF/S-CSCF–HSS interface) (WHFD-302310)
 Sh interface (AS–HSS interface) (WHFD-302320)
 Si interface (IM-SSF–HSS interface) (WHFD-302330)
 Gi interface (GGSN–HSS interface) (WHFD-302340)
 MAP interface (HLR–HSS interface) (WHFD-302350)
The IMS HSS provides registration restriction and subscriber barring. Carriers
can set the registration rights of subscribers and subscriber barring status.
During the registration procedure, the IMS HSS verifies the registration rights
and barring status of a subscriber.
 Subscriber barring (WHFD-302410): This function prevents a subscriber
from using IMS services.
 Registration restriction (WHFD-302420): This function prevents a
subscriber from being registered with the network.
The IMS HSS supports roaming restriction check.
During the registration of a subscriber, the IMS HSS checks whether the
subscriber is allowed to roam to the IMS domain based on the IMS roaming
address list associated with the subscriber. This feature facilitates service
management.
1.2.1 WHFD-302110 Association Between One IMPI

and Multiple IMPUs
Availability
Specification
None.
Summary
An IMPI can be associated with multiple IMPUs. Thus, a UE can be
registered with the network by using multiple IMPUs.
Benefits
 For carriers
This feature facilitates the deployment of the multi-MSISDN service and
helps the carriers to increase their subscriber base and enhance their
competitive edge.
 For subscribers

Subscribers can use different identities to register different services.
Description
The IMPI identifies a UE, and the IMPU identifies the public number used by
other subscribers to contact the subscriber. If the MSISDN of a mobile
subscriber is +8613812345678, the IMPI of the subscriber can be tel:
+8613812345678 (IMPU1, in TEL URI format). If the subscriber wants to
access the IMS network through the UE, the subscriber can apply for another
IMPU (IMPU2, in SIP URI format), which can be sip:
+8613812345678@huawei.com. In this way, the IMPI of the subscriber is
associated with two IMPUs.
Dependency
1.2.2 WHFD-302120 Implicit Registration

Availability
Specification
None.
Summary
An implicit registration set (IRS) can be configured for multiple IMPUs. If
one IMPU in the IRS is registered, the other IMPUs in the IRS are registered
automatically.
Benefits
 For carriers
This feature facilitates the deployment of new services and helps carriers
to improve their competitive edge.
 For subscribers

This feature facilitates the registration of subscribers and allows

subscribers to use services conveniently.
Description
In the IMS HSS, an IRS consists of multiple IMPUs or PUSIs. If one IMPU
or PUSI in the IRS is registered with the network, the other IMPUs or PUSIs
in the IRS are registered automatically.
Assume that an IMPI is associated with two IMPUs (namely,
sip:hss@huawei.com and tel:+86779988667) and the two IMPUs belong to
the same IRS. If tel:+86779988667 is registered with the network,
sip:hss@huawei.com is registered automatically and can be used for setting
up session.
Dependency
1.2.3 WHFD-302210 Supporting Charging

Availability
Specification
None.
Summary
The IMS HSS stores the charging address information for subscribers.
Benefits
 For carriers
This feature allows carriers to specify different types of charging
addresses for different types of subscribers.
 For subscribers
None.
Description
The IMS HSS allows carriers to use the following types of charging
addresses:
 Primary Event Charging Function (PECF) address
 Secondary Event Charging Function (SECF) address

 Primary Charging Collection Function (PCCF) address

 Secondary Charging Collection Function (PCCF) address
Dependency
1.2.4 WHFD-302310 Supporting the Cx Interface

Availability
Specification
 3GPP TS29 228
 3GPP TS29 229
Summary
The IMS HSS interacts with the I-CSCF or S-CSCF through the Cx interface.
Benefits
 For carriers
None.
 For subscribers
None.
Description
The IMS HSS interacts with the I-CSCF or S-CSCF through the Cx interface
to implement initial registration, deregistration, and authentication of
subscribers and the LIR/LIA procedure.
Dependency
1.2.5 WHFD-302320 Supporting the Sh Interface

Availability

Specification
 3GPP TS29.328
 3GPP TS 29.329
Summary
The IMS HSS interacts with the Application Server (AS) through the Sh
interface.
Benefits
 For carriers
None.
 For subscribers
None.
Description
The IMS HSS interacts with the Application Server (AS) through the Sh
interface. Through the Sh interface, the AS requests or subscribes to the
subscription data from the IMS HSS and stores the service data in the
HSS9982. If the data stored in the IMS HSS is modified, the IMS HSS sends
a notification to the AS through the Sh interface.
Dependency
1.2.6 WHFD-302330 Supporting the Gi Interface

Availability
Specification
3GPP TS 33.978
Summary
The IMS HSS interacts with the GGSN through the Gi interface.
Benefits
 For carriers
None.

 For subscribers
None.
Description
The IMS HSS interacts with the GGSN through the Gi interface. The IMS
HSS stores the IP addresses assigned for UMTS subscribers in the PS domain
and interacts with the GGSN through the Gi interface to implement the Early
IMS Security authentication.
Dependency
1.2.7 WHFD-302340 Supporting the Si Interface

Availability
Specification
3GPP TS23.278
Summary
The IMS HSS interacts with the IM-SSF through the Si interface.
Benefits
 For carriers
None.
 For subscribers
None.
Description
The IMS HSS interacts with the IM-SSF through the Si interface. Through the
Si interface, the IM-SSF requests the CAMEL data from the IMS HSS. When
the data in the IMS HSS is modified, the IMS HSS sends a notification to the
IM-SSF.

Dependency
1.2.8 WHFD-302350 Supporting the MAP

Availability
Specification
3GPP TS29.002
Summary
The IMS HSS can serve as a VLR and retrieve the authentication vector and
PS/CS location information from the HLR.
Benefits
 For carriers
None.
 For subscribers
None.
Description
The IMS HSS can use MAP to obtain the authentication data, status, and
location information of the subscribers in the CS/PS domain from the HLR.
Dependency
1.2.9 WHFD-302410 Subscriber Barring

Availability
Specification
None.

Summary
The IMS HSS supports subscriber barring.
Benefits
 For carriers
The function helps carriers to provide more value-added services and
increase revenue.
 For subscribers
This function provides flexible call restriction means for subscribers.
Description
The subscriber barring status is configured on the provisioning system and
stored in the HSS. The HSS delivers the service code and status information
to the S-CSCF. Then, the S-CSCF implements the call barring.
Once a subscriber is barred, the subscriber cannot be registered with the
network of the carrier. The subscriber can be registered with the network only
after the subscriber is not barred.
Dependency
1.2.10 WHFD-302420 Registration Restriction

Availability
Specification
None.
Summary
The IMS HSS supports registration restriction.
Benefits
 For carriers
The function helps carriers to provide more value-added services and
increase revenue.
 For subscribers
None.

Description
The IMS HSS provides the registration restriction function, which prevents a
subscriber from being registered with the IMS network. Thus, only the
authorized subscriber can be registered with the network.
Dependency
1.2.11 WHFD-302510 IMS Roaming Restriction

Availability
Specification
None.
Summary
Carriers can configure data and perform operations on the HSS to restrict the
roaming of subscribers. This function facilitates mobility management.
Benefits
 For carriers
The function allows carriers to flexibly control the roaming of
subscribers and to implement service control of different subscribers. It
also facilitates the customization and provisioning of service packages.
 For subscribers
Subscribers can select the required services, thus preventing unnecessary
service charge.
Description
The IMS HSS provides the IMS roaming restriction function, which allows
carriers to specify the IMS networks to which an IMS subscriber can or
cannot roam.
The IMS HSS stores the roaming address list and roaming restriction
information of subscribers. The HSS verifies whether a subscriber is allowed
to roam by comparing the roaming information stored in the HSS and that
roaming information sent from the visited network.
Figure 1-1 illustrates the procedure in which the roaming of a subscriber is
restricted.

Figure 1-1 Roaming restriction procedure
1. When a UE initiates a register request, a Register message is sent from

the UE to the P-CSCF.
2. On receiving a Register message, the P-CSCF sends a Register message
to the I-CSCF.
3. The I-CSCF sends a User Authorization Request (UAR) message to the
HSS to query the information about the S-CSCF.
4. The HSS obtains the information abut the roaming rights of the
subscriber from the subscription information of the subscriber.
5. The HSS compares the roaming right information of the subscriber with
the roaming address information (P-CSCF address) contained in the
Register message. On determining that the subscriber is not allowed to
roam to the area, the HSS sends the I-CSCF a User Authorization
Answer (UAA) message indicating that the subscriber is not allowed to
roam to the area.
6. The I-CSCF sends a Forbidden message to the P-CSCF.
7. The P-CSCF sends a Forbidden message to the UE.
The IMS HSS also provides the roaming restriction template to facilitate the
management of roaming restriction. Through the roaming restriction template,
carriers can set the roaming rights for multiple subscribers. The IMS HSS
supports the configuration of subscriber-specific roaming restriction and NE-
specific roaming restriction.
Dependency

1.2.12 WHFD-302631 SCTP Multi-Homing in FE-BE

Communication
Availability
Specification
None.
Summary
The communication between the FE and the BE supports SCTP multi-homing.
This feature improves system reliability.
Benefits
 For carriers
This feature improves system reliability and reduces call loss. It helps to
improve customer satisfaction.
 For subscribers
None.
Description
SCTP multi-homing is adopted for the communication between the FE and the
BE of the IMS HSS. The SCTP link is established according to the data
configuration. Network ports work in load-sharing mode.
Dependency
1.2.13 WHFD-302633 Overload Control (Flow Control)

Availability
Specification
None.

Summary
The flow control function prevents congestion when the traffic volume
exceeds the upper threshold of the processing capability of the IMS HSS.
Benefits
 For carriers
This function enables carriers to enhance system reliability, avoid service
interruption resulting from surging traffics, and prevent the avalanche
effect.
 For subscribers
None.
Description
The IMS HSS adopts flow control when the load on the system is heavy. The
IMS HSS calculates the service processing capability of the system based on
the CPU load and the number of messages to be processed. The messages
exceeding the service processing capability are restricted.
The IMS HSS implements flow control based on the priorities of messages.
Only the initial messages exchanged in service procedures are discarded.
Thus, the service procedures can be implemented successfully.
Dependency
1.2.14 WHFD-310040 HTTP/SIP Digest Authentication

Availability
Specification
None.
Summary
The IMS HSS supports the HTTP/SIP Digest authentication. The
authentication vectors used in the HTTP/SIP Digest authentication are
username/password.
Benefits
 For carriers

Carriers can provide the HTTP/SIP Digest authentication for the PSTN
terminals, soft terminals, and SIP terminals that do not support the IMS
AKA or Early IMS authentication.
 For subscribers
None.
Description
The parameters used in the HTTP/SIP Digest authentication include the
following:
Digest = MD5 (HA1 + ":" + RAND + ":" + HA2)
HA1 = MD5 (username + ":" + realm + ":" + password)
HA2 = MD5 (Method + ":" + Digest-URI)
Table 1-1 describes the parameters used in the HTTP/SIP Digest

authentication.
Table 1-1 Parameters used in the HTTP/SIP Digest authentication

Parameter Description
realm It identifies the network on which the authentication is performed.

Method It specifies the message type. It is REGISTER for the HTTP/SIP Digest
authentication.
Digest-URI The Digest-URI equals the Request-URI carried in the REGISTER
message, that is, the SIP-URI of the S-CSCF.
username It specifies the username used in the HTTP/SIP Digest authentication.
password It specifies the password used in the HTTP/SIP Digest authentication.
Figure 1-2 shows the HTTP/SIP Digest authentication procedure.

Figure 1-2 HTTP Digest authentication procedure
Client P-CSCF I-CSCF HSS S-CSCF
Register Register
UAR
UAA
S-CSCF
selection Register
MAR
Calculate the HA1
MAA
(HA1)
Unauthorised
Unauthorised (RAND)
Unauthorised (RAND)
(RAND)
Calculate the Digest based
on the RAND, HA1, and HA2
Register
Register
UAR
(Digest)
(Digest) UAA
Register
(Digest)
Authentication
SAR
SAA
OK
OK
OK
The HTTP Digest authentication procedure is as follows:

2. The UE initiates an SIP registration request.
3. On receiving a Register message from the UE, the P-CSCF forwards the
message to the I-CSCF.
4. The I-CSCF obtains the capability set of the UE from the HSS, selects an
S-CSCF based on the capability set, and sends a Register message to the
S-CSCF.
5. The S-CSCF sends a Multimedia Authentication Request (MAR)
message to the HSS, requesting the authentication information.

6. On receiving an MAR message, the HSS calculates HA1 by using the

Digest-Realm, User Name, and Password.
The Digest-Realm is carried in the MAR message. The User Name and
Password are obtained from the HSS database.
7. The HSS sends HA1 in a Multimedia Authentication Answer (MAA)
message to the S-CSCF.
8. The S-CSCF saves HA1 and generates the RAND.
9. The S-CSCF sends the RAND to the UE through the I-CSCF and P-
CSCF.
10. The UE calculates HA1 and HA2, and then calculates the Digest by
using the RAND, HA1, and HA2. Then, the UE sends the Digest to the
S-CSCF through the I-CSCF and P-CSCF.
11. The S-CSCF calculates HA2 and uses RAND, HA1, and HA2 to
calculate the Digest. Then, the S-CSCF checks whether the value of
Digest is the same as the value of Digest calculated by the UE. If yes, the
authentication is successful.
12. The S-CSCF sends an OK message to the UE through the I-CSCF and P-
CSCF.
Dependency
None.
1.2.15 WHFD-310120 Enhanced Subscriber Tracing

Availability
Specification
None.
Summary
The IMS HSS supports the signaling tracing that is performed based on the
specified interface, port, connection, or subscriber.
Benefits
 For carriers
This function helps carriers to identify and rectify faults.
 For subscribers
None.

Description
The IMS HSS consists of the FE and BE. The signaling tracing of the FE
helps carriers to identify and rectify signaling problems. The signaling tracing
of the BE provides the information about the data services and data contents
provided by the BE to the FE.
The signaling tracing function facilitates fault identification during the routine
operation and maintenance of the system.
Dependency
None.
1.3 WHFD-303000 Basic Software Functions of the

SLF
The Subscription Locator Function (SLF) is an independent NE in the IMS
network. It stores the mapping between the subscription ID (IMPI, IMPU,
IMSI, MSISDN, PISI, WPUSI, or DPUSI) and the HSS address. The SLF can
be physically integrated with the HSS or independently deployed. The IMS
HSS incorporates the SLF function in the IMS network.
The SLF provides the following software functions:
 Support of protocols
 Subscriber data management
 Service provisioning through the SOAP interface
The SLF works in Re-direct mode. Figure 1-1 illustrates the service
processing procedure of the SLF.

Figure 1-1 Service processing procedure of the SLF
Home Network
P-CSCF I-CSCF SLF HSS
1. REGISTER
2. DX_SLF_QUERY
3. SLF database
lookup
4. DX_SLF_RESP
5. CX_QUERY
2. The P-CSCF sends a REGISTER message to the I-CSCF.

3. The I-CSCF sends the SLF a DX_SLF_QUERY message carrying the
user identity, which is obtained from the REGISTER message.
4. The SLF queries the HSS address based on the user identity.
5. The SLF sends the I-CSCF a DX_SLF_RESP message carrying the
address of the HSS that stores the subscriber data.
6. The I-CSCF sends a CS_QUERY message to the HSS to query the
subscriber data.
Huawei SLF can be integrated with the HSS or separately deployed.

Generally, the SLF is equipped with a large-capacity database to manage the
mapping between the subscription IDs and the HSS IDs of the entire network.
Therefore, separated deployment is recommended for the purpose of high
reliability.
The IMS HSS incorporating the SLF function supports the following
interfaces:
 Dx interface (I-CSCF/S-CSCF–SLF interface) (WHFD-303110)
 Dh interface (AS–SLF interface) (WHFD-303120)
1.3.2 I WHFD-303110 Supporting the Dx Interface

Availability

Specification
 3GPP TS29.228
 3GPP TS 29 328
Summary
The IMS HSS supports the Dx interface.
Benefits
 For carriers
None.
 For subscribers
None.
Description
The Dx interface, the interface between the SLF and the I-CSCF or S-CSCF,
supports Diameter over SCTP and Diameter over TCP. Through the Dx
interface, the SLF provides the routing information of the HSS for the I-CSCF
or S-CSCF.
Dependency
1.3.3 I WHFD-303120 Supporting the Dh Interface

Availability
Specification
 3GPP TS29.328
 3GPP TS 29 329
Summary
The IMS HSS supports the Dh interface.
Benefits
 For carriers
None.
 For subscribers

None.
Description
The Dh interface, the interface between the SLF and the Application Server
(AS), supports Diameter over SCTP and Diameter over TCP. Through the Dh
interface, the SLF provides the routing information of the HSS for the AS.
Dependency
2 Optional Features
2.1 WHFD-310111 Premium Authentication

The premium authentication provides the following authentication functions:
 IMS Authentication and Key Agreement (AKA) Authentication
It is an authentication scheme defined in the 3GPP. It allows IMS
subscribers to access the IMS network.
 Early AKA Authentication (EAA) Authentication
It allows the GSM or UMTS subscribers whose authentication data is
stored in the HLR to access the IMS network without changing the
authentication data in the SIM or USIM card when both the HSS and the
HLR are deployed on the IMS network.
 Early IMS Authentication (EIA) Authentication
It allows PS subscribers who do not support the IMS AKA authentication
scheme to access the IMS network and thus allowing the IMS network to
be compatible with the PS network.
 NASS Bundled Authentication (NBA) Authentication
It allows fixed network subscribers to access the IMS network through
the NASS.

 Trusted Access Authentication (TAA) Authentication

It allows PVS subscribers to access the IMS network without being
authenticated.
 CAVE AKA Authentication (CAA) Authentication
It allows soft terminals such as CDMA and Onekey subscribers to access
the IMS network.
2.1.1 WHFD-310010 IMS AKA Authentication

Availability
This feature is provided by the HSS9820 from V900R001.
Specification
None.
Summary
The HSS9820 supports the IMS AKA authentication scheme defined in 3GPP
TS33.203. This mechanism can be used for mutual authentication between the
IMS network and the UE.
Benefits
 For carriers
The IMS AKA authentication scheme allows the IMS UEs to access the
IMS network.
 For subscribers
None.
Description
The authentication vectors are generated by the HSS, which comprise:
 RAND (Random Number)
 XRES (Expected User Response)
 CK (Cipher Key)
 IK (Integrity Key)
 AUTN (Authentication Token)
Table 2-1 describes the authentication vectors.

Table 2-1 Authentication vectors

Authentication Description
Vector
RAND It is provided by the network to a UE. The UE uses the RAND to

calculate the authentication response parameter User Response (RES)
and security parameters IK and CK. The RAND has 16 bytes.
XRES It is the expected response of the network to a UE authentication
request. The XRES is compared with the RES to determine whether the
authentication is successful. The XRES has 4 to 16 bytes.
CK It is used to encrypt the signaling data that is considered to be
confidential, that is, the logical channel, thus securing the data access.
The CK has 16 bytes.
IK It secures the integrity of the signaling data. The IK has 16 bytes.
AUTN It provides information to a UE. Thus, the UE can authenticate a
network. The AUTN has 16 bytes.
Before an IMS subscriber uses the IP multimedia services, ensure that:

 At least one IMPU is registered.
 The IMPI passes the authentication at the IMS application layer.
The home network authenticates an IMS subscriber during the initial
registration of the subscriber.
Figure 2-2 shows the IMS AKA authentication process.

Figure 2-2 IMS AKA authentication process
UE P-CSCF I-CSCF HSS S-CSCF

Register Register UAR
(IMPI, IMPU)
(IMPI, IMPU)
UAA
S-CSCF selection Register
(IMPI, IMPU) MAR
Authentication
Vector selection
MAA
Auth_Challenge
Auth_Challenge
(IMPI, RAND, AUTN, IK, CK)
Auth_Challenge
(IMPI, RAND,
(IMPI, RAND, AUTN) AUTN, IK, CK)
Register
(IMPI, RES) Register
(IMPI, RES) UAR
UAA
Register
(IMPI, RES)
Authentication
SAR
SAA
OK
OK OK
The IMS AKA authentication procedure is as follows:

2. The UE originates a Register request.
3. The Proxy-Call Session Control Function (P-CSCF) receives the request
and then forwards it to the Interrogating-Call Session Control Function
(I-CSCF).
4. The I-CSCF obtains the capability set of the subscriber from the HSS,
identifies the S-CSCF serving the subscriber based on the capability set,
and then sends the registration request to the S-CSCF.
5. If the S-CSCF does not have valid authentication vectors, the S-CSCF
sends a request for authentication vectors to the HSS. The request
contains the required number (m) of authentication vectors, where m is at
least one and at most five. If the S-CSCF has valid authentication
vectors, the S-CSCF proceeds with 11).
6. On receiving the request from the S-CSCF, the HSS sends the
authentication vectors to the S-CSCF.
7. The S-CSCF selects an authentication vector and sends an
Auth_Challenge message to the I-CSCF. The message contains the IMPI,

RAND, AUTN, IK, and CK. The S-CSCF also stores the RAND for use
in case of a synchronization failure.
8. The I-CSCF forwards the Auth_Challenge message to the P-CSCF.
9. On receiving the Auth_Challenge message, the P-CSCF stores the IK
and CK and removes them from the message and forwards the message
containing the IMPI, RAND, and AUTN to the UE.
10. Upon receiving the Auth_Challenge message, the UE obtains the AUTN
and calculates the MAC and XMAC. The XMAC is calculated based on
the KI and RAND. Then, the UE checks whether the XMAC is the same
as the MAC and whether the SQN is within the correct range.
If both checks are successful, the UE completes the authentication towards the
network. If the checks fail, the UE re-initiates a registration procedure and does not
proceed with the subsequent operations.
11. The UE uses RES and some other parameters to calculate an
authentication response. This response is put into the Authorization
header and sent back to the P-CSCF.
12. On receiving the authentication response, the P-CSCF forwards the
authentication response to the I-CSCF. The I-CSCF obtains the address
of the S-CSCF serving the subscriber, and then sends the authentication
response to the S-CSCF.
13. On receiving the authentication response, the S-CSCF checks whether
the expected XRES is the same as the received authentication response.
− If the check is successful, the UE passes the authentication and the
IMPU is registered in the S-CSCF.
− If the check fails, the UE fails to pass the authentication. The S-CSCF
rejects the request by sending a 403 Forbidden response to the UE
and does not proceed with the subsequent operations.
14. The S-CSCF sends an SAR message to the HSS. Then, the HSS updates
the registration state of the UE.
15. The S-CSCF sends an OK message indicating authentication success to
the UE through the I-CSCF and P-CSCF.
Dependency
None.
2.1.2 WHFD-310020 Early IMS Authentication

Availability
Specification
None.

Summary
The HSS9820 supports the Early IMS authentication scheme defined in 3GPP
TS33.978.
Benefits
 For carriers
The Early IMS authentication scheme allows subscribers who do not
support the IMS AKA authentication scheme to access the IMS network.
 For subscribers
None.
Description
In the Early IMS authentication scheme, the HSS associates an IMPI with an
IP address allocated by the GGSN. On receiving the PDP Context Activation
Request from the UE, the GGSN allocates an IP address to the UE and sends
the IP address, MSISDN, and IMSI to the HSS over the Gi interface. On
receiving the IP address, MSISDN, and IMSI, the HSS searches for an
associated IMPI based on the association between the IMSI/MSISDN and the
IMPI, and then binds the IP address to the IMPI. The GGSN notifies the HSS
of the change or deactivation of the PDP Context, so that the HSS can update
the stored IP address.
On receiving the SIP Register request or some other SIP request of a certain
IMPU, the S-CSCF checks whether the IP address in the SIP header is the
same as that stored in the HSS. Based on the check result, the S-CSCF
determines whether to complete the authentication.
In the Early IMS authentication scheme, the GGSN can prohibit the UE from
using the IP address allocated during procedures other than PDP context
activation to send IP packets. This helps eliminate the security threat of IP
spoofing. The P-CSCF can check whether the IP address in the SIP header is
the same as the IP address in the IP packet header. If the two IP addresses are
different, the P-CSCF adds the IP address in the IP packet header to the
received parameter of the SIP header. This helps prevent the network address
transmission (NAT) between the GGSN and P-CSCF.
The Early IMS authentication scheme prevents an attacker from using his/her
own IP address and forging the IMS user identity of another person to access
the IMS network. It also prevents the attacker from forging an IP address, thus
eliminating the security threats.
Figure 2-1 shows the Early IMS authentication process.

Figure 2-1 Early IMS authentication process
UE GGSN HSS P-CSCF/I-CSCF S-CSCF

PDP Context
Accounting-
Activation Request
Request Start
Accounting-
PDP Context Request Answer
Activation Accept
SIP Register
GGSN checks for IP
address spoofing
SIP Register
Check source IP address
against SIP "via" field
SIP Register
MAR
Map IMPI to MSISDN or IMSI to
retrieve associated IP address
MAA
Check "received" IP
address against HSS
stored IP
SAR
SAA
OK
OK
OK
The functions of the I-CSCF in the Early IMS authentication are the same as
those in other authentication schemes. Therefore, the process related to the I-
CSCF is not shown in Figure 2-1.
The Early IMS authentication process is as follows:
2. The UE sends a PDP Context Activation Request to the GGSN.
3. The GGSN allocates an IP address to the UE and then sends an
Accounting-Request START message to the HSS. The message carries
the allocated IP address, MSISDN, and IMSI.
4. On receiving the Accounting-Request START message, the HSS
searches for an associated IMPI based on the association between the
IMSI/MSISDN and the IMPI, and then binds the IP address to the IMPI.
5. After the IP address is bound to the IMPI, the HSS sends an Accounting-
Request Answer message to the GGSN.
6. The GGSN sends a PDP Context Activation Accept message to the UE.
The message carries the allocated IP address.

7. The UE sends a SIP Register request to the GGSN. In the message, the
parameter sent-by of the via field contains the IP address, and from
contains the IMPU of the subscriber.
 The GGSN checks whether the IP address contained in the IP packet
header is the same as the address allocated during the PDP context
activation. If the two IP addresses are different, the SIP Register request
is rejected.
If the two IP addresses are the same, the authentication proceeds.
8. The GGSN forwards the SIP Register request to the P-CSCF.
 The P-CSCF checks whether the IP address in the IP packet header
is the same as that contained in sent-by. If the two IP addresses are
different, the P-CSCF adds the parameter received to the via field. In
addition, received is set to the IP address that is contained in the IP
packet header.
If the two IP addresses are the same, the authentication proceeds.
9. The P-CSCF sends the SIP Register request to the I-CSCF.
10. The I-CSCF obtains the address of the S-CSCF from the HSS and then
forwards the registration request to the S-CSCF.
11. The S-CSCF sends an MAR message to the HSS. The message contains
the IMPU. In addition, Authentication-Scheme AVP is set to Early-
IMS-Security. This enables the HSS to authenticate the subscriber by
using the Early IMS authentication. Using the IMPI, the HSS searches
for the stored IP address, which is then added to an MAA message. The
IP address is the one allocated during the PDP context activation.
12. The HSS sends the MAA message to the S-CSCF. The message contains
the IP address.
13. The S-CSCF checks whether the via field in the SIP Register request
received in step 9 contains received.
If received is contained, the S-CSCF checks whether the IP address in
received is the same as that stored in the HSS.
− If the two IP addresses are different, the S-CSCF sends Forbidden (a
response of failed authentication) to the UE.
− If the two IP addresses are the same, the S-CSCF sends OK (a
response of successful authentication) to the UE.
If received is not contained, the S-CSCF checks whether the IP address
in sent-by is the same as that stored in the HSS.
− If the two IP addresses are different, the S-CSCF sends Forbidden (a
response of failed authentication) to the UE.
− If the two IP addresses are the same, the S-CSCF sends OK (a
response of successful authentication) to the UE.
Dependency
None.

2.1.3 WHFD-310040 NASS Bundled Authentication

Availability
Specification
None.
Summary
The HSS9820 supports the NASS Bundled authentication scheme defined in
TISPAN ETSI TS 183 033. The NASS Bundled authentication scheme is
applicable to the scenario where a fixed network subscriber accesses the IMS
network through the NASS.
Benefits
 For carriers
The NASS Bundled authentication scheme enables subscribers to access
the IMS network through the NASS to enjoy the various services.
 For subscribers
None.
Description
In the NASS Bundled authentication scheme, the parameter Line ID is used
to authenticate subscribers. Line ID stores location information and identifies
the location that the subscriber can access. The subscriber can access the IMS
network from multiple locations as one IMPI can associate with multiple Line
IDs on the HSS.
Figure 2-1 shows the NASS Bundled authentication process.

Figure 2-1 NASS Bundled authentication process
CLF UE P-CSCF I-CSCF HSS S-CSCF
Register
CLF Query(IP address)
CLF Response(Location info)

Register
P-Access-Network- UAR
Info=Location info
UAA
S-CSCF selection
Register
P-Access-Network-
Info=Location info
MAR
(User identity)
User profile check
MAA
(Location info)
Compare
location info
SAR
SAA
OK
OK
OK
For a fixed network subscriber, the association between the IMPI and the Line
ID is configured on the HSS. The Line ID includes the number of the access
port and the identity of the access equipment. It uniquely identifies a fixed
network UE. After a UE passes the authentication of the NASS and obtains an
IP address, the Connectivity Session Location and Repository Function (CLF)
stores the association between the Line ID and the allocated IP address.
The NASS Bundled authentication process is as follows:
2. The UE sends an IMS registration request to the P-CSCF. The request
carries the IP address of the UE.
3. The P-CSCF requests the CLF for the Line ID of the UE.
4. The P-CSCF adds the Line ID to the P-Access-Network-Info field in the
registration request and then sends the request to the I-CSCF.
6. On receiving the request, the S-CSCF saves the Line ID contained in the
P-Access-Network-Info field.

7. The S-CSCF sends an MAR message to the HSS for the NASS Bundled
authentication information, that is, the Line ID configured in advance.
8. On receiving the MAR message, the HSS detects all the Line IDs
associated with the IMPI and then sends an MAA message to the S-
CSCF. The MAA message carries the Line IDs.
 The S-CSCF compares the Line ID sent from the P-CSCF with the
Line IDs sent from the HSS. If the Line ID sent from the P-CSCF
matches one of the Line IDs sent from the HSS, the authentication is
successful.
If the Line ID sent from the P-CSCF does not match any of the Line IDs
sent from the HSS, the registration is rejected.
Dependency
None.
2.1.4 WHFD-310150 SIM/USIM Authentication

Availability
Specification
None.
Summary
The HSS9820 supports the SIM/USIM authentication scheme that uses the
SIM or USIM card for authentication.
Benefits
 For carriers
The SIM/USIM authentication scheme allows the GSM or UMTS
subscribers to access the IMS network without changing the
authentication data in the SIM or USIM card. The scheme does not
require authentication data to be added again on the IMS network. This
helps prevent repetitive definition of subscribers and decrease the
difficulty in BOSS operations.
 For subscribers
None.

Description
On a network that connects to the HSS and the HLR, the data of different
subscribers is saved on the HSS and HLR. The HSS saves only the data of
IMS subscribers, such as the IMPIs and IMPUs of GSM or UMTS
subscribers, whereas the HLR saves only the data of PS or CS subscribers,
such as the IMSI, MSISDN, and authentication data.
When a PS or CS subscriber sends a registration request to the IMS network,
the HSS requests the HLR for authentication vectors and then forwards the
vectors to the S-CSCF. This requires that the HSS be able to find the
corresponding IMSI of the PS or CS subscriber based on the IMPI or IMPU
and to send a Mobile Application Part (MAP) request to the HLR for
authentication vectors.
The HLR responds with authentication vectors in triplets in the GSM network
and in quintets in the UMTS network. This scheme is termed Early AKA
authentication.
Error: Reference source not found shows the Early AKA authentication
process.

Figure 2-1 Early AKA authentication process
Visited Network Home Network
UE P-CSCF I-CSCF HSS S-CSCF HLR
Register
Register
UAR
UAA
S-CSCF selection
Register
MAR
MAP_SAI_REQ
MAP_SAI_RSP
MAA
Unauthorised
Unauthorised
Unauthorised
Register
Register
UAR
UAA
Register
Authentication
SAR
SAA
OK
OK
OK

The Early AKA authentication process is as follows:

2. The UE sends a registration request to the P-CSCF.
3. On receiving the registration request, the P-CSCF forwards the request to
the I-CSCF.
5. On receiving the request, the S-CSCF sends an MAR message to the
HSS.
6. Based on Authentication-Scheme AVP in the MAR message, the HSS
determines that the Early AKA authentication is used. Then, it detects
the IMSI based on the IMPI and sends the HLR a MAP_SAI_REQ
message to request for authentication vectors.
7. The HLR sends the authentication vectors to the HSS through a
MAP_SAI_RSP message.
8. The HSS sends the obtained authentication vectors to the S-CSCF
through an MAA message.
The MAA message can carry only authentication quintets.

 If the HLR returns the authentication triplets, the HSS converts the triplets into
quintets and then sends the quintets to the S-CSCF through the MAA message.
 If the HLR returns the authentication quintets, the HSS directly sends the quintets
to the S-CSCF through the MAA message.
9. Based on the principle of First In First Out, the S-CSCF selects one
authentication vector to send an authentication request to the I-CSCF.
10. The I-CSCF forwards the authentication request to the P-CSCF.
11. On receiving the request, the P-CSCF saves the IK and CK, and then
sends the request to the UE.
12. On receiving the request, the UE uses the AUTN to authenticate the IMS
network. (The UE calculates the Expected Message Authentication Code
(MAC) based on the AUTN and calculates the XMAC based on the KI
and RAND. Then, the UE checks the consistency between XMAC and
MAC and checks the validity of the SQN. )
 If the XMAC and MAC are consistent and the SQN is valid, the UE completes the
authentication of the IMS network.
 If the HLR returns the authentication triplets, the value of the AUTN is 0. In this
case, this step is omitted.
 If the check on XMAC, MAC, and SQN fails, the UE initiates the registration
procedure again without proceeding with the following steps.
13. After the network passes the authentication, the UE calculates the RES
by using the RAND and sends the RES to the P-CSCF through the
registration request.
14. On receiving the RES, the P-CSCF forwards it to the I-CSCF. The I-
CSCF obtains the address of the S-CSCF from the HSS and then
forwards the RES to the S-CSCF.

15. On receiving the RES, the S-CSCF checks whether the XRES is the
same as the received RES. If the XRES and the RES are the same, the
UE passes the authentication.
16. The S-CSCF sends a message to the UE indicating successful
authentication.
Dependency
None.
2.1.5 WHFD-310060 Trusted Access Authentication

Availability
Specification
None.
Summary
The HSS9820 provides the trusted access authentication scheme, which
allows certain subscribers to access the IMS network without being
authenticated.
Benefits
 For carriers
This feature simplifies the session flow, and thus improves the
performance of the entire network.
 For subscribers
None.
Description
When a subscriber accesses the IMS network from a trusted location, the HSS
does not authenticate the subscriber. This can simplify the service procedure.
Dependency
This feature is applicable only when the PVS solution is adopted.

2.1.6 WHFD-310071 CAVE AKA Authentication

Availability
Specification
3GPP2 SS0127-0
Summary
The CAVE AKA authentication scheme allows UEs such as CDMA terminals
and Onekey soft terminals to access the IMS network.
Benefits
 For carriers
The CAVE AKA authentication scheme allows CDMA and Onekey
subscribers to access the IMS network to enjoy services. This enriches the
access mode of the IMS network.
 For subscribers
None.
Description
The HSS9820 adopts the CAVE AKA authentication scheme when the
following requirements are met:
 The UEs support the CAVE AKA authentication.
 The shared secret data (SSD) of the removable user identity modules (R-
UIM) is consistent with the SSD of the HLR/AC.
 The HSS9820 supports the CAVE AKA authentication.
The CDMA subscribers must meet the following requirements:
 The CDMA subscribers are defined in the HSS9820.
 The authentication function of the CDMA subscribers is enabled in the
HLR on the CDMA network and the subscribers are provided with the
voice privacy (VP) service and signaling message encryption (SME)
service.

Figure 2-1 CAVE AKA authentication process
The CAVE AKA authentication process is as follows:

1. The UE sends a Register message to the P-CSCF.
2. The P-CSCF forwards the Register message to the I-CSCF.
3. The I-CSCF sends a user authorization request (UAR) message to the
HSS, requesting the information about the S-CSCF that serves the subscriber.
4. The HSS responds to the I-CSCF with a user authorization answer
(UAA) message, which carries the domain name or the capability set of the S-
CSCF that serves the subscriber.
5. The I-CSCF assigns an S-CSCF and sends a Register message to the S-
CSCF.
6. The S-CSCF sends a multimedia authentication request (MAR) message
to the HSS to request the authentication data.
7. The HSS sends an Authentication data message to the HLR/AC to obtain
the authentication data RANDU, AUTHU, SMEKEY, and CDMAPLCM.
8. The HSS generates the AKA_KEY based on the authentication data and
calculates the authentication quintuplets (AUTN, RAND_AKA, XRES, CK,
and IK). Then the HSS sends a multimedia authentication answer (MAA)
message to the S-CSCF. The MAA message carries the authentication
quintuplets.
9. The S-CSCF sends a 401 message to the I-CSCF to authenticate the UE.
The 401 message carries the authentication data AUTN, RAND_AKA, CK,

and IK. The S-CSCF reserves the authentication data XRES to compare the
value of XRES and the value of the RES that is carried in the authentication
response to be sent from the UE.
10. The I-CSCF forwards the 401 message to the P-CSCF.
11. The P-CSCF forwards the 401 message to the UE.
12. The UE calculates the RES based on the KEYSM stored on the UE and
the unique random variable (RANDU) carried in the message and then sends a
Register message to the P-CSCF.
13. The P-CSCF forwards the Register message to the I-CSCF.
14. The I-CSCF sends a UAR message to the HSS, requesting the
information about the S-CSCF that serves the subscriber.
15. The HSS responds to the I-CSCF with a UAA message, which carries the
domain name or the capability set of the S-CSCF that serves the subscriber.
16. The I-CSCF assigns an S-CSCF and sends a Register message to the S-
CSCF.
17. The S-CSCF compares the value of the RES carried in the Register
message and the value of the XRES stored in the S-CSCF. If the value is the
same, the S-CSCF sends a server assignment request (SAR) message to the
HSS, requesting the HSS to change the registration status of the UE to
Registered.
18. The HSS sends a server assignment answer (SAA) message to the S-
CSCF. The SAA message carries the user profile of the UE.
19. The S-CSCF saves the user profile and responds to the I-CSCF with a
200 OK message.
20. The I-CSCF forwards the 200 OK message to the P-CSCF.
21. The P-CSCF forwards the 200 OK message to the UE.
Dependency
The UE must support the CAVE AKA authentication.
2.2 WHFD-310211Roaming Awareness

2.2.1 WHFD-310100 PS/CS Location Information
Retrieving
Availability

Specification
None.
Summary
The HSS9820 supports the obtaining of location information of a PS or CS
subscriber from the HLR on the existing network. The HSS9820 sends the
location information to the AS over the Sh interface.
Benefits
 For carriers
With the convergence of the IMS network and GSM/UMTS network, the
IMS network frequently requests the GSM/UMTS network for
subscriber information. The HSS9820 supports the retrieving of
subscriber information from the HLR. The HSS9820 sends the subscriber
information to the AS over the Sh interface. This facilitates the
deployment of new services.
 For subscribers
None.
Description
When the AS requests the HSS for the location information of a PS or CS
subscriber, the HSS9820 obtains the location information from the HLR
through the MAP-AnyTimeInterrogation message and forwards the location
information to the AS.
Dependency
None.
2.2.2 WHFD-310140 NASS State/Location Info

Management
Availability
Specification
None.

Summary
The HSS9820 supports the NASS state and location information management.
The HSS sends the NASS state or location information to the AS over the Sh
interface.
Benefits
 For carriers
This feature provides the AS with various types of information and
facilitates the deployment of new services.
 For subscribers
None.
Description
During the UE registration or deregistration process, the HSS9820 obtains the
location information of a NASS subscriber and sets the registration status of
the subscriber. Over the Sh interface, the HSS sends the state and location
information of the subscriber to the AS.
Dependency
None.
2.2.3 WHFD-310110 NASS Nomadism Control

Management
Availability
Specification
None.
Summary
The HSS9820 supports the NASS nomadism control management so that
carriers can control the accessing of the IMS network by the fixed network
subscribers. That is, the HSS9820 supports the setting of black and white lists
in the nomadism address list.
Benefits
 For carriers

This feature allows carriers to control the accessing of the IMS network
by the fixed network subscribers, thus enhancing the access control
capability of carriers and mobilizing the fixed network subscribers.
 For subscribers
None.
Description
The HSS stores the nomadism address list and the nomadism authority
information of the subscribers.
When a subscriber registers the location, the registration message carries the
access address information of the fixed network. The HSS compares the
reference information and nomadism information in the subscription data with
the address information in the message to verify the nomadism authority of
the subscriber. Meanwhile, the HSS updates the nomadism status and dynamic
nomadism location information of the subscriber.
When the access network cannot report the location information of the
subscriber to the IMS network, the IMS network can provide the location
service for subscribers based on the location information specified upon
subscription. Such location information is called reference location
information. The IMS network can implement the NASS nomadism control
over a subscriber based on the reference location information.
When the HSS checks the NASS nomadism authority of a subscriber, it
matches the reference location information and then the nomadism template
information.
Dependency
None.
2.3 WHFD-310080 Public Service Identities

Availability
Specification
None.
Summary
The IMS network supports various services such as presence, chat, and
messaging. The Public Service Identity (PSI) identifies the services that are
provided by the AS.

Benefits
 For carriers
This feature enables carriers to introduce on the IMS system various
value-added services provided by the third parties. This helps the carriers
to widen the subscriber base and increase revenues.
 For subscribers
This feature allows subscribers to enjoy various value-added services.
Description
The PSI user identities include the Private Service Identity (PISI) and the
Public Service Identity (PUSI).
Figure 2-1 shows the association between PISIs and PUSIs.
Figure 2-1 Association between PISIs and PUSIs
PISI: Private Service Identity PUSI: Public Service Identity

IRS: Implicitly Registered Set AS: Application Server
The PISI has the following characteristics:

 The PISI is allocated by carriers.
 The PISI is the permanent subscriber data. It is stored in the HSS and the
S-CSCF.
 The PISI contains charging address information but no authentication
information.
 One PISI can be associated with multiple PUSIs.
 The PISI uses the NAI format.

NAI format: username + @ + domain name

For example, username@huawei.com
The PUSI has the following characteristics:
 The PUSI belongs to an AS.
 The PUSIs are classified into two types, namely, wildcard PSI (WPUSI)
and distinct PUSI (DPUSI).
− A WPSI contains wildcards, for example, as!.*!@domain.net. It can
be as1@domain.net or as2@domain.net.
− A DPUSI does not contain wildcards, for example, as1@domain.net.
 The PUSI is the permanent subscriber data. It is stored in the HSS and
the S-CSCF.
 The attributes of the PUSI include the barring status and the IRS ID.
 The PUSI and IMPU share the same service profile data.
 The PUSIs of the same PSI subscriber can be added to the same
implicitly registered set; however, the implicitly registered set formed by
the PUSIs does not have a default PUSI.
 One PUSI can map one AS address or none.
 The service profile associated with one PUSI cannot be shared by other
PUSIs.
 The PUSI uses the SIP URI or TEL URI format.
SIP URI format: sip: + user information + @ + host
Here, host can be a domain name, an IPv4 address, or an IPv6 address.
For example, sip:user@huawei.com
TEL URI format: tel: + number
Here, number can be a global number or a local number.
If a global number is used, prefix the character + in the global number.
For example, tel:+36120012345678.
If a local number is used, the PUSI must contain the parameter phone-
context, which indicates the area to which the number belongs. For
example, tel:12345678;phone-context=+361200.
Dependency
None.
2.4 WHFD-310070 Shared Public User Identities

Availability

Specification
None.
Summary
The HSS supports the shared IMS Public User Identity (IMPU).
Benefits
 For carriers
This feature allows subscribers to use services such as car phone,
through various terminals of the same user identity.
 For subscribers
None.
Description
On the HSS, a shared IMPU must be associated with all IMPIs in the IMS
subscription.
Figure 2-1 shows the association between a shared IMPU and IMPIs.
Figure 2-1 Association between a shared IMPU and IMPIs
IMPU 2 can be associated with both IMPI 1 and IMPI 2.
Dependency
None.

2.5 WHFD-310150 CSCF Data Backup

Availability
Specification
None.
Summary
The HSS9820 can work with Huawei CSCF to provide the geographic
redundancy solution.
Benefits
 For carriers
The network reliability is strengthened.
 For subscribers
None.
Description
To achieve geographic redundancy, Huawei CSCF sends certain part of
dynamic data to the HSS for storage through the Cx interface, and retrieves
the data stored in the HSS after the switchover. This ensures that the services
are not interrupted during the switchover.
The HSS9820 backs up the redundancy data and sends the data to the S-CSCF
upon request. The redundancy data contains the Path and Contact header
fields defined during the registration. The S-CSCF sends an SAR message to
download from or upload to the HSS the redundancy data through the Cx
interface. The following figure shows the related message flow.

Dependency
The HSS works with Huawei CSCF to implement this feature.
2.6 WHFD-310160 IM-SSF CAMEL subscriber

Availability
Specification
None.

Summary
The HSS9820 supports the subscription and delivery of the CAMEL data,
thus helping to provide IN services over the IMS network.
Benefits
 For carriers
This feature helps to provide more IN services for IMS subscribers.
 For subscribers
None.
Description
The HSS supports the subscription and management of the CAMEL data such
as O-IM-CSI and VT-IM-CSI. It sends the CAMEL data to the IM-SSF
through the Si interface and facilitates the IMS network to implement IN
services. The MAP-based Si interface complies with 3GPP TS 23.278 and
3GPP TS 29.002. The following figure shows the interfaces between the HSS
and other MEs.
gsmSCF The gsmSCF is not involved in

this procedure.
IM-SSF
imcnSSF
Si interface (MAP)
HSS Register_
IM_SSF
Cx interface (DIAMETER) ISC interface
Mobile S-CSCF
Station SIP
The message flow is as follows:

1. When receiving a third-party registration request of a subscriber from the
S-CSCF, the IM-SSF sends an MAP message to the HSS through the Si
interface, requesting to subscribe to the CAMEL data of the subscriber.

2. After receiving the request from the IM-SSF, the HSS returns the
required CAMEL data to the IM-SSF. If the CAMEL data of the
subscriber is updated, the HSS sends the updated CAMEL data to the
corresponding IM-SSF automatically.
Dependency
None.
2.7 WHFD-310210 Sh interface supports Notif-Eff

featurefeature
Availability
Specification
None.
Summary
The HSS9820 supports the Notif-Eff feature defined in 3GPP TS29.328.
Benefits
 For carriers
This feature improves the performance of the Sh interface and in turn
improves the service performance of the entire network.
 For subscribers
None.
Description
The HSS can deliver multiple repository data entries to the AS through one
message over the Sh interface.
The HSS supports Notif-Eff feature of the following messages: UDR/UDA,
SNR/SNA, and PNR/PNA.
For details on the service procedure, see 3GPP TS 29.328 v8.2.0.
Dependency
The implementation of this feature requires the cooperation of the AS.

2.8 WHFD-310230 Supporting IPv6

Availability
Specification
3GPP TS 29.228
Summary
This feature enables the HSS9820 to support the IPv6 address type.
Benefits
 For carriers
The IPv6 address type is required when the IPv4 address resources is
insufficient. Huawei IMS solution and the HSS9820 support IPv6-based
applications, which meet the demand of carriers to expand network
deployment.
 For subscribers
None.
Description
The HSS9820 supports the IPv6-based Early IMS authentication and NBA
authentication.
The HSS9820 can process the messages that contain the IPv4 or IPv6 address
type at the Diameter signaling layer.
Dependency
None.
2.9 WHFD-310240 Geographic Node Redundancy

Availability
Specification
None.

Summary
The HSS9820 supports the geographic node redundancy solution, which
allows the active HSS and the redundancy HSS to be deployed in different
geographical locations. In addition, the FE and the BE can be separately
deployed. When the subscriber data in the active HSS is updated, the updated
data is sent to the redundancy HSS in real time. Thus, data synchronization
between the active and redundancy HSSs is ensured. The HSS also provides
the periodic data consistency check function to ensure data consistency
between the active and redundancy HSSs.
Benefits
 For carriers
The HSS adopting the geographic node redundancy solution has higher
reliability and security. This reduces the CAPEX and OPEX of carriers
and improves their competitiveness.
 For subscribers
None.
Description
The HSS9820 supports two types of geographic node redundancy solutions:
 1+1 mated redundancy solution
In this solution, the FE and the BE are integrated. Two HSSs working in
active/redundancy mode implement data synchronization over the data
layer. The active HSS processes all the services whereas the redundancy
HSS does not process services in normal conditions.
 1+1 load-sharing redundancy solution
In this solution, the FE and the BE are integrated. Two HSSs working in
load sharing mode implement data synchronization over the data layer.
The two HSSs process services simultaneously, and each HSS backs up
the data of the other.
The geographic node redundancy solutions supported by the HSS9820 have
the following features:
 Using dedicated IP channels to automatically synchronize dynamic and
static data between the active and redundancy HSSs in real time
 Providing the data consistency check function to ensure data consistency
 Supporting automatic switchover between the active HSS and
redundancy HSS, which ensures uninterrupted services
Dependency
None.

Huawei SingleSDB V100R003C01 IMS HSS Feature Description

Uploaded by

Copyright:

Available Formats

You might also like

Huawei SingleSDB V100R003C01 IMS HSS Feature Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei SingleSDB V100R003C01 IMS HSS Feature Description

Uploaded by

Copyright:

Available Formats

Huawei SingleSDB V100R003C01 IMS HSS

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 1.0 (2024-06-17) Huawei Proprietary and Confidential Page 3 of 74

1.1 WHFD-301000 Basic Software Features of the

1.1.1 WHFD-301111 Supporting Diameter over SCTP

2024-06-17 HUAWEI Confidential Page4, Total74

1.1.2 WHFD-301112 Supporting Diameter over TCP

2024-06-17 HUAWEI Confidential Page5, Total74

1.1.3 WHFD-301121 Supporting RADIUS over UDP

2024-06-17 HUAWEI Confidential Page6, Total74

1.1.4 WHFD-301131 Supporting SIGTRAN over SCTP

2024-06-17 HUAWEI Confidential Page7, Total74

1.1.5 WHFD-301132 Supporting MAP

2024-06-17 HUAWEI Confidential Page8, Total74

1.1.6 WHFD-301140 Supporting SCTP Multi-Homing

1.1.7 WHFD-301210 IMPI

2024-06-17 HUAWEI Confidential Page9, Total74

1.1.8 WHFD-301211 IMPI in NAI Format

2024-06-17 HUAWEI Confidential Page10, Total74

1.1.9 WHFD-301221 IMPU in SIP URI format

1.1.10 WHFD-301222 IMPU in E.164/TEL URI Format

2024-06-17 HUAWEI Confidential Page11, Total74

1.1.11 WHFD-301310 IPv4

2024-06-17 HUAWEI Confidential Page12, Total74

1.1.12 WHFD-301410 Equipment Management

2024-06-17 HUAWEI Confidential Page13, Total74

1.1.13 WHFD-301420 Fault Management

2024-06-17 HUAWEI Confidential Page14, Total74

 Enable or disable alarm shielding manually.

1.1.14 WHFD-301430 Configuration Management

2024-06-17 HUAWEI Confidential Page15, Total74

1.1.15 WHFD-301440 Performance Management

1.1.16 WHFD-301450 Log Management

2024-06-17 HUAWEI Confidential Page16, Total74

1.1.17 WHFD-301460 Pool-Based Network Management

2024-06-17 HUAWEI Confidential Page17, Total74

1.1.18 WHFD-301510 Automatic or Manual Board

2024-06-17 HUAWEI Confidential Page18, Total74

be manually or automatically switched over to the redundancy board for

1.1.19 WHFD-301520 Interface Redundancy

1.1.20 WHFD-301521 Supporting Multiple IP

2024-06-17 HUAWEI Confidential Page19, Total74

1.1.21 WHFD-301522 Supporting Multiple Signaling

2024-06-17 HUAWEI Confidential Page20, Total74

1.1.22 WHFD-301523 Redundancy of Gigabit Network

1.1.23 WHFD-301530 One Logical Port Shared by

2024-06-17 HUAWEI Confidential Page21, Total74

1.1.24 WHFD-301540 One Network Adapter Shared by

2024-06-17 HUAWEI Confidential Page22, Total74

1.1.25 WHFD-301550 Hard Disk Redundancy

2024-06-17 HUAWEI Confidential Page23, Total74

1.1.26 WHFD-301620 Distributed Structure of Software

2024-06-17 HUAWEI Confidential Page24, Total74

1.1.27 WHFD-301650 Automatic Load Balancing

2024-06-17 HUAWEI Confidential Page25, Total74

1.2 WHFD-302000 Basic Software Functions of the

2024-06-17 HUAWEI Confidential Page26, Total74