Руководство По Устранению Ошибки для Cisco Cisco Packet Data Gateway (PDG)
Policy-Based Management and EV-DO Rev A
EV-DO Rev A Call Setup ▀
Cisco ASR 5000 Series Enhanced Feature Configuration Guide ▄
OL-22982-01
Table 32. EV-DO Rev A Call Setup Description
Step
Description
1
Main service connection is setup. Here, the PDSN receives an A11 RRQ indicating that this is a request to setup the main
service connection for a Rev A call. For main A10s, the A11 RRQ always includes an SR_ID of 1, a forward traffic flow
ID of 255, and a reverse traffic flow ID of 255.
service connection for a Rev A call. For main A10s, the A11 RRQ always includes an SR_ID of 1, a forward traffic flow
ID of 255, and a reverse traffic flow ID of 255.
2
The PDSN sends an Access Request message to the AAA to authenticate the subscriber and to retrieve the subscriber‘s
QoS profile. (If no authentication is required, the PDSN uses the QoS profile from the default subscriber template.)
QoS profile. (If no authentication is required, the PDSN uses the QoS profile from the default subscriber template.)
3
The AAA sends the subscriber‘s profile that includes the QoS profile to the PDSN.
4
The PDSN stores the QoS attributes from the subscribers profile and sends a copy to the RAN via A11 Session Update
message The RAN also stores the QoS attributes.
message The RAN also stores the QoS attributes.
5
The AT sends an IP flow reservation message to the RAN that includes the requested levels of QoS for each data flow.
6
The RAN determines if the subscriber is authorized using the QoS attributes it stored from step 4. If the subscriber is
authorized, the RAN sends a QoS Granted message to the AT. Otherwise, the RAN denies the QoS requested by the RAN.
authorized, the RAN sends a QoS Granted message to the AT. Otherwise, the RAN denies the QoS requested by the RAN.
7
The AT sends the RAN an Acknowledgment.
8
The RAN sends an A11 RRQ to the PDSN that includes SR_IDs for the auxiliary A10 connections and the QoS granted the
MS.
MS.
9
The PDSN verifies the QoS parameters granted to the MS using the attributes it stores in step 4 and returns an A11 RRP.
10
The AT sends the TFTs—which identify the different flows in both the forward and reverse directions—to the PDSN via
modified RSVP Reservation message. (RSVP formats the TFTs for the PDSN.)
modified RSVP Reservation message. (RSVP formats the TFTs for the PDSN.)
11
The PDSN sends Reservation Confirm message to the AT and uses the packet filters within the TFTs to map flows to the
auxiliary A10 connections.
The PDSN also stores the TFTs for flow look up when mapping flows in the reverse direction and for flow-based
accounting.
During intra-PDSN handoff, PDSN will send the subscriber QoS Profile that it received in the Access-Accept during
authentication to the new PCF. This includes the list of authorized profile IDs in addition to other QoS attributes, but this
does not contain the requested/granted profile IDs. The PDSN may send the profile in the A11 RRP or generates an RP
Session Update message and sends it to the PCF.
The system assumes that the AT uses the same NAI, even if it initiates multiple simultaneous sessions.
auxiliary A10 connections.
The PDSN also stores the TFTs for flow look up when mapping flows in the reverse direction and for flow-based
accounting.
During intra-PDSN handoff, PDSN will send the subscriber QoS Profile that it received in the Access-Accept during
authentication to the new PCF. This includes the list of authorized profile IDs in addition to other QoS attributes, but this
does not contain the requested/granted profile IDs. The PDSN may send the profile in the A11 RRP or generates an RP
Session Update message and sends it to the PCF.
The system assumes that the AT uses the same NAI, even if it initiates multiple simultaneous sessions.
Call Flow for Updating QoS for Dynamic Flows
The PDSN and the PCF can perform QoS update procedures to modify the QoS that is granted for an IP flow. The QoS
update procedure is applicable to dynamic flows only.
update procedure is applicable to dynamic flows only.
You can configure the system to ensure that the granted QoS is downgraded to best effort (i.e. class x to best effort but
not class x to class x-1). The reservation for the downgraded flow is removed at the RNC and PCF and the user detail
record for the flow is closed at the PDSN.
not class x to class x-1). The reservation for the downgraded flow is removed at the RNC and PCF and the user detail
record for the flow is closed at the PDSN.
In a downgrade scenario, the PDSN downgrades the profile ID for a flow from the Profile ID that was originally granted
by the RAN. The profile ID is downgraded to a lower precedence profile ID or to best effort.
by the RAN. The profile ID is downgraded to a lower precedence profile ID or to best effort.