RE: [802.21] 802.21: Scope
Colleagues,
This is good summary of the issues, below. Thanks to the .16g group for
their proactive and close cooperation with the work in .21, and help
with communication beween the groups.
The three services of 21 are being specified to facilitate
inter-technology handover. There are many similarities and analogies
possible between the mobility events of intra-technology handover with a
subnet change, and inter-technology handover with subnet change. It was
thought during the beginning of .21 that close cooperation between the
mobility groups within the 802 WGs would identify these similarities,
and commonalities would emerge and be used to guide the evolution of
mobility both within .21 and the native WGs.
Comments or suggestions on this thread are welcome.
Best Regards,
Michael
________________________________
From: ext Phillip Barber [mailto:pbarber@emobiletech.com]
Sent: Tuesday, September 27, 2005 12:07 PM
To: STDS-802-21@listserv.ieee.org
Cc: Singh Ajoy-ASINGH1; Prakash Iyer; Williams Michael.G
(Nokia-ES/MtView)
Subject: Re: [802.21] 802.21: Scope
802.16g is authorized to work on this.
802.16g's PAR was essentially formulated to provide four authorized
functions:
1) to provide revision to the 802.16 reference model to bring
management into scope;
2) to provide management and control primitives, triggers and
any necessary information elements to support all features and
functions--including mobility (though in 802.16, mobility is currently
only defined for intra-802.16, intra-operator mobility)--in the 802.16
family of standards. Think authentication, admission, accounting,
security, mobility management, radio resource management, idle mode
management, service provisioning, etc..
3) provide those other management and control MAC and PHY
feature and function enhancements necessary to support the management
and control of 802.16 devices, especially as they relate to enabling the
existing defined features and functions in the 802.16 family of
standards. Not established to create all new features and functions,
especially those not specifically directed at enabling previously
existing features or functions. But if something was determined to be
broken from the standpoint that it could not be enabled to work with the
network, we can amend the use in 802.16 to make it work. But expect
802.16 to be very cautious in moving down such a path. The rule is we
are here to make existing stuff work, not to redo.
4) to act as the repository and implement changes requested by
802.21 to support heterogeneous technology handovers (though whether
that could be stretched to also include 802.21 handling of intra-802.16,
inter-operator mobility is questionable; depends on the 802.21 PAR).
That is quite a bit.
I hope this helps frame 802.21 scope discussion.
Speaking purely as a member of 802.16, I am not sure that it is terribly
wise from a project focus and completion standpoint for 802.21 to
bite-off solving every groups basic mobility problem. Probably best to
have 802.21 solve its heterogeneous piece and give the required changes
over to the individual air interface technology groups to implement. If
in implementing, the groups have to solve more fundamental questions
regarding mobility, authentication, security, etc..., these groups are
probably closer to their own technology and better equipped to handle
it.
Just my two cents.
Thanks,
Phillip Barber
Huawei
----- Original Message -----
From: Singh Ajoy-ASINGH1 <mailto:ASINGH1@motorola.com>
To: Iyer, Prakash <mailto:prakash.iyer@INTEL.COM> ;
STDS-802-21@listserv.ieee.org
Sent: Tuesday, September 27, 2005 1:04 PM
Subject: RE: [802.21] 802.21: Scope
Hi Prakash,
Which working group of 802.16 is working to define triggers for
inter-subnet L3 handoff? I am not sure
if 802.21 is defining inter-technology handoff itself. Rather it
is defining triggers, information elements
etc for higher layer mobility management protocol.
Regards,
Ajoy
________________________________
From: Iyer, Prakash [mailto:prakash.iyer@INTEL.COM]
Sent: Tuesday, September 27, 2005 12:36 PM
To: STDS-802-21@listserv.ieee.org
Subject: Re: [802.21] 802.21: Scope
Intra 802.16 handovers are being addressed in various 802.16TGs
and the WiMAX Forum. So I do not see a need for .21 to work on .16
handovers.
If .21 identifies specific deficiencies, then perhaps we can
figure out where to add/fix them.
-Prakash
________________________________
From: Gupta, Vivek G [mailto:vivek.g.gupta@INTEL.COM]
Sent: Tuesday, September 27, 2005 10:20 AM
To: STDS-802-21@listserv.ieee.org
Subject: [802.21] 802.21: Scope
802.21 mostly applies to handovers across heterogeneous
technologies such as 802.11, 802.16, etc. and Cellular systems.
However intra 802.11 handovers i.e. handovers between 802.11
ESSs are also within scope of 802.21.
Along similar lines I was wandering if 802.21 also needs to
address intra 802.16 handovers (in any form).
Did not see anything specific to that effect in the PAR or 5
Criteria documents, so my initial understanding is "no".
Any clarifications from Chairs or even other folks welcome.
Best Regards
-Vivek