(Basic Training) HSS9820 Data Configuration ISSUE3.30

HSS9820 Data
Configuration
www.huawei.com
Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

References
 HUAWEI HSS9820 Home Subscriber Server Local Device
Commissioning-(V900R008C01)
 HUAWEI HSS9820 Home Subscriber Server Interworking

Commissioning-(V900R008C01).
Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved. Page2
Objectives
 Upon completion of this course, you will be able to:
 Perform the HSS hardware configuration
 Perform the HSS FE and BE local configuration
 Perform the HSS interworking configuration
Configuration Process
Contents
1. HSS9820 Hardware Data Configuration
2. HSS9820 Local Data Configuration
3. HSS9820 Interconnection Data Configuration
Hardware Configuration
 Device number Integrated rack 00 Service rack 01
 Rack number Power distribution

Filler panel
subrack
 Subrack number
extension subrack 01 extension subrack 04
Basic subrack 00 extension subrack 03
LAN switch/hard disk extension subrack 02

Array/KVMS/filler panel
Filler panel
Hardware Configuration
 Subrack number
 In the actual deployment, the subrack numbers are determined by
the 8-bit DIP switches on the SDM board
switch 1 2 3 4 5 6 7 8
Subrack No.
0 off off off off off off off off
1 off off off off off off off on
2 off off off off off off on off
3 off off off off off off on on
… … … … … … … … …
255 on on on on on on on on
Hardware Configuration Command
Navigation
 Hardware configuration command is belong to OMS object
tree
ME: OMS2600
Navigation Tree
Hardware
ADD RACK
management
ADD SUBRACK
ADD BRD
Example
Slot No. 0 1 2 3 4 5 6 7 8 9 10 11 12 13
Back panel U U U U S S
S S S S W W
card position
I I I I I I
1 1 1 1
U U U U S S U U U U
board name
Front Panel card Position
Physical Process group
P P P P W W P P P P
B B B B U U B B B B
A A A A A A A A
2 2 2 2 0 2 0 2
O M O M H U H U
M N M N S S S S
name
U A U A H D H D
H H I I I I
U U U D U D
Slot No. 0 1 2 3 4 5 6 7 8 9 10 11 12 13
Example
 Data Configuration
 Step1: Add Rack and Subrack
 select <ME: OMS2600>  <Navigation Tree>  < MML

commands>
– ADD RACK: RN=0, RNM="rack0", POSNUM=0, ROWNUM=0,
COLNUM=0, MOG="public";
– ADD SUBRACK: SRN=0, RN=0, PN=0, SBVER=T8280,

SRMUSN1=0, SRMUSN2=1,SWFBRDT=SWU0,
SWBBRDT=SWI0, SRNNM="basic subrack", MOG="public";
~ SRMU is system reliability management unit
Example
 Step 3：Add board
 For FE
– ADD BRD: SRN=0, SN=10, METYPE=HSS, FBRDHTYP=UPBA0,
BBRDHTYP=USI1, APPTYPE=HSHIU, MOG="public",
REFERABLE=YES;
– ADD BRD: SRN=0, SN=12, METYPE=HSS, FBRDHTYP=UPBA0,

BBRDHTYP=USI1, APPTYPE=HSHIU, MOG="public",
REFERABLE=YES
Example
 Physical board & Application Type ( FE )
Physical board Application type Process Configuration

3DPU+1HSF+4HCF+1DSG+1SLF+
HSHIU
1BSG+1CCU
HSHCS 2*DPU+1*HSF+1*DSG+4*HCF
UPB0
HSSCS 2*DPU+6*HSF+1*DSG+2*SLF
HSBCU 1*DPU+2*BSG+2*CCU
HSDPU 4DPU
3DPU+1HSF+8HCF+1DSG+2SLF+
HSHIU
1BSG+1CCU
HSHCS 2*DPU+2*HSF+2*DSG+8*HCF
UPBA0
HSSCS 2*DPU+12*HSF+2*DSG+4*SLF
HSBCU 1*DPU+4*BSG+4*CCU
HSDPU 8DPU
Example
 For BE
– ADD BRD: SRN=0, SN=11, METYPE=USCBD,
FBRDHTYP=UPBA2, BBRDHTYP=USI1, APPTYPE=USDID,
MOG="public", REFERABLE=YES;
– ADD BRD: SRN=0, SN=13, METYPE=USCDB,

FBRDHTYP=UPBA2, BBRDHTYP=USI1, APPTYPE=USDID,
MOG="public", REFERABLE=YES
Example
 Physical board & Application Type ( BE )
1DPU+1DRU+1DSU+1NDF+1PGW+1DSG
USDIU
+1DBG+11DTL
USDMU 1*NDF+1*DBG
USPGW 1*DPU+4*PGW+1*DTL
UPB0
USDRU 1*DPU+1*DSG+4*DRU
USDSU 3*DSU
USRSU 1*DPU+1*DSG+2*DRU+2*DSU
1DPU+2DRU+7DSU+1NDF+1PGW+1DSG
USDIU
+1DBG+11DTL
USDMU 1*NDF+1*DBG
USPGW 1*DPU+8*PGW+1*DTL
UPBA2
USDRU 1*DPU+3*DSG+10*DRU
USDSU 10*DSU
USRSU 1*DPU+1*DSG++4*DRU+8*DSU
Example
Physical board & Application Type ( BE )

1DPU+1DRU+1DSU+1NDF+1PGW+1DSG+1DBG
USDID
UPB0 +11DTL
USDMD 1*NDF+1*DBG
1DPU+2DRU+7DSU+1NDF+1PGW+1DSG+1DBG
USDID
UPBA2 +11DTL
USDMD 1*NDF+1*DBG
Tips: The USDIU/USDMU application types are used in disk array

environment;
the USDMD/USDID application types are used in non-disk-array
environment.
Example
 Process configuration of the BE when the FE and BE are
deployed on the same board
– ADD BRD: SRN=0, SN=1, METYPE=MNB_IMS,
FBRDHTYP=UPBA2, BBRDHTYP=USI1, APPTYPE=MNAHU,
MOG="public", REFERABLE=YES;
– ADD BRD: SRN=0, SN=3, METYPE=USCDB, FBRDHTYP=UPBA2,

BBRDHTYP=USI1, APPTYPE=MNAHU, MOG="public",
REFERABLE=YES
Example
 FE and BE are deployed on the same board

HSS:2*DPU+1*HSF+1*DSG+1*HCF+1*BSG+1*CCU+1*SLF
MNAHU USCDB:2*DPU+1*NDF+1*DBG+1*DSG+1*PGW+2*DRU+1*
DSU+1*DTL
UPB0 HSS:2*DPU+1*HSF+1*DSG+1*HCF+1*BSG+1*CCU+1*SLF
MNAEJ
USCDB:2*DPU+1*DSG+1*PGW+2*DRU+1*DSU+1*DTL
MNAEW
USCDB:1*DPU+1*PGW+1*DTL
MNAHU USCDB:2*DPU+1*NDF+1*DBG+1*DSG+1*PGW+3*DRU+3*
DSU+1*DTL
UPBA2 HSS:2*DPU+1*HSF+1*DSG+4*HCF+1*BSG+1*CCU+1*SLF
MNAEJ
USCDB:2*DPU+1*DSG+1*PGW+4*DRU+6*DSU+1*DTL
MNAEW
USCDB:1*DPU+1*PGW+1*DTL
Contents
Contents
2.1 Basic concept
2.2 Configure FE local data
2.3 Configure BE local data
2.4 Configure Connection data between FE and BE
Managed Element
 Entity (Managed Element)

 The HSS9820 consists of the following logical entities:
 HSS
 USCDB
ME in FE and BE
ME NE
FE HSS HSS
SLF
BE USCDB
Process
 Module: a module is the internal processing unit of a board
 a single board can include multiple processes
 HSS Processing:
HSS9820 Process
FE Process BE Process
DPU DPU
DSG PGW
HSF DRU
HCF DSU
BSG DSG
CCU DBG
SLF NDF
IP Address Distribution IP address for
service
 FE need 2 IP addresses:
 IP for providing CSCF/AS/HLR
the services on the

FE
network side
IP address for
 IP for communicating with communicating with BE
the BE IP address for
communicating with FE
 BE need 2 IP addresses
BE
 IP for communicating with
service provisioning
SPG
gateway
 IP for communicating with

IP address for
the FE service provisioning
FE Plug Package
 Function: Used to activate the Database function of BE that fit for the
FE
The Relation Between Module,
Application Type & Board ( FE )
DPU＋ BSG+CCU DPU+HSF+HCF+D HSF+HCF+I HSF+SLF+
IMU SG+SLF+BSG+CC MU IMU
+IMU
U+IMU
Processing
(Module)
Application HSDPU HSBCU HSHIU HSHCS HSSCS
Type
U U U
P P P
B B B
0 A0 A2
Physical boards U S S U S
P W W S M
B I U I U
The Relation Between Module,
Application Type & Board ( BE )
DPU+DRU+ DSU
DSU＋ +NDF+DSG+PG PGW+IMU
DRU＋ DSU+DRU+ NDF+IMU
IMU W+DBG+IMU
IMU IMU
Processing
(Module)
Application USDRU USDSU USRSU USDIU/USDID USDMU/USDMD USPGW
Type
U U
P P
B B
0 A2
Physical boards U S S U S
P W W S M
B I U I U
Relationship of Location, Cluster, Node
 Node: could provide the
service independently
 Location: several nodes
in the same physical
location, such as one
USCDB
 Cluster: nodes which
manage the same
subscriber data
 Cluster is a service
entity to outside
Configuration Step
 3 steps to configure the HSS9820
FE Local Data
Configuration
BE Local Data
Configuration
Interconnection
Between the FE
and the BE
Contents
2.1 Basic concept
FE Configuration flow
 The commands following will be used when configure the FE
Object Navigation Tree

OMS2600 ADD ME
SET LOCATION FE Local Data

ADD HSS Configuration(
ADD MODULE The objects
ADD ADDR HSS and SLF
HSS need to be
SET LOCATION
ADD SLF configed
ADD SLFROUTE separately.)
ADD MODULE
ADD ADDR
ADD ME
 Function: This command is used to add a Managed Element
 Parameter:
Parameter Mandatory or Not Value
MEID Yes Specifies the ME instant in the subnet. It is an

integer, ranging from 5 to 1023.
MENAME Yes Specifies the ME name. It is a string with a

maximum of 40 characters.
METYPE Yes Specifies the ME type. It is a choice
MEVER Yes Specifies the version of ME. It is a string with

a maximum of 40 characters.
MEVD No Specifies the vendor of the ME. It is a string

with a maximum of 40 characters.
 Example: ADD ME: MEID=80,MENAME=“HSS", METYPE=“HSS",

MEVER="V900R008C00“, MEVD="huawei“;
SET LOCATION
 Function: This command is used to set the local location
information.
 Parameter:

LOCID Yes Specifies the location ID of the HSS.
It is an integer.
 Example:
SET LOCATION: LOCID=8;
ADD

HSS
Function: This command is used to add a local HSS.
 Parameter:
HSSID Yes Specifies the HSS entity index number. It is

an integer, ranging from 0 to 63.
DN Yes Specifies the domain name. It is a string with

HN Yes Specifies the host name. It is a string with a

EN Yes Specifies the entity name. It is a string with a

 Example: ADD HSS: HSSID=0,DN=“im2.com",HN="hss.ims2.com",

EN="HSS";
 Precaution: Although the value of HSSID ranges from 0 to 63, the system
supports only one entity.
ADD MODULE
 Function: This command is used to add a module.
 Parameter:
MID Yes Specifies the module number. It is an integer, ranging
from 1 to 1023.
MT Yes Specifies the module type. The values are enumerated.

There are seven types of module, namely, DPU, HCF,
HSF, SLF, BSG, CCU, and DSG.
SRN1 Yes Specifies the subrack number of the active process. It

is an integer, ranging from 0 to 19.
SN1 Yes Specifies the slot number of the active process. It is an

SRN2 No Specifies the subrack number of the standby process. It

is an integer, ranging from 0 to 19.
SN2 No Specifies the slot number of the standby process. It is

MNAME No Specifies the module name. It is a string with a

ADD MODULE
 Example:
Run the following command to add a module with both active and standby
processes:
ADD MODULE:MID=1,MT=DPU,SRN1=0,SN1=1,SRN2=0,SN2=2,MNAME=
"DPU";
Run the following command to add a module without standby process:
ADD MODULE:MID=5, MT=HCF, SRN1=0, SN1=1, MNAME="HCF";
 Precaution:
1. Before adding the SLF module, you must add the SLF entity. Before
adding other modules, you must add the HSS entity.
2. The module number under the same ME must be unique.
3. Only the DPU module is configured with a standby process. Therefore,
only when MT is set to DPU, the parameters SRN2 and SN2 can be
specified.
ADD ADDR
 Function: This command is used to add an IP address.
 Parameter:

ADDRID Yes Specifies the address ID. It is an integer, ranging from 0 to 1023.
MID Yes Specifies the referenced module ID. It is an integer, ranging from 1 to
1023.
IPV4IP1 Yes Specifies the IP address, which is in IPv4 format.
IPV4IP2 No Specifies the IP address, which is in IPv4 format.
IPV4GW1 Yes Specifies the gateway address, which is in IPv4 format.
IPV4GW2 No Specifies the gateway address, which is in IPv4 format.
IPV6GW1 Yes Specifies the gateway address, which is in IPv6 format.
IPV6GW2 No Specifies the gateway address, which is in IPv6 format.
ADD ADDR

IPV4MASK1 Yes Specifies the subnet mask address, which is in IPv4 format.
IPV4MASK2 No Specifies the subnet mask address, which is in IPv4 format.
IPV6MASK1 Yes Specifies the subnet mask address, which is in IPv6 format.
IPV6MASK2 No Specifies the subnet mask address, which is in IPv6 format.
NP1 Yes Specifies the network port number. The values are enumerated, ranging
from BACK1 to BACK8.
NP2 No Specifies the network port number. The values are enumerated, ranging
from BACK1 to BACK8.
SO Yes Specifies the Flow unbalanced detection policy. The values are Remote
FD and Local FD.
ADDRTYPE Yes Specifies the IP address type. The values are BUSINESSADDR and
DATAACCESSADDR.
ADD ADDR
 Example:
ADD ADDR: ADDRID=2, MID=1, ADDRTYPE=IPV4_DATAACCESSADDR,
IPV4IP1="2.2.10.36", IPV4GW1="2.2.0.1", IPV4MASK1="255.255.0.0",
NP1=BACK7, IPV4IP2="2.2.10.37", IPV4GW2="2.2.0.1",
IPV4MASK2="255.255.0.0", NP2=BACK8, SO=LOCALNETWORK-
1&REMOTENETWORK-1;
 Precaution:
1. The parameter MID must be set to DPU.
2. The format of the IP address, gateway IP address, and subnet mask IP address is
determined by the client. Currently, the client supports IPv4 and IPv6 format.
3. The IP addresses of the MEs managed by the same OMU must be unique. For
example, assume that ME66 uses the IP address 2.2.10.36. When you run ADD
ADDR to add the same IP address to ME88, an error is reported.
Contents
2.1 Basic concept
Commands Navigation
 The commands following will be used when configure the
HSS9820
OMS2600 ADD ME
SET LOCATION
ADD MODULE
ADD IPADDR
Configure environment
USCDB of physical database BE Local Data
LOD FEPLUG Configuration
ADD CLUSTER
ADD NODE
ACT FEPLUG
ADD ME
 Function: This command is used to add a Managed Element
 Parameter:
MEID Yes Specifies the ME instant in the subnet. It is an

MENAME Yes Specifies the ME name. It is a string with a

METYPE Yes Specifies the ME type. It is a choice
MEVER Yes Specifies the version of ME. It is a string with

MEVD No Specifies the vendor of the ME. It is a string

with a maximum of 40 characters.
 Example: ADD ME: MEID=90,MENAME=“USCDB",

METYPE=“USCDB", MEVER=" V100R002C03“, MEVD="huawei“;
SET LOCATION
 Function: This command is used to set the local location
information.
 Parameter:

LOCID Yes Specifies the location ID of the HSS.
It is an integer.
 Example:
SET LOCATION: LOCID=9;
ADD MODULE
 Function: This command is used to add a module.
 Parameter:
MID Yes Specifies the module ID. It is an integer, ranging from 1 to 1023.
MT Yes Specifies the module type. The values are DPU, NDF, DRU, DSU, DBG,
DSG, PGW, and DTL.
SRN1 Yes Specifies the subrack number of the active process. It is an integer,
ranging from 0 to 19.
SN1 Yes Specifies the slot number of the active process. It is an integer, ranging
from 0 to 15.
SRN2 No Specifies the subrack number of the standby process. It is an integer,

SN2 No Specifies the slot number of the standby process. It is an integer, ranging
from 0 to 15.
MNAME No Specifies the module name. It is a string with a maximum of 32 characters.
ADD MODULE
 Example
Run the following command to add a module with both the active and
standby processes:
ADD
MODULE:MID=1,MT=NDF,SRN1=0,SN1=1,SRN2=0,SN2=2,MNAME=“NDF
";
Run the following command to add a module without the standby process:
ADD MODULE:MID=10, MT=DRU, SRN1=0, SN1=1, MNAME=“DRU";
 Precaution:
1. Under the same ME, the module number must be unique.
2. Only the DPU and NDF have standby processes. Therefore, only when
MT is set to DUP or NDF, the parameters SRN2 and SN2 are available.
3. The DSG interacts with the HSS. Therefore, if you add a DSG module,
you need to add a DSG node record to the HSS; if you add a DSG module
to the HSS, you also need to add a DSG node record to the USCDB.
ADD IPADDR
 Function: This command is used to configure the IP addresses for the
DPU module connected to the FE and the provisioning system.
 Parameter:

DPUMID Yes Specifies the referenced module ID. It is an integer, ranging from 1 to
1023.
GATEWAYT Yes Specifies the IP address type. The values are DSG and PGW.
YPE
IP1 Yes Specifies the IP address, which is in IPv4 format.
IP2 No Specifies the IP address, which is in IPv4 format.
GW1 Yes Specifies the gateway address, which is in IPv4 format.
GW2 No Specifies the gateway address, which is in IPv4 format.
ADD IPADDR

MASK1 Yes Specifies the subnet mask address, which is in IPv4 format.
MASK2 No Specifies the subnet mask address, which is in IPv4 format.
ETH1 Yes Specifies the network port number. The values are enumerated, ranging
from Card1/Lan0 to Card4/Lan1.
ETH2 No Specifies the network port number. The values are enumerated, ranging
from Card1/Lan0 to Card4/Lan1.
ADD IPADDR
 Example:
ADD ADDR: DPUMID=1, GATEWAYTYPE=DSG, IP1="2.2.10.38",
GW1="2.2.0.1", MASK1="255.255.0.0", ETH1=Card4/Lan0, IP2="2.2.10.39",
GW2="2.2.0.1", MASK2="255.255.0.0", ETH2=Card4/Lan1;
Precaution:
1. The parameter DPUMID must be set to DPU.
2. The format of the IP address, gateway IP address, and subnet mask IP address is
determined by the client. Currently, the client supports only IPv4 format.
3. The IP addresses of the MEs managed by the same OMU must be unique. For
example, assume that ME66 uses the IP address 2.2.10.36. When you run ADD
ADDR to add the same IP address to ME88, an error is reported.
LOD FEPLUG
 Function: This command is used to load the HSS plug-in package. FEPLUG is used to
active the BE function fit to the FE.
 Parameter:

UPFILENAME Yes Specifies the name of the HSS
plug-in package.
 Example:
LOD FEPLUG: UPFILENAME=" IMS_HSS_PLUG_V900R008C00.tar ";
 Precaution:
1. Before running this command, ensure that the physical database has been set up, all
the modules (excluding the DRU and DSU) are running properly, and the active NDF
process is running on the board where the active physical database process resides.
2. After this command is executed, you can run the LST FEPLUG command to check
whether the command is executed successfully.
ADD CLUSTER
 Function: This command is used to add a cluster.
 Parameter:

CID Yes Specifies the cluster ID. It is an integer, ranging
from 2 to 512.
CT Yes Specifies the cluster type. The values are DRU

and DSU.
ROLE Yes Specifies the cluster role. The values are ACTIVE
and REDUNDANCY.
SERVICETYPE Yes Specifies the service type. The value is IMS-HSS

currently.
ADD CLUSTER
 Example
ADD CLUSTER: CID=11, CT=DRU, DATATYPE=GLOBAL_ROUTE_DATA,
ROLE=ACTIVE, SERVICETYPE="IMS-HSS";
 Precaution:
 Precaution:
1. The USCDB requires at least three DRU clusters. The USCDB uses the
global data cluster, and the HSS uses the two clusters. One node is used to
store the global data, and the other node is used to store the route data. In
addition, the HSS requires at least two DSU clusters..
2. When configuring the redundancy HLR, you need to set ROLE to
REDUNDANCY, indicating that the cluster is a redundancy cluster. When
there is no redundancy HLR, set ROLE to ACTIVE.
3. You are advised to see the Software Installation for the basic operations.
ADD NODE
 Function: This command is used to add a node.
 Parameter:
CID Yes Specifies the cluster ID. It is an
NID Yes Specifies the node ID. It is an integer,

MID Yes Specifies the module number. It is

 Example:
ADD NODE: CID=1, NID=161, MID=161;
ACT FEPLUG
 Function: This command is used to activate the loaded HSS plug-in
package. FEPLUG is used to active the BE function fit to the FE.
 Parameter:
FETYPENAME Yes Specifies the name of the HSS
plug-in package.
 Example:
ACT FEPLUG: FETYPENAME="IMS-HSS";
 Precaution:
1. Before running this command, ensure that the execution of the

ADD NODE command is complete.
USCDB Loading Mode
 The USCDB can load the data from the physical database or the dump file. You
can run MOD INSP to change the loading mode.
 Software parameter: LDRSOURCE
Values:
0: Default loading mode
1: to load the data from the master node
2: to load the data from the dump file
3: to load the data from the physical database (as shown in the figure)
 The default loading mode means that the USCDB loads the data from the master
node first. If the loading fails, it loads the data from the dump file. If the loading fails
again, it loads the data from the physical database.
Configurations for Loading the Data to
the USCDB
 Configurations when the USCDB loads the data from the master node:
When the USCDB loads the data from the master node, the loaded node must be
located in the cluster and its status must be master. Otherwise, the USCDB cannot
load the data from the master node.
 Configurations when the USCDB loads the data from the dump file:
Copy the required files to the /opt/uscdb/snp directory of the USCDB board.
Modify the software parameters of the USCDB and enables the USCDB to load
data from the dump file.
 Configurations when the USCDB loads the data from the physical database:
Configure the NDF module. After the NDF process is started, the system downloads
the required files from the OMU to the /opt/SigPlat/etc directory on the NDF board.
Open the Config.cfg file and modify the slot and listening IP address of the NDF
module. Ensure that the listening IP address is not used by other boards. Then,
run the mainmenu.sh script to complete the configuration. For details, see the
related section about configuring the environment without the disk array in the
attachment.
Configurations for Loading the Data to
the USCDB
 Precaution:
If multiple MEs share one board, you need to pay attention to the
configurations of the memory parameter when you configure
the dump file loading mode and the physical database loading
mode. For details, see the attachments.
Verification
 After the database is loaded, run DSP NODE to check the
node state. If the node state is master or slave, it indicates that
the database is successfully loaded. If the node state is initial
or null, it indicates that there are exceptions. The following
figure shows the normal result.
Contents
2.1 Basic concept
Referencing Relation Between the FE-BE
 Referencing relation between the FE-BE interconnection data
tables
Commands Navigation (FE)
interworking data between FE and BE
ADD RLOCATION Interconnection

HSS ADD RDSG Between the FE
ADD RIPADDR and the BE
ADD RLOCATION
 Function: This command is used to add a remote location record.
 Parameter:
RLOCID Yes Specifies the location ID of the USCDB. It is an integer.
RMT Yes Specifies the type of remote ME. Currently, it is set to

USCDB.
LP Yes Specifies the priority. The value ranges from 1 to 512.
 Example:
ADD RLOCATION: RLOCID=9, RMT="USCDB", LP=1;
 Precaution
1. The parameters RLOCID is the interconnection data. Therefore, the
value of this parameter must be the same as the location ID of the
USCDB.
2. The parameter LP indicates the priority of the HSS. When multiple
HSSs correspond to one USCDB, the subscription notification of the
USCDB is delivered to the HSS with a lower priority. A higher value of LP
indicates a higher priority.
ADD RIPADDR
 Function: This command is used to add an IP address of the BE.
 Parameter:

RLOCID Yes Specifies the location ID of the USCDB. It is an
integer.
ID Yes Specifies the address ID of the peer ME. The value

ranges from 1 to 512.
IP1 Yes Identifies IP address 1 of the DSG of the USCDB.
IP2 Yes Identifies IP address 2 of the DSG of the USCDB.
ADD RIPADDR
 Example:
ADD RIPADDR: RLOCID=32, ID=1, IP1="2.2.10.38",
IP2="2.2.10.39";
 Precaution:
1. The parameters RLOCID is the interconnection data. Therefore, the
value of this parameter must be the same as the location ID of the
USCDB.
2. IP1 and IP2 map the two IP addresses of the DSG module on the
USCDB that are conrfigured by using the IPADDR command.
ADD RDSG
 Function: This command is used to add the DSG information of the
BE.
 Parameter:
RLOCID Yes Specifies the location ID of the USCDB. It is an

integer.
RDSGMID Yes Specifies the number of the DSG module of the

USCDB.
 Example:
ADD RDSG: RLOCID=32, RDSGMID=151;
 Precaution:
1. The parameters RLOCID is the interconnection data. Therefore,
the value of this parameter must be the same as the location ID of
the USCDB.
2. The parameter RDSGMID identifies the number of the DSG
module of the USCDB. You need to configure RDSGs based on the
number of DSG modules.
Commands Navigation (BE)
interworking date between BE and FE
ADD RLOCATION
ADD RDSG
Interconnection
USCDB Between the BE
ADD RIPADDR
and the FE
ADD NOTIFYCFG
ADD RLOCATION
 Function: This command is used to add the information about the remote
location.
 Parameter:

RLOCID Yes Specifies the remote location ID. It is an integer, ranging from 1 to 512.
RMT Yes Specifies the peer ME. The values are IMS-HSS and USCDB. Here, it is set
to IMS-HSS.
LP Yes Specifies the priority. The value ranges from 1 to 512.
ADD RLOCATION
 Example:
ADD RLOCATION: RLOCID=8, RMT="IMS-HSS", LP=1;
 Precaution:
1. The parameter RLOCID is the interconnection data. It must be the same

as the location ID of the HSS to be interconnected.
2. The parameter RMT identifies the type of the interconnected ME. It is set
to IMS-HSS here.
3. The parameter LP indicates the priority of an HSS. If one USCDB

corresponds to multiple HSSs, the subscription notification of the USCDB is
delivered to the HSS with a lower priority. A higher value of LP indicates a
higher priority.
ADD RIPADDR
 Function: This command is used to add the IP address of the FE.
 Parameter:
RLOCID Yes Specifies the location ID of the HSS to be

interconnected. It is an integer.
ID Yes Specifies the ID of the data IP address of the HSS.

The value ranges from 1 to 512.
IP1 Yes Specifies data IP address 1 of the HSS.
IP2 Yes Specifies data IP address 2 of the HSS.
ADD RIPADDR
 Example:
ADD RIPADDR: RLOCID=8, ID=1, IP1="2.2.10.36",
IP2="2.2.10.37";
 Precaution:
1. The parameter RLOCID is the interconnection data. It must be
the same as the location ID of the HSS to be interconnected.
2. IP1 and IP2 map the two data IP addresses of the HSS configured
by using the ADDR command.
ADD RDSG
 Function: This command is used to add a DSG module of the FE.
 Parameter:

RLOCID Yes Specifies the location ID of the HSS to be
interconnected. It is an integer.
RDSGMID Yes Specifies the number of the DSG module of the HSS.
 Example:
ADD RDSG: RLOCID=8, RDSGMID=4;
 Precaution:
1. The parameter RLOCID is the interconnection data. It must be
the same as the location ID of the HSS to be interconnected.
2. The parameter RDSGMID identifies the number of the DSG
module of the HSS. You need to configure the RDSGs based on the
number of DSG modules.
ADD NOTIFYCFG
 Function: This command is used to send the subscription notification
messages delivered from the PGW.
 Parameter:

FETYPE Yes IMS-HSS
INFTYPE Yes MCI
LOCATIONID Yes Specifies the location ID of the HSS to

be interconnected. It is an integer.
 Example:
ADD NOTIFYCFG: FETYPE="IMS-HSS", INFTYPE=MCI,

LOCATIONID=8;
Contents
Protocols and Reference Interfaces
for HSS9820
Interface and Link
 HSS  SLF
I-CSCF I-CSCF
S-CSCF S-CSCF
HSS SLF
AS AS
GGSN
HLR/IM-SSF
Commands Navigation
 commands for HSS/SLF connection data configuration

ADD HICSCF
ADD HICSCFL
ADD HSCSCF
ADD HSCSCFL
ADD HAS
ADD HASL
ADD HGGSN
HSS
ADD HGGSNL
ADD SLFICSCF
ADD SLFICSCFL
ADD SLFSCSCF
ADD SLFSCSCFL
ADD SLFAS
ADD SLFASL
Example
 HSS connection data configuration
IP:190.1.20.1
Port No:3868
Protocol :SCTP
Mode :Server
IP:190.1.10.2
Port No: 2222
Protocol :SCTP
I-CSCF HSS9820
Mode: client
Example
 Add I-CSCF
 ADD HICSCF: HSSID=0, ICSCID=0, CSCFN=“icscf”, HN=“icscf.ims1.com”,
LNKMOD=POLLING, FEATURELIST=SharedIFC-1;
– Link selection mode need to be negotiated with peer node.
 Add link to I-CSCF

 ADD HICSCFL: HSSID=0, ICSCID=0, LNKID=0, PTYPE=SCTP,
WMODE=SERVER, HSFMID=4, ADDRID=0, PIPVER=IPV4,
PIPV4="190.1.10.2", PPT=2222;
– Port number (local and remote), protocol type, work mode must be negotiated
with peer node.
– Local port number for HSS is 3868
Thank you
www.huawei.com

(Basic Training) HSS9820 Data Configuration ISSUE3.30

Uploaded by

Copyright:

Available Formats

(Basic Training) HSS9820 Data Configuration ISSUE3.30

Uploaded by

Document Information

Original Title

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

(Basic Training) HSS9820 Data Configuration ISSUE3.30

Uploaded by

Copyright:

Available Formats

What are the main components of an HSS9820 system?

What are the main components of an HSS9820 system?

What are the main steps in configuring an HSS9820?

What are the main steps in configuring an HSS9820?

HSS9820 Data

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

 HUAWEI HSS9820 Home Subscriber Server Interworking

 Perform the HSS FE and BE local configuration

 Perform the HSS interworking configuration

2. HSS9820 Local Data Configuration

3. HSS9820 Interconnection Data Configuration

 Device number Integrated rack 00 Service rack 01

 Rack number Power distribution

Basic subrack 00 extension subrack 03

LAN switch/hard disk extension subrack 02

Physical Process group

 Step1: Add Rack and Subrack

 select <ME: OMS2600>  <Navigation Tree>  < MML

– ADD SUBRACK: SRN=0, RN=0, PN=0, SBVER=T8280,

~ SRMU is system reliability management unit

– ADD BRD: SRN=0, SN=12, METYPE=HSS, FBRDHTYP=UPBA0,

Physical board Application type Process Configuration

– ADD BRD: SRN=0, SN=13, METYPE=USCDB,

Physical board Application type Process Configuration

Tips: The USDIU/USDMU application types are used in disk array

– ADD BRD: SRN=0, SN=3, METYPE=USCDB, FBRDHTYP=UPBA2,

Physical board Application type Process Configuration

2. HSS9820 Local Data Configuration

3. HSS9820 Interconnection Data Configuration

2.2 Configure FE local data

2.3 Configure BE local data

2.4 Configure Connection data between FE and BE

 Entity (Managed Element)

 a single board can include multiple processes

 IP for providing CSCF/AS/HLR

the services on the

 IP for communicating with

Application HSDPU HSBCU HSHIU HSHCS HSSCS

Application USDRU USDSU USRSU USDIU/USDID USDMU/USDMD USPGW

2.2 Configure FE local data

2.3 Configure BE local data

2.4 Configure Connection data between FE and BE

Object Navigation Tree

SET LOCATION FE Local Data

Parameter Mandatory or Not Value

MEID Yes Specifies the ME instant in the subnet. It is an

MENAME Yes Specifies the ME name. It is a string with a

METYPE Yes Specifies the ME type. It is a choice

MEVER Yes Specifies the version of ME. It is a string with

MEVD No Specifies the vendor of the ME. It is a string

 Example: ADD ME: MEID=80,MENAME=“HSS", METYPE=“HSS",

Parameter Mandatory or Not Value

SET LOCATION: LOCID=8;

Parameter Mandatory or Not Value

HSSID Yes Specifies the HSS entity index number. It is

DN Yes Specifies the domain name. It is a string with

HN Yes Specifies the host name. It is a string with a

EN Yes Specifies the entity name. It is a string with a

 Example: ADD HSS: HSSID=0,DN=“im2.com",HN="hss.ims2.com",