1. 0 Title:Evolution Architecture Functional Proposal Abstract: This contribution proposes a new RAN Architecture. Source: Brent Hirschman, Sprint Nextel – brent.hirschman@sprint.com Jingyi Zhou, Verizon Wireless – jingyi.zhou@verizonwireless.comjingyi.zhou@verizonwireless.com Kuntal Chowdhury, Starent - kchowdhury@starentnetworks.comkchowdhury@starentnetworks.com Sebastian Thalany, US Cellular - Sebastian.Thalanany@uscellular.comSebastian.Thalanany@uscellular.com Avi Lior, Bridgewater - avi@bridgewatersystems.comavi@bridgewatersystems.com Bjorn Hjelm, ALLTEL - Bjorn.Hjelm@alltel.comBjorn.Hjelm@alltel.com Anda Farcasanu, Motorola - afarcas1@motorola.comafarcas1@motorola.com Takatsugu Kito, KDDI - ta-kito@kddi.comta-kito@kddi.com Vojislav Vucetic, Cisco - vvucetic@cisco.comvvucetic@cisco.com Gabor Bajko, Nokia - Gabor.Bajko@nokia.comGabor.Bajko@nokia.com Brian Smith, Bell Mobility - b.smith@bell.cab.smith@bell.ca Date:January 8, 2007 Recommendation: Review and adopt proposal for RAN Architecture. Notice These companies 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. These companies 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. These companies 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. 1 Objectives of Evolved Architecture –Realize improvements in basic system performance Provide higher data rates Reduce communication delay Improve communication quality – end to end QoS Reduce connection set-up time Provide separation of control signaling and transport paths from RAN to Core Provide increased security and privacy for users and network –Support of a variety of access technologies Seamless mobility across technologies Maintain access control across technologies – authentication, authorization, privacy, charging Service continuity across technologies – access to same service (e.g., IMS) –Improve Operations and Maintenance Capabilities Reduce complexity Simplify Network Architecture Encourage “Mix and Match” capabilities for RAN and IP vendors – preserve standardized open interfaces

3. 2 Current User Plane Protocol Stack ATM IP GRE PHY ATM PHY ATM IP/MIP PHY ATM TCP UDP IP ATM PHY IP/MIP PPP TCP UDP IP/MIP Sublayers of HRPD PPP RLP PHYT1 HDLC IP TCP/UDP RMI PHY ATM PHY Ethernet IP TCP/UDP RMI RLP IP GRE PHYT1 HDLC IP Ethernet PHY IP BackhaulR-P (A10/A11) IP over ATM ATBTSAggregation Router RNCPDSN/FAHAApplication Server IP over ATM EthernetT1 Evolution needs to consider the following operators’ goals: Separation of access and IP networks Simplification of RAN/PDS Interface Minimize number of elements in bearer path and support low latency bearers Standards based Interfaces in the RAN and at RAN/PDS interfaces Leverage IP technology for backhaul and core networks RAN Security considerations for privacy, confidentiality, Man-in-the-middle (MITM) and Distributed Denial of Service (DDoS) attacks Support for both Home and Visited Network Control for IMS and other services Sub- layers of HRPD

4. 3 Proposed New User Plane Protocol Stack AT – Access TerminaleBS – Evolved Base StationAG – Access Gateway L2 IP GRE PHY L2 PHY L2 IP/MIP PHY L2 TCP UDP IP L2 PHY IP/MIP ROHC/Sec TCP UDP IP/MIP MAC ROHC/Sec RLP PHY MAC PHY L2 IP GRE PHY RLP PHY AGCore ATeBS Evolved RAN Architecture has the following features: Centralized Layer 2 functions like paging, location management, and idle state management Complete link layer stack in the NG-BTS to allow for cross-layer optimization in airlink protocol Evolved PDS Architecture has the following features ROHC and Ciphering (considered between link layer and IP layer) terminate in the PDS PPP Free Operation EAP Authentication mechanisms Mechanisms to set up Low latency bearers for real-time services

5. 4 Access Gateway Functionality AG – Access Gateway. This function is the Layer 3 terminating point for all bearer and signaling traffic entering the Core IP Network. It also supports the following functions: AAA client NAS (Network Access Server) device IDS (Intrusion Detection System) access point Hot-lining device Prepaid client Network Mobility Agent (NMA) – CMIP (Foreign Agent (FA) for MIPv4) and PMIP Client QoS enforcement point Policy enforcement point NFCC (Network Firewall Configuration and Control) packet filter IAP (Intercept Access Point) (lawful Intercept) ROHC (Robust Header Compression) - (Optional in case of UMB) Ciphering - General placement (placed in BS for UMB)

6. 5 Lower Layer Termination Functionality - Specific to an Access Technology There are two main aspects to this functional area: Signaling RNC (S-RNC)– Mobility management (similar to the signaling management in current RNCs) above the radio layer (RLP) between Base stations. These functions include: –Paging and location– In a pure IP mobile network a paging controller function to locate mobiles when idle will be needed. –Idle Mode Termination – Some State information about the MS needs to be maintained by the network while the MS is in idle mode. Bearer - Mobility management of the bearer flows to the Access Gateway. Tunnel establishment and tear-down between Base Stations and Access Gateway. Independence of the Signaling and Bearer functions is important. Separate standardized interfaces for Signaling and Bearer functional components are needed. Implementation scenarios are subject to operator’s preference.

7. 6 Base Station Functionality Radio Link Accounting data source (provided to Access Gateway) Radio Link Protocol Function Radio Link QoS and Policy enforcement Device Authentication Relay Layer 2 Handoff between BS Header Compression (optional in case of UMB) Ciphering (in case of UMB)

8. 7 Functional Entities - AG - S-RNC - BS Layer 3 Common Functions FA/NMA NAS device AAA Client QoS EP Lawful Intercept IAP Policy EP NFCC Packet Filter Prepaid Client Hot-lining device IDS/IPS Access Point ROHC (optional UMB) Ciphering (General) Lower Layer Termination Point Support for Bearer Management AG IP Core Network Various Access Network Technologies AAAPolicy and QoS IP Signaling and transport (e.g., SIP) Other AGs, Legacy NEs (e.g., PDSNs, SGSN/GGSN) And new NEs (e.g., ASN-GW, PDIF) Signaling Management (S-RNC) Paging and Location Idle Mode Termination Std Interface Std Interface Std Interface Base Station RLP Radio Link Usage records Radio Link QoS/Policy Layer 2 HO among BS Device Auth. Relay RoHC (optional UMB) Ciphering (UMB)

9. 8 Common Functions FA/NMA QoS EP NFCC Pkt Filter AAA Client Policy EP Prepaid Client Lawful Intercept IAP NAS Dev. Hot-lining device IDS/IPSROHCCiphering LLT (PPP/PFO) Current Access LLT PFO Proposed Access LLT (IP-Sec) Non-trusted Access RNC BTSeBSAP IP Core Network AAA HA A10/ A11 Access Gateway – Supporting Current and Proposed Evolved Architecture PDSN P-P PCRF Signaling Bearer IP Gateway G-G EV-DO Rev.A EV-DO Rev.C WLAN S-RNC