hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
30.20 Side Tone Masking Rating (STMR) HATS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
30.20.1 Definition
|
The sidetone loudness ratings are a means of expressing the path loss from the artificial mouth to the artificial ear based on objective single tone measurements in a way that relates to how a speaker will perceive his own voice when speaking (talker sidetone, expressed by the sidetone masking rating - STMR), or how a listener will perceive the background noise picked up by the microphone (listener sidetone rating - LSTR).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
30.20.2 Conformance requirement
|
The conformance requirement is specified in 3GPP TS 26.131.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
30.20.3 Test purpose
|
To verify that the requirement for STMR stated in TS 26.131 is met.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
30.20.4 Method of test
|
The method of test shall be as specified in 3GPP TS 26.132 section 7.5.1.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
30.20.5 Test requirement
|
The STMR shall be within the limits specified in 3GPP TS 26.131.
31 Test of supplementary services
The general aspects of the specification of supplementary services at the layer 3 radio interface are given in 3GPP TS 04.10.
The formats and coding are given in 3GPP TS 04.80. If the value of a parameter of an uplink message (MS to network) is specified in a test, the implicit meaning is that it has to be checked; if the value is not specified, it is not to be checked unless otherwise stated.
Unless otherwise stated, the MS shall be in the idle updated state at the beginning of each test (including repetition of a test).
In each test, before the MS sends the first REGISTER message, a MM connection is established.
3GPP TS 04.81 to 3GPP TS 04.88 give the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of supplementary services.
The supplementary services are described in 3GPP TS 02.04 and 3GPP TS 02.81 to 3GPP TS 02.88.
Whenever activation via the standard MMI is mentioned, if the MS does not support it but supports a different procedure, this different procedure is used. In the supplementary services tests, only the applicable (see 3GPP TS 02.8x series) MMI service code groups (3GPP TS 02.30 annex 4), of the basic service code in 3GPP TS 09.02,which are supported by the MAP, will be used.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1 Number identification supplementary services
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.1 CLIP
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.1.2 Interrogation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.2 CLIR
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.2.3 Interrogation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.3 COLP
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.3.2 Interrogation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.4 COLR
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.4.1 Interrogation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.4.2 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.1.5 CNAP
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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”
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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”
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.2 Call offering supplementary services
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.2.1 Call forwarding supplementary services
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.2.1.1 Registration
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
31.2.1.1.1 Registration accepted
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
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.
|
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
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.