31.2 Call offering supplementary services
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
The following abbreviations are used:
CF: Call Forwarding (common name for CFU, CFB, CFNRy and CFNRc).
CFB: Call Forwarding on mobile subscriber Busy
CFC: Call Forwarding Conditional (common name for CFB, CFNRy and CFNRc)
CFNRc: Call Forwarding on mobile subscriber Not Reachable
CFNRy: Call Forwarding on No Reply
CFU: Call Forwarding Unconditional
NOTE: These abbreviations are also used to represent the corresponding SS-Code; e.g. CFC is the SS-Code for all conditional forwarding services.
31.2.1 Call forwarding supplementary services
31.2.1.1 Registration
31.2.1.1.1 Registration accepted
31.2.1.1.1.1 Conformance requirements
For registration 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 RegisterSS 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.
31.2.1.1.1.2 Test purpose
1) To check that the MS correctly requests a supplementary service transaction for registration of call forwarding in CHANNEL REQUEST message.
2) To check that the MS correctly requests a supplementary service transaction for registration of call forwarding in the subsequent CM SERVICE REQUEST.
3) 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.
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) CFNRy, for basic service group speech.
b) CFU, for basic service group all facsimile.
31.2.1.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
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of CFNRy for Speech, to a number arbitrarily selected and with a no reply time value 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 the return result of the RegisterSS 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 registration of CFU 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 the return result of the RegisterSS operation.
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 CFNRy (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 |
CNFRySS 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 registration of call forwarding service for CFU (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 |
RegisterSS operation Return result |
|
17 |
SS -> MS |
CHANNEL RELEASE |
|
|
18 |
MS |
Provide correct MMI user indication after step 16 |
Specific message content
step 6 – CFNRy
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Registration:
Supplementary service code = CFNRy.
Forwarded to number: as selected.
No reply condition time: as selected.
Basic service code: TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present.
step 7 – CFU
– protocol discriminator: non call related SS message.
– transaction identifier: same as at step 6.
– message type: RELEASE COMPLETE.
– facility:
Return Result = Registration:
Supplementary service code = CFNRy.
Forwarded to number.
No Reply condition time.
Basic service code: TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present.
step 15 – CFU
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Registration:
Supplementary service code = CFU.
Forwarded to number: as selected.
Basic service code: no bearer service present, teleservice (all facsimile).
step 16 – CFU
– protocol discriminator: non call related SS message.
– transaction identifier: same as at step 15.
– message type: RELEASE COMPLETE.
– facility:
Return Result = Registration:
Supplementary service code = CFU.
Forwarded to number.
Basic service code: TeleService (all facsimile), no Bearerservice present.
31.2.1.1.2 Registration rejected
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.
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".
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.
31.2.1.2 Erasure by the subscriber
31.2.1.2.1 Erasure accepted
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.
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.
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.
31.2.1.2.2 Erasure rejected
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.
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".
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.
31.2.1.3 Activation
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.
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.
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.
31.2.1.4 Deactivation
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.
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.
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).
31.2.1.5 Invocation
Invocation is not applicable to the MS and causes no signalling on the radio path.
31.2.1.6 Interrogation
31.2.1.6.1 Interrogation accepted
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.
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.
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).
31.2.1.6.2 Interrogation rejected
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.
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".
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.
31.2.1.7 Normal operation
31.2.1.7.1 Served mobile subscriber side
31.2.1.7.1.1 Notification during an incoming call
This subscription option is only applicable to CFB and CFNRy.
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.
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.
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).
31.2.1.7.1.2 Notification during an outgoing call
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.
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.
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).
31.2.1.7.2 Forwarded-to mobile subscriber side
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.
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).
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.
31.2.2 Call transfer and mobile access hunting supplementary services
(Reserved).