| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Following are the minutes from the handoff adhoc telecon on 6/10/04:
Discussions:
Following contributions have been
withdrawn:
04/74, 04/75r2
We went over contributions categorized
across different scenarios; details are as follows:
Scenario: Inter-sector HO where BS ID of serving and
target BS is assumed to be the same:
(Diff. freq, same FFT size, same IP subnet/prefix, no AAS)
This is one of the basic scenarios.
From a scrub of pending contributions, the following contribution (available in
temporary upload directory) seems applicable:
* method to reduce a munber of scanning.pdf
We did not discuss this contribution. Action item for the group is to review this draft prior to the next telecon.
Scenario: Inter-sector HO where it does
not matter if serving and target BS ID are same or different:
(Diff. freq, same FFT size, same IP
subnet/prefix, no AAS)
There are several contributions (including ones promised) that potentially fall into this category. They are listed below with updates based on the telecon:
* 04/87r1, 04/105_enhanced HO reentry, Phil's planned contribution on optimizing invited ranging, skipping SBC-REQ/RSP, skip PKM REQ-RSP, skip REG REQ/RSP, skip IP addrress acquisition
Group agreed that these 3 contributions should be harmonized to address the following: Definitions of levels of backbone information sharing/communication, grouping of functions during network (re)entry and how levels map to such groupings, under what conditions can certain MSS - BS network entry functions be skipped or optimized and how, how will an MSS 'discover' the level of backbone information sharing supported by a serving and target BS and format and content of information that is shared at each level. Transport of such information between a serving and target BS will not be discussed for now. It may also be possible to combine this with the previous contribution - method to reduce a munber of scanning.pdf
Action Item: Itzik, Jung-won, Phil (others interested) work together to harmonize contribution and upload new text for group review prior to next telecon
* 105_Inter-sector HO, 04/58
Action Item:
Jung-won to attempt to harmonize these 2 contributions prior to next
telecon
*
04/48 - Group to review prior to
next telecon
Action Item: Phil Barber to propose updated text for MSS Context (ID?),
Sector ID and FA ID based on recent email discussions prior to next
telecon
Scenario: Inter-sector HO where serving
and target BS ID are assumed to be different:
(Diff. freq, same FFT size, same IP
subnet/prefix, no AAS)
Following
contributions seem to be relevant to this category:
* 04/105-MSS Release after completing initial network entry -
Group to review prior to next telecon
* 04/55
Action Item: Changhoi Koo to upload revised contribution before next
telecon
* 04/57 - Group to
review prior to next telecon
* 04/76r2 - Group to review prior to next
telecon
* 04/61 - Group to review prior to next telecon
* 04/65 - Group to
review prior to next telecon
* 04/50r1 - Group to review prior to next
telecon
* 04/51r1 - Group to review prior to next telecon
* Scanning Optimization.pdf, A method
for scanning neighbor BSs periodically.pdf, BS initiated Handover with early
scanning.pdf
Action Item: Contribution
authors (Ronny Kim, Changjae Lee) to harmonize text before next telecon
* 04/105r1 - Proposal for fast timing
synchronization in OFDMA - Group to
review prior to next telecon
Scenario: Different FFT size between sectors (same or different BS
ID):
Lots of discussion around
possibly extending NBR-ADV to include PHY information such as modulation,
frequency, FFT size etc. Discussion to continue on the mailing list.
Scenario: Multiple frequencies per
sector (same or different BS ID):
Discussions were inconclusive in terms of requirements and how to
support multiple frequency assignment per sector. David Castelow has posted a
response to an earlier comment from Vladimir. Request to other adhoc group
members to review and respond to this thread. 3 action items were
identified:
Action Item: Jung-won to send out email on deployment scenarios involving multiple frequency assignment to level set the group
Raja Banerjea to send out
email to level set understanding of FA in DCD map
Dave Mcginniss to send out deployment
scenario requirements
Scenario: Different IP subnet/prefix
(Serving and Target BS IDs are assumed to be different):
At least 3 contributions that need to be harmonized
* 04/90r2, 04/68r2, Phil Barber's proposal ARID
proposal
Ronny
described a scenario in which a BS may need to support DHCP enabled client and
MIP clients implying that a BS may need to support more than 1 subnet/prefix ID
or ARID simultaneously. Discussions to continue on the mailing list.
Scenario: Optimization of Idle Mode
during HO:
There are 4
contributions:
* 04/108
* 04/66
* 04/28r1
*
04/105 - Complementing Idle Mode handover
operations
Group to review
these contributions prior to the next telecon.
Scenario:
Soft HO (Serving and Target BS ID are assumed to be different) - including AAS
support:
* 04/105 Soft HO defintion and requirements
* 04/110
* Soft Handover Procedure.pdf
Group to review these contributions and discuss on
the mailing list - especially PHY
folks. Also, it may be possible to
harmonize contributions on Fast BS Switching HO with Soft HO
contributions: 04/117,
04/60r1
Miscellaneous contributions:
Group is requested to review the following
contributions prior to the next telecon:
* 04/115 - improving cell search when mobile
* 04/69 - support for
multicast services (Yong Chang to upload updated contributions suggesting text
changes in D3 draft)
* 04/52 - protection of
backbone messages (we may want to defer discussion on this contribution)
* New contribution to be uploaded by
Changhoi Koo on ping-pong criteria
Next week:
*
Group agreed to 2 telecons: Monday 8 PM US Pacific time and Thursday 6 AM US
Pacific time. Telecon logistics to follow.
* Priorities for next week:
- Follow up on action items listed above
including all group reviews of contributions
- Discussion on text changes relative to D3 and
finalization of scope of changes
-
Discussion on remaining open issues - Mobility Agent, updates to SDLs in
annexes
- Review requirements being
uploaded by operators