Default Priority

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

Default value is 0.

Message Sla Ms

This is the Service Level Agreement in milliseconds. This defines the number of milliseconds associated with an incoming event/message within which Policy Director (load balancer) has to submit it to Policy Server (QNS) for processing failing which the Default Discard Behavior is applied.

Default value is 1500 ms.

Inbound Message Queue Size

Number of messages waiting to be processed before the inbound overload feature is activated.

Default value is 15000.

Default Instance Rate Limit

This defines the Rate at which incoming messages are staggered before being submitted to the Policy Server.

Default value is 0.

Emergency Message Priority

Default priority assigned to messages related to an emergency session.

Default value is 0.

Default Discard Behavior

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

• MESSAGE_DROP (default) Silently discards the request.
• DIAMETER_TOO_BUSY Sends a response message having Result-Code AVP value set to DIAMETER_TOO_BUSY (3004)

Apply Discard Behavior For Emergency Messages

Indicates if Emergency Messages can be discarded under overload conditions.

Default value is not checked.

Message Handling Rules

Defines specific inbound message overload handling rules based on different criteria. For more information refer to Table 3.

inboundMessageSlaMs

This parameter specifies the Service Level Agreement in milliseconds. This defines the number of milliseconds associated with an incoming event/message within which Policy Director (load balancer) has to submit it to Policy Server for processing failing which the Default Discard Behavior is applied.

If inboundMessageSlaMs is not defined in qns.conf file then the default value of 1500 is used.

Example: -DinboundMessageSlaMs=2000

After modifying the configuration on Cluster Manager execute reinit.sh or copytoall.sh scripts for applying the changes on all VMs as described in the CPS Installation Guide for VMware for this release.

inboundMessageQueueSize

This parameter specified the number of messages waiting to be processed before the inbound overload feature is activated.

If inboundMessageQueueSize is not defined in qns.conf file then the default value of 15000 is used.

Example: -DinoundMessageQueueSizes=5000

After modifying the configuration on Cluster Manager execute reinit.sh or copytoall.sh scripts for applying the changes on all VMs as described in the CPS Installation Guide for VMware for this release.

INPUT

Diameter Client

Diameter client defined under Diameter Clients section. This field is optional, but is used so that different clients (based on realms) can have different priorities. For more information, refer to Diameter Clients.

Protocol

Specific application id value to be used for scoring. This is to match Auth-Application-Id AVP value. For more information refer to Table 4.

Command Code

Specific command code value to be used for scoring. This is to match the Command-Code field. These command codes map to different types of Diameter messages (CCR = 272 RAR = 258 etc).

Default value is 0.

Request Type

Specific request type value to be used for scoring. This is to match the value of the CC-Request-Type AVP only for CCR messages.

• 0 (default) Request Type not used for scoring
• 1 INITIAL_REQUEST (1)
• 2 UPDATE_REQUEST (2)
• 3 TERMINATION_REQUEST (3)

OUTPUT

Priority

Priority value assigned to the message. Higher numerical value will be having higher priority

Default value is 0.

Per Instance Tps

Transactions per second limit per process. This is the TPS that these messages are limited to. Note that this is per CPS process so if there are 20 Policy Server VM's with 1 Policy Server java process the total TPS is this number x 20.

The actual system's transaction per second limit can be calculated using the following formula

Per Instance Tps x Number of instances per VM x Number of VMs

Default value is 0.

Discard Behavior

Behavior to be applied to an incoming message.

• MESSAGE_DROP (default) Silently discards the request.
• DIAMETER_TOO_BUSY Sends a response message having Result-Code AVP value set to DIAMETER_TOO_BUSY (3004)

GY_V8

Standard Gy application as per 3GPP TS 32.299

GX_SCE

Custom Gx implementation

RF_V10

Not supported

RF_VERIZON

Not supported

RX_TGPP

Standard Rx application as per 3GPP TS 29.214

SH_TGPP

Standard Sh application as per 3GPP TS 29.329

SY_V11

Standard Sy application as per 3GPP TS 29.219

GX_HUAWEI

Custom Gx implementation

SD_V11

Standard Sd application as per 3GPP TS 29.212

GX_TGPP (default)

Standard Gx application as per 3GPP TS 29.212

GXX_TGPP

Not supported

GX_ALLOT

Custom Gx implementation

RX_CLIENT

Local MINE adapter

GY_V8_PROXY

Gy proxy implementation as per RFC 3588

GX_TGPP_PROXY

Gx proxy implementation as per RFC 3588

SY_TGPP_PROXY

Sy proxy implementation as per RFC 3588

SY_OCS

Sy Proxy from OAM (PCRF) end

GY_RECHARGE_WALLET

Support Gy client functionality with external OCS (ECUR model only)

SY_PRIME

Custom Sy implementation as per RFC 3588

RX_TGPP_PROXY

Rx proxy implementation as per RFC 3588

Next Hop Realm

DRA realm name as received in Origin-Realm AVP in CER or CEA message.

Next Hop Hosts

DRA hosts name list as received in Origin-Host AVP in CER or CEA message.

Application Id

Diameter application id advertised as being supported by the DRA. It contains information that identifies the particular service that the service session belongs to.

Destination Realms Pattern

Actual destination realm name pattern as received in Origin-Realm AVP in AAR message. The pattern needs to follow the standard Java regular expression syntax described here.

Destination Host Pattern

Actual destination host name pattern as received in Origin-Host AVP in AAR message. The pattern needs to follow standard Java pattern conventions. The pattern needs to follow the standard Java regular expression syntax described here.

Application Id

The Diameter Application ID (Auth-Application-Id) on the message which is to be retired.

Default: 0

Command Code

The Diameter command code of the message which is to be retried.

Default: 0

Result Code

This is the result code received in the diameter response for which the user wants to retry. The values configured should be a valid diameter result code value or an experimental result code value. For example, 3002 (DIAMETER_UNABLE_TO_DELIVER) received in RAA.

Permanent failure result codes 5xxx and successful result codes 2xxx should not be configured (where, x denotes a valid number).

However, if configured CPS, will retry for it.

Default: 0

Is Experimental

If this check-box is selected, it means that the value configured in the Result Code column is an Experimental-Result-Code value.

This is necessary because there are few values which are the same for both experimental-result-code and result-code.

Default: Not selected

Action

The action for the CPS platform to take after the Diameter Response is received. The options are Retry or None.

• Retry - CPS will retry the request message identified by the value in the command code column depending on the retry count configured in Retry Count column.

• None - No retry.

Default: None

Action Timer (Ms)

The amount of time in milliseconds for CPS to wait before retry.

Default: 0

Retry Count

The number of times to retry when the action is “Retry”.

Default: 1

Retry on Alternate

Configures CPS to retry on any alternate peer configured in Policy Builder.

Default: Not selected

Backoff Algorithm

The back-off algorithm used while determining the actual delay between retry attempts. Currently, only one option (CONSTANT_INTERVAL) is supported.

• LINEAR_INTERVAL: Causes the configured retry interval to increase linearity with each attempt using the formula retry interval = Action Timer (Ms) x current retry attempt number.

  For example, Action=Retry, Action Timer (Ms)=200, Retry Count=3, Backoff Algorithmm=LINEAR_INTERVAL will trigger the first retry after 200 x 1 = 200 ms, the second retry after 200x2 = 400 ms, the third retry after 200x3 = 600ms

• CONSTANT_INTERVAL: Causes the configured retry interval to be used (without any change) for delay for all retry attempts (other options like exponential back-off where retry interval increases exponentially are currently not supported/implemented).

Default: CONSTANT_INTERVAL

Application Id

The diameter interface in numeric format (Auth-Application-Id) on which the message is received. For example Sy (16777302) and Sd (16777303).

Currently only Sd and Sy interfaces are supported.

Default: 0

Command Code

The diameter message type. For example SLR (8388635) in case of Sy and RAR (258) in case of Sd.

Default: 0

Request Type

The request type of the message for Sy interface. For example INITIAL_REQUEST (0) INTERMEDIATE_REQUEST (1). For Sd Request Type is not valid.

Default: 0

Result Code

The result-code received in the response for which the action over Gx and/or Sy/Sd is to be taken.

Default: 0

Is Experimental

If this check-box is selected, it means that the value configured in the Result Code column is an Experimental-Result-Code value.

This is necessary because there are few values which are the same for both experimental-result-code and result-code.

Default: Not selected

Action

The action to be taken over the Sy/Sd interface when the response is received. Possible actions are Continue/Terminate/Reinitiate.

• Continue (default) In case of Continue CPS just continues with the session and does not clear the session from the DB.
• Terminate (for Sd) In case of Terminate CPS removes the session from database after triggering a Session Removal RAR over Sd interface.

  Terminate (for Sy) In case of Terminate CPS removes the session from database after triggering a Session Removal STR over Sy interface.

• Reinitiate (for Sd) In case of Reinitiate CPS first triggers a Session Removal RAR over Sd interface. Once we receive Sd RAR response (any result-code) CPS removes the old session and triggers creation of a new session by sending out a TSR towards TDF.

  Reinitiate (for Sy) In case of Reinitiate CPS first triggers a Session Removal STR over Sy interface. Once we receive Sy STR response (any result-code) CPS removes the old session and triggers creation of a new session by sending out SLR towards OCS.

Action Over Gx

The action to be taken over the Gx interface when the response is received. Possible actions are None/Terminate/Reauthorize.

Currently Action over Gx is not supported for Sd RAR.

• None (default) No action would be taken on Gx interface.
• Terminate In case of Terminate CPS would terminate the Gx session by sending a RAR with Session Release Cause. Also CPS would be sending STR which would then clear the corresponding Sy device session. If the action over Gx is TERMINATE the action over Sy does not matter as the Sy session would be terminated.
• Reauthorize In case of Reauthorize CPS would mark the Sy session as waiting for action over Gx and would mark corresponding Gx session as needing action over Gx as Re-Auth.

The Gx Network Device Manager would then perform the ReAuthorization by sending RAR over Gx interface. On receiving RAA the action over Sy interface would then be performed. If the Gx session is stale and we receive DIAMTER_UNKNOWN_SESSION_ID the Sy session would then be automatically terminated irrespective of the action configured on Sy interface.

User Uri As Fqdn

Sets the Origin-Host AVP value in CER/CEA to the user URI value instead of FQDn value. Default value is not set.

Stop Timeout Ms

Determines how long the stack waits for all resources to stop. The delay is in milliseconds.

Default value is 10000.

Cea Timeout Ms

Determines how long it takes for CER/CEA exchanges to timeout if there is no response. The delay is in milliseconds.

Default value is 10000.

Iac Timeout Ms

Determines how long the stack waits before retrying the communication with a peer that has stopped answering DWR messages. The delay is in milliseconds.

Default value is 5000.

Dwa Timeout Ms

Determines how long it takes for a DWR/DWA exchange to timeout if there is no response. The delay is in milliseconds.

Default value is 10000.

Dpa Timeout Ms

Determines how long it takes for a DPR/DPA exchange to timeout if there is no response. The delay is in milliseconds.

Default value is 5000.

Rec Timeout Ms

Determines how long it takes for the reconnection procedure to timeout. The delay is in milliseconds.

Default value is 10000.

Peers

Defines which peer names are allowed to initiate connections towards PCRF.

Local Host Name

Identifies the local host name of the Policy Director (load balancer) that identifies and will allow an incoming connection from the Peer.

Instance Number

Indicates the assigned number of the Policy Server (QNS) process that will initiate a connection with the Outbound Peer.

Default value is 0.

Rating

Priority assigned to this peer for delivering a PCRF initiated request. The higher the rating value the higher is the priority assigned to the peer.

Default value is 1.

Port Range

Should be specified only when the underlying transport connection Is SCTP and not required when the same is TCP.

Response Timeout

Cisco recommends not to use this parameter.

Name Pattern

Origin-Host AVP value in CER needs to validate against this pattern in order for the connection to be established. If that doesn't happen the CER is silently discarded and the TCP connection is reset by PCRF.

Name pattern check will not happen if Accept Undefined Peer option described in Diameter Stack Configuration is checked.

The Name Pattern needs to follow the standard Java regular expression syntax described here.

Realms

Defines which peer realms are allowed to initiate connections towards PCRF.

Peer Type

Not used with inbound realms.

Processing Protocol

Mapping between the realm name and the specific PCRF logic that should be applied for the message. For more information on processing protocol refer to Table 4.

Rating

Priority assigned to this realm for delivering a PCRF initiated request. This is only used with SY_PRIME processing protocol.

The lower the rating value, the higher is the priority assigned to the realm. For example, a realm having Rating=10 is used after a realm having Rating=1.

Default value is 0.

Stats Alias

Whatever the statistics that gets generated for the respective realm will get the name that is configured in “Stats Alias” appended to those statistics.

This is applicable for com.broadhop.message mbean statistics only.

Name Pattern

Origin-Realm AVP value in CER needs to validate against this pattern in order for the incoming message to be processed. If that doesn't happen the message is silently discarded and the TCP connection is reset by PCRF.

The Name Pattern needs to follow the standard Java regular expression syntax described here.

Peers

Defines the peers to which CPS can initiate connections.

Local Host Name

Identifies the local host name of the Policy Director (load balancer) that initiates a connection with the said Peer.

Instance Number

Indicates the assigned number of the Policy Server (QNS) process that will allow an incoming connection from the Peer.

Default: 0

Rating

Priority assigned to this peer for delivering a PCRF initiated request. The higher the rating value the higher is the priority assigned to the peer.

Default: 1

Port Range

Should be specified only when the underlying transport connection is SCTP and not required when the same is TCP. However in mixed mode where both SCTP and TCP co-exist then it is mandatory to provide port range values for both TCP and SCTP peers in order to avoid any conflicts on using local ports on same host.

Response Timeout

Cisco recommends not to use this parameter.

Name

Peer host name. Peer host name needs to be mapped to a valid IP address or the diameter connection is not initiated. By default the connection is initiated on the standard diameter port (3868). If a different port needs to be used than the peer name shall be defined using the host:port format.

Default value is “default”.

Transport Protocol

Allows you to select either 'TCP' or 'SCTP' for the selected diameter stack instance. Default value is TCP.

Multi Homing Hosts

This is a comma separated list of IP addresses that CPS will use to start the client connections towards external diameter peer. If either TCP/SCTP or both TCP and SCTP are configured in the Outbound Peers (Peers) table then client connections to the peers will be initiated based on whether the PD instance is started as a ‘SCTP’ or ‘TCP’ stack. Mixed mode of client and stack running on both ‘TCP’ and ‘SCTP’ is not currently supported by diameter.

Realms

Defines the realms to which CPS can initiate connections.

Peer Type

This indicates which diameter server to use when there are multiple target servers for the same protocol. This is only used with SY_PRIME processing protocol.

Processing Protocol

Mapping between the realm name and the specific PCRF logic that should be applied for the message. For more information on processing protocol refer to Table 4.

Rating

Priority assigned to this realm for delivering a PCRF initiated request. This attribute is not currently used. This is only used with SY_PRIME processing protocol.

The lower the rating value, the higher is the priority assigned to the realm. For example, a realm having Rating=10 is used after a realm having Rating=1.

Default: 0

Stats Alias

Whatever the statistics that gets generated for the respective realm will get the name that is configured in “Stats Alias” appended to those statistics.

This is applicable for com.broadhop.message mbean statistics only.

Name

Origin-Realm AVP value in CER needs to validate against this pattern in order for the incoming message to be processed. If that doesn't happen the message is silently discarded and the TCP connection is reset by PCRF.

The Name Pattern needs to follow the standard Java regular expression syntax described here.

Name

The client name that is going to be used to reference this particular client in the service configuration object.

Realm Pattern

The pattern that peer realm name should match in order for this diameter client to be used. The pattern needs to follow the standard Java regular expression syntax described here.

The first choice for Realm Pattern value should always be the exact peer realm name whenever possible.

Extract Avps

See Extract Avps

Copy Current Diameter Client

This action creates a new diameter client that is an exact copy of the current diameter client. The only difference between the original and the copy is that “-Copy” is appended to the name of the copy.

The Copy action works exactly the same for all types of diameter clients.

Session Binding Attribute

Allows the Rx sessions initiated by this client to bind to the Gx session by other attribute than the IP address as per 3GPP TS 29.214. For more information refer to Table 2.

Flow Description Source Ip Evaluation

• None: When selected, CPS does not take any action on source IP.

• Replace with 'any': When selected, CPS replaces the flow description source IP with ‘any’.

• Replace with UE IP: When selected, CPS replaces flow description source IP with UE framed IP.

STA Hold Time Ms

This parameter is used to define the timer by which the STA will be held back. Once the timer expires even if the CCR-U is not received, STA will be sent to the AF and the rxSession will be removed.

Default value is 4000 milliseconds.

CCR-U Wait Time (in seconds)

CCR-U timer is started for every request (default bearer boost/spawning of dedicated bearer) from AF if the CCR-U is configured in Policy Builder and CUSTOM_DPCC_STATUS_REPORT(200) is armed in AAR request. There is a separate timer event for different Rx client.

This timer is stopped by PCRF when CCR-U is received from P-GW. Also in case when P-GW does not respond to Gx-RAR then CCR-U timer is stopped on receiving internal Gx-RAA (result-code=7000) message.

CCR-U timer is helpful in informing AF if the QoS requested through AF is updated on P-GW. In case of default bearer QoS boost/throttle request from AF, there is no notification sent by the P-GW to PCRF. In this case PCRF internally runs this CCR-U time which on expiry sends an update (through Rx_RAR having DPCC-Status AVP) to AF that QoS request is served.

There is no default value for this timer. If you want to start CCR-U timer, then you need to configure through Policy Builder. The maximum value is 15 seconds.

Emergency URN List

The list of URNs that are used to indicate that a AF session relates to emergency traffic as per procedures described in 3GPP TS 29.214. For more information refer to Wildcard URN. See Emergency URN List.

Override AF App Id with URN for Emergency sessions

When selected, CPS overrides the AF-Application-Identifier AVP value with the Service-URN AVP value for emergency calls. This option is provided in order to overcome the lack of AF-Application-Identifier AVP value in Rx AAR in case of IMS emergency calls.

The default setting is unchecked.

Validate Flow-Description AVP Value

When selected, CPS validates the Flow-Description AVP values received as part of Media-Sub-Component based on restrictions provided in the 3GPP 29.214 Release 11 specification. If the Flow-Description value does not comply with the format specified then the AAR request is rejected with FILTER_RESTRICTIONS (5062) value in Experimental-Result-Code.

When unchecked, CPS does not validate the Flow-Description AVP value and simply forwards it is as is to PCEF as part of generated rules.

The default setting is unchecked.

29.213 standard QoS for preliminary service

When selected, CPS supports the QoS handling for Preliminary Service Status. So, on receiving Service-Info-Status AVP as preliminary service information from AF, CPS will generate the dynamic PCC rule and assign QCI and ARP values of the default bearer to these PCC rule to avoid signaling to the UE.

When unchecked, CPS ignores the Service-Info-Status AVP value and derive the ARP and QCI values as per the QoS derivation algorithm defined in 3GPP TS 29.213 specification.

The default setting is unchecked.

Auto Increment Precedence Avp

When selected, CPS automatically increments the precedence AVP value by 1 for every Rx charging rule that is installed as part of any Rx session that is using this Rx client within the same Gx session. For example, Gx session (Gx1) has one Rx session (Rx1). When Rx1 is created, two charging rules are installed and they are assigned precedence values 1 and 2. A second Rx session (Rx2) starts for Gx1 and also installs two Rx charging rules. These rules are assigned precedence values 3 and 4.

The precedence values are stored in the Gx session in the rxPrecedenceCounter attribute.

Using this option overrides any other Rx charging rule precedence settings (for example, any that may have been configured for the RxSponsoredDataChargingParameters service option).

You can use the Precedence Start Value and Precedence End Value options to set lower and upper limits for the precedence AVP values. If you do not set these options, the starting precedence value is set to 1 and will increment to 9223372036854775807.

The default setting is unchecked.

Remove Rule On Rule Deactivation

When selected, CPS manages the expiration of Rule-Deactivation time triggers. On expiration of the installed Rule-Deactivation time, CPS initiates removal of the inactive dynamic rules and tear-down of the existing Rx session.

The default setting is unchecked (false).

Authorize Sponsor Data Connectivity

When selected, CPS validates the sponsor ID received in AAR request. If the received sponsor ID is unauthorized, CPS returns UNAUTHORIZED_SPONSORED_DATA_CONNECTIVITY (5067) code in AAA.

The default setting is unchecked (false).

Enforce Unique AF-Charging-Identifier

When selected, CPS enforces a unique AF-Charging-Identifier across all Rx sessions within a given subscriber or network session. During an Rx session establishment, if there is already an Rx session (within the subscriber or network session) containing the same AF-Charging-Identifier value, CPS rejects the new Rx session with DUPLICATED_AF_SESSION (5064) experimental result code.

The default setting is unchecked.

Send timezone and location info in AAA Response

When selected, CPS sends time zone and location information in an Rx AAA response message provided that 3GPP-MS-TimeZone AVP and 3GPP-User-Location-Info AVP are already received in the CCR message.

To receive the updated time zone and location information in the Rx AAA message, CPS should arm the UE_TIME_ZONE_CHANGE event trigger and USER_LOCATION_CHANGE event trigger in the service option under Event-Trigger configuration.

Extract Avps

See Extract Avps.

Netloc Access Not Supported Configuration

See Netloc Access Not Supported Configuration.

Precedence Avp Lower And Upper

Precedence Start Value

When selected, CPS automatically increments the precedence AVP value by 1 for every Rx charging rule that is installed as part of any Rx session using this Rx Client, within the same Gx session. The precedence values are stored in the Gx session in the rxPrecedenceCounter attribute.

This value is optional, but when used, must be greater than 0 and less than the Precedence End Value.

Precedence End Value

The upper limit of the precedence values for Rx charging rules that are installed. When this value is reached, the rxPrecedenceCounter is reset to the Precedence Start Value.

This value is required when using the Precedence Start Value. It must be greater than the start value.

IP Address (default)

Attempts to bind by

• 1 Framed-IP-Address

• 2 Framed-IPv6-Prefix

IMSI and APN

IMSI value and APN value from incoming request

MSISDN and APN

MSISDN value and APN value from incoming request

Load By Realm And User Id

If checked attempts to load the session by realm (Origin-Realm AVP value) and User Id.

Default value is unchecked.

Load By Apn And User Id

If checked attempts to load the session by APN (Called-Station-Id AVP value) and User Id.

Default value is unchecked.

Extract Avps

See Extract Avps

IMSI

Subscription-Id-Data AVP value under Subscription-Id grouped AVP where Subscription-Id-Type AVP value is END_USER_IMSI (1)

MSISDN

Subscription-Id-Data AVP value under Subscription-Id grouped AVP where Subscription-Id-Type AVP value is END_USER_E164 (0)

NAI

Subscription-Id-Data AVP value under Subscription-Id grouped AVP where Subscription-Id-Type AVP value is END_USER_NAI (3)

Input

Gx CCR-i

Gx Realm

Origin-Realm

Gx Host Pattern

Origin-Host

Output

Sd TSR

TDF Realm

Destination-Realm

TDF Host

Destination-Host

Push Pre Configured Rule Options

Controls whether the configured default bearer QoS will be installed on the default bearer or on the secondary bearers.

• PushOnDefaultBearerQoS (default)
• PushWithUpgradedDefaultBearerQoS

Logical Apn

Allows for a default APN name to be defined. This APN name is going to be further used as an input into the AF Application Id Validation feature described below. The APN value will be set based on the available data and the priorities described below.

• 1 - A policy derived AVP having the same value as the Logical Apn
• 2 - Called-Station-Id AVP from incoming Rx AAR
• 3 - Called-Station-Id AVP from Gx session

Gx Client QoS Exclusion List

Gx client names that are allowed not to have a default bearer QoS installed. In case a default bearer QoS has not been configured in the policy and the Gx client name has not been added to this list an error response will be sent to the PCEF containing the Result-Code AVP value DIAMETER_ERROR_BEARER_NOT_AUTHORIZED (5143).

Grant Requested QoS

Controls whether the requested QoS should be granted or not as the default bearer QoS.

Default value is unchecked.

Grant Requested Qos Over Global Qos

If this option is selected then the requested QoS should be granted even if the global QoS is provisioned. There are three type of QoS first is taken from service second is from default QoS and third one is from request. If this flag is checked then requested QoS will take priority over default QoS.

Default value is unchecked.

Global Default Granted QoS

Qci

The QoS class identifier identifies a set of IP-CAN specific QoS parameters that define QoS excluding the applicable bitrates and ARP. It is applicable both for uplink and downlink direction. The QCI values 0 10 – 255 are divided for usage as follows

• 0 - Reserved
• 10-127 - Reserved
• 128-254 - Operator specific
• 255 - Reserved

Max Req Bandwidth UL

It defines the maximum bit rate allowed for the uplink direction.

Max Req Bandwidth DL

It defines the maximum bit rate allowed for the downlink direction.

Guaranteed Bit Rate UL

It defines the guaranteed bit rate allowed for the uplink direction.

Guaranteed Bit Rate DL

It defines the guaranteed bit rate allowed for the downlink direction.

Apn Agg Max Bit Rate UL

It defines the total bandwidth usage for the uplink direction of non-GBR QCIs at the APN.

Apn Agg Max Bit Rate DL

It defines the total bandwidth usage for the downlink direction of non-GBR QCIs at the APN.

Enable Pending Policy Evaluation

When selected, pending policy calculation is enabled for one look ahead in advance.

Ims Apn

List of IMS APNs for which the MPS feature is supported.

This field can accommodate several Ims Apn that are used to match with the incoming service request for priority service. The values that are received by the Default Bearer QoS are looked up for a suitable Ims Apn match. If the APN value of a Gx session request matches IMS APN IMS signaling priority from EMPS service is used as priority level.

Mps QoS

For information on parameters under Mps QoS refer to ARP Parameters.