PCC (Tx/Rx)


The Tx and Rx tabs contain the parameters that define the Tx and Rx interfaces to the PCRF, respectively. Landslide emulates the Application Function (AF) to provide the Tx/Rx interface to the PCRF.

During Network Host testing, the Rx tab contains the PCC parameters that define the Rx Interface between the PCRF and the AF Node.

NOTE: Although defined slightly different in their associated standards, both the 3GPP and 3GPP2 organizations have implemented a policy decision function and associated reference points. 3GPP2 defines the reference points as Tx and Ty, while 3GPP defines them as Rx and Gx.

Parameter Index

PCC (Rx > PCC in Network Host TC)

(DRA Nodal)

Media Flows

Optional Messages

(DRA Nodal TC)

2nd Media Component Description

 

 

 

Media Component Description (Audio/Video/Messaging/RTT)

Media Sub Component

MSC1

 

 

 

User IP to Destination IP

Destination IP

 

 

 

 

 

Codec-Data

Include Codec Data

Codec 1

 

Number of Codecs

 

 

Signalling Flows

  • Enable PCC For AF Signalling Flows

Signaling Options

  • Subscribe to Notification of Release of Bearer
  • Subscribe to Notification of Loss of Bearer
  • Provision Signaling Flow Information


NOTE: The Open/Close timers (Open Gate After Session Established and Close Gate After Gate Opened) are not used in DRA Nodal test case, as it uses the  message flows and message timers to simulate what messages are sent and when they are sent.
Open Gate After Session Established Enter the number of seconds after the session is established to enable an IP flow (gate open).
Close Gate After Gate Opened Enter the number of seconds after the gate is opened to disable an IP flow (gate closed).

 

^ Back to Top


Optional Messages

Service Information Request Indicates that the AF requests the PCRF to demand service information at each bearer authorization.
Charging Correlation Exchange Indicates that the AF requests the PCRF to provide an access network charging identifier to the AF at each bearer establishment/modification, when a new access network charging identifier becomes available.
Indication of Loss of Flow Indicates that the AF requests the PCRF to provide a notification at the loss of a bearer.
Indication of Recovery of Flow Indicates that the AF requests the PCRF to provide a notification at the recovery of a bearer.
Indication of Release of Flow Indicates that the AF requests the PCRF to provide a notification at the release of a flow.
Indication of Establish of Flow Indicates that the AF requests the PCRF to provide a notification at the establishment of a flow.

 

^ Back to Top


Media Flows

# of Rx Media Sessions per Subscriber

Available in IMS Node (proxy Mode),  MME Nodal, PGW Nodal, SGW Nodal, Wifi Offload Gateway Nodal (With VoLTE, Rx Interface and P-CSCF Mode in Proxy mode), and PCRF Node when Rx interface is enabled.

Support for VoLTE / AF Functionality in the case of Multiparty Conference with regard to NETLOC feature.  

Select to provide a unique Rx Client Session per SIP Dialog.

Range: 1 to 64

Default: 1

Tcl Parameter: TxClnRxSessPerSub

Tcl Parameter: TxSrvRxSessPerSub

Preemption Control Info

Part of the Mission Critical Push-To-Talk (MCPTT) services. Enable the MCPTT check box on IMS Node emulator configuration.

Select the Preemption Control Info.

Pre-emption-Control-Info AVP (553)

Contains bit mask that indicates to PCRF on how to perform pre-emption among multiple potential media flow candidates of the same priority. Only one bit may be enabled at any given time.

Bit

Name

Description

0

Most recent added flow

This bit, when set, indicates that the most recent added flow is to be pre-empted.

1

Least recent added flow

This bit, when set, indicates that the least recent added flow is to be pre-empted.

2

Highest bandwidth flow

This bit, when set, indicates that the highest bandwidth flow is to be pre-empted.

 

Options: Most recent added flow (default), Least recent added flow and Highest bandwidth flow.

Tcl Parameter: TxClnPreemptCtrlInfoEn

Tcl Parameter: TxClnPreemptCtrlInfo

MCPTT Identifier

Part of the Mission Critical Push-To-Talk (MCPTT) services. Enable the MCPTT check box on IMS Node emulator configuration.

Select to enter MCPTT Identifier. AF may include the MCPTT-Identifier AVP to indicate that the new AF session relates to an MCPTT session with priority call. This AVP is required in AAR. MCPTT-Identifier AVP (547).

Range: Up to 255 Characters.

Default: mcpttp

Tcl Parameter: TxClnMcpttIdEn

Tcl Parameter: TxClnMcpttId

GCS Identifier

Part of the Mission Critical Push-To-Talk (MCPTT) services. Enable the MCPTT check box on IMS Node emulator configuration.

Select to enter GCS Identifier. Indicates that an AF session relates to a group communication session that requires prioritization. This AVP is required in AAR. GCS-Identifier AVP (538).

Range: Up to 255 Characters.

Default: GCS

Tcl Parameter: TxClnGcsIdEn

Tcl Parameter: TxClnGcsId

Configure Media Component Description

In SGW Nodal, MME Nodal, and in IMS Node test cases, select to indicate using manually provided Media-Component-Description attributes for constructing Media-Component-Description AVP rather than from SDP offer/answer procedure.

NOTES:
  • In IMS Node test case, The functionality applies to both remote and local IMS Node.
  • In SGW Nodal and MME Nodal test case, the Rx | PCC tab is available when you select Enable Rx on VoLTE| IMS Node pane when IMS Node Type is Local.

 

Select Configure Media Component Description to enable Media Component Description pane on Rx > PCC tab (in IMS Node TC).

When selected

Rx Client constructs Media-Component-Description AVP from both SIP/SDP and the attributes you configure on the Rx > PCC | Media Component Description pane.

  • If an attribute is not present in SIP/SDP it is taken from the attributes you configure on the Media Component Description pane
  • If an attribute is present in both SIP/SDP and the Media Component Description pane, the SIP/SDP offer/answer takes precedence unless you select to Override SDP attributes.
When Not Selected   Rx Client constructs Media-Component-Description AVP from SIP/SDP offer/answer procedure.

 

Tcl Parameter: TxClnConfigMcdEn

Apply From SDP

Define the SDP (from offer or from answer) applied to construct Media Component Description AVP.

Option:

The value you select is reflected in Codec-Data AVP. For example, when Codec configuration is from SDP (that is, Override SDP is not selected) Codec-Data AVP may be constructed as follows (example):

“uplink \n offer \n m=audio 6000 RTP/AVP 0 \n” or

“uplink \n answer \n m=audio 6000 RTP/AVP 0 \n”

 

Tcl Parameter: TxClnApplyFromSdp

NOTE: The value of Apply from SDP is not used to change IMS Node message flow. It allows you to change/override the MCD AVP you want in the AAR.
Override SDP

Available when you select Configure Media Component Description. Allows you to replace SDP attributes by the values configured in Rx > PCC | Media Component Description pane.

When selected

Configuration from Rx > PCC | Media Component Description pane overrides the attributes from SDP offer/answer procedures.

When Not Selected   Attributes from SDP offer/answer procedures overrides configured attributes from Rx > PCC | Media Component Description pane.

 

Tcl Parameter: TxClnOverrideSdpEn

Use Protocol from SDP in Packet Filters

Available on IMS Node when Rx Interface is enabled and when "Configure Media Component Description" is not enabled.  

Select to use the Protocol from the SDP in the Packet Filters. (Per TS 29.213 - See rules for derivation of Media-Sub-Component AVP from SDP media component)

Tcl Parameter: TxClnUseFilterProtoFromSdpEn

Port Information In Packet Filter Description

Available on IMS Node when Rx Interface is enabled and when "Configure Media Component Description" is not enabled.  

Provides flexibility for determining the position of port number in the filter description.

Uplink

Include local port

Select to include the local port in the uplink section. (default)

Tcl Parameter: TxClnLocalPortUpLinkEn

Include remote port    

Select to include the remote port in the uplink section.

Tcl Parameter: TxClnRemotePortUpLinkEn

 

Downlink

Include local port

Select to include the local port in the Downlink section.

Tcl Parameter: TxClnLocalPortDownLinkEn

Include remote port    

Select to include the remote port in the Downlink section. (default)

Tcl Parameter: TxClnRemotePortDownLinkEn

 

 

^ Back to Top


Voice,  Video, Messaging and RTT (Real Time Text) tabs

Allow users to configure the Media Component Description for the Rx interface and is available for each media type: Audio, Video, Messaging and RTT.

The MCD Template allows you to configure relevant AAR/AAA exchange with PCRF in addition to the SIP/SDP on SGW/MME Nodal information. You may configure different templates for Voice,  Video, and SIP/SDP messages.

The Voice,  Video, Messaging and RTT tabs allow you to define parameters to override the Media-Component-Description and the Media Sub-Component.

Media Component Description

DRA Nodal Test Case
Enable 2nd Media Component Description

Select to enable a second set of MCD (Media Component Description) tab

Tcl Parameter: TxClnConfig2ndMcdEn   


AF Application Identifier

Indicates the Application Function (AF) with an identifier string. Media-Component-Description AVP (517).

Ending digit in TCL Parameters = Audio = 0, Video = 1, Messaging = 2 and RTT = 3

Tcl Parameters:

TxClnAFAppIdentEn_0

TxClnAFAppIdentEn_1

TxClnAFAppIdentEn_2

TxClnAFAppIdentEn_3

TxClnAFAppIdent_0

TxClnAFAppIdent_1

TxClnAFAppIdent_2

TxClnAFAppIdent_3

RR Bandwidth (bps)

Indicates the maximum required bandwidth in bits per second for RTCP receiver reports within the session component.

Range: 1 - 65535

Default: 1

TxClnRRBandwidthEn_0

TxClnRRBandwidthEn_1

TxClnRRBandwidthEn_2

TxClnRRBandwidthEn_3

TxClnRRBandwidth_0

TxClnRRBandwidth_1

TxClnRRBandwidth_2

TxClnRRBandwidth_3

RS Bandwidth (bps)  

Indicates the maximum required bandwidth in bits per second for RTCP sender reports within the session component.

Range: 1 - 65535

Default: 1

TxClnRSBandwidthEn_0

TxClnRSBandwidthEn_1

TxClnRSBandwidthEn_2

TxClnRSBandwidthEn_3

TxClnRSBandwidth_0

TxClnRSBandwidth_1

TxClnRSBandwidth_2

TxClnRSBandwidth_3

 

Max Requested UL (bps)

Indicates the maximum requested bandwidth in bits per second for an uplink IP flow.

Range: 1 - 4294967295

Default: 330

Tcl Parameters:

TxClnMaxReqULEn_0

TxClnMaxReqULEn_1

TxClnMaxReqULEn_2

TxClnMaxReqULEn_3

TxClnMaxReqUL_0

TxClnMaxReqUL_1

TxClnMaxReqUL_2

TxClnMaxReqUL_3

 

Max Requested DL (bps)

Indicates the maximum requested bandwidth in bits per second for a downlink IP flow.

Range: 1 - 4294967295

Default: 330

Tcl Parameter:

TxClnMaxReqDLEn_0

TxClnMaxReqDLEn_1

TxClnMaxReqDLEn_2

TxClnMaxReqDLEn_3

TxClnMaxReqDL_0

TxClnMaxReqDL_1

TxClnMaxReqDL_2

TxClnMaxReqDL_3

 

Min Requested UL (bps)

Indicates the minimum requested bandwidth in bits per second for a Uplink IP flow. Min-Requested-Bandwidth-UL AVP (535).

Range: 1 - 4294967295

Default: 330

TxClnMinReqUlEn_0

TxClnMinReqUlEn_1

TxClnMinReqUlEn_2

TxClnMinReqUlEn_3

TxClnMinReqUl_0

TxClnMinReqUl_1

TxClnMinReqUl_2

TxClnMinReqUl_3

 

Min Requested DL (bps)

Indicates the minimum requested bandwidth in bits per second for a Downlink IP flow. Min-Requested-Bandwidth-DL AVP (534).

Range: 1 - 4294967295

Default: 330

TxClnMinReqDlEn_0

TxClnMinReqDlEn_1

TxClnMinReqDlEn_2

TxClnMinReqDlEn_3

TxClnMinReqDl_0

TxClnMinReqDl_1

TxClnMinReqDl_2

TxClnMinReqDl_3

 

Max Supported UL (bps)

Indicates the maximum supported bandwidth in bits per second for a Uplink IP flow as defined in 3GPP TS 26.114. Max-Supported-Bandwidth-UL AVP (544).

Range: 1 - 4294967295

Default: 330

TxClnMinSupUlEn_0

TxClnMinSupUlEn_1

TxClnMinSupUlEn_2

TxClnMinSupUlEn_3

TxClnMinSupUl_0

TxClnMinSupUl_1

TxClnMinSupUl_2

TxClnMinSupUl_3

 

Max Supported DL (bps)

Indicates the maximum supported bandwidth in bits per second for a Downlink IP flow as defined in 3GPP TS 26.114. Max-Supported-Bandwidth-DL AVP (543).

Range: 1 - 4294967295

Default: 330

TxClnMinSupDlEn_0

TxClnMinSupDlEn_1

TxClnMinSupDlEn_2

TxClnMinSupDlEn_3

TxClnMinSupDl_0

TxClnMinSupDl_1

TxClnMinSupDl_2

TxClnMinSupDl_3

Min Desired UL (bps)

Indicates the minimum desired bandwidth in bits per second for a Uplink IP flow as defined in 3GPP TS 26.114. Min-Desired-Bandwidth-UL AVP (546).

Range: 1 - 4294967295

Default: 330

TxClnMinDesiredUlEn_0

TxClnMinDesiredUlEn_1

TxClnMinDesiredUlEn_2

TxClnMinDesiredUlEn_3

TxClnMinDesiredUl_0

TxClnMinDesiredUl_1

TxClnMinDesiredUl_2

TxClnMinDesiredUl_3

Min Desired DL (bps)

Indicates the minimum desired bandwidth in bits per second for a Downlink IP flow. Min-Desired-Bandwidth-DL AVP (545).

Range: 1 - 4294967295

Default: 330

TxClnMinDesiredDlEn_0

TxClnMinDesiredDlEn_1

TxClnMinDesiredDlEn_2

TxClnMinDesiredDlEn_3

TxClnMinDesiredDl_0

TxClnMinDesiredDl_1

TxClnMinDesiredDl_2

TxClnMinDesiredDl_3

Reservation Priority

Use Reservation Priority to indicate whether a Codec Data is included in a media component description. Select Reservation Priority to include Codec Data in the media component description.

The Reservation Priority value indicates importance of the IP flow and applies to all the IP flows within the Media Component. If the Reservation Priority value is not specified, the IP flow priority is set to the default value (0). The PCRF uses this value to implement priority based admission.

Option: 0 - 7

Default: 0

NOTE: This parameter is available only when AF I/F is Rx during PCRF testing and when Rx Interface is selecting during Network Host testing.

Tcl Parameter:

TxClnResPriorityEn_0

TxClnResPriorityEn_1

TxClnResPriorityEn_2

TxClnResPriorityEn_3

TxClnResPriority_0

TxClnResPriority_1

TxClnResPriority_2

TxClnResPriority_3

 

Media Type

In DRA Nodal test case, select the applicable media type for a session component.

Options:

  • Audio
  • Video
  • Data
  • Application
  • Control
  • Text
  • Message
  • Other
Flow Status

Indicates whether the IP flow(s) are enabled or disabled.

Options:

  • Enable UpLink

  • Enable DownLink

  • Enable

  • Disable

  • Removed

TxClnFlowStatusEn_0

TxClnFlowStatusEn_1

TxClnFlowStatusEn_2

TxClnFlowStatusEn_3

TxClnFlowStatus_0

TxClnFlowStatus_1

TxClnFlowStatus_2

TxClnFlowStatus_3

 

Priority Sharing Indicator

Indicates whether the related media component can use the same allocation and retention as media component (s) which are assigned the same QCI in the PCRF belonging to other AF sessions for the same IP-CAN session that also contains the Priority-Sharing Indicator AVP set to PRIORITY_SHARING_ENABLED. Priority-Sharing-Indicator AVP (550).

Options: Enabled, Disabled

TxClnPrioritySharingIndEn_0

TxClnPrioritySharingIndEn_1

TxClnPrioritySharingIndEn_2

TxClnPrioritySharingIndEn_3

TxClnPrioritySharingInd_0

TxClnPrioritySharingInd_1

TxClnPrioritySharingInd_2

TxClnPrioritySharingInd_3

 

Sharing Key UL

Indicates that the related media of the modified AF Session may share resources with other media components in the related uplink direction that have the same Sharing-Key-UL. Sharing-key-UL AVP (540).

Select to enable Sharing Key UL.

Range: 1 - 4294967295

Default: 1

TxClnSharingKeyUlEn_0

TxClnSharingKeyUlEn_1

TxClnSharingKeyUlEn_2

TxClnSharingKeyUlEn_3

TxClnSharingKeyUl_0

TxClnSharingKeyUl_1

TxClnSharingKeyUl_2

TxClnSharingKeyUl_3

 

Sharing Key DL

Indicates that the related media of the modified AF Session may share resources with other media components in the related downlink direction that have the same Sharing-Key-DL. Sharing-key-DL AVP (539).

Select to enable Sharing Key DL.

Range: 1 - 4294967295

Default: 1

TxClnSharingKeyDlEn_0

TxClnSharingKeyDlEn_1

TxClnSharingKeyDlEn_2

TxClnSharingKeyDlEn_3

TxClnSharingKeyDl_0

TxClnSharingKeyDl_1

TxClnSharingKeyDl_2

TxClnSharingKeyDl_3

AF Requested Data

AF-Requested-Data AVP (551). Indicates the information that the AF requested to be exposed.

 

Bit

Name

Description

0

EPC-level identities required

This bit, when set, indicates that the AF requests the PCRF to provide the EPC-level identities (MSISDN, IMSI, IMEI(SV)) available for that IP-CAN session.

 

Option: EPC-Level Identities Required.

TxClnAfReqDataEn_0

TxClnAfReqDataEn_1

TxClnAfReqDataEn_2

TxClnAfReqDataEn_3

TxClnAfReqData_0

TxClnAfReqData_1

TxClnAfReqData_2

TxClnAfReqData_3

 

^ Back to Top


Media Sub Component

Allows you to choose any MSC (and related QoS values) in a Message flow.

IMS Node Test Case
Include MSC

Select to enable MSCs, and select the Number of MSCs for the MCD from the drop-down list. The number of MSC (Media Sub Component) tabs depend on the value you select from the dropdown list.

Options: 1 through 11

Default: 1

TxClnMSCEn_0

TxClnMSCEn_1

TxClnMSCEn_2

TxClnMSCEn_3

TxClnNumSubComp_0

TxClnNumSubComp_1

TxClnNumSubComp_2

TxClnNumSubComp_3

 


MSC n

(n = the value you select from the list.)

NOTE: The User IP is not configured in IMS Node Test Case (unlike in PCRF Nodal TC) and is applied from incoming SIP requests.

Description 1

Describes packet filter information for an IP flow (for in direction). Enter the User IP to Destination IP.

Tcl Parameter: TxClnMcdSubFlowDesp1En

Tcl Parameter: TxClnMcdSubFlowDesp1

Tcl Parameter: TxClnMcdSubFlowDesp1Desp  

Overwrite User IP With Source IP: Select this option and enter the Source IP for Description 1. This  ensures that the Mobile IP is overwritten with the provisioned Source IP. In addition,  the selection also removes Mobile IP from packet filter in "Follow description" AVP.

Tcl Parameter: TxClnMcdSubFlowDesp1OverwriteEn

Tcl Parameter: TxClnMcdSubFlowDesp1OverwriteSrcpIp

Description 2

Describes packet filter information for an IP flow (for out direction). Enter the Destination IP

Tcl Parameter: TxClnMcdSubFlowDesp2En

Tcl Parameter: TxClnMcdSubFlowDesp2

Tcl Parameter: TxClnMcdSubFlowDesp2Desp  

Overwrite User IP With Source IP: Select this option and enter the Source IP for Description 2. This  ensures that the Mobile IP is overwritten with the provisioned Source IP. In addition,  the selection also removes Mobile IP from packet filter in "Follow description" AVP.

Tcl Parameter: TxClnMcdSubFlowDesp2OverwriteEn

Tcl Parameter: TxClnMcdSubFlowDesp2OverwriteSrcpIp

Flow Status

Indicates whether the IP flow(s) are enabled or disabled.

Options:

  • Enable UpLink

  • Enable DownLink

  • Enable

  • Disable

  • Removed

Tcl Parameter: TxClnMcdSubFlowStatusEn

Tcl Parameter: TxClnMcdSubFlowStatus

Flow Usage

 

Provides information about the usage of IP flows.

Options:

  • No Information

  • RTCP

  • AF Signalling (value of 2)

Tcl Parameter: TxClnMcdSubFlowUsageEn

Tcl Parameter: TxClnMcdSubFlowUsage

Max Request UL

 

Indicates the maximum requested bandwidth in bits per second for an uplink IP flow.

Range: 1 - 4294967295

Default: 30

Tcl Parameter: TxClnMcdSubMaxReqUlEn

Tcl Parameter: TxClnMcdSubMaxReqUL

Max Request DL

 

Indicates the maximum requested bandwidth in bits per second for a downlink IP flow.

Range: 1 - 4294967295

Default: 30

Tcl Parameter: TxClnMcdSubMaxReqDLEn

Tcl Parameter: TxClnMcdSubMaxReqDL

 

^ Back to Top


Codec Data

The Codec Data pane allows you to configure one or multiple Codec-Data within the Media Component Description of the Rx interface.

Include Codec Data

Indicates whether a Codec Data includes a media component description.

Tcl Parameter: TxClnCodecEn_0

Number of Codecs

Indicates the number of Codec Data you wish to provided.  The maximum number of Codec Data you may provide is 2.  Depending on the number of Codec Data you select, an equivalent number of Codec data tabs display for you to enter the actual codec data.

Tcl Parameter: TxClnNumCodecs_0

Codec 1

You may enter 1 codec data and description for each codec.

NOTE: You are responsible for entering correct codec description as multi-lines ASCII text.

 

AVP Line 1: Value Uplink or Downlink.  

  • Uplink indicates a configured SDP is used by UE for sending data to network.

  • Downlink indicates configured SDP is used by network for sending data to UE.  

AVP Line 2: Value Offer, Answer, Description. See RFC 3264.

SDP Lines: The Session Description Protocol (SDP) lines describe a media session. For syntax and Detail information see RFC 4566.

Tcl Parameter:

TxClnCodecLn1_0_1

TxClnCodecLn2_0_1

NOTE: In IMS Node TC, if you select Override SDP, for example, the Codec-Data AVP is constructed as follows.

<AVP line 1> \n <AVP line 2> \n <SDP lines>

For example, if SDP Line value is m=audio 49172 RTP/AVP 0, the Codec-Data AVP value is as follows.

uplink \n description \n m=audio 49172 RTP/AVP 0 \n

Where, description indicates that the SDP lines are not being applied from SDP offer/answer messages.

^ Back to Top


Signaling Flows

Enable PCC For AF Signalling Flows

In IMS Node test case, select to support  AF signaling message flows on Rx interface (Rx sessions for SIP signaling flows), in addition to Rx session for SIP media.

Tcl Parameter: TxClnAfSignalingEn

NOTE: AF Application also processes additional triggers from SIP layer and hence provides AF Signaling in PCRF Node.

 

In PCRF Node test case, select to support the Rx session for SIP signaling (use for back-to-back testing).

NOTE: The PCRF Node | PCC tab contains only  Enable PCC For AF Signalling Flows option.

 

Tcl Parameter: TxSrvAfSignalingEn

Signaling Options

Subscribe to Notification of Release of Bearer

Select to send Notification of Release of Bearer.

When the subscription is active, PCRF sends an RAR to IMS to notify the Bearer is released. If the bearer is releases, P-CSCF may terminate the Rx session, and other related Rx sessions.

Tcl Parameter: TxClnSubscribeRelOfBearerEn

Subscribe to Notification of Loss of Bearer

Select to send Notification of Loss of Bearer.

When the subscription is active, PCRF sends an RAR to IMS to notify the Bearer is lost. If the bearer is lost, P-CSCF may decide to terminate the Rx session, and other related Rx sessions.

Tcl Parameter: TxClnSubscribeRelOfBearerEn

Provision Signaling Flow Information

Select to Provision Signaling Flow Information.

The P-CSCF may provision information for signaling flow after receiving 200 OK in response to the initial register message.

Selecting to send subscription and provision, the AAR will establish one Rx session for both (subscription and provision) purposes.

After provisioning (information to PCRF), the corresponding PCC/QoS rules is activated for the signaling flows.

Tcl Parameter: TxClnProvisionSigFlowInfoEn

 

^ Back to Top