1 / 6

Requirements for NETLMM Protocol: 802.16e Mobile BWA* Perspective

Requirements for NETLMM Protocol: 802.16e Mobile BWA* Perspective. Prakash Iyer Perviz Yegani 63 rd IETF, Paris NETLMM BOF. BWA – Broadband Wireless Access. WiMAX/802.16e Mobile BWA.

eljah
Download Presentation

Requirements for NETLMM Protocol: 802.16e Mobile BWA* Perspective

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements for NETLMMProtocol: 802.16e Mobile BWA* Perspective Prakash Iyer Perviz Yegani 63rd IETF, Paris NETLMM BOF BWA – Broadband Wireless Access

  2. WiMAX/802.16e Mobile BWA • Mobile WiMAX (based on 802.16-2004 amended by 802.16e) is an emerging standard for broadband, wide-area wireless access • Optimized for IP services • Usage will be characterized by • High average/peak data rates to subscriber terminals compared to traditional 3G networks • Mix of audio, video, data and voice applications • Symmetric and asymmetric UL and DL traffic, real-time and non-real-time • Mobility rates exceeding 200 km/hr while satisfying ITU-T and other benchmarks for low handover packet loss, latency, jitter and delay • Need to support low power modes

  3. Mobile WiMAX – E2E Architecture Perspective BS All-IP Access Service Network (ASN) Applications Service Network • Mobility Management Requirements: • Need two-level MM hierarchy • ‘Make-Before-Break’ HO within and across ASN – could eliminate need for complex over-the-air MM primitives • Client to remote CSN HO could be delayed and seamless over ASN anchored paths • Must support notion of separate Network Access (ASN) Provider – NAP and Network Service (CSN) Provider - NSP i.e. different security domains • Seamless integration between localized and E2E MM protocols IP Connectivity Service Network (CSN) BS BS All-IP Access Service Network (ASN) INTERNET BS

  4. Mobile WiMAX – ASN Variants BS To CSN BS + Router To CSN IP Cloud IP Cloud • Mobility Management Requirements: • Must accommodate Flat and Hierarchical ASN topologies – and variants thereof • Must support multi-hop relay among BSs • Must support multi-path configurations among BSs • Eliminate need for signaling from client to ASN for intra/inter ASN MM • Ideal scenario is network-based MM both within/across ASN and end-to-end • Must work irrespective of client connectivity state – Active, Idle • Client IP reachability in all power states with configurable location anonymity • IPv4 and IPv6 • Eliminate / reduce need to simulcast within ASN for duration of HO – prevent backhaul BW wastage especially for wireless backhaul Anchor Router / Gateway BS + Router BS ASN

  5. Multi-Access Support BS WiMAX ASN Applications Service Network • Mobility Management Requirements: • Seamless client-transparent inter-technology ASN HOs and anchoring across ASNs BS IP Connectivity Service Network (CSN) BS Beyond 3G Evolved ASN INTERNET BS

  6. Summary • Traditional E2E IP MM protocols (e.g. MIP) are not adequate for needs of MBWA and Next-Gen multi-access wide-area networks • Need for a localized MM protocol • Optimized for handover performance of different application classes, client power-management states and IP reachability • Support • Unbundled provider domains • ASN topology variants • Heterogeneous access networks integrated via common IP core

More Related