NOTE - Harmonization adhoc will
again meet tonight (8/12) from 8 - 11 PM US Pacific time. Logistics will
be posted shortly
Phil briefly reviewed comments
received on the reflector:
- PS Park - both
comments accepted
- Inkyu Paek - both comments
accepted
- Jungje Son's comments were
resolved
- Phil to update the idle mode
draft to rev 4 - this will be tagged as consensus
contribution.
All - Please review current
draft and email comments if any of the reflector
ASAP.
- Lengthy discussions resulted
in a few open issues.
Mo-Han to summarize open issues
and solution alternatives for each issue on the reflector today (8/12).
Consensus via discussions on the reflector and brief discussions on the
call later today. If possible, would like to move this forward as
consensus contribution.
- General comment: Good concept;
implementation question - where to place this channel without affecting
backward compatibility with 802.16-2004
- Need volunteers to work with
Kamran to figure out how this could be implemented. If progress cannot be
made, this will not be a harmonized consensus
contribution.
* Periodic ranging and sleep
mode
LGe took the action item to
harmonize with Samsung and upload a contribution for consideration as
consensus contribution on the call today.
All - meanwhile read both docs and send any comments to the
reflector ASAP.
- Phil had raised some issues;
Samsung requested more time to resolve these issues
-
Decision - discuss on reflector and attempt to close on telecon later
today.
- Group agreed to the 2 new
1-bit FA indicator fields as defined
- Open issue - how can we
flexibly define bandwidth so we are not restricted to what's in
the table in the document. To be discussed on the
reflector
- Yigal E. had proposed 2 new
fields on the reflector. These will be defined as optional TLVs and added
to this contribution (Yigal to send text to Jungwon
ASAP)
If we can find a satisfactory
solution for the bandwidth parameter representation, this contribution can
be tagged as consensus contribution
- Based on discussions, it was
decided that FA hashing could be used for initial network load balancing
but will have to be augmented by policy mangement which is out of scope of
.16e. Send any comments to Jungwon / reflector. No plans to move forward
as consensus contribution.
NOTE: Based on
discussions, we came up with 2 recommendations (need larger group to weigh in
ASAP)
- Preferred BS paramter as
specified in the contribution will be accepted
- Neighbor BS ID should be made
an optional parameter for SOFDMA in NBR-ADV message (takes up 24 bits, use
unclear in all scenarios)
Brainstorming resulted in a few
solution options:
- Make BS ID a
TLV
- Leave as
is
- Create a nested loop for FA
assignments (which could share the same BS ID)
- Create a long and short form
of NBR-ADV will specific fields omitted in short form to avoid parsing
challenges
DID NOT DISCUSS - Continue
on reflector today and telecons later today
*
Update on SHO/FBSS harmonization
* Update and plan for MBS
harmonization
*
Update on IP address management (ARID vs. Subnet zone ID etc.)
* New contributions that have been uploaded on the
reflector