MIPSHOP – November, 2005 Event Services and Command Services for Media Independent Handover Presentation prepared by: Srini Sreemanthula Presented by:

Slides:



Advertisements
Similar presentations
1 IEEE Media Independent Handoff Overview of services and scenarios for 3GPP2 Stefano M. Faccin Liaison officer to 3GPP2.
Advertisements

IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Network Controlled Network Selection and HO scenarios Date Submitted: September,
Doc.: Handoff_WNG_Presentation r3 Submission July David Johnston, IntelSlide Handoff Presentation to WNG David Johnston.
LTE-A Carrier Aggregation
xxx IEEE MEDIA INDEPENDENT HANDOVER DCN: LB1c-handover-issues.ppt Title: MIH Security – What is it? Date Submitted:
Network Initiated Handovers T. Melia, J. Korhonen, R. Aguiar, S. Sreemanthula, V. Gupta Based on draft-melia-mipshop-niho-ps-00.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
xx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: July,
1 Handover for PMIPv6 Using MIH KANG Joon-Suk 姜 俊錫.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH Protocol Security Date Submitted: December, 2007 Presented.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Issues with Date Submitted: July, 2009 Presented at IEEE Session.
I-D: draft-rahman-mipshop-mih-transport-01.txt Transport of Media Independent Handover Messages Over IP 67 th IETF Annual Meeting MIPSHOP Working Group.
Doc.: _IETF_DNA_r1 Submission March David Johnston, IntelSlide L2 Services for Handover Optimization David Johnston
68 th IETF, Prague Czech Republic Issues with L2 abstractions and how they affect QOS-based handovers Nada Golmie Advanced Networking Technologies Division.
DCN: March 7, 2005 IETF 62 - Minneapolis, MN Media Independent Handover Services and Interoperability Ajay Rajkumar Chair, IEEE
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIIS and Its Higher Layer Transport Requirements: Ad hoc Update and Discussion on.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: MIH_Handover primitives and scenarios Date Submitted: April, 30,
Doc.: 802_Handoff_WMAN_Presentation Submission July David Johnston, IntelSlide Handoff A Technical Preview David Johnston
xx-001 IEEE MEDIA INDEPENDENT HANDOVER Title: Potential Media Independent Services Date Submitted: Presented at IEEE 802 plenary Authors.
Doc.: 802_Handoff_Architecture_Elements_r2 Submission May David Johnston, IntelSlide 1 Architectural Elements of an 802 Handoff Solution David Johnston.
1 NetLMM Vidya Narayanan Jonne Soininen
Some use cases and requirements for handover Information Services Greg Daley MIPSHOP Session IETF 64.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Analysis on Identifiers Date Submitted: January 9, 2006 Presented.
21-07-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: Subscription ID Scope Date Submitted: June, 14 th, 2007 Presented.
Requirements For Handover Information Services MIPSHOP – IETF #65 Srinivas Sreemanthula (Ed.)
ABSTRACT: This contribution introduces the inter-RAT fast handover solution. TITLE: Inter-Radio Access Technology Fast Handover TSG-A WG4 RECOMMENDATION:
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
- IETF 64 - FMIPv6 over IEEE (draft-jang-mipshop-fh ’.txt) HeeJin Jang, Youn-Hee Han, Soohong Daniel Park SAMSUNG Junghoon Jee, Jaesun Cha.
IEEE MEDIA INDEPENDENT HANDOVER DCN: LB1a-handover-big-picture.ppt Title: LB 1a, Handover example flow with.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Media Independent Paging Date Submitted: :November 9, 2006 Presented.
Omniran IEEE 802 OmniRAN EC SG Results and Outlook Date: Authors: NameAffiliationPhone Max RiegelNSN
August 2, 2005 IETF 63 – Paris, France Media Independent Handover Services and Interoperability Ajay Rajkumar Chair, IEEE WG.
Design Considerations for the Common MIH Protocol Functions draft-hepworth-mipshop-mih-design-considerations-01 Ele Hepworth (*), Robert Hancock, Srinivas.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: September,
1 IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: EAP Pre-authentication Problem Statement in IETF HOKEY WG Date Submitted: September,
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Submission May 2016 H. H. LEESlide 1 IEEE Framework and Its Applicability to IMT-2020 Date: Authors:
Problem Statement: Media Independent Handover Signalling draft-hepworth-mipshop-mih-problem-statement-01 Ele Hepworth (*), Greg Daley, Srinivas Sreemanthula,
Trend of Mobility Management Yen-Wen Chen Ref: 1.Draft IEEE Standard for Local and Metropolitan Area Networks: Media Independent Handover Services 2.Transport.
Transport of Media Independent HO Messages over IP
IEEE 802 OmniRAN Study Group: SDN Use Case
IEEE MEDIA INDEPENDENT HANDOVER
Media Independent Handover Services and Interoperability
Media Independent Coexistence
Maryna Komarova (ENST)
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Group Management and Routing Issues in Heterogeneous Networks Date Submitted: January.
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN: bcst
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER
Mobility Support in Wireless LAN
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE P vs IEEE Date: Authors:
Media Independent Handover
Motivation L3 enable both scenarios under
Media Independent Coexistence
Media Independent Coexistence
Media Independent Coexistence
Media Independent Coexistence
IEEE MEDIA INDEPENDENT HANDOVER
Presentation transcript:

MIPSHOP – November, 2005 Event Services and Command Services for Media Independent Handover Presentation prepared by: Srini Sreemanthula Presented by: Greg Daley, with some additions MIPSHOP IETF 64

MIPSHOP – November, 2005 IEEE Introduction IEEE WG defines media independent handover (MIH) services that enable handoffs from one link technology to another involving subnet changes MIH services aid in handoff based on existing mobility management protocols MIH services are classified as 3 types MIH Information Services MIH Command Services MIH Event Services

MIPSHOP – November, 2005 What MIH provides MIH service carry L2 information that is processed locally or carried to some other network node, remotely MIH Services enable two facets of inter- technology handover Inter-technology Network selection Handover control

MIPSHOP – November, 2005 ES/CS Introduction Event Services (ES) provide: indications from one layer or functionality to another about changes in the connectivity state. Remote ES convey information from one network node to another Command Services (CS) provide: mechanisms for controlling handovers or functions aiding handovers. mechanisms to establish, redirect, or remove state in either the network or mobile node, so that handovers occur smoothly. Remote CS convey information from one network node to another

MIPSHOP – November, 2005 Motivations functional definitions are to enable two scenarios Terminal centric/controlled Network centric/controlled

MIPSHOP – November, 2005 Terminal Controlled Handover Terminal makes all the decisions of network selection and initiates HO control Can utilizes native L2 signaling or L2/L3 MIH ES/CS and L3 IS services Used in operator, enterprise or individual user scenarios

MIPSHOP – November, 2005 Network Controlled Handover Network makes decisions of network selection in coordination with the terminal and initiates HO control Assumption is that network selection is in core network (beyond L2) HO control resides where MME (common to both accesses) resides (beyond L2) This requires that L3 MIH IS, ES and CS services are available Important for operator models with multiple access technologies

MIPSHOP – November, 2005 Motivation Summary Higher layer MIH ES/CS services provide architectural flexibility for deployment does not need in certain link technologies ES/CS are utilized for both network selection and handover control Applicable to network entity common to both media types Not scalable to provision these functions within subnet Easier and faster adoption in other SDO e.g. 3GPP Can coexist or share functions with MIH ES/CS at L2

MIPSHOP – November, 2005 ES/CS Service Model Other Sources MIHF (ES) MIH (ES) Other Sources Remote ES Other triggers Link Layer Link Layer Other triggers Link Indications Link Indications Network Node Network Node Other layers/ functions MIHF (CS) MIH (CS) Remote CS Commands MME Link Layer Link Commands Network Node Network Node Event Service model Command Service Model

MIPSHOP – November, 2005 Usage Models Direct and Proxy models Direct model Proxy model MIHF UE MIHF MME Remote ES/CS MIHF UE MIHF proxu MIHF Remote ES/CS

MIPSHOP – November, 2005 NW Initiated NW Selection MAC Layers Beacon AN ANMIHF UE UE DL-Burst* Link-Detect AN Beacon MMEMIHF NW (IS) MIH-Register-Event.Resp() Link-Event.Detect(link_info) Network Operator Link-Event.Detect(link_info) MIH-Register-Event.Req() MIH-Info.Resp MIH-Info.Req Unfavorable Network Favorable Network => Selection UE Discovery and Registration MIH-Info.Resp MIH-Info.Req

MIPSHOP – November, 2005 NW Controlled HO MIHF UE Mobile IP UE Operator Network HA Network New-FA AN MIH-Remote-Link-Switch.Req( nwk) L2-Procedures (Security, Re-association, QoS Neg.) Link-Event-Up( nwk) MIH-Link-Event-Up FBU L3-switch.Ind MAC MIH-Remote-Link-Switch.Resp Release Mobile-IP Signaling MIH signaling over new link Legend MME Network Selection Link-Associate Proxy Rtr Solicitation Proxy Rtr Advertisement Mobile IP update procedure over new link

MIPSHOP – November, 2005 Remote ES/CS Feasibility Discussion relevant due to: Adoba, B., "Architectural Implications of Link Indications draft-iab-link-indications-03.txt", June Explicit signaling required Intertechnology handover may not result in IP subnet change Mitigation of security issues Trust issues Mapping of identifiers Done at the UE

MIPSHOP – November, 2005 Explicit Signalling Command and event signalling Implicit signalling possible when path changes or link-aware routing metrics from access network Explicit signaling required Intertechnology handover may not result in IP subnet change May inform devices of mobility management issues which aren’t apparent in the current access net Needs safeguards to ensure damping/robustness

MIPSHOP – November, 2005 Identifier Mappings May be possible to make identifier mappings Appl/ Trans/ Netw MIHF ES/CS Link- Layers Mapping of Local Identifiers MME Discovery Registration Authentication Security Association Media independent host ID Mobile NodeNetwork

MIPSHOP – November, 2005 ES/CS Higher Layer Requirements Work is similar to IS higher layer MIIS for Identifying usage scenarios Provisioning models e.g. proxy and direct Finalizing ES/CS MIH functionality Message sequences, message types, data elements associated with each message Other higher layer requirement categories Transport Layer Discovery Registration and Deregistration Capability negotiation Security Reliability and failure recovery