26.13.2 Multislot signalling / CC
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
26.13.2.1 Multislot signalling / CC / In-call functions
26.13.2.1.1 Multislot signalling / CC / In-call functions / User initiated service level upgrade / successful
26.13.2.1.1.1 Definition
Multislot connection is established. Multislot configuration with one TCH/F is allocated. User initiated service level upgrade is successfully performed.
26.13.2.1.1.2 Conformance requirements
1) MS shall send MODIFY message to SS indicating that User initiated service level upgrade is initiated.
2) MS enters CC state ‘Mobile originating modify (U26)’ after sending MODIFY.
3) MS enters CC state ‘Active (U10)’ when MODIFY COMPLETE is received.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.13.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.5.1.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.5.2.
26.13.2.1.1.3 Test purpose
1) To verify that the procedure is initiated by the MS in the "active" state of a multislot connection. It sends a MODIFY message including the wanted value of the "maximum number of traffic channels" and/or the "wanted air interface" parameters; and enters the "mobile originating modify" state. Other parameters of the bearer capability given in MODIFY message and already negotiated and agreed during the establishment phase of the call, may not be changed.
2) To verify that upon receipt of the MODIFY COMPLETE message with bearer capability negotiated at call setup in the MS enters the "active" state.
26.13.2.1.1.4 Method of test
Initial conditions
Mobile station:
– MS in the active state of a service using a multislot connection.
System simulator:
– 1 cell, default parameters except:
– Early classmark sending enabled in SI3 rest octets
Specific PICS statements:
– Multislot class (TSPC_Type_Multislot_ClassX)
PIXIT statements:
–
Foreseen final state of the MS
MS is in the active state of a service using a multislot connection.
Test procedure
MS is in the active state of a multislot connection. Multislot configuration with one TCH/F is allocated. User initiates User initiated service level upgrade by sending MODIFY message including the wanted value of the Maximum number of traffic channels, this being one supported by the MS and channel modes supported by the MS. The MS enters ‘mobile originating modify’ state. This is verified by a status enquiry procedure.
MS receives MODIFY COMPLETE message from SS and enters the ‘active’ state. This is verified by a status enquiry procedure.
Maximum duration of test
3 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
MODIFY |
User initiated service level upgrade is initiated. |
2 |
MS |
MS enters the Mobile originating modify state |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
Cause shall be 30# (response to enq.) and state U26 Mobile originated modify. |
5 |
SS -> MS |
MODIFY COMPLETE |
|
6 |
MS |
MS enters the active state |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
STATUS |
Cause shall be 30# (response to enq.) and state U10 Active. |
Specific message contents
MODIFY
Information element |
Value/remark |
Bearer capability |
Maximum number of TCH/F’s the MS is able to support and channel modes supported by the MS |
Low layer comp. |
Appropriate for the basic service selected for the test |
High layer comp. |
Appropriate for the basic service selected for the test |
Reverse call setup direction |
Presence and value not checked |
26.13.2.1.2 Multislot signalling / CC / In-call functions / User initiated service level downgrade / successful
25.13.2.1.2.1 Definition
Multislot connection is established. Multislot configuration has the maximum number of timeslots supported by the MS. User initiated service level downgrade is successfully performed.
26.13.2.1.2.2 Conformance requirements
1) MS shall send MODIFY message to SS indicating that User initiated service level downgrade is initiated.
2) MS enters CC state ‘Mobile originating modify (U26)’ after sending MODIFY.
3) MS enters CC state ‘Active (U10)’ when MODIFY COMPLETE is received.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.13.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.5.1.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.5.2.
26.13.2.1.2.3 Test purpose
1) To verify that the procedure is initiated by the MS in the "active" state of a multislot connection. It sends a MODIFY message including the wanted value of the "maximum number of traffic channels" and/or the "wanted air interface" parameters; and enters the "mobile originating modify" state. Other parameters of the bearer capability given in MODIFY message and already negotiated and agreed during the establishment phase of the call, may not be changed.
2) To verify that upon receipt of the MODIFY COMPLETE message with bearer capability negotiated at call setup in the MS enters the "active" state.
26.13.2.1.2.4 Method of test
Initial conditions
Mobile station:
– MS in the active state of a service using a multislot connection. Multislot configuration has maximum number of timeslots supported by the MS.
System simulator:
– 1 cell, default parameters except:
– Early classmark sending enabled in SI3 rest octets
Specific PICS statements:
– Multislot class (TSPC_Type_Multislot_ClassX)
PIXIT statements:
–
Foreseen final state of the MS
MS is in the active state of a service using a multislot connection.
Test procedure
MS in the active state of a multislot connection. Multislot configuration has maximum number of timeslots supported by the MS. User initiates User initiated service level downgrade by sending MODIFY message including the wanted value of the Maximum number of traffic channels, this being one supported by the MS and channel modes supported by the MS. The MS enters ‘mobile originating modify’ state. This is verified by a status enquiry procedure.MS receives MODIFY COMPLETE message from SS and enters the active state. This is verified by a status enquiry procedure.
Maximum duration of test
3 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
MODIFY |
User initiated service level downgrade is initiated. |
2 |
MS |
MS enters the Mobile originating modify state |
|
3 |
SS -> MS |
STATUS ENQUIRY |
|
4 |
MS -> SS |
STATUS |
Cause shall be 30# (response to enq.) and state U26 Mobile originated modify. |
5 |
SS -> MS |
MODIFY COMPLETE |
|
6 |
MS |
MS enters the active state |
|
7 |
SS -> MS |
STATUS ENQUIRY |
|
8 |
MS -> SS |
STATUS |
Cause shall be 30# (response to enq.) and state U10 Active. |
Specific message contents
MODIFY
Information element |
Value/remark |
Bearer capability |
One TCH/F is indicated and the channel modes supported by the MS |
Low layer comp. |
Appropriate for the basic service selected for the test |
High layer comp. |
Appropriate for the basic service selected for the test |
Reverse call setup direction |
Presence and value not checked |
26.13.2.1.3 Multislot signalling / CC / In-call functions / User initiated service level upgrade / Time-out of timer T323
26.13.2.1.3.1 Definition
Multislot connection is established. Multislot configuration with one TCH/F is allocated. User initiated service level upgrade is requested. Timer T323 expires. Call is cleared.
26.13.2.1.3.2 Conformance requirements
1) MS shall send MODIFY message to SS indicating that User initiated service level upgrade is initiated.
2) After timer T323 has expired MS starts call clearing by sending DISCONNECT message.
3) After receipt of RELEASE message the MS sends RELEASE COMPLETE message and goes to idle updated state.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.13.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.7.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 9.3.18 and 5.4.4.2.2,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.7.
26.13.2.1.3.3 Test purpose
1) To verify that upon expiration of T323 (accuracy ± 10%) the MS shall initiate the procedures for call clearing with cause #102 "recovery on timer expiry".
26.13.2.1.3.4 Method of test
Initial conditions
Mobile station:
– MS in the active state of a service using a multislot connection.
System simulator:
– 1 cell, default parameters
Specific PICS statements:
– Multislot class (TSPC_Type_Multislot_ClassX)
PIXIT statements:
–
Foreseen final state of the MS
"Idle, updated", with TMSI allocated.
Test procedure
MS is in the active state of a multislot connection. Multislot configuration with one TCH/F is allocated. User initiates User initiated service level upgrade by sending MODIFY message including the wanted value of the Maximum number of traffic channels, this being one supported by the MS and channel modes supported by the MS.
Timer T323 expires and MS starts call clearing procedure by sending DISCONNECT message to SS. After MS receives RELEASE message it sends RELEASE COMPLETE message. SS sends CHANNEL RELEASE message to MS and the main signalling link is released.
Maximum duration of test
3 minutes.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
MODIFY |
User initiated service level upgrade is initiated. |
2 |
MS |
Timer T323 expires |
|
3 |
MS -> SS |
DISCONNECT |
Cause = #102 "recovery on timer expiry" |
4 |
SS -> MS |
RELEASE |
|
5 |
MS -> SS |
RELEASE COMPLETE |
|
6 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released |
Specific message contents
MODIFY
Information element |
Value/remark |
Bearer capability |
Maximum number of TCH/F’s the MS is able to support and channel modes supported by the MS |
Low layer comp. |
Appropriate for the basic service selected for the test |
High layer comp. |
Appropriate for the basic service selected for the test |
Reverse call setup direction |
Presence and value not checked |
26.13.2.1.4 Multislot signalling / CC / In-call functions / User initiated service level upgrade / modify reject
26.13.2.1.4.1 Definition
Multislot connection is established. Multislot configuration with one TCH/F is allocated. User initiated service level upgrade is requested. SS responds to upgrade request by rejecting it. MS enters the active multislot connection state.
26.13.2.1.4.2 Conformance requirements
1) MS shall send MODIFY message to SS indicating that User initiated service level upgrade is initiated.
2) MS enters CC state ‘Mobile originating modify (U26)’ after sending MODIFY.
3) MS enters CC state ‘Active (U10)’ when MODIFY REJECT is received.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.13.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.5.1.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.5.3.
26.13.2.1.4.3 Test purpose
1) To verify that upon receipt of the MODIFY REJECT message with the bearer capability negotiated at the call setup, the MS is continuously sending user information according to current call mode.
26.13.2.1.4.4 Method of test
Initial conditions
Mobile station:
– MS in the active state of a service using a multislot connection.
System simulator:
– 1 cell, default parameters
Specific PICS statements:
– Multislot class (TSPC_Type_Multislot_ClassX)
PIXIT statements:
–
Foreseen final state of the MS
MS is in the active state of a service using a multislot connection.
Test procedure
MS is in the active state of a multislot connection. Multislot configuration with one TCH/F is allocated. Then user initiates User initiated service level upgrade by sending MODIFY message including the wanted value of the Maximum number of traffic channels, this being one supported by the MS and channel modes supported by the MS. The MS enters ‘mobile originating modify’ state. This is verified by a status enquiry procedure.SS responds to MODIFY message by sending MODIFY REJECT message to MS. MS enters the active state. This is verified by a status enquiry procedure.Maximum duration of test
1 minute.
Expected sequence
Step |
Direction |
Message |
Comments |
1 |
MS -> SS |
MODIFY |
User initiated service level upgrade is initiated. |
2 |
SS -> MS |
STATUS ENQUIRY |
|
3 |
MS -> SS |
STATUS |
Cause shall be 30# (response to enq.) and state U26 Mobile originated modify. |
4 |
SS -> MS |
MODIFY REJECT |
Cause = #58 "bearer capability not presently available". |
5 |
MS |
MS enters in the active state of multislot call |
|
6 |
SS -> MS |
STATUS ENQUIRY |
|
7 |
MS -> SS |
STATUS |
Cause shall be 30# (response to enq.) and state U10 Active. |
Specific message contents
MODIFY
Information element |
Value/remark |
Bearer capability |
Maximum number of TCH/F’s the MS is able to support and channel modes supported by the MS |
Low layer comp. |
Appropriate for the basic service selected for the test |
High layer comp. |
Appropriate for the basic service selected for the test |
Reverse call setup direction |
Presence and value not checked |
26.13.2.1.5 Multislot signalling / CC / In call functions / contents of some of the messages
The following messages are used for testing in-call modification procedures, test cases 26.13.2.1.*, as default messages for those ones defined below. If any other values are defined in the expected sequence of the actual test cases, those values take precedence over the ones defined hereafter.
SETUP (MS to SS)
Information element |
Value/remark |
BC Repeat indicator |
Omitted |
Bearer capability 1 |
Appropriate for the teleservice/Bearer Service selected as an initial call mode |
Bearer capability 2 |
Omitted |
Facility |
Omitted |
Calling party subaddress |
Omitted |
Called party BCD number |
As entered |
Called party subaddress |
Omitted |
LLC repeat indicator |
Omitted |
Low layer compatibility I |
See note |
Low layer compatibility II |
Omitted |
HLC repeat indicator |
Omitted |
High layer compatibility I |
See note |
High layer compatibility ii |
Omitted |
User-user |
Omitted |
SS version |
Omitted |
CLIR suppression |
Omitted |
CC Capabilities |
present, but contents not checked |
NOTE: HLC/LLC may or may not be present. The contents of HLC/LLC are not verified. |
CALL PROCEEDING
Information element |
Value/remark |
Repeat Indicator |
Omitted |
Bearer Capability 1 |
3GPP TS 04.08 / 3GPP TS 24.008 subclause 10.5.4.5 |
Bearer Capability 2 |
Omitted |
Facility |
Omitted |
Progress indicator |
Omitted |
MODIFY
Information element |
Value/remark |
Bearer capability |
Appropriate for the selected test |
Low layer comp. |
Appropriate for the basic service selected for the test |
High layer comp. |
Appropriate for the basic service selected for the test |
Reverse call setup direction |
Presence and value not checked |
MODIFY COMPLETE
Information element |
Value/remark |
Bearer capability |
Appropriate for the selected test |
Low layer comp. |
Appropriate for the basic service selected for the test |
High layer comp. |
Appropriate for the basic service selected for the test |
Reverse call setup direction |
Presence and value not checked |
MODIFY REJECT
Information element |
Value/remark |
Bearer capability |
Appropriate for the selected test |
Cause |
#58 "bearer capability not presently available". |
Low layer compatibility |
Appropriate for the basic service selected for the test |
High layer compatibility |
Appropriate for the basic service selected for the test |