PCF Configuration

  1. Log in into Policy Builder.

  2. Select Reference Data tab.

  3. From the left pane, select Systems.

  4. Select and expand your system name.

  5. Select PCF Configuration.

  6. In the right pane, to add the parameters of the inbound message overload handling, check the Inbound Message Overload Handling check box.

  7. In the Inbound Message Overload Handling area, define the following parameter details.

    Inbound Message Overload Handling Parameters

    Parameter

    Description

    Default Priority

    Default priority to be assigned to an incoming message if no specific priority is defined in the Message Handling Rules table.

    Default value is 0.

    Message Sla Ms

    Service Level Agreement (SLA) in milliseconds, defines the number of milliseconds that are associated with an incoming event or message. In case the configured duration times out, the Default Discard Behavior is applied.

    Maximum time (in millisec) that a message has in an inbound message handling queue waiting for a worker thread. Configuring this value avoids processing a message to time out by a remote peer.

    Default value is 1500 ms.

    Inbound Message Queue Size

    Allows the maximum number of messages in the Inbound Message Queue. When the number of messages exceeds this value, messages are discarded as defined in the Message Handling Rules and the Default Discard Behavior.

    Default value is 1000.

    Default Instance Rate Limit

    This parameter is applied to messages that do not have an applicable overload handling rule configured in the Message Handling Rules table.

    Default value is 0.

    N7 Emergency Message Priority

    Default priority assigned to messages related to an emergency session.. Emergency message priority is applied when the DNN matches an emergency DNN configured under PCF Configuration.

    Default value is 1.

    Default Discard Behaviour

    Default behavior to be applied to an incoming message if no specific priority is defined in the Message Handling Rules table.

    • MESSAGE_DROP: Discards the request.

    • SERVICE_UNAVAILABLE: Service is not available.

    Default value is MESSAGE_DROP.

    Message Handling Rules

    Defines specific inbound message overload handling rules based on different criteria. For more information, see Table 3
    N5 Message Prioritization Rule

    The following tables provides the inputs for N5 Message Prioritization Parameters.

    N5 Message Prioritization Parameters

    Parameter

    Description

    mpsId

    mpsId indicates that an AF session relates to an MPS session. It contains the national variant for MPS service name. For example, NGN GETS.

    resPrio

    The AF specifies the Reservation-Priority (resPrio) attribute at request level in the N5 messages in order to assign a priority to the AF session as well as specify the Reservation-Priority attribute at the medComponents attribute level to assign a priority to the IP flow.

    The Reservation-Priority attribute available at the request level only is used under N5 Message Prioritization table.

    If Reservation-Priority is not found at the message level in N5 message, then best value of Reservation-Priority is calculated from the MCD and used for lookup.

    Range: 1 to 15, where 15 is considered as the highest priority and 1 is considered as the least priority.

    Priority

    A user defined priority based on mpsId and Reservation-Priority combination.

    Higher Priority messages are processed before lower priority messages.

    Inbound Message Overload Handling Parameters
    Message Handling Rules Parameters

    Parameter

    Description

    Request Type

    Specifies request type value to be used for scoring.

    For example N7_CREATE, N28_NOTIFY, and so on.

    Priority

    Priority value assigned to the message. Higher numerical value has the higher priority.

    For example, 700, 800 and so on.

    Per Instance Tps

    Transactions per second limit per process. This value is the TPS that these messages are limited to.

    Default value is 0.

    Discard Behavior

    Behavior to be applied to an incoming message.

    • SERVER_TOO_BUSY: Sends a responsive message having result code attribute value with HTTP code 503.

    • MESSAGE_DROP: Discards the request.