Setting Up a PCRF Node


You can configure a PCRF node to respond to AGW/AF messages received from PCRF SUTs or nodes. This topic will guide you through configuring a PCRF Node test case.

After you have a functioning PCRF node, you can add the PCC Rules.


Before You Start:

You should have a basic understanding of the test system:

^Back to Top


To configure a PCRF node:

Open a PCRF Nodal Capacity test session and add a PCRF Node test case from the Basic library.

Configure the node's address, protocol options, and capabilities.

  1. Select the LTE Spec Version.

  2. Select LTE Mobility to indicate the PCRF handover type as Inter SGW or Intra PGW.

NOTE: When you selct LTE Mobility, none of the other interface selection is available, that is, the AGW I/F, AF I/F, and the BBERF I/F are not available.
  1. Depending on the Test Options selected, interface and Nodes display as shown in the table below.

    Test Options

    Protocol

    Interface, Nodes

    AGW I/F

    Ty Diameter

    Ty, AGW I/F Node

    Gx

    Gx, AGW I/F Node

    R3

    R3, AGW I/F Node
    AF I/F

    Rx/Tx

    Rx/Tx, AF I/F Node (Not available when BBERF is selected, unless AGW I/F Gx is also selected)
    BBERF I/F

    Gxc

    Gxc, BBERF I/F Node
  2. For the diameter protocols, enter the parameters as shown in Diameter Tab. 

  3. In the PCC Rules tab, define the policy rules and charging rules associate with the uplink and downlink IP traffic as described in PCC Rules tab. See also the PCC Rules Overview topic.

  4. In the Gxc QoS Rules tab, define QoS rules associate with the uplink and downlink IP traffic as described in QoS Rules tab. You may also define the events that trigger application of these QoS rules.

You are now ready to test your configuration. The parameters that have not been addressed control optional behaviors that do not affect the success of this test. Click OK to accept the test case. If any parameters fail validation, you will receive an error indicating the problem parameter. Correct the problem and when the definition is accepted, the test case is listed in the Test Session window.

When you run the test session, the PCRF Node test case should start first and should not stop until after the PCRF Nodal test case is finished and the final messages have been received from the PCRF. Use Automation Control to define the test case execution sequencing. Make sure that the stop step for the node includes as a predecessor that the node test case has reached the STOPPED state, and add a delay time of at least 60 seconds to ensure that the PCRF has time to transmit all of the data records to the node. (See Adding Automation Control for instructions.)

Run the test session, and a validation check is performed on the test session. This validation ensures that the IP addresses used by the test case do not conflict with any other test sessions that may be running on the test server, and that the test definition does not violate rate and volume limits. You will also receive an error if you attempt to run the test session on a test server that is already running at capacity or is otherwise unable to accept a test session. See Running a Test Session for more information on handling these types of errors.

Select the Reports tab when it becomes available and then select the PCRF sub-tab. Depending on the Initiate Mode setting, you should see that 1 Node Alive request was either sent (Active) or received (Passive) and that 1 Node Alive response was either received or sent. Select the PCRF Node test case from the Report View drop-down list and explore the measurements displayed on the tabs. The measurement definitions are located in the Measurement Reference. Stop the test session when you are ready to continue, and you should see that PCRF Data Records were received for each PDP context.

TROUBLESHOOT: If a Node Alive request or response was not received, confirm that there is connectivity between the PCRF node and the AF/AGW interface. If you selected Active initiate mode, ensure that you selected the SUT definition for the PCRF interface.