31.13 Explicit Call Transfer (ECT)
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
NOTE: In this subclause, Subscriber A is the MS under test, and subscribers B and C are distant parties to the calls made during the tests.
31.13.1 Explicit Call Transfer invocation
31.13.1.1 Explicit Call Transfer invocation, successful case, both calls active, clearing using DISCONNECT
Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a DISCONNECT response from the network.
Method of test
Specific PICS Statements
–
PIXIT Statements
– Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a DISCONNECT message with respect to one of the calls containing a return result component, followed by a DISCONNECT message for the other call, the MS shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
Using MMI commands, perform and explicit call transfer |
|
|
2 |
MS -> SS |
FACILITY |
TI for Call A-B or Call A-C, ExplicitCT Invoke component |
|
3 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
4 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
5 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
6 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
7 |
SS -> MS |
DISCONNECT |
Transaction identifier of Call A-B |
|
8 |
MS -> SS |
RELEASE |
Transaction identifier of Call A-B |
|
9 |
SS -> MS |
DISCONNECT |
Transaction identifier of Call A-C |
|
10 |
MS -> SS |
RELEASE |
Transaction identifier of Call A-C |
|
11 |
SS -> MS |
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
12 |
SS -> MS |
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
13 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
14 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" |
|
15 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
16 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
31.13.1.2 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE
Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a RELEASE response from the network.
Method of test
Specific PICS Statements
–
PIXIT Statements
– Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a RELEASE message with respect to one of the calls containing a return result component, followed by a RELEASE message for the other call, the MS shall respond with a RELEASE COMPLETE message for each call and shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
Using MMI commands, perform and explicit call transfer |
|
|
2 |
MS -> SS |
FACILITY |
TI for Call A-B or Call A-C, ExplicitCT Invoke component |
|
3 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
4 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
5 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
6 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
7 |
SS -> MS |
RELEASE |
Transaction identifier of Call A-B |
|
8 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
9 |
SS -> MS |
RELEASE |
Transaction identifier of Call A-C |
|
10 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
11 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
12 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" |
|
13 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
14 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
31.13.1.3 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE COMPLETE
Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a RELEASE COMPLETE response from the network.
Method of test
Specific PICS Statements
–
PIXIT Statements
– Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a RELEASE COMPLETE message with respect to one of the calls containing a return result component, followed by a RELEASE COMPLETE message for the other call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
Using MMI commands, perform and explicit call transfer |
|
|
2 |
MS -> SS |
FACILITY |
TI for Call A-B or Call A-C, ExplicitCT Invoke component |
|
3 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
4 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
5 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
6 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
7 |
SS -> MS |
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
8 |
SS -> MS |
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
9 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
10 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" |
|
11 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
12 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
31.13.1.4 Explicit Call Transfer invocation, successful case, second call alerting
Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between an active held call and an alerting call by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of clearing messages from the network.
Method of test
Specific PICS Statements
–
PIXIT Statements
– Method of performing Explicit Call transfer on an active call and an alerting call.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U4 "Call Delivered" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a DISCONNECT message with respect to one of the calls containing a return result component, followed by a DISCONNECT message for the other call, the MS shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
Using MMI commands, perform and explicit call transfer |
|
|
2 |
MS -> SS |
FACILITY |
TI for Call A-B or Call A-C, ExplicitCT Invoke component |
|
3 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
4 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
5 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
6 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U4 |
|
7 |
SS -> MS |
DISCONNECT |
Transaction identifier of Call A-B |
|
8 |
MS -> SS |
RELEASE |
Transaction identifier of Call A-B |
|
9 |
SS -> MS |
DISCONNECT |
Transaction identifier of Call A-C |
|
10 |
MS -> SS |
RELEASE |
Transaction identifier of Call A-C |
|
11 |
SS -> MS |
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
12 |
SS -> MS |
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
13 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
14 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value" |
|
15 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
16 |
MS -> SS |
RELEASE COMPLETE |
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
31.13.1.5 Explicit Call Transfer invocation, unsuccessful case
Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and returns both calls to their original states on receipt of an error or reject response.
Method of test
Specific PICS Statements
–
PIXIT Statements
– Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active"with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U10, auxiliary state "Call held". Call A-C, Call A-C, state U10, no auxiliary state.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a FACILITY message using the same transaction identifier and including a return error component, the MS shall not send any further messages in respect of the transfer attempt, and shall remain in the same call state for both calls. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Using suitable MMI commands, the MS shall again invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a FACILITY message using the same transaction identifier and including a reject component, the MS shall not send any further messages in respect of the transfer attempt, and shall remain in the same call state for both calls. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
Using MMI commands, perform an explicit call transfer |
|
|
2 |
MS -> SS |
FACILITY |
TI for Call A-B or Call A-C, ExplicitCT Invoke component |
|
3 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
4 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
5 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
6 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
7 |
SS -> MS |
FACILITY |
TI same as step 2, Return Error component |
|
8 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
9 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
10 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
11 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
12 |
MS |
Using MMI commands, perform an explicit call transfer |
|
|
13 |
MS -> SS |
FACILITY |
TI for Call A-B or Call A-C, ExplicitCT Invoke component |
|
14 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
15 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
16 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
17 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
18 |
SS -> MS |
FACILITY |
TI same as step 2, Reject component |
|
19 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
20 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
21 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
22 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
31.13.1.6 Explicit Call Transfer invocation, expiry of T(ECT)
Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
3GPP TS 04.80 subclause 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
To test that the MS invokes explicit call transfer between an active held call and an alerting call by sending a FACILITY message with the correct invoke component, and returns both calls to their original states on expiry of T(ECT).
Method of test
Specific PICS Statements
–
PIXIT Statements
– Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U10, auxiliary state "Call held". Call A-C, Call A-C, state U10, no auxiliary state.
Maximum duration of test
45 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Between 5s and 15s after sending the FACILITY message, the MS shall either:
– remain in the same call states and indicate failure to the user; or
– send another FACILITY message with the same contents.
The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
Using MMI commands, perform an explicit call transfer |
|
|
2 |
MS -> SS |
FACILITY |
TI for Call A-B or Call A-C, ExplicitCT Invoke component |
|
3 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
4 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
5 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
6 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
7 |
SS |
Wait 15 s from receiving FACILITY message |
|
|
Take this branch if no message is received within 15 s |
|||
|
A8 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
A9 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
A10 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
A11 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |
|
Take this branch if a message is received within 15 s |
|||
|
B8 |
MS -> SS |
FACILITY |
Same as Step 2. Message shall not be received less than 5 s after the first FACILITY message |
|
B9 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
B10 |
MS -> SS |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
B11 |
SS -> MS |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
B12 |
MS -> SS |
STATUS |
Transaction identifier of Call A-C, state U10, no auxiliary state |