Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Dear Jungje and all
I'm BJ, the author of the contribution
entitled as "Clarification of Paging Announce Message", and writing this Email
in connection with the contribution.
First, let me explain the reason why the
PAGING_CYCLE and PAGING_OFFSET field may be removed from the Paging-announce
message. As you know well, PAGING_CYCLE and
PAGING_OFFSET is determined when a paging group is defined using
Paging-group-action message. Therefore, when
a BS belonging a paging group receives a Paging-announce message, the BS has
already been informed of the PAGING_CYCLE and PAGING_OFFSET of the paging group
to which the BS belongs. The BS just transmits the MOB-PAG_ADV message
according to the active PAGING_CYCLE and PAGING_OFFSET. Also, note that the
first purpose of the Paging-announce message is to inform the recepient BS
of the MSSs that should be paged, not of the PAGING_CYCLE and
PAGING_OFFSET.
If it is possible to change the PAGING_CYCLE
and PAGING_OFFSET at any time for the purpose of distributing paging load you
mentioned, it is right that these two
fields must not be removed from the Paging-announce message. However,
unfortuately, we have no field to indicate the change of PAGING_CYCLE and
PAGING_OFFSET to MSSs that have already been in IDLE MODE because, in
MOB-PAG_ADV message, there is no field to notify the change of two parameters.
The MOB-PAG_ADV message has fields to indicate the Number of Paging Group
IDs and Paging Group IDs.
If you have another reason addressed above,
give me a response about that.
Best Regards,
BJ
|