Cisco Cisco Packet Data Interworking Function (PDIF) Guía Para Resolver Problemas
Policy-Based Management and EV-DO Rev A
▀ Quality of Service in EV-DO Rev A
▄ Cisco ASR 5000 Series Enhanced Feature Configuration Guide
OL-22983-01
A10 connections. The PCF uses A11 messaging to signal new A10 connection creation and to convey the requested and
granted QoS parameters and the mapping of flows to A10 connections.
granted QoS parameters and the mapping of flows to A10 connections.
Important:
If the subscriber is not authorized, the RAN denies the requested QoS profile to the MN and
downgrades the flow to best effort traffic.
The MN sends Traffic Flow Templates (TFTs) that identify different IP flows in both the forward and reverse directions
to the PDSN. The PDSN stores the TFTs. For traffic towards the mobile network, the PDSN uses the TFTs to identify
the traffic flows and to map the flows to different A10 connections and for flow-based accounting. For traffic from the
mobile network, the PDSN looks up the flow for per-flow based accounting. The PDSN also tracks accounting per A10
connection in addition to a per-flow basis.
to the PDSN. The PDSN stores the TFTs. For traffic towards the mobile network, the PDSN uses the TFTs to identify
the traffic flows and to map the flows to different A10 connections and for flow-based accounting. For traffic from the
mobile network, the PDSN looks up the flow for per-flow based accounting. The PDSN also tracks accounting per A10
connection in addition to a per-flow basis.
Flow Mapping
Flow mapping includes these basic areas:
Basic TFT processing
Forward Traffic Processing
Basic TFT processing
The MN may be assigned one IP address. This IP address is not associated with any particular A10 connection. The MN
may send Traffic Flow Templates (TFTs) for flow mapping to the PDSN carried over RSVP reservation messages. The
TFTs are used to map forward traffic to the main or auxiliary A10 connections and to indicate if a specific flow
treatment (such as header compression) should be applied for the matching packets. The TFTs are also used by PDSN to
associate packets from forward and reverse traffic to flows for flow-based accounting and QoS enforcement. Since the
MN may be assigned multiple IP addresses, each TFT corresponds to a specific IP address.
may send Traffic Flow Templates (TFTs) for flow mapping to the PDSN carried over RSVP reservation messages. The
TFTs are used to map forward traffic to the main or auxiliary A10 connections and to indicate if a specific flow
treatment (such as header compression) should be applied for the matching packets. The TFTs are also used by PDSN to
associate packets from forward and reverse traffic to flows for flow-based accounting and QoS enforcement. Since the
MN may be assigned multiple IP addresses, each TFT corresponds to a specific IP address.
The TFTs can contain:
Source and destination ports
Source and destination addresses
Protocol
Type of service (TOS in IPv4)
After the main and auxiliary A10 connections are created, the MN sends TFTs to the PDSN via a reservation message
(RSVP).
(RSVP).
Forward Traffic Processing
When a packet arrives at the PDSN from the external IP network, the packet is matched against the set of packet filters
stored at the PDSN. The packet is sent down the A10 connection that matches the flow id in the packet filter.
stored at the PDSN. The packet is sent down the A10 connection that matches the flow id in the packet filter.