| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
In the entire example for Fast Cell Switching and Soft Handoff I had assumed the anchor was analogous to a BSC/APC (base station controller/Access Point Controller) Only in a decentralized implementation without this element would a BS/AP serve as an anchor. I think the original question posed by Jay form LG is a crucial one. If all the BS in the active set are served the same data for the MSS by the Anchor (BS/BSC) this could be a significant impact on backhaul requirements. Is there a concrete methodology for limiting the active set? I see the H_ADD and H_Delete messages but cant see where they are set. The Neighbor list can have 255 BS in it. The 802.16E/D4 has a lot of information to support FBSS and soft handoff has the active set been adopted? Should there be a value to set a limit on the number in the active set? Also should there be a parameter that if set precludes a BS form becoming an anchor. As an operator I would not want a Pico cell end node with little backhaul serving as an anchor. If you can set an option that a BS cannot serve as an anchor and FBSS is to be supported then in 6.3.20.2.6 “When operating in FBSS, the MSS only communicates with the Anchor BS for UL and DL unicast messages and traffic” is an incorrect statement.
David S. McGinniss Distinguished Member of Technical Staff Sprint Broadband Wireless Technology Development Group (630) 926-3184 david.s.mcginniss@mail.sprint.com
-----Original Message-----
Hi, Jay nad Inkyu,
This is Mary Chion. Sorry about the late reply.
In FBSS, only one BS will be communicating with the MSS at any time instance (the anchor BS). The BS can choose one of the BS in the active set to be the anchor BS through MOB-BSHO-REQ/RSP message. Once the MSS confirms the HO with MOB-HO-IND, The MSS should only expect trasmission from the anchor BS.
Regarding the question of which BS have the data, it's really an implementation issue, it also depends on what kind of network architecture you will be using. If your network architecture includes a control point for the BSs (i.e. BSC), the control point can buffer the data and only send to current anchor BS. When a new anchor BS is chosen, the conotrl point will just redirect the traffic. With distributed system, the anchor BS should be resposible for the data. When the ahcnor BS is changed, the old anchor BS can forward data to the new anchor BS. The above scenarios are only examples, the implementatios can be different from each company and should not be specified in the standard.
Regards,
Mary
|