
TC3x Multiplexer User's Guide
TC3x_UG_01_V03.10 -
Released
Page 48/50
10.01.2002
9.4.4 Description Case (04)
There is a version conflict – the lowest internal version is used.
<Message Flow Case (04)>
9.4.5 Abnormal Cases
The SW implementation from the MS point of view is known, but on the TE side the following abnormal
cases are possible:
•
´Request Test Message´ is not sent from TE side:
No Version check takes place. No retransmission for ´Request Test Message´ is triggered. The
multiplexer is started with the lower version.
•
´Response Test Message´ is not sent from TE side:
No timer has been implemented for the non responding cases. If the response message is not
received as expected, the multiplexer stays in the state DLC_CONNECTEDWAIT4RESPONSE
until another multiplexing related action takes place.
However it is possible to send test commands with “any contents” (with exception of test messages
with the specific IEI for the Version Check, as defined in chapter 9.5).
If a test command with “any contents” is sent, it has to be sent back to the originator with the same
contents.
TE
MS
enable DLC (DLCI=0..3)
- AT+CMUX=0
UIH TestCommand
(P=0, C/R=1, TEMUX_VersionX)
UIH TestCommand_Resp
(P=0, C/R=0, TEMUX_VersionX)
- Comparison MSMUX_VersionY =! TEMUX_VersionX -> the lower
multiplexer version is used (minimum of internal version TE and MS)
UIH TestCommand
(P=0, C/R=1, MSMUX_VersionY)
UIH TestCommand_Resp
(P=0, C/R=0, MSMUX_VersionY)
- Version check