DSA Mandatory Configuration

2.3.1 DSA Mandatory Configuration

The Rx ShUDR application uses these tables for holding the configuration value.

Table 2-1 Configuration tables for the Rx ShUDR application

Table Name	Table Description	Single row indicator	Table Level
Rx_Client	This table includes the configuration parameters for each Rx Client regarding the details of Sh Lookup and Topology hiding. This is a table generated by the DCA Framework.	No	NO
PDNGWHost_PCRF_Mapping	This table contains one to one mapping between PDN Gateway Host and PCRF. This is a table generated by the DCA Framework.	No	NO
Topology_Hiding	This table contains 1:1 mapping between PCRF FQDN and corresponding Pseudo FQDN for each PCRF MPEs. This is a table generated by the DCA Framework.	No	NO
Error_Action_Config	This table contains the error action configuration parameters to be applied for send answer during runtime errors while processing Sh UDR/UDA message.	No	NO
System_Config_Options	This table contains system wide common configurable options required to process Rx-ShUDR application.	Yes	SO

Rx_Client Table

This table contains the list of Rx Client FQDN’s and the corresponding details of Sh Lookup and Topology Hiding for each Rx client.

Table 2-2 Details of the Rx_Client table for the Rx-ShUDR application

Parameter Name	Unique	Mandatory	Range and default value	Description
Rx_Client_FQDN	No	Yes	DiameterIdentity Default: n/a,	Indicates the Fully Qualified Domain Name of Rx Client (MCPTT Client).
Sh_Lookup_Required	No	Yes	Enumerated, Yes/No Default=No	Decides whether Sh Lookup is required upon receiving Rx AAR from Rx(MCPTT) Client. If configured as Yes, then Sh Lookup is performed by Rx-ShUDR application. If configured as No, then AAR message is forwarded without processing at Rx-ShUDR application.
Topology_Hiding_Required	No	Yes	Enumerated, Yes/No Default=No	Decides whether Topology hiding should be applied for answer messages. If it is configured as Yes, then Topology hiding is performed for AAR answer message before routing the answer message from PCRF to Policy client. If it is configured as No, then no topology hiding is applied for the AAR answer message.

Parameter Name

Unique

Mandatory

Range and default value

Description

Rx_Client_FQDN

Yes

DiameterIdentity Default: n/a,

Indicates the Fully Qualified Domain Name of Rx Client (MCPTT Client).

Sh_Lookup_Required

Yes

Enumerated, Yes/No Default=No

Decides whether Sh Lookup is required upon receiving Rx AAR from Rx(MCPTT) Client.

If configured as Yes, then Sh Lookup is performed by Rx-ShUDR application.

If configured as No, then AAR message is forwarded without processing at Rx-ShUDR application.

Topology_Hiding_Required

Yes

Enumerated, Yes/No Default=No

Decides whether Topology hiding should be applied for answer messages.

If it is configured as Yes, then Topology hiding is performed for AAR answer message before routing the answer message from PCRF to Policy client.

If it is configured as No, then no topology hiding is applied for the AAR answer message.

PDNGWHost_PCRF_Mapping Table

This table contains one to one mapping between PDN Gateway Host and PCRF.

Table 2-3 Details of the PDNGWHost_PCRF_Mapping Table

Parameter Name	Unique	Mandatory	Range and default value	Description
PDNGW_Host	No	Yes	DiameterIdentity Default: n/a,	Indicates the PDN Gateway FQDN
PCRF_FQDN	No	Yes	DiameterIdentity Default: n/a,	Indicates the FQDN of the PCRF

Topology_Hiding Table

This table contains the list of Actual Hostnames and their Pseudo Hostnames in this PCRF Topology Hiding Configuration.

Table 2-4 Details of Topology_Hiding table records

Parameter Name	Unique	Mandatory	Range and default value	Description
PCRF_FQDN	Yes	Yes	DiameterIdentity Default: n/a,	Indicates the actual hostname of the PCRF
Pseudo_FQDN	No	Yes	DiameterIdentity Default: n/a,	Indicates the Pseudo hostname value to be populated in the Diameter Origin-Host AVP for request/answer messages routed from a PCRF to a policy client, or the Diameter Destination-Host AVP for request/answer messages routed from a PCRF to a policy client.

Error_Action_Config Table

This table contains the error action configuration parameters applied to send answer during runtime errors while processing Sh UDR/UDA message.

Table 2-5 Details of Error_Action_Config table records

Parameter Name

Unique

Mandatory

Range and default value

Description

Result_Code

Yes

Integer

Min:1000

Max:5999

This configuration is applicable when the application is configured to send answer during runtime errors while processing AAR/AAA message. This value is used to set the Result-Code AVP of the Answer Message. [Range = 1000 - 5999]

Error_Message

Yes

UTF8String

Max Length: 64,

This configuration is applicable when the application is configured to send answer during runtime errors while processing AAR/AAA. If specified, the Answer is added with Error-Message AVP with the specified Text. [Range = 1 to 64 character]

Vendor_Id

Integer

Min:1

Max: 4294967295

This configuration is applicable when the application is configured to send answer during runtime errors. If the value is specified, the Answer Message consists of Experimental-Result grouped AVP with the specified Vendor-ID [Range=1-4294967295]

System_Config_Options Table

This table contains system wide common configurable options required to process Rx ShUDR Application. This is single record table and configurable from active SOAM server.

Table 2-6 Details of System_Config_Options table records

Parameter Name	Unique	Mandatory	Range and default value	Description
Result_Code	Yes	Yes	Integer Min:1000 Max:5999	This configuration is applicable when the application is configured to send answer during runtime errors while processing AAR/AAA message. This value is used to set the Result-Code AVP of the Answer Message. [Range = 1000 - 5999]
Error_Message	No	Yes	UTF8String Max Length: 64,	This configuration is applicable when the application is configured to send answer during runtime errors while processing AAR/AAA. If specified, the Answer is added with Error-Message AVP with the specified Text. [Range = 1 to 64 character]
Vendor_Id	No	No	Integer Min:1 Max: 4294967295	This configuration is applicable when the application is configured to send answer during runtime errors. If the value is specified, the Answer Message consists of Experimental-Result grouped AVP with the specified Vendor-ID [Range=1-4294967295]
Origin_Host	No	No	DiameterIdentity Default: n/a,	Indicates the Origin-Host value to be used while Sending Sh UDR message from Rx-ShUDR application Business Logic.
Origin_Realm	No	No	DiameterIdentity Default: n/a,	Indicates the Origin-Realm value to be used while Sending Sh UDR message from Rx-ShUDR application Business Logic.