31.6 Charging supplementary services
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
The following Advice of Charge abbreviations are used in this subclause:
AoC Advice of Charge
AoCC Advice of Charge Charging
AoCI Advice of Charge Information
ACM Accumulated Charge Meter
ACMmax Accumulated Charge Meter Maximum
CCM Current Call Meter
CAI Charge Advice Information
CDUR Chargeable Duration
The following other abbreviations are used:
IE Information Element
FIE Facility Information Element
TCH Traffic CHannel
General on Advice of Charge.
The purpose of these tests is to verify that the MS under test correctly performs procedures related to the AoC supplementary service.
The reasons for these test purposes are:
– One example of a possible use for AoCC is in applications where the subscriber hires out a GSM ME and SIM to a user and bills the user according to the charge stored on the SIM at the end of the hire period. If a mobile station claims to support AoCC but does so incorrectly or not at all, this may cause the subscriber to mischarge the user of the hire phone. Hence an MS claiming to support AoCC must be shown to be reliable in that context.
– Since AoCC offers the use of telecommunication services according to the charge stored independently in the MS, the AoCC service must not be susceptible to fraud at the MS end.
– To ensure that a mobile station not claiming to support AoCC does not respond with a signal to the network indicating that it does. This could cause the network to allow the call to be placed without any charge being inserted on to the SIM.
Mobile originating and terminating speech AoC calls are tested and if supported, Call Hold and Multi-party calls. The type testing of data calls (i.e. those calls with a volume related charging component) will not be specified at the phase 2 stage but will be deferred to phase 2+ since the interaction of AoC with packet services is not yet defined in 3GPP TS 09.06 and 3GPP TS 09.07.
Tests are made on the ME-SIM interface to ensure that call charges are being correctly stored in the ACM field of the SIM in several situations. The AoC ACMmax function is also tested for incoming and outgoing calls.
Basic service verification tests for the AoCC, Call Hold, and Multi-party supplementary services which have direct relevance to the testing of AoC have been added to 3GPP TS 11.10, subclauses 11.3, 11.4 and 11.5 respectively.
31.6.1 Advice of Charge Charging
31.6.1.1 AoCC time related charging / MS originated call
Purpose:
1) To verify that when the MS receives the AoCC parameters in a Facility IE which is contained in the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives the AoCC parameters in a Facility IE which is contained in a CONNECT message and when a TCH has already been assigned, the MS stores the correct value in the ACM field of the SIM.
3) To verify that the when the call has no volume related component the MS ignores non-zero AoCC e5, e6 parameters sent to it.
Conformance Requirement(s):
1) When the MS receives the AoCC parameters in a Facility IE which is contained in a CONNECT message and when a TCH has already been assigned, the MS shall return a FACILITY message containing the acknowledgement within 1 s.
2) When the MS receives the AoCC parameters in a Facility IE which is contained in a CONNECT or FACILITY message and when a TCH has already been assigned, the MS shall store the correct value in the ACM field of the SIM.
3) When the call has no volume related component the MS shall ignore non-zero AoC e5 and e6 parameters sent to it.
Reference(s):
Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86.
Conformance requirement 2: 3GPP TS 02.24.
Conformance requirement 3: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.
The SS sends the DISCONNECT y seconds after sending the CONNECT message containing the CAI. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. The test is repeated for several different sets of e-parameters as defined below.
Maximum Duration of Test:
30 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,…,5.
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 y seconds 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. |
|
19 |
MS |
SIM contents checked (either via MMI or by removing the SIM and using SIM reader). ACM shall have been incremented correctly. |
NOTE: The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
y is set to a constant value of 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
|
k-value |
e-parameter |
CCM Total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
6 |
14 |
1 |
25 |
0 |
0 |
60 |
43 |
43 |
|
2 |
0 |
0 |
1 |
100 |
0 |
0 |
0 |
100 |
143 |
|
3 |
250 |
16 |
2 |
500 |
0 |
0 |
60 |
2 000 |
2 143 |
|
4 |
1 |
1 |
1 |
0 |
10 |
10 |
1 |
89 or 90 |
2 232 or 2 233 |
|
5 |
12,5 |
30 |
1 |
25 |
10 |
10 |
30 |
50 or 62,5 |
2 295, 2 296, 2 282 or 2 283 |
Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.
The ASN.1 description for each e-parameter allows integers in the range 0 to 8191 to be transmitted but some e-parameters have different actual ranges (e.g. e1 can take any value 0..819,1 with 0,1 resolution). The MS knows how to interpret the received parameter (e.g. received e1 refers to 10 times actual e1, see 3GPP TS 04.80 subclause 4.4.3). Therefore e1=12,5 would be sent to the MS as 125. The MS knows the value sent is 10 times the "real" e1 and hence interprets the value as 12,5.
The non-zero e5 and e6 values for the k=4 and k=5 execution of the test are to check that the MS ignores the volume related parameters when carrying out time only related charging.
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.4.
31.6.1.2 AoCC time related charging / MS terminated call
Purpose:
1) To verify that when the MS receives certain AoCC e-parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives the AoCC parameters in a Facility IE which is contained in a FACILITY message and when a TCH has already been assigned, the MS stores the correct value in the ACM field of the SIM.
Conformance Requirement(s):
1) When the MS receives the AoCC parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS shall return a Facility message containing the acknowledgement within 1 s.
2) When the MS receives the AoCC parameters in a Facility IE which is contained in a FACILITY message and when a TCH has already been assigned, the MS shall store the correct value in the ACM field of the SIM.
Reference(s):
Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86.
Conformance requirement 2: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The SS is made to initiate a call. The call is established and certain AoCC e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCC acknowledgement within 1 s of the FACILITY message. It is an implementation option whether the AoCC e-parameters and the AoCC acknowledge are sent before or after the CONNECT ACKNOWLEDGE.
The SS sends the DISCONNECT y seconds after sending the FACILITY message. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. The test is repeated for several different sets of e-parameters as defined below.
Maximum Duration of Test:
30 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,…,5.
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
1 |
SS |
The SS is made to initiate a call |
|
|
2 |
SS -> MS |
PAGING REQUEST |
|
|
3 |
MS -> SS |
CHANNEL REQUEST |
|
|
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
5 |
MS -> SS |
PAGING RESPONSE |
|
|
6 |
SS -> MS |
SETUP |
|
|
7 |
MS -> SS |
CALL CONFIRMED |
|
|
8 |
SS -> MS |
ASSIGNMENT COMMAND |
to a supported channel type |
|
9 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
10 |
MS -> SS |
ALERTING |
|
|
11 |
MS -> SS |
CONNECT |
|
|
12 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
Either A or B branch is taken |
|||
|
A13 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
|
A14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B14 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
|
15 |
call duration y seconds after CAI information sent by SS |
||
|
16 |
SS -> MS |
DISCONNECT |
|
|
17 |
MS -> SS |
RELEASE |
|
|
18 |
SS -> MS |
RELEASE COMPLETE |
|
|
19 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
20 |
MS |
SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. |
NOTE: The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
y is set to a constant value of 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
2 |
0 |
0 |
1 |
100 |
0 |
0 |
0 |
100 |
100 |
|
3 |
6 |
14 |
1 |
25 |
0 |
0 |
60 |
43 |
143 |
|
4 |
1 |
1 |
1 |
0 |
0 |
0 |
1 |
89 or 90 |
233 or 232 |
|
5 |
12,5 |
30 |
1 |
25 |
0 |
0 |
30 |
50 or 62,5 |
296, 295, 282 or 283 |
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.4.
31.6.1.3 AoCC volume related charging / MS originated call
Future addition at GSM Phase 2+ stage.
31.6.1.4 AoCC volume related charging / MS terminated call
Future addition at GSM Phase 2+ stage.
31.6.1.5 Change in charging information during a call
Purpose:
1) To verify that when the MS receives new AoCC parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information.
Conformance Requirement(s):
1) When the MS receives new AoCC parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS shall return a FACILITY message containing the acknowledgement within 1 s.
2) When the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information.
Reference(s):
Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86.
Conformance requirement 2: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc)
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in a FACILITY message sent after the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of the FACILITY message. x seconds after sending the original CAI, new (and different) e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCC acknowledge within 1 s of the FACILITY message.
The SS sends the DISCONNECT y seconds after sending the first CAI in the FACILITY message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and the times for the two parts of the call.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 |
|
|
Either A, B or C branch is taken |
|||
|
A12 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
A13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
A14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
B13 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
B14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
C12 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
C13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
C14 |
MS-> SS |
CONNECT ACKNOWLEDGE |
|
|
Second CAI sent x sec after first CAI |
|||
|
15 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in iii below |
|
16 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below New CAI held in abeyance until CDUR has timed out present e2 value |
|
17 |
Call duration y seconds after first CAI information sent by SS |
||
|
18 |
SS -> MS |
DISCONNECT |
|
|
19 |
MS -> SS |
RELEASE |
|
|
20 |
SS -> MS |
RELEASE COMPLETE |
|
|
21 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
22 |
MS |
SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly |
NOTE The values of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x, y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as defined below:
|
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||
|
10 |
28 |
1 |
10 |
0 |
0 |
60 |
(30) |
(30) |
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.4.
iii) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x is set to a constant value of 80 s.
y is set to a constant value of 180 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||
|
10 |
14 |
1 |
5 |
0 |
0 |
60 |
65 |
65 |
Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.
31.6.1.6 Different formats of charging information
Purpose:
1) To verify that when the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated is the same as that when the same e-parameters are completely omitted from the Facility IE.
2) To verify the operation of a shortened channel release procedure where the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message.
Conformance Requirement(s):
1) When the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated shall be the same as that when the same e-parameters are completely omitted from the Facility IE.
2) The channel shall be correctly released when a shortened channel release procedure is used – the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message.
Reference(s):
Conformance requirement 1: 3GPP TS 02.24.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
Part 1:
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in a FACILITY message sent before the CONNECT message.
The SS sends the DISCONNECT y seconds after sending the FACILITY message containing the e-parameters. The MS shall have stored the correct amount on the SIM according to the e-parameters sent.
Part 2:
Part 1 is repeated twice with the e-parameters that were set to zero above now omitted completely from the Facility IE. The shortened release procedures are used. The MS shall have stored the correct amount on the SIM.
The results of parts 1 and 2 are compared. The value for the charge calculated by the MS shall be identical for parts 1 and 2.
Maximum Duration of Test:
20 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,..3.
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
Either A, B or C branch is taken |
|||
|
A12 |
SS -> MS |
CONNECT |
|
|
A13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
A14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B12 |
SS -> MS |
CONNECT |
|
|
B13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
C12 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
C13 |
SS -> MS |
CONNECT |
|
|
C14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
15 |
call duration y seconds after CAI information sent by SS |
||
|
Branch D, E and F shall be taken for k= 1,2 and 3 respectively |
|||
|
D16 |
SS -> MS |
DISCONNECT |
|
|
D17 |
MS -> SS |
RELEASE |
|
|
D18 |
SS -> MS |
RELEASE COMPLETE |
|
|
D19 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
E16 |
SS -> MS |
RELEASE COMPLETE |
Shortened channel release procedure |
|
E17 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
F16 |
SS -> MS |
CHANNEL RELEASE |
|
|
20 |
MS |
SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. |
NOTE The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
y is set to a constant value of 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
10 |
40 |
1 |
0 |
0 |
0 |
0 |
20 |
20 |
|
2 |
10 |
40 |
1 |
———omitted——— |
20 |
40 |
|||
|
3 |
10 |
40 |
1 |
———omitted——— |
20 |
60 |
|||
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.4.
31.6.1.7 AoCC on a Call Hold call
Purpose:
1) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCC acknowledgement within 1 s of transmission of each set of e-parameters.
2) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM records the sum of all the charges for the services currently being used and hence that the ME inserts the correct charge in the ACM field of the SIM.
Conformance Requirement(s)
1) When the MS invokes a Call Hold call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCC acknowledgement within 1 s of receiving each set of e-parameters.
2) When the MS invokes a Call Hold call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM shall record the sum of all the charges for the services currently being used and hence the ME shall insert the correct charge in the ACM field of the SIM.
Reference(s):
Conformance requirement 1: 3GPP TS 04.13.
Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of transmission of the CONNECT message.
The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call.
The MS is made to initiate a second call (call C). The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement in a FACILITY message within 1 s of transmission of the CONNECT message.
The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT/FACILITY message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT/FACILITY message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and call times x and y.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 D or E branch is taken |
|||
|
D12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
D13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E12 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
14 |
MS |
The MS is made to initiate a second call, and the first call is placed on hold. DTMF signalling may occur, when MMI keys are depressed |
|
|
15 |
MS -> SS |
HOLD |
|
|
16 |
SS -> MS |
HOLD ACKNOWLEDGE |
|
|
17 |
MS -> SS |
CM SERVICE REQUEST |
|
|
18 |
SS -> MS |
CM SERVICE ACCEPT |
|
|
19 |
MS -> SS |
SETUP |
TI arbitrary but different from existing TI |
|
20 |
SS -> MS |
CALL PROCEEDING |
|
|
21 |
SS -> MS |
ALERTING |
|
|
22 |
SS -> MS |
CONNECT |
As default message except contains Facility IE with contents as indicated in i below |
|
Either F or G branch is taken |
|||
|
F23 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
F24 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G23 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G24 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
25 |
Call durations x and y seconds after respective CAI information sent by SS |
||
|
Branch H and I branch are taken, the sequence depending on the durations x and y |
|||
|
For call C |
|||
|
H26 |
SS -> MS |
DISCONNECT |
y seconds after call C CAI sent |
|
H27 |
MS -> SS |
RELEASE |
|
|
H28 |
SS -> MS |
RELEASE COMPLETE |
|
|
For call B |
|||
|
I26 |
SS -> MS |
DISCONNECT |
x seconds after call B CAI sent |
|
I27 |
MS -> SS |
RELEASE |
|
|
I28 |
SS -> MS |
RELEASE COMPLETE |
|
|
29 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released |
|
30 |
MS |
SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. |
NOTE The value of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x set to 180 s, y is set to 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
Call |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
B(time x) |
7 |
40 |
1 |
0 |
0 |
0 |
0 |
||
|
C(time y) |
13 |
40 |
1 |
0 |
0 |
0 |
0 |
54 |
54 |
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.4.
31.6.1.8 AoCC on a Multi-party call
Purpose:
1) To verify that when the MS invokes a Multi-party call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCC acknowledgement within 1 s of transmission of each set of e-parameters.
2) To verify that when the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM records the sum of all the charges for the services currently being used and hence the ME inserts the correct charge in the ACM field of the SIM.
Conformance Requirement(s):
1) When the MS invokes a Multi-party call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCC acknowledgement within 1 s of receiving each set of e-parameters.
2) When the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM shall record the sum of all the charges for the services currently being used and hence the ME shall insert the correct charge in the ACM field of the SIM.
Reference(s):
Conformance requirement 1: 3GPP TS 04.13.
Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of transmission of the CONNECT message.
The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call.
The MS is made to initiate a second call (call C). The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of transmission of the CONNECT message.
The MS invokes the multi-party service by sending a FACILITY message to the SS containing the BuildMPTY request.
The SS accepts the request and connects the MS with the other existing connections (active call C and held call B) and confirms with a FACILITY message.
The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and call times x and y.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|---|---|---|---|
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 D or E branch is taken |
|||
|
D12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
D13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E12 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
14 |
MS -> SS |
HOLD |
The MS is made to initiate a second call and the first call (call B) is placed on hold. DTMF signalling may occur, when MMI keys are depressed |
|
15 |
MS->SS |
HOLD |
|
|
16 |
SS -> MS |
HOLD ACKNOWLEDGE |
|
|
17 |
MS -> SS |
CM SERVICE REQUEST |
|
|
18 |
SS -> MS |
CM SERVICE ACCEPT |
|
|
19 |
MS -> SS |
SETUP |
TI arbitrary but different from existing TI |
|
20 |
SS -> MS |
CALL PROCEEDING |
|
|
21 |
SS -> MS |
ALERTING |
|
|
22 |
SS -> MS |
CONNECT |
As default message except contains Facility IE with contents as indicated in i below |
|
Either F or G branch is taken |
|||
|
F23 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
F24 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G23 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G24 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
The MS is made to build a multi-party call. DTMF signalling may occur, when MMI keys are depressed |
|||
|
25 |
MS -> SS |
FACILITY (TI A-B/A-C) |
As default message except contains Facility IE with contents as indicated in iii below |
|
26 |
SS -> MS |
FACILITY (TI A-B/A-C) |
As default message except contains Facility IE with contents as indicated in iv, below |
|
27 |
Call durations x and y seconds after respective CAI information sent by SS |
||
|
Branch H and branch I are taken, the sequence depending on the durations x and y |
|||
|
For call C |
|||
|
H28 |
SS -> MS |
DISCONNECT |
y seconds after call C CAI sent |
|
H29 |
MS -> SS |
RELEASE |
|
|
H30 |
SS -> MS |
RELEASE COMPLETE |
|
|
For call B |
|||
|
I28 |
SS -> MS |
DISCONNECT |
x seconds after call B CAI sent |
|
I29 |
MS -> SS |
RELEASE |
|
|
I30 |
SS -> MS |
RELEASE COMPLETE |
|
|
31 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
32 |
MS |
SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. |
NOTE: A-B/A-C indicates a choice. the transaction identifier (TI) used must be that of the active call or the held call (ref. 3GPP TS 04.84).
The values of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x set to 180 s, y set to 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
Call |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
B(time x) |
19 |
40 |
1 |
0 |
0 |
0 |
0 |
||
|
C(time y) |
29 |
40 |
1 |
0 |
0 |
0 |
0 |
134 |
134 |
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.4.
iii) FACILITY Information Element with Invoke = BuildMPTY component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
The following abbreviations are used in the descriptions below:
U Universal tag class.
CS Context Specific tag class.
P Primitive tag form.
C Constructed tag form.
FIE Facility Information Element.
|
Contents Facility IE Identifier |
Value/remark As 3GPP TS 04.80 |
Coding 00011100 |
|
Length of FIE contents |
8 |
00001000 |
|
Component type tag |
CS/C/tag=1 |
10100001 |
|
Component length |
6 |
00000110 |
|
Invoke ID tag |
U/P/tag=2 |
00000010 |
|
Invoke ID length |
1 |
00000001 |
|
Invoke ID |
Arbitrary |
(00000000) |
|
Op-Code tag |
From 3GPP TS 04.80 |
00000010 |
|
Op-Code length |
1 |
00000001 |
|
Op-Code |
Build Multi-party |
00000001 |
ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
|
Contents Facility IE Identifier |
Value/remark As 3GPP TS 04.80 |
Coding 00111100 |
|
Length of FIE contents |
5 |
00001001 |
|
Component type tag |
CS/C/tag=2 |
10100010 |
|
Component length |
3 |
00000011 |
|
Invoke ID tag |
U/P/Integer |
00000010 |
|
Invoke ID length |
1 |
00000001 |
|
Invoke ID |
Same as used as |
(00000000) |
31.6.2 Charge Storage
31.6.2.1 Removal of SIM during an active call
Purpose:
1) To verify that when the SIM is removed from the ME during an active AoCC call the ME immediately terminates the call.
2) To verify that when the SIM is removed during an active AoCC call the ME has written the total charge up to that point in the call to the ACM field of the SIM.
Conformance Requirement(s):
1) When the SIM is removed from the ME during an active AoCC call the ME shall immediately terminate the call.
2) When the SIM is removed during an active AoCC call midway through an AoC charging time interval (e7 or e2) the ME shall have written the total charge up to the point in the call where the charging time interval last expired to the ACM field of the SIM.
Reference(s):
Conformance requirement 1: 3GPP TS 02.17.
Conformance requirement 1: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
This test is only performed if it is possible to remove SIM without disconnecting the power supply. If the battery pack must be removed to get at the SIM see subclause 31.6.2.2.
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE.
If possible, without removing the power supply, the SIM is removed from the ME y seconds after the SS sends the CAI in the CONNECT/FACILITY message. The call shall be terminated immediately by the MS and the MS shall have stored the correct amount on the SIM according to the e-parameters sent.
Maximum Duration of Test:
5 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 |
SIM removed y seconds after CAI information sent by SS. |
||
|
Either C, D, E or F branch is taken |
|||
|
C15 |
MS -> SS |
DISCONNECT |
|
|
C16 |
SS -> MS |
RELEASE |
|
|
C17 |
MS -> SS |
RELEASE COMPLETE |
|
|
C18 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
D15 |
MS -> SS |
RELEASE COMPLETE |
|
|
D16 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
E15 |
MS -> SS |
Layer 2 DISC |
|
|
E16 |
SS -> MS |
UA |
|
|
F15 |
No further messages are sent |
||
|
19 |
SIM contents checked (by removing the SIM and using SIM reader). ACM shall have been incremented correctly. |
NOTE: The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
The SIM is removed after approximately y=90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
10 |
55 |
1 |
10 |
0 |
0 |
10 |
30 |
30 |
|
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.4.
31.6.2.2 Interruption of power supply during an active call
Purpose:
To verify that when the power supply of the MS is removed during an active AoCC call the ME has written the total charge up to that point in the call to the ACM field of the SIM.
Conformance Requirement(s):
When the power supply of the MS is removed during an active AoCC call midway through an AoC charging time interval (e7 or e2) the ME shall have written the total charge up to the point in the call where the charging time interval last expired to the ACM field of the SIM.
Reference(s):
Conformance requirement 1: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of removing power supply.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is switched off.
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE.
The ME power is switched off by pressing power button on MMI during the active call. The call shall be terminated immediately and the MS shall have stored the correct amount on the SIM according to the e-parameters sent.
The test is repeated for ME power being lost by removal of battery pack. The call shall be terminated immediately and the MS shall have stored the correct amount on the SIM according to the e-parameters sent.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,2.
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 |
ME power interrupted y seconds after CAI information sent by SS by: MMI power switch (for k=1) Removing battery pack (for k=2) Depending on the value of k C or D branch is taken |
||
|
15 |
SIM contents checked (by removing the SIM and using SIM reader). ACM shall have been incremented correctly. |
NOTE: The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
The ME power is removed after approximately y=90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
10 |
55 |
1 |
10 |
0 |
0 |
10 |
30 |
30 |
|
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.4.
31.6.2.3 MS going out of coverage during an active AoCC call
NOTE: At present the core recommendations for AoCC in the case where the radio link is lost during an active call are vague. Does the mobile go on charging for a fixed period after radio link loss and continue as usual if radio link reestablishment occurs, or does charging stop? Input from people involved in charging for GSM is required.
Hence this test will be enhanced in the future when the requirements become clearer.
Purpose:
To verify that when the MS goes out of radio coverage area and an active call is dropped the ME has written the total charge up to that point in the call to the ACM field of the SIM.
Conformance Requirement(s):
When the MS goes out of radio coverage area during an active AoCC call midway through an AoC charging time interval (e7 or e2) and the call is dropped the ME shall have written the total charge up to the point in the call where the charging time interval last expired to the ACM field of the SIM.
Reference(s):
Conformance requirement 1: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE.
The cell simulated by the system simulator is then switched off to model the MS losing radio coverage. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. [What happens on call reestablishment?]
Maximum Duration of Test:
5 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 |
SS cell switched off y seconds after CAI information sent by SS Failure of radio path, end of call (CEND) occurs and MS stops charging (ref. 3GPP TS 02.24 sec 2) |
||
|
15 |
SIM contents checked (either via MMI or by removing the SIM and using SIM reader). ACM shall have been incremented correctly. |
NOTE: The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
The cell being simulated by the SS is switched off after approximately y=90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
10 |
55 |
1 |
10 |
0 |
0 |
10 |
30 |
30 |
|
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.4.
31.6.2.4 ACMmax operation / Mobile Originating
Purpose:
1) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any outgoing calls in progress for which a non-zero CAI exists are terminated by the ME, with cause value #68 once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user.
2) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of non-emergency calls is inhibited.
3) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of emergency calls is uninhibited.
Conformance Requirement(s):
1) When the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any outgoing calls in progress for which a non-zero CAI exists shall be terminated by the ME with cause value #68, once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user.
2) When the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of further non-emergency calls shall be inhibited.
3) When the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of emergency calls shall be uninhibited.
Reference(s):
Conformance requirement 1: 3GPP TS 02.24,
3GPP TS 04.86 subclause 2.3.
Conformance requirement 2: 3GPP TS 02.24.
Conformance requirement 3: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Type of user indication when ACMmax exceeded.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
PIN 2 is entered into the MS allowing modification of both the ACM and ACMmax fields on the SIM. The ACM is reset to zero and the ACMmax is set to 2 units.
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCC non-zero e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE.
After the ACM has been incremented to 2 units (60 s) the call shall be terminated by the MS once an additional chargeable interval of 30 s has elapsed, and an indication given to the user. The call duration is recorded and the ACM is checked to ensure it has been incremented to 2 units.
The MS is then made to attempt to originate an ordinary call to the MS for which a non-zero CAI exists for the calling party and shall be unsuccessful. The MS shall not send a CHANNEL REQUEST for that call.
The MS is then made to attempt to originate an emergency call and shall be successful.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM (it shall be zero) |
||
|
For k= 1 |
|||
|
A1 |
MS |
The MS is made to initiate an ordinary call |
|
|
A2 |
MS -> SS |
CHANNEL REQUEST |
|
|
A3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
A4 |
MS -> SS |
CM SERVICE REQUEST |
|
|
A5 |
SS -> MS |
CM SERVICE ACCEPT |
|
|
A6 |
MS -> SS |
SETUP |
|
|
A7 |
SS -> MS |
CALL PROCEEDING |
|
|
A8 |
SS -> MS |
ASSIGNMENT COMMAND |
to a supported channel type |
|
A9 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
A10 |
SS -> MS |
ALERTING |
|
|
A11 |
SS -> MS |
CONNECT |
As default message except contains Facility IE with contents as indicated in I below |
|
For k = 3 |
|||
|
B1 |
MS |
The MS is made to initiate an emergency call |
|
|
B2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is emergency call establishment |
|
B3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
B4 |
MS -> SS |
CM SERVICE REQUEST |
CM service type IE indicates "emergency call establishment" |
|
B5 |
SS -> MS |
CM SERVICE ACCEPT |
|
|
B6 |
MS -> SS |
EMERGENCY SETUP |
|
|
B7 |
SS -> MS |
CALL PROCEEDING |
|
|
B8 |
SS -> MS |
ASSIGNMENT COMMAND |
to a supported channel type |
|
B9 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
B10 |
SS -> MS |
ALERTING |
|
|
B11 |
SS -> MS |
CONNECT |
As default message except contains Facility IE with contents as indicated in i below For k=1 or 3 either branch C or D is taken |
|
C12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
C13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
D12 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
D13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
For k=1 |
|||
|
L14 |
Record call duration, x seconds, after CAI information sent by SS until call is terminated by the ME |
||
|
L15 |
MS -> SS |
DISCONNECT |
Cause value #68 |
|
L16 |
SS -> MS |
RELEASE |
|
|
L17 |
MS -> SS |
RELEASE COMPLETE |
|
|
L18 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
L19 |
ACM checked (shall be 2 units) |
||
|
For k=3 |
|||
|
M14 |
Call duration y seconds after CAI information sent by SS |
||
|
M15 |
MS -> SS |
DISCONNECT |
|
|
M16 |
SS -> MS |
RELEASE |
|
|
M17 |
MS -> SS |
RELEASE COMPLETE |
|
|
M18 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
M19 |
ACM checked (shall be 2 units) |
k=1 – Non zero CAI call attempted by MS and should succeed.
k=2 – Non zero CAI call attempted by MS and should fail.
k=3 – Emergency call attempted by MS and should succeed.
NOTE: The values of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x shall be 90 ± 2 s.
y shall be set to 120 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
1 |
30 |
1 |
0 |
0 |
0 |
0 |
2 |
2 |
|
2 |
1 |
30 |
1 |
0 |
0 |
0 |
0 |
0 |
2 |
|
3 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
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.4.
31.6.2.5 ACMmax operation / Mobile Terminating
Purpose:
1) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any mobile terminating calls in progress for which a non-zero CAI exists are terminated by the ME with cause value #68, once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user.
2) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, and an incoming call is received for which subsequently a non-zero CAI is received, then the call is terminated by the ME using cause value #68 with an appropriate indication given to the user.
3) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the receiving of calls for which the CAI is zero is uninhibited.
Conformance Requirement(s):
1) When the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any mobile terminating calls in progress for which a non-zero CAI exists shall be terminated by the ME with cause value #68, once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user.
2) When the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, and an incoming call is received for which subsequently a non-zero CAI is received, the call shall be terminated by the ME using cause value #68 with an appropriate indication given to the user.
3) When the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the receiving of calls for which the CAI is zero shall be uninhibited.
Reference(s):
Conformance requirement 1: 3GPP TS 02.24,
3GPP TS 04.86 subclause 2.3.
Conformance requirement 2: 3GPP TS 02.24,
3GPP TS 04.86 subclause 2.3.
Conformance requirement 2: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Method of reading ACM from the SIM via the ME.
– Type of user indication when ACMmax exceeded.
– Support for active state of the call control protocol (U10).
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
PIN 2 is entered into the MS allowing modification of both the ACM and ACMmax fields on the SIM. The ACM is reset to zero and the ACMmax is set to 2 units.
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The SS is made to initiate a call. The call is established with certain non-zero AoCC e-parameters sent in a Facility IE contained in a FACILITY message sent before the CONNECT message. It is an implementation option whether the AoCC e-parameters and AoCC acknowledge are sent before or after the CONNECT ACKNOWLEDGE.
After the ACM has been incremented to 2 units (60s) the call shall be terminated by the MS once an additional chargeable interval of 30s has elapsed and an indication given to the user. The ACM shall be checked to ensure that it has been incremented to 2 units.
The SS is then made to attempt to make an ordinary call to the MS for which a non-zero CAI exists for the called party and shall be unsuccessful. The MS shall terminate the call with a DISCONNECT message.
The SS is then made to attempt to make an ordinary call to the MS for which a zero CAI exists for the called party and shall be successful.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,…,3..
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
1 |
SS |
The SS is made to initiate a call |
|
|
2 |
SS -> MS |
PAGING REQUEST |
|
|
3 |
MS -> SS |
CHANNEL REQUEST |
|
|
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
5 |
MS -> SS |
PAGING RESPONSE |
|
|
6 |
SS -> MS |
SETUP |
|
|
7 |
MS -> SS |
CALL CONFIRMED |
|
|
8 |
SS -> MS |
ASSIGNMENT COMMAND |
to a supported channel type |
|
9 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
10 |
MS -> SS |
ALERTING |
|
|
11 |
MS -> SS |
CONNECT |
|
|
12 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
|
For k=1 or 3 branch A is taken |
|||
|
A13 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
A14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
For k=2 branch B, and then either branch C, D or E is taken |
|||
|
B13 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
C13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
C14 |
MS -> SS |
DISCONNECT |
MS terminates call with cause value #68 |
|
D13 |
MS -> SS |
DISCONNECT |
MS terminates call with cause value #68 |
|
D14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E13 |
MS -> SS |
DISCONNECT |
MS terminates call with cause value #68. DISCONNECT may or may not contain Facility IE with contents as indicated in ii below |
|
For k= 1, 2 and 3, F, G and branch shall be taken respectively |
|||
|
For k=1 |
|||
|
F15 |
Record call duration, x seconds, after CAI information sent by SS until call is terminated by the ME |
||
|
F16 |
MS -> SS |
DISCONNECT |
MS terminates call with cause value #68 |
|
F17 |
SS -> MS |
RELEASE |
|
|
F18 |
MS -> SS |
RELEASE COMPLETE |
|
|
F19 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
For k=2 |
|||
|
G15 |
SS -> MS |
RELEASE |
|
|
G16 |
MS -> SS |
RELEASE COMPLETE |
RELEASE COMPLETE may or may not contain Facility IE with contents as indicated in ii below |
|
G17 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
For k=3 |
|||
|
H15 |
Call duration y seconds after CAI information sent by SS |
||
|
H16 |
MS -> SS |
DISCONNECT |
MS terminates call |
|
H17 |
SS -> MS |
RELEASE |
|
|
H18 |
MS -> SS |
RELEASE COMPLETE |
|
|
H19 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
20 |
ACM checked (should be 2 units) |
k=1 – Non zero CAI call attempted to MS and should succeed.
k=2 – Non zero CAI call attempted to MS and should fail.
k=3 – Zero CAI call attempted to MS and should succeed.
NOTE: The values of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x shall be 90 ± 2 s.
y shall be set to 120 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
1 |
30 |
1 |
0 |
0 |
0 |
0 |
2 |
2 |
|
2 |
1 |
30 |
1 |
0 |
0 |
0 |
0 |
0 |
2 |
|
3 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
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.4.
31.6.3 Advice of Charge Information
31.6.3.1 AoCI time related charging / MS originated call
Purpose:
1) To verify that when the MS receives the AoCI parameters in a Facility IE which is contained in the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that the when the call has no volume related component the MS ignores non-zero AoCI e5, e6 parameters sent to it.
Conformance Requirement(s):
1) When the MS receives the AoCI parameters in a Facility IE which is contained in a CONNECT message and when a TCH has already been assigned, the MS shall return a FACILITY message containing the acknowledgement within 1 s.
2) When the call has no volume related component the MS shall ignore non-zero AoC e5 and e6 parameters sent to it.
Reference(s):
Conformance requirement 1: 3GPP TS 03.86,
3GPP TS 04.13,
3GPP TS 04.86.
Conformance requirement 2: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Support for active state of the call control protocol (U10).
– MMI method of reading the AoCI information.
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of the CONNECT message. It is an implementation option whether the AoCI acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE.
The SS sends the DISCONNECT y seconds after sending the CONNECT message containing the CAI. The test is repeated for several different sets of e-parameters as defined below.
Maximum Duration of Test:
30 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,…,5.
|
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 y seconds 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. |
|
19 |
MS |
MS display is checked to determine whether the correct call charge has been indicated |
NOTE: The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
y is set to a constant value of 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
6 |
14 |
1 |
25 |
0 |
0 |
60 |
43 |
43 |
|
2 |
0 |
0 |
1 |
100 |
0 |
0 |
0 |
100 |
143 |
|
3 |
250 |
16 |
2 |
500 |
0 |
0 |
60 |
2 000 |
2 143 |
|
4 |
1 |
1 |
1 |
0 |
10 |
10 |
1 |
89 or 90 |
2 232 or 2 233 |
|
5 |
12,5 |
30 |
1 |
25 |
10 |
10 |
30 |
50 or 62,5 |
2 295, 2 296, |
Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.
The ASN.1 description for each e-parameter allows integers in the range 0 to 8 191 to be transmitted but some e-parameters have different actual ranges (e.g. e1 can take any value 0..819,1 with 0,1 resolution). The MS knows how to interpret the received parameter (e.g. received e1 refers to 10 times actual e1, see 3GPP TS 04.80 subclause 4.4.3). Therefore e1=12,5 would be sent to the MS as 125. The MS knows the value sent is 10 times the "real" e1 and hence interprets the value as 12,5.
The non-zero e5 and e6 values for the k=4 and k=5 execution of the test are to check that the MS ignores the volume related parameters when carrying out time only related charging.
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.4.
31.6.3.2 AoCI time related charging / MS terminated call
Purpose:
1) To verify that when the MS receives certain AoCI e-parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
Conformance Requirement(s):
1) When the MS receives the AoCI parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS shall return a Facility message containing the acknowledgement within 1 s.
Reference(s):
Conformance requirement 1: 3GPP TS 03.86,
3GPP TS 04.13,
3GPP TS 04.86.
Conformance requirement 2: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Support for active state of the call control protocol (U10).
– MMI method of reading the AoCI information.
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The SS is made to initiate a call. The call is established and certain AoCI e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCI acknowledgement within 1 s of the FACILITY message. It is an implementation option whether the AoCI e-parameters and the AoCI acknowledge are sent before or after the CONNECT ACKNOWLEDGE.
The SS sends the DISCONNECT y seconds after sending the FACILITY message. The test is repeated for several different sets of e-parameters as defined below.
Maximum Duration of Test:
30 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,…,5.
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
1 |
SS |
The SS is made to initiate a call |
|
|
2 |
SS -> MS |
PAGING REQUEST |
|
|
3 |
MS -> SS |
CHANNEL REQUEST |
|
|
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
5 |
MS -> SS |
PAGING RESPONSE |
|
|
6 |
SS -> MS |
SETUP |
|
|
7 |
MS -> SS |
CALL CONFIRMED |
|
|
8 |
SS -> MS |
ASSIGNMENT COMMAND |
to a supported channel type |
|
9 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
10 |
MS -> SS |
ALERTING |
|
|
11 |
MS -> SS |
CONNECT |
|
|
12 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
Either A or B branch is taken |
|||
|
A13 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
|
A14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B14 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
|
15 |
call duration y seconds after CAI information sent by SS |
||
|
16 |
SS -> MS |
DISCONNECT |
|
|
17 |
MS -> SS |
RELEASE |
|
|
18 |
SS -> MS |
RELEASE COMPLETE |
|
|
19 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
20 |
MS |
MS display is checked to determine whether the correct call charge has been indicated |
NOTE: The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
y is set to a constant value of 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
2 |
0 |
0 |
1 |
100 |
0 |
0 |
0 |
100 |
100 |
|
3 |
6 |
14 |
1 |
25 |
0 |
0 |
60 |
43 |
143 |
|
4 |
1 |
1 |
1 |
0 |
0 |
0 |
1 |
89 or 90 |
233 or 232 |
|
5 |
12,5 |
30 |
1 |
25 |
0 |
0 |
30 |
50 or 62,5 |
296, 295, |
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.4.
31.6.3.3 AoCI volume related charging / MS originated call
Future addition at GSM Phase 2+ stage.
31.6.3.4 AoCI volume related charging / MS terminated call
Future addition at GSM Phase 2+ stage.
31.6.3.5 Change in charging information during a call
Purpose:
1) To verify that when the MS receives new AoCI parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information.
Conformance Requirement(s):
1) When the MS receives new AoCI parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS shall return a FACILITY message containing the acknowledgement within 1 s.
2) When the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information.
Reference(s):
Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86.
Conformance requirement 2: 3GPP TS 02.24.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Support for active state of the call control protocol (U10).
– MMI method of reading the AoCI information.
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in a FACILITY message sent after the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of the FACILITY message. x seconds after sending the original CAI, new (and different) e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCI acknowledge within 1 s of the FACILITY message.
The SS sends the DISCONNECT y seconds after sending the first CAI in the FACILITY message.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 |
|
|
Either A, B or C branch is taken |
|||
|
A12 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
A13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
A14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
B13 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
B14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
C12 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
C13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
C14 |
MS-> SS |
CONNECT ACKNOWLEDGE |
|
|
Second CAI sent x sec after first CAI |
|||
|
15 |
SS -> MS |
FACILITY |
As default message except contains Facility IE with contents as indicated in iii below |
|
16 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below New CAI held in abeyance until CDUR has timed out present e2 value |
|
17 |
Call duration y seconds after first CAI information sent by SS |
||
|
18 |
SS -> MS |
DISCONNECT |
|
|
19 |
MS -> SS |
RELEASE |
|
|
20 |
SS -> MS |
RELEASE COMPLETE |
|
|
21 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
22 |
MS |
MS display is checked to determine whether the correct call charge has been indicated |
NOTE The values of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x, y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set as defined below:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
10 |
28 |
1 |
10 |
0 |
0 |
60 |
(30) |
(30) |
|
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.4.
iii) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x is set to a constant value of 80 s.
y is set to a constant value of 180 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
e-parameter |
CCM total |
Step 0 ACM |
|||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
10 |
14 |
1 |
5 |
0 |
0 |
60 |
65 |
65 |
|
Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.
31.6.3.6 Different formats of charging information
Purpose:
1) To verify that when the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated is the same as that when the same e-parameters are completely omitted from the Facility IE.
2) To verify the operation of a shortened channel release procedure where the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message.
Conformance Requirement(s):
1) When the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated shall be the same as that when the same e-parameters are completely omitted from the Facility IE.
2) The channel shall be correctly released when a shortened channel release procedure is used – the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message.
Reference(s):
Conformance requirement 1: 3GPP TS 02.24.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Support for active state of the call control protocol (U10).
– MMI method of reading the AoCI information.
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
Part 1:
The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in a FACILITY message sent before the CONNECT message.
The SS sends the DISCONNECT y seconds after sending the FACILITY message containing the e-parameters. The MS shall have stored the correct amount on the SIM according to the e-parameters sent.
Part 2:
Part 1 is repeated twice with the e-parameters that were set to zero above now omitted completely from the Facility IE. The shortened release procedures are used. The MS shall have stored the correct amount on the SIM.
The results of parts 1 and 2 are compared. The value for the charge calculated by the MS shall be identical for parts 1 and 2.
Maximum Duration of Test:
20 minutes.
Expected Sequence:
The sequence step 1‑20 is executed for execution counter k = 1,..3.
|
Step |
Direction |
Message |
Comments |
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 |
FACILITY |
As default message except contains Facility IE with contents as indicated in i below |
|
Either A, B or C branch is taken |
|||
|
A12 |
SS -> MS |
CONNECT |
|
|
A13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
A14 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B12 |
SS -> MS |
CONNECT |
|
|
B13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
B14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
C12 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
C13 |
SS -> MS |
CONNECT |
|
|
C14 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
15 |
call duration y seconds after CAI information sent by SS |
||
|
Branch D, E and F shall be taken for k= 1,2 and 3 respectively |
|||
|
D16 |
SS -> MS |
DISCONNECT |
|
|
D17 |
MS -> SS |
RELEASE |
|
|
D18 |
SS -> MS |
RELEASE COMPLETE |
|
|
D19 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
E16 |
SS -> MS |
RELEASE COMPLETE |
Shortened channel release procedure |
|
E17 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
F16 |
SS -> MS |
CHANNEL RELEASE |
|
|
20 |
MS |
MS display is checked to determine whether the correct call charge has been indicated |
NOTE The value of y is given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
y is set to a constant value of 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
k-value |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
1 |
10 |
40 |
1 |
0 |
0 |
0 |
0 |
20 |
20 |
|
2 |
10 |
40 |
1 |
———omitted——— |
20 |
40 |
|||
|
3 |
10 |
40 |
1 |
———omitted——— |
20 |
60 |
|||
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.4.
31.6.3.7 AoCI on a Call Hold call
Purpose:
1) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCI acknowledgement within 1 s of transmission of each set of e-parameters.
Conformance Requirement(s):
1) When the MS invokes a Call Hold call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCI acknowledgement within 1 s of receiving each set of e-parameters.
Reference(s):
Conformance requirement 1: 3GPP TS 04.13.
Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Support for active state of the call control protocol (U10).
– MMI method of reading the AoCI information.
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of transmission of the CONNECT message.
The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call.
The MS is made to initiate a second call (call C). The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement in a FACILITY message within 1 s of transmission of the CONNECT message.
The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT/FACILITY message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT/FACILITY message.
Maximum Duration of Test:
10 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 D or E branch is taken |
|||
|
D12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
D13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E12 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
14 |
MS |
The MS is made to initiate a second call, and the first call is placed on hold. DTMF signalling may occur, when MMI keys are depressed |
|
|
15 |
MS -> SS |
HOLD |
|
|
16 |
SS -> MS |
HOLD ACKNOWLEDGE |
|
|
17 |
MS -> SS |
CM SERVICE REQUEST |
|
|
18 |
SS -> MS |
CM SERVICE ACCEPT |
|
|
19 |
MS -> SS |
SETUP |
TI arbitrary but different from existing TI |
|
20 |
SS -> MS |
CALL PROCEEDING |
|
|
21 |
SS -> MS |
ALERTING |
|
|
22 |
SS -> MS |
CONNECT |
As default message except contains Facility IE with contents as indicated in i below |
|
Either F or G branch is taken |
|||
|
F23 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
F24 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G23 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G24 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
25 |
Call durations x and y seconds after respective CAI information sent by SS |
||
|
Branch H and I branch are taken, the sequence depending on the durations x and y |
|||
|
For call C |
|||
|
H26 |
SS -> MS |
DISCONNECT |
y seconds after call C CAI sent |
|
H27 |
MS -> SS |
RELEASE |
|
|
H28 |
SS -> MS |
RELEASE COMPLETE |
|
|
For call B |
|||
|
I26 |
SS -> MS |
DISCONNECT |
x seconds after call B CAI sent |
|
I27 |
MS -> SS |
RELEASE |
|
|
I28 |
SS -> MS |
RELEASE COMPLETE |
|
|
29 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released |
|
30 |
MS |
MS display is checked to determine whether the correct call charge has been indicated |
NOTE The value of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x set to 180 s, y is set to 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
Call |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
B(time x) |
7 |
40 |
1 |
0 |
0 |
0 |
0 |
||
|
C(time y) |
13 |
40 |
1 |
0 |
0 |
0 |
0 |
54 |
54 |
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.4.
31.6.3.8 AoCI on a Multi-party call
Purpose:
1) To verify that when the MS invokes a Multi-party call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCI acknowledgement within 1 s of transmission of each set of e-parameters.
2) To verify that when the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM records the sum of all the charges for the services currently being used and hence the ME inserts the correct charge in the ACM field of the SIM.
Conformance Requirement(s):
1) When the MS invokes a Multi-party call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCI acknowledgement within 1 s of receiving each set of e-parameters.
2) When the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM shall record the sum of all the charges for the services currently being used and hence the ME shall insert the correct charge in the ACM field of the SIM.
Reference(s):
Conformance requirement 1: 3GPP TS 04.13.
Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86.
Specific PICS Statements
– Supported teleservices (TSPC_AddInfo_TeleSvc).
PIXIT Statements
– Support for active state of the call control protocol (U10).
– MMI method of reading the AoCI information.
Initial Conditions:
System Simulator:
1 cell, default parameters, IMSI attach/detach disabled.
Mobile Station:
The MS is in MM-state "idle, updated".
Foreseen Final State of the MS:
The MS is in MM-state "idle, updated".
Method of Test:
The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of transmission of the CONNECT message.
The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call.
The MS is made to initiate a second call (call C). The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of transmission of the CONNECT message.
The MS invokes the multi-party service by sending a FACILITY message to the SS containing the BuildMPTY request.
The SS accepts the request and connects the MS with the other existing connections (active call C and held call B) and confirms with a FACILITY message.
The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and call times x and y.
Maximum Duration of Test:
10 minutes.
Expected Sequence:
|
Step |
Direction |
Message |
Comments |
|---|---|---|---|
|
0 |
At start of test only, read and note value of ACM on SIM |
||
|
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 D or E branch is taken |
|||
|
D12 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
D13 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E12 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
E13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
14 |
MS -> SS |
HOLD |
The MS is made to initiate a second call and the first call (call B) is placed on hold. DTMF signalling may occur, when MMI keys are depressed |
|
15 |
MS->SS |
HOLD |
|
|
16 |
SS -> MS |
HOLD ACKNOWLEDGE |
|
|
17 |
MS -> SS |
CM SERVICE REQUEST |
|
|
18 |
SS -> MS |
CM SERVICE ACCEPT |
|
|
19 |
MS -> SS |
SETUP |
TI arbitrary but different from existing TI |
|
20 |
SS -> MS |
CALL PROCEEDING |
|
|
21 |
SS -> MS |
ALERTING |
|
|
22 |
SS -> MS |
CONNECT |
As default message except contains Facility IE with contents as indicated in i below |
|
Either F or G branch is taken |
|||
|
F23 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
F24 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G23 |
MS -> SS |
FACILITY |
As default message except contains Facility IE with contents as indicated in ii below |
|
G24 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
The MS is made to build a multi-party call. DTMF signalling may occur, when MMI keys are depressed |
|||
|
25 |
MS -> SS |
FACILITY (TI A-B/A-C) |
As default message except contains Facility IE with contents as indicated in iii below |
|
26 |
SS -> MS |
FACILITY (TI A-B/A-C) |
As default message except contains Facility IE with contents as indicated in iv, below |
|
27 |
Call durations x and y seconds after respective CAI information sent by SS |
||
|
Branch H and branch I are taken, the sequence depending on the durations x and y |
|||
|
For call C |
|||
|
H28 |
SS -> MS |
DISCONNECT |
y seconds after call C CAI sent |
|
H29 |
MS -> SS |
RELEASE |
|
|
H30 |
SS -> MS |
RELEASE COMPLETE |
|
|
For call B |
|||
|
I28 |
SS -> MS |
DISCONNECT |
x seconds after call B CAI sent |
|
I29 |
MS -> SS |
RELEASE |
|
|
I30 |
SS -> MS |
RELEASE COMPLETE |
|
|
31 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
|
32 |
MS |
MS display is checked to determine whether the correct call charge has been indicated |
NOTE: A-B/A-C indicates a choice. the transaction identifier (TI) used must be that of the active call or the held call (ref. 3GPP TS 04.84).
The values of x and y are given below.
The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below.
Specific Message Contents:
i) FACILITY Information Element with Invoke = ForwardChargeAdvice 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.4.
x set to 180 s, y set to 90 s.
The values of the e-parameters within the parameter part of the Facility Information Element shall be set to:
|
Call |
e-parameter |
CCM total |
Step 0 ACM |
||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||
|
B(time x) |
19 |
40 |
1 |
0 |
0 |
0 |
0 |
||
|
C(time y) |
29 |
40 |
1 |
0 |
0 |
0 |
0 |
134 |
134 |
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.4.
iii) FACILITY Information Element with Invoke = BuildMPTY component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
The following abbreviations are used in the descriptions below:
U Universal tag class.
CS Context Specific tag class.
P Primitive tag form.
C Constructed tag form.
FIE Facility Information Element.
|
Contents Facility IE Identifier |
Value/remark As 3GPP TS 04.80 |
Coding 00011100 |
|
Length of FIE contents |
8 |
00001000 |
|
Component type tag |
CS/C/tag=1 |
10100001 |
|
Component length |
6 |
00000110 |
|
Invoke ID tag |
U/P/tag=2 |
00000010 |
|
Invoke ID length |
1 |
00000001 |
|
Invoke ID |
Arbitrary |
(00000000) |
|
Op-Code tag |
From 3GPP TS 04.80 |
00000010 |
|
Op-Code length |
1 |
00000001 |
|
Op-Code |
Build Multi-party |
00000001 |
ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
|
Contents Facility IE Identifier |
Value/remark As 3GPP TS 04.80 |
Coding 00111100 |
|
Length of FIE contents |
5 |
00001001 |
|
Component type tag |
CS/C/tag=2 |
10100010 |
|
Component length |
3 |
00000011 |
|
Invoke ID tag |
U/P/Integer |
00000010 |
|
Invoke ID length |
1 |
00000001 |
|
Invoke ID |
Same as used as |
(00000000) |
31.6.4 Default contents of messages
As default message contents in 3GPP TS 11.10 subclause 26.8. These messages shall not contain SS version IEs.
Where indicated in specific tests CONNECT and FACILITY messages have Facility Information Elements as defined below.
Default contents of ForwardChargeAdvice Facility Information Elements
The following abbreviations are used in the descriptions below:
U Universal tag class.
CS Context Specific tag class.
P Primitive tag form.
C Constructed tag form.
FIE Facility Information Element.
i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
|
Contents |
Value/remark |
Coding |
|
Facility IE Identifier |
As 3GPP TS 04.80 |
00011100 |
|
Length of FIE contents |
43 |
00101011 |
|
Component type tag |
CS/C/tag=1 |
10100001 |
|
Component length |
41 |
00101001 |
|
Invoke ID tag |
U/P/tag=2 |
00000010 |
|
Invoke ID length |
1 |
00000001 |
|
Invoke ID |
Arbitrary |
(00000000) (1 octet) |
|
Op-Code tag |
From 3GPP TS 04.80 |
00000010 |
|
Op-Code length |
1 |
00000001 |
|
Op-Code |
Forward Charge Advice operation |
01111101 (local value 125) |
|
Sequence Identifier |
U/C/tag=16 |
00110000 from CCITT X.208 |
|
Length Indicator |
33 |
00100001 |
|
SS-Code Identifier |
CS/P/tag=0 |
10000000 |
|
Length Indicator |
1 |
00000001 |
|
SS-Code |
AoCC SS-Code (for AoCC tests) AoCI SS-Code (for AoCI tests) |
01110010 01110001 |
|
Charging Info. identifier |
CS/C/tag=1 |
10100001 |
|
Length Indicator |
28 |
00011100 |
|
e1 Identifier |
CS/P/tag=1 |
10000001 |
|
Length Indicator |
2 |
00000010 |
|
e1 |
(2 Octets) |
See e-parameter table in relevant test |
|
e2 Identifier |
CS/P/tag=2 |
10000010 |
|
Length Indicator |
2 |
00000010 |
|
e2 |
(2 Octets) |
See e-parameter table in relevant test |
|
. |
. |
. |
|
. |
. |
. |
|
. |
. |
. |
|
e7 Identifier |
CS/P/tag=7 |
10000111 |
|
Length Indicator |
2 |
00000010 |
|
e7 |
(2 Octets) |
See e-parameter table in relevant test |
ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
|
Contents |
Value/remark |
Coding |
|
Facility IE Identifier |
As 3GPP TS 04.80 |
00111100 |
|
Length of FIE contents |
5 |
00001001 |
|
Component type tag |
CS/C/tag=2 |
10100010 |
|
Component length |
3 |
00000011 |
|
Invoke ID tag |
U/P/Integer |
00000010 |
|
Invoke ID length |
1 |
00000001 |
|
Invoke ID |
Same as used as |
(00000000) |
|
Invoke ID in Invoke FIE |