Since the server is currently experiencing heavy traffic Ceilidh is
sending you this message without waiting to update the counter.

UMTSForum.com

Re: Frame Protocol related questions

guest

the standards suggest that the target CFN used in the tr ch sync can be random. However it is suggested to use the target CFN derived from the RFN and also based on the results of the Node synchronization as it takes into account the delay over Iub, and also the offset between the clocks on the two nodes.

On 3/11/01, K.A.Rajsekhar wrote
--------------------------------
>Hello ,
>
>I have the following questions related to FP-CTCH spec:

>1. How is the 'Target CFN' field determined in the DL Transport Channel synchronisation frame. The UTRAN Sync spec( 25.401 ) and the FP-CTCH spec( 25.435 ) do not provide information about this.

>2. The DSCH DL frame header contains the 'MC info', 'Spreading Factor' and 'Code Number' fields. The first two are related to the PDSCH code mapping and can be determined using , the current TFCI(Field 2) value. But , the TFCI(Field2) value to be used for a DSCH , would have been known at Node-B via the 'DSCH TFCI signalling' procedure. Also the TFCI(Field2) seems to be sufficient to determine the 'MC Info', 'Spreading Factor' at Node-B, based on the DSCH configuration information. Related to this I have the following questions:

>i) Are the 'MC Info','Code Number' and 'Spreading Factor' information derived based on the selected TFCI , by FP at CRNC?

>ii) What is the need for sending this across to Node-B, if the latter already knows the TFCI(Field2) value to be used and hence the corresponding values for the above fields ?
>

> Thanks in advance for any information related to this.
>
>
>Regards,
>Rajsekhar
>

7/11/01