36558d9526
Since there can be multiple PDCH channels configured on different timeslots, different TRXes, and BTSes, the PTCCH/U handling code in OsmoPCU needs to know the exact origin of a given RACH.ind. Otherwise, it is not known which subscriber originated a given PTCCH/U indication, and hence it is impossible to send PTCCH/D Timing Advance notification properly. Fortunately, we can extend the RACH.ind message without even bumping the protocol version, because every single PDU has a fixed size defined by the largest message - INFO.ind. In case if the actual message payload is smaller, the rest is filled with a constant padding byte (0x00). Older versions of OsmoPCU will consider the new fields as padding, while the messages from older OsmoBTS versions will always have both fields set to 0x00. Since C0/TS0 cannot be configured to PDCH, this can be easily detected on the other end. Change-Id: Ia5c4e504a21dc5508920553d3856027455dba1b1 Related: OS#4102, OS#1545 |
||
---|---|---|
.. | ||
BTS_Tests.cfg | ||
BTS_Tests.default | ||
BTS_Tests.ttcn | ||
BTS_Tests_LAPDm.ttcn | ||
BTS_Tests_OML.ttcn | ||
BTS_Tests_SMSCB.ttcn | ||
README.md | ||
expected-results.xml | ||
gen_links.sh | ||
osmo-bsc.cfg | ||
osmo-bts.cfg | ||
regen_makefile.sh |
README.md
BTS_Tests.ttcn
- external interfaces
- A-bis side: RSL (emulates BSC-side server)
- Um side: L1CTL to control MS
- PCU side: pcu_socket
- VTY
- CTRL
{% dot bts_tests.svg digraph G { rankdir=LR; { rank=same; BTS, BSC}; BTS [label="IUT\nosmo-bts-trx",shape="box"]; ATS [label="ATS\nBTS_Tests.ttcn"]; BSC [label="osmo-bsc\nOML only"]; BTS -> fake_trx [label="bursts"]; fake_trx -> trxcon [label="bursts"]; trxcon -> ATS [label="GSM MAC blocks"];
BTS -> BSC [label="A-bis OML"]; BTS -> ATS [label="A-bis RSL"];
ATS -> BTS [label="pcu_sock"]; ATS -> BSC [label="VTY"]; ATS -> BTS [label="CTRL"]; } %}