Hello Shishir,
You wrote:
Q: If the JCs(basically Cm(t)) inserted in a OPU4 frame , is for next frame ?
-If yes then what is the value of JCs , for first frame ?
The value does not matter because the first frame transported does not
contain client data.
As explained in ITU TG 709 - Annex D:
"Before GMP Sink synchronization: incoming II/DI values are indication that GMP source may change Cm(t) values in next frame. This seems II/DI field of current frame is telling about Cm(t) of next frame.
Yes, it is telling that it will change, not what the value will be.
Though after GMP sink synchronization: Spec says to use II/DI along with current Cm(t) to demap payload."
Correct.
IS that the case, as if behavior of II/DI changes before (used to decode Cm(t) of next frame) and after (To decode Cm(t) of current frame) synchronization at sink side?
If II/DI procedure is followed as described sink side and source side
are synchronised.
Kind regards, Huub.
--
reply to hhelvooort with 2 'o's ================================================================
http://www.van-helvoort.eu/ ================================================================
Always remember that you are unique...just like everyone else...
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)