2005.02.14 HRPD Multi-flow QoS Archite cture 1 HRPD Multi-flow QoS Architecture Overview and Issues Related to TSG-A QoS Architecture D. N. Knisely Lucent Technologies [email protected]630-979-7344 Notice The contributor grants a free, irrevocable license to 3GPP2 and its Organization 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 portions of the contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. The contributor 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 contribution. This document has been prepared by the contributor 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 the contributor. The contributor specifically reserves 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 contributor other than provided in the copyright statement above.
Transcript
2005.02.14 HRPD Multi-flow QoS Architecture
1
HRPD Multi-flow QoS Architecture Overview and Issues Related to TSG-A QoS Architecture
NoticeThe contributor grants a free, irrevocable license to 3GPP2 and its Organization 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 portions of the contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. The contributor 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 contribution.This document has been prepared by the contributor 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 the contributor. The contributor specifically reserves 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 contributor other than provided in the copyright statement above.
2005.02.14 HRPD Multi-flow QoS Architecture
2
Overview
• Assumptions
• Overview of HRPD Multi-flow QoS Architecture
• Issues with TSG-A Multi-flow QoS Decisions
• Recommendations
2005.02.14 HRPD Multi-flow QoS Architecture
3
Assumptions
• Ignoring Multi-Route Capabilities of C.S0063/TIA-1054
2005.02.14 HRPD Multi-flow QoS Architecture
4
HRPD Multi-flow QoS
• Specified in Two Documents:– C.S0024-A/TIA-856-A
• Three Layers:– Reservations– Link Flows– MAC Flows (Reverse Link Only)
• Issues for Forward and Reverse Links are Different
2005.02.14 HRPD Multi-flow QoS Architecture
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 Exactly One Link 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)
2005.02.14 HRPD Multi-flow QoS Architecture
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)
2005.02.14 HRPD Multi-flow QoS Architecture
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”)
2005.02.14 HRPD Multi-flow QoS Architecture
8
HRPD Multi-flow QoS
Architecture(Forward Flows)
AT
RAN
Link Flow 0x00
Activated
Link Flow 0xaa
Activated
Link Flow 0xbb
Activated(Not in Use)
Link Flow0xcc
De-activated
PDSN
Reservation 0xFF
ON
Reservation 0xss
ON
Reservation 0xtt
ON
Reservation 0xvv
OFF
Reservation 0xuu
OFF
Reservation 0xww
ON
Temporary Plumbing (e.g.,
because Link Flow is De-activated
or is being reconfigured)
Plumbing to map Reservations to Link Flows and parameters to configure Link Flows modified dynamically by OTA Signaling.Set up by AN.
RLP00
RLPaa
RLPbb
RLPcc
Desired
Plumbing
What to dowith this flow?
?
Desired Plumbing(via A10 dedicated to this service)
A10sTemporary Plumbing
(if A10 is 1:1with Link Flow)
Packet Filter
Medium amount of signaling; may change based on AI conditions.
Note that Link Flows must be de-activated to be re-configured.
Light-weight signaling; changes
frequently.
A100 A101 A102 A103
Enhanced FL MAC/PHY
Link Flow 0x00
Activated
Link Flow 0xaa
Activated
Link Flow 0xbb
Activated(Not in Use)
Link Flow0xcc
De-activated
Reservation 0xFF
ON
Reservation 0xss
ON
Reservation 0xtt
ON
Reservation 0xvv
OFF
Reservation 0xuu
OFF
Reservation 0xww
ON
Temporary Plumbing (e.g.,because Link Flow is De-activatedor is being reconfigured)
RLP00
RLPaa
RLPbb
RLPcc
DesiredPlumbing
Enhanced FL MAC/PHY
Application(s)
Reservations are turned ON/OFF dynamically by OTA Signaling.
Transition may be triggered by AT (typical) or AN.
Reservations within a RL Link Flow are Indistinguishable
for Delibery Purposes
2005.02.14 HRPD Multi-flow QoS Architecture
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”
2005.02.14 HRPD Multi-flow QoS Architecture
10
HRPD Multi-flow QoS
Architecture(Reverse
Flows)
RAN
PDSN
MAC Flow 0x00
ConfiguredIn Use
MAC Flow 0xnn
ConfiguredNot In Use
MAC Flow 0xmm
ConfiguredNot In Use
PHY
Reservations are turned ON/OFF dynamically by OTA Signaling.
Transition may be triggered by AT (typical) or AN.
Plumbing to map Reservations to Link Flows and parameters to configure Link Flows modified dynamically by OTA Signaling.Set up by AN.
Plumbing to map Link Flows to MAC
Flows and parameters to configure MAC Flows modified dynamically by OTA Signaling.Set up by AN.
What to dowith this flow?
Desired Plumbing(via A10 dedicated to this service)
A10s
Temporary Plumbing(if A10 is 1:1
with Link Flow)
A100 A101 A102 A103
AT
Link Flow 0x00
Activated
Link Flow 0xaa
Activated
Link Flow 0xbb
Activated(Not in Use)
Link Flow0xcc
De-activated
MAC Flow 0x00
ConfiguredIn Use
MAC Flow 0xnn
ConfiguredNot In Use
MAC Flow 0xmm
ConfiguredNot In Use
PHY
Reservation 0xFF
ON
Reservation 0xss
ON
Reservation 0xtt
ON
Reservation 0xvv
OFF
Reservation 0xuu
OFF
Reservation 0xww
ON
Temporary Plumbing (e.g.,because Link Flow is De-activatedor is being reconfigured)
RLP00
RLPaa
RLPbb
RLPcc
DesiredPlumbing
Relatively large amount of signaling; changes less frequently (possibly only at SCP.
Note that MAC flows must not be in use when being reconfigured.
Medium amount of signaling; may change based on AI conditions.
Note that Link Flows must be de-activated to be re-configured.
Light-weight signaling; changes
frequently.
Application(s)
Link Flow 0x00
Activated
Link Flow 0xaa
Activated
Link Flow 0xbb
Activated(Not in Use)
Link Flow0xcc
De-activated
RLP00
RLPaa
RLPbb
RLPcc
Reservations within a RL Link Flow are Indistinguishable
2005.02.14 HRPD Multi-flow QoS Architecture
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”
2005.02.14 HRPD Multi-flow QoS Architecture
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
