X50-20111205-032 QC TDF-based-Network-Control

Traffic Detection Function Extensions for cdma2000 1x and HRPD
Sources: Qualcomm
Contact: George Cherian ([email protected]),
Jun Wang([email protected])
Dec 05, 2011
Abstract: This contribution proposes extensions to TDF for cdma2000 1x & HRPD networks
Recommendation: Review and adopt for X.S0062 -A
Notice ©2009. All rights reserved.
Qualcomm Incorporated grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the
contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s
standards publication even though it may include all or portions of this contribution; and at the Organizational Partner’s sole discretion to permit others to reproduce in whole or
in part such contribution or the resulting Organizational Partner’s standards publication. Qualcomm Incorporated is also willing to grant licenses under such contributor
copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this
This document has been prepared by the Qualcomm Incorporated to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion
and is not to be construed as a binding proposal on Qualcomm Incorporated. Qualcomm Incorporated specifically reserve the right to amend or modify the material contained
herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the Qualcomm Incorporated other than
provided in the copyright statement above.
Page 1
• TDF for cdma2000 network was proposed in X50-20110725-031r1
CT+ZTE TDF architecture for cdma2000.pptx
• What are the TDF functions as defined by 3GPP?
– The TDF is a functional entity that performs application detection and
reporting of detected application and its service data flow description to
the PCRF.
– TDF performs following functions:
• Gating:
– The gate status indicates whether the application, identified by the application
identifier, may pass (gate is open) or shall be blocked (gate is closed) in uplink
and/or in downlink direction
• Redirection:
– The Redirect indicates whether the detected application traffic should be
redirected to another controlled address. The target redirect address shall also be
• Bandwidth limitation:
– The UL maximum bitrate indicates the authorized maximum bitrate for the uplink
component of the detected application traffic
Page 2
• Extend the Traffic Detection Function for 3GPP2 to
control the following network functions
– Application based charging
– QoS Control
Page 3
Application based charging
• Differentiate charging based on different application
types for a connection
– Operator may apply different charging rules for different
type of traffic with the same application server.
– For example,
• Applications such as Facebook offers different services from
the same server: chat, personal-status-updates, video-call,
audio-call etc.
• Skype offers text chat, video-call, audio call etc
– Current mechanisms of charging based on 5-tuple packet
filter will not work due to:
• Both source & destination IP addresses are the same
• All services uses http port
Page 4
Application based charging - details
• Extend current 5-tuple to 6-tuple as follows:
Source IP addr
Destination IP addr
Source port
Destination port
Application Identifier (added in this proposal)
• Enhance the charging record to use 6-tuple packet filter
– 6-tuple is used to identify the number of packets, QoS etc.
• Accounting entity(PDSN/HA/LMA) hosts TDF
– Mapping of Application type to the Application identifier may either
be pre-configured or be sent to accounting entity (PDSN/HA/LMA)
– When http based application are used, http header/MIME type
may be used to derive application identifier.
Page 5
QoS Control
• BBERF hosts TDF/DPI function
• PCRF installs rules to BBERF using the 6-tuple packet filter
– 6-tuple Packet Filter was discussed earlier
– Option-1: Static-Rules:
• The rules are installed statically at the time of IP connection setup
• The static rules may be set by AAA or by PCRF
– Option-2: The rules are installed dynamically
• TDF signals PCRF when it detects an application whose rules are
not installed
• PCRF obtains the rules from Application Function and passes to
– Application Function identifies the application based on 6-tuple
• Step-2: BBERF sets up different service connections with RAN (A10
connections for (e)HRPD) with different priority
– RAN follows the priority set by the BBERF for scheduling
packets for different service connections
Page 6
QoS Control: RL control
• BBERF passes the 6-tuple packet filter to UE using
– BBERF uses 6-tuple to identify the rule
– ReservationLabel (Flow identifier) is based on 6-tuple
• Application to Application-ID mapping may be configured
at the MS/AT either through pre-configuration or through
configuration-downloading mechanisms
Page 7

similar documents