Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION] Minutes f rom 8/11 telecon



Title: Message
Hi, all
 
 
In the middle of Page 3,  in the following sentence
"These TLVs are OFDMA-PHY specific parameters and are used to indicate an assigned ranging region and an assigned CDMA code
to a MSS who is being paged in this MOB_PAG-ADV message.", the assigned ranging region should be deleted, per Mo-Han's resolution below.
 
1. Move the dedicated ranging region allocation out of the MOB_PAG_ADV message and put it in the UL_MAP
    - I agree with this suggestion. Also, as suggested, we can use the reserved bit in UIUC = 12 for this purpose.
 
Regards,
 
Inkyu Paek
hanarotelecom
470-9, Shindaebang-dong,
Dongjak-gu, Seoul, Korea
 
Voice : +82-2-6266-5290
Fax : +82-2-6266-5309
 
----- Original Message -----
Sent: Friday, August 13, 2004 10:51 AM
Subject: Re: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION] Minutes f rom 8/11 telecon

Hi all,
 
I have uploaded a revised version of the contribution "Enhanced paging with assigned CDMA code (revision of 04_222) rev 1.pdf".
 
Regards,
 
Mo-Han

-----Original Message-----
From: Fong, Mo-Han [CAR:DP31:EXCH]
Sent: Thursday, August 12, 2004 3:21 PM
To: 'Iyer, Prakash'; STDS-802-16@listserv.ieee.org
Subject: RE: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION] Minutes from 8/11 telecon

Hi all,
 
Thanks for your comments during yesterday's conference call. Here is a summary of the open issues for the "Enhanced paging with assigned CDMA code (revision of 04_222).pdf":
 
1. Move the dedicated ranging region allocation out of the MOB_PAG_ADV message and put it in the UL_MAP
    - I agree with this suggestion. Also, as suggested, we can use the reserved bit in UIUC = 12 for this purpose.
 
2. There is also a suggestion for the BS to allocate dedicated UL resource for the MSS to send RNG_REQ immediately without first using CDMA code for ranging
    - My view is that this will incur too much overhead since the MSS timing/power has not been adjusted properly. Also, assigning dedicated UL resource for
      RNG_REQ immediately across multiple paging BSs will incur unnecessary overhead.
 
Please let me know if you have any further comments. We plan to upload a revised contribution for tonight's call to reflect the 1st open issue above.
 
Regards,
 
Mo-Han
-----Original Message-----
From: Iyer, Prakash [mailto:prakash.iyer@INTEL.COM]
Sent: Thursday, August 12, 2004 1:17 PM
To: STDS-802-16@listserv.ieee.org
Subject: [STDS-802-16] [STDS-802-16-MOBILE] [HARMONIZATION] Minutes from 8/11 telecon

NOTE - Harmonization adhoc will again meet tonight (8/12) from 8 - 11 PM US Pacific time. Logistics will be posted shortly
 
* Idle mode and paging harmonization  (DRAFT of Idle Mode Harmonization Rev.3.pdf)
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.
 
* Enhancement of association using SCAN REQ-RSP  (H80216e-04_03r1.pdf)
- 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.

* PHY Profile ID  (H80216e-04_04r1.doc)
- 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.
 
* Changes to NBR-ADV  (Enhancements.to.NBR.ADV.doc)
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