September 2004Rudolf, Carlton and TGr Marian Rudolf, Alan Carlton - InterDigital doc: IEEE /1052r0
September 2004 Submission Rudolf, Carlton 2 Summary and TGr seem to address complementary mobility scenarios – Across 802 networks and Inter-ESS mobility r – Intra-ESS mobility for But expect partial overlap between and TGr mobility solutions, ESS definition is too broad and unclear and does not allow to draw a clear boundary line between and TGr When addressing L2 mobility handling across different 802 technologies, will automatically come up with a solution that implies L2 mobility handling for the same 802 technology Two different mobility solutions for are not an attractive option, and TGr mobility solutions should, either be fully complementary or TGr solution should be forwards-compatible with future framework Many good reasons speak in favor of a quickly available TGr standards supplement, but need to anticipate on development
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 3 Introduction From and TGr PARs and requirements, TGr scope “… This PAR will apply only to the STA-AP state within the same ESS,…” scope “… extensible 802 media access independent mechanisms that enable the optimization of handover between heterogeneous 802 systems and may facilitate handover between 802 systems and cellular systems” draft requirements – Handover Scenarios IEEE 802 Family, … Handover between and networks Handover between and networks, across ESSs … Media-Independent Handover addresses 802.xx to 802.yy and inter-ESS mobility cases r Fast BSS Transition addresses intra-ESS mobility cases
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton ESS definition ESS definition in Clause 3.25 “A set of one or more interconnected basic service sets (BSSs) and integrated local area networks (LANs) that appears as a single BSS to the logical link control layer at any station associated with one of those BSSs.” ESS definition in Clause 5 “ The key concept is that the ESS network appears the same to an LLC layer as an IBSS network. Stations within an ESS may communicate and mobile stations may move from one BSS to another (within the same ESS) transparently to LLC.” Key points, L2 connectivity inside ESS SSID does not define the ESS STAs within ESS may communicate and move transparently to LLC
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton ESS – logical definition AP + DS + Portal AP Distribution System STA Portal network HOSTRouter Clause “The key concept is that the ESS network appears the same to an LLC layer as an IBSS network. Stations within an ESS may communicate and mobile stations may move from one BSS to another (within the same ESS) transparently to LLC.” Source: by Nortel, Airespace
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 6 WM Portal Integration Distribution System AP Device WM Portal Integration Distribution System AP Device ESS with a logical DS and Portal using a Router STA network HOSTRouter STA L2 Hub or Switch Portal L2 link L2 Hub or Switch Portal Distribution System ESS ESS definition / L2 connectivity with VLAN Source: by Nortel, Airespace
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 7 Scenario 1 – L3 versus L2 mobility Internet R1 AP4 R2 AP3 AP2 AP1 L2 link ESS1 L2 link ESS2 TGr L2 mobility L3 assisted mobility (Mobile IP) FA No L2 connectivity between two DS Clear separation between L2 and L3 mobility handling and r complementary
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 8 Scenario 2 – Complex network setups Internet R1 AP4 AP3 AP2 AP1 L2 link ESS TGr L2 mobility L3 assisted mobility (Mobile IP) FA R VLAN L2 connectivity with Router Both L3 and L2 mobility handling apply (L3 assisted) and r (L2) conflicting mobility handling procedures ? Need to ensure some degree of cooperation between and TGr mobility solutions FA R2
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 9 Scenario 3 – In case and TGr don’t have the same understanding what an ESS is Internet R1 AP4 AP3 AP2 AP1 TGr L2 mobility FA R VLAN If don’t agree on “ESS” definition Both come up with a L2 mobility solution, but addressing the same scenario and r conflicting mobility handling procedures ? Need to define mobility scenarios to avoid solving the same problem twice ESS L2 mobility perspective L2 link ESS1 L2 link ESS2 TGr perspective
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 10 Scenario 4 – L2 mobility part Internet R AP2 AP L2 mobility FA R VLAN L2 link ESS TGr L2 mobility handover scenario from to To be seamless, will need features such as pre- authentication and neighbor discovery – same functionality needed in TGr for ESS From perspective, the ports could be replaced by AP, it would very likely not change the L2 mobility procedure ! Both and r duplicate functionality to allow seamless handover ?
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 11 Scenario 4 – L2 mobility (cont’d) r Pre-authentication Network discovery Management information … In L2.5 Pre-authentication Network discovery Management information … In MAC
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 12 Conclusions Expect partial overlap between and TGr mobility solutions, ESS definition is too broad and unclear and does not allow to draw a clear boundary line between and TGr without agreeing on specific mobility scenarios When addressing L2 mobility handling across different 802 technologies, will automatically come up with a solution that implies L2 mobility handling for the same 802 technology Two different mobility solutions for are not an attractive option, and TGr mobility solutions should, either be fully complementary or TGr solution should be forwards-compatible with future framework
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 13 Conclusions (cont) We favor quickly available solutions that address mobility but recognize that evolution towards 802 inter- technology solutions (802.21) is of great importance
doc: IEEE /1052r0September 2004 Submission Rudolf, Carlton 14 Recommendations Harmonization Valuable worked conducted within the group shall provide solid ground for further development within (Forward Compatibility) Joined meeting slot with is required as soon as 11r starts proposal evaluation Existing ESS logical concept needs to be translated into tangible implementation scenarios Either define mobility scenarios or Bring the issue up to 802.1