5.4.6 Diameter Configuration for PCA
The PCA (Policy and Charging Application) requires configuration of several Diameter Configuration components before the PCA configuration can be performed.
All Diameter Configuration components are configured using the SOAM (Service Operations, Administration, and Maintenance) GUI (Graphical User Interface).
- Application Ids
The Diameter, Configuration, and Application Ids [Insert] screen to define an Application Id for each Diameter interface that will be used by PCA in the system.
PCA supports values that can be selected from the Application Id Value dropdown list:- 4 - Diameter Credit Control
- 4 - 3GPP Gy/Ro
- 16777236 – 3GPP Rx
- 16777238 – 3GPP Gx
- 16777238 – 3GPP Gx-Prime
- 16777266 – 3GPP Gxx
- 16777267 - 3GPP S9
- 4294967295 – Relay
Note:
Gx-Prime shares the same Application Id as Gx. To distinguish between them, the content of the Diameter message is checked against a configured Application Routing Table to determine if the message originates from a Gx or Gx-Prime interface.PCA always attempts to route using PRT (Peer Route Table). The PRT can be configured here for each Application Id, or can be configured for Peer Nodes. If neither is configured, the Default PRT will be used. See PCA Routing of Diameter Messages.
- CEX (Capabilities Exchange)
Parameters
The Diameter, Configuration, and CEX Parameters [Insert] screen to define the capability exchange parameters for each Application Id that is configured for use by PCA:
For each Application Id, select or enter:- Application Id Type: Authentication
- Vendor Specific Application Id: If the Application Id and Vendor Id will be grouped in a Vendor specific Application Id AVP
- Vendor Id: if
Vendor Specific Application
Id is selected the Vendor ID 10415 is defined in
3GPP as:
- Gx: 16777238 with Vendor-Id of 10415 (Defined in 3GPP 29.212)
- Gx-Prime: 16777238 with Vendor-Id of 10415 (Defined in 3GPP 29.212)
- Gxx: 16777266 with Vendor-Id of 10415 (Defined in 3GPP 29.212)
- Rx: 16777236 with Vendor-Id of 10415 (Defined in 3GPP 29.214)
- S9: 16777267 with Vendor-Id of 10415 (Defined in 3GPP 29.215)
- Gy/Ro: 4 with Vendor-Id of 10415 (defined in 3GPP 32.299)
- CEX Configuration Sets
The Diameter, Configuration, Configuration Sets, and CEX Configuration Sets [Insert] screen to select the configured CEX parameters to use in:
- A CEX Configuration Set to be used for connections with the PCEF (Policy and Charging Enforcement Function) nodes (Gx).
- A CEX Configuration Set to be used for connections with the AF (Application Function) nodes (Rx).
- A CEX Configuration Set to be used for connections with the PCRF (Policy and Charging Rules Function) nodes (Gx and Rx).
- A CEX Configuration Set to be used for connections with the OCS (Online Charging Function ) nodes (Gy/Ro).
- CEX Configuration Sets to be used with any other types of nodes, such as BBERF (Bearer Binding and Event Reporting Function) (Gxx).
- A CEX Configuration Set named Default is provided for the Relay Application Id, it can be edited if needed.
- Transaction Configuration
Sets
The Diameter, Configuration, Configuration Sets, and Transaction Configuration Sets [Insert] screen to configure Transaction Configuration parameters.
The transaction configuration, once configured, needs to be set in the Diameter, Configuration, Peer Nodes screen.
- Local Nodes
The Diameter, Configuration, and Local Nodes [Insert] screen to configure the Diameter identity or identities by which the PCA DSR (Diameter Signaling Router) will be known to peer nodes.
The dropdown list of IP Addresses contains the XSI (External Signaling Interface) addresses configured on DSR MP (Message Processor) servers. If IPFE is being used, a local node should be created for each IPFE (IP Front End) TSA (Target Set Address).
- Peer Nodes
The Diameter, Configuration, and Peer Nodes [Insert] screen to configure PCEFs, AFs, BBERFs, and any other types of nodes as Peer Nodes to the PCA DA-MPs in the system. (PCA DA-MPs can also be Peer Nodes to each other at different sites). Additionally, select a Transaction Configuration Set from the dropdown list.
Note:
For PCA, the Replace Destination-Realm and Replace Destination-Host boxes must be checked for PCRF and OCS peer nodes.See PCA Routing of Diameter Messages for details on routing of messages for PCA.
- Connections
The Diameter, Configuration, and Connections [Insert] screen to configure connections between the PCA DA-MPs and the Peer Nodes.
Any IPFE TSA that is used to configure a connection must use the same Transport Protocol SCTP (Stream Control Transmission Protocol) or TCP (Transmission Control Protocol) that is selected to configure the connection.
- Route Groups
The Diameter, Configuration, and Route Groups [Insert] screen to configure Route Groups for use with PCA Peers.
For priority-based initial CCR-I routing, configure N+1 Route Groups where N is the number of PCRF/OCSs in the system. The first N Route Groups contain one corresponding PCRF or OCS Peer Node in each one, and the last Route Group contains all PCRF/OCSs.
The goal is to setup a routing configuration such that if there is no route available to the suggested PCRF or OCS in an initial (binding capable) session request, Diameter automatically sends the request messages to any other available PCRF or OCS.
Define a Route Group for each PCRF or OCS; enter the Route Group Name, select the Peer Node name (PCRF/OCS name) and enter the Provisioned Capacity as 1.
Define a last Route Group for all PCRF or OCSs, enter the Route Group Name, and then add a Peer Node, Connection, and Capacity entry for every PCRF or OCS. Select the Peer Node (PCRF or OCS) and enter the Provisioned Capacity as 1 for each PCRF or OCS entry.
- Route Lists
The Diameter, Configuration, and Route Lists [Insert] screen to configure Route Lists for use with the configured Route Groups.
For priority based initial session binding, configure N Route Lists where N is the number of PCRF or OCSs in the system.
All Route Lists must contain at least two Route Groups, one for a single PCRF or OCS and one for all PCRF or OCSs.
Assign Priority value 1 to each Route Group for a single PCRF or OCS; assign Priority value 2 to the Route Group containing all the PCRF or OCSs.
Enter 1 for the Minimum Route Group Availability Weight in all of the Route Lists.
- Peer Route Table and
Peer Routing Rules
The Diameter, Configuration, and Peer Route Tables [Insert] screen to configure new Peer Route Tables if needed, and the Viewing Rules for PRT screen to configure Peer Routing Rules, such that DSR forwards messages based on the PCRF or OCS preference.
Peer Routing Rules can be added to the Default Peer Route Table (PRT) or to new Peer Route Tables.
See PCA Routing of Diameter Messages for details on PRT routing of PCA messages.
The routing configuration will ensure whenever PCA requests Diameter to route to a particular PCRF or OCS based on the PRT:- If the PCRF or OCS is available, Diameter will route to it.
- If the PCRF or OCS is not available, Diameter will route the message to any other available PCRF or OCS.
- Application Route Tables and Application
Routing Rules
The Diameter, Configuration, and Application Route Tables [Insert] screen to configure new Application Routing Rules, if needed for each Diameter interface (such as GxGx-Prime, or Rx) that is configured in an Application Name, to be used for Diameter routing of messages to the PCA application. PCA must receive all Diameter Requests.
The Viewing Rules for ART (Applicatin Route Table) screen to view existing Rule Names, configure new rules, or edit, and delete existing Application Routing Rules.
Application Routing Rules can be added to the Default Application Route Table or to new Application Route Tables.
For each rule, enter or select:- Rule Name for a configured Application Id (Diameter interface)
- Priority
- In Conditions, select a hyperlink to view the associated Diameter,Configuration, andApplication Ids (Filtered) screen configured for PCA.
- Application Name: PCA
- Gx-Prime
Note:
Gx-Prime will only be enabled when the Application Id is set to 16777238 – 3GPP Gx. - Applicaton Route table