Implementation - Siemens TC3 Series User Manual

TC3x Multiplexer User's Guide
The TE and MS multiplexer version numbers can be traced on the serial interface.
They appear as follows:
• TE version (e.g. version 1):
• MS version (e.g. version 2):
During the version check process the valid multiplexer version is negotiated. TE and MS agree on the
lower version of the two.
Examples:
1, 2:
These cases (bright green arrows) describe the straight case. TE and MS have the same multiplexer
version.
3:
TE does no version check, MS does version check. On MS side the protocol is automatically switched
back to the older state.
This constellation is never a problem, because the TE side has been realized with the known features.
Thus it expects no features, which will only be added in the next protocol version.
Example: TE Version 1, MS Version 2 Þ multiplexer version 1 is valid
4:
The TE side has the version check included, the MS side does not. The TE has to use the protocol
according to the old version. This can be done in the following ways:
PC
(MUX driver or PC Mux): DLLs for all versions are available and have to be chosen according to
the negotiated version.
•
Customer application with Siemens AG sources:
Switch back to the older protocol version on TE side. This is done automatically when using the
Siemens AG sources. This case should not happen, since the customer application is put into
service with the features which are being offered by Siemens AG at that point of time. New
protocol features can only be contacted by the application when they have been implemented on
the MS side.
•
Customer application with proprietary multiplexer implementation:
See Customer application with Siemens AG sources.
Example: TE Version 2, MS Version 1 Þ multiplexer version 1 is valid

9.3 Implementation

The TE initiates the version check by sending the test command message on DLCI 0
(with TEMUX_Version).
As specified in the GSM recommendation 07.10 (chapter 5.4.6.3.4) the opposite entity shall respond
with exactly the same value bytes.
The Test Command response (with TEMUX_Version) shall be sent from the MS with the same
contents for the verification pattern.
In the next step the MS shall send a Test Command message (with MSMUX_Version) and the TE shall
respond with the same contents. After sending the response a comparison will be performed.
The version check of the multiplexer is used to ensure the compatibility between TE- and MS-side. Via
this implementation it is possible to manage the different multiplexer versions.
After exchanging of version information a version compare is made on both sides. On both sides the
TC3x_UG_01_V03.10 - Released
TEMUXVERSION0001
MSMUXVERSION0002
Page 44/50 10.01.2002