1. 20061204x31-20061204-XXX Sprint_AG_proposal 0 Title:Evolution Architecture Functional Proposal Abstract: This contribution proposes a new architectural network element called an Access Gateway (AG). Source: Lew Milton, Motorola – lewis.milton@motorola.comlewis.milton@motorola.com Date:December 4, 2006 Recommendation:Review and adopt proposal for AG. Notice Motorola, Inc. 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. Motorola, Inc. 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. Motorola, Inc. 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.

2. 20061204x31-20061204-XXX Sprint_AG_proposal 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 OPEX Reduce CAPEX Simplify Network Architecture Encourage “Mix and Match” capabilities for RAN and IP vendors – preserve standardized open interfaces

3. 20061204x31-20061204-XXX Sprint_AG_proposal 2 Current Reference Architecture Open Interface Interface Not Implemented Interface Undefined

4. 20061204x31-20061204-XXX Sprint_AG_proposal 3 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

5. 20061204x31-20061204-XXX Sprint_AG_proposal 4 Proposed New User Plane Protocol Stack AT – Access TerminalNG BTS – Next Gen Base Terminal 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 ATNG-BTS 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 air link 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

6. 20061204x31-20061204-XXX Sprint_AG_proposal 5 Sprint Proposed Edge Functional Element - Access Gateway 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 Foreign Agent (FA) for MIPv4 –Separation of this function within the core network is FFS Network Mobility Agent for localized network mobility (NMA) –Separation of this function within the core network is FFS QoS enforcement point Policy enforcement point NFCC (Network Firewall Configuration and Control) packet filter IAP (Intercept Access Point) (lawful Intercept) ROHC (Robust Header Compression)

7. 20061204x31-20061204-XXX Sprint_AG_proposal 6 Lower Layer Termination Functionalities - Specific to an Access Technology There are two main aspects to this functional area: Signaling – Mobility management (similar to the signaling management in current RNCs) above the radio layer (RLP) between Base stations served by the same Access Gateway. 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.

8. 20061204x31-20061204-XXX Sprint_AG_proposal 7 Access Gateway 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 Ciphering 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

9. 20061204x31-20061204-XXX Sprint_AG_proposal 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 BTSBSAP IP Core Network AAA HA/BM A10/ A11 Access Gateway – Supporting Current and Proposed Evolved Architecture PDSN P-P PCRF Signaling Bearer Access Gateway P-P’ EV-DO Rev.A EV-DO Rev.C WLAN S-RNC

10. 20061204x31-20061204-XXX Sprint_AG_proposal 9 Handoffs within and across Access Gateways LLT (PPP/PFO) Current Access S-RNC Proposed Access RNC BTSBSAP A10/ A11 Signaling P-P’ LLT (IP-Sec) Non-trusted Access Bearer Mgmt BS Bearer BS Layer 3 Proposed Access Bearer Mgmt Handoff DO-Rev.A – DO-Rev.C Handoff DO-Rev.C – DO-Rev.C In the same AG Handoff DO-Rev.C – WLAN Handoff DO-Rev.C – DO-Rev.C In different AG AG S-RNC