31.1 Number identification supplementary services
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
31.1.1 CLIP
31.1.1.1 Normal operation
Conformance requirement:
3GPP TS 04.81 subclause 1.1.
Purpose:
To test that the MS presents to the user the calling number presented to it in an incoming SETUP message.
Specific PICS Statements
– Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
– Description of display for CLIP.
– Support of displaying the calling party subaddress.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The SIM in the MS under test has CLIP enabled.
Foreseen final state of the MS
State U7
Maximum duration of test
30 s.
Procedure:
Set up an MT call to the MS under test. The SETUP message shall include a calling party BCD number information element and a calling party subaddress information element.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
SS sends paging |
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
(SDCCH) |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
9 |
SS -> MS |
SETUP |
Shall include a valid calling party BCD number and calling party subaddress |
10 |
MS -> SS |
CALL CONFIRMED |
|
11 |
MS -> SS |
ALERTING |
|
12 |
MS |
Depending on the PICS, the MS shall display the calling party BCD number and calling party subaddress |
31.1.1.2 Interrogation
31.1.1.2.1 Interrogation accepted
Conformance requirement:
3GPP TS 04.81 subclause 1.2.
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 CLIP.
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 CLIP 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.
Maximum duration of test
3 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate an interrogation of CLIP (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 |
Specific message content
step 6 – CLIP
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation
Supplementary service code = CLIP.
Basic service code: no Bearer Service present, no teleservice present.
31.1.1.2.2 Interrogation rejected
Conformance requirement
3GPP TS 04.81 subclause 1.2.
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 interrogation of CLIP.
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 CLIP 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 CLIP 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 for CLIP (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 CLIP (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 – CLIP
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation
Supplementary service code = CLIP.
Basic service code:no Bearer Service present, no teleservice present.
step 5 – CLIP
– 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.
31.1.2 CLIR
31.1.2.1 Normal operation – requesting presentation of CLI
Conformance requirement:
3GPP TS 04.81 subclause 2.2.
Test Purpose
To test that when the CLIR presentation mode is temporary (presentation restricted), it is possible for the subscriber to present his CLI on a per call basis.
Method of test
Specific PICS Statements
– Supported MO circuit switched basic services (TSPC_AddInfo_MOsvc)
PIXIT Statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The SIM in the MS under test has CLIR enabled with CLIR presentation mode "temporary (presentation restricted)".
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U0.1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U1, call initiated.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Using MMI commands, the MS is made to initiate an outgoing call with CLI presented. When the MS is requesting a MM-connection, the SS will indicate acceptance by sending a CM SERVICE ACCEPT message. The MS shall respond with SETUP. The SETUP message shall contain the CLIR suppression information element.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CM SERVICE ACCEPT |
|
2 |
MS -> SS |
SETUP |
with CLIR suppression information element |
31.1.2.2 Normal operation – requesting restriction of CLI presentation
Conformance requirement:
3GPP TS 04.81 subclause 2.3.
Test Purpose
To test that when the CLIR presentation mode is temporary (presentation allowed), it is possible for the subscriber to present his CLI on a per call basis.
Procedure
Using MMI commands, the MS is made to initiate an outgoing call with CLI restricted.
Requirements:
The SETUP message sent by the MS shall include the CLIR invocation information element.
Method of test
Specific PICS Statements
– Supported MO circuit switched basic services (TSPC_AddInfo_MOsvc)
PIXIT Statements
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The SIM in the MS under test has CLIR enabled with CLIR presentation mode "temporary (presentation allowed)".
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U0.1 by using table 26.8.1.2/1.
Foreseen final state of the MS
U1, call initiated.
Maximum duration of test
30 s.
Test procedure
An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Using MMI commands, the MS is made to initiate an outgoing call with CLI restricted. When the MS is requesting a MM-connection, the SS will indicate acceptance by sending a CM SERVICE ACCEPT message. The MS shall respond with SETUP. The SETUP message sent by the MS shall include the CLIR invocation information element.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CM SERVICE ACCEPT |
|
2 |
MS -> SS |
SETUP |
with CLIR invocation information element |
31.1.2.3 Interrogation
31.1.2.3.1 Interrogation accepted
Conformance requirement:
3GPP TS 04.81 subclause 2.4.
Applicability
MS supporting the CLIR supplementary service.
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 CLIR.
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 CLIR 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.
Maximum duration of test
3 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate an interrogation of CLIR (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 |
Specific message content
step 6 – CLIR
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation:
Supplementary service code = CLIR.
Basic service code: no Bearer Service present, no teleservice present.
31.1.2.3.2 Interrogation rejected
Conformance requirement
3GPP TS 04.81 subclause 2.4.
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 interrogation of CLIR.
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 CLIR 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 CLIR 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 for CLIR (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 CLIR (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 – CLIR
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation:
Supplementary service code = CLIR.
Basic service code:no Bearer Service present, no teleservice present.
step 5 – CLIR
– 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.
31.1.3 COLP
31.1.3.1 Normal operation
Conformance requirement:
3GPP TS 04.81 subclause 3.1.
Purpose:
To test that the MS displays the connected number presented to it in an incoming CONNECT message.
Method of test
Specific PICS Statements
– Supported MO circuit switched basic services (TSPC_AddInfo_MOsvc)
PIXIT Statements
– Description of display for COLP.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The SIM in the MS under test has COLP enabled.
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
The MS is brought into the state U1 by using table 26.8.1.2/4.
Foreseen final state of the MS
U10, call active.
Maximum duration of test
30 s.
Test procedure
1. An MO circuit switched basic service is selected that is supported by the MS; if the MS supports MO telephony, the selected basic service is telephony. If necessary, the MS is configured for that basic service. Then, the MS is made to initiate a call. The CC entity of the MS is brought to the state U4. The SS sends a CONNECT message to the MS containing a connected number information element and a connected party subaddress information element. The MS shall respond by sending a CONNECT ACKNOWLEDGE message. The MS shall correctly display the connected line information.
Expected sequence, procedure 1
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
CONNECT |
See specific message contents |
2 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
3 |
MS |
The MS shall correctly display the connected line information |
Specific message contents
CONNECT
Connected number information element |
|
Presentation indicator |
Presentation allowed |
Screening indicator |
User provided, not screened |
Connected subaddress |
Any valid subaddress |
31.1.3.2 Interrogation
31.1.3.2.1 Interrogation accepted
Conformance requirement:
3GPP TS 04.81 subclause 3.2.
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 COLP.
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 COLP 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.
Maximum duration of test
3 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate an interrogation of COLP (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 |
Specific message content
step 6 – COLP
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation:
Supplementary service code = COLP.
Basic service code: no Bearer Service present, no teleservice present.
31.1.3.2.2 Interrogation rejected
Conformance requirement
3GPP TS 04.81 subclause 3.2.
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 interrogation of COLP.
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 COLP 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 COLP 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 for COLP (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 COLP (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 – COLP
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation:
Supplementary service code = COLP.
Basic service code:no Bearer Service present, no teleservice present.
step 5 – COLP
– 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.
31.1.4 COLR
31.1.4.1 Interrogation
31.1.4.1.1 Interrogation accepted
Conformance requirement:
3GPP TS 04.81 subclause 4.2.
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 COLR.
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 COLR 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.
Maximum duration of test
3 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate an interrogation of COLR (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 |
Specific message content
step 6 – COLR
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation:
Supplementary service code = COLR.
Basic service code: no Bearer Service present, no teleservice present.
31.1.4.1.2 Interrogation rejected
Conformance requirement
3GPP TS 04.81 subclause 4.2.
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 interrogation of COLR.
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 COLR 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 COLR 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 for COLR (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 COLR (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 – COLR
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation:
Supplementary service code = COLR.
Basic service code:no Bearer Service present, no teleservice present.
step 5 – COLR
– 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.
31.1.4.2 Void
31.1.5 CNAP
31.1.5.1.1 Normal Operation – Name indication contained in Setup message
Conformance requirements
3GPP TS 24.096 subclause 4.1
Purpose
To test that the MS presents to the user the name information of the calling party to the called party at call setup time for all incoming calls.
Specific PICS Statements
– Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
– Description of display for CNAP.
Initial Conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is in MM-state “idle, updated” with valid TMSI and CKSN
Foreseen final state of the MS
Stae U7
Maximum Duration of Test
3 minutes.
Procedure
Set up an MT Call to the MS under test. The SS sends the Name Indication in the Facilty IE of the CC Setup
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
SS sends paging |
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
(SDCCH) |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
9 |
SS -> MS |
SETUP |
Shall include Facility (Invoke = NotifySS (CNAP, nameIndicator )) Signal IE included |
10 |
MS -> SS |
CALL CONFIRMED |
|
11 |
MS -> SS |
ALERTING |
|
12 |
MS |
Depending on the PICS, the MS shall display the calling nameIndicator |
Specific message content
step 9 – CNAP nameIndicator settings:
– namePresentationAllowed
– NameSet: “TESTNAME”
31.1.5.1.2 Normal Operation – Name indication contained in Facility message
Conformance requirements
3GPP TS 24.096 subclause 4.1
Purpose
To test that the MS presents to the user the name information of the calling party to the called party at call setup time for all incoming calls.
Specific PICS Statements
– Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
– Description of display for CNAP.
Initial Conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is in MM-state “idle, updated” with valid TMSI and CKSN
Foreseen final state of the MS
Stae U7
Maximum Duration of Test
3 minutes.
Procedure
Set up an MT Call to the MS under test. The SS sends the Name Indication in a Facilty message
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST |
SS sends paging |
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
(SDCCH) |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
9 |
SS -> MS |
SETUP |
Signal IE included |
10 |
MS -> SS |
CALL CONFIRMED |
|
11 |
MS -> SS |
ALERTING |
|
12 |
SS -> MS |
FACILITY |
Facility (Invoke=NotifiSS (CNAP, nameIndicator)) |
13 |
MS |
Depending on the PICS, the MS shall display the calling nameIndicator |
Specific message content
step 10 – CNAP nameIndicator settings:
– namePresentationAllowed
– NameSet: “TESTNAME”
31.1.5.2.1 Interrogation accepted
Conformance requirements
3GPP TS 24.096 subclause 4.2
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 CNAP.
Forseen final state of the MS
The MS is Idle Updated
Maximum Duration of Test
3 minutes.
Procedure
By mean´s of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the users requests interrogation of CNAP 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 InterrogtaeSS operation .
The SS transaction is released and the dedicated channel is released
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate an interrogation of CNAP (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 |
Facility (Invoke = InterrogateSS (CNAP)) |
7 |
SS -> MS |
RELEASE COMPLETE |
Facility (Return Result = InterrogateSS (ss-status)) |
8 |
SS -> MS |
CHANNEL RELEASE |
Specific message content
step 6 – CNAP
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation
Supplementary service code = CNAP.
Basic service code: no Bearer Service present, no teleservice present.
31.1.5.2.2 Interrogation rejected
Conformance requirements
3GPP TS 24.096 subclause 4.2
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.
Specific PICS Statements
–
PIXIT Statements
– Description of the user’s commands and of display of the answers from the network for interrogation of CNAP.
Initial Conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is in CC state U10
Maximum Duration of Test
3 minutes.
Procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of CNAP 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 CNAP 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.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is made to initiate an interrogation for CNAP (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 CNAP (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 – CNAP
– protocol discriminator: non call related SS message.
– message type: REGISTER.
– facility:
invoke = Interrogation
Supplementary service code = CNAP.
Basic service code:no Bearer Service present, no teleservice present.
step 5 – CNAP
– 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.