Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] DCD/UCD Change in Idle Mode



Beomjoon,
MSS may be interested in the value of DCD Change Count only in the following
context: the MSS decided [for some reason] to get synch with DL transmissions from certain BS
and to be able to receive DL data e.g. wait for Paging message [the BS is not necessarily the last one where
the MSS was registered]. During that procedure, MSS waits for DCD message to get DL PHY
parameters [like DIUC meaning] and current DCD change count.
After it's done, MSS may receive further DL transmissions.
There is no need to wait for UCD unless there is an intention to transmit RNG-REQ.
Vladimir
 
-----Original Message-----
From: Beomjoon Kim [mailto:beom@LGE.COM]
Sent: Saturday, December 18, 2004 9:03 AM
To: STDS-802-16@listserv.ieee.org
Subject: [STDS-802-16] DCD/UCD Change in Idle Mode

Dear all,
 
Can anyone answer the question if an MSS in Idle Mode detects a different value of DCD/UCD Count in DL/UL-MAP message during MSS Paging Listening Interval, does the MSS need to wait for DCD/UCD messages without entering Paging Unavailable Interval? I think when an MSS enters Idle Mode, it does de-registration from the current Serving BS, which means it does not keep DCD/UCD Count value to which it shall refer during Idle Mode. If it is true, the MSS cannot perceive if its DCD/UCD value has been changed or not. Am I correct?
 
Best Regards,
 
Beomjoon


This mail passed through mail.alvarion.com

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************


This mail passed through mail.alvarion.com

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************<b
This mail was sent via mail.alvarion.com

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************