Datasets:

OrganizedProgrammers
/

3GPPSpecContent

Dataset card Data Studio Files Files and versions Community

Split (1)

train · 466k rows

hash stringlengths 32 32	doc_id stringlengths 5 12	section stringlengths 4 595	content stringlengths 0 6.67M
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.3.1.6.1 Interrogation accepted	Conformance requirement 3GPP TS 04.83 subclause 1.6. Test purpose To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of successful interrogation. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is "idle updated". Specific PICS Statements - PIXIT Statements - Description of the user's commands and of display of the answers from the network for interrogation of call waiting. Foreseen final state of the MS The MS is "idle updated". Test procedure By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CW for all basic service groups. Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogateSS (BasicServiceCode(s)) operation. The SS transaction is released and the dedicated channel is released. Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests interrogation of CW for all basic service groups. Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogateSS (SS-Status) operation. The dedicated channel is released. Maximum duration of test 3 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate an interrogation of CW (all) 2 MS -> SS CHANNEL REQUEST with establishment cause "Other procedures which can be completed with an SDCCH" 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS REGISTER 7 SS -> MS RELEASE COMPLETE InterrogateSS (BasicServiceCode(s)) operation Return_result 8 SS -> MS CHANNEL RELEASE 10 MS The MS is made to initiate an interrogation of CW (all) 11 MS -> SS CHANNEL REQUEST with establishment cause "Other procedures which can be completed with an SDCCH" 12 SS -> MS IMMEDIATE ASSIGNMENT 13 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 14 SS -> MS CM SERVICE ACCEPT 15 MS -> SS REGISTER 16 SS -> MS RELEASE COMPLETE InterrogateSS (SS-Status) operation Return result 17 SS -> MS CHANNEL RELEASE 18 MS Provide correct MMI user indication after step 16 Specific message content step 6, 15 - CW - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Interrogation: Supplementary service code = CW. Basic service code: no Bearer Service present, no teleservice present.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.3.1.6.2 Interrogation rejected	Conformance requirement 3GPP TS 04.83 subclause 1.6. Test purpose To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of an error response and an invoke problem Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in CC state U10. Specific PICS Statements - PIXIT Statements - Description of the user's commands and of display of the answers from the network for call waiting. Foreseen final state of the MS The MS is in CC state U10. Test procedure By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CW for all basic service groups. Upon receipt of the operation (in a REGISTER message),the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing a Return_error(error: SS not available) of the InterrogateSS operation. The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10. Then again, by means of appropriate MMI functions as defined by the basic public MMI described in 3GPP TS 02.30, the user requests interrogation of CW for all basic service groups. Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message (same PD and TI that in the REGISTER message) with the Facility information element containing a reject(invoke_problem: resource limitation) of the InterrogateSS operation. The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10. Maximum duration of test 3 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate an interrogation of CW (all) 2 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 3 SS -> MS CM SERVICE ACCEPT 4 MS -> SS REGISTER 5 SS -> MS RELEASE COMPLETE InterrogateSS operation Return_error 6 SS -> MS STATUS ENQUIRY 7 MS -> SS STATUS CC state U10 8 MS The MS is made to initiate an interrogation of CW for (all) 9 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 10 SS -> MS CM SERVICE ACCEPT 11 MS -> SS REGISTER 12 SS -> MS RELEASE COMPLETE InterrogateSS operation Reject 13 MS provide correct MMI user indication 14 SS -> MS STATUS ENQUIRY 15 MS -> SS STATUS CC state U10 Specific message content step 4, 11 - CW - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = Interrogation: Supplementary service code = CW. Basic service code:no Bearer Service present, no teleservice present. step 5 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: return error code: SS not available. For the return error the invoke ID must be the same as in the invoke of the InterrogateSS operation. step 12 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: reject code: resource limitation. For the reject the invoke ID must be the same as in the invoke of the InterrogateSS operation.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.3.2 Call Hold
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.3.2.1 Hold invocation	Conformance requirement 3GPP TS 04.83 subclause 2.1.2. Test purpose To test the correct operation of the Hold procedure, and the MS reaction to the following messages sent in response to the HOLD message. 1. HOLD REJECT. 2. HOLD ACKNOWLEDGE. Method of test Specific PICS Statements - PIXIT Statements - Method of placing a call on hold. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have a call of a basic service supported by the MS and applicable to Call Hold as described in 3GPP TS 02.04 table A.1 in state U10 "Active" Foreseen final state of the MS State U10, Auxiliary state "Call Held". Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall request that the call is placed on hold. The MS shall send a HOLD message and enter auxiliary state "hold request". On receipt of a HOLD REJECT message from the SS shall return to state U10 "Active". The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of the call, and receiving a STATUS message indicating the appropriate call state and auxiliary state. Using suitable MMI commands, the MS shall again request that the call is placed on hold. The MS shall send a HOLD message and enter auxiliary state "hold request". On receipt of a HOLD ACKNOWLEDGE message from the SS shall enter to state U10 "Active " with auxiliary state "Call held". The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of call, and receiving a STATUS message indicating the appropriate call state and auxiliary state. Expected sequence Step Direction Message Comments 1 MS Using MMI commands, the MS places the call on hold 2 MS -> SS HOLD 3 SS -> MS STATUS ENQUIRY 4 MS -> SS STATUS State U10, auxiliary state "Hold request" 5 SS -> MS HOLD REJECT 6 SS -> MS STATUS ENQUIRY 7 MS -> SS STATUS State U10, no auxiliary state 8 SS Check that the TCH is through-connected 9 MS Using MMI commands, the MS places the call on hold 10 MS -> SS HOLD 11 SS -> MS STATUS ENQUIRY 12 MS -> SS STATUS State U10, auxiliary state "Hold request" 13 SS -> MS HOLD ACKNOWLEDGE 14 SS -> MS STATUS ENQUIRY 15 MS -> SS STATUS State U10, auxiliary state "Call held"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.3.2.2 Retrieve procedure	Conformance requirement 3GPP TS 04.83 subclause 2.1.3. Applicability MS supporting the Call Hold supplementary service. Test purpose To test the correct operation of the retrieve procedure, and the MS reaction to the following messages sent in response to the RETRIEVE message. 1) RETRIEVE REJECT. 2) RETRIEVE ACKNOWLEDGE. Method of test Specific PICS Statements - PIXIT Statements - Method of retrieving a held call. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have a call of a basic service supported by the MS and applicable to Call Hold as described in 3GPP TS 02.04 table A.1 in state U10 "Active" with auxiliary state "Call held". Foreseen final state of the MS State U10, no auxiliary state. Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall request that the call is placed on RETRIEVE. The MS shall send a RETRIEVE message and enter auxiliary state "retrieve request". On receipt of a RETRIEVE REJECT message from the SS, the MS shall return to state U10 "Active" with auxiliary state "Call held". The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of call, and receiving a STATUS message indicating the appropriate call state and auxiliary state. Using suitable MMI commands, the MS shall again request that the call is placed on RETRIEVE. The MS shall send a RETRIEVE message and enter auxiliary state "retrieve request". On receipt of a RETRIEVE ACKNOWLEDGE message from the SS, the MS shall enter state U10 "Active".The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of call, and receiving a STATUS message indicating the appropriate call state and auxiliary state. Expected sequence Step Direction Message Comments 1 MS Using MMI commands, the MS retrieves the held call 2 MS -> SS RETRIEVE 3 SS -> MS STATUS ENQUIRY 4 MS -> SS STATUS State U10, auxiliary state "Retrieve request" 5 SS -> MS RETRIEVE REJECT 6 SS -> MS STATUS ENQUIRY 7 MS -> SS STATUS State U10, auxiliary state "Call held" 8 MS Using MMI commands, the MS retrieves the held call 9 MS -> SS RETRIEVE 10 SS -> MS STATUS ENQUIRY 11 MS -> SS STATUS State U10, auxiliary state "Retrieve request" 12 SS -> MS RETRIEVE ACKNOWLEDGE 13 SS -> MS STATUS ENQUIRY 14 MS -> SS STATUS State U10, no auxiliary state 15 SS Check that the TCH is through-connected
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.3.2.3 Alternate from one call to the other	Conformance requirement 3GPP TS 04.83 subclause 2.1.4. Test purpose To test that the MS correctly alternates between one call and the other, by placing the active call on hold, and retrieving the previously held call. To test that the MS correctly returns to the original call states in the event of receipt of a HOLD REJECT or RETRIEVE REJECT. Method of test Specific PICS Statements - PIXIT Statements - Method of alternating between an active call and a held call. Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS shall have Call A-B in state U10 "Active", and Call C-B in state U10 "Active" with auxiliary state "Call held". Both calls shall be of a basic service supported by the MS and applicable to Call Hold 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 C-B: State U10, No Auxiliary State. Maximum duration of test 30 s. Procedure Using suitable MMI commands, the MS shall alternate between Call A-B and Call C-B. The MS shall send a HOLD message with the transaction identifier for Call A-B and enter auxiliary state "hold request", and send a RETRIEVE message with the transaction identifier for Call C-B and enter auxiliary state "retrieve request". On receipt of a HOLD ACKNOWLEDGE and RETRIEVE ACKNOWLEDGE message, the MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held", and Call C-B in 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 and auxiliary state. Using suitable MMI commands, the MS shall alternate between Call A-B and Call C-B. The MS shall send a HOLD message with the transaction identifier for Call C-B and enter auxiliary state "hold request", and send a RETRIEVE message with the transaction identifier for Call A-B and enter auxiliary state "retrieve request". On receipt of a HOLD REJECT and RETRIEVE REJECT message, the MS shall have Call A-B remain in state U10 "Active" with auxiliary state "Call held", and Call C-B in 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 and auxiliary state. Expected sequence Step Direction Message Comments 1 MS Using MMI commands, the MS changes from call A-B to call C-B 2 MS -> SS HOLD Transaction identifier for call A-B 3 MS -> SS RETRIEVE Transaction identifier for call C-B 4 SS -> MS STATUS ENQUIRY Transaction identifier for call A-B 5 MS -> SS STATUS Transaction identifier for call A-B, State U10, auxiliary state "Hold request" 6 SS -> MS STATUS ENQUIRY Transaction identifier for call C-B 7 MS -> SS STATUS Transaction identifier for call C-B, State U10, auxiliary state "Retrieve request" 8 SS -> MS HOLD ACKNOWLEDGE Transaction identifier for call A-B 9 SS -> MS RETRIEVE ACKNOWLEDGE Transaction identifier for call C-B 10 SS -> MS STATUS ENQUIRY Transaction identifier for call A-B 11 MS -> SS STATUS Transaction identifier for call A-B, state U10, auxiliary state "Call Held" 12 SS -> MS STATUS ENQUIRY Transaction identifier for call C-B 13 MS -> SS STATUS Transaction identifier for call C-B, state U10, no auxiliary state 14 SS Check that the TCH is through-connected 15 MS Using MMI commands, the MS changes from call C-B to call A-B 16 MS -> SS HOLD Transaction identifier for call C-B 17 MS -> SS RETRIEVE Transaction identifier for call A-B 18 SS -> MS STATUS ENQUIRY Transaction identifier for call C-B 19 MS -> SS STATUS Transaction identifier for call C-B, State U10, auxiliary state "Hold request" 20 SS -> MS STATUS ENQUIRY Transaction identifier for call A-B 21 MS -> SS STATUS Transaction identifier for call A-B, State U10, auxiliary state "Retrieve request" 22 SS -> MS HOLD REJECT Transaction identifier for call C-B 23 SS -> MS RETRIEVE REJECT Transaction identifier for call A-B 24 SS -> MS STATUS ENQUIRY Transaction identifier for call C-B 25 MS -> SS STATUS Transaction identifier for call C-B, state U10, no auxiliary state 26 SS -> MS STATUS ENQUIRY Transaction identifier for call A-B 27 MS -> SS STATUS Transaction identifier for call A-B, state U10, auxiliary state "Call Held" 28 SS Check that the TCH is through-connected
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4 Multi-party supplementary services	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.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.1 Beginning the MultiParty service
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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 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. 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.2 Managing an active MultiParty call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.2.1 Served mobile subscriber
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.2.1.1 Put the MultiParty call on hold
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 A-C, state U10, auxiliary state "Call in MPTY". Maximum duration of test 45 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 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. 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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 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. 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, 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.2.1.2 Create a private communication with one of the remote parties
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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, 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
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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. 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.2.2 Remote parties
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.3 Managing a held MultiParty call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.3.1 Retrieve the held MultiParty call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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 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 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. 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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 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. 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, 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.4 Managing a single call and a MultiParty call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.4.1 Served mobile subscriber
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.4.1.1 Disconnect the single call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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 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. 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.4.1.2 Disconnect the MultiParty call
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.4.1.2.1 Void
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.4.1.2.2 Void
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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. 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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. 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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.4.4.3 Add the single call to the MPTY
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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 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
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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"
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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. 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
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	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: 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. 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
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.5 Community of interest supplementary services	(Reserved).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6 Charging supplementary services	The following Advice of Charge abbreviations are used in this subclause: AoC Advice of Charge AoCC Advice of Charge Charging AoCI Advice of Charge Information ACM Accumulated Charge Meter ACMmax Accumulated Charge Meter Maximum CCM Current Call Meter CAI Charge Advice Information CDUR Chargeable Duration The following other abbreviations are used: IE Information Element FIE Facility Information Element TCH Traffic CHannel General on Advice of Charge. The purpose of these tests is to verify that the MS under test correctly performs procedures related to the AoC supplementary service. The reasons for these test purposes are: - One example of a possible use for AoCC is in applications where the subscriber hires out a GSM ME and SIM to a user and bills the user according to the charge stored on the SIM at the end of the hire period. If a mobile station claims to support AoCC but does so incorrectly or not at all, this may cause the subscriber to mischarge the user of the hire phone. Hence an MS claiming to support AoCC must be shown to be reliable in that context. - Since AoCC offers the use of telecommunication services according to the charge stored independently in the MS, the AoCC service must not be susceptible to fraud at the MS end. - To ensure that a mobile station not claiming to support AoCC does not respond with a signal to the network indicating that it does. This could cause the network to allow the call to be placed without any charge being inserted on to the SIM. Mobile originating and terminating speech AoC calls are tested and if supported, Call Hold and Multi-party calls. The type testing of data calls (i.e. those calls with a volume related charging component) will not be specified at the phase 2 stage but will be deferred to phase 2+ since the interaction of AoC with packet services is not yet defined in 3GPP TS 09.06 and 3GPP TS 09.07. Tests are made on the ME-SIM interface to ensure that call charges are being correctly stored in the ACM field of the SIM in several situations. The AoC ACMmax function is also tested for incoming and outgoing calls. Basic service verification tests for the AoCC, Call Hold, and Multi-party supplementary services which have direct relevance to the testing of AoC have been added to 3GPP TS 11.10, subclauses 11.3, 11.4 and 11.5 respectively.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1 Advice of Charge Charging
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.1 AoCC time related charging / MS originated call	Purpose: 1) To verify that when the MS receives the AoCC parameters in a Facility IE which is contained in the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s. 2) To verify that when the MS receives the AoCC parameters in a Facility IE which is contained in a CONNECT message and when a TCH has already been assigned, the MS stores the correct value in the ACM field of the SIM. 3) To verify that the when the call has no volume related component the MS ignores non-zero AoCC e5, e6 parameters sent to it. Conformance Requirement(s): 1) When the MS receives the AoCC parameters in a Facility IE which is contained in a CONNECT message and when a TCH has already been assigned, the MS shall return a FACILITY message containing the acknowledgement within 1 s. 2) When the MS receives the AoCC parameters in a Facility IE which is contained in a CONNECT or FACILITY message and when a TCH has already been assigned, the MS shall store the correct value in the ACM field of the SIM. 3) When the call has no volume related component the MS shall ignore non-zero AoC e5 and e6 parameters sent to it. Reference(s): Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86. Conformance requirement 2: 3GPP TS 02.24. Conformance requirement 3: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE. The SS sends the DISCONNECT y seconds after sending the CONNECT message containing the CAI. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. The test is repeated for several different sets of e-parameters as defined below. Maximum Duration of Test: 30 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,...,5. Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either A or B branch is taken A12 MS -> SS CONNECT ACKNOWLEDGE A13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B13 MS -> SS CONNECT ACKNOWLEDGE 14 call duration y seconds after CAI information sent by SS 15 SS -> MS DISCONNECT 16 MS -> SS RELEASE 17 SS -> MS RELEASE COMPLETE 18 SS -> MS CHANNEL RELEASE The main signalling link is released. 19 MS SIM contents checked (either via MMI or by removing the SIM and using SIM reader). ACM shall have been incremented correctly. NOTE: The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. y is set to a constant value of 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below: k-value e-parameter CCM Total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 6 14 1 25 0 0 60 43 43 2 0 0 1 100 0 0 0 100 143 3 250 16 2 500 0 0 60 2 000 2 143 4 1 1 1 0 10 10 1 89 or 90 2 232 or 2 233 5 12,5 30 1 25 10 10 30 50 or 62,5 2 295, 2 296, 2 282 or 2 283 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. The ASN.1 description for each e-parameter allows integers in the range 0 to 8191 to be transmitted but some e-parameters have different actual ranges (e.g. e1 can take any value 0..819,1 with 0,1 resolution). The MS knows how to interpret the received parameter (e.g. received e1 refers to 10 times actual e1, see 3GPP TS 04.80 subclause 4.4.3). Therefore e1=12,5 would be sent to the MS as 125. The MS knows the value sent is 10 times the "real" e1 and hence interprets the value as 12,5. The non-zero e5 and e6 values for the k=4 and k=5 execution of the test are to check that the MS ignores the volume related parameters when carrying out time only related charging. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.2 AoCC time related charging / MS terminated call	Purpose: 1) To verify that when the MS receives certain AoCC e-parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s. 2) To verify that when the MS receives the AoCC parameters in a Facility IE which is contained in a FACILITY message and when a TCH has already been assigned, the MS stores the correct value in the ACM field of the SIM. Conformance Requirement(s): 1) When the MS receives the AoCC parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS shall return a Facility message containing the acknowledgement within 1 s. 2) When the MS receives the AoCC parameters in a Facility IE which is contained in a FACILITY message and when a TCH has already been assigned, the MS shall store the correct value in the ACM field of the SIM. Reference(s): Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86. Conformance requirement 2: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The SS is made to initiate a call. The call is established and certain AoCC e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCC acknowledgement within 1 s of the FACILITY message. It is an implementation option whether the AoCC e-parameters and the AoCC acknowledge are sent before or after the CONNECT ACKNOWLEDGE. The SS sends the DISCONNECT y seconds after sending the FACILITY message. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. The test is repeated for several different sets of e-parameters as defined below. Maximum Duration of Test: 30 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,...,5. Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 SS The SS is made to initiate a call 2 SS -> MS PAGING REQUEST 3 MS -> SS CHANNEL REQUEST 4 SS -> MS IMMEDIATE ASSIGNMENT 5 MS -> SS PAGING RESPONSE 6 SS -> MS SETUP 7 MS -> SS CALL CONFIRMED 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 MS -> SS ALERTING 11 MS -> SS CONNECT 12 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below Either A or B branch is taken A13 SS -> MS CONNECT ACKNOWLEDGE A14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B14 SS -> MS CONNECT ACKNOWLEDGE 15 call duration y seconds after CAI information sent by SS 16 SS -> MS DISCONNECT 17 MS -> SS RELEASE 18 SS -> MS RELEASE COMPLETE 19 SS -> MS CHANNEL RELEASE The main signalling link is released. 20 MS SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. NOTE: The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. y is set to a constant value of 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 0 0 0 0 0 0 0 0 0 2 0 0 1 100 0 0 0 100 100 3 6 14 1 25 0 0 60 43 143 4 1 1 1 0 0 0 1 89 or 90 233 or 232 5 12,5 30 1 25 0 0 30 50 or 62,5 296, 295, 282 or 283 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.3 AoCC volume related charging / MS originated call	Future addition at GSM Phase 2+ stage.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.4 AoCC volume related charging / MS terminated call	Future addition at GSM Phase 2+ stage.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.5 Change in charging information during a call	Purpose: 1) To verify that when the MS receives new AoCC parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS returns a FACILITY message containing the acknowledgement within 1 s. 2) To verify that when the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information. Conformance Requirement(s): 1) When the MS receives new AoCC parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS shall return a FACILITY message containing the acknowledgement within 1 s. 2) When the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information. Reference(s): Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86. Conformance requirement 2: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc) PIXIT Statements - Method of reading ACM from the SIM via the ME. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in a FACILITY message sent after the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of the FACILITY message. x seconds after sending the original CAI, new (and different) e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCC acknowledge within 1 s of the FACILITY message. The SS sends the DISCONNECT y seconds after sending the first CAI in the FACILITY message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and the times for the two parts of the call. Maximum Duration of Test: 10 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT Either A, B or C branch is taken A12 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below A13 MS -> SS CONNECT ACKNOWLEDGE A14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 MS -> SS CONNECT ACKNOWLEDGE B13 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below B14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below C12 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below C13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below C14 MS-> SS CONNECT ACKNOWLEDGE Second CAI sent x sec after first CAI 15 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in iii below 16 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below New CAI held in abeyance until CDUR has timed out present e2 value 17 Call duration y seconds after first CAI information sent by SS 18 SS -> MS DISCONNECT 19 MS -> SS RELEASE 20 SS -> MS RELEASE COMPLETE 21 SS -> MS CHANNEL RELEASE The main signalling link is released. 22 MS SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly NOTE The values of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x, y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. The values of the e-parameters within the parameter part of the Facility Information Element shall be set as defined below: e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 10 28 1 10 0 0 60 (30) (30) Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4. iii) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x is set to a constant value of 80 s. y is set to a constant value of 180 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 10 14 1 5 0 0 60 65 65 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.6 Different formats of charging information	Purpose: 1) To verify that when the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated is the same as that when the same e-parameters are completely omitted from the Facility IE. 2) To verify the operation of a shortened channel release procedure where the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message. Conformance Requirement(s): 1) When the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated shall be the same as that when the same e-parameters are completely omitted from the Facility IE. 2) The channel shall be correctly released when a shortened channel release procedure is used - the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message. Reference(s): Conformance requirement 1: 3GPP TS 02.24. Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: Part 1: The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in a FACILITY message sent before the CONNECT message. The SS sends the DISCONNECT y seconds after sending the FACILITY message containing the e-parameters. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. Part 2: Part 1 is repeated twice with the e-parameters that were set to zero above now omitted completely from the Facility IE. The shortened release procedures are used. The MS shall have stored the correct amount on the SIM. The results of parts 1 and 2 are compared. The value for the charge calculated by the MS shall be identical for parts 1 and 2. Maximum Duration of Test: 20 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,..3. Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below Either A, B or C branch is taken A12 SS -> MS CONNECT A13 MS -> SS CONNECT ACKNOWLEDGE A14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 SS -> MS CONNECT B13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B14 MS -> SS CONNECT ACKNOWLEDGE C12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below C13 SS -> MS CONNECT C14 MS -> SS CONNECT ACKNOWLEDGE 15 call duration y seconds after CAI information sent by SS Branch D, E and F shall be taken for k= 1,2 and 3 respectively D16 SS -> MS DISCONNECT D17 MS -> SS RELEASE D18 SS -> MS RELEASE COMPLETE D19 SS -> MS CHANNEL RELEASE The main signalling link is released. E16 SS -> MS RELEASE COMPLETE Shortened channel release procedure E17 SS -> MS CHANNEL RELEASE The main signalling link is released. F16 SS -> MS CHANNEL RELEASE 20 MS SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. NOTE The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. y is set to a constant value of 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 10 40 1 0 0 0 0 20 20 2 10 40 1 ---------omitted--------- 20 40 3 10 40 1 ---------omitted--------- 20 60 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.7 AoCC on a Call Hold call	Purpose: 1) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCC acknowledgement within 1 s of transmission of each set of e-parameters. 2) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM records the sum of all the charges for the services currently being used and hence that the ME inserts the correct charge in the ACM field of the SIM. Conformance Requirement(s) 1) When the MS invokes a Call Hold call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCC acknowledgement within 1 s of receiving each set of e-parameters. 2) When the MS invokes a Call Hold call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM shall record the sum of all the charges for the services currently being used and hence the ME shall insert the correct charge in the ACM field of the SIM. Reference(s): Conformance requirement 1: 3GPP TS 04.13. Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of transmission of the CONNECT message. The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call. The MS is made to initiate a second call (call C). The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement in a FACILITY message within 1 s of transmission of the CONNECT message. The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT/FACILITY message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT/FACILITY message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and call times x and y. Maximum Duration of Test: 10 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either D or E branch is taken D12 MS -> SS CONNECT ACKNOWLEDGE D13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E13 MS -> SS CONNECT ACKNOWLEDGE 14 MS The MS is made to initiate a second call, and the first call is placed on hold. DTMF signalling may occur, when MMI keys are depressed 15 MS -> SS HOLD 16 SS -> MS HOLD ACKNOWLEDGE 17 MS -> SS CM SERVICE REQUEST 18 SS -> MS CM SERVICE ACCEPT 19 MS -> SS SETUP TI arbitrary but different from existing TI 20 SS -> MS CALL PROCEEDING 21 SS -> MS ALERTING 22 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either F or G branch is taken F23 MS -> SS CONNECT ACKNOWLEDGE F24 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G23 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G24 MS -> SS CONNECT ACKNOWLEDGE 25 Call durations x and y seconds after respective CAI information sent by SS Branch H and I branch are taken, the sequence depending on the durations x and y For call C H26 SS -> MS DISCONNECT y seconds after call C CAI sent H27 MS -> SS RELEASE H28 SS -> MS RELEASE COMPLETE For call B I26 SS -> MS DISCONNECT x seconds after call B CAI sent I27 MS -> SS RELEASE I28 SS -> MS RELEASE COMPLETE 29 SS -> MS CHANNEL RELEASE The main signalling link is released 30 MS SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. NOTE The value of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x set to 180 s, y is set to 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: Call e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 B(time x) 7 40 1 0 0 0 0 C(time y) 13 40 1 0 0 0 0 54 54 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.1.8 AoCC on a Multi-party call	Purpose: 1) To verify that when the MS invokes a Multi-party call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCC acknowledgement within 1 s of transmission of each set of e-parameters. 2) To verify that when the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM records the sum of all the charges for the services currently being used and hence the ME inserts the correct charge in the ACM field of the SIM. Conformance Requirement(s): 1) When the MS invokes a Multi-party call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCC acknowledgement within 1 s of receiving each set of e-parameters. 2) When the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM shall record the sum of all the charges for the services currently being used and hence the ME shall insert the correct charge in the ACM field of the SIM. Reference(s): Conformance requirement 1: 3GPP TS 04.13. Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of transmission of the CONNECT message. The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call. The MS is made to initiate a second call (call C). The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCC acknowledgement within 1 s of transmission of the CONNECT message. The MS invokes the multi-party service by sending a FACILITY message to the SS containing the BuildMPTY request. The SS accepts the request and connects the MS with the other existing connections (active call C and held call B) and confirms with a FACILITY message. The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and call times x and y. Maximum Duration of Test: 10 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either D or E branch is taken D12 MS -> SS CONNECT ACKNOWLEDGE D13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E13 MS -> SS CONNECT ACKNOWLEDGE 14 MS -> SS HOLD The MS is made to initiate a second call and the first call (call B) is placed on hold. DTMF signalling may occur, when MMI keys are depressed 15 MS->SS HOLD 16 SS -> MS HOLD ACKNOWLEDGE 17 MS -> SS CM SERVICE REQUEST 18 SS -> MS CM SERVICE ACCEPT 19 MS -> SS SETUP TI arbitrary but different from existing TI 20 SS -> MS CALL PROCEEDING 21 SS -> MS ALERTING 22 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either F or G branch is taken F23 MS -> SS CONNECT ACKNOWLEDGE F24 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G23 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G24 MS -> SS CONNECT ACKNOWLEDGE The MS is made to build a multi-party call. DTMF signalling may occur, when MMI keys are depressed 25 MS -> SS FACILITY (TI A-B/A-C) As default message except contains Facility IE with contents as indicated in iii below 26 SS -> MS FACILITY (TI A-B/A-C) As default message except contains Facility IE with contents as indicated in iv, below 27 Call durations x and y seconds after respective CAI information sent by SS Branch H and branch I are taken, the sequence depending on the durations x and y For call C H28 SS -> MS DISCONNECT y seconds after call C CAI sent H29 MS -> SS RELEASE H30 SS -> MS RELEASE COMPLETE For call B I28 SS -> MS DISCONNECT x seconds after call B CAI sent I29 MS -> SS RELEASE I30 SS -> MS RELEASE COMPLETE 31 SS -> MS CHANNEL RELEASE The main signalling link is released. 32 MS SIM contents checked (either via MMI or by removing the SIM and using SIM reader) ACM shall have been incremented correctly. NOTE: A-B/A-C indicates a choice. the transaction identifier (TI) used must be that of the active call or the held call (ref. 3GPP TS 04.84). The values of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x set to 180 s, y set to 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: Call e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 B(time x) 19 40 1 0 0 0 0 C(time y) 29 40 1 0 0 0 0 134 134 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4. iii) FACILITY Information Element with Invoke = BuildMPTY component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. The following abbreviations are used in the descriptions below: U Universal tag class. CS Context Specific tag class. P Primitive tag form. C Constructed tag form. FIE Facility Information Element. Contents Facility IE Identifier Value/remark As 3GPP TS 04.80 Coding 00011100 Length of FIE contents 8 00001000 Component type tag CS/C/tag=1 10100001 Component length 6 00000110 Invoke ID tag U/P/tag=2 00000010 Invoke ID length 1 00000001 Invoke ID Arbitrary (1 octet) (00000000) Op-Code tag From 3GPP TS 04.80 00000010 Op-Code length 1 00000001 Op-Code Build Multi-party operation (local value 124) 00000001 ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Facility IE Identifier Value/remark As 3GPP TS 04.80 Coding 00111100 Length of FIE contents 5 00001001 Component type tag CS/C/tag=2 10100010 Component length 3 00000011 Invoke ID tag U/P/Integer 00000010 Invoke ID length 1 00000001 Invoke ID Same as used as Invoke ID in Invoke FIE (00000000)
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.2 Charge Storage
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.2.1 Removal of SIM during an active call	Purpose: 1) To verify that when the SIM is removed from the ME during an active AoCC call the ME immediately terminates the call. 2) To verify that when the SIM is removed during an active AoCC call the ME has written the total charge up to that point in the call to the ACM field of the SIM. Conformance Requirement(s): 1) When the SIM is removed from the ME during an active AoCC call the ME shall immediately terminate the call. 2) When the SIM is removed during an active AoCC call midway through an AoC charging time interval (e7 or e2) the ME shall have written the total charge up to the point in the call where the charging time interval last expired to the ACM field of the SIM. Reference(s): Conformance requirement 1: 3GPP TS 02.17. Conformance requirement 1: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: This test is only performed if it is possible to remove SIM without disconnecting the power supply. If the battery pack must be removed to get at the SIM see subclause 31.6.2.2. The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE. If possible, without removing the power supply, the SIM is removed from the ME y seconds after the SS sends the CAI in the CONNECT/FACILITY message. The call shall be terminated immediately by the MS and the MS shall have stored the correct amount on the SIM according to the e-parameters sent. Maximum Duration of Test: 5 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either A or B branch is taken A12 MS -> SS CONNECT ACKNOWLEDGE A13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B13 MS -> SS CONNECT ACKNOWLEDGE 14 SIM removed y seconds after CAI information sent by SS. Either C, D, E or F branch is taken C15 MS -> SS DISCONNECT C16 SS -> MS RELEASE C17 MS -> SS RELEASE COMPLETE C18 SS -> MS CHANNEL RELEASE The main signalling link is released. D15 MS -> SS RELEASE COMPLETE D16 SS -> MS CHANNEL RELEASE The main signalling link is released. E15 MS -> SS Layer 2 DISC E16 SS -> MS UA F15 No further messages are sent 19 SIM contents checked (by removing the SIM and using SIM reader). ACM shall have been incremented correctly. NOTE: The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. The SIM is removed after approximately y=90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 10 55 1 10 0 0 10 30 30 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.2.2 Interruption of power supply during an active call	Purpose: To verify that when the power supply of the MS is removed during an active AoCC call the ME has written the total charge up to that point in the call to the ACM field of the SIM. Conformance Requirement(s): When the power supply of the MS is removed during an active AoCC call midway through an AoC charging time interval (e7 or e2) the ME shall have written the total charge up to the point in the call where the charging time interval last expired to the ACM field of the SIM. Reference(s): Conformance requirement 1: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of removing power supply. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is switched off. Method of Test: The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE. The ME power is switched off by pressing power button on MMI during the active call. The call shall be terminated immediately and the MS shall have stored the correct amount on the SIM according to the e-parameters sent. The test is repeated for ME power being lost by removal of battery pack. The call shall be terminated immediately and the MS shall have stored the correct amount on the SIM according to the e-parameters sent. Maximum Duration of Test: 10 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,2. Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either A or B branch is taken A12 MS -> SS CONNECT ACKNOWLEDGE A13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B13 MS -> SS CONNECT ACKNOWLEDGE 14 ME power interrupted y seconds after CAI information sent by SS by: MMI power switch (for k=1) Removing battery pack (for k=2) Depending on the value of k C or D branch is taken 15 SIM contents checked (by removing the SIM and using SIM reader). ACM shall have been incremented correctly. NOTE: The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. The ME power is removed after approximately y=90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 10 55 1 10 0 0 10 30 30 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.2.3 MS going out of coverage during an active AoCC call	NOTE: At present the core recommendations for AoCC in the case where the radio link is lost during an active call are vague. Does the mobile go on charging for a fixed period after radio link loss and continue as usual if radio link reestablishment occurs, or does charging stop? Input from people involved in charging for GSM is required. Hence this test will be enhanced in the future when the requirements become clearer. Purpose: To verify that when the MS goes out of radio coverage area and an active call is dropped the ME has written the total charge up to that point in the call to the ACM field of the SIM. Conformance Requirement(s): When the MS goes out of radio coverage area during an active AoCC call midway through an AoC charging time interval (e7 or e2) and the call is dropped the ME shall have written the total charge up to the point in the call where the charging time interval last expired to the ACM field of the SIM. Reference(s): Conformance requirement 1: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCC e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE. The cell simulated by the system simulator is then switched off to model the MS losing radio coverage. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. [What happens on call reestablishment?] Maximum Duration of Test: 5 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either A or B branch is taken A12 MS -> SS CONNECT ACKNOWLEDGE A13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B13 MS -> SS CONNECT ACKNOWLEDGE 14 SS cell switched off y seconds after CAI information sent by SS Failure of radio path, end of call (CEND) occurs and MS stops charging (ref. 3GPP TS 02.24 sec 2) 15 SIM contents checked (either via MMI or by removing the SIM and using SIM reader). ACM shall have been incremented correctly. NOTE: The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. The cell being simulated by the SS is switched off after approximately y=90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 10 55 1 10 0 0 10 30 30 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.2.4 ACMmax operation / Mobile Originating	Purpose: 1) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any outgoing calls in progress for which a non-zero CAI exists are terminated by the ME, with cause value #68 once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user. 2) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of non-emergency calls is inhibited. 3) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of emergency calls is uninhibited. Conformance Requirement(s): 1) When the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any outgoing calls in progress for which a non-zero CAI exists shall be terminated by the ME with cause value #68, once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user. 2) When the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of further non-emergency calls shall be inhibited. 3) When the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the making of emergency calls shall be uninhibited. Reference(s): Conformance requirement 1: 3GPP TS 02.24, 3GPP TS 04.86 subclause 2.3. Conformance requirement 2: 3GPP TS 02.24. Conformance requirement 3: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Type of user indication when ACMmax exceeded. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". PIN 2 is entered into the MS allowing modification of both the ACM and ACMmax fields on the SIM. The ACM is reset to zero and the ACMmax is set to 2 units. Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCC non-zero e-parameters sent in a Facility IE in the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent before or after the CONNECT ACKNOWLEDGE. After the ACM has been incremented to 2 units (60 s) the call shall be terminated by the MS once an additional chargeable interval of 30 s has elapsed, and an indication given to the user. The call duration is recorded and the ACM is checked to ensure it has been incremented to 2 units. The MS is then made to attempt to originate an ordinary call to the MS for which a non-zero CAI exists for the calling party and shall be unsuccessful. The MS shall not send a CHANNEL REQUEST for that call. The MS is then made to attempt to originate an emergency call and shall be successful. Maximum Duration of Test: 10 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM (it shall be zero) For k= 1 A1 MS The MS is made to initiate an ordinary call A2 MS -> SS CHANNEL REQUEST A3 SS -> MS IMMEDIATE ASSIGNMENT A4 MS -> SS CM SERVICE REQUEST A5 SS -> MS CM SERVICE ACCEPT A6 MS -> SS SETUP A7 SS -> MS CALL PROCEEDING A8 SS -> MS ASSIGNMENT COMMAND to a supported channel type A9 MS -> SS ASSIGNMENT COMPLETE A10 SS -> MS ALERTING A11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in I below For k = 3 B1 MS The MS is made to initiate an emergency call B2 MS -> SS CHANNEL REQUEST Establishment cause is emergency call establishment B3 SS -> MS IMMEDIATE ASSIGNMENT B4 MS -> SS CM SERVICE REQUEST CM service type IE indicates "emergency call establishment" B5 SS -> MS CM SERVICE ACCEPT B6 MS -> SS EMERGENCY SETUP B7 SS -> MS CALL PROCEEDING B8 SS -> MS ASSIGNMENT COMMAND to a supported channel type B9 MS -> SS ASSIGNMENT COMPLETE B10 SS -> MS ALERTING B11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below For k=1 or 3 either branch C or D is taken C12 MS -> SS CONNECT ACKNOWLEDGE C13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below D12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below D13 MS -> SS CONNECT ACKNOWLEDGE For k=1 L14 Record call duration, x seconds, after CAI information sent by SS until call is terminated by the ME L15 MS -> SS DISCONNECT Cause value #68 L16 SS -> MS RELEASE L17 MS -> SS RELEASE COMPLETE L18 SS -> MS CHANNEL RELEASE The main signalling link is released. L19 ACM checked (shall be 2 units) For k=3 M14 Call duration y seconds after CAI information sent by SS M15 MS -> SS DISCONNECT M16 SS -> MS RELEASE M17 MS -> SS RELEASE COMPLETE M18 SS -> MS CHANNEL RELEASE The main signalling link is released. M19 ACM checked (shall be 2 units) k=1 - Non zero CAI call attempted by MS and should succeed. k=2 - Non zero CAI call attempted by MS and should fail. k=3 - Emergency call attempted by MS and should succeed. NOTE: The values of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x shall be 90 ± 2 s. y shall be set to 120 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 1 30 1 0 0 0 0 2 2 2 1 30 1 0 0 0 0 0 2 3 0 0 0 0 0 0 0 0 2 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.2.5 ACMmax operation / Mobile Terminating	Purpose: 1) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any mobile terminating calls in progress for which a non-zero CAI exists are terminated by the ME with cause value #68, once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user. 2) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, and an incoming call is received for which subsequently a non-zero CAI is received, then the call is terminated by the ME using cause value #68 with an appropriate indication given to the user. 3) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the receiving of calls for which the CAI is zero is uninhibited. Conformance Requirement(s): 1) When the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any mobile terminating calls in progress for which a non-zero CAI exists shall be terminated by the ME with cause value #68, once the chargeable interval determined by the CAI has elapsed, with an appropriate indication given to the user. 2) When the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, and an incoming call is received for which subsequently a non-zero CAI is received, the call shall be terminated by the ME using cause value #68 with an appropriate indication given to the user. 3) When the value stored in the ACM becomes equal to or exceeds its maximum limit, the ACMmax, the receiving of calls for which the CAI is zero shall be uninhibited. Reference(s): Conformance requirement 1: 3GPP TS 02.24, 3GPP TS 04.86 subclause 2.3. Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.86 subclause 2.3. Conformance requirement 2: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Method of reading ACM from the SIM via the ME. - Type of user indication when ACMmax exceeded. - Support for active state of the call control protocol (U10). Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". PIN 2 is entered into the MS allowing modification of both the ACM and ACMmax fields on the SIM. The ACM is reset to zero and the ACMmax is set to 2 units. Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The SS is made to initiate a call. The call is established with certain non-zero AoCC e-parameters sent in a Facility IE contained in a FACILITY message sent before the CONNECT message. It is an implementation option whether the AoCC e-parameters and AoCC acknowledge are sent before or after the CONNECT ACKNOWLEDGE. After the ACM has been incremented to 2 units (60s) the call shall be terminated by the MS once an additional chargeable interval of 30s has elapsed and an indication given to the user. The ACM shall be checked to ensure that it has been incremented to 2 units. The SS is then made to attempt to make an ordinary call to the MS for which a non-zero CAI exists for the called party and shall be unsuccessful. The MS shall terminate the call with a DISCONNECT message. The SS is then made to attempt to make an ordinary call to the MS for which a zero CAI exists for the called party and shall be successful. Maximum Duration of Test: 10 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,...,3.. Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 SS The SS is made to initiate a call 2 SS -> MS PAGING REQUEST 3 MS -> SS CHANNEL REQUEST 4 SS -> MS IMMEDIATE ASSIGNMENT 5 MS -> SS PAGING RESPONSE 6 SS -> MS SETUP 7 MS -> SS CALL CONFIRMED 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 MS -> SS ALERTING 11 MS -> SS CONNECT 12 SS -> MS CONNECT ACKNOWLEDGE For k=1 or 3 branch A is taken A13 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below A14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below For k=2 branch B, and then either branch C, D or E is taken B13 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below C13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below C14 MS -> SS DISCONNECT MS terminates call with cause value #68 D13 MS -> SS DISCONNECT MS terminates call with cause value #68 D14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E13 MS -> SS DISCONNECT MS terminates call with cause value #68. DISCONNECT may or may not contain Facility IE with contents as indicated in ii below For k= 1, 2 and 3, F, G and branch shall be taken respectively For k=1 F15 Record call duration, x seconds, after CAI information sent by SS until call is terminated by the ME F16 MS -> SS DISCONNECT MS terminates call with cause value #68 F17 SS -> MS RELEASE F18 MS -> SS RELEASE COMPLETE F19 SS -> MS CHANNEL RELEASE The main signalling link is released. For k=2 G15 SS -> MS RELEASE G16 MS -> SS RELEASE COMPLETE RELEASE COMPLETE may or may not contain Facility IE with contents as indicated in ii below G17 SS -> MS CHANNEL RELEASE The main signalling link is released. For k=3 H15 Call duration y seconds after CAI information sent by SS H16 MS -> SS DISCONNECT MS terminates call H17 SS -> MS RELEASE H18 MS -> SS RELEASE COMPLETE H19 SS -> MS CHANNEL RELEASE The main signalling link is released. 20 ACM checked (should be 2 units) k=1 - Non zero CAI call attempted to MS and should succeed. k=2 - Non zero CAI call attempted to MS and should fail. k=3 - Zero CAI call attempted to MS and should succeed. NOTE: The values of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x shall be 90 ± 2 s. y shall be set to 120 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 1 30 1 0 0 0 0 2 2 2 1 30 1 0 0 0 0 0 2 3 0 0 0 0 0 0 0 0 2 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3 Advice of Charge Information
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.1 AoCI time related charging / MS originated call	Purpose: 1) To verify that when the MS receives the AoCI parameters in a Facility IE which is contained in the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s. 2) To verify that the when the call has no volume related component the MS ignores non-zero AoCI e5, e6 parameters sent to it. Conformance Requirement(s): 1) When the MS receives the AoCI parameters in a Facility IE which is contained in a CONNECT message and when a TCH has already been assigned, the MS shall return a FACILITY message containing the acknowledgement within 1 s. 2) When the call has no volume related component the MS shall ignore non-zero AoC e5 and e6 parameters sent to it. Reference(s): Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86. Conformance requirement 2: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Support for active state of the call control protocol (U10). - MMI method of reading the AoCI information. Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of the CONNECT message. It is an implementation option whether the AoCI acknowledge is sent by the MS before or after the CONNECT ACKNOWLEDGE. The SS sends the DISCONNECT y seconds after sending the CONNECT message containing the CAI. The test is repeated for several different sets of e-parameters as defined below. Maximum Duration of Test: 30 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,...,5. Step Direction Message Comments 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either A or B branch is taken A12 MS -> SS CONNECT ACKNOWLEDGE A13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B13 MS -> SS CONNECT ACKNOWLEDGE 14 call duration y seconds after CAI information sent by SS 15 SS -> MS DISCONNECT 16 MS -> SS RELEASE 17 SS -> MS RELEASE COMPLETE 18 SS -> MS CHANNEL RELEASE The main signalling link is released. 19 MS MS display is checked to determine whether the correct call charge has been indicated NOTE: The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. y is set to a constant value of 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 6 14 1 25 0 0 60 43 43 2 0 0 1 100 0 0 0 100 143 3 250 16 2 500 0 0 60 2 000 2 143 4 1 1 1 0 10 10 1 89 or 90 2 232 or 2 233 5 12,5 30 1 25 10 10 30 50 or 62,5 2 295, 2 296, 2 282 or 2 283 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. The ASN.1 description for each e-parameter allows integers in the range 0 to 8 191 to be transmitted but some e-parameters have different actual ranges (e.g. e1 can take any value 0..819,1 with 0,1 resolution). The MS knows how to interpret the received parameter (e.g. received e1 refers to 10 times actual e1, see 3GPP TS 04.80 subclause 4.4.3). Therefore e1=12,5 would be sent to the MS as 125. The MS knows the value sent is 10 times the "real" e1 and hence interprets the value as 12,5. The non-zero e5 and e6 values for the k=4 and k=5 execution of the test are to check that the MS ignores the volume related parameters when carrying out time only related charging. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.2 AoCI time related charging / MS terminated call	Purpose: 1) To verify that when the MS receives certain AoCI e-parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s. Conformance Requirement(s): 1) When the MS receives the AoCI parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS shall return a Facility message containing the acknowledgement within 1 s. Reference(s): Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86. Conformance requirement 2: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Support for active state of the call control protocol (U10). - MMI method of reading the AoCI information. Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The SS is made to initiate a call. The call is established and certain AoCI e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCI acknowledgement within 1 s of the FACILITY message. It is an implementation option whether the AoCI e-parameters and the AoCI acknowledge are sent before or after the CONNECT ACKNOWLEDGE. The SS sends the DISCONNECT y seconds after sending the FACILITY message. The test is repeated for several different sets of e-parameters as defined below. Maximum Duration of Test: 30 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,...,5. Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 SS The SS is made to initiate a call 2 SS -> MS PAGING REQUEST 3 MS -> SS CHANNEL REQUEST 4 SS -> MS IMMEDIATE ASSIGNMENT 5 MS -> SS PAGING RESPONSE 6 SS -> MS SETUP 7 MS -> SS CALL CONFIRMED 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 MS -> SS ALERTING 11 MS -> SS CONNECT 12 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below Either A or B branch is taken A13 SS -> MS CONNECT ACKNOWLEDGE A14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B14 SS -> MS CONNECT ACKNOWLEDGE 15 call duration y seconds after CAI information sent by SS 16 SS -> MS DISCONNECT 17 MS -> SS RELEASE 18 SS -> MS RELEASE COMPLETE 19 SS -> MS CHANNEL RELEASE The main signalling link is released. 20 MS MS display is checked to determine whether the correct call charge has been indicated NOTE: The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. y is set to a constant value of 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set as below: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 0 0 0 0 0 0 0 0 0 2 0 0 1 100 0 0 0 100 100 3 6 14 1 25 0 0 60 43 143 4 1 1 1 0 0 0 1 89 or 90 233 or 232 5 12,5 30 1 25 0 0 30 50 or 62,5 296, 295, 282 or 283 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.3 AoCI volume related charging / MS originated call	Future addition at GSM Phase 2+ stage.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.4 AoCI volume related charging / MS terminated call	Future addition at GSM Phase 2+ stage.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.5 Change in charging information during a call	Purpose: 1) To verify that when the MS receives new AoCI parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS returns a FACILITY message containing the acknowledgement within 1 s. 2) To verify that when the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information. Conformance Requirement(s): 1) When the MS receives new AoCI parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS shall return a FACILITY message containing the acknowledgement within 1 s. 2) When the MS receives new charging information mid-way through a call in the form of a Facility IE contained within a FACILITY message the MS correctly indicates the total charge considering both sets of charging information. Reference(s): Conformance requirement 1: 3GPP TS 03.86, 3GPP TS 04.13, 3GPP TS 04.86. Conformance requirement 2: 3GPP TS 02.24. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Support for active state of the call control protocol (U10). - MMI method of reading the AoCI information. Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in a FACILITY message sent after the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of the FACILITY message. x seconds after sending the original CAI, new (and different) e-parameters are sent to the MS in a Facility IE contained within a FACILITY message. The MS shall return the AoCI acknowledge within 1 s of the FACILITY message. The SS sends the DISCONNECT y seconds after sending the first CAI in the FACILITY message. Maximum Duration of Test: 10 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT Either A, B or C branch is taken A12 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below A13 MS -> SS CONNECT ACKNOWLEDGE A14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 MS -> SS CONNECT ACKNOWLEDGE B13 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below B14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below C12 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below C13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below C14 MS-> SS CONNECT ACKNOWLEDGE Second CAI sent x sec after first CAI 15 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in iii below 16 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below New CAI held in abeyance until CDUR has timed out present e2 value 17 Call duration y seconds after first CAI information sent by SS 18 SS -> MS DISCONNECT 19 MS -> SS RELEASE 20 SS -> MS RELEASE COMPLETE 21 SS -> MS CHANNEL RELEASE The main signalling link is released. 22 MS MS display is checked to determine whether the correct call charge has been indicated NOTE The values of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x, y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. The values of the e-parameters within the parameter part of the Facility Information Element shall be set as defined below: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 10 28 1 10 0 0 60 (30) (30) Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4. iii) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x is set to a constant value of 80 s. y is set to a constant value of 180 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 10 14 1 5 0 0 60 65 65 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.6 Different formats of charging information	Purpose: 1) To verify that when the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated is the same as that when the same e-parameters are completely omitted from the Facility IE. 2) To verify the operation of a shortened channel release procedure where the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message. Conformance Requirement(s): 1) When the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated shall be the same as that when the same e-parameters are completely omitted from the Facility IE. 2) The channel shall be correctly released when a shortened channel release procedure is used - the SS does not send DISCONNECT but only the RELEASE COMPLETE and CHANNEL RELEASE messages or just the CHANNEL RELEASE message. Reference(s): Conformance requirement 1: 3GPP TS 02.24. Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Support for active state of the call control protocol (U10). - MMI method of reading the AoCI information. Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: Part 1: The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in a FACILITY message sent before the CONNECT message. The SS sends the DISCONNECT y seconds after sending the FACILITY message containing the e-parameters. The MS shall have stored the correct amount on the SIM according to the e-parameters sent. Part 2: Part 1 is repeated twice with the e-parameters that were set to zero above now omitted completely from the Facility IE. The shortened release procedures are used. The MS shall have stored the correct amount on the SIM. The results of parts 1 and 2 are compared. The value for the charge calculated by the MS shall be identical for parts 1 and 2. Maximum Duration of Test: 20 minutes. Expected Sequence: The sequence step 1‑20 is executed for execution counter k = 1,..3. Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS FACILITY As default message except contains Facility IE with contents as indicated in i below Either A, B or C branch is taken A12 SS -> MS CONNECT A13 MS -> SS CONNECT ACKNOWLEDGE A14 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B12 SS -> MS CONNECT B13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below B14 MS -> SS CONNECT ACKNOWLEDGE C12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below C13 SS -> MS CONNECT C14 MS -> SS CONNECT ACKNOWLEDGE 15 call duration y seconds after CAI information sent by SS Branch D, E and F shall be taken for k= 1,2 and 3 respectively D16 SS -> MS DISCONNECT D17 MS -> SS RELEASE D18 SS -> MS RELEASE COMPLETE D19 SS -> MS CHANNEL RELEASE The main signalling link is released. E16 SS -> MS RELEASE COMPLETE Shortened channel release procedure E17 SS -> MS CHANNEL RELEASE The main signalling link is released. F16 SS -> MS CHANNEL RELEASE 20 MS MS display is checked to determine whether the correct call charge has been indicated NOTE The value of y is given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. y is set to a constant value of 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: k-value e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 1 10 40 1 0 0 0 0 20 20 2 10 40 1 ---------omitted--------- 20 40 3 10 40 1 ---------omitted--------- 20 60 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.7 AoCI on a Call Hold call	Purpose: 1) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCI acknowledgement within 1 s of transmission of each set of e-parameters. Conformance Requirement(s): 1) When the MS invokes a Call Hold call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCI acknowledgement within 1 s of receiving each set of e-parameters. Reference(s): Conformance requirement 1: 3GPP TS 04.13. Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Support for active state of the call control protocol (U10). - MMI method of reading the AoCI information. Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of transmission of the CONNECT message. The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call. The MS is made to initiate a second call (call C). The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement in a FACILITY message within 1 s of transmission of the CONNECT message. The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT/FACILITY message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT/FACILITY message. Maximum Duration of Test: 10 minutes. Expected Sequence: Step Direction Message Comments 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either D or E branch is taken D12 MS -> SS CONNECT ACKNOWLEDGE D13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E13 MS -> SS CONNECT ACKNOWLEDGE 14 MS The MS is made to initiate a second call, and the first call is placed on hold. DTMF signalling may occur, when MMI keys are depressed 15 MS -> SS HOLD 16 SS -> MS HOLD ACKNOWLEDGE 17 MS -> SS CM SERVICE REQUEST 18 SS -> MS CM SERVICE ACCEPT 19 MS -> SS SETUP TI arbitrary but different from existing TI 20 SS -> MS CALL PROCEEDING 21 SS -> MS ALERTING 22 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either F or G branch is taken F23 MS -> SS CONNECT ACKNOWLEDGE F24 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G23 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G24 MS -> SS CONNECT ACKNOWLEDGE 25 Call durations x and y seconds after respective CAI information sent by SS Branch H and I branch are taken, the sequence depending on the durations x and y For call C H26 SS -> MS DISCONNECT y seconds after call C CAI sent H27 MS -> SS RELEASE H28 SS -> MS RELEASE COMPLETE For call B I26 SS -> MS DISCONNECT x seconds after call B CAI sent I27 MS -> SS RELEASE I28 SS -> MS RELEASE COMPLETE 29 SS -> MS CHANNEL RELEASE The main signalling link is released 30 MS MS display is checked to determine whether the correct call charge has been indicated NOTE The value of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x set to 180 s, y is set to 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: Call e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 B(time x) 7 40 1 0 0 0 0 C(time y) 13 40 1 0 0 0 0 54 54 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.3.8 AoCI on a Multi-party call	Purpose: 1) To verify that when the MS invokes a Multi-party call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCI acknowledgement within 1 s of transmission of each set of e-parameters. 2) To verify that when the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM records the sum of all the charges for the services currently being used and hence the ME inserts the correct charge in the ACM field of the SIM. Conformance Requirement(s): 1) When the MS invokes a Multi-party call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS shall return a FACILITY message containing the AoCI acknowledgement within 1 s of receiving each set of e-parameters. 2) When the MS originates a Multi-party call and hence receives Facility IEs containing CAI elements for each chargeable call the CCM shall record the sum of all the charges for the services currently being used and hence the ME shall insert the correct charge in the ACM field of the SIM. Reference(s): Conformance requirement 1: 3GPP TS 04.13. Conformance requirement 2: 3GPP TS 02.24, 3GPP TS 04.83, 3GPP TS 04.84, 3GPP TS 04.86. Specific PICS Statements - Supported teleservices (TSPC_AddInfo_TeleSvc). PIXIT Statements - Support for active state of the call control protocol (U10). - MMI method of reading the AoCI information. Initial Conditions: System Simulator: 1 cell, default parameters, IMSI attach/detach disabled. Mobile Station: The MS is in MM-state "idle, updated". Foreseen Final State of the MS: The MS is in MM-state "idle, updated". Method of Test: The MS is made to initiate a call. The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of transmission of the CONNECT message. The call (call B) is then put on hold by sending a HOLD message from the MS to the SS. The SS shall reply with a HOLD ACKNOWLEDGE. The traffic channel is now available to originate another call. The MS is made to initiate a second call (call C). The call is established with certain AoCI e-parameters sent in a Facility IE in the CONNECT message. The MS shall return the AoCI acknowledgement within 1 s of transmission of the CONNECT message. The MS invokes the multi-party service by sending a FACILITY message to the SS containing the BuildMPTY request. The SS accepts the request and connects the MS with the other existing connections (active call C and held call B) and confirms with a FACILITY message. The SS sends the DISCONNECT to the MS for call B x seconds after sending the call B CAI in the CONNECT message and the DISCONNECT for call C y seconds after sending the call C CAI in the CONNECT message. The MS shall have stored the correct amount on the SIM according to the two sets of e-parameters sent and call times x and y. Maximum Duration of Test: 10 minutes. Expected Sequence: Step Direction Message Comments 0 At start of test only, read and note value of ACM on SIM 1 MS The MS is made to initiate a call 2 MS -> SS CHANNEL REQUEST 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS SETUP 7 SS -> MS CALL PROCEEDING 8 SS -> MS ASSIGNMENT COMMAND to a supported channel type 9 MS -> SS ASSIGNMENT COMPLETE 10 SS -> MS ALERTING 11 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either D or E branch is taken D12 MS -> SS CONNECT ACKNOWLEDGE D13 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E12 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below E13 MS -> SS CONNECT ACKNOWLEDGE 14 MS -> SS HOLD The MS is made to initiate a second call and the first call (call B) is placed on hold. DTMF signalling may occur, when MMI keys are depressed 15 MS->SS HOLD 16 SS -> MS HOLD ACKNOWLEDGE 17 MS -> SS CM SERVICE REQUEST 18 SS -> MS CM SERVICE ACCEPT 19 MS -> SS SETUP TI arbitrary but different from existing TI 20 SS -> MS CALL PROCEEDING 21 SS -> MS ALERTING 22 SS -> MS CONNECT As default message except contains Facility IE with contents as indicated in i below Either F or G branch is taken F23 MS -> SS CONNECT ACKNOWLEDGE F24 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G23 MS -> SS FACILITY As default message except contains Facility IE with contents as indicated in ii below G24 MS -> SS CONNECT ACKNOWLEDGE The MS is made to build a multi-party call. DTMF signalling may occur, when MMI keys are depressed 25 MS -> SS FACILITY (TI A-B/A-C) As default message except contains Facility IE with contents as indicated in iii below 26 SS -> MS FACILITY (TI A-B/A-C) As default message except contains Facility IE with contents as indicated in iv, below 27 Call durations x and y seconds after respective CAI information sent by SS Branch H and branch I are taken, the sequence depending on the durations x and y For call C H28 SS -> MS DISCONNECT y seconds after call C CAI sent H29 MS -> SS RELEASE H30 SS -> MS RELEASE COMPLETE For call B I28 SS -> MS DISCONNECT x seconds after call B CAI sent I29 MS -> SS RELEASE I30 SS -> MS RELEASE COMPLETE 31 SS -> MS CHANNEL RELEASE The main signalling link is released. 32 MS MS display is checked to determine whether the correct call charge has been indicated NOTE: A-B/A-C indicates a choice. the transaction identifier (TI) used must be that of the active call or the held call (ref. 3GPP TS 04.84). The values of x and y are given below. The correct value of the ACM is found from the general AoC formula given in 3GPP TS 02.24 clause 4 with CDUR = x,y seconds and e parameters as defined below. Specific Message Contents: i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. For ASN.1 description see default message contents in subclause 31.6.4. x set to 180 s, y set to 90 s. The values of the e-parameters within the parameter part of the Facility Information Element shall be set to: Call e-parameter CCM total at call end increased by Step 0 ACM value 1 2 3 4 5 6 7 B(time x) 19 40 1 0 0 0 0 C(time y) 29 40 1 0 0 0 0 134 134 Values shown in table are in the format and have units as in 3GPP TS 02.24 clause 3. ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. For ASN.1 description see default message contents in subclause 31.6.4. iii) FACILITY Information Element with Invoke = BuildMPTY component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. The following abbreviations are used in the descriptions below: U Universal tag class. CS Context Specific tag class. P Primitive tag form. C Constructed tag form. FIE Facility Information Element. Contents Facility IE Identifier Value/remark As 3GPP TS 04.80 Coding 00011100 Length of FIE contents 8 00001000 Component type tag CS/C/tag=1 10100001 Component length 6 00000110 Invoke ID tag U/P/tag=2 00000010 Invoke ID length 1 00000001 Invoke ID Arbitrary (1 octet) (00000000) Op-Code tag From 3GPP TS 04.80 00000010 Op-Code length 1 00000001 Op-Code Build Multi-party operation (local value 124) 00000001 ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Facility IE Identifier Value/remark As 3GPP TS 04.80 Coding 00111100 Length of FIE contents 5 00001001 Component type tag CS/C/tag=2 10100010 Component length 3 00000011 Invoke ID tag U/P/Integer 00000010 Invoke ID length 1 00000001 Invoke ID Same as used as Invoke ID in Invoke FIE (00000000)
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.6.4 Default contents of messages	As default message contents in 3GPP TS 11.10 subclause 26.8. These messages shall not contain SS version IEs. Where indicated in specific tests CONNECT and FACILITY messages have Facility Information Elements as defined below. Default contents of ForwardChargeAdvice Facility Information Elements The following abbreviations are used in the descriptions below: U Universal tag class. CS Context Specific tag class. P Primitive tag form. C Constructed tag form. FIE Facility Information Element. i) FACILITY Information Element with Invoke = ForwardChargeAdvice component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3. Contents Value/remark Coding Facility IE Identifier As 3GPP TS 04.80 00011100 Length of FIE contents 43 00101011 Component type tag CS/C/tag=1 10100001 Component length 41 00101001 Invoke ID tag U/P/tag=2 00000010 Invoke ID length 1 00000001 Invoke ID Arbitrary (00000000) (1 octet) Op-Code tag From 3GPP TS 04.80 00000010 Op-Code length 1 00000001 Op-Code Forward Charge Advice operation 01111101 (local value 125) Sequence Identifier U/C/tag=16 00110000 from CCITT X.208 Length Indicator 33 00100001 SS-Code Identifier CS/P/tag=0 10000000 Length Indicator 1 00000001 SS-Code AoCC SS-Code (for AoCC tests) AoCI SS-Code (for AoCI tests) 01110010 01110001 Charging Info. identifier CS/C/tag=1 10100001 Length Indicator 28 00011100 e1 Identifier CS/P/tag=1 10000001 Length Indicator 2 00000010 e1 (2 Octets) See e-parameter table in relevant test e2 Identifier CS/P/tag=2 10000010 Length Indicator 2 00000010 e2 (2 Octets) See e-parameter table in relevant test . . . . . . . . . e7 Identifier CS/P/tag=7 10000111 Length Indicator 2 00000010 e7 (2 Octets) See e-parameter table in relevant test ii) FACILITY Information Element with Return Result component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4. Contents Value/remark Coding Facility IE Identifier As 3GPP TS 04.80 00111100 Length of FIE contents 5 00001001 Component type tag CS/C/tag=2 10100010 Component length 3 00000011 Invoke ID tag U/P/Integer 00000010 Invoke ID length 1 00000001 Invoke ID Same as used as (00000000) Invoke ID in Invoke FIE
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.7 Additional information transfer supplementary services	(Reserved).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8 Call restriction supplementary services	The following abbreviations are used: BO: Barring of Outgoing calls. BAOC: Barring of All Outgoing Calls. BOIC: Barring of Outgoing International Calls. BOICExHC: Barring of Outgoing International Call EXcept those directed to the Home PLMN country. BI: Barring of Incoming calls. BAIC: Barring of All Incoming calls. BICRoam: Barring of Incoming when Roaming outside the home PLMN country. B: Barring (common name for BAOC, BOIC, BOICExHC, BAIC and BICRoam). These abbreviations are also used to represent the corresponding SS-Code; e.g. B is the SS-Code for all barring services. NOTE: The password(s) to be used during tests of this subclause 31.8 may be randomly chosen - unless otherwise stated - in accordance with 3GPP TS 02.04 subclause 5.2.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1 Registration of a password
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.1 Registration accepted
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.1.1 Conformance requirements	1) For registration of a password for all barring services, the MS shall transmit successively: 1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user"; 1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation"; 1.3) and then the REGISTER message containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user's request (MMI action). 2) When the mobile subscriber wants to register a new password, the old password, the new password and the repeat of the new password shall be entered into the MS. Then the MS sends to the network an invoke component of the operation "register password". 3) The MS shall be able to send a password by sending a FACILITY message in accordance to the user request (MMI actions). 4) Upon receipt of the result of the procedure, contained in RELEASE COMPLETE or FACILITY message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer). References 1.1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9. 1.2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3. 1.3) 3GPP TS 04.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 2) 3GPP TS 04.10 subclause 4.2. 3) 3GPP TS 04.80. 4) 3GPP TS 02.30.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.1.2 Test purpose	1) To check that the MS correctly requests a supplementary service transaction for registration of a password for all barring services in CHANNEL REQUEST message. 2) To check that the MS correctly requests a supplementary service transaction for registration of a password for all barring services in the subsequent CM SERVICE REQUEST. 3) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all barring services. 4) To check that when the mobile subscriber wants to register a new password, the old password, the new password and the repeat of the new password shall be entered into the MS before the MS sends to the network a CHANNEL REQUEST. 5) To check that the MS is able to send a password by sending a FACILITY message in accordance to the user request (MMI actions). 6) To check that upon receipt of the result of the procedure, contained in RELEASE COMPLETE or FACILITY message, the MS provides the appropriate user indication (as described by the manufacturer). These checks are done for: - All barring services, the result of the operation being sent in a RELEASE COMPLETE message.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.1.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is "idle updated". Specific PICS Statements - PIXIT Statements - Description of the user's commands and of display of the answers from the network for call barring. Foreseen final state of the MS The MS is "idle updated". Test procedure By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all barring services by entering the old password, new password and a repeat of the old password. Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the old password. Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring a new password. Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring again the new password. Upon receipt of the FACILITY message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing the return result of the RegisterPassword operation. Maximum duration of test 3 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate a registration of a password for all call barring services. The old password, the new password and a repeat of the new password are entered. 2 MS -> SS CHANNEL REQUEST with establishment cause "Other procedures which can be completed with an SDCCH" 3 SS -> MS IMMEDIATE ASSIGNMENT 4 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 5 SS -> MS CM SERVICE ACCEPT 6 MS -> SS REGISTER 7 SS -> MS FACILITY Invoke = GetPassword (password) 8 MS -> SS FACILITY GetPassword operation ReturnResult 9 SS -> MS FACILITY Invoke = GetPassword (new password) 10 MS -> SS FACILITY GetPassword operation ReturnResult 11 SS -> MS FACILITY Invoke = GetPassword (new password again) 12 MS -> SS FACILITY GetPassword operation ReturnResult 13 SS -> MS RELEASE COMPLETE RegisterPassword operation ReturnResult 14 SS -> MS CHANNEL RELEASE Specific message content step 6 - - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = RegisterPassword: Supplementary service code = B. steps 7, 9, and 11 - - protocol discriminator: non call related SS message. - message type: FACILITY. - facility: invoke = GetPassword: Guidance info: Password (step 7), new password (step 9), new password again (step 11). The linked ID must be the same as the invoke ID in the invoke of the RegisterPassword operation.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2 Registration rejected
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.1 Rejection after invoke of the RegisterPassword operation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.1.1 Conformance requirements	1) A transaction of any kind being already established, for registration of a password for all call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation", 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer). References 1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9. 2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3. 3) 3GPP TS 04.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.1.2 Test purpose	1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of registration of a password for all call restriction services, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all call restriction services. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). Those checks are performed with a call transaction already established for: - all call restriction services, the RELEASE COMPLETE message being sent at the beginning of the procedure with a facility IE containing a return_error(error) where error is "SS subscription violation".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.1.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in CC state U10. Specific PICS Statements - PIXIT Statements - Description of the user's commands and of display of the answers from the network for call barring. Foreseen final state of the MS The MS is in CC state U10. Test procedure By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all call restriction services by entering the old password, the new password and a repeat of the new password. Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE (PD and TI of the SS transaction) message with the Facility information element containing a Return_error(error: SS subscription violation) of the RegisterPassword operation. Upon receipt of the FACILITY message, the system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10. Maximum duration of test 2 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate a registration of a new password for all call restriction services. The old password, the new password and a repeat of the new password are entered. 2 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 3 SS -> MS CM SERVICE ACCEPT 4 MS -> SS REGISTER 5 SS -> MS RELEASE COMPLETE RegisterPassword operation Return_error 6 MS provide correct MMI user indication 7 SS -> MS STATUS ENQUIRY 8 MS -> SS STATUS CC staTE U10 Specific message content step 4 - - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = RegisterPassword: Supplementary service code = all call restrictions. step 5 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: return error code: SS subscription violation. For the return error the invoke ID must be the same as in the invoke of the RegisterPassword operation.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.2 Rejection after password check with negative result
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.2.1 Conformance requirements	1) A transaction of any kind being already established, for registration of a password for all call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation". 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer). References 1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9. 2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3. 3) 3GPP TS 04.88, 3GPP TS 04.80 subclauses 2.3 and 3.6, 3GPP TS 04.10 subclause 4.2.2, 3GPP TS 03.11 clause 3. 4) 3GPP TS 02.30 subclause 4.5.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.2.2 Test purpose	1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of registration of a password for all call restriction services, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all call restriction services. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). Those checks are performed with a call transaction already established for: - all call restriction services, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "NegativePasswordCheck".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.2.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. WPA > 3. Mobile Station: The MS is in CC state U10. Specific PICS Statements - PIXIT Statements - Description of the user's commands and of display of the answers from the network for call barring. Foreseen final state of the MS The MS is in CC state U10. Test procedure By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all call restriction services. By means of appropriate MMI functions the user enters the old and new passwords. Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the old password. Upon receipt of the FACILITY message, the system simulator answers with the RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: NegativePasswordCheck) of the RegisterPassword operation. The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10. Maximum duration of test 5 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate a registration of a new password for all call restriction services. The old and new passwords are entered. 2 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 3 SS -> MS CM SERVICE ACCEPT 4 MS -> SS REGISTER 5 SS -> MS FACILITY Invoke = GetPassword (password) 6 SS -> MS RELEASE COMPLETE Register Password operation ReturnError 7 MS provide correct MMI user indication 8 SS -> MS STATUS ENQUIRY 9 MS -> SS STATUS CC staTE U10 Specific message content step 4 - - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = RegisterPassword: Supplementary service code = B. step 6 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: error code: NegativePasswordCheck. For the reject the invoke ID must be the same as in the invoke of the Registerpassword operation. step 5 - - protocol discriminator: non call related SS message. - transaction identifier: in FACILITY same as previous REGISTER message. - message type: FACILITY. - facility: invoke = GetPassword: Guidance info: Password (step 1).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.3 Rejection after new password mismatch
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.3.1 Conformance requirements	1) A transaction of any kind being already established, for registration of a password for all call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation". 2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user's request (MMI action). 3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected. 4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer). References 1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9. 2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3. 3) 3GPP TS 04.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 4) 3GPP TS 02.30 subclause 4.5. 5) 3GPP TS 04.10 subclause 4.2.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.3.2 Test purpose	1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of registration of a password for all call restriction services, sending a CM SERVICE REQUEST. 2) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all call restriction services. 3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected. 4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer). Those checks are performed with a call transaction already established for: - all call restriction services, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "PasswordRegistrationFailure" with diagnostic "new password mismatch".
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.1.2.3.3 Method of test	Initial conditions System Simulator: 1 cell, default parameters. Mobile Station: The MS is in CC state U10. Specific PICS Statements - PIXIT Statements - Description of the user's commands and of display of the answers from the network for call barring. Foreseen final state of the MS The MS is in CC state U10. Test procedure By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all call restriction services by entering the old password, the new password and a repeat of the new password. Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the old password. Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the new password. Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring again the new password. Upon receipt of the FACILITY message, the system simulator answers with the RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: PasswordRegistrationFailure, parameter: NewPasswordMismatch) of the RegisterPassword operation. The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10. Maximum duration of test 3 minutes. Expected sequence Step Direction Message Comments 1 MS The MS is made to initiate a registration of a new password for all call restriction services. The old password, new password and a repeat of the new password are entered. 2 MS -> SS CM SERVICE REQUEST cause: "supplementary service activation" 3 SS -> MS CM SERVICE ACCEPT 4 MS -> SS REGISTER 5 SS -> MS FACILITY Invoke = GetPassword (password) 6 MS -> SS FACILITY GetPassword operation ReturnResult 7 SS -> MS FACILITY Invoke = GetPassword (new password) 8 MS -> SS FACILITY GetPassword operation ReturnResult 9 SS -> MS FACILITY Invoke = GetPassword (new password again) 10 MS -> SS FACILITY GetPassword operation ReturnResult 11 SS -> MS RELEASE COMPLETE Register Password operation ReturnError 12 MS provide correct MMI user indication 13 SS -> MS STATUS ENQUIRY 14 MS -> SS STATUS CC staTE U10 Specific message content step 4 - - protocol discriminator: non call related SS message. - message type: REGISTER. - facility: invoke = RegisterPassword: Supplementary service code = B. step 11 - - protocol discriminator: non call related SS message. - transaction identifier: same TI as previous REGISTER message. - message type: RELEASE COMPLETE. - facility: error code: PasswordRegistrationFailure. parameter: NewPasswordMismatch. For the reject the invoke ID must be the same as in the invoke of the Registerpassword operation. steps 5, 7, and 8 - - protocol discriminator: non call related SS message. - transaction identifier: in FACILITY same as previous REGISTER message. - message type: FACILITY. - facility: invoke = GetPassword: Supplementary service code = B. Guidance info: Password (step 5), new password (step 7), new password again (step 8).
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.2 Erasure	Not applicable.
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3 Activation
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.1 Activation accepted
683b5b8a98f7b1390ddd5516ea9247a2	51.010-1	31.8.3.1.1 Conformance requirements	1) For activation of any specific call restriction service with any parameters, the MS shall transmit successively 1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user"; 1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation"; 1.3) and then the REGISTER message containing a facility IE that includes an invoke of the ActivateSS operation with parameter values according to the user's request (MMI action). 2) Upon receipt of FACILITY message requiring the password, the MS shall be able to send a password by sending a FACILITY message. 3) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer). References 1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.2.9. 2) 3GPP TS 04.88, 3GPP TS 04.80 subclauses 2.3 and 3.6. 3) 3GPP TS 02.30 subclause 4.5.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.