From: John Wu <jw...@gm...> - 2011-10-27 07:55:33
|
Alexander Thanks, I don't know if I understand gsm 04.60 correctly. I think even on BTS side you are not able to know which cs you received. for in uplink TBF, MS may send some control message which is fixed coded with CS1 and you do not know when will the MS send a control message. On Thu, Oct 27, 2011 at 3:43 PM, Alexander Chemeris < ale...@gm...> wrote: > John, > > As Sylvain already mentioned, coding scheme is encoded in stealing > bits of Normal Bursts, transmitted over PDCH. Each RLC/MAC consist of > 4 NB's and thus you have 8 stealing bits pattern for each CS. Check > GSM 05.03 and read gprsdecode sources, it helps. > > Also note, that Uplink Coding Scheme is controlled by BTS and thus if > you're on the BTS side you always know which CS you receive. > > Are you implementing GPRS for some commercial stack? > > On Thu, Oct 27, 2011 at 11:06, John Wu <jw...@gm...> wrote: > > Hi all, > > I want to know how to know GPRS channel coding. GPRS using PDCH, both > > MAC/RLC data block and MAC/RLC control block is > > transmitted on PDCH, although there is PACCH, PTCH, PTCCH and so on it > > still PDCH. then the MAC/RLC control block is coded > > with cs-1 channel coding scheme and MAC/RLC data block may be coded with > > other channel coding scheme. so when received a > > burst how to know what kind of MAC/RLC block it belong to and which > channel > > coding scheme it used? > > > > Thanks! > > > ------------------------------------------------------------------------------ > > The demand for IT networking professionals continues to grow, and the > > demand for specialized networking skills is growing even more rapidly. > > Take a complimentary Learning@Cisco Self-Assessment and learn > > about Cisco certifications, training, and career opportunities. > > http://p.sf.net/sfu/cisco-dev2dev > > _______________________________________________ > > Openbts-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > > > > > > > -- > Regards, > Alexander Chemeris. > |