HRPD Multi-flow QoS Architecture Overview and Issues Related to TSG-A QoS Architecture

1. HRPD Multi-flow QoS Architecture Overview and Issues Related to TSG-A QoS Architecture D. N. Knisely Lucent Technologies dnk@lucent.com 630-979-7344

2. Overview • Assumptions • Overview of HRPD Multi-flow QoS Architecture • Issues with TSG-A Multi-flow QoS Decisions • Recommendations

3. Assumptions • Ignoring Multi-Route Capabilities of C.S0063/TIA-1054

4. HRPD Multi-flow QoS • Specified in Two Documents: • C.S0024-A/TIA-856-A • Multi-flow Packet Application (MFPA) • C.S0063/TIA-1054 • Enhanced Multi-flow Packet Application (EMFPA) • Three Layers: • Reservations • Link Flows • MAC Flows (Reverse Link Only) • Issues for Forward and Reverse Links are Different

5. Reservations • Analogous to “Application Flow” or “IP Flow” • Identified by an 8-bit ReservationLabel • Associated Requested QoS and Granted QoS • Can be in One of Two States: • On (Open State in AI) • Granted QoS has been Made Available • “Meter is Running,” i.e., the Reservation has been “Active-Started” from a Billing Perspective • Off (Close State in AI) • Granted QoS is Not Currently Available • “Meter is Not Running” • Reservations Turned On/Off by Efficient OTA Signaling • Default Reservation (On by Default) is 0xFF • Assumed to be Best Effort, but this is Not Hard-Coded in the Air Interface • Associated with ExactlyOneLink Flows • (Actually, each FL/RL Link Flow as a Set of Associated FL/RL Reservations) • When Associated Link Flow is Disabled, Data May be Delivered over Link Flow Associated with Reservation 0xFF • Notes: • ReservationLabel is Not Transmitted Over the Air (i.e., Receiver can Only Distinguish Link Flows) • On/Off State is NOT Flow Control; Data May be Delivered via Data Over Signaling (DoS, Analogous to 3G1X SDB)

6. Link Flows • Link Layer Flows with Varying QoS Delivery Attributes • Identified by a Link Flow Identifier, which Is Transmitted Over the Air (i.e., Link Flows are Identifiable by the Receiver) • States: • Enabled: • Link Flow May Transport PDUs • AI Resources are Assigned • Disabled: • Link Flow May Not Transport Data • AI Resources Not Assigned • Link Flow May be Re-configured • OTA Delivery is the Same for All Reservations Associated with the Same Link Flow • Each Link Flow Contains One RLP Instance • RLP Attributes Independently Settable (e.g., ACK/NAK, Retransmissions, etc.) • Link Flow also has Associated EMFPA Protocol Stack Characteristics: • ROHC? • PPP/HDLC Present or Absent? • Each Link Flow is Associated with Exactly One MAC Flow (RL)

7. MAC Flows • Applies to Reverse Link Only • Each MAC Flow has its own “Fluid MAC” Parameters for Reverse Link Distributed MAC • Independent RL-MAC-Layer Delivery Properties • Large Number of Configurable Parameters • May Run Over Rev. 0 PHY (“Subtype 2”) or Rev. A PHY (“Subtype 3”)

8. HRPD Multi-flow QoS Architecture(Forward Flows)

9. FL Observations • Reservations are 1:1 with Application Flows/IP Flows • FL Reservation to Link Flow Bindings Change Dynamically • Potentially Based on Changing AI Conditions • Binding Changes Whenever Link Flow Reconfiguration Occurs • Unit of Activation (On/Off) is the Reservation • Reservation States are Logically Visible to AT and Applications • Reservation State is Visible to PDSN • Linked to Billing State (e.g., Active Start/Stop) • Reservations are the Sole “Flow” Intended by TSG-C to be Visible to IOS, Packet Data Network Architecture in Original TSG-C Design • Data Arriving at AT is Distinguishable Only per Link Flow • Link Flow States are Not Logically Visible to IOS or Packet Data Network Architecture • Data for a Reservation (Application Flow) Can be Carried for Different Link Flows in a Dynamically Changing Manner • E.g., Required to Reconfigure Link Flow Parameters • Entirely Under RAN Control • May often be Temporary “Plumbing”

10. HRPD Multi-flow QoS Architecture(Reverse Flows)

11. RL Observations • Reservations are 1:1 with Application Flows/IP Flows • Reservation States are Visible to AT and Applications • E.g., AT Must Request Transition to Open State before Desired QoS Capabilities are Available • Reservation State is Visible to PDSN • Linked to Billing State (e.g., Active Start/Stop) • RL Reservation to Link Flow Bindings Change Dynamically • Potentially Based on Changing AI Conditions • Binding Changes Whenever Link Flow Reconfiguration Occurs • Unit of Activation (On/Off) is the Reservation • Data Arriving at AN is Distinguishable Only per Link Flow • Link Flow States are Not Logically Visible to IOS or Packet Data Network Architecture • Data for a Reservation (Application Flow) Can be Carried for Different Link Flows in a Dynamically Changing Manner • E.g., Required to Reconfigure Link Flow Parameters • Entirely Under RAN Control • May often be Temporary “Plumbing”

12. Conclusions/Recommendations • “Unit of QoS” Visible to PDSN and AT/Application is the Reservation • Turned On/Off by OTA Signaling • Visible/Under Control of AT/Application • AN Controls: • Binding of Reservations to Link Flows • Opening/Closing of Reservations • Assignment of Resources to Enable Link Flows • Logical Architecture is to Let AN Control Binding of Reservations to A10 • Likely to Assign all RL Reservations Associated with One Link Flow to Same A10 • Likely to Assign FL Reservations to A10s Based on Commonality of QoS Transport Requirements and Ultimate QoS Requirements for Each Reservation • AN May have Insights into Transport Requirements (e.g., Based on Carrier’s Transport Network Capabilities) • TSG-A Decision to Associate A10s 1:1 with Link Flows is Inconsistent with TSG-C Air Interface Design Objectives • Intention was for Reservations to be Visible to IOS • Link Flows Change in Dynamic Manner; Link Flows Not Intended to be Visible to IOS • Undesirable to Re-plumb A10s in Highly Dynamic Manner when Reservation <-> Link Flow Plumbing Changes • If TSG-A Includes ReservationLabel in each GRE Packet, Multiple Reservations Can be Mapped (by AN) to One A10. • Alternatively, AN Can Bind One Reservation to One A10. • Either way is Consistent with Air Interface