1. Benefits of HC @ eBS for UMB Qualcomm Inc. January 08, 2007 Notice Contributors grant 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. Contributors are 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 contributors 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 contributors. Contributors 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 contributors other than provided in the copyright statement above.

2. Background X31-20061204-016R1 (LU_NT_QCOM) provides general reasons for locating HC (Header Compression and UDC (User Data Ciphering) in the eBS The group agreed to have UDC in the edge node in 3GPP2 December Meeting This slide provide further clarifications on benefits to have HC in the eBS

3. UMB Design UMB supports multiple routes which facilitates: –Individual eBSes maintain their own air link with the AT –The eBSes do not need to communicate with each other to synchronize connection state. –Each eBS has an independent instance of Header Compression individually established with the AT, hence no HC state needs to be exchanged between the eBSes UMB air interface is designed to perform well when the ROHC is in the eBS

4. Benefits of HC @ the eBS By placing HC at the eBS –Significantly simplify the interface between the eBS and the AAG as well as interface between eBSes. –Make AAG to be truly access agnostic since link layer is fully terminated at the eBS –Eliminates the needs: To establish one tunnel per over the air QoS flow To communicate individual over the air QoS reservation information between the eBS and AAG To Perform flow control on individual tunnels between AAG and eBS To perform HC parameter negotiations between eBS (on behalf of AT) and AAG

5. Myths for HC @ the AAG (1) Myth 1: Header compression benefit is extended to the backhaul –Rebuttal The packets on the backhaul are tunneled with GRE which cancels HC savings HC @ the AAG only allows compression of inner IP header If backhaul requires header compression, it is better to run a separate HC between the eBS and the AAG which can compress both outer and inner IP headers (See following slides figures)

6. VoIP Backhaul Analysis Voice Activity Factor –50% Voice Payload: –8Kb/s

7. TCP Backhaul Analysis

8. Myths for HC @ the AAG (2) Myth 2: It is more efficient to consolidate HC processing at the AG –Rebuttal The additional processing required at the eBS to header compress IP packets is incrementally very minimal. eBS can potentially perform HC in software while AAG will probably need HW acceleration to handle all the user's HC needs.

9. Myths for HC @ the AAG (3) Myth 3: Header compression can be reused across different technologies if placed at AAG –Rebuttal HC can not be shared by the different technologies since the different HC parameters will be used for different technologies It makes AG to be access dependent and complex because AG has to support 3GPP2 specific A11/A10 interface, 3GPP GTP, and WiMaX R6 interface. Even within 3GPP, HC is located in the different places for different technologies. –In UMTS, HC is not in Gateway (it is in RNC). –For HSPA evolution, 3GPP has decided to allow HC at eNodeB. –For 3GPP SAE, whether to put UPE (including HC) in the 3GPP Anchor or ENodeB is still in debate.