| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Dear BJ, Your explain is based on the wrong reference
¡°Paging-group-action
message¡±. PAGING_OFFSET can be assigned individual MSS
according to current draft and original purpose of contribution about idle
mode, But Paging-group-action message doesn¡¯t reflect it well. I admit we, co-contributor of idle mode,
have a mistake for them but we don¡¯t care much about it because it is not subject
of standardization but annex. And I appreciate your work to refine it. But, anyway, backbone message in your contribution
should reflect current draft as it is. As conclusion, PAGING_OFFSET should not be
removed in Paging-announcement message. P.S. I add my reply for your e-mail in
line. Jung Je Son, Ph. D. Senior Engineer Global Standards Strategy Team SAMSUNG ELECTRONICS CO., LTD Tel : +82-31-279-5098 --------------------------------------------------
What Do You Want To Be?
Plan, Do and See? -------------------------------------------------- From:
owner-stds-802-16-mobile@LISTSERV.IEEE.ORG
[mailto:owner-stds-802-16-mobile@LISTSERV.IEEE.ORG] On Behalf Of BJ Kim 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. à not
right as I already mention above 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. à Because Paging-announce message
is to inform the recipient BS of the MSS with right position of paging, therefore, we still need
PAGING_OFFSET and PAGING_CYLCLE. 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. à still not right, MOB-PAG_ADV message will be
transmitted in right position for each MSS, therefore it doesn¡¯t to include
PAGING_OFFSET. And If MSS or BS want to re-negotiate those parameter, they
should operate network-entry or location update for it. If you have another
reason addressed above, give me a response about that. Best Regards, BJ |