HSS Server
The HSS Server tab is used to define the information in LTE requests sent from the HSS node to the MME/SGSN.
The HSS Server via the S6a/S13 interfaces enables transfer of subscription and authentication data for authenticating/authorizing user access to the evolved system (AAA interface) between MME and HSS. Similarly, the HSS Server via the S6d/S13' interface enables data transfer between SGSN and HSS.
| NOTE: The HSS Node testing supports multiple interfaces to an emulated HSS/HLR. The HSS Node test case enables connection of multiple SUTs (MME's and/or SGSNs) and supports all interfaces (S6a, S6d, Gr) simultaneously from a single emulated HSS/HLR. For example, a message received on a Gr interface may result in a message being sent on an S6a interface. |
|
Authentication
|
Data Subscription
|
|
ProSe Subscription Data
Enable ProSe Data
-
Direct Discovery EPC Level Discovery
-
EPC Support WLAN Direct Discovery/Communication
-
One-to-many Direct communications
-
Direct Discovery EPC Level Discovery
-
EPC Support WLAN Direct Discovery/Communication
-
One-to-many Direct communications
ProSe Withdrawal
|
|
Feature-List-Id 2
|
|
Cancellation/Termination Timeout
|
|
Regional Zones
Zone n
|
|
T-ADS Information
|
|
Teleservices
|
Related Measurements
Measurements collected for HSS related processing are reported on the HSS Node report tab.
Authentication
Defines the authentication keys used by the MNs.
Algorithm
Select an Authentication Algorithm. Additional fields become available for input.
Options : Milenage ( Defined in 3GPP TS 35.205) , TUAK ( Defined in 3GPP TS 35.231)
TUAK is a 3GPP defined algorithm and key generation set of functions (f1, f1*, f2, f2, f4, f5, and f5*).
Tcl Parameter: HssSrvNasAuthAlgorithm
Secret Key
The MN's text or hexadecimal key that is associated with its IMSI and is used to derive the UMTS ciphering key.
Tcl Parameter: HssSrvSecretKey
Operator Variant
The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network.
Range: Up to 16-Byte hex string
Default: 0x63BFA50EE6523365FF14C1F45F88737D
Tcl Parameter: HssSrvOpVar
OPc
A128-bit value derived from OP and K and used in subsequent computations. Hence, less sensitive and if obtained by third party.
NOTE: The OPc may be computed off the USIM if possible, since this provides the following:
- Reduces complexity of the algorithms run on the USIM.
- Enhanced security as the algorithms are designed to be secure whether or not OP is known to the attacker. Even if a large number of OPC, K pairs have been discovered it would be difficult to deduce OP. That is, the OPC associated with any other value of K will be unknown, which makes it harder to for any crypt-analytic and forgery attacks.
|
Range: Up to 16-Byte hex string
Default: 0x63BFA50EE6523365FF14C1F45F88737D
Tcl Parameter: HssSrvOpC
EPS, UMTS, GSM Authentications
EPS, UMTS, and EPS authentication are available for selection when Interface is either S6a, S6d, or Gr on the Emulator Configuration tab. If you select only SWx Interface, the EPS, UMTS, and EPS authentication are not available. The authentication type is used in authentication-info AVP.
| NOTE: You may select either UMTS or GSM authentication at a time. |
Tcl Parameter: HssSrvEpsAuthEn
Tcl Parameter: HssSrvUmtsAuthEn
Tcl Parameter: HssSrvGsmAuthEn
Type: True/False
| TUAK Algorithm |
The following fields become available when Algorithm = TUAK. For information about how the fields are used in the TUAK algorithm the user should refer to the 3GPP TS 35.231 specification.
| Key |
This is the secret key and is analogous to the Milenage Secret Key field. Enter either a String value or a Hex value beginning with 0x.
Tcl Parameter: HssSrvTuakKey
|
| TOP |
The Edit Top data input box associated with TOP allows the user to input a 32 byte Hex string value used for the operator variant. Tcl Parameter: HssSrvTuakOpType  |
| Key Length (bytes) |
Select the maximum length supported for the secret key. Support for 16 or 32 bytes. Tcl Parameter: HssSrvTuakKeyLen |
| RES Length (bytes) |
Select the maximum length supported for the RES value. Support of 4 or 8 bytes only. Tcl Parameter: HssSrvTuakResLen |
| Keccak_f Iterations |
Enter the number of times the Keccak permutation is performed. Range : 1 to 255 Default : 1 Tcl Parameter: HssSrvTuakIterations |
| MAC Length (bytes) |
Select the maximum length supported for the MAC fields (MAC-A and MAC-S). Support 8 bytes. Tcl Parameter: HssSrvTuakMacLen |
| CK Length (bytes) |
Select the maximum length supported for the confidentiality key. Support 16 bytes only. Tcl Parameter: HssSrvTuakCkLen |
| IK Length (bytes) |
Select the maximum length supported for the integrity key. Support 16 bytes only. Tcl Parameter: HssSrvTuakIkLen |
|
^ Back to Top
Data Subscription
The Data Subscription allows you to configure timers to insert and delete Subscription data. The AVP Editor on the Diameter tab provides the Subscription data to be inserted or deleted. In addition, you may also define the charging characteristics and the IP flow rate for the uplink and downlink traffic.
| NOTE: The Data Subscription timers (Include Data Subscription Timer, IDR Time, and DSR Time) is not used in DRA Nodal test case, as it uses the message flows and message timers to simulate what messages are sent and when they are sent. |
| Include Data Subscription Timer |
Select the checkbox to enable entering the subscription insert and delete timers.
Tcl Parameter: HssSrvDataSubTimeEn
|
| IDR Time |
Enter the time to wait (after a session is established) before sending and IDR message along with the Data Subscription information from the AVP Editor.
Tcl Parameter: HssSrvIdrTime
|
| DSR Time |
Enter the time to wait (after receiving an IDR response) before sending and DSR message along with the Data Subscription information from the AVP Editor.
Tcl Parameter: HssSrvDsrTime
| NOTES:
The IDR and DSR timers will alternate between insert and delete. For example, if the IDR is set to 10 seconds, and the DSR is set to 20 seconds the following happens:
- 10 seconds after the session is established the HSS Node sends an IDR (with information from AVP editor).
- 20 seconds after the session gets a response, the HSS Node sends a DSR (with information from the AVP editor).
- 10 seconds after the session gets a response to the DSR (DSA) the HSS Node then sends an IDR again, and so on.
|
|
| Include 3Gpp Charging Characteristics |
Use this checkbox to enable the type of charging for which the subscribed data is liable. Selected from one of 16 charging profiles that may be configured on the SGSN.
See table of Charging Profiles.
Range: 0 - 65535
Default: 0 (indicates that it is not used)
Tcl Parameter:
|
HssSrvChgCharacteristicsEn
|
HssSrvChgCharacteristics
|
|
| Include Aggregate Max Bit Rate |
Select the checkbox and define the IP flow Aggregate Maximum Bit Rate for UL and DL traffic. The rate defined here applies to the data subscribed on the HSS Server.
Enter Max Downlink (bps) and Max Uplink (bps).
Range = 0 to 4294967295
Default value = 0
Tcl Parameter:
|
HssSrvAmbrEn
|
HssSrvAmbrMaxDl
|
HssSrvAmbrMaxUl
|
HssSrvAmbrMaxDlBps
|
HssSrvAmbrMaxUlBps
|
|
| Include Fault Recover (RSR) Timer |
Select the checkbox and enter the time to wait, after a restart, before indicating (from HSS) to the MME or the SGSN that a failure has occurred.
Options: 0 - 65535
Tcl Parameter: HssSrvRSRTime
|
| Network Access Mode |
Indicates the type of Network Access service allowed in the HSS; Packet and Circuit service; only Packet or only Circuit. Select the Network Access Mode allowed in the HSS from the dropdown list.
|
HssSrvNetworkAccessModeEn
|
HssSrvNetworkAccessMode
|
|
| Access Restriction Data |
The Access Restriction Data is permanent subscriber data stored in the HLR/HSS, and temporary subscriber data stored in the VLR and SGSN and MME.
When LTE Spec Version >= 15.X.0, the maximum Value for this field is 2047 to set all bits to true as demonstrated by the table below.
The range is now dynamic. For versions below "LTE Spec Version <= 16.1.0", the Value range is 0-2047.
For "LTE Spec Version = 16.1.0", the Value range will be 0-8191.
|
Bit
|
Description
|
|
0
|
UTRAN Not Allowed
|
|
1
|
GERAN Not Allowed
|
|
2
|
GAN Not Allowed
|
|
3
|
I-HSPA-Evolution Not Allowed
|
|
4
|
WB-E-UTRAN Not Allowed
|
|
5
|
HO-To-Non-3GPP-Access Not Allowed
|
|
6
|
NB-IoT Not Allowed
|
|
7
|
Enhanced Coverage Not Allowed
|
|
8
|
NR as Secondary RAT Not Allowed
|
|
9
|
Unlicensed Spectrum as Secondary RAT Not Allowed
|
|
10
|
NR in 5GS Not Allowed
|
| 11 |
LTE-M Not Allowed (Available when LTE Spec Version >= 16.1.0) |
| 12 |
WB-E-UTRAN Except LTE-M Not Allowed (Available when LTE Spec Version >= 16.1.0) |
|
HssSrvAccessRestrictDataEn
|
HssSrvAccessRestrictData
|
|
| Operator Determined Barring |
Select Operator Determined Barring and enter a value that indicates the services of a subscriber that are barred by the operator.
Tcl Parameter:
|
HssSrvOperatorBarringDataEn
|
HssSrvOperatorBarringData
|
Option: 0 - 4294967294
Default: 0
|
| Include Roaming Restricted Unsupported |
Select to include the AVP (when the MME receives) in Update-Location-Answer message to indicate Roaming restricted in MME due to unsupported feature.
Tcl Parameter: HssSrvRoamingRestrictedUnsupportedEn
|
| RFSP Index |
Select to include the RFSP (RAT-Frequency Selection Priority ID) AVP (when the MME receives). In Update-Location-Answer message to include the subscribed value of Subscriber Profile ID for RAT/Frequency Priority.
Options: 1 to 256
Tcl Parameter:
|
HssSrvRFSPIndexEn
|
HssSrvRFSPIndexData
|
|
| STN-SR |
Select to include the STN-SR in the ULA/ISR messages for SRVCC cases. If the STN-SR is present, it indicates the UE is SRVCC subscribed.
Available for S6a, S6d and GR.
Options: 1 to 18 Characters
Tcl Parameter:
|
HssSrvStnSrEn
|
HssSrvStnSr
|
|
| Include Subscribed vSRVCC |
Select to include the vSRVCC flag as part of the subscription data sent to the MME. If the subscriber is allowed to have vSRVCC in the VPLMN, then the HSS can it include if enabled.
Available for S6a, S6d and GR.
Tcl Parameter:
|
| Include APN OI Replacement |
Select to include the APN-OI-Replacement AVP in Subscription-Data AVP for ULA and IDR messages.
Available for S6a and S6d.
Tcl Parameter:
|
HssSrvApnOIRepEn
|
HssSrvApnOIRep
|
|
| Include Trace Data |
Select to include the Trace-Data AVP in Subscription-Data AVP for ULA and IDR messages. An new Tab called Trace Data becomes available for input.
Available for S6a and S6d.
|
| Include Core Network Restrictions Access To 5G - Allowed, Not Allowed |
Select to include Core-Network-Restrictions AVP per Clause 7.3.230.
Select Access To 5G - Allowed or Not Allowed. Interworking-5GS-Indicator AVP Clause 7.3.231.
|
HssSrvCoreNetworkRestrictionsEn
|
HssSrvAccessTo5gC
|
|
| CSG Subscription Data |
Enable CSG Subscription Data (Grouped AVP, code 1436). The CSG subscription data is an element of grouped AVP Subscription data (AVP code 1400.
The Insert-Subscriber-Data-Request and Update-Location-Answer AVPs use the CSG subscription AVP.
Tcl Parameter: HssCsgSubDataEn
| CSG ID |
Enter the CSG Id. Range from 0 to 134217727 Default = 0 Tcl Parameter: HssCsgId |
| Expiration Time (s) |
Enable the Expiration Time checkbox to enter a time in seconds. The entered values is used as "elapsed time" in seconds. This value will be added to current NTP time. Range = 0 to 4294967295 Default = 36000
|
HssCsgExpireDateEn
|
HssCsgExpireDate
|
|
| Service Selection |
When checked, the value of APN from the HSS to PDN Context's of the subscriber will be used. Tcl Parameter: HssCsgServiceSelectionEn |
| Visited PLMN ID |
When checked, this allows user to add MCC and MNC Values. Range from 000 to 999 Default = 000
|
HssCsgVisitedPlmnIdEn
|
HssCsgMcc
|
HssCsgMnc
|
|
|
^ Back to Top
ProSe Subscription Data
| Enable ProSe Data |
Enable ProSe Data - Enables the ProSe-Subscription-Data AVP in messages like ULA and IDR. (3GPP TS 29.344 (Release 12).
Only available when LTE Spec Version is >= 12.10.0.
Tcl Parameter: HssAppProSeDataEn
Permission(Initial in LUA/ULA)
| Direct Discovery |
When checked, indicates that the user is allowed to use ProSe Direct Discovery.
|
| EPC Level Discovery |
When checked, indicates that the user is allowed to use EPC Level ProSe Discovery.
|
| EPC Support WLAN Direct Discovery/Communication |
When checked, indicates that the user is allowed to use EPC Support WLAN Direct Discovery and communication.
|
HssAppEpcDirectDisCommLuaEn
|
|
| One-to-many Direct Communications |
When checked, indicates that the user is allowed to use one-to-many ProSe Direct Communication.
|
Permision (Update in IDR)
| Direct Discovery |
When checked, indicates that the user is allowed to use ProSe Direct Discovery. Tcl Parameter: HssAppDirectDisIdrEn |
| EPC Level Discovery |
When checked, indicates that the user is allowed to use EPC Level ProSe Discovery.
|
| EPC Support WLAN Direct Discovery/Communication |
When checked, indicates that the user is allowed to use EPC Support WLAN Direct Discovery and communication.
|
HssAppEpcDirectDisCommIdrEn
|
|
| One-to-many Direct Communications |
When checked, indicates that the user is allowed to use one-to-many ProSe Direct Communication.
|
ProSe Withdrawal
When checked, indicates that the ProSe subscription data shall be deleted from the MME.
Tcl Parameter: HssAppWithDrawalEn
|
^ Back to Top
Feature-List-Id 2
|
Feature-List-Id 2
|
Select for support of NR as Secondary RAT per 3GPP TS 29.272 v 15.2.0. Available when LTE Spec Version >= 15.0.
This option is only available for S6a, S6d, and Gr Interfaces.
|
27
|
NR as Secondary RAT
|
O
|
Support of NR as Secondary RAT
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over S6a (and S6d) when the MME (or combined MME/SGSN) supports NR as Secondary RAT, and over S6d when the SGSN supports the indication related to NR as Secondary RAT (such as, e.g., the related Access Restriction Data, or extended QoS parameters).
If the MME, SGSN, or combined MME/SGSN does not support this feature, the HSS shall not send (in ULA) or update (in IDR) subscription data related to NR as Secondary RAT.
If the HSS does not support this feature, the MME shall ignore the bit "NR as Secondary RAT Not Allowed" in Access-Restriction-Data.
|
|
Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "SMS in MME".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature.
NOTE 1: If both bits, corresponding to the same feature defined for Lg interface and Lgd interface, are not set, and the HSS supports the feature, the HSS shall not send the related LCS information to the SGSN within ULA and IDR.
|
| NOTE: A value of 0 (Zero) means that none of the bits are checked / configured and thus Feature List 2 AVP will not be added. |
Enable Bit Mask Helper Feature-List-Id 2 wizard and select the Features:
|
Feature bit
|
Feature
|
|
0
|
SMS in MME
|
|
1
|
SMS in SGSN
|
|
2
|
Dia-LCS-all-PrivExcep
|
|
3
|
Dia-LCS-Universal
|
|
4
|
Dia-LCS-CallSessionRelated
|
|
5
|
Dia-LCS-CallSessionUnrelated
|
|
6
|
Dia-LCS-PLMNOperator
|
|
7
|
Dia-LCS-ServiceType
|
|
8
|
Dia-LCS-all-MOLR-SS
|
|
9
|
Dia-LCS- BasicSelfLocation
|
|
10
|
Dia-LCS- AutonomousSelfLocation
|
|
11
|
Dia-LCS- TransferToThirdParty
|
|
12
|
Gdd-in-SGSN
|
|
13
|
Optimized-LCS-Proc-Support
|
|
14
|
SGSN CAMEL Capability
|
|
15
|
ProSe Capability
|
|
16
|
P-CSCF Restoration
|
|
17
|
Reset-IDs
|
|
18
|
Communication-Pattern
|
|
19
|
Monitoring-Event
|
|
20
|
Dedicated Core Networks
|
|
21
|
Non-IP PDN Type APNs
|
|
22
|
Non-IP PDP Type APNs
|
|
23
|
Removal of MSISDN
|
|
24
|
Emergency Service Continuity
|
|
25
|
V2X Capability
|
|
26
|
External-Identifier
|
|
27
|
NR as Secondary RAT
|
|
28
|
Unlicensed Spectrum as Secondary RAT
|
Range: 0 to 536870911, Default = 32768
|
^ Back to Top
Cancellation/Termination Timeout
|
Wait for Response Answer Timeout
Wait Time
|
Enable to Add Handling of Cancellation/termination procedure (allowed for S6a, S6d, Gr and Swx Interfaces).
S6a/S6d - On reception of a ULR from a new MME/SGSN (S6d), the HSS initiates a CLR to the old MME/SGSN (S6d). If it does not receive a CLA from the old MME/SGSN (within the configured Wait Time), the HSS continues the procedure by sending the ULA to the new MME/SGSN (S6d).
SWx - When network initiated De-Registration is executed by the HSS, the HSS sends a RTR message to the AAA server. If it does not receive RTA, within the configured Wait Time, it will de-register the user and cleanup the session.
Enter Wait Time in seconds- Range from 1 to 65535, Default = 1
|
HssSrvWaitTimeForRespEn
|
HssSrvWaitTime
|
|
Regional Zones
The Regional-Subscription-Zone-Code AVP is defined as the tracking or routing areas into which the subscriber is allowed to roam.
|
Number of Zones
|
Indicates the subscription Zone code.
Option: 0 - 10
Default: 0
Tcl Parameter: HssSrvNumZones
|
|
Zone n
Zone Code
MCC
MNC
|
The number of Zone tabs depends upon the number of Regional Zones selected.
| Zone Code: Indicates the subscription Zone code. |
0 - 65535 |
Default: 0 |
HssSrvZoneCode_1 |
| MCC: Mobile Country Code |
3 numerical digits |
Default: 000 |
HssSrvZoneMcc_1 |
| MNC: Mobile Network Code |
2 or 3 numerical digits |
Default: 000 |
HssSrvZoneMnc_1 |
|
|
T-ADS IMS Voice over PS Query
Timeout (ms)
|
Enable to Add T-ADS Information (allowed for S6a, S6d, and Sh Interfaces).
When enabled and when Sh receives UDR with "TADSinformation" in Data-Reference, Sh will query HSS/SGSN for TADS Information on S6a/S6d through IDR/IDA.
Enter Timeout in Milli-seconds to indicate how long Sh will wait for HSS to query TADS informations on IDR/IDA before giving up and sending UDA.
Range from 1 to 65535, Default = 1000
|
ImsVoiceOverPsQueryEn
|
ImsVoiceOverPsQueryTimeout
|
|
Teleservices
In insertSubscriberData, the teleserviceList IE is located in the MAP section.
|
Number of Teleservice Codes
|
Available in HSS Node when Gr interface is enabled.
Enter the number Teleservice Codes.
In insertSubscriberData, the teleserviceList IE is located in the MAP section.
Option: 0 - 20
Default: 0
Tcl Parameter: HssSrvNumTeleSvcs
|
|
Teleservice n
Teleservice Code
Custom Code
|
The number of Teleservice tabs depends upon the "Number of Teleservice Codes" selected.
Per 3GPP 22.003.
| The Teleservice Code column allows the selection of the spec-defined, single byte service codes and gives their names: |
Options:
00 - allTeleservices (default)
10 - allSpeechTransmisssionServices
11 - telephony
12 - emergencyCalls
20 - allShortMessageServices
21 - shortMessageMT-PP
22 - shortMessageMO-PP
23 - Cell Broadcast Service
60 - allFacsimileTransmissionServices
61 - facsimileGroup3AndAlterSpeech
62 - automaticfacsimileGroup3
63 - facsimileGroup4
70 - allDataTeleservices
80 - allTeleservices-ExceptSMS
90 - allVoiceGroupCallServices
91 - voiceGroupCall
92 - voiceBroadcastCall
D0 - allPLMN-specificTS
D1 - plmn-specificTS-1
D2 - plmn-specificTS-2
D3 - plmn-specificTS-3
D4 - plmn-specificTS-4
D5 - plmn-specificTS-5
D6 - plmn-specificTS-6
D7 - plmn-specificTS-7
D8 - plmn-specificTS-8
D9 - plmn-specificTS-9
DA - plmn-specificTS-A
DB - plmn-specificTS-B
DC - plmn-specificTS-C
DD - plmn-specificTS-D
DF - plmn-specificTS-F
Custom Value
|
HssSrvTeleSvc_1 |
| Custom Code |
When "Custom Value" is selected for Teleservice Code , the Custom Code column is enabled for editing in that row.
The format is 1 to 5 HEX bytes (2, 4, 6, 8, or 10 HEX chars).
|
|
|
^ Back to Top