| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear all:
As we had a discussion on the yesterday CC, the further explanation and clarification of the two indicator bits (Co-located FA Indicator and FA Configuration Indicator) with some deployment scenarios is necessary.
Actually, these two indicator bits are necessary only when the network is a multi-FA system. The main purpose of employing multiple FAs is to facilitate the load balancing including service redirection and to increase the total channel capacity at some hot traffic zones. Hence, only when the multi FA BSs are present, the structure of NBR-ADV would be a little changed.
The basic structure of NBR-ADV (the neighbor BSs are just listed) is made when there are only single-sector-single-FA BSs. (NBR-ADV would look like Start of NBR-ADV of BS_0 N_BS_ID 1 Its information N_BS_ID 2 Its information … ) The next level complication would be made if multi-sector BSs are present among the neighbor BSs. In this case, each sector would be described by an individual element in NBR-ADV (the same BS-ID but with different preamble index). (NBR-ADV would look like Start of NBR-ADV of BS_0 having BS_ID 0 BS_ID 0 Preamble index 1 and its information BS_ID 0 Preamble index 2 and its information N_BS_ID 1 Preamble index x and its information (Optionally can have other sectors of BS 1 as the following: N_BS_ID 1 Preamble index y and its information N_BS_ID 1 Preamble index z and its information) N_BS_ID 2 Preamble index x’ and its information (Optionally can have other sectors of BS 2 as the following: N_BS_ID 2 Preamble index y’ and its information N_BS_ID 2 Preamble index z’ and its information) … )
If there are multi-FA BSs are present, the next complication would be made. Each FA in a multi FA BS cannot have the same BS_ID in the current standard. (Apart from the standard aspect, if the # of FA is 4, the 22 most significant bit of the BS ID excluding the operator ID 24 bits can represent the real BS ID. But this would be only an implementation issue right now for the network designer right now, and it would cause some problems for legacy terminals. So, I want to preclude this kind of options at this time.) The NBR-ADV would look like as the following: Start of NBR-ADV of BS_0 having BS_ID 0 BS_ID 0 Preamble index 1 and its information BS_ID 0 Preamble index 2 and its information BS_ID 0 + \alpha (The co-located FA BS, but should have a different BS_ID from 0) Co-located FA Indicator = 1 with channel number i. Option 1: all information such as preamble index and DCD/UCD changes. But this BS (actually only ID-wisely different) would have the structure. So, the rest of the information including preamble index and else can be omitted. By doing so, the required number bits are reduced to only 48 bits (only 24 extra bits) Option 2: All sector can be listed afterwards. However, for the same reason that it would have the same structure as the serving BS, those can be omitted to reduce the size of the NBR-ADV. BS_ID 0 + \beta (The co-located FA BS, but should have a different BS_ID from 0) Co-located FA Indicator = 1 with channel number j.
N_BS_ID 1 with Co-located FA indicator = 0, which means that it’s a ‘real’ different BS Preamble index x and its information Option 3: If the FA Configuration Indicator = 1, the listing of the different FA can be omitted without loss of information since the BS 1 has the same FA configuration as the BS 0 (the same set of FA’s are used). But, this feature can be just not used by just setting 0 as the following and the serving BS may list all other FA’s of BS 1 although the size of NBR-ADV would be enormous.
(Optionally can have other sectors of BS 1 as the following: N_BS_ID 1 Preamble index y and its information N_BS_ID 1 Preamble index z and its information N_BS_ID 1 + \alpha
N_BS_ID 1 + \beta )
N_BS_ID 2 (Co-located Indicator = 0, FA Configuration Indicator = 0) PHY Profile ID, Preamble index and its information Option 4: Optionally, the serving BS may list all BS 2’s FA afterwards. But, to reduce the size of the message, it just indicates that it has a different FA structure. And the IDLE mobile which tries to connect BS 2 for location update or connection setup should decide the appropriate FA for load balancing using some hashing algorithm (on this idea, we are preparing a contribution) after listening the BS 2’s NBR-ADV. (Optionally can have other sectors of BS 2 as the following: N_BS_ID 2 Preamble index y’ and its information N_BS_ID 2 Preamble index z’ and its information
N_BS_ID 2 + \alpha’
N_BS_ID 2 + \beta’ ) I hope this email helps you understand the use of two indicator bits (actually, the contribution nearly has text changes alone). Please let me know if you have any feedback on this.
Best regards,
Jung-Won Kim
---------------------------------------------------------------- Jung-Won Kim, Ph.D.
Senior Engineer NTP System Lab. 1 Telecommunication Systems Division Samsung Electronics Co., Ltd.
Office: +82-31-279-3356 Mobile: +82-10-9530-3356 Email: jungwon74.kim@samsung.com
|