hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.2 Registration rejected | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.2.1 Conformance requirements | 1) A transaction of any kind being already established, for registration of any type of call forwarding with any parameters, 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 RegisterSS 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.82, 3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.2.2 Test purpose | 1) To check that the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of registration of call forwarding, sending a CM SERVICE REQUEST.
2) To check that the MS sends a REGISTER message containing the invoke of the RegisterSS operation with the expected parameter values for registration of call forwarding.
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).
These checks are performed with a call transaction already established for:
a) CFB, for all asynchronous services, the RELEASE COMPLETE message being sent with a facility IE containing a return_error(error) where error is "Bearer Service not provisioned".
b) CF, for all facsimile, the RELEASE COMPLETE message being sent with a facility IE containing a reject(invoke_problem) where invoke_problem is "resource limitation". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.1.2.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 forwarding.
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 CFB for all asynchronous services, to a number arbitrarily selected.
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: BearerService not provisioned) of the RegisterSS 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 registration of CF for all facsimile, to a number arbitrarily selected.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a reject(invoke_problem: resource limitation) of the RegisterSS 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 call forwarding service for CFB (all asynchronous services)
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
RegisterSS operation Return_error
6
MS
provide correct MMI user indication
7
SS -> MS
STATUS ENQUIRY
8
MS -> SS
STATUS
CC state U10
9
MS
The MS is made to initiate a registration of call forwarding service for CF (all facsimile)
10
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
11
SS -> MS
CM SERVICE ACCEPT
12
MS -> SS
REGISTER
13
SS -> MS
RELEASE COMPLETE
RegisterSS operation Reject
14
MS
provide correct MMI user indication
15
SS -> MS
STATUS ENQUIRY
16
MS -> SS
STATUS
CC state U10
Specific message content
step 4 - CFB
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Registration:
Supplementary service code = CFB.
Forwarded to number: as selected.
Basic service code: Bearer Service (all asynchronous services), 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: BearerService not provisioned.
For the return error the invoke ID must be the same as in the invoke of the RegisterSS operation.
step 11 - CF
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Registration:
Supplementary service code = CF.
Forwarded to number: as selected.
Basic service code: no bearer service present, teleservice (all facsimile)).
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 Register SS operation. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2 Erasure by the subscriber | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.1 Erasure accepted | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.1.1 Conformance requirements | For erasure of any type of call forwarding, the MS shall transmit successively:
1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";
2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";
3) and then the REGISTER message containing a facility that includes an invoke of the EraseSS operation with the expected parameter values according to the user request (MMI action);
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.82, 3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.1.2 Test purpose | 1) To check that the MS correctly requests supplementary service transaction for erasure of call forwarding in CHANNEL REQUEST message.
2) To check that the MS correctly requests supplementary service transaction for erasure of call forwarding in the subsequent CM SERVICE REQUEST.
3) To check that the MS sends a REGISTER message containing the invoke of the EraseSS operation with the expected parameter values for erasure of call forwarding.
4) To check that upon receipt of the result of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).
These checks are done for:
a) CFC, for basic service group all facsimile.
b) CFNRc, for all basic service groups. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.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 forwarding.
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 erasure of CFC for all facsimile.
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 result of the EraseSS 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 erasure of CFNRc 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 EraseSS 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 erasure of call forwarding for CFC (all facsimile)
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
EraseSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
MS
Provide correct MMI user indication after step 7
10
MS
The MS is made to initiate a erasure of call forwarding service for CFNRc (all basic services)
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
EraseSS operation Return result
17
SS -> MS
CHANNEL RELEASE
Specific message content
step 6 - CFC
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Erasure:
Supplementary service code = CFC.
Basic service code: no Bearer Service, teleservice (all facsimile).
step 15 - CFNRc
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Erasure:
Supplementary service code = CFNRc.
Basic service code: no bearer service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.2 Erasure rejected | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.2.1 Conformance requirements | 1) A transaction of any kind being already established, for erasure of any type of call forwarding with any parameters, 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 EraseSS 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.82,
3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.2.2 Test purpose | 1) To check that the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of erasure of call forwarding, sending a CM SERVICE REQUEST.
2) To check that the MS sends a REGISTER message containing the invoke of the EraseSS operation with the expected parameter values for erasure of call forwarding.
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).
These checks are performed with a call transaction already established for:
a) CFU, for Speech, the RELEASE COMPLETE message being sent with a facility IE containing a return_error(error) where error is "Teleservice not provisioned".
b) CFNRy, for all facsimile, the RELEASE COMPLETE message being sent with a facility IE containing a reject(invoke_problem) where invoke_problem is "resource limitation". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.2.2.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 forwarding.
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 erasure of CFU for Speech.
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: TeleService not provisioned) of the EraseSS 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 erasure of CFNRy for all facsimile.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a reject(invoke_problem: resource limitation) of the EraseSS 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 erasure of call forwarding service for CFU (speech)
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
EraseSS operation Return_error
6
SS -> MS
STATUS ENQUIRY
7
MS -> SS
STATUS
CC state U10
8
MS
The MS is made to initiate a erasure of call forwarding service for CFNRy (all facsimile)
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
EraseSS 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 - CFU
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Erasure:
Supplementary service code = CFU.
Basic service code: Tele Service AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice 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: TeleService not provisioned.
For the return error the invoke ID must be the same as in the invoke of the EraseSS operation.
step 11 - CFNRy
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Erasure:
Supplementary service code = CFNRy.
Basic service code: no bearer service present, teleservice (all facsimile)).
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 EraseSS operation. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.3 Activation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.3.1 Conformance requirements | For activation of any type of call forwarding with any parameters, the MS shall transmit successively
1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";
2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";
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);
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.82,
3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.3.2 Test purpose | 1) To check that the MS correctly requests a supplementary service transaction for activation of call forwarding in CHANNEL REQUEST message.
2) To check that the MS correctly requests a supplementary service transaction for activation of call forwarding in the subsequent CM SERVICE REQUEST.
3) To check that the MS sends a REGISTER message containing the invoke of the ActivateSS operation with the expected parameter values for activation of call forwarding.
4) To check that upon receipt of the result of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).
These checks are done for:
a) CF, for basic service group "all synchronous services".
b) CFU, for all basic service groups. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.3.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 forwarding.
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 activation of CF for all synchronous services.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing the return result of the ActivateSS 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 activation of CFU 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 ActivateSS operation.
Maximum duration of test
3 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a activation of call forwarding service for CF (all synchronous services)
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
ActivateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
Provide correct MMI user indication after step 7
10
MS
The MS is made to initiate a activation of call forwarding service for CFU (all basic service groups)
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
ActivateSS operation Return result
17
SS -> MS
CHANNEL RELEASE
Specific message contents:
step 6 - CF
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Activation:
Supplementary service code = CF.
Basic service code: Bearer Service (all synchronous services), no teleservice present.
step 15 - CFU
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Activation:
Supplementary service code = CFU.
Basic service code: no bearer service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.4 Deactivation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.4.1 Conformance requirements | For deactivation of any type of call forwarding with any parameters, the MS shall transmit successively:
1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";
2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";
3) and then the REGISTER message containing a facility IE that includes an invoke of the DeactivateSS operation with parameter values according to the user's request (MMI action);
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.82,
3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.4.2 Test purpose | 1) To check that the MS correctly requests a supplementary service transaction for deactivation of call forwarding in CHANNEL REQUEST message.
2) To check that the MS correctly requests a supplementary service transaction for deactivation of call forwarding in the subsequent CM SERVICE REQUEST.
3) To check that the MS sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for deactivation of call forwarding.
4) To check that upon receipt of the result of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).
These checks are done for:
a) CFC, for basic service group speech.
b) CFNRc, for basic service group all facsimile. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.4.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 forwarding.
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 deactivation of CFC for speech.
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 DeactivateSS 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 deactivation of CFNRc for all facsimile.
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 DeactivateSS 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 a deactivation of call forwarding service for CFC (speech)
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
DeactivateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
MS
Provide correct MMI user indication after step 7
10
MS
The MS is made to initiate a deactivation of call forwarding service for CFNRc (all facsimile)
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
DeactivateSS operation Return result
17
SS -> MS
CHANNEL RELEASE
18
MS
Provide correct MMI user indication after step 16
Specific message content
step 6 - CFC
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Deactivation:
Supplementary service code = CFC.
Basic service code: no bearer service , teleservice (All Speech Transmission Services).
step 15 - CFNRc
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Deactivation:
Supplementary service code = CFNRc.
Basic service code: no bearer service present, teleservice (all facsimile). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.5 Invocation | Invocation is not applicable to the MS and causes no signalling on the radio path. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6 Interrogation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.1 Interrogation accepted | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.1.1 Conformance requirements | For interrogation of any specific call forwarding service (not applicable to a group of services) with any parameters, the MS shall transmit successively:
1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";
2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";
3) and then the REGISTER message containing a facility IE that includes an invoke of the InterrogateSS operation with parameter values according to the user's request (MMI action);
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.82,
3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.1.2 Test purpose | 1) To check that the MS correctly requests a supplementary service transaction for interrogation of a specific call forwarding in CHANNEL REQUEST message.
2) To check that the MS correctly requests a supplementary service transaction for interrogation of call forwarding in the subsequent CM SERVICE REQUEST.
3) To check that the MS sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of call forwarding.
4) To check that upon receipt of the result of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).
These checks are done for:
a) CFB, for all basic service groups.
b) CFNRy, for basic service group speech. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle updated".
Specific PICS Statements
- Speech supported for Full rate version 1 (TSPC_AddInfo_Full_rate_version_1)
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for call forwarding.
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 CFB 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 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 CFNRy for speech.
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 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 a interrogation of call forwarding service for CFB (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 operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
Provide correct MMI user indication after step 7
9A
Steps 10 to 19 are applicable if MS supports speech (TSPC_AddInfo_Full_rate_version_1).
10
MS
The MS is made to initiate a interrogation of call forwarding service for CFNRy(speech)
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
16
MS -> SS
REGISTER
17
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return result
18
SS -> MS
CHANNEL RELEASE
Specific message content
step 6 - CFB
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = CFB.
Basic service code: no Bearer Service present, no teleservice present.
step 15 - CFNRy
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = CFNRy.
Basic service code: no bearer service present, teleservice (speech). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.2 Interrogation rejected | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.2.1 Conformance requirements | 1) A transaction of any kind being already established, for interrogation of any specific call forwarding service with any parameters, 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 InterrogateSS 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.82,
3GPP TS 04.80 subclauses 2.3 and 3.6.
4) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.2.2 Test purpose | 1) To check that the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of interrogation of a specific call forwarding service, sending a CM SERVICE REQUEST.
2) To check that the MS sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of call forwarding.
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).
These checks are performed with a call transaction already established for:
a) CFNRc, for all basic service group, the RELEASE COMPLETE message being sent with a facility IE containing a return_error(error) where error is "SS not available".
b) CFB, for all facsimile, the RELEASE COMPLETE message being sent with a facility IE containing a reject(invoke_problem) where invoke_problem is "resource limitation". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.6.2.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 forwarding.
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 CFNRc 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 CFB for all facsimile.
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 a interrogation of call forwarding service for CFNRc (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 a interrogation of call forwarding service for CFB (all facsimile)
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 - CFNRc
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = CFNRc.
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 11 - CFB
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Interrogation:
Supplementary service code = CFB.
Basic service code: no bearer service present, teleservice (all facsimile)).
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.2.1.7 Normal operation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1 Served mobile subscriber side | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1.1 Notification during an incoming call | This subscription option is only applicable to CFB and CFNRy. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1.1.1 Conformance requirements | 1) During a call transaction, call establishment or not, upon receipt of a FACILITY message notifying an incoming call, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).
2) If a call transaction is being established or is already established when the notification of incoming call is received, the receipt of the notification has no effect on its state.
References
1) 3GPP TS 02.30 subclause 4.5.
2) 3GPP TS 04.82 clause 1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1.1.2 Test purpose | 1) To check that, in state U7 or U10, upon receipt of a FACILITY message notifying an incoming call, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).
2) To check that when the notification of incoming call is received while the MS is in CC state U7 and U10 of another incoming call, it has no effect on its state.
These checks are performed in the case of CFB. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.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 forwarding.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
The MS is brought to the call state U7 of an incoming call.
The system simulator transmits a FACILITY message with the facility information element containing an invoke of the NotifySS operation for CFB.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U7.
The MS is brought into the call state U10 of an incoming call.
The system simulator transmits a FACILITY message with the facility information element containing an invoke of the NotifySS operation for CFB.
The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.
The transaction and the channel are released by the SS.
Maximum duration of test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING
2
MS -> SS
CHANNEL REQUEST
with establishment cause "answer to paging"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
SETUP
6
MS -> SS
CALL CONFIRMED
7
SS -> MS
ASSIGNMENT COMMAND
8
MS -> SS
ASSIGNMENT COMPLETE
9
MS -> SS
ALERTING
10
SS -> MS
FACILITY
(invoke NotifySS)
11
SS -> MS
STATUS ENQUIRY
12
MS -> SS
STATUS
(U7)
13
MS -> SS
CONNECT
MS off hook
14
SS -> MS
CONNECT ACKNOWLEDGE
15
SS -> MS
FACILITY
(invoke NotifySS)
16
SS -> MS
STATUS ENQUIRY
17
MS -> SS
STATUS
(U10)
18
SS -> MS
RELEASE COMPLETE
19
SS -> MS
CHANNEL RELEASE
Specific message contents
Steps 10 and 15
- protocol discriminator: CC.
- transaction identifier: same as for the call transaction already established.
- message type: FACILITY.
- facility:
invoke = notification:
Supplementary service code = CFB.
SS notification = incoming call is forwarded.
(call is forwarded indication to B subscriber). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1.2 Notification during an outgoing call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1.2.1 Conformance requirements | 1) As an outgoing call is being established, if the ALERTING message is received with the facility information element containing an SS notification (for CFU or CFC), the MS shall correctly reach CC state U4.
2) As an outgoing call is being established, if the ALERTING message is received with the facility information element containing an SS notification (for CFU or CFC), the MS shall provide the appropriate user indication (which is to be described by the manufacturer).
3) As an outgoing call is being established, if the CONNECT message is received with the facility information element containing an SS notification (for CFU or CFC), the MS shall normally send a CONNECT ACKNOWLEDGE message and enter CC state U10.
4) As an outgoing call is being established, if the CONNECT message is received with the facility information element containing an SS notification (for CFU or CFC), the MS shall provide the appropriate user indication (which is to be described by the manufacturer).
References
1) 3GPP TS 04.82,
3GPP TS 04.80 subclause 3.6.
2) 3GPP TS 04.82 TBS,
3GPP TS 04.80 subclause 3.6. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1.2.2 Test purpose | 1) To check that when an outgoing call is being established, if the ALERTING message is received with the facility information element containing an SS notification, the MS correctly reaches CC state U4. This is tested for CFU.
2) As an outgoing call is being established, if the ALERTING message is received with the facility information element containing an SS notification, the MS provides the appropriate user indication (which is to be described by the manufacturer). This is tested for CFU.
3) As an outgoing call is being established, if the CONNECT message is received with the facility information element containing an SS notification, the MS normally sends a CONNECT ACKNOWLEDGE message and enter CC state U10. This is tested for CFC.
4) As an outgoing call is being established, if the CONNECT message is received with the facility information element containing an SS notification (for CFU or CFC), the MS provides the appropriate user indication (which is to be described by the manufacturer). This is tested for CFC. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.1.2.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 forwarding.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
The MS is made to place an outgoing call.
After having received a SETUP message and sent a CALL PROCEEDING message and after a TCH has been allocated the system simulator transmits an ALERTING message with the facility information element containing a notification.
The system simulator send then a STATUS ENQUIRY message. On receipt of the STATUS ENQUIRY message the MS shall send a STATUS message with CC-state U4.
After that, the system simulator transmits a CONNECT with the facility information element containing a notification.
After reception of a CONNECT ACKNOWLEDGE message the system simulator sends a STATUS ENQUIRY message.
The MS shall respond with a STATUS message indicating CC-state U10.
The transaction and the channel are released by the SS.
Maximum duration of test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
2
SS -> MS
IMMEDIATE ASSIGNMENT
3
MS -> SS
CM SERVICE REQUEST
"mobile originating call establishment"
4
SS -> MS
CM SERVICE ACCEPT
5
MS -> SS
SETUP
6
SS -> MS
CALL PROCEEDING
7
SS -> MS
ASSIGNMENT COMMAND
8
MS -> SS
ASSIGNMENT COMPLETE
9
SS -> MS
ALERTING
containing facility IE
10
SS -> MS
STATUS ENQUIRY
11
MS -> SS
STATUS
(U4)
12
SS -> MS
CONNECT
containing facility IE
13
MS -> SS
CONNECT ACKNOWLEDGE
14
SS -> MS
STATUS ENQUIRY
15
MS -> SS
STATUS
(U10)
16
SS -> MS
RELEASE COMPLETE
17
SS -> MS
CHANNEL RELEASE
Specific message contents
At step 9 -
Facility invoke = notification:
- SS-Code (CFU).
- SS-Status (indicating:
Provisioned, registered and active).
At step 12 -
Facility invoke = notification:
- SS-Code (CFC).
- SS-Status (indicating:
Provisioned, registered and active). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.2 Forwarded-to mobile subscriber side | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.2.1 Conformance requirements | 1) Upon receipt of the SETUP message containing a notification indication that the call is a forwarded one (with any SS code except CFC), the MS shall correctly continue call establishment and enter CC state U6.
2) Upon receipt of the SETUP message containing a notification indication that the call is a forwarded one, or after sending CALL CONFIRMED, or after sending ALERTING, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).
References
1) 3GPP TS 04.82.
2) 3GPP TS 02.30 subclause 4.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.2.2 Test purpose | 1) To check that, upon receipt of the SETUP message containing a notification indication that the call is a forwarded one, the MS correctly continues call establishment and enters CC state U6.
2) To check that upon receipt of the SETUP message containing a notification indication that the call is a forwarded one, or after sending CALL CONFIRMED, or after sending ALERTING, the MS provides the appropriate user indication (which is to be described by the manufacturer). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.2.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 forwarding.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
An incoming call is given to the MS with the SETUP message with the facility information element containing an invoke of the NotifySS operation with the indication that the call is forwarded.
After the MS was brought to CC state U7, the SS sends a STATUS ENQUIRY message. The MS responds indicating CC state U7 (implying that it has travelled through CC state U6).
The transaction and the channel are released by the SS.
Maximum duration of test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING
2
MS -> SS
CHANNEL REQUEST
with establishment cause "answer to paging"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
SETUP
containing the notification that the call is a forwarded one
6
MS -> SS
CALL CONFIRMED
7
SS -> MS
ASSIGNMENT COMMAND
8
MS -> SS
ASSIGNMENT COMPLETE
9
MS -> SS
ALERTING
Ringing and user indication that the incoming call is forwarded
10
SS -> MS
STATUS ENQUIRY
11
MS -> SS
STATUS
(U7)
12
SS -> MS
RELEASE COMPLETE
13
SS -> MS
CHANNEL RELEASE
Specific message contents
at step 5 -
- protocol discriminator: CC.
- transaction identifier.
- message type: SETUP.
- facility.
invoke = notification:
- SS-Code (CFU, CFB, CFNRy, CFNRc or CF).
- SS-Notification (indicating: call is forwarded i.e.:
Call is forwarded indication to C-subscriber. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.2 Call transfer and mobile access hunting supplementary services | (Reserved). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3 Call completion supplementary services | NOTE: In this subclause, Subscriber B is the MS under test, and subscribers A, C and D are distant parties to the calls made during the tests. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1 Call Waiting | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.1 Waiting call indication and confirmation | Conformance requirement
3GPP TS 04.83 subclause 1.1.
Test purpose
With an active call, an MS receiving an MT call shall include Cause #17 "user busy" in the CALL CONFIRMED message sent to the SS, and indicate the waiting call to the subscriber.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Method of indicating a waiting call to the user.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a call ("Call A-B") of a basic service supported by the MS and applicable to Call Waiting as described in 3GPP TS 02.04 table A.1 in the active state. The SIM in the MS under test has Call Waiting enabled.
Foreseen final state of the MS
Call A-B, state U10. Call C-B, state U7.
Maximum duration of test
30 s.
Procedure
The SS shall initiate Call C-B by sending a SETUP message to the MS. The MS shall respond with a CALL CONFIRMED message including cause #17 "user busy", followed by an ALERTING message.
The MS shall remain in state U10 in respect of the Call A-B, and enter state U7 "Call received" in respect of Call C-B. The MS shall indicate the existence of the waiting call to the user by a method defined by the manufacturer. 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
SS -> MS
SETUP
Transaction identifier different from that of Call A-B
2
MS -> SS
CALL CONFIRMED
cause #17 "user busy".
3
MS -> SS
ALERTING
4
MS
A waiting call indication as defined in a PICS/PIXIT statement is given by the MS.
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
6
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10
7
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call C-B
8
MS -> SS
STATUS
Transaction identifier of Call C-B, state U7 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2 Normal operation with successful outcome | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.1 Waiting call accepted; existing call released | Conformance requirement
3GPP TS 04.83 subclause 1.2.1.
Test purpose
The MS shall release the active call using the call clearing procedures of 3GPP TS 04.08 / 3GPP TS 24.008, and then accept the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Method of clearing an active call and answering a waiting call.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has Call A-B of a basic service supported by the MS and applicable to Call Waiting as described in 3GPP TS 02.04 table A.1 in the state U10 "Active" and Call C-B in the state U7 "Call Received".
Foreseen final state of the MS
Call A-B, state U0. Call C-B, state U10.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall clear Call A-B, and then answer Call C-B.
The MS shall send a DISCONNECT message with the transaction identifier Call A-B, and then respond to a RELEASE message from the SS with a RELEASE COMPLETE message, and then enter state U0 "Null" in respect of this call.
The MS shall then send a CONNECT in respect of Call C-B, and enter state U10 "Active" on receipt of a CONNECT ACKNOWLEDGE message. 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 Call A-B and a STATUS message indicating the appropriate call state for Call C-B.
Expected sequence
Step
Direction
Message
Comments
1
MS
Call A-B is cleared using MMI commands
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
MS
Call C-B is answered using MMI commands
6
MS -> SS
CONNECT
Transaction identifier of Call C-B
7
SS -> MS
CONNECT ACKNOWLEDGE
Transaction identifier of Call C-B
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 C-B
11
MS -> SS
STATUS
Transaction identifier of Call C-B, state U10 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.2 Waiting call accepted; existing call on hold | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.2.1 Waiting call accepted; existing call on hold, no additional calls | Conformance requirement
3GPP TS 04.83 subclause 1.2.2.
Test purpose
With one active call and one waiting call, the MS shall place the active call on hold, and then accept the waiting call.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of placing an active call on hold and answering a waiting call.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
- The MS has Call A-B of a basic service supported by the MS and applicable to Call Waiting as described in 3GPP TS 02.04 table A.1 in the state U10 "Active" and Call C-B in the state U7 "Call Received".
Foreseen final state of the MS
Call A-B, state U10, auxiliary state "Call held". Call C-B, state U10.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall place Call A-B on hold, and then answer Call C-B.
The MS shall send a HOLD message to the SS using the transaction identifier of Call A-B and enter state U10 "Active" with auxiliary state "Call held". On receipt of a HOLD ACKNOWLEDGE from the SS the MS shall enter state U10 "Active" with auxiliary state "Call held".
The MS shall then send a CONNECT message to the SS, using the transaction identifier of Call C-B, 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
Call A-B is placed on hold using MMI commands
2
MS -> SS
HOLD
Transaction identifier of Call A-B
3
SS -> MS
HOLD ACKNOWLEDGE
Transaction identifier of Call A-B
4
MS
Call C-B is answered using MMI commands
5
MS -> SS
CONNECT
Transaction identifier of Call C-B
6
SS -> MS
CONNECT ACKNOWLEDGE
Transaction identifier of Call C-B
7
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
8
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call Held"
9
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call C-B
10
MS -> SS
STATUS
Transaction identifier of Call C-B, state U10 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.3 Existing call released by user A; waiting call accepted | Conformance requirement
3GPP TS 04.83 subclause 1.2.3.
Test purpose
The MS, on receipt of a DISCONNECT message from the active call, shall complete the clearance of the active call, and accept the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Method of clearing an active call and answering a waiting call.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has Call A-B of a basic service supported by the MS and applicable to Call Waiting as described in 3GPP TS 02.04 table A.1 in the state U10 "Active" and Call C-B in the state U7 "Call Received".
Foreseen final state of the MS
Call A-B, state U0. Call C-B, state U10.
Maximum duration of test
30 s.
Procedure
On receipt of a DISCONNECT message using the transaction identifier of Call A-B, the MS shall respond with a RELEASE message. On receipt of a RELEASE COMPLETE message, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
If necessary, MMI commands shall be entered to accept call C-B. The MS shall then send a CONNECT message using the transaction identifier of Call C-B, 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 RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Call A-B and a STATUS message indicating the appropriate call state for Call C-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
MS
If necessary, call C-B is answered using MMI commands
5
MS -> SS
CONNECT
Transaction identifier of Call C-B
6
SS -> MS
CONNECT ACKNOWLEDGE
Transaction identifier of Call C-B
7
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
8
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
9
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call C-B
10
MS -> SS
STATUS
Transaction identifier of Call C-B, state U10 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.3 Normal operation with unsuccessful outcome | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.3.1 Waiting call released by subscriber B | Conformance requirement
3GPP TS 04.83 subclause 1.3.1.
Test purpose
To test that, using MMI commands, the MS shall clear the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Method of clearing a waiting call.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has Call A-B of a basic service supported by the MS and applicable to Call Waiting as described in 3GPP TS 02.04 table A.1 in the state U10 "Active" and Call C-B in the state U7 "Call Received".
Foreseen final state of the MS
Call A-B, state U10. Call C-B, state U0.
Maximum duration of test
30 s.
Procedure
Using appropriate MMI commands, the MS shall clear Call C-B.
The MS shall send a DISCONNECT message with the transaction identifier of Call B, and on receipt of a RELEASE message from the network, shall send a RELEASE COMPLETE and enter state U0 "Null". The call states shall be verified by the SS sending a a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Call C-B and 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 Call C-B and a STATUS message indicating the appropriate call state for Call A-B.
Expected sequence
Step
Direction
Message
Comments
1
MS
Call C-B is cleared using MMI commands
2
MS -> SS
DISCONNECT
Transaction identifier of Call C-B
3
SS -> MS
RELEASE
Transaction identifier of Call C-B
4
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call C-B
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
6
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10
7
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call C-B
8
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call C-B, with cause #81 "invalid transaction identifier value" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.3.2 Waiting call released by calling user C | Conformance requirement
3GPP TS 04.83 subclause 1.3.2.
Test purpose
To test that the MS responds correctly to the receipt of a clearing message from the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has Call A-B of a basic service supported by the MS and applicable to Call Waiting as described in 3GPP TS 02.04 table A.1 in the state U10 "Active" and Call C-B in the state U7 "Call Received".
Foreseen final state of the MS
Call A-B, state U10. Call C-B, state U0.
Maximum duration of test
30 s.
Procedure
On receipt of a DISCONNECT message using the transaction identifier of Call C-B, the MS shall respond with a RELEASE message. On receipt of a RELEASE COMPLETE message, the MS shall enter state U0 "Null". Call A-B shall remain in state U10. 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 a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value" for Call C-B and STATUS message indicating the appropriate call state for Call A-B.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
DISCONNECT
Transaction identifier of Call C-B
2
MS -> SS
RELEASE
Transaction identifier of Call C-B
3
SS -> MS
RELEASE COMPLETE
Transaction identifier of Call C-B
4
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
5
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10
6
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call C-B
7
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call C-B, with cause #81 "invalid transaction identifier value" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.4 Activation | Conformance requirement
3GPP TS 04.83 subclause 1.4.
Test purpose
To test the correct operation of the activation procedure, and correctly display of the response from the SS in the following cases.
1) Successful activation.
2) Error response (reject).
3) Activation reject (Invoke problem).
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 activation 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 activation of CW for a basic service group supported by the MS.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing the return result of the ActivateSS 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 activation 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 ActivateSS operation.
The SS transaction is released and the dedicated channel is released.
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests activation of CW for a basic service group supported by the MS.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a Return Error component with Error code:SS not available.
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 activation of CW for all basic service groups.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a Return Error component with Error code:SS not available.
The SS transaction is released and the dedicated channel is released.
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests activation of CW for a basic service group supported by the MS.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a Reject component with Invoke problem (Resource limitation).
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 activation 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 A Reject component with Invoke problem (Resource limitation).
Maximum duration of test
9 minutes
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate activation of CW for a basic service group supported by the MS
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
ActivateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
MS
Provide correct MMI user indication after step 7
10
MS
The MS is made to initiate a activation of CW (all basic service groups)
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
ActivateSS operation Return result
17
SS -> MS
CHANNEL RELEASE
18
MS
Provide correct MMI user indication after step 16
19
MS
The MS is made to initiate activation of CW for a basic service group supported by the MS
20
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
21
SS -> MS
IMMEDIATE ASSIGNMENT
22
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
23
SS -> MS
CM SERVICE ACCEPT
24
MS -> SS
REGISTER
25
SS -> MS
RELEASE COMPLETE
ActivateSS operation Return Error
26
SS -> MS
CHANNEL RELEASE
27
MS
Provide correct MMI user indication after step 25
28
MS
The MS is made to initiate a activation of CW (all basic service groups)
29
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
30
SS -> MS
IMMEDIATE ASSIGNMENT
31
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
32
SS -> MS
CM SERVICE ACCEPT
33
MS -> SS
REGISTER
34
SS -> MS
RELEASE COMPLETE
ActivateSS operation Return Error
35
SS -> MS
CHANNEL RELEASE
36
MS
Provide correct MMI user indication after step 34
37
MS
The MS is made to initiate activation of CW for a basic service group supported by the MS
38
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
39
SS -> MS
IMMEDIATE ASSIGNMENT
40
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
41
SS -> MS
CM SERVICE ACCEPT
42
MS -> SS
REGISTER
43
SS -> MS
RELEASE COMPLETE
ActivateSS operation Reject
44
SS -> MS
CHANNEL RELEASE
45
MS
Provide correct MMI user indication after step 43
46
MS
The MS is made to initiate a activation of CW (all basic service groups)
47
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
48
SS -> MS
IMMEDIATE ASSIGNMENT
49
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
50
SS -> MS
CM SERVICE ACCEPT
51
MS -> SS
REGISTER
52
SS -> MS
RELEASE COMPLETE
ActivateSS operation Reject
53
SS -> MS
CHANNEL RELEASE
Specific message contents:
step 6, 24, 42 - CW
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Activation:
Supplementary service code = CW.
Basic service code: the selected basic service group.
step 15, 33, 51 - CW
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Activation:
Supplementary service code = CW.
Basic service code: no bearer service present, no teleservice present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.5 Deactivation | Conformance requirement
3GPP TS 04.83 subclause 1.5.
Test purpose
To test the correct operation of the deactivation procedure, and correct display of the response from the SS in the following cases.
1) Successful deactivation.
2) Error response (reject).
3) Activation reject (Invoke problem).
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 deactivation 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 deactivation of CW for a basic service group supported by the MS.
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 DeactivateSS 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 deactivation 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 DeactivateSS operation.
The SS transaction is released and the dedicated channel is released.
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests deactivation of CW for a basic service group supported by the MS.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a Return Error component with Error code:SS not available.
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 deactivation of CW for all basic service groups.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a Return Error component with Error code:SS not available.
The SS transaction is released and the dedicated channel is released.
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests deactivation of CW for a basic service group supported by the MS.
Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing A Reject component with Invoke problem (Resource limitation).
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 deactivation 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 A Reject component with Invoke problem (Resource limitation).
Maximum duration of test
9 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a deactivation of CW for a basic service group supported by the MS
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
DeactivateSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
MS
Provide correct MMI user indication after step 7
10
MS
The MS is made to initiate a deactivation of CW (all basic services)
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
DeactivateSS operation Return result
17
SS -> MS
CHANNEL RELEASE
19
MS
TThe MS is made to initiate a deactivation of CW for a basic service group supported by the MShe MS is made to initiate a deactivation of call forwarding service for CW for the selected basic service group
20
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
21
SS -> MS
IMMEDIATE ASSIGNMENT
22
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
23
SS -> MS
CM SERVICE ACCEPT
24
MS -> SS
REGISTER
25
SS -> MS
RELEASE COMPLETE
DeactivateSS operation Return Error
26
SS -> MS
CHANNEL RELEASE
27
MS
Provide correct MMI user indication after step 25
28
MS
The MS is made to initiate a deactivation of CW (all basic service groups)
29
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
30
SS -> MS
IMMEDIATE ASSIGNMENT
31
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
32
SS -> MS
CM SERVICE ACCEPT
33
MS -> SS
REGISTER
34
SS -> MS
RELEASE COMPLETE
DeactivateSS operation Return Error
35
SS -> MS
CHANNEL RELEASE
36
MS
Provide correct MMI user indication after step 34
37
MS
The MS is made to initiate a deactivation of CW for a basic service group supported by the MS
38
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
39
SS -> MS
IMMEDIATE ASSIGNMENT
40
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
41
SS -> MS
CM SERVICE ACCEPT
42
MS -> SS
REGISTER
43
SS -> MS
RELEASE COMPLETE
DeactivateSS operation Reject
44
SS -> MS
CHANNEL RELEASE
45
MS
Provide correct MMI user indication after step 43
46
MS
The MS is made to initiate a deactivation of CW (all basic service groups)
47
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
48
SS -> MS
IMMEDIATE ASSIGNMENT
49
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
50
SS -> MS
CM SERVICE ACCEPT
51
MS -> SS
REGISTER
52
SS -> MS
RELEASE COMPLETE
DeactivateSS operation Reject
53
SS -> MS
CHANNEL RELEASE
54
MS
Provide correct MMI user indication after step 52
Specific message content
step 6, 24, 42 - CW
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Deactivation:
Supplementary service code = CW.
Basic service code: the selected basic service group.
step 15, 33, 51 - CW
- protocol discriminator: non call related SS message.
- message type: REGISTER.
- facility:
invoke = Deactivation:
Supplementary service code = CW.
Basic service code: no bearer service present |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.6 Interrogation | |
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.