2. MWIF Architecture Status Jan 25 2001 Paul Reynolds TC Chair

3. Page 2 Steps to Achieve the MWIF Vision 5. Launch strategy advisory board 4. Create strategy to lead toward harmonization w/3GPP and 3GPP2 3. Prioritize technical activities in order to most efficiently affect 3GPP,3GPP2, IETF and potentially others 2. Significantly improve linkages w/3GPP, 3GPP2 and IETF 1. Produce business case for MWIF vision Mission To drive acceptance and adoption of a single mobile wireless and internet architecture that is independent of the access technology. Accelerated Time to Market Significant Cost Reduction New Business Development Opportunities Faster Service Application Development Alignment of Data Services/Internet Leveraging of wireline investments BOLD STEPS Supportive Trends Challenges Vision

4. Page 3 MWIF Technical Plan (2001) Sydney (January) [Completed] –Working Draft NRA V2 –RAN Architecture Final Draft –ISP/Operator Requirements V2 Seoul (April) –RAN Architecture Complete –Final vision Combined RAN / Core NRA V3 Kansas City (July) –Interoperability demonstration ready –3GPP2 work complete –Final draft NRA V4 Europe (October) –Final version RAN V2 –Version NRA V5 –Spectacular demonstration (Orange Labs)

5. Page 4 Achievements of January Meeting üReviewed Outstanding issues in Network Reference Architecture v1 –Closed 12 Issues (CSM, Policy Server, OAM&P, Access Network, Resource Management). –Remaining issues will be resolved by feedback from task forces (Security, QoS, OAM&P) –IPv4/v6, Legacy Interworking deferred to post version 2 of NRA. üUpdated message sequence charts for NRA v2 –Mobile Originated SIP (existing flow updated and text added) –PSTN to Mobile (existing flow updated and text added) –Modification of QoS Resources mid-session –Emergency call

6. Page 5 Achievements of January Meeting üDefined a model for support of Emergency Call (including message sequence charts). need for access network to allow the message through to the Access Transport Gateway without authentication üApplications Working Group Started ü. Reviewed proposal for Service Agent in Application architecture. üSee separate slide

7. Page 6 üConsensus on IP in the RAN contents. üMPLS simulation. üConsensus on functionality of Access Gateway. üReviewed comments on Foreign Agent and NRA. üInitial discussions about protocol solutions for addressing/micromobility, QoS, and security. Achievements of January Meeting

8. Page 7 MWIF - 3GPP2 Contributions 3GPP2 San Diego TSG-A Meeting (Jan. 15-19). –MTR006 submitted as a contribution from individual companies. –Requirements for OpenRAN submitted as MWIF contribution. Achievements of January Meeting

9. Page 8 OAM&P Task Force Summary White Paper Presented (OAMP_White_Paper.doc) Proposal for workplan: -Utilize ongoing work in the industry -Identify relevant IETF protocols -Take a lead in identifying gaps in IETF protocols -Contribute MWIF’s OAM&P proposal to TMF Task Force anticipated to complete work by Oct. 2001

10. Page 9 Security Task Force Summary Scope of task force: –Core network (NRA v2), RAN (IP-RAN v1/Open RAN v1) Charter is to perform a top down security analysis of the overall architecture based on: –Security Requirements from WG-1 –Typically network security policies for End users Infrastructure 3 rd Parties Goal is to complete the work of this task force by July 2001

11. Page 10 Applications Task Force Summary Charter Validate MWIF Architecture to meet a minimum set of application and services requirements. This will be achieved by utilizing the applications layer as a guide to what is necessary to fulfill the promise of 3G Mobile Services Evaluate relative cost and complexity of an MWIF architecture solution. This supports the goal of efficient and inexpensive deployment of 3G wireless services by maintaining a focus on System and Application Level issues such as Performance, Scalability, Monitoring, Serviceability, Security and Manageability. Gain understanding of architecture advantages or issues: better, faster, cheaper, more reliable, more modular… etc. Proof of Concept: determine if the architecture is implementable by encouraging members to perform simulations, demonstrations, build testbeds,..etc.

12. Page 11 QoS Task Force Summary üQoS Task Force formed üEnd to end üRadio üDevelop detailed design (including protocols) for end to end QoS including radio.