11.1 Verification of support and non-support of services (multiple numbering scheme or ISDN)

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

11.1.1 Mobile Terminated (MT) calls

11.1.1.1 Definition

This test is repeated for all Mobile Terminated Bearer Services / Teleservices according to 3GPP TS 02.02 and 3GPP TS 02.03 except Teleservices 21, 22 and 23.

11.1.1.2 Conformance requirement

1. The MS shall check the Information Elements for Bearer Capability in a received SETUP message, and if it agrees to the proposed set, it shall respond with a CALL CONFIRMED message.

3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.2; 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.3.

2. The MS in the "Null" state, U0, ready to receive a SETUP shall reject a SETUP with Information Elements for Bearer Capability which are incompatible with the Bearer Services / Teleservices supported by the MS, and shall send a RELEASE COMPLETE message.

3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.2; 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.3.1; 3GPP TS 07.01, subclause 8.3.1; 3GPP TS 04.08 / 3GPP TS 24.008, subclause B.3.2.

11.1.1.3 Test purpose

1. To verify that the MS, for the case of the Multinumbering scheme or ISDN, accepts a SETUP message, where the Information Elements for Bearer Capability are compatible with the Bearer Services / Teleservices declared as supported by the MS, by sending a CALL CONFIRMED message.

This is verified for all Mobile Terminated Bearer Services / Teleservices declared as supported by the MS.

2. To verify that the MS in the "Null" state, U0, when receiving a SETUP message containing incompatible Information Elements for Bearer Capability will respond with a RELEASE COMPLETE message.

This is verified for all Mobile Terminated Bearer Services / Teleservices not declared as supported by the MS.

11.1.1.4 Method of test

11.1.1.4.1 Initial conditions

For an MS with an external interface the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question. The manufacturer shall state how this is done in a PIXIT statement. The same applies to features which must be activated by MMI before an incoming call can be accepted.

The PIXIT statement for the service in question shall be consistent with the PICS statement made by the manufacturer and will result for this tests in one or several valid BC codings as presented in subclause 11.8.

The generic call set-up procedure shall be followed up to and including the reception of the CIPHERING MODE COMPLETE message from the MS.

11.1.1.4.2 Procedure

a) For a Mobile Terminated Bearer Service / Teleservice declared as supported by the MS. The SS transmits a SETUP message.

The SETUP shall contain a single or dual BC-IE where the parameter values are arbitrarily selected among those declared as supported by the MS in PIXIT statements and corresponding to the Bearer Service / Teleservice being tested.

b) If more than one BC-IE (or pair of) correspond to the Bearer Service / Teleservice being tested, step a) is repeated once (and only once) with another single or dual BC-IE. The BC-IE shall be chosen in such a way that as many parameters as possible are different from the previous BC-IE. In particular, if more than one value for the "Connection Element" parameter is possible, the new BC-IE shall contain a different value from the previous one for this parameter.

c) Step a) and b) are repeated for all Bearer Services / Teleservices declared as supported by the MS.

d) For an Mobile Terminated Bearer Service / Teleservice not declared as supported by the MS. The SS transmits SETUP. If the MS supports TS62 but not TS61, then TS61 is not tested.

The SETUP shall contain a single or dual BC-IE where the parameter values are arbitrarily selected among those defined in 3GPP TS 07.01 Annex II and corresponding to the Bearer Service / Teleservice being tested. The complete coding of the corresponding BC-IE(s) can be found in subclause 11.8.

e) Step d) is repeated for all Bearer Services / Teleservices not declared as supported by the MS.

11.1.1.5 Test requirement

1) After steps a), b) and c), the MS shall send a CALL CONFIRMED message. The MS may contain a single or dual BC-IE. If present these IEs are not checked.

2) After steps d) and e), the MS shall send a RELEASE COMPLETE message with cause value 88 – incompatible destination.

11.1.2 Mobile Originated (MO) calls

11.1.2.1 Definition

This test is repeated for all Mobile Originated Bearer Services / Teleservices according to 3GPP TS 02.02 and 3GPP TS 02.03 except Teleservices 21, 22 and 23, which are supported by the MS.

11.1.2.2 Conformance requirement

1. The MS shall set up a call with a SETUP message containing a single or multiple BC-IE and if required by the service, a single or multiple LLC according to the actual configuration of the MS. Two bearer capabilities can be present only in the cases described in 3GPP TS 07.01.

3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.2; 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.3.1; 3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.2; 3GPP TS 07.01, subclause 8.3.3.

2. The Repeat Indicator Information Element shall be included in the SETUP message, when the in-call modification procedure is used.

3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.2.

11.1.2.3 Test purpose

1. To verify that the MS generates a SETUP message which includes a single or multiple Bearer Capability and if required by the service, a single or multiple LLC, according to the actual configuration on the MS.

This is verified for all Mobile Originated Bearer Services / Teleservices described in 3GPP TS 07.01 and declared as supported by the MS.

2. To verify that the MS includes a correctly encoded Repeat Indicator if it includes multiple Bearer Capabilities in the SETUP message.

11.1.2.4 Method of test

11.1.2.4.1 Initial conditions

If possible, the MS shall be configured to initiate an outgoing call with a specified BC and with the corresponding LLC when the ITC value is "unrestricted digital" in the SETUP message. The manufacturer must state how this is done in a PIXIT statement. The same applies to features which must be activated by MMI before an outgoing call can be initiated.

The PIXIT statement for the service in question shall be consistent with the PICS statement made by the manufacturer and will result for this test in one valid BC coding as presented in subclause 11.8.

11.1.2.4.2 Procedure

a) The MS shall be made to initiate a call.

b) If the MS can be configured to send a specific BC, the test is repeated with the MS configured for all possible preferred Bearer Services and Teleservices declared as supported by the MS. The complete coding of the corresponding BC-IE(s) can be found in subclause 11.8.

11.1.2.5 Test requirement

The MS shall send a SETUP message, which shall contain the BC among those declared as supported by the MS. If the MS is configured to send a specific BC, the SETUP message shall contain this particular BC. The BC-IE(s) shall be set according to 3GPP TS 07.01. When an ITC value is set to "unrestricted digital" the MS shall include the corresponding LLC information element.

Where two BCs are contained in the SETUP message, it shall be checked that the combination is allowed, according to 3GPP TS 07.01 and that a Repeat Indicator is also included.