2section (Continued) 6 Layer 3 Processing



Download 3.74 Mb.
Page53/61
Date19.10.2016
Size3.74 Mb.
#3566
1   ...   49   50   51   52   53   54   55   56   ...   61
2.6.6.2.6 Set Maintenance
2.6.6.2.6.1 Maintenance of the Active Set

The mobile station shall support a maximum Active Set size of N6m pilots. The mobile station shall track the pilot strengths of all pilots in the Active Set.

When the mobile station is first assigned Forward Traffic Channels, the mobile station shall initialize the Active Set to contain the pilots associated with the assigned Forward Traffic Channels. When the mobile station processes an Extended Handoff Direction Message, a General Handoff Direction Message or Universal Handoff Direction Message, then at the action time of the message the mobile station shall replace the pilots in the Active Set with the pilots listed in the message.

If the call rescue allowed timer is enabled, then the mobile station shall autonomously add one or more Candidate Set pilots whose strength exceeds T_ADDs to the Active Set, beginning with the strongest, provided that:

• the NGHBR_RESQ_CONFIGURED field of the NGHBR_REC for the corresponding pilot is equal to ‘1’, and

• the resulting Active Set size does not exceed N6m pilots.

When autonomously adding Rescue Channel pilots to the Active Set, the mobile station may autonomously drop one or more of the existing pilots in the Active Set, beginning with the weakest, to allow for adding pilots when the Active Set is full.


2.6.6.2.6.2 Maintenance of the Candidate Set

The mobile station shall support a maximum Candidate Set size of N7m pilots.

When the mobile station is first assigned a Forward Traffic Channel, the mobile station shall initialize the Candidate Set to contain no pilots. The mobile station shall adjust the Candidate Set whenever any of the following events occur:

• If the mobile station detects that the strength of a Neighbor Set pilot or a Remaining Set pilot exceeds T_ADDs, the mobile station shall add the pilot to the Candidate Set.

• If the mobile station processes an Extended Handoff Direction Message, a General Handoff Direction Message or a Universal Handoff Direction Message which does not list a pilot in the current Active Set, and the handoff drop timer corresponding to that pilot has not expired at the action time of the message, the mobile station shall add the pilot to the Candidate Set at the action time of the message.

• If the mobile station autonomously drops an existing pilot in the Active Set (see 2.6.6.2.6.1), and the handoff drop timer corresponding to that pilot has not expired, the mobile station shall add the pilot to the Candidate Set.

• If P_REV_IN_USEs is greater than three, and SOFT_SLOPEs is not equal to ‘000000’, the mobile station shall perform the following:

– If the mobile station processes a General Handoff Direction Message or a Universal Handoff Direction Message which does not list a pilot in the current Active Set, the handoff drop timer corresponding to that pilot has expired at the action time of the message, and that pilot is found to be above T_DROPs, the mobile station shall add the pilot to the Candidate Set at the action time of the message.

– If the mobile station autonomously drops an existing pilot in the Active Set (see 2.6.6.2.6.1), the handoff drop timer corresponding to that pilot has expired, and that pilot is found to be above T_DROPs, the mobile station shall add the pilot to the Candidate Set.

• If the mobile station processes an Extended Handoff Direction Message, a General Handoff Direction Message or Universal Handoff Direction Message, which lists a pilot in the current Candidate Set, the mobile station shall delete the pilot from the Candidate Set at the action time of the message.

• If the handoff drop timer corresponding to a Candidate Set pilot expires, the mobile station shall delete the pilot from the Candidate Set.

• If the mobile station autonomously adds a Candidate Set pilot to the Active Set (see 2.6.6.2.6.1), the mobile station shall delete the pilot from the Candidate Set.

• If the mobile station adds a pilot to the Candidate Set, and the resulting Candidate Set size exceeds N7m, the mobile station shall delete from the Candidate Set the pilot whose handoff drop timer is closest to expiration. If more than one such pilot exists, the mobile station shall delete one such pilot that has the lowest strength. If no pilot in the Candidate Set has an enabled handoff drop timer, the mobile station shall delete from the Candidate Set the pilot that has the lowest strength.


2.6.6.2.6.3 Maintenance of the Neighbor Set

The mobile station shall support a Neighbor Set size of at least N8m pilots.

When the mobile station is first assigned a Forward Traffic Channel, the mobile station shall initialize the Neighbor Set to contain all the pilots specified in the most recently received Neighbor List Message, Extended Neighbor List Message or General Neighbor List Message.

The mobile station shall maintain a counter, AGEs, for each pilot in the Neighbor Set. The mobile station shall initialize this counter to zero when it moves the pilot from the Active Set or the Candidate Set to the Neighbor Set. The mobile station shall initialize this counter to NGHBR_MAX_AGEs when it moves the pilot from the Remaining Set to the Neighbor Set. The mobile station shall increment AGEs for each pilot in the Neighbor Set upon receipt of a Neighbor List Update Message or an Extended Neighbor List Update Message. When the mobile station is first assigned to a Forward Traffic Channel, the mobile station shall set AGEs for each pilot in the Neighbor Set to NGHBR_MAX_AGEs.

The mobile station shall adjust the Neighbor Set whenever any of the following events occur:

• If the mobile station receives a Neighbor List Update Message or an Extended Neighbor List Update Message, it shall perform the following:

– Increment AGEs for each pilot in the Neighbor Set.

– Delete from the Neighbor Set all pilots whose AGEs exceeds NGHBR_MAX_AGEs.

– Add to the Neighbor Set each pilot named in the message, if it is not already a pilot of the Active Set, Candidate Set, or Neighbor Set. If the mobile station can store in the Neighbor Set only k additional pilots, and more than k new pilots were sent in the Neighbor List Update Message or the Extended Neighbor List Update Message, the mobile station shall store the first k new pilots listed in the message.

• If the handoff drop timer of a pilot in the Candidate Set expires, the mobile station shall add the pilot to the Neighbor Set.

• If P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to ‘000000’, the mobile station shall perform the following:

– If the mobile station processes an Extended Handoff Direction Message, a General Handoff Direction Message, or a Universal Handoff Direction Message in which a pilot in the Active Set is not listed, and the handoff drop timer corresponding to the pilot has expired, the mobile station shall add the pilot to the Neighbor Set.

– If the mobile station autonomously drops an existing pilot in the Active Set (see 2.6.6.2.6.1) and the handoff drop timer corresponding to the pilot has expired, the mobile station shall add the pilot to the Neighbor Set.

• If P_REV_IN_USEs is greater than three, and SOFT_SLOPEs is not equal to ‘000000’, the mobile station shall perform the following:

– If the mobile station processes an Extended Handoff Direction Message, a General Handoff Direction Message, or a Universal Handoff Direction Message which does not list a pilot in the current Active Set, the handoff drop timer corresponding to that pilot has expired, and that pilot is found to be below T_DROPs, the mobile station shall add the pilot to the Neighbor Set.

– If the mobile station autonomously drops an existing pilot in the Active Set (see 2.6.6.2.6.1), the handoff drop timer corresponding to that pilot has expired, and that pilot is found to be below T_DROPs, the mobile station shall add the pilot to the Neighbor Set.

• If the mobile station adds a pilot to the Candidate Set, and the resulting Candidate Set size exceeds the size supported by the mobile station, the mobile station shall add the deleted Candidate Set pilot to the Neighbor Set (see 2.6.6.2.6.2).

• If the mobile station detects that the strength of a Neighbor Set pilot exceeds T_ADDs, the mobile station shall delete the pilot from the Neighbor Set.

• If the mobile station processes an Extended Handoff Direction Message, a General Handoff Direction Message or a Universal Handoff Direction Message which lists a pilot in the current Neighbor Set, the mobile station shall delete the pilot from the Neighbor Set.

• If the mobile station adds a pilot to the Neighbor Set, and the resulting Neighbor Set size exceeds the size supported by the mobile station, the mobile station shall delete from the Neighbor Set the pilot whose AGEs is the largest. If more than one such pilot exists, the mobile station shall delete one such pilot that has the lowest strength.



Download 3.74 Mb.

Share with your friends:
1   ...   49   50   51   52   53   54   55   56   ...   61




The database is protected by copyright ©ininet.org 2024
send message

    Main page