hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4 In call functions
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.1 In-call functions / DTMF information transfer
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.1.1 In-call functions / DTMF information transfer / basic procedures
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.1.1.1 Definition
|
Dual Tone Multi Frequency (DTMF) is an inband one out of four plus one out of four signalling system primarily used from terminal instruments in telecommunication networks.
The support of DTMF is only permitted when a bearer capability for speech is in use or during the speech phase of alternate speech/data and alternate speech/facsimile teleservices.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.1.1.2 Conformance requirement
|
1) An MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone, shall send a START DTMF message on the correct DCCH.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.3.
2) An MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone (the corresponding IA5 character being selected from among the ones supported), shall send a START DTMF message specifying the correct IA5 character in the "keypad information" field of the keypad facility information element.
2.1 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.1.1.3 Test purpose
|
1) To verify that an MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone, sends a START DTMF message on the correct DCCH.
2) To verify that an MS supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone (the corresponding IA5 character being selected from among the ones supported), sends a START DTMF message specifying the correct IA5 character in the "keypad information" field of the keypad facility information element.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.1.1.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- supported character set (e.g. 0‑9, #, *, A, B, C, D);
- if and how DTMF tone is indicated to the user.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
1 min.
Test procedure
The MS being in the call active state, a user causes a DTMF tone to be generated e.g. by depression of a key in the MS. A DTMF digit corresponding to the digit indicated by the user is sent in a START DTMF message by the MS. The SS will return a START DTMF ACKNOWLEDGE message to the MS. This acknowledgement may be used in the MS to generate an indication as a feedback for a successful transmission. Then the user indicates that the DTMF sending should cease e.g. by releasing the key. The MS will send a STOP DTMF message to the network which is acknowledged with STOP DTMF ACKNOWLEDGE by the SS.
The sequence described above is repeated for each of the applicable characters 0‑9, #, *, A, B, C, and D.
Then a case of rejecting a DTMF tone is tested and the state of the MS is verified.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
START DTMF
the user causes DTMF tone to be generated
SS
the SS will verify that the transmitted information corresponds to the digit pressed
2
SS -> MS
START DTMF ACKNOWLEDGE
possible indication of a DTMF tone depending the PIXIT statements
3
SS -> MS
STATUS ENQUIRY
4
MS -> SS
STATUS
cause 30#, state U10
5
MS -> SS
STOP DTMF
6
SS -> MS
STOP DTMF ACKNOWLEDGE
the DTMF tone indication shall be stopped
7
the steps 1‑6 shall be repeated for each of the applicable characters 0‑9, #, *, A, B, C, D.
8
SS -> MS
STATUS ENQUIRY
9
MS -> SS
STATUS
cause 30#, state U10
10
MS -> SS
START DTMF
11
SS -> MS
START DTMF REJECT
12
SS -> MS
STATUS ENQUIRY
13
MS -> SS
STATUS
cause 30#, state U10
Specific message contents:
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.2 In-call functions / user notification
|
User notification procedure allows the network to notify a MS of any call-related event during the "active" state of a call. It also may allow a MS to notify the remote user of any appropriate call-related event during the "active" state of a call by sending a NOTIFY message containing a notification indicator to the network. No state change occurs at any of the interface sides during this procedure.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.2.1 In-call functions / User notification / MS terminated
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.2.1.1 Definition
|
This is a case for testing user notification procedure terminated by the mobile station. The test is applicable for those equipments supporting at least one circuit switched basic service.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.2.1.2 Conformance requirement
|
1) A CC entity of a MS in CC-state U10, "active", upon receiving of a NOTIFY message shall remain in the active state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.2.1.3 Test purpose
|
To verify that a CC entity of a MS in CC-state U10, "active", upon receiving of a NOTIFY message remains in the active state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.2.1.4 Method of test
|
Specific PICS statements
-
PIXIT statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS being in the call active state, the SS will send a NOTIFY message to the MS. The state of the MS is checked after that.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
NOTIFY
2
SS -> MS
STATUS ENQUIRY
3
MS -> SS
STATUS
cause 30#, state U10
Specific message contents:
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3 In-call functions / channel changes
|
The two following test cases are for testing some elementary radio resource level procedures during an active state of a call to ensure call maintenance also during physical channel changes.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.1 In-call functions / channel changes / a successful channel change in active state/ Handover and Assignment Command
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.1.1 Definition
|
This is a case to test a change of a physical channel during active state of a call. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.1.2 Conformance requirement
|
1) The MS being in the call active state after having successful completed a channel assignment or a handover command, shall remain in the call active state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.6.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.1.3 Test purpose
|
To verify that the MS being in the call active state after having successful completed a channel assignment or having completed a handover command remains in the call active state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.1.4 Method of test
|
Specific PICS statements
-
PIXIT statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The SS initiates a call to the Mobile Station, using an arbitrarily chosen MT circuit switched basic service (see clause 10 for generic call set up procedures).
The MS being in the call active state, the SS initiated channel assignment procedure causing an intracell change of channel by sending ASSIGNMENT COMMAND message to the MS. The MS performs channel assignment procedure and after the main signalling link is successfully established, the MS returns an ASSIGNMENT COMPLETE message. The state of the MS is then checked.
The SS then initiates a Finely Synchronized handover intra cell procedure. On the successful completion of this procedure the state of the MS is checked.
Expected sequence
Step
Direction
Message
Comments
0
Generic call set up procedure defined in subclauses 10.1 and 10.3, depending on choice of Bearer Capability.
1
SS -> MS
ASSIGNMENT COMMAND
2
MS -> SS
ASSIGNMENT COMPLETE
3
SS -> MS
STATUS ENQUIRY
4
MS -> SS
STATUS
cause 30#, state U10
5
SS -> MS
HANDOVER COMMAND
See Specific message contents.
6
MS -> SS
HANDOVER ACCESS
7
MS -> SS
HANDOVER ACCESS
8
MS -> SS
HANDOVER ACCESS
9
MS -> SS
HANDOVER ACCESS
Before completion of the 4 access bursts on the new DCCH, additional access bursts may also be sent on the SACCH
10
MS -> SS
HANDOVER COMPLETE
11
SS -> MS
STATUS ENQUIRY
12
MS -> SS
STATUS
cause 30#, state U10
Specific message contents:
ASSIGNMENT COMMAND
Information Element
value/remark
Channel Description
As used in Assignment Command when setting up the call, except:
- Timeslot Number
Arbitrary value, but different to originally used.
HANDOVER COMMAND
Information Element
value/remark
Cell Description
- Network Colour Code
1
- Base Station Colour Code
5
- BCCH Carrier Number
GSM 450 – ARFCN 263
GSM 480 – ARFCN 310
P-GSM 900 - ARFCN 20
DCS 1 800 - ARFCN 590
PCS 1 900 – ARFCN 650
GSM 710 – ARFCN 457
GSM 750 – ARFCN 457
T-GSM 810 – ARFCN 457
GSM 850 – ARFCN 147
Channel Description
As used in Assignment Command when setting up the call, except:
- Timeslot Number
Arbitrary value, but different to originally used.
Synchronization Indication
- Report Observed Time Difference
Shall not be included.
- Synchronization Indication
"Synchronized".
- Normal Cell Indication
Ignore out of range timing advance.
STATUS
Information Element
value/remark
cause
#30, statue U10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.2 In-call functions / channel changes / an unsuccessful channel change in active mode/ Handover and Assignment Command
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.2.1 Definition
|
This is a case to test an unsuccessful change of a physical channel during active state of a call. This test is applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.2.2 Conformance requirement
|
1) The MS, when returning to the old channel after handover or Assignment failure and having established the link, shall remain in the call active state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.2.3 Test purpose
|
To verify that the MS, when returning to the old channel after handover or Assignment failure and correctly establishing the link, will remain in the call active state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.3.2.4 Method of test
|
Specific PICS statements
-
PIXIT statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
30 s.
Test procedure
The SS initiates a call to the Mobile Station, using an arbitrarily chosen circuit switched basic service (see clause 10 for generic call set up procedures).
The MS being in the call active state, the SS initiates non synchronized handover procedure to cell B. The MS begins to send access bursts on the new DCCH (and optionally the SACCH). The SS activates the SACCH, but does not send a PHYSICAL INFORMATION MESSAGE, thus causing timer T3124 to time-out. Then the MS shall return back to the old channel and re-establish the signalling link on cell A and send a HANDOVER FAILURE message. The state of the MS is then checked.
The SS sends an Assignment command message allocating a hopping TCH/F, but does not activate the assigned channel. The MS shall attempt try to activate the new channel (this is not verified) and shall then reactivate the "old" channel and trigger the establishment of the main signalling link on the old channel. The MS shall send an ASSIGNMENT FAILURE message. The state of the MS is then checked.
Expected sequence
Step
Direction
Message
Comments
0
Generic call set up procedure defined in subclauses 10.1 and 10.3, depending on choice of Bearer Capability.
1
SS -> MS
HANDOVER COMMAND
2
MS -> SS
HANDOVER ACCESS
Several messages are sent, all with the handover reference sent in the HANDOVER COMMAND message.
3
MS -> SS
HANDOVER FAILURE
4
SS -> MS
STATUS ENQUIRY
5
MS -> SS
STATUS
cause 30#, state U10
6
SS -> MS
ASSIGNMENT COMMAND
Channel type = TCH/F, hopping. The MS attempts and fails to establish a signalling link on the new channel.
7
The MS re-establishes the signalling link on the "old" channel.
8
MS -> SS
ASSIGNMENT FAILURE
RR cause value = "protocol error unspecified"
9
SS -> MS
STATUS ENQUIRY
10
MS -> SS
STATUS
cause 30#, state U10
Specific message contents:
ASSIGNMENT FAILURE
Information Element
value/remark
RR cause
"protocol error unspecified"
HANDOVER FAILURE
Information Element
value/remark
RR cause
Not checked, as tested elsewhere.
STATUS
Information Element
value/remark
cause
#30, statue U10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.4 In-call functions / MS terminated in-call modification
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.4.1 In-call functions / MS terminated in-call modification / modify when new mode is not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.4.1.1 Definition
|
This is to test a special case of a in-call modification procedure, in which the new mode is not supported (and consequently not one of those negotiated and agreed during the establishment phase of the call). This test is applicable for any equipment supporting at least one circuit switched basic service.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.4.1.2 Conformance requirement
|
1) In the case that the MS supports the network originated in-call modification procedure, the MS after having received a MODIFY message with a new mode which is not the actual one and cannot be supported by the MS shall reject it by sending a MODIFY REJECT message or a STATUS message.
2) In the case that the MS does not support the network originated in-call modification procedure, the MS shall, when receiving a MODIFY message, treat the message as unknown and respond with a STATUS message.
References
1) 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.3.4.3.4.2 and 5.3.4.4.
2) 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.4.1.3 Test purpose
|
1) To verify that an MS supporting the network originated in-call modification procedure, after having received a MODIFY message with a new mode which is not the actual one and cannot be supported by the MS, rejects it by sending a MODIFY REJECT.
2) To verify that an MS not supporting the network originated in-call modification procedure, after having received a MODIFY message, responds with a STATUS message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.4.1.4 Method of test
|
Specific PICS statements
- the MS supports the network originated in-call modification procedure (p = Yes/No) (TSPC_AddInfo_InCallMod)
PIXIT statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in CC-state "active".
Foreseen final state of the MS
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS being in the call active state, the SS initiates in-call modification procedure by sending a MODIFY message with new mode different from actual mode and one of those not supported by the MS. The MS either returns a MODIFY REJECT message with the old bearer capability or a STATUS message with reject cause #97, depending on the PICS statement. The state of the MS is then checked.
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
MODIFY
with new mode different from actual one
2a
MS -> SS
MODIFY REJECT
with the old call mode included OR, p = Yes
2b
MS -> SS
STATUS
cause #97, state U10, p = No
3
SS -> MS
STATUS ENQUIRY
4
MS -> SS
STATUS
cause 30#, state U10
Specific message contents:
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5 In-call functions / MS originated in-call modification
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.1 In-call functions / MS originated in-call modification / a successful case of modifying
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.1.1 Definition
|
This test is to test a successful case of in-call modification, which is triggered by the calling tone identification (CNG) received by the MS. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.1.2 Conformance requirement
|
1) The procedure shall be initiated by the MS in the "active" state of the call. It shall send a MODIFY message including the new mode to be changed to; and enter the "mobile originating modify" state. The new mode given in the MODIFY message shall be one of those already negotiated and agreed during the establishment phase of the call. The MS shall stop sending Bm-channel information according to the old mode and enter the state U26 "Mobile Originating Modify".
2) Upon receipt of the MODIFY COMPLETE message the MS shall start sending channel information according to the new call mode and enter the "active" state.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.1.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.1.3 Test purpose
|
1) To verify that the procedure is initiated by the MS in the "active" state of the call. It sends a MODIFY message including the new mode to be changed to; and enters the "mobile originating modify" state. The new mode given in the MODIFY message is one of those already negotiated and agreed during the establishment phase of the call. The MODIFY originating side stops sending Bm-channel information.
2) To verify that upon receipt of the MODIFY COMPLETE message the MS starts sending channel information according to the new call mode and enters the "active" state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.1.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modificationInitial 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
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with the new mode to the SS and the state of the MS is checked. The channel mode is modified with the CHANNEL MODE MODIFY message including the appropriate channel mode for the new service. The SS then returns a MODIFY COMPLETE message. The state of the MS is then checked.
NOTE: ICM can be initiated by manual intervention at the MS.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a dual mode call
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
4
MS -> SS
CM SERVICE REQUEST
5
SS -> MS
CIPHERING MODE COMMAND
6
MS -> SS
CIPHERING MODE COMPLETE
7
MS -> SS
SETUP
as specified in specific message contents
8
SS -> MS
AUTHENTICATION REQUEST
9
MS -> SS
AUTHENTICATION RESPONSE
10
SS -> MS
CALL PROCEEDING
as specified in specific message contents
11
SS -> MS
ASSIGNMENT COMMAND
channel mode: see subclause 10.4
12
MS -> SS
ASSIGNMENT COMPLETE
13
SS -> MS
ALERTING
14
SS -> MS
CONNECT
15
MS -> SS
CONNECT ACKNOWLEDGE
16
MS -> SS
MODIFY
as specified in specific message contents
17
SS -> MS
STATUS ENQUIRY
18
MS -> SS
STATUS
cause 30#, state U26
19
SS -> MS
CHANNEL MODE MODIFY
as specified in specific message contents
20
MS -> SS
CHANNEL MODE MODIFY ACKNOWLEDGE
21
SS -> MS
MODIFY COMPLETE
contains the new mode as bearer capability
22
SS
allow at least 2 s for the MS to adapt for the new mode
23
SS -> MS
STATUS ENQUIRY
24
MS -> SS
STATUS
cause 30#, state U10
25
SS
verify that the MS starts sending Bm channel information according to the new mode
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.2 In-call functions / MS originated in-call modification / modify rejected
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.2.1 Definition
|
This is to test a special case of a in-call modification procedure, in which the in-call modification is rejected. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.2.2 Conformance requirement
|
1) Upon receipt of the MODIFY REJECT message with the old bearer capability the MS shall: resume sending Bm-channel information according to the present call mode; resume interpreting received Bm-channel information according to the present call mode; and enter the "active" state.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.4.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.2.3 Test purpose
|
To verify that upon receipt of the MODIFY REJECT message with the old bearer capability the MS resumes sending Bm-channel information according to the present call mode; resumes interpreting received Bm-channel information according to the present call mode; and enters the "active" state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.2.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
CC-state "active".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS returns a MODIFY REJECT message. The state of the MS is then checked.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
MMI action to initiate a dual mode call
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
5
MS -> SS
CIPHERING MODE COMPLETE
6
MS -> SS
SETUP
as specified in specific message contents
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESPONSE
9
SS -> MS
CALL PROCEEDING
agreeing bearer capabilities for dual mode call
10
SS -> MS
ASSIGNMENT COMMAND
TCH
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> SS
ALERTING
13
SS -> MS
CONNECT
14
MS -> SS
CONNECT ACKNOWLEDGE
15
MS -> SS
MODIFY
MMI action to change the mode
16
SS -> MS
MODIFY REJECT
with cause #58 bearer capability not available and with old bearer capabilities
17
SS -> MS
STATUS ENQUIRY
18
MS -> SS
STATUS
cause 30#, state U10
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.3 In-call functions / MS originated in-call modification / an abnormal case of acceptance
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.3.1 Definition
|
This is to test a special case of a in-call modification procedure, in which the in-call modification is accepted incorrectly. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.3.2 Conformance requirement
|
1) Upon receipt of the MODIFY COMPLETE message indicating a call mode which does not correspond to the requested one the MS shall discard it and take no action.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.3.3 Test purpose
|
To verify that upon receipt of the MODIFY COMPLETE message indicating a call mode which does not correspond to the requested one the MS discards it and takes no action.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.3.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
CC-state U26 "Mobile Originating Modify".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS returns a MODIFY COMPLETE message specifying a mode that does not correspond to the requested one. It will be verified then that the MS shall not take any action and the state of the MS will be checked.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
MMI action to initiate a dual mode call
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
5
MS -> SS
CIPHERING MODE COMPLETE
6
MS -> SS
SETUP
as specified in specific message contents
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESPONSE
9
SS -> MS
CALL PROCEEDING
agreeing bearer capabilities for dual mode call
10
SS -> MS
ASSIGNMENT COMMAND
TCH
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> SS
ALERTING
13
SS -> MS
CONNECT
14
MS -> SS
CONNECT ACKNOWLEDGE
15
MS -> SS
MODIFY
MMI action to change the mode
16
SS -> MS
MODIFY COMPLETE
with a mode that does not correspond to the requested one
17
SS -> MS
STATUS ENQUIRY
18
MS -> SS
STATUS
cause 30#, state U26
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.4 In-call functions / MS originated in-call modification / an abnormal case of rejection
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.4.1 Definition
|
This is to test a special case of a in-call modification procedure, in which the in-call modification is rejected incorrectly. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.4.2 Conformance requirement
|
1) Upon receipt of the MODIFY REJECT message indicating a call mode which does not correspond to the actual one the MS shall discard it and take no action.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.4.3 Test purpose
|
To verify that upon receipt of the MODIFY REJECT message indicating a call mode which does not correspond to the actual one the MS discards it and takes no action.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.4.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
CC-state U26 "Mobile Originating Modify".
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS returns a MODIFY REJECT message specifying a mode that does not correspond to the actual one. The state of the MS is then checked.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
MMI action to initiate a dual mode call
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
5
MS -> SS
CIPHERING MODE COMPLETE
6
MS -> SS
SETUP
as specified in specific message contents
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESPONSE
9
SS -> MS
CALL PROCEEDING
agreeing bearer capabilities for dual mode call
10
SS -> MS
ASSIGNMENT COMMAND
TCH
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> SS
ALERTING
13
SS -> MS
CONNECT
14
MS -> SS
CONNECT ACKNOWLEDGE
15
MS -> SS
MODIFY
MMI action to change the mode
16
SS -> MS
MODIFY REJECT
with a mode that does not correspond to the actual one
17
SS -> MS
STATUS ENQUIRY
18
MS -> SS
STATUS
cause 30#, state U26
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.5 In-call functions / MS originated in-call modification / time-out of timer T323
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.5.1 Definition
|
This is to test a special case of a in-call modification procedure, in which timer T323 expires in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.5.2 Conformance requirement
|
1) Upon expiration of T323 the MS shall initiate the procedures for call clearing with cause #102 "recovery on timer expiry".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.4.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.5.3 Test purpose
|
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".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.5.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
CC-state U11 "disconnect request".
Maximum duration of test
1 minute.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with new mode to the SS. The SS does not respond until timer T323 expires at the MS. The MS is expected to respond with a DISCONNECT message. The SS checks timer T323 accuracy between emission of MODIFY and reception of DISCONNECT messages, the state of the MS and a cause value from the DISCONNECT message.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
MMI action to initiate a dual mode call
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
5
MS -> SS
CIPHERING MODE COMPLETE
6
MS -> SS
SETUP
as specified in specific message contents
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESPONSE
9
SS -> MS
CALL PROCEEDING
agreeing bearer capabilities for dual mode call
10
SS -> MS
ASSIGNMENT COMMAND
TCH
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> MS
ALERTING
13
SS -> MS
CONNECT
14
MS -> SS
CONNECT ACKNOWLEDGE
15
MS -> SS
MODIFY
MMI action to change the mode
16
SS
the SS waits for the timer T323 expiry
17
MS -> SS
DISCONNECT
cause value #102, the SS checks timer T323 accuracy (± 10 %) between MODIFY and DISCONNECT messages
18
SS -> MS
STATUS ENQUIRY
19
MS -> SS
STATUS
cause 30#, state U11
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.6 In-call functions / MS originated in-call modification / a successful channel change in state mobile originating modify
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.6.1 Definition
|
This is to test a special case of a in-call modification procedure, in which a change of a physical channel occurs in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.6.2 Conformance requirement
|
1) A CC-entity of the MS in CC-state U26, "Mobile Originating Modify", after successful completion of a channel assignment procedure or channel mode modify procedure shall remain in the call state U26.
2) Upon receipt of the MODIFY COMPLETE message the MS shall start sending channel information according to the new call mode and enter the "active" state.
References
1) 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.6.1.
2) 3GPP TS 04.08, subclause 5.3.4.3.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.6.3 Test purpose
|
1) To verify that a CC-entity of the MS in CC-state U26, "Mobile Originating Modify", after successful completion of a channel assignment procedure remains in the call state U26.
2) To verify that upon receipt of the MODIFY COMPLETE message the MS starts sending channel information according to the new call mode and enters the "active" state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.6.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
CC-state U10, active.
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with a new mode to the SS. The SS does not respond immediately, but performs channel assignment procedure including the appropriate channel mode for the new service. The state of the MS is then checked. The SS then returns a MODIFY COMPLETE message. The state of the MS is checked finally.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
MMI action to initiate a dual mode call
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
5
MS -> SS
CIPHERING MODE COMPLETE
6
MS -> SS
SETUP
as specified in specific message contents
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESPONSE
9
SS -> MS
CALL PROCEEDING
agreeing bearer capabilities for dual mode call
10
SS -> MS
ASSIGNMENT COMMAND
TCH
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> MS
ALERTING
13
SS -> MS
CONNECT
14
MS -> SS
CONNECT ACKNOWLEDGE
15
MS -> SS
MODIFY
MMI action to change the mode
16
SS -> MS
ASSIGNMENT COMMAND
channel mode implied by the MODIFY message
17
MS -> SS
ASSIGNMENT COMPLETE
18
SS -> MS
STATUS ENQUIRY
19
MS -> SS
STATUS
cause 30#, state U26
20
SS -> MS
MODIFY COMPLETE
21
SS -> MS
STATUS ENQUIRY
22
MS -> SS
STATUS
cause 30#, state U10
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.7 In-call functions / MS originated in-call modification / an unsuccessful channel change in state mobile originating modify
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.7.1 Definition
|
This is to test a special case of a in-call modification procedure, in which an unsuccessful change of a physical channel occurs in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.7.2 Conformance requirement
|
1) A CC-entity of the MS in CC-state U26, "Mobile Originating Modify", when returning to the old channel after handover failure and having established the link, shall remain in the call state U26.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.3.4.3.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.7.3 Test purpose
|
To verify that a CC-entity of the MS in CC-state U26, "Mobile Originating Modify", when returning to the old channel after handover failure and having established the link, remains in the call state U26.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.7.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
CC-state U26, mobile originating modify.
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with a new mode to the SS. The SS initiates handover procedure. When the MS tries to establish the main signalling link, it is prohibited by the SS. Then the MS shall return back to the old channel and re-establish correctly the link. The state of the MS is then checked.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
MMI action to initiate a dual mode call
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
5
MS -> SS
CIPHERING MODE COMPLETE
6
MS -> SS
SETUP
as specified in specific message contents
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESPONSE
9
SS -> MS
CALL PROCEEDING
agreeing bearer capabilities for dual mode call
10
SS -> MS
ASSIGNMENT COMMAND
TCH
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> SS
ALERTING
13
SS -> MS
CONNECT
14
MS -> SS
CONNECT ACKNOWLEDGE
15
MS -> SS
MODIFY
MMI action to change the mode
16
SS -> MS
HANDOVER COMMAND
17
MS -> SS
HANDOVER ACCESS
the SS does not respond
18
MS -> SS
HANDOVER FAILURE
after the MS has re-established the main signalling link in the old channel
19
SS -> MS
STATUS ENQUIRY
20
MS -> SS
STATUS
cause 30#, state U26
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.8 In-call functions / MS originated in-call modification / unknown message received
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.8.1 Definition
|
This is to test a special case of a in-call modification procedure, in which an unknown message is received in state U26, mobile originating modify. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech/Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech/Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.8.2 Conformance requirement
|
A CC entity of a MS in CC-state U26, "Mobile Originating Modify", having received an unknown message from its peer entity shall return a STATUS message.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 8.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.8.3 Test purpose
|
To verify that a CC entity of a MS in CC-state U26, "Mobile Originating Modify", having received an unknown message from its peer entity returns a STATUS message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.8.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
CC-state U26, mobile originating modify.
Maximum duration of test
10 s.
Test procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with a new mode to the SS. The SS sends a message with message type not defined for the protocol discriminator. The state of the MS is then checked.
Expected sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
MMI action to initiate a dual mode call
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
5
MS -> SS
CIPHERING MODE COMPLETE
6
MS -> SS
SETUP
as specified in specific message contents
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESPONSE
9
SS -> MS
CALL PROCEEDING
agreeing bearer capabilities for dual mode call
10
SS -> MS
ASSIGNMENT COMMAND
TCH
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> SS
ALERTING
13
SS -> MS
CONNECT
14
MS -> SS
CONNECT ACKNOWLEDGE
15
MS -> SS
MODIFY
MMI action to change the mode
16
SS -> MS
unknown message
message type not defined for PD
17
MS -> SS
STATUS
cause 97#, state U26
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.9 In-call functions / MS originated in-call modification / a release complete received
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.9.1 Definition
|
The call control entity of the MS being in the state, U26, the call is cleared by a RELEASE COMPLETE message sent by the SS. This test is applicable for any equipment supporting any dual mode bearer capability service (BS61 - Alternate Speech / Data, BS81 - Speech followed by Data, Teleservice 61 - Alternate Speech / Group 3 fax).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.9.2 Conformance requirement
|
1) A CC entity of the MS in CC-state U26, "mobile originating modify", upon receipt of a RELEASE COMPLETE message with valid cause value, shall enter CC state U0, "Null".
2) On returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers shall be in state U0, "Null".
Reference(s)
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.4.2 and 5.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.9.3 Test purpose
|
1) To verify that a CC entity of the MS in CC-state U26, "mobile originating modify", upon receipt of a RELEASE COMPLETE message with valid cause value, enters CC state U0, "Null".
2) To verify that on returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.9.4 Method of test
|
Specific PICS statements
-
PIXIT statements
- a way to activate a dual mode call
- a way to activate in-call modification
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
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Maximum duration of test
30 s.
Test Procedure
The MS initiates a call for one of the supported dual mode services. The MS being in the call active state, in-call modification procedure is initiated for the selected service from the MS side. The MS shall send a MODIFY message with the new mode to the SS and the state of the MS is checked. The SS sends a RELEASE COMPLETE message to the MS. The SS checks by using the status enquiry procedure that the CC entity has entered the state U0 with all the relevant transaction identifiers.
NOTE: ICM can be initiated by manual intervention at the MS.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a dual mode call
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
4
MS -> SS
CM SERVICE REQUEST
5
SS -> MS
CIPHERING MODE COMMAND
6
MS -> SS
CIPHERING MODE COMPLETE
7
MS -> SS
SETUP
as specified in specific message contents
8
SS -> MS
AUTHENTICATION REQUEST
9
MS -> SS
AUTHENTICATION RESPONSE
10
SS -> MS
CALL PROCEEDING
as specified in specific message contents
11
SS -> MS
ASSIGNMENT COMMAND
channel mode: see subclause 10.4
12
MS -> SS
ASSIGNMENT COMPLETE
13
SS -> MS
ALERTING
14
SS -> MS
CONNECT
15
MS -> SS
CONNECT ACKNOWLEDGE
16
MS -> SS
MODIFY
as specified in specific message contents
17
SS -> MS
STATUS ENQUIRY
18
MS -> SS
STATUS
cause #30, state U26
19
SS -> MS
RELEASE COMPLETE
20
SS -> MS
STATUS ENQUIRY
21
MS -> SS
RELEASE COMPLETE
cause #81 (invalid TI value)
22
SS
repeat steps 20 - 21 to cover all the transaction identifiers from 000 ... 110
23
SS -> MS
CHANNEL RELEASE
the main signalling link shall be released by the MS (L2: DISC/UA)
Specific message contents:
As specified in subclause 26.8.1.4.5.10.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.1.4.5.10 In-call functions/MS originated in-call modification/contents of some of the messages
|
The following messages are used for testing in-call modification procedures, test cases 26.8.1.4.5.*, 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
Repeat indication
Sequential, if BS81 is being tested, otherwise circular for successive selection
Bearer capability 1
Appropriate for the teleservice/Bearer Service selected as an initial call mode
Bearer capability 2
Appropriate for the teleservice/Bearer Service to be selected as a new call mode
Facility
Omitted
Calling party subaddress
Omitted
Called party BCD number
As entered
Called party subaddress
Omitted
LLC repeat indicator
The same repeat indication as the one for BC. Present if and only if LLC I and LLC II are present
Low layer compatibility I
See note
Low layer compatibility II
See note
HLC repeat indicator
The same repeat indication as the one for BC. Present if and only if HLC i and HLC ii are present.
High layer compatibility i
See note
High layer compatibility ii
See note
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. If LLC I is present then LLC II shall be present. If HLC i is present then HLC ii shall be present.
CALL PROCEEDING
If the MS offers a choice in a SETUP message with respect to its bearer capabilities (this choice is restricted to the connection element), the bearer capabilities 1 and 2 and BC repeat indicator must all be present in this message. Otherwise, all three IEs are omitted.
Information element
Value/remark
Repeat Indicator
See above
Repeat indication
As received in the SETUP message
Bearer Capability 1
Same as in subclause 10.4
Bearer Capability 2
Same as in subclause 10.4
Facility
Omitted
Progress indicator
Omitted
MODIFY
Information element
Value/remark
Bearer capability
If the bearer capability IEs were present in the CALL PROCEEDING message, then as it was specified in the bearer capability 2 of the CALL PROCEEDING message. Otherwise as in the bearer capability 2 of the SETUP message.
Reverse Call Setup Direction
Presence and value not checked
Low layer compatibility
See note
High layer compatibility
See note
NOTE: HLC (LLC) shall be included if the HLC (LLC) was included in the SETUP message. The contents of LLC/HLC are not verified.
MODIFY COMPLETE
Information element
Value/remark
Bearer capability
If the bearer capability IEs were present in the CALL PROCEEDING message, then as it was specified in the bearer capability 2 of the CALL PROCEEDING message. Otherwise as in the bearer capability 2 of the SETUP message.
Reverse Call Setup Direction
Same as in MODIFY
Low layer compatibility
See note
High layer compatibility
See note
NOTE: HLC (LLC) shall be included if the HLC (LLC) was included in the SETUP message. The contents of LLC/HLC are not verified.
MODIFY REJECT
Information element
Value/remark
Bearer capability
If the bearer capability IEs were present in the CALL PROCEEDING message, then as it was specified in the bearer capability 1 of the CALL PROCEEDING message. Otherwise as in the bearer capability 1 of the SETUP message.
Cause
#58 "bearer capability not presently available".
Low layer compatibility
See note
High layer compatibility
See note
NOTE: HLC (LLC) shall be included if the HLC (LLC) was included in the SETUP message. The contents of LLC/HLC are not verified.
CHANNEL MODE MODIFY
Information element
Value/remark
Channel description
describes non-hopping Bm+ACCHs or Lm+ACCHs as appropriate for the test
Channel Mode
appropriate for the BC in the MODIFY
CHANNEL MODE MODIFY ACKNOWLEDGE
Information element
Value/remark
Channel description
as sent by the SS in the corresponding CHANNEL MODE MODIFY message
Channel mode
as sent by the SS in the corresponding CHANNEL MODE MODIFY message
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2 Call Re-establishment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.1 Call Re-establishment/call present, re-establishment allowed
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.1.1 Definition
|
This is to test a successful case of a call re-establishment procedure. This test is applicable for any equipment supporting at least one bearer capability. If the MS does not perform call re-establishment procedure correctly, the network will waste resources.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.1.2 Conformance requirement
|
1) If the call is in the "active" state or "mobile originating modify" state, the indication from MM that re-establishment is possible shall cause call control to request re-establishment from the MM-connection, suspend any further message to be sent and await the completion of the re-establishment procedure.
2) When the call control entity is notified that the MM-connection is re-established, it shall then resume the transmission of possibly suspended messages and resume user data exchange when an appropriate channel is available.
References
1) 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.5.1.6 and 5.5.4.2.
2) 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.5.1.6 and 5.5.4.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.1.3 Test purpose
|
The purpose of this test is to verify that the MS can correctly perform a call re-establishment procedure.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.1.4 Method of test
|
Specific PICS statements
-
PIXIT statements
-
Initial conditions
System Simulator:
The SS simulates cells A and B. The LAC of cell A is different from the LAC of cell B. The PLMN identities of cell A and B are equal.
The call re-establishment parameter concerning cell A is set to an arbitrary value.
Cell B is not barred, the RACH control parameters information element sent in SYSTEM INFORMATION TYPE 1 to 4 messages of cell A and B specifies "call reestablishment allowed in the cell", the NCC of cell B is indicated as permitted in the PLMN permitted information element of SYSTEM INFORMATION TYPE 2 and 6 messages of cell A. Cell B is indicated as a neighbour cell of cell A in SYSTEM INFORMATION TYPE 2 and 5 messages of cell A. Cell reselect hysteresis parameter of cell A is set to zero.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN on cell A.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Maximum duration of test
1 minute.
Test procedure
The MS is brought to active state by using procedure 26.9.2, "structured procedures, MS originated call, early assignment". The RF level of cell A is lowered so that cell B is to be selected (when the MS performs re-establishment after radio link failure), while keeping the C1 and C2 of cell A greater than zero. SS waits for at least 5 s. Then the SS stops transmission on the TCH/SACCH. The MS shall re-establish the call on cell B using a CM RE-ESTABLISHMENT message. The SS performs ciphering mode setting and assignment procedures. The MS shall through-connect the appropriate bearer channel. Then, the call is cleared by the SS.
Expected sequence
Step
Direction
Message
Comments
1
Steps 1‑19 of test case 26.9.2 are performed (the appropriate bearer channel is through connected in both directions in TCH)
2
SS
The RF level of cell A is lowered. The SS waits at least 5 s. The SS stops transmission on the TCH/SACCH.
3
MS -> SS
CHANNEL REQUEST
this is sent on cell B. Establ. cause shall be "call re-establishment; TCH/F was in use,..."
4
SS -> MS
IMMEDIATE ASSIGNMENT
5
MS -> SS
CM REESTABLISHMENT REQUEST
note specific message contents
6
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
7
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
8
SS
SS starts ciphering.
9
SS -> MS
ASSIGNMENT COMMAND
10
MS -> SS
ASSIGNMENT COMPLETE
11
MS
The appropriate bearer channel is through connected in both directions.
12
SS -> MS
DISCONNECT
with cause value "Normal"
13
MS -> SS
RELEASE
14
SS -> MS
RELEASE COMPLETE
15
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific message contents:
CM RE-ESTABLISHMENT REQUEST
Information element
Value/remark
Protocol discriminator
Mobility Management
Skip indicator
Encoded as zeroes
Message type
CM RE-ESTABLISHMENT REQUEST
Ciphering key sequence number
The CKSN which the MS was allocated in step 6 of the procedure of subclause 26.9.2.
Spare half octet
zero
Mobile station classmark 2
- ES_IND
as declared in the PICS/PIXIT
- RF Power capability
as declared in the PICS/PIXIT for band of operation
- Ciphering A5/1
as declared in the PICS/PIXIT
Mobile identity
The TMSI that the MS is having initially
Location area identification
Corresponding the LAI of cell A
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.2 Call Re-establishment/call present, re-establishment not allowed
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.2.1 Definition
|
This is to test a special case of a call re-establishment, in which it is not allowed for a MS to attempt re-establishment of a call. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.2.2 Conformance requirement
|
When a lower layer failure occurs while an MM-connection is active, if a cell allowing call re-establishment is not available, the MS shall release the MM-connection and shall not attempt call re-establishment.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.5.1.6 and 5.5.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.2.3 Test purpose
|
The purpose of this test is to verify that the MS does not attempt call re-establishment when it is not allowed to take place because of the unavailability of a cell allowing call re-establishment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.2.4 Method of test
|
Specific PICS statements
-
PIXIT statements
-
Initial conditions
System Simulator:
The SS simulates cell A.
Cell A is not barred, the NCC of cell A is indicated as permitted in the PLMN permitted information element of SYSTEM INFORMATION TYPE 2 and 6 messages. The RE field of the RACH control parameters information element broadcast in messages SYSTEM INFORMATION TYPE 1, 2, 3 and 4 of cell A are set to "call reestablishment not allowed in the cell".
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Maximum duration of test
1 minute.
Test procedure
The MS is brought to active state by using procedure 26.9.2, "structured procedures, MS originated call, early assignment". The SS stops transmission on the TCH/SACCH. The MS shall not require re-establishment of the call.
Expected sequence
Step
Direction
Message
Comments
1
Steps 1‑19 of test case 26.9.2 are performed (the appropriate bearer channel is through connected in both directions in TCH)
2
SS
the SS stops transmission on the TCH/SACCH
3
MS
the MS shall not attempt re-establishment on cell A. This is checked for 30 s after the radio link failure.
Specific message contents:
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.3 Call Re-establishment/call under establishment, transmission stopped
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.3.1 Definition
|
This is to test a special case of a call re-establishment, in which it is not allowed for a MS to attempt re-establishment of a call, since the call has not been established yet. This test is applicable for any equipment supporting at least one mobile originated circuit switched basic service.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.3.2 Conformance requirement
|
When a lower layer failure occurs while an MM-connection is active, if the state of the call control entity is not "active", the MS shall release the MM-connection and shall not attempt call re-establishment.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.5.1.6 and 5.5.4.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.3.3 Test purpose
|
The purpose of this test is to verify that the MS does not attempt call re-establishment when it is not allowed to take place because of the call control state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.2.3.4 Method of test
|
Specific PICS statements
-
PIXIT statements
-
Initial conditions
System Simulator:
The SS simulates cell A.
Cell A is not barred, the RACH control parameters information element sent in SYSTEM INFORMATION TYPE 1 to 4 messages of cell A specifies "call reestablishment allowed in the cell", the NCC of cell A is indicated as permitted in the PLMN permitted information element of SYSTEM INFORMATION TYPE 2 and 6 messages.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Maximum duration of test
1 minute.
Test procedure
The call control entity of the MS is brought to state U4, "call delivered" by using initial part of procedure 26.9.2, "structured procedures, MS originated call, early assignment". The SS stops transmission on the TCH/SACCH. The MS shall not require re-establishment of the call on cell A.
Expected sequence
Step
Direction
Message
Comments
1
the MS is made to initiate a call
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
7
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
8
MS -> SS
CIPHERING MODE COMPLETE
All following messages shall be sent enciphered.
9
SS
SS starts ciphering.
10
MS -> SS
SETUP
11
SS -> MS
CALL PROCEEDING
12
SS -> MS
ASSIGNMENT COMMAND
13
MS -> SS
ASSIGNMENT COMPLETE
14
SS -> MS
ALERTING
15
SS
the SS stops transmission on the TCH/SACCH
16
MS
the MS shall not attempt re-establishment on cell A. This is checked for 30 s after the radio link failure.
Specific message contents:
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.3 User to user signalling
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.3.1 Definition
|
The "user to user" information element is used to convey information between the mobile user and a remote ISDN user. This test is therefore applicable for any equipment supporting at least one mobile terminating circuit switched basic service.
NOTE: There is no test for an MS originating call including a "user-user" information element since it is not a mandatory MS feature.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.3.2 Conformance requirement
|
The inclusion of the "user-user" information element in downlink call control messages shall cause no adverse effects on the operation of the MS.
References
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.2, 9.3.7, 9.3.23.1 and 10.5.4.25.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.3.3 Purpose of the test
|
The purpose of this test is to verify that inclusion of the "user-user" information element in either of the down link messages, SETUP or DISCONNECT causes no adverse effects on the operation of the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.3.4 Method of test
|
Specific PICS statements
-
PIXIT statements
-
Initial conditions.
System Simulator:
The SS simulates 1 cell, with default parameters.
Mobile Station:
The MS is in MM-state "idle updated", with a valid TMSI and CKSN.
Foreseen final state of the MS
The MS is in MM-state "idle updated", with a valid TMSI and CKSN.
Maximum duration of test
2 minutes.
Test procedure
The SS attempts to set up a mobile terminated call, with one of the supported circuit switched basic services which has been arbitrarily chosen, using one of the generic call set up procedures,(either speech or data) as specified in clause 10. The default SETUP message contents are modified to include the user-user Information Element. The MS shall not respond adversely to the inclusion of the user-user information element.
After 30 s the SS sends a DISCONNECT message, again the MS shall not respond adversely to the inclusion of the user-user information element, but shall continue to clear down the call normally.
Expected sequence
Step
Direction
Message
Comments
1
Generic Call Setup procedure defined in clauses 10.1 or 10.3, depending on choice of Bearer Capability. The SETUP message in either case contains the user-user IE, see Specific message contents.
2
The SS waits 30 s.
3
SS -> MS
DISCONNECT
Message contains the user-user IE, see Specific message contents
4
MS -> SS
RELEASE
As defined in subclause 26.8.4
5
SS-> MS
RELEASE COMPLETE
As defined in subclause 26.8.4
6
SS-> MS
CHANNEL RELEASE
As defined in subclause 26.8.4
Specific message contents:
SETUP
As default message contents as defined in the Generic Call setup procedures subclauses 10.1 or 10.3 except:
Information Element
value/remark
Bearer Capability
Bearer capability arbitrarily chosen from those supported by the Mobile Station under test.
user-user
- length
Length of user-user contents (note)
- PD
IA5 characters (note)
- user-user
The following string coded in IA5 characters: "Call Setup" (note)
DISCONNECT
As default message contents as defined in subclause 26.8.4, except:
Information Element
value/remark
user-user
- length
Length of user-user contents (note)
- PD
IA5 characters (note)
- user-user
The following string coded in IA5 characters: "Call Disconnect" (note)
NOTE: The codings above are for example only. For the case of an MS which supports "user-user" signalling it may be necessary to add meaning to the data fields, see PICS/PIXIT statement(s).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.8.4 Default contents of message
|
ALERTING (mobile station to network direction)
No default requirements defined for this message.
ALERTING (network to mobile station direction)
Information element
Value/remark
Facility
Omitted
Progress indicator
Omitted
User-user
Omitted
ASSIGNMENT COMMAND
Information element
Value/remark
Description of the first channel
describes non-hopping Bm+ACCHs or Lm+ACCHs as appropriate for the test
Power Command
As in subclause 6.3
Frequency list
Omitted
Cell channel description
Omitted
Mode of the first channel
appropriate for the bearer capability chosen for the test
Description of the second channel
Omitted
Mode of the second channel
Omitted
Mobile allocation
Omitted
Starting time
Omitted
Cipher mode setting
Omitted
ASSIGNMENT COMPLETE
Information element
Value/remark
RR cause
not checked
AUTHENTICATION REQUEST
Information element
Value/remark
Ciphering key sequence number
Arbitrary excluding 111B
Spare half octet
(spare bits)
Authentication parameter RAND
Arbitrary
AUTHENTICATION RESPONSE
Information element
Value/remark
Authentication parameter SRES
not checked
CALL CONFIRMED
No default requirements defined for this message.
CALL PROCEEDING
Information element
Value/remark
Repeat Indicator
Omitted
Bearer Capability 1
Omitted if the SETUP message did not specify in the bearer capability 1 IE a connection element value "both, transparent preferred" or "both, non-transparent preferred". Otherwise included; in that case the connection element specifies the value that is appropriate for the selected basic service (either value "transparent" or value "non transparent (RLP)"), all other parameters are same as in the bearer capability 1 IE of the received SETUP message.
Bearer Capability 2
Omitted
Facility
Omitted
Progress indicator
Omitted
CHANNEL MODE MODIFY
Information element
Value/remark
Channel description
describes non-hopping Bm+ACCHs or Lm+ACCHs as appropriate for the test
Channel mode
appropriate for the bearer capability chosen for the test
CHANNEL MODE MODIFY ACKNOWLEDGE
Information element
Value/remark
Channel description
as sent by the SS in the corresponding CHANNEL MODE MODIFY message
Channel mode
as sent by the SS in the corresponding CHANNEL MODE MODIFY message
CHANNEL RELEASE
Information element
Value/remark
RR cause
Normal event
CHANNEL REQUEST
Information element
Value/remark
Establishment cause
If in response to paging, then "100"; if a mobile originating call, then "111"
Random reference
Arbitrary value of 5 bits length
CIPHERING MODE COMMAND
Information element
Value/remark
Cipher mode setting
algorithm identifier
indicates a supported algorithm
SC
Start ciphering
Cipher response
CR
IMEI must not be included
CIPHERING MODE COMPLETE
No default requirements defined for this message.
CM SERVICE ACCEPT
No default values defined for this message.
CM SERVICE REJECT
Information element
Value/remark
Reject cause
Service or option not available, unspecified
CM SERVICE REQUEST
No default requirements defined for this message.
CONNECT (network to mobile station direction)
Information element
Value/remark
Facility
Omitted
Progress indicator
Omitted
Connected number
Omitted
Connected subaddress
Omitted
User-user
Omitted
CONNECT (mobile station to network direction)
No default requirements defined for this message.
CONNECT ACKNOWLEDGE
No default requirements defined for this message.
DISCONNECT (network to mobile station direction)
Information element
Value/remark
Cause
Coding standard
GSM
Location
User
Cause value
Normal clearing
Facility
Omitted
Progress indicator
Omitted
User-user
Omitted
DISCONNECT (mobile station to network direction)
Information element
Value/remark
Cause
Shall be present, contents not checked
Facility
Omitted
User-user
Omitted
SS version
Omitted
HANDOVER ACCESS
No default requirements defined for this message.
HANDOVER COMMAND
Information element
Value/remark
Cell Description
a BCCH frequency, which is one of the neighbour cells
Description of the first channel
describes non-hopping Bm+ACCHs or Lm+ACCHs as appropriate for the test
Handover Reference
an arbitrary value
Power Command
as in 6.3
Synchronization indication
Omitted
Frequency short list
Omitted
Frequency List
Omitted
Cell Channel Description
Omitted
Channel Mode
Omitted
Channel Description
Omitted
Channel Mode 2
Omitted
Frequency Channel Sequence
Omitted
Mobile Allocation
Omitted
Starting Time
Omitted
Real time difference
Omitted
Timing advance
Omitted
Cipher Mode setting
Omitted
HANDOVER FAILURE
No default requirements defined for this message.
IMMEDIATE ASSIGNMENT
Information element
Value/remark
Page mode
Normal paging
Channel description
describes a valid SDCCH+SACCH in non-hopping mode
Request reference
Random access information
As received from MS
T1', T2, T3
Corresponding to frame number of the CHANNEL REQUEST
Timing advance
corresponding the timing difference between the MS and the SS
Mobile allocation
Empty (L=0)
Starting time
Omitted
MODIFY
No default values defined for this message.
MODIFY COMPLETE
No default requirements defined for this message.
MODIFY REJECT
No default values defined for this message.
NOTIFY (network to mobile station direction)
Information element
Value/remark
Notification indicator
one of the valid values chosen arbitrarily
PAGING REQUEST TYPE 1
Information element
Value/remark
L2 pseudo length
L2 pseudo length of the message
Page Mode
Normal Paging
Channels needed for Mobiles 1 and 2
channel (first)
any channel
channel (second)
any channel
Mobile identity 1
TMSI of MS under test
Mobile identity 2
Omitted
P1 rest octets
(spare octets)
PAGING RESPONSE
No default requirements defined for this message.
PROGRESS
No default values defined for this message.
RELEASE (network to mobile station direction)
Information element
Value/remark
Cause
Omitted
Second cause
Omitted
Facility
Omitted
User-user
Omitted
RELEASE (mobile station to network direction)
No default requirements defined for this message.
RELEASE COMPLETE (network to mobile station direction)
Information element
Value/remark
Cause
Omitted
Facility
Omitted
User-user
Omitted
RELEASE COMPLETE (mobile station to network direction)
No default requirements defined for this message.
SETUP (mobile station to network direction)
Information element
Value/remark
BC Repeat indicator
Omitted
Bearer capability 1
Appropriate for the basic service selected for the test
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
Appropriate for the basic service selected for the test
Low layer compatibility II
Omitted
HLC repeat indicator
Omitted
High layer compatibility i
Appropriate for the basic service selected for the test
High layer compatibility ii
Omitted
User-user
Omitted
SS version
Omitted
CLIR suppression
Omitted
CC Capabilities
present, shall indicate support for DTMF as per subclause 5.5.7 of 3GPP TS 04.08 / 3GPP TS 24.008
SETUP (network to mobile station direction)
Information element
Value/remark
BC repeat indicator
Omitted
Bearer capability 1
Appropriate for the basic service selected for the test
Bearer capability 2
Omitted
Facility
Omitted
Progress indicator
Omitted
Signal
Any defined value as described for Signal IE in 3GPP TS 04.08 / 3GPP TS 24.008
Calling party BCD number
Omitted
Calling party subaddress
Omitted
Called party BCD number
Omitted
Called party subaddress
Omitted
LLC repeat indicator
Omitted
Low layer compatibility I
Appropriate for the basic service selected for the test
Low layer compatibility II
Omitted
HLC repeat indicator
Omitted
High layer compatibility i
Appropriate for the basic service selected for the test
High layer compatibility ii
Omitted
User-user
Omitted
START DTMF
No default requirements defined for this message.
START DTMF ACKNOWLEDGE
Information element
Value/remark
Keypad facility
corresponding to the DTMF digit indicated in the START DTMF message
START DTMF REJECT
Information element
Value/remark
Cause
value "Resources unavailable, unspecified"
STATUS
Information element
Value/remark
Cause
Value "Response to STATUS ENQUIRY"
Call state
Specified separately in each test case
Auxiliary states
Omitted
STATUS ENQUIRY
No default values defined for this message, except that when this message is used to check that "all the transaction identifiers from 000 to 110" are in the null state, the TI flag shall take the value "1" in mobile originating call tests and shall take the value "0" in mobile terminating call tests.
STOP DTMF
No default requirements defined for this message.
STOP DTMF ACKNOWLEDGE
No default values defined for this message.
Unknown Message
Protocol Discriminator
Call Control; Call Related SS
Transaction Identifier
same as in use in the test
Message Type
0000 0100
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.9 Structured procedures
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.