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. |
PCC
(Rx > PCC in Network Host TC) |
||
(DRA Nodal) |
||
Media Flows |
||
Optional Messages |
||
(DRA Nodal TC) |
|
|
|
|
|
Media Component Description (Audio/Video/Messaging/RTT) | ||
Media Sub Component MSC1
|
|
|
Codec-Data |
|
|
Signalling Flows |
||
Signaling Options
|
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. |
# 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.
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.
Select Configure Media Component Description to enable Media Component Description pane on Rx > PCC tab (in IMS Node TC).
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
|
||||||||||||
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.
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.
|
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. |
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:
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
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:
|
||||||||||||||
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:
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
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
Tcl Parameter:
|
||||||||||||||
Media Type | In DRA Nodal test case, select the applicable media type for a session component. Options:
|
||||||||||||||
Flow Status | Indicates whether the IP flow(s) are enabled or disabled. Options:
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
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
|
||||||||||||||
AF Requested Data | AF-Requested-Data AVP (551). Indicates the information that the AF requested to be exposed.
Option: EPC-Level Identities Required.
|
Allows you to choose any MSC (and related QoS values) in a Message flow.
MSC n | (n = the value you select from the list.)
|
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.
|
||
AVP Line 1: Value Uplink or Downlink.
|
|||
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:
|
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
In PCRF Node test case, select to support the Rx session for SIP signaling (use for back-to-back testing).
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 |