11.5 Verification of non-support of services (multiparty)

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

11.5.1 Definition

–

11.5.2 Conformance requirement

An MS claiming to not support the MultiParty supplementary service and in the U10 call active state with one call and in the held state with another call shall, when the appropriate MultiParty MMI command is entered:

– Fail to combine the three parties in a MultiParty call.

– Optionally provide some indication to the user of an error.

3GPP TS 02.83, 3GPP TS 02.84, 3GPP TS 04.83, 3GPP TS 04.84.

11.5.3 Test purpose

To verify that an MS claiming to not support the MultiParty supplementary service and in the U10 call active state with one call and another call on hold, reacts in the following manner when the appropriate MultiParty MMI command is entered:

– Fails to combine the three parties in a MultiParty call.

– Optionally provides some indication to the user of an error.

11.5.4 Method of test

11.5.4.1 Initial conditions

The mobile originating generic call set up procedures shall be followed up to and including the transmission by the MS of the CONNECT ACKNOWLEDGE to place the call in the U10 call active state. A second directory number is then entered followed by send to put the first call on hold and place a second call.

11.5.4.2 Procedure

"3" followed by "SEND" is entered via the MMI.

11.5.5 Test requirement

The MS shall not send a FACILITY message, containing the build multiparty request, on the dedicated channel. This is checked for 3 s.

The MS may however send other messages.

The MS may also give the user an indication of the error that has occurred.