A3.2.5 Characteristics related to bearer services or teleservices

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

A3.2.5.1 Access interface

Description of the access interface to connect the DTE (e.g. V series (V.24, V.28), X series, two wire analogue interface for use with fax group 3, I.420 (S-reference point).

In case of a proprietary interface to a DTE (non standard), description of this interface (hardware and software).

In case of a non standard connector provide a mechanical adapter.

A3.2.5.2 Configuration of the MT

Description of the configuration information to be selected in the MT to connect a terminal equipment to the mobile termination.

Description of the (different) configuration(s) of the MT for each bearer service and each teleservice supported, with the range or value for the parameters and the configuration procedure.

For the purpose of test of MOC, the manufacturer shall describe precisely how it is possible to put the MT in the different configurations to generate the capability information of the Mobile according to subclause, and described as supported by the MS.

For the purpose of test of MTC, the manufacturer shall describe how to verify the correct selection by the MT of the required function with regard to the capability information as described below, especially using the messages at the Um interface if there is no R or S interface available (case MTO). The description shall be made for every combination of the parameter value valid for the MT.

A3.2.5.3 Capability information

Description of the capability information, related to supported bearer services:

– bearer capabilities;

– higher layer capabilities;

– lower layer capabilities.

The manufacturer shall describe for every capability the associated terminal functions and their characteristics.

A3.2.5.4 Subaddress or DDI number

Subaddress or a DDI number of the MT.

Procedure to allocate or change DDI number or subaddress, if possible.

A3.2.5.5 User to user signalling

Description of the function and the user’s access to it.

A3.2.5.6 Data call set-up and data call clearing

For each implemented transparent and non-transparent data service:

– Description of the data call establishment mechanism:

– Terminal initiated (CT108) (if possible);

– MT (MMI/EMMI) initiated;

– Description of DCE provided information (MT to TE), if any;

– Declaration of optimal function and procedure, services supported by the MT.

– Description of the data call clearing mechanism:

– Terminal initiated (CT109) (if possible);

– MT (MMI/EMMI) initiated;

– Description of DCE provided information (MT to TE) related to a mobile or network initiated call clearing, if any.

A3.2.5.7 Characteristics of non-transparent data services

Description of Radio Link Protocol (RLP) features supported.

Description of supported RLP parameters and how to modify these values (if possible):

<iws> IWF to MS window size

<mws> MS to IWF window size

<T1> acknowledgement timer T1

<N2> retransmission attempts N2

Ability to configure the MS to use non-default RLP parameters.

Description of flow control mechanism:


– OUTBAND COPnoFICt (CT105 and CT106).

A3.2.5.8 Possible ways of setting-up a call from either an external interface or internally

Describe in detail all possible ways a call can be initiated from the MS or a connected terminal.

A3.2.5.9 Application layer causing automatic call termination

State whether the call termination facility can be disabled and if so, describe in detail how.

A3.2.5.10 Call re-establishment for MS not supporting speech

Applicability of call re-establishment.