802 21-IEEE-Tutorial.ppt

**IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-06-0706-00-0000Title: IEEE P802.21 TutorialDate Submitted: July 17, 2006Presented at IEEE 802.21 session #15 in San Diego, CAAuthors or Source(s):Vivek GuptaAbstract: IEEE P802.21 is the 802 standard for handover services. This tutorial helps communicate the architecture and definition of these services.

**IEEE 802.21 presentation release statementsThis document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21.The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html>

IEEE 802.21 Overview of Standard forMedia Independent Handover ServicesVivek GuptaMichael G WilliamsDJ JohnstonStephen McCann Phil BarberYoshihiro OhbaIEEE 802 Plenary, San Diego Tuesday, July 18 2006, 7:30 PM

**Key ContributorsRonny Kim (802.11 and 802.16 Amendments)

Dave Stephenson

**AgendaHistory and Need for Handovers802.21 Standard OverviewMedia Specific Enhancements802.11 802.16IETF3GPPUse Case

**How it all started.Handover Tutorial: Nov 2002IEEE 802 Tutorial: "Handoff Mechanisms and their Role in IEEE 802 Wireless Standards 11 November 2002, 6:30-9:30 pm Organized by Roger Marks and Brian Kiernan Co-sponsored by 802.16, 802.11, 802.15 Attendance: approximately 250 Abstract and Speaker Details http://ieee802.org/16/tutorial/T80216-02_03.pdf Presentation Materials http://ieee802.org/16/tutorial/T80216-02_04.zip Speakers Steve Dick, InterDigital Communications Avi Freedman, Hexagon System Engineering Joe Kwak, InterDigital Communications (T1P1 Representative) Bob O'Hara, Black Storm Networks (Editor, P802.11F Inter-Access Point Protocol) Richard Paine, Boeing (Chair, 802.11 Radio Resource Measurement Study Group) Charles Perkins, Nokia (Editor of numerous IEEE IP Mobility documents) TK Tan, Philips Semiconductors (Chair, Wireless LAN Interworking Group [802/ETSI/ARIB]) http://www.ieee802.org/16/arc/802-handoff/msg00001.html

**How it all startedRogers Email: Feb 2003From: Roger B. Marks [mailto:[email protected]] Sent: Wednesday, February 12, 2003 03:29 PM To: [email protected]: stds-802-handoff: Call for Interest on "IEEE 802 Handoff Mechanism" for March Dear 802 Handoff Reflector:The 802 Handoff Call for Interest has been scheduled for 6-7:30 pm on Tuesday March 11.Based on discussions I have had, I believe that there is interest in this topic. However, the reflector has been quiet, and no one has volunteered any input or commented on my proposed agenda (see below).So, please let me know (preferably via the reflector):*Do you think that 802 ought to be thinking about a common handoff approach? *Is it time to start a Study Group? *Would you attend the Call for Interest? *Would you want to be a presenter at the Call for Interest? *If so, what would you say?Roger

**Problems.Incorrect Network SelectionAbility of a device to choose its connection was hopeless. You could often connect at L2, but not at the network layer. The PC would often connect to the wrong one of many available APs, based on signal strength criteria alone.Increasing number of interfaces on devices Problem could extend to cover multiple interfaces.Various fast handover mechanisms in IETF MIPv4, FMIPv6IETF anticipated L2 constructs in standardized form Triggers, events, hints etc, but 802 was not providing them in a standard form or a media independent form

**Initial Thinking..Develop common standard across 802 mediaDefine L2 Triggers to make FMIP work wellDefine media independent information to enable my laptop to detect and select networks effectivelyDefine a way to transport this information and these triggers over all 802 mediaCFI with some initial slides : http://www.ieee802.org/21/archived_docs/Documents/802_Handoff_CFIr1.pdf

**The Use CaseMy DeskUndocked & walking aroundHeaded out of the building802.3802.11802.16Internet

**The ECSG ExperiencePeople wanted cellular inter-working also802.11 and 802.16 were ready and willing to develop text to work with 802.21Wired+wireless was desiredSecurity is hard. Steer clear of it for now.

**802.21 PrehistoryMarch 2003CFI.802 Handover ECSG Formed by SECPAR & 5CSubmissionInitial WG MeetingEC PAR ApprovalMay 2003Jan 2003802 Handover TutorialJuly 2003Sept 2003Nov 2003Jan 2004CFI : http://www.ieee802.org/21/archived_docs/Documents/802_Handoff_CFIr1.pdfpiippiiFirst Meeting of ECSGMar 2004pECSG Docs :http://www.ieee802.org/21/archived_docs/

**Semi-Official LogoThanks to Eric Jacobson

**Multi-Radio Networking EvolutionMultiple Wireless Technologies

More Capable Devices

Evolving Usage Models

Multi-radio operation is becoming the NormNeed for Handovers

**Types of HandoversHomogeneous (Horizontal) HandoversWithin Single Network (Localized Mobility)802.11r, 802.16e, 3GPP, 3GPP2Limited opportunitiesHeterogeneous (Vertical) HandoversAcross Different Networks (Global Mobility)More OpportunisticNeed for HandoversIEEE 802.21 is primarily for Vertical Handovers.can also be used for Homogeneous Handovers

**Genesis for 802.21Handover InitiationHandover PreparationHandover ExecutionIEEE 802.21 helps with Handover Initiation, Network Selection and Interface ActivationNeed for Handovers

**Handover StandardsHorizontal HandoversIP Mobility & Handover SignalingInter-working & Handover SignalingProvides 802 component to other Handover StandardsNeed for Handovers

**IEEE 802.21 StandardMedia Independent Handover ServicesOptimize Layer 3 and above Handovers Across 802 Networks and extend to Cellular Networks(802.3 802.11 802.16 Cellular)Key BenefitsOptimum Network SelectionSeamless Roaming to Maintain ConnectionsLower Power operation for Multi-Radio devicesFor More Information: www.ieee802.org/21802.21 Overview

**IEEE 802.21 MembershipSessionsSession #1 Orlando Mar 2004 ~40Session #5 San AntonioNov 200448Session #9 San Francisco July 200555Session #11 VancouverNov 200566Session #15 San DiegoJuly 2006 74

ParticipantsMembership has almost doubled over the last two years802.21 Overview

**802.21 History & Timeline1H 20042H 2004802.21 WG CreatedCall For Proposals1H 200514 Initial Proposals2H 20051H 2006Down selection Initial 802.21 Draft Text2H 2006Initiate Amendments to 802.11u, 802.16g. IETF (MIPSHOP) on L3 1H 2007Sponsor Ballot*2H 2007802.21 Spec Ratified*2008-2009802.21 Deployment*Letter Ballot* Projected Timelines802.21 Overview

**802.21: Key Services802.21 uses multiple services to Optimize Vertical Handovers802.21 Overview

**L2 Events (Triggers)WLANWWANLink UpLink Going DownLink DownLink UpLink SwitchMake before BreakConnectedDisconnectedState Change Events Link Up Link Down Link Parameters ChangePredictive Events Link Going Down Network Initiated Events Load BalancingOperator PreferencesTriggers Minimize Connectivity Disruption during Link SwitchingTime802.21 Overview

**Proposed Link Layer Events802.21 Overview

NoEvent TypeEvent NameDescription1State ChangeLink UpL2 Connection established2State ChangeLink DownL2 Connection is broken3PredictiveLink Going DownL2 connection breakdown imminent4State ChangeLink DetectedNew L2 link has been found5State ChangeLink Parameters ChangeChange in specific link parameters has crossed pre-specified thresholds (link Speed, Quality metrics)6AdministrativeLink Event RollbackEvent rollback7Link TransmissionLink SDU Transmit StatusImprove handover performance through local feedback as opposed to waiting for end-to-end notifications8Link Synchronous Link Handover ImminentL2 intra-technology handover imminent (subnet change). Notify Handover information without change in link state.9Link SynchronousLink Handover CompleteNotify handover state

**802.21 Information ServerMedia Independent Information ServiceGlobal Network MapList of Available Networks - 802.11/16/22, GSM, UMTSLink Layer Information - Neighbor MapsHigher Layer Services - ISP, MMS, .802.21 Overview

Network TypeSSID/ Cell IDBSSIDOperatorSecurityNWChannelQoSPhysical LayerData RateGSM13989N/AAT&TNANA1900N/AN/A9.6 kbps

Network TypeSSID/ Cell IDBSSIDOperatorSecurityNWChannelQoSPhysical LayerData RateGSM13989N/AAT&TNANA1900N/AN/A9.6 kbps802.11bIntel00:00:Intel.11iEAP-PEAP6.11eOFDM11 Mbps

Network TypeSSID/ Cell IDBSSIDOperatorSecurityEAP TypeChannelQoSPhysical LayerData RateGSM13989N/AOper-1NANA1900N/AN/A9.6 Kbps802.11nEnterprise00:00:Oper-2.11iEAP-PEAP6.11eOFDM100 Mbps802.16eNANAOper-3PKMEAP-PEAP11YesOFDM40 Mbps

**Information about all Networks from Single radioCellular radio indicates presence of suitable WiFi hotspotCommon Information Representation across different Networks, Rich InformationTLV, XMLEnable mobile policies beyond what can be pre-configuredMedia Independent ModelUse L2 for initial Network Discovery and SelectionUse L3 when available for client specific informationMedia Independent Information ServiceInformation Service can help with Network Discovery and Selection leading to more effective Handover decisions802.21 Overview

**Information Elements802.21 Overview

Information ElementDescriptionCommentsList of networks availableList all network types that are available given client locationE.g., 802.11, 802.16, GSM, GPRS/EDGE, UMTS networks Location of PoA Geographical Location, Civic address, PoA IDE.g. GML format for LBS or network management purpose Operator IDName of the network providerE.g. Could be equivalent to Network ID.Roaming PartnersList of direct roaming agreementsE.g. in form of NAIs or MCC+MNCCostIndication of costs for service/network usage E.g, Free/Not free or (flat rate, hourly, day or weekly rate)SecurityLink layer security supportedCipher Suites and Authentication Methods, Technology specific, e.g. WEP in 802.11, 802.11i, PKM in 802.16, etc.Quality of Service Link QoS parameters 802 wide representation, application friendlyPoA CapabilitiesEmergency Services, IMS Services, etc.Higher Layer Services Vendor Specific IEsVendor/Operator specific informationCustom information

**Types of Handover Based on Control ModelTerminal ControlledTerminal makes use of some MIH servicesTerminal Initiated, Network AssistedTerminal makes use of MIH Information ServiceNetwork Initiated and Network ControlledNetwork makes use of MIH Event and Command Service, plus Information Service knowledge, to decide if handover is needed/desired, to decide the target, and to command the terminal to handover

**Handover Commands for Network Initiated Handovers802.21 Overview

NoCommand NameMIHF MIHFDescription1MIH Handover InitiateClient Network Initiates handovers and sends a list of suggested networks and suggested PoA (AP/BS).2MIH Handover PrepareNetwork Network This command is sent by MIHF on old network to MIHF on suggested new network . This allows the client to query for resources on new network and also allows to prepare the new network for handover3MIH Handover CommitClient NetworkIn this case the client commits to do the handover based on selected choices for network and PoA.4MIH Handover CompleteClient NetworkNetwork Network This is a notification from new network PoA to old network PoA that handover has been completed, new PoA has been established and any pending packets may now be forwarded to the new PoA.

**Handovers: Who makes the Decision ?IEEE 802.21 enables Co-operative Handover Decision MakingMeasurementsTriggersNeighbor MapsService InformationIEEE 802.21Measurements, Triggers, Neighbor InformationMobile Device(User)Network(Operators)802.21 Overview

**Collection of all MIHF messages sent between peer MIH entitiesIncludes Events, Commands and IS exchangeCommon message payload across different media802.3, 802.11, 802.16, CellularMedia specific TransportsUse Data plane whenever availablee.g: In State 3 for 802.11Use Management plane when Data plane not availableAction Frames in State 1 for 802.11MIHF Protocol802.21 Overview

** F MIHF Fixed HeaderMIHF Variable HeaderMIHF PayloadMIH Function FrameMIHF Protocol802.21 Overview

**Media specific AmendmentsMIH Protocol (MAC independent messages) defined in 802.21Container for MIH messages for 802.11 defined in 802.11uContainer for MIH messages for 802.16 defined in 802.16gWorking with 3GPP-SAE for 3GPP specific changesTransport for MIH Protocol defined in IETF (MIPSHOP)Media specific changes closely follow base protocol Media Specific Enhancements

**802.11 Amendments802.11u is a task group that was chartered to allow devices to inter-work with external networks, as typically found in hotspots.It assists the advertising and connection to remote services beyond the DS and it intends to provide information to the STA about the external network prior to association.Natural task group to work with 802.21

**802.11 AmendmentsMIH Capability Delivery802.11 MLME SAP ExtensionsInformation Service for Generic Network Selection802.11 Transport for MIHF Protocol

**MIH Amendments for 802.11New items in scope of 802.21No New Mobility ProtocolsDoes Not handle Handover ExecutionNo Redesign of Existing PHY/MAC802.11 Amendments

PHY_SAP

MLME_SAP

MAC

PHY

MAC_SAP

MLME

PLME

MLME_PLME_SAP

PLME_SAP

LLC

SMEorNME

LSAP

MLME_SAP

Layer 3 or higher Mobility Protocol (L3MP)

MIH FunctionMIH Event ServiceMIH Command ServiceMIH Information Service

802.21 Scope

MIH_SAP

**802.11 based Reference Network802.21 ISHot Spot #1Hot Spot #NNAP Core NetworkNAP NOCAAASSPN #2 Core Network802.21 ISSSPN #2 NOCAAASSPN #1 Core Network802.21 ISSSPN #1 NOCAAAInternetTunnelTunnelMIHMIHUse 802.21 as Protocol for Network Selection

**Mobile Node can detect whether 802.11 Network supports MIH Function through 802.11 BeaconBeacon conveys MIH Capability InformationWhat does MIH Capability mean?802.11 supports MIH query in state 1 using Action FrameInformation Service QueryES/CS Capability DiscoveryMIH Capability Discovery802.11 Amendments

**SAP ExtensionExtensions to MLME-SAP to support MIH related PrimitivesUse existing 802.11 Primitives when applicableSome extensionsMLME-SCAN.confirmMLME-MIHProtocol.indication, MLME-LinkUp.indication802.11 Amendments

**Information Service as Generic Network Selection Info QueryClientAPIS ServerBeacon(MIH Capability)Probe Request (IS Query frame)Probe Response (Status, Multicast Address)IS QueryIS Query ResponseB-SNA, MC(Query Response)MC(Query Response)802.11 Amendments

**802.11 Transport for MIHState 1Probe Request/Response for Information Service Query and ES/CS Capability discoveryAction FrameIS Query response, and ES/CS capability discovery responseState 3Ethernet frame with MIH Ethertype802.11 MAC is transparent to MIH protocol messages

802.11 Amendments

**802.16 Amendments802.16 Architectural Extension for MIH MIH Capability DeliveryNCMS Extension802.16 SAP Extension802.16 Transport for MIHF Protocol

**MIH Amendments for 802.16New SAPs in scope of 802.21L2.5No Redesign of Existing PHY/MAC802.21 is designed for existing and evolving NetworksNo New Mobility ProtocolsDoes Not handle Handover Execution802.16 AmendmentsC_SAP, M_SAP are extended to Support MIHNCMS supports MIH Primitives Delivery to MIH Function

PHY_SAP

M_SAP

MAC Common Part Sublayer

PHY

MAC_SAP

Convergence Sublayer (CS)

CS_SAP

C_SAP

NCMS

MAC Security Sublayer

Management Plane

Layer 3 or higher Mobility Protocol (L3MP)

MIH FunctionMIH Event ServiceMIH Command ServiceMIH Information Service

802.21 Scope

MIH_SAP

**Mobile Node can detect whether 802.16 supports MIH Function through 802.16 Broadcast MessageDCD (Downlink Channel Descriptor) conveys MIH Capability InformationMIH Capability Delivery802.16 Amendments

**NCMS ExtensionNetwork Control and Management SystemService Flow Id /Connection Id Management ServicesRF Transmission and Synchronization ServicesAAA ServicesNetwork Address Management ServicesMobility Management ServicesGateway and Router ServicesPaging Services Idle Mode ServicesNetwork Management ServicesMultimedia Session Management ServicesInter-working ServicesSecurity ServicesMedia Independent Handover Function ServicesRadio Resource Management Services802.16 Amendments

**SAP ExtensionC-SAP are M-SAP are extended to support MIH related PrimitivesManagement SAPMulti-mode interface managementControl SAPMedia Independent Handover Function ServicesUse existing 802.16 Primitives as much as possibleSome extensions e.g. C-MIH-NOTIFY, C-NEM-REQ/RSP, M-MTM-REQ/RSP/NOTIFY, etc 802.16 Amendments

**802.16 Transport for MIHGeneric MAC Mgmt message is defined for MIH (MOB-MIH_MSG)MIH Frame is conveyed through the Generic MAC management messageUse MIH Ethertype802.16 Amendments

Applications

UMTS Layer 1

MAC (H-ARQ)

RLC

RRC

GMM/SM

PHY_SAP

MAC

Management Entity

CS_SAP

NCMS

MAC_SAP

MIH_MGMT_SAP

MIH_RRC_SAP

IP

Mobility Management Protocol 2

Mobility Management Protocol 1

Handover Policy Control Function

Device Manager

MIH_SAP

M_SAP

C_SAP

Media Independent Handover Function

MIH_SME_SAP

PHY

PHY_SAP

MAC

Management Entity

CS_SAP

Network Control Management System

MAC_SAP

CS

MIH_SAP

M_SAP

C_SAP

Media Independent Handover Function

MIH Message (Data Plane)

MIH Message (Control Plane)

Multi-Mode Mobile Terminal

Base Station

MIH_SME_SAP

PHY

CS

**IETF WorkOn going work in MIPSHOP WG, Internet AreaAim is at:Defining a problem statement for transport over IP of the MIH protocolDefining delivery of information for MIH services layer 3 or above" protocolThis allows the network information to reside anywhere (not necessarily across the link-layer hop)Enables MIH services even in the absence of the corresponding link-layer supportFor discovery of IP node(s) providing services, it is expected that any of the several current L3 discovery mechanisms will be usedAn existing or new protocol may be used for the transport. If an existing one, MIPSHOP will create a guide on how to use such protocol for the specific taskDefine IP-layer discovery componentAddress security (out of scope for IEEE 802.21)

**Current IETF DraftsPersonal drafts on the problem statementMIH Problem Statement (draft-hepworth-mipshop-mih-problem-statement)Network Initiated Handovers PS (draft-melia-mobopts-niho-ps)Design Considerations for MIH Transport, draft-hepworth-mipshop-mih-design-considerations-00, E. HepworthPersonal drafts on transport protocolTransport of Media Independent Handover Messages Over IP I-D: draft-rahman-mipshop-mih-transport-00.txtSupporting Media Independent Handover Protocols with GIST, draft-hancock-mipshop-gist-for-mih-00.txtMobile and Wireless Neighborhood Discovery by Using DHCP (draft-jang-mipshop-nhdisc-00.txt)

**IETF UpdateNext steps:MIPSHOP WG chair instructed group to create a common agreed PS draft to be adopted by the WGMIPSHOP WG chair will work with 802.21 chair and liaison officers to ensure appropriate dialogue takes place to ensure alignmentTo satisfy IEEE 802.21 requirementsTo enable IETF to provide any necessary inputCreation of a design team to develop one proposal for the solution (to speed up completion)Need to ensure running code is created (a la IETF)

**3GPP Amendments(Working with SA2/SAE)Requirements in TR 23.882For Information ServiceFor Operator influenced Handovers (Handover Commands)It shall be possible for the operator to provide the UE with access network information pertaining to locally supported 3GPP and non-3GPP access technologies. The access network information may also include operator preferences based on locally available 3GPP and non-3GPP access technologies, and the information may be restricted to the access technologies or access networks the UE can use. Others: Work in Progress

**802.21 Amendments

802.21 Features802.11802.16IETFCapability DiscoveryBeaconsDCD Broadcast MessagesDHCPMIH Services when NOT Attached to NetworkIS only Mgmt Plane Action FramesIS only Mgmt Plane MAC Mgmt MessagesN/AMIH Services when Attached to NetworkIS/ES/CS Data Plane MIH EthertypeIS/ES/CS Data Plane MIH EthertypeIS/ES/CSNew Signaling protocol being definedSAP ChangesMLME SAPNCMS, C_SAP, M_SAPN/A

**3G WWANMxN Mixed-Network Client Use CaseHomeAirportZone 1Zone 2Zone 3Zone 4Zone 5Zone 6Zone 7Zone 9WiMAXZone 8WiMAXIEEE 802.21 for Network DiscoveryIEEE 802.21, SIP, VCC, IMS, for Network Selection and Service Continuity across multiple radios (3G WWAN Wi-Fi WiMAX)802.21, SIP, IMS for Service Continuity (Wi-Fi WiMAX)VCC, SIP, IMS for Call Continuity (3G WWAN Wi-Fi)Plug into power jack Wakeup Wi-FiContinue over Wi-FiWi-Fi Link Going Down. Operator initiated switch to WiMAXContinue session on WiMAXShutdown Wi-FiConnect to Wi-FiBattery level lowShutdown WiMAXSwitch to 3G WWANWakeup Wi-FiContinue session on Wi-FiOperating on 3G WWANContinue session on 3G WWAN

**SummaryWith advances in Devices, Networks and Usage Models Multi-radio operation is likely to become the norm IEEE 802.21 helps with Handover Initiation, Network Selection and Interface Activation during Vertical Handovers802.21 enables Co-operative Handover decision making between Clients and NetworkMedia specific changes closely follow base 802.21 MIH Protocol

**Thank You!

**Backup

**Acronyms

APAccess PointASN.1Abstract Syntax Notation number OneBSBase StationBSS Basic Service SetBSSID Basic Service Set IdentifierEAPExtended Authentication ProtocolGSMGlobal System for Mobile CommunicationsISP Internet Service ProviderMIHMedia Independent HandoverMMSMultimedia Message ServiceNCMSNetwork Control and Management SystemPoAPoint of Attachment (L2, AP/BS)PoSPoint of ServiceQoS Quality of ServiceRTPReal Time ProtocolSAPService Access PointSSIDService Set IdentifierVPNVirtual Private NetworkUMTSUniversal Mobile Terrestrial SystemXMLeXtended Markup Language

**LLC/CSMACPHY3 GPP3 GPP 2InterfaceMACPHYMedia Independent Handover Function (Network)ES CS IS802 InterfaceClient Station802 Networks3GPP3GPP2NetworkMIH Network Entity(. e.g ). MIH Server Controller Media Independent Handover Function (Client)Information Service over L2 Transport Remote MIH Events over L2 TransportHigher LayerTransport (E.g.,IP)IS / CS / ES over Higher Layer Transport Higher Layer TransportLLC/CSHigher Layer Transport L2/Co-located with MIHMGMTMGMTEventsES CS ISEventsEventsEventsMedia Independent Handover UserMedia Independent Handover User

IS: Information ServiceCS: Command ServiceES: Event ServiceLLC: Logical link controller

ES CS IS802.21 Services

**MIH Communication Model Serving PoA R3 R1 R2 R4 R4 MIH PoSNetwork Side Client Side R4 R5 R5 Candidate PoANon PoA Network EntityNon PoA Network EntityMIH PoSMIH PoSMIH MIH UE/MN PoA:L2 Point of Attachment (AP/BS)PoS: Point of ServiceMN: Mobile NodeUE: User EquipmentMIH: Media Independent Handover

Communication Reference PointCommentsTransportScope 802.21R1, R2Between MIH on a UE and MIH PoS on serving/candidate PoA.Usually L2YesR3Between the MIH on a UE and an MIH PoS on a non-PoA network entityUsually L3YesR4Between MIH PoS and a non-PoS MIH Function instance in distinct Network entitiesUsually L3YesR5Between MIH PoS and another MIH PoS instance in distinct Network entitiesUsually L3Yes

*******************************************************

802 21-IEEE-Tutorial.ppt

Documents

Transcript of 802 21-IEEE-Tutorial.ppt