11.3 Verification of non-support of services (Advice of Charge Charging (AoCC))

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

11.3.1 Definition

Test procedures (a) and (b) apply to MS which support MT calls.

Test procedure (c) applies to MS which support MO calls.

Test procedure (d) applies to MS which support at least one circuit switched basic service.

11.3.2 Conformance requirement

1. An MS claiming to not support AoCC and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information shall acknowledge the CONNECT message but ignore and not acknowledge the AoCC information sent within the CONNECT.

2. An MS claiming to not support AoCC and in the outgoing call / U4 call delivered state, on receipt of a FACILITY message containing AoCC information shall ignore and not acknowledge the AoCC information contained within the FACILITY.

3. An MS claiming to not support AoCC and in the incoming call / U9 call confirmed state, on receipt of a FACILITY message containing AoCC information shall ignore and not acknowledge the AoCC information contained within the FACILITY.

4. An MS claiming to not support AoCC and in the U10 call active state, on receipt of a FACILITY message containing AoCC information shall ignore and not acknowledge the AoCC information contained within the FACILITY.

3GPP TS 03.86 subclauses 1.2, 1.3, 2.2 and 2.3; 3GPP TS 04.86 clause 2.

11.3.3 Test purpose

1. To verify that an MS claiming to not support AoCC and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information acknowledges the CONNECT message but ignores and does not acknowledge the AoCC information sent within the CONNECT.

2. To verify that an MS claiming to not support AoCC and in the outgoing call / U4 call delivered state, on receipt of a FACILITY message containing AoCC information ignores and does not acknowledge the AoCC information contained within the FACILITY.

3. To verify that an MS claiming to not support AoCC and in the incoming call / U9 call confirmed state, on receipt of a FACILITY message containing AoCC information ignores and does not acknowledge the AoCC information contained within the FACILITY.

4. To verify that an MS claiming to not support AoCC and in the U10 call active state, on receipt of a FACILITY message containing AoCC information ignores and does not acknowledge the AoCC information contained within the FACILITY.

11.3.4 Method of test

11.3.4.1 Initial conditions

The generic call set up procedures are followed up to and including the reception, or transmission, of the ALERTING message by the MS.

Specific PICS statements:

– Support of at least one MT circuit switched basic service (TSPC_AddInfo_MTsvc)

– Support of at least one MO circuit switched basic service (TSPC_AddInfo_MOsvc)

PIXIT Statements:

11.3.4.2 Procedure

a) For an Mobile Originated call in the U4 state the SS transmits CONNECT containing AoCC information.

b) For an Mobile Originated call in the U4 state the SS transmits FACILITY containing AoCC information.

c) For an Mobile Terminated call in the U9 state the SS transmits a FACILITY containing AoCC information.

d) For a call in the U10 state the SS transmits a FACILITY containing AoCC information

11.3.5 Test requirement

The MS shall ignore the AoCC information sent to it in the Facility information elements as part of the CONNECT/FACILITY messages and not send any AoCC information acknowledgement. It shall be checked for 15 s that the MS does not transmit any AoCC information acknowledgement after the receipt of AoCC information.