27.21 Advice of Charge (AoC)

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

27.21.1 AoC not supported by SIM

27.21.1.1 Definition

If the ME under test supports Advice of Charge Charging, it shall still look at the capability of the SIM, before responding to any AoCC information from the network.

27.21.1.2 Conformance requirement

1. An MS not supporting 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 not supporting 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 sent within the FACILITY.

3. An MS not supporting 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 sent within the FACILITY.

4. An MS not supporting 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 sent within the FACILITY.

References:

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

27.21.1.3 Test purpose

1. To verify that an MS not supporting AoCC (where the ME does support AoCC but the SIM does not) 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. To verify that an MS not supporting AoCC (where the ME does support AoCC but the SIM does not) 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 sent within the FACILITY.

3. To verify that an MS not supporting AoCC (where the ME does support AoCC but the SIM does not) 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 sent within the FACILITY.

4. To verify that an MS not supporting AoCC (where the ME does support AoCC but the SIM does not) and in the U10 call active state, on receipt of a FACILITY message containing AoCC information, shall ignore and not acknowledge the AoCC information sent within the FACILITY.

27.21.1.4 Method of test

27.21.1.4.1 Initial conditions

The ME shall be installed with a SIM or SIM simulator, with all elementary files coded as for the default SIM, with the exception of:

EFSST (SIM Service Table)

Logically: CHV1 disable function allocated and activated.

Abbreviated dialling numbers allocated and activated.

PLMN selector allocated and activated.

Fixed dialling numbers not activated.

AoC not activated.

Coding:

B1

B2

B3

B4

Value (binary)

xx0x1111

0011xx0x

xxxxxxxx

0000xxxx

The coding of EFSST shall conform with the capabilities of the SIM used.

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

27.21.1.4.2 Procedure

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

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

c) For an MTcall in the U9 state the SS transmits FACILITY containing AoCC information.

d) For an MO call in the U10 state the SS transmits FACILITY containing AoCC information.

27.21.1.5 Test requirement

In all cases, 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.

27.21.2 Maximum frequency of ACM updating

27.21.2.1 Definition

During a call, the ACM shall be updated at the end of every interval. The interval length is the greater of either 5 s or the value given by parameter e2.

27.21.2.2 Conformance requirement

The ACM shall be incremented when the CCM is incremented or once every 5 s, whichever is the longer period.

Reference:

3GPP TS 02.24, subclause 4.3, part h.

27.21.2.3 Test purpose

To verify that the terminal, during a call, increments the ACM every 5 s when e2 is less or equal to 5 s.

27.21.2.4 Method of test

27.21.2.4.1 Initial conditions

The ME shall be connected to the SIM simulator, with all elementary files coded as default with the exception of:

EFSST (SIM Service Table)

Logically: CHV1 disable function allocated and activated.

Abbreviated dialling numbers allocated and activated.

PLMN selector allocated and activated.

Fixed dialling numbers not activated.

AoC allocated and activated.

Coding:

B1

B2

B3

B4

Value (binary)

xx0x1111

0011xx11

xxxxxxxx

0000xxxx

The coding of EFSST shall conform with the capabilities of the SIM used.

EFACM (Accumulated call meter)

Logically: 50 units

EFACMmax (Accumulated call meter maximum)

Logically: 150 units

System Simulator:

1 cell, default parameters, IMSI attach/detach disabled.

Mobile Station:

The MS is in MM-state "idle, updated".

27.21.2.4.2 Procedure

a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.

b) The call is maintained for 90 s, then terminated by the SS. During the call, the SIM-simulator monitors the time intervals between successive INCREMENT commands. As the final INCREMENT command will have occurred as a result of call termination, the time interval calculated since the prior INCREMENT command shall be ignored.

Maximum Duration of Test:

2 minutes.

Expected Sequence:

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a call

2

MS -> SS

CHANNEL REQUEST

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

5

SS -> MS

CM SERVICE ACCEPT

6

MS -> SS

SETUP

7

SS -> MS

CALL PROCEEDING

8

SS -> MS

ASSIGNMENT COMMAND

to a supported channel type

9

MS -> SS

ASSIGNMENT COMPLETE

10

SS -> MS

ALERTING

11

SS -> MS

CONNECT

As default message except contains Facility IE with contents as indicated in i below

Either A or B branch is taken

A12

MS -> SS

CONNECT ACKNOWLEDGE

A13

MS -> SS

FACILITY

As default message except contains Facility IE with contents as indicated in ii below

B12

MS -> SS

FACILITY

As default message except contains Facility IE with contents as indicated in ii below

B13

MS -> SS

CONNECT ACKNOWLEDGE

14

call duration 90 s after CAI information sent by SS,

15

SS -> MS

DISCONNECT

16

MS -> SS

RELEASE

17

SS -> MS

RELEASE COMPLETE

18

SS -> MS

CHANNEL RELEASE

The main signalling link is released.

Specific Message Contents:

i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.

For ASN.1 description see default message contents in subclause 31.6.1.3.

The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:

e-parameters

parameter

1

2

3

4

5

6

7

value

1

1

1

0

0

0

0

Values shown in table are in the format and have units as in 3GPP TS 02.24 subclause 3.

ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.

For ASN.1 description see default message contents in subclause 31.6.1.3.

27.21.2.5 Test requirement

The MS shall, during a call, send INCREMENT commands to the SIM every 5 s.

27.21.3 Call terminated when ACM greater than ACMmax

27.21.3.1 Definition

ACMmax gives the maximum value of ACM, at which the current calls shall be terminated and no further outgoing calls and charged incoming calls may be made (except emergency calls).

27.21.3.2 Conformance requirement

ACM shall be incremented by the value of CCM.

If the ACMmax is valid, and the ACM becomes equal to or exceeds the value of the ACMmax, then all calls in progress, chargeable to the user, shall be terminated by the MS with cause value #68, once the chargeable interval determined by the CAI has elapsed, (except emergency calls).

Reference:

3GPP TS 02.24, subclause 4.3 part h and subclause 4.2.2.

3GPP TS 04.86, subclause 2.3.

27.21.3.3 Test purpose

1. To verify that the ME increments the ACM by the correct number of units, even though this may take ACM above ACMmax.

2. To verify that the ME terminates the call with cause value #68.

27.21.3.4 Method of test

27.21.3.4.1 Initial conditions

The ME shall be connected to a SIM or the SIM simulator, with all elementary files coded as default with the exception of:

EFSST (SIM Service Table)

Logically: CHV1 disable function allocated and activated.

Abbreviated dialling numbers allocated and activated.

PLMN selector allocated and activated.

Fixed dialling numbers not activated.

AoC allocated and activated.

Coding:

B1

B2

B3

B4

Value (Binary)

xx0x1111

0011xx11

xxxxxxxx

0000xxxx

The coding of EFSST shall conform with the capabilities of the SIM used.

EFACM (Accumulated call meter)

Logically: 80 units

EFACMmax (Accumulated call meter maximum)

Logically: 94 units

System Simulator:

1 cell, default parameters, IMSI attach/detach disabled.

Mobile Station:

The MS is in MM-state "idle, updated".

27.21.3.4.2 Procedure

a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.

b) The call is maintained until cleared by the MS (after 30 s) with cause value #68.

c) The contents of ACM are checked.

Maximum Duration of Test:

2 minutes.

Expected Sequence:

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a call

2

MS -> SS

CHANNEL REQUEST

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

5

SS -> MS

CM SERVICE ACCEPT

6

MS -> SS

SETUP

7

SS -> MS

CALL PROCEEDING

8

SS -> MS

ASSIGNMENT COMMAND

to a supported channel type

9

MS -> SS

ASSIGNMENT COMPLETE

10

SS -> MS

ALERTING

11

SS -> MS

CONNECT

As default message except contains Facility IE with contents as indicated in i below

Either A or B branch is taken

A12

MS -> SS

CONNECT ACKNOWLEDGE

A13

MS -> SS

FACILITY

As default message except contains Facility IE with contents as indicated in ii below

B12

MS -> SS

FACILITY

As default message except contains Facility IE with contents as indicated in ii below

B13

MS -> SS

CONNECT ACKNOWLEDGE

14

call duration 30 s after CAI information sent by SS

15

MS -> SS

DISCONNECT

Cause value #68

16

SS -> MS

RELEASE

17

MS -> SS

RELEASE COMPLETE

18

MS -> SS

CHANNEL RELEASE

The main signalling link is released.

Specific Message Contents:

i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.

For ASN.1 description see default message contents in subclause 31.6.1.3.

The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:

e-parameters

parameter

1

2

3

4

5

6

7

value

10

10

1

0

0

0

0

Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.

ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.

For ASN.1 description see default message contents in subclause 31.6.1.3.

27.21.3.5 Test requirement

1) The MS shall terminate the call correctly 30 s after CAI was sent.

2) The value of ACM shall be 100 units.

27.21.4 Response codes of increase command

27.21.4.1 Definition

ACM has a maximum value in terms of coding, and an attempt by the ME to exceed that value by sending an INCREASE command shall result in an error message from the SIM.

27.21.4.2 Conformance requirement

The ME shall perform the increasing procedure, sending the amount to be increased.

The running accumulated charge shall be stored in the ACM of the SIM.

Where this charge cannot be stored in the MS, use of the telecommunications service shall be prevented.

References:

3GPP TS 11.11, subclause 11.5.3; 3GPP TS 02.86, subclauses 2.2.1 and 2.1.

27.21.4.3 Test purpose

To verify that the ME clears a charged call if the SIM indicates that the ACM cannot be increased.

27.21.4.4 Method of test

27.21.4.4.1 Initial conditions

The ME shall be connected to the SIM simulator, with all elementary files coded as default with the exception of:

EFSST (SIM Service Table)

Logically: CHV1 disable function allocated and activated.

Abbreviated dialling numbers allocated and activated.

PLMN selector allocated and activated.

Fixed dialling numbers not activated.

AoC allocated and activated.

Coding:

B1

B2

B3

B4

Value (binary)

xx0x1111

0011xx11

xxxxxxxx

0000xxxx

The coding of EFSST shall conform with the capabilities of the SIM used.

EFACM (Accumulated call meter)

Logically: (Maximum‑10) units

EFACMmax (Accumulated call meter maximum)

Logically: (Maximum‑2) units

System Simulator:

1 cell, default parameters, IMSI attach/detach disabled.

Mobile Station:

The MS is in MM-state "idle, updated".

27.21.4.4.2 Procedure

a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.

b) After an interval has elapsed, the ME increments the ACM. When an INCREASE command is received, the SIM-sim sends back the error "98 50".

c) Conditions are reset to those described in the initial conditions. Steps a) and b) of the test are repeated, except that the error code sent by the SIM simulator at step b) is now "6F xx".

d) Conditions are reset to those described in the initial conditions. Steps a) and b) of the test are repeated, except that the error code sent by the SIM simulator at step b) is now "92 40".

Maximum Duration of Test:

3 minutes.

Expected Sequence:

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a call

2

MS -> SS

CHANNEL REQUEST

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

5

SS -> MS

CM SERVICE ACCEPT

6

MS -> SS

SETUP

7

SS -> MS

CALL PROCEEDING

8

SS -> MS

ASSIGNMENT COMMAND

to a supported channel type

9

MS -> SS

ASSIGNMENT COMPLETE

10

SS -> MS

ALERTING

11

SS -> MS

CONNECT

As default message except contains Facility IE with contents as indicated in i below

Either A or B branch is taken

A12

MS -> SS

CONNECT ACKNOWLEDGE

A13

MS -> SS

FACILITY

As default message except contains Facility IE with contents as indicated in ii below

B12

MS -> SS

FACILITY

As default message except contains Facility IE with contents as indicated in ii below

B13

MS -> SS

CONNECT ACKNOWLEDGE

14

call duration approx 10s after CAI information sent by SS

15

MS -> SS

DISCONNECT

16

SS -> MS

RELEASE

17

MS -> SS

RELEASE COMPLETE

18

MS -> SS

CHANNEL RELEASE

The main signalling link is released.

Specific Message Contents:

i) FACILITY Information Element with Invoke = ForwardChargeInformation component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.

The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:

e-parameters

parameter

1

2

3

4

5

6

7

value

20

10

1

0

0

0

0

Values shown in table are in the format and have units as in 3GPP TS 02.24 subclause 3.

ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.

27.21.4.5 Test requirement

In each of the three cases, as described in steps b), c) and d) of the procedure, the MS shall terminate the call correctly when it receives an indication from the SIM that the ACM cannot be incremented.