31.4 Multi-party supplementary services

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

NOTE: In this subclause, subscriber A is the MS under test, and subscribers B to G are distant parties in the calls used in the tests.

31.4.1 Beginning the MultiParty service

31.4.1.1 Beginning the MultiParty service, successful case

Conformance requirement

3GPP TS 04.84 subclause 1.1.

Test purpose

To test that the MS correctly starts the MultiParty service when it has an active call and a held call, and reacts correctly to a response from the SS indicating success.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of joining two calls into a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have Call A-B in state U10 "Active" and Call A-C in state U10 "Active" with Auxiliary state "Call held". Both calls shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall join the two calls in a MultiParty call. The MS shall send a FACILITY message containing an invoke component set to BuildMPTY, and with the transaction identifier for either Call A-B or Call A-C. Both calls shall enter auxiliary state "MPTY request". 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 including a Return Result component, the MS shall enter the state U10 "Active" with auxiliary state "Call in MPTY". 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, join the two calls
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, BuildMPTY 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 "MPTY request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "MPTY request, call held"
7	SS -> MS	FACILITY	Same TI as step 2, Return Result 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 in MPTY"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
12	SS		Check that the TCH is through-connected

31.4.1.2 Beginning the MultiParty service, unsuccessful case

Conformance requirement

3GPP TS 04.84 subclause 1.1.

Test purpose

To test that the MS correctly starts the MultiParty service when it has an active call and a held call, and reacts correctly to the following responses from the SS.

1) Return error.

2) Reject.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of joining two calls into a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

– The MS shall have Call A-B in state U10 "Active" and Call A-C in state U10 "Active" with Auxiliary state "Call held". Both calls shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

Foreseen final state of the MS

Call A-B, state U10, no auxiliary state. Call A-C, state U10, auxiliary state "Call Held".

Maximum duration of test

45 s.

Procedure

Using suitable MMI commands, the MS shall initiate a MultiParty call. The MS shall send a FACILITY message containing an invoke component set to BuildMPTY, and with the transaction identifier for either Call A-B or Call A-C. Both calls shall enter auxiliary state "MPTY request". 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 including a Return Error component, the MS shall return both calls to their original call states. 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 initiate a MultiParty call. The MS shall send a FACILITY message containing an invoke component set to BuildMPTY, and with the transaction identifier for boeither Call A-B or Call A‑C. Both calls shall enter auxiliary state "MPTY request". 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 including a Reject component, the MS shall return both calls to their original call states. 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, set up a MultiParty call
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, BuildMPTY 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 "MPTY request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "MPTY request, call held"
7	SS -> MS	FACILITY	Same TI 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, no auxiliary state
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call Held"
12	MS		Using MMI commands, set up a MultiParty call
13	MS -> SS	FACILITY	TI for Call A-B or Call A-C, BuildMPTY 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 "MPTY request"
16	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
17	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "MPTY request, call held"
18	SS -> MS	FACILITY	Same TI as step 13, 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, no auxiliary state
21	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
22	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call Held"

31.4.1.3 Beginning the MultiParty service, expiry of timer T(BuildMPTY)

Conformance requirement

3GPP TS 04.84 subclause 1.1.

Test purpose

To test that the MS correctly starts the MultiParty service when it has an active call and a held call, and on expiry of timer T(BuildMPTY) returns both calls to their original states.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of joining two calls into a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

Foreseen final state of the MS

Branch A – Call A-B, state U10, no auxiliary state. Call A-C, state U10, auxiliary state "Call Held".

Branch B – Call A-B, state U10, auxiliary state "MPTY Request". Call A-C, state U10, auxiliary state "MPTY Request".

Maximum duration of test

45 s.

Procedure

Not less than 5s and not more than 30s after sending the FACILITY message, one of the following shall have occurred:

– both calls shall be in their original call states and the MS shall have indicated the failure to the user; or

– the MS shall have sent 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, set up a MultiParty call
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, BuildMPTY 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 "MPTY request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "MPTY request, call held"
7	SS		Wait 30 s from receiving FACILITY message
			Take this branch if no message is received within 30 s
A8	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
A9	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, no auxiliary state
A10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
A11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call Held"
			Take this branch if a message is received within 30 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 "MPTY request"
B11	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
B12	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "MPTY request, call held"

31.4.2 Managing an active MultiParty call

31.4.2.1 Served mobile subscriber

31.4.2.1.1 Put the MultiParty call on hold

31.4.2.1.1.1 Put the MultiParty call on hold, successful case

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.1.

Test purpose

To test that the MS correctly places an active MultiParty call on hold, and reacts correctly to a response from the SS indicating success.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of placing a MultiParty call on hold.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY, call held". Call A-C, state U10, auxiliary state "Call in MPTY, call held".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall place the MultiParty call on hold. The MS shall send a FACILITY message containing one of the transaction identifiers of the call, and containing an invoke component HoldMPTY. Both calls shall enter the auxiliary state "Call in MPTY, hold request". 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 with the same transaction identifier and containing a return result component, the MS shall enter the state U10 "Active" with auxiliary state "Call in MPTY, call held" for both transaction identifiers. 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, put the MultiParty call on hold
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, HoldMPTY 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 in MPTY, hold request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, hold request"
7	SS -> MS	FACILITY	Same TI as step 2, Return Result 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 in MPTY, 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, auxiliary state "Call in MPTY, call held"

31.4.2.1.1.2 Put the MultiParty call on hold, unsuccessful case

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.1.

Test purpose

To test that the MS correctly places an active MultiParty call on hold, and reacts correctly to a response from the SS indicating an error or a reject condition.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of placing a MultiParty call on hold.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY".

Maximum duration of test

45 s.

Procedure

On receipt of a FACILITY message with the same transaction identifier and containing a return error component, the MS shall return to the original states for both transaction identifiers. 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 with the same transaction identifier and containing a Reject component, the MS shall return to the original states for both transaction identifiers. 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, put the MultiParty call on hold
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, HoldMPTY 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 in MPTY, hold request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, hold request"
7	SS -> MS	FACILITY	Same TI 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 in MPTY"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
12	MS		Using MMI commands, place the MultiParty call on hold
13	MS -> SS	FACILITY	TI for Call A-B or Call A-C, HoldMPTY 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 in MPTY, hold request"
16	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
17	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, hold request"
18	SS -> MS	FACILITY	Same TI as step 13, 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 in MPTY"
21	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
22	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"

31.4.2.1.1.3 Put the MultiParty call on hold, expiry of timer T(HoldMPTY)

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.1.

Test purpose

To test that the MS correctly places an active MultiParty call on hold, and on expiry of T(HoldMPTY) returns the MultiParty call to the auxiliary state "Call in MPTY".

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of placing a MultiParty call on hold.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Branch A, Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY".

Branch B, Call A-B, state U10, auxiliary state "Call in MPTY, hold request". Call A-C, state U10, auxiliary state "Call in MPTY, hold request".

Maximum duration of test

45 s.

Procedure

Not less than 5s and not more than 30s after sending the FACILITY message, one of the following shall have occurred:

– both calls shall be in their original call states and the MS shall have indicated the failure to the user; or

– the MS shall have sent another FACILITY message with the same contents.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, put the MultiParty call on hold
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, HoldMPTY 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 in MPTY, hold request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, hold request"
7	SS		Wait 30 s from receiving FACILITY message
			Take this branch if no message is received within 30 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 in MPTY"
A10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
A11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
			Take this branch if a message is received within 30 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 in MPTY, hold request"
B11	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
B12	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, hold request"

31.4.2.1.2 Create a private communication with one of the remote parties

31.4.2.1.2.1 Create a private communication with one of the remote parties, successful case

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.2.

Test purpose

To test that the MS correctly splits an active MultiParty call, and reacts correctly to a response from the SS indicating success.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of creating a private communication with one party of a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U10, no auxiliary state. Call A-C, state U10, auxiliary state "Call Held".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall request a private communication with Call A-B. The MS shall send a FACILITY message containing the transaction identifier for Call A-B and an invoke component SplitMPTY. Call A-B shall enter the auxiliary state "split request" and call A-C shall remain in state "Call in MPTY". 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 containing the same transaction identifier and a return result component, Call A-B shall enter the state U10 "Active", and Call A-C shall enter the state U10 "Active" with auxiliary state "Call held". 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, request a private communication with Call A-B
2	MS -> SS	FACILITY	TI for Call A-B, SplitMPTY 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 "Split request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
7	SS -> MS	FACILITY	Return Result component
8	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
9	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, no auxiliary state
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call held"
12	SS		Check that the TCH is through-connected

31.4.2.1.2.2 Create a private communication with one of the remote parties, unsuccessful case

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.2.

Test purpose

To test that the MS correctly splits an active MultiParty call, and reacts correctly to a response from the SS indicating an error or reject condition.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of creating a private communication with one party of a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall request a private communication with Call A-B. The MS shall send a FACILITY message containing the transaction identifier for Call A-B and an invoke component SplitMPTY. Call A-B shall enter the auxiliary state "Split request" and call A-C shall remain in state "Call in MPTY". 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 containing the same transaction identifier and a return error component, both calls shall return to their initial states. 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 request a private communication with Call A-B. The MS shall send a FACILITY message containing the transaction identifier for Call A-B and an invoke component SplitMPTY. Call A-B shall enter the auxiliary state "Split request" and call A-C shall remain in state "Call in MPTY". 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 containing the same transaction identifier and a Reject component, both calls shall return to their initial states. 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, create a private communication for Call A-B
2	MS -> SS	FACILITY	TI for Call A-B, SplitMPTY 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 "Split request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
7	SS -> MS	FACILITY	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 in MPTY"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
12	MS		Using MMI commands, create a private communication for Call A-B
13	MS -> SS	FACILITY	TI for Call A-B, SplitMPTY 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 "Split request"
16	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
17	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
18	SS -> MS	FACILITY	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 in MPTY"
21	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
22	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"

31.4.2.1.2.3 Create a private communication with one of the remote parties, expiry of timer T(SplitMPTY)

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.2.

Test purpose

To test that the MS correctly splits an active MultiParty call, and on expiry of T(SplitMPTY) returns the call to the auxiliary state "Call in MPTY".

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of creating a private communication with one party of a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Branch A, Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY".

Branch B, Call A-B, state U10, auxiliary state "Split request". Call A-C, state U10, auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall request a private communication with Call A-B. The MS shall send a FACILITY message containing the transaction identifier for Call A-B and an invoke component SplitMPTY. Call A-B shall enter the auxiliary state "Split request" and call A-C shall remain in state "Call in MPTY". 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.

After not less than 5s and not more than 30s, the MS shall either:

– return both calls to their original states; or

– send another FACILITY message with the same contents.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, request a private communication with Call A-B
2	MS -> SS	FACILITY	TI for Call A-B, SplitMPTY 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 "Split request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
7	SS		Wait 30 s from receiving FACILITY message
			Take this branch if no message is received within 30 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 in MPTY"
A10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
A11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
			Take this branch if a message is received within 30 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 "Split request"
B11	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
B12	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"

31.4.2.1.3 Terminate the entire MultiParty call

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.3.

Test purpose

To test that the MS correctly terminates an entire MultiParty call by implementing the call clearance procedure for each call in turn.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of terminating a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.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 initiate a clearance of the entire MultiParty call. The MS shall send a DISCONNECT message in respect of each of the transaction identifiers of the call. On receipt of a RELEASE message in respect of each transaction identifier, the MS shall respond with a RELEASE COMPLETE message, and 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, terminate the entire MultiParty call
			Steps 2 and 3 may occur in any order
2	MS -> SS	DISCONNECT	Transaction identifier of Call A-B
3	MS -> SS	DISCONNECT	Transaction identifier of Call A-C
4	SS -> MS	RELEASE	Transaction identifier of Call A-B
5	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B
6	SS -> MS	RELEASE	Transaction identifier of Call A-C
7	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C
8	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
9	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"

31.4.2.1.4 Explicitly disconnect a remote party

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.4.

Test purpose

To test that the MS correctly disconnects a single remote party by implementing the call clearance procedure for that party.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of disconnecting one party of a MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U0. Call A-C, state U10, with auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall initiate a clearance of the Call A-B. The MS shall send a DISCONNECT message containing the transaction identifier of Call A-B. On receipt of a RELEASE message the MS shall respond with a RELEASE COMPLETE message, and enter state U0 "Null" for Call A-B. Call A-C shall enter state U10 "Active" with, auxiliary state "Call in MPTY". 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 state U10, with auxiliary state "Call in MPTY" for Call A-C, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Call A-B.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, clear call A-B
2	MS -> SS	DISCONNECT	Transaction identifier of Call A-B
3	SS -> MS	RELEASE	Transaction identifier of Call A-B
4	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
6	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
7	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
8	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, with auxilliary state "Call in MPTY"

31.4.2.2 Remote parties

31.4.2.2.1 Release from the MultiParty call

Conformance requirement

3GPP TS 04.84 subclause 1.2.1.4.

Test purpose

To test that the MS responds correctly to a call clearance from one of the remote parties.

Method of test

Specific PICS Statements

–

PIXIT Statements

–

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U0. Call A-C, state U10, with auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

On receipt of a DISCONNECT message containing the transaction identifier of Call A-B, the MS shall send a RELEASE message. On receipt of a RELEASE COMPLETE message the MS shall enter state U0 "Null" for Call A-B. Call A-C shall enter state U10 "Active", with auxiliary state "Call in MPTY". 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 state U10, with auxiliary state "Call in MPTY"for Call A-C, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Call A-B.

Expected sequence

Step	Direction	Message	Comments
1	SS -> MS	DISCONNECT	Transaction identifier of Call A-B
2	MS -> SS	RELEASE	Transaction identifier of Call A-B
3	SS -> MS	RELEASE COMPLETE	Transaction identifier of Call A-B
4	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
5	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
6	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
7	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, with auxiliary state "Call in MPTY"

31.4.3 Managing a held MultiParty call

31.4.3.1 Retrieve the held MultiParty call

31.4.3.1.1 Retrieve the held MultiParty call, successful case

Conformance requirement

3GPP TS 04.84 subclause 1.3.1.1.

Test purpose

To test that the MS correctly retrieves a held MultiParty call, and reacts correctly to a response from the SS indicating success.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of retrieving a held MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have a held MultiParty call to two destinations (Call A-B and Call A-C). Both call states shall be U10 "Active" with auxiliary state "Call in MPTY, call held". The call shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.2.1.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall retrieve the MultiParty call. The MS shall send a FACILITY message containing one of the transaction identifiers of the call, and containing an invoke component RetrieveMPTY. Both calls shall enter the auxiliary state "Call in MPTY, retrieve request". 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 with the same transaction identifier and containing a return result component, the MS shall enter the state U10 "Active" with auxiliary state "Call in MPTY" for both transaction identifiers. 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, retrieve the MultiParty call
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, RetrieveMPTY 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 in MPTY, Retrieve request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, Retrieve request"
7	SS -> MS	FACILITY	Same TI as step 2, Return Result 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 in MPTY"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
12	SS		Check that the TCH is through-connected

31.4.3.1.2 Retrieve the held MultiParty call, unsuccessful case

Conformance requirement

3GPP TS 04.84 subclause 1.3.1.1.

Test purpose

To test that the MS correctly retrieves a held MultiParty call, and reacts correctly to a response from the SS indicating an error or a reject condition.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of retrieving a held MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.2.1.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY, call held". Call A-C, state U10, auxiliary state "Call in MPTY, call held".

Maximum duration of test

30 s.

Procedure

On receipt of a FACILITY message with the same transaction identifier and containing a reject component, the MS shall return to the original states for both transaction identifiers. 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, retrieve the held MultiParty call
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, RetrieveMPTY 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 in MPTY, retrieve request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, retrieve request"
7	SS -> MS	FACILITY	Same TI 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 in MPTY, 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, auxiliary state "Call in MPTY, call held"
12	MS		Using MMI commands, retrieve the held MultiParty call
13	MS -> SS	FACILITY	TI for Call A-B or Call A-C, RetrieveMPTY 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 in MPTY, retrieve request"
16	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
17	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, retrieve request"
18	SS -> MS	FACILITY	Same TI as step 13, 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 in MPTY, 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, auxiliary state "Call in MPTY, call held"

31.4.3.1.3 Retrieve the held MultiParty call, expiry of timer T(RetrieveMPTY)

Conformance requirement

3GPP TS 04.84 subclause 1.3.1.1.

Test purpose

To test that the MS correctly retrieves a MultiParty call on hold, and on expiry of T(RetrieveMPTY) returns the MultiParty call to the auxiliary state "Call in MPTY, call held".

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of retrieving a held MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.2.1.1.1.

Foreseen final state of the MS

Branch A, Call A-B, state U10, auxiliary state "Call in MPTY, call held". Call A-C, state U10, auxiliary state "Call in MPTY, call held".

Branch B, Call A-B, state U10, auxiliary state "Call in MPTY, retrieve request". Call A-C, state U10, auxiliary state "Call in MPTY, retrieve request".

Maximum duration of test

45 s.

Procedure

Not less than 5s and not more than 30s after sending the FACILITY message, one of the following shall have occurred:

– both calls shall be in their original call states and the MS shall have indicated the failure to the user; or

– the MS shall have sent another FACILITY message with the same contents.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, retrieve the held MultiParty call
2	MS -> SS	FACILITY	TI for Call A-B or Call A-C, RetrieveMPTY 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 in MPTY, retrieve request"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, retrieve request"
7	SS		Wait 30 s from receiving FACILITY message
			Take this branch if no message is received within 30 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 in MPTY, 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, auxiliary state "Call in MPTY, call held"
			Take this branch if a message is received within 30 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 in MPTY, retrieve request"
B11	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
B12	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, retrieve request"

31.4.3.2 Initiate a new call

Conformance requirement

3GPP TS 04.84 subclause 1.3.1.2.

Test purpose

To test that the MS can set up a new outgoing call with a held MultiParty call.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of making a new outgoing call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.2.1.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY, call held". Call A-C, state U10, auxiliary state "Call in MPTY, call held". Call A-D State U10.

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall initiate a new outgoing call A-D. The MS shall send a SETUP message with a new transaction identifier and enter state U1 "Call initiated". On receipt of an ALERTING message followed by a CONNECT message, the MS shall send a CONNECT ACKNOWLEDGE message and enter state U10 "Active". The call state of the MultiParty call shall not be affected. 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, make a new call
2	MS -> SS	CM SERVICE REQUEST
3	SS -> MS	CM SERVICE ACCEPT
4	MS -> SS	SETUP	TI different from Call A-B or Call A-C (new Call A-D)
5	SS -> MS	ALERTING	Transaction identifier of Call A-D
6	SS -> MS	CONNECT	Transaction identifier of Call A-D
7	MS -> SS	CONNECT ACKNOWLEDGE	Transaction identifier of Call A-D
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 in MPTY, 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, auxiliary state "Call in MPTY, call held"
12	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
13	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, no auxiliary state.

31.4.3.3 Process a call waiting request

Conformance requirement

3GPP TS 04.84 subclause 1.3.1.3.

Test purpose

To test that the MS can correctly process a Call Waiting request with a held MultiParty call.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of answering a waiting call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both calls states shall be U10 "Active" with auxiliary state "Call in MPTY". The MS shall also have a Call A-D in state U7 "Call received". The Multiparty call shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY, call held". Call A-C, state U10, auxiliary state "Call in MPTY, call held". Call A-D State U10.

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall place the MultiParty on hold, and answer Call A-D.

The MS shall send a FACILITY message to the SS using any one of the transaction identifiers of the MultiParty call and containing an invoke component HoldMPTY, and shall enter state U10 "Active", with auxiliary state "call in MPTY, hold request" in respect of each of the transaction identifiers.

On receipt of a FACILITY message using the same transaction identifier and containing a return result component, the MS shall enter state U10 "Active" with auxiliary state "Call in MPTY, call held" for each of the transaction identifiers.

The MS shall then send a CONNECT message to the SS, using the transaction identifier of Call A-D, and on receipt of a CONNECT ACKNOWLEDGE message, shall enter state U10 "Active". 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, place the multiparty call on hold and answer the waiting call
2	MS -> SS	FACILITY	Transaction identifier of Call A-B or A-C, HoldMPTY invoke component
3	SS -> MS	FACILITY	Same transaction identifier as step 2
4	MS -> SS	CONNECT	Transaction identifier of Call A-D
5	SS -> MS	CONNECT ACKNOWLEDGE	Transaction identifier of Call A-D
6	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
7	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY, call held"
8	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
9	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, call held"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
11	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, no auxiliary state.

31.4.3.4 Terminate the held MultiParty call

Conformance requirement

3GPP TS 04.84 subclause 1.3.1.4.

Test purpose

To test that the MS correctly terminates a held MultiParty call by initiating call clearance for each party in turn.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of terminating a held MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.2.1.1.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 initiate a clearance of the entire held MultiParty call. The MS shall send a DISCONNECT message in respect of each of the transaction identifiers of the call. On receipt of a RELEASE message in respect of each transaction identifier, the MS shall respond with a RELEASE COMPLETE message, and 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" for each call.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, terminate the entire MultiParty call
			Steps 2 and 3 may occur in any order
2	MS -> SS	DISCONNECT	Transaction identifier of Call A-B
3	MS -> SS	DISCONNECT	Transaction identifier of Call A-C
4	SS -> MS	RELEASE	Transaction identifier of Call A-B
5	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B
6	SS -> MS	RELEASE	Transaction identifier of Call A-C
7	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C
8	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
9	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"

31.4.4 Managing a single call and a MultiParty call

31.4.4.1 Served mobile subscriber

31.4.4.1.1 Disconnect the single call

31.4.4.1.1.1 Disconnect active single call

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.1.

Test purpose

To test that the MS correctly clears the single call when the single call is active and the MultiParty call is held.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of clearing the single call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY, call held". The MS shall have in addition a single call (A-D) in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.2.1.1.2.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY, call held". Call A-C, state U10, auxiliary state "Call in MPTY, call held". Call A-D State U0.

Maximum duration of test

30 s.

Procedure

Within 5 s of sending the RELEASE COMPLETE message, the MS may send a FACILITY message to retrieve the Held Call. The SS must reject this request. The call state and auxiliary state for Call A-B and Call A-C shall not change. 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 for Calls A-B and A-C, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Call A-D.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, clear call A-D
2	MS -> SS	DISCONNECT	Transaction identifier of Call A-D
3	SS -> MS	RELEASE	Transaction identifier of Call A-D
4	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-D
5	SS		Wait 5 s from receiving a RELEASE COMPLETE
			Take this branch if no message is received within 5s
A1	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
A2	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY, call held"
A3	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
A4	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, call held"
A5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
A6	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-D, with cause #81 "invalid transaction identifier value"
			Take this branch if a message is received within 5s
B1	MS -> SS	FACILITY	TI for Call A-B, RetrieveMPTY Invoke component
B2	SS -> MS	FACILITY	TI for Call A-B, Reject component
B3	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
B4	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY, call held"
B5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
B6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, call held"
B7	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
B8	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-D, with cause #81 "invalid transaction identifier value"

31.4.4.1.1.2 Disconnect held single call

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.1.

Test purpose

To test that the MS correctly clears the single call when the single call is held and the MultiParty call is active.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of clearing the held single call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY". The MS shall have in addition a single call (A-D) in state U10 "Active" with auxiliary state "Call held". Both calls shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY". Call A-D State U0.

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall clear Call A-D. The MS shall send a DISCONNECT message with the transaction identifier for Call A-D. On receipt of a RELEASE message the MS shall send a RELEASE COMPLETE message and enter state U0 "Null" for Call A-D. The call state and auxiliary state for Call A-B and Call A-C shall not change. 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 for Calls A-B and A-C, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Call A-D.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, clear call A-D
2	MS -> SS	DISCONNECT	Transaction identifier of Call A-D
3	SS -> MS	RELEASE	Transaction identifier of Call A-D
4	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-D
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
6	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY"
7	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
8	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
9	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
10	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-D, with cause #81 "invalid transaction identifier value"

31.4.4.1.2 Disconnect the MultiParty call

31.4.4.1.2.1 Void

31.4.4.1.2.2 Void

31.4.4.1.2.3 Clear all parties of held MultiParty call

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.2.

Test purpose

To test that the MS correctly clears the MultiParty call by clearing all remote parties to a held MultiParty call.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of clearing a held MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY, Call held". The MS shall have in addition a single call (A-D) in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

Foreseen final state of the MS

Call A-B, state U0. Call A-C, state U0. Call A-D State U10, no auxiliary state.

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall clear the MultiParty call. The MS shall send DISCONNECT messages with the transaction identifiers for Call A-B and A-C. On receipt of a RELEASE message to each DISCONNECT the MS shall send a RELEASE COMPLETE message and enter state U0 "Null". Call A-B and Call A-C shall enter state U0 "Null". The call state and auxiliary state for Call A-D shall not change. 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 for Call A-D, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Calls A-B and A-C.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, terminate the entire MultiParty call
			Steps 2 and 3 may occur in any order
2	MS -> SS	DISCONNECT	Transaction identifier of Call A-B
3	MS -> SS	DISCONNECT	Transaction identifier of Call A-C
4	SS -> MS	RELEASE	Transaction identifier of Call A-B
5	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B
6	SS -> MS	RELEASE	Transaction identifier of Call A-C
7	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C
8	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
9	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
11	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
12	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
13	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10

31.4.4.1.2.4 Clear all parties of active MultiParty call

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.2.

Test purpose

To test that the MS correctly clears the MultiParty call by clearing all remote parties to an active MultiParty call.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of clearing an active MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

Foreseen final state of the MS

Call A-B, state U0. Call A-C, state U0. Call A-D State U10, auxiliary state "Call Held".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall clear the MultiParty call. The MS shall send DISCONNECT messages with the transaction identifier for Call A-B and A-C. On receipt of a RELEASE message to each DISCONNECT the MS shall send a RELEASE COMPLETE message and enter state U0 "Null. Call A-B and Call A-C shall enter state U0 "Null". Within 5 s of sending the RELEASE COMPLETE message, the MS may send a RETRIEVE message to retrieve the Held Call. The SS shall reject this request. The call state and auxiliary state for Call A-D shall not change. 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. for Call A-D, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Calls A-B and A-C.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, terminate the entire MultiParty call
			Steps 2 and and 3 may occur in any order
2	MS -> SS	DISCONNECT	Transaction identifier of Call A-B
3	MS -> SS	DISCONNECT	Transaction identifier of Call A-C
4	SS -> MS	RELEASE	Transaction identifier of Call A-B
5	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B
6	SS -> MS	RELEASE	Transaction identifier of Call A-C
7	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C
8	SS		Wait 5 s from receiving a RELEASE COMPLETE
			Take this branch if no message is received within 5s
A9	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
A10	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
A11	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
A12	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
A13	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
A14	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Call Held"
			Take this branch if a message is received within 5s
B9	MS -> SS	RETRIEVE	Transaction identifier of Call A-D
B10	SS -> MS	RETRIEVE REJECT
B11	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
B12	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
B13	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
B14	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
B15	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
B16	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Call Held"

31.4.4.2 Disconnect all calls

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.3.

Test purpose

To test the MS correctly clears all calls, by clearing in turn each connected party.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of clearing all active calls.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

Foreseen final state of the MS

Call A-B, state U0. Call A-C, state U0. Call A-D state U0.

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall clear all calls. The MS shall send DISCONNECT messages with the transaction identifier for Call A-B, Call A-C and Call A-D. On receipt of a RELEASE message to each DISCONNECT the MS shall send a RELEASE COMPLETE message and enter state U0 "Null". Call A-B, Call A-C Call A-D 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" for each call.

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, terminate allcalls
			The DISCONNECT messages (steps 2a, 3a, and 4a) may occur in any order. SS shall respond to each DISCONNECT independently as soon as it is received. The step sequences 2a-2c, 3a-3c and 4a-4c may overlap
2a	MS -> SS	DISCONNECT	Transaction identifier of Call A-B
2b	SS -> MS	RELEASE	Transaction identifier of Call A-B
2c	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B
3a	MS -> SS	DISCONNECT	Transaction identifier of Call A-C
3b	SS -> MS	RELEASE	Transaction identifier of Call A-C
3c	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C
4a	MS -> SS	DISCONNECT	Transaction identifier of Call A-D
4b	SS -> MS	RELEASE	Transaction identifier of Call A-D
4c	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-D
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
6	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
7	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
8	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value"
9	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
10	MS -> SS	RELEASE COMPLETE	Transaction identifier of Call A-D, with cause #81 "invalid transaction identifier value"

31.4.4.3 Add the single call to the MPTY

31.4.4.3.1 Add the single call to the MPTY, successful case

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.4.

Test purpose

To test that the MS correctly adds a single held call to an active MultiParty call, and reacts correctly to a response from the SS indicating success.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of adding the single call to the MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

NOTE: The MultiParty call may be set up using the procedures of subclause 31.4.1.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY". Call A-D state U10, auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall add the single call to the MultiParty call. The MS shall send a FACILITY message containing one of the transaction identifiers A-B, A-C or A-D and containing a BuildMPTY invoke component. Calls A-B and A-C shall remain in state U10 "Active" with auxiliary state "Call in MPTY". Call A-D shall enter state U10 "Active" with auxiliary state "MPTY request, call held". 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 containing a return result component, all calls shall enter state U10 "Active" with auxiliary state "Call in MPTY". 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, join the single call to the MultiParty call
2	MS -> SS	FACILITY	TI for Call A-B, Call A-C or call A-D, BuildMPTY 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 in MPTY"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
7	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
8	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "MPTY request, Call held"
9	SS -> MS	FACILITY	TI same as step 2, Return Result component
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
11	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY"
12	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
13	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
14	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
15	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Call in MPTY"
16	SS		Check that the TCH is through-connected

31.4.4.3.2 Add the single call to the MPTY, maximum number of participants exceeded

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.4.

Test purpose

To test that the MS correctly adds a single held call to an active MultiParty call, and reacts correctly to a response from the SS indicating maximum number of participants exceeded.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of adding the single call to the MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS shall have a MultiParty call to five destinations (A-B, A-C and A-D) all in state U10 "Active" with auxiliary state "Call in MPTY". The MS shall have in addition a single call (A-E) in state U10 "Active" with auxiliary state "Call held". Both calls shall be of a basic service supported by the MS and relevant to the MultiParty supplementary service as stated in 3GPP TS 02.04 table A.1.

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY". Call A-D state U10, auxiliary state "Call in MPTY", Call A-E state U10, auxiliary state "Call Held".

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall add the single call to the MultiParty call. The MS shall send a FACILITY message containing any one of the transaction identifiers and containing a BuildMPTY invoke component. Calls A-B to A-D shall remain in state U10 "Active" with auxiliary state "Call in MPTY". Call A-E shall enter state U10 "Active" with auxiliary state "MPTY request, call held". 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 containing a return error component "MaxNumberOfMPTY-ParticipantsExceeded", then all calls shall return to their original states. 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, join the single call to the MultiParty call
2	MS -> SS	FACILITY	TI for Call A-B, Call A-C, Call A-D or Call A-E, BuildMPTY 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 in MPTY"
5	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
6	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state " Call in MPTY"
7	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
8	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state " Call in MPTY"
9	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-E
10	MS -> SS	STATUS	Transaction identifier of Call A-E, state U10, auxiliary state "MPTY request, Call held"
11	SS -> MS	FACILITY	Same TI as step 2, Return error component "MaxNumberOfMPTY-ParticipantsExceeded"
12	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
13	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY"
14	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
15	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
16	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
17	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Call in MPTY"
18	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-E
19	MS -> SS	STATUS	Transaction identifier of Call A-E, state U10, auxiliary state "Call Held"

31.4.4.4 Alternate between the MPTY call and the single call

Conformance requirement

3GPP TS 04.84 subclause 1.4.1.5.

Test purpose

To test that the MS correctly alternates between the single call and the MultiParty call, by proper use of the hold and retrieve procedures.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of alternating between the single call to the MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY". Call A-D state U10, auxiliary state "Call Held",

Maximum duration of test

30 s.

Procedure

Using suitable MMI commands, the MS shall alternate between the single call and the MultiParty call. The MS shall send a FACILITY message containing one of the transaction identifiers of the MultiParty call, and containing an invoke component HoldMPTY. The MS shall then send a RETRIEVE message with the transaction identifier for Call A-D. Call A-B and Call A-C shall enter the auxiliary state "Call in MPTY, hold request". Call A-D shall enter auxiliary state "retrieve request". 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.

The SS shall send a FACILITY message with a return result component and then send a RETRIEVE ACKNOWLEDGE message. On receipt of these messages, Calls A-B and A-C shall enter auxiliary state "Call in MPTY, call held", and Call A-D shall enter state U10 "Active" with no auxiliary state. 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 alternate between the single call and the MultiParty call. The MS shall send a HOLD message with the transaction identifier for Call A-D. The MS shall also send a FACILITY message containing one of the transaction identifiers of the MultiParty call, and containing an invoke component RetrieveMPTY. Call A-D shall enter the auxiliary state "hold request". Call A-B and Call A-C shall enter the auxiliary state "Call in MPTY, retrieve request". 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.

The SS shall send a HOLD ACKNOWLEDGE message and shall also send a FACILITY message with a return result component. On receipt of these messages, Call A-B and A-C shall enter auxiliary state "Call in MPTY", and Call A-D shall enter state U10 "Active" with auxiliary state "Call held". 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, alternate between the active and held calls
2	MS -> SS	FACILITY	TI for Call A-B or call A-C, HoldMPTY Invoke component
3	MS -> SS	RETRIEVE	Transaction identifier of Call A-D
4	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
5	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY, Hold request"
6	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
7	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, Hold request
8	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
9	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Retrieve request"
10	SS -> MS	FACILITY	Same TI as step 2, Return result component
11	SS -> MS	RETRIEVE ACKNOWLEDGE	Transaction identifier of Call A-D
12	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
13	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY, Call held"
14	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
15	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, Call held"
16	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
17	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, no auxiliary state
18	SS		Check that the TCH is through-connected
19	MS		Using MMI commands, alternate between the active and held calls
20	MS -> SS	HOLD	Transaction identifier of Call A-D
21	MS -> SS	FACILITY	TI for Call A-B or call A-C, RetrieveMPTY Invoke component
22	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
23	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY, Retrieve request"
24	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
25	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY, Retrieve request
26	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
27	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Hold request"
28	SS -> MS	HOLD ACKNOWLEDGE	Transaction identifier of Call A-D
29	SS -> MS	FACILITY	Same TI as step 20, Return result component
30	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
31	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY"
32	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
33	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
34	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
35	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Call Held"
36	SS		Check that the TCH is through-connected

31.4.5 Adding extra remote parties

Conformance requirement

3GPP TS 04.84 subclause 1.5.

Test purpose

To test that the MS adds extra remote parties to the MultiParty call.

Method of test

Specific PICS Statements

–

PIXIT Statements

– Method of alternating between the single call to the MultiParty call.

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

Foreseen final state of the MS

Call A-B, state U10, auxiliary state "Call in MPTY". Call A-C, state U10, auxiliary state "Call in MPTY". Call A-D state U10, auxiliary state "Call in MPTY".

Maximum duration of test

30 s.

Procedure

The procedure of test 34.4.2.1.1.1 "Put the MultiParty call on hold, successful case" shall be performed followed by the procedure of 34.4.3.2 "Initiate a new call", followed by the procedure of 31.4.4.3.1 " Add the single call to the MPTY, successful case".

Expected sequence

Step	Direction	Message	Comments
1	MS		Using MMI commands, put the MultiParty call on Hold
2	MS -> SS	FACILITY	TI for Call A-B or call A-C, HoldMPTY Invoke component
3	SS -> MS	FACILITY	Same TI as step 2, Return Result component
4	MS -> SS	SETUP	TI different from Call A-B or Call A-C (new Call A-D)
5	SS -> MS	ALERTING	Transaction identifier of Call A-D
6	SS -> MS	CONNECT	Transaction identifier of Call A-D
7	MS -> SS	CONNECT ACKNOWLEDGE	Transaction identifier of Call A-D
8	MS -> SS	FACILITY	TI for Call A-B, Call A-C or call A-D, BuildMPTY Invoke component
9	SS -> MS	FACILITY	TI same as step 8, Return Result component
10	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-B
11	MS -> SS	STATUS	Transaction identifier of Call A-B, state U10, auxiliary state "Call in MPTY"
12	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-C
13	MS -> SS	STATUS	Transaction identifier of Call A-C, state U10, auxiliary state "Call in MPTY"
14	SS -> MS	STATUS ENQUIRY	Transaction identifier of Call A-D
15	MS -> SS	STATUS	Transaction identifier of Call A-D, state U10, auxiliary state "Call in MPTY"
16	SS		Check that the TCH is through-connected