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

Re: [STDS-802-16-MOBILE] [Handoff] Phil Barber action item from HO Ad-hoc conference call on 6/2/04



Dear Phil and all,
 
My comments are inline.
 
BR,
 
Changjae.
----- Original Message -----
Sent: Saturday, June 05, 2004 12:03 AM
Subject: [STDS-802-16-MOBILE] [Handoff] Phil Barber action item from HO Ad-hoc conference call on 6/2/04

I had this action item from the call:
 
* Phil - Propose new TLV flags to support notion of context ID - to convey sectors, frequency assignment and subnet/prefix/access router ID - by 6/8/04
 
A 'Sector ID' in the form of a BS MAC ID prefix, suffix, or additional message advertisement through DCD (and, by implication through NBR-ADV) has already been proposed by Samsung and I am just going to refine this idea.  Allowing for the bifurcation the existing BS MAC ID, exactly as proposed by Samsung, seems the best approach since it encourages fewer changes in other places in the document affecting, among other things, NBR-ADV messages.
 
I was planning on borrowing ARID use proposed in 802.21 and advertising it through NBR-ADV.  Sticking ARID into DCD seems overkill.  And we don't need ARID in RNG-RSP or SBC-RSP because I am already going to propose some HO/network re-entry flags in RNG-RSP that will cover that.
 
My question concerns the FA (frequency assignment) element.  My question is,
 
1) wouldn't the sector DCD have the required information for FA? 
Yes, the DCD have the Frequency param (DL center frequency).
 
Do we actually require additional MAC level information for advertising FA? 
I think by definition, each sector would have its own DCD, though for sectored BS using a single frequency/channel assignment, that DCD would be identical.  For sectored BS using different frequencies/channel assignments in each sector, the DCD would necessarily be different.  And since DCD is imbedded in NBR-ADV, we get appropriate neighbor advertisement as well.
 
I think that there is a problem on advertise the DCD for multiple frequency in a sector.
Because, In Neighbor Advertisement message structure, The TLV only got a "DCD_setting" per a sector (if we agree on the first paragraph- "Sector ID").
So, I think we actually require additional MAC level information for advertising for a FA_ID per multiple FA in a sector.
 
I would appreciate feedback on this item prior to my scheduled due date for submission.
 
Thanks,
Phil