Forwarding on behalf of Phil Barber
...
From: Phillip Barber
[mailto:pbarber@broadbandmobiletech.com] Sent: Monday, June 07, 2004
6:50 AM To: Iyer, Prakash Subject: Revised action list for
Phil Barber
This is my revised list. Please discuss today
in the conference call as I will be unavailable due to travel. Also, I
have received only the two comments on-list regarding my posted questions.
I am looking for more input.
Phil Barber HO Ad-Hoc Action
Items
- Clean-up
language in RNG-REQ/RSP and HO Process in ‘e’ doc to show:
- non-contention
based ranging is same as ‘invited’ ranging in ‘d’ doc except uses MAC
Address instead of Basic CID in RNG-REQ
- non-contention
based ranging only requires single RNG-REQ/RSP loop to establish Basic &
Primary CID and coarse PHY link conditions
- additional,
MSS initiated ranging loops may be required on MSS failure to decode Basic
& Primary CID and set working coarse PHY
- Clean-up
language in HO Process and add RNG-RSP tickler in ‘e’ doc to show:
- SBC-REQ/RSP
may, under most conditions, be skipped during HO (as when capabilities of
Target BS do not differ from Serving BS)
- add
tickler TLV item to RNG-RSP as shorthand mechanism for BS to notify MSS that
capabilities negotiation process can be omitted during the current HO
attempt
- Clean-up
language in HO Process and add RNG-RSP tickler in ‘e’ doc to show:
- PKM-REQ/RSP
may, under some conditions, be skipped during HO (as in pre-keying
authentication)
- add
tickler TLV item to RNG-RSP as shorthand mechanism for BS to notify MSS that
key authentication process during HO can be omitted during the current HO
attempt
- Clean-up
language in HO Process and add RNG-RSP tickler in ‘e’ doc to show:
- REG-REQ/RSP
may, under some conditions, be skipped during HO (as in
intra-BS/inter-sector BS HO; when context is persistent from Serving BS to
Target BS)
- add
tickler TLV item to RNG-RSP as shorthand mechanism for BS to notify MSS that
REG-REQ/RSP process during HO can be omitted during the current HO
attempt
- Clean-up
language in HO Process and add RNG-RSP tickler in ‘e’ doc to show:
- Network
Address acquisition may, under some conditions, be skipped during HO (as in
HO where Serving BS and Target BS have a common ARID)
- add
tickler TLV item to RNG-RSP as shorthand mechanism for BS to notify MSS that
Network Address acquisition process during HO can be omitted during the
current HO attempt
- Add
‘MSS Context Manager ID’, that would be a TLV item in the RNG-RSP MAC
management message identifying MSS context management between multiple
sectors/shared context management systems
- Add
‘ARID’ into NBR-ADV, that would identify Access Router ID for a given network
attachment through a given BS
- Fix
HO messaging mechanics to separate information discovery sharing activities
used to formulate HO decision from actual HO decision MAC management
messages. Currently, information
sharing and decision notification are muddled/merged.
Thanks, Phil
|