26.9 Structured procedures
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
26.9.1 Structured procedures / general
The purpose of these tests is to verify that the MS performs certain elementary procedures of the RR, MM, and CC protocol correctly within a structured procedure. The term "structured procedure" is defined in 3GPP TS 04.08 / 3GPP TS 23.108, clause 7, where also examples of structured procedures are given.
The reason for this test purposes is twofold:
– The behaviour of the MS in an elementary procedure may depend on the preamble which precedes the elementary procedure.
– Structured procedures tested in this subclause are used in other parts of this Technical Specification as preambles to establish the initial conditions for other tests; correct behaviour of an implementation under test in a preamble is essential for the validity of a test.
Mobile originating and terminating calls are tested in cases of both early and late assignment of the traffic channel; in one of the cases call release initiated by the network is tested, in another one, call release initiated by the MS.
The feature Directed Retry is tested in both Mobile Originated and Mobile Terminated Call. The configuration of the assigned channels is described in table 26.9-1:
Table 26.9-1
Directed Retry from |
To |
Call direction |
Start Time |
Sync. |
Subclause |
Exec. Counter |
SDCCH/4 |
TCH/F, cycl. FH |
MOC |
None |
No |
26.9.7 |
1 |
SDCCH/8, cycl. FH |
TCH/H, rand. FH |
MOC |
None |
No |
26.9.7 |
2 |
SDCCH/4 |
TCH/F, no FH |
MTC |
None |
No |
26.9.8 |
1 |
SDCCH/8, rand. FH |
TCH/H, cycl. FH |
MTC |
1.1 sec. |
No |
26.9.8 |
2 |
The tests in this subclause only cover the successful outcome of elementary procedures (i.e. they do not deal with abnormal cases).
In this subclause, the emergency call service is tested for mobile stations that do not support the full rate speech version 2 in the following cases:
– emergency call initiated in the idle, updated state with authentication and ciphering, for speech full rate version 1 and if supported, speech half rate version 1;
– emergency call initiated in the idle, no IMSI state (hence without authentication and without ciphering), the network accepting the call, for either speech full rate version 1 or, provided it is supported, speech half rate version 1;
– emergency call initiated in the idle, no IMSI state (hence without authentication and without ciphering), the network rejecting the call, for either speech full rate version 1 or, provided it is supported, speech half rate version 1.
These tests on emergency calls are only applicable to an MS supporting speech.
For an MS supporting speech the test procedures in 26.9.2, 26.9.3, 26.9.4, 26.9.5, 26.9.7 and 26.9.8 are performed for speech (teleservice 11, telephony), once for speech full rate version 1 and, if supported, once for speech half rate version 1.
For an MS not supporting speech but supporting at least one teleservice, for each of the test procedures in subclauses 26.9.2, 26.9.3, 26.9.4, 26.9.5, 26.9.7 and 26.9.8 and each supported rate (full rate/half rate) a teleservice supported by the MS (see PICS/PIXIT statement) is chosen, and the test is performed corresponding to that teleservice (note that this teleservice is never a dual service).
In cases where a mobile originated call for the tested teleservice can be initiated both
– via the MMI; and
– via the R or S interface,
procedures 26.9.2 and 26.9.7 (m = 1) shall be performed when initiating the mobile originated call via the MMI and procedures 26.9.3 and 26.9.7 (m = 2) shall be performed when initiating the mobile originated call via an appropriate interface (R or S).
26.9.2 Structured procedures / MS originated call / early assignment
26.9.2.1 Conformance requirements
1) An MS in MM state "idle, updated" and in RR idle mode, when made to initiate a call, if it provides a human interface, shall display the dialled number.
2) An MS in MM state "idle, updated" and in RR idle mode, when made to initiate a call for a selected teleservice that is supported by the MS, shall start to initiate the immediate assignment procedure by sending a CHANNEL REQUEST message with correct establishment cause.
3) Subsequently after establishment of an MM connection, the MS shall send a SETUP message with correct parameters.
4) The call control entity of the Mobile Station in the "call initiated" state, in the "mobile originating call proceeding" state or in the "call delivered" state, shall, upon receipt of a CONNECT message:
– attach the user connection to the radio path;
– return a CONNECT ACKNOWLEDGE message.
5) Subsequently when the network initiates call clearing by sending a DISCONNECT message, the MS shall proceed to release the call by sending a RELEASE message.
6) On receipt of a CHANNEL RELEASE message, the MS shall disconnect the main signalling link.
References
Conformance requirement 1: 3GPP TS 02.07.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.3.1.1
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.1.
Conformance requirement 4: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.6.
Conformance requirement 5: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.4.4.
Conformance requirement 6: 3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.13.1
26.9.2.2 Test purpose
1) To verify that the MS in MM state "idle, updated" with a TMSI assigned, when made to initiate a call for a selected teleservice that is supported by the MS as declared in a PICS/PIXIT statement, displays the dialled number in the way described in a PICS/PIXIT statement.
2) To verify that the MS in MM state "idle, updated" and in RR idle mode, with a TMSI assigned, when made to initiate a call for a selected teleservice that is supported by the MS as declared in a PICS/PIXIT statement, starts to initiate an immediate assignment procedure by sending the CHANNEL REQUEST message with correct establishment cause.
3) To verify that subsequently after receipt of an IMMEDIATE ASSIGNMENT message allocating an SDCCH, after completion of establishment of the main signalling link, after having sent a CM SERVICE REQUEST message, after having successfully performed the authentication and cipher mode setting procedures, the MS sends a SETUP message with correct parameters.
4) To verify that subsequently, after receipt of a CALL PROCEEDING message and of an ASSIGNMENT COMMAND message allocating an appropriate TCH, after having completed the traffic channel early assignment procedure by replying with the ASSIGNMENT COMPLETE message, after receipt of an ALERTING message and a CONNECT message, the MS returns a CONNECT ACKNOWLEDGE message.
5) To verify that subsequently the MS has attached the user connection to the radio path. (This is checked by verifying that there is a point in time after transmission of the first L2 frame containing the (complete) CONNECT message, where the MS is sending appropriate speech or data frames whenever it does not have to transmit or acknowledge an I frame on layer 2 of the FACCH.)
6) To verify that subsequently upon the network initiating call clearing by sending a DISCONNECT message, the MS proceed to release the call with RELEASE.
7) To verify that subsequently, on receipt of a RELEASE COMPLETE message followed by a CHANNEL RELEASE message, the MS disconnects the main signalling link.
These test purposes are tested for all rates supported by the MS (full rate/half rate).
26.9.2.3 Method of test
(* this affects the ‘correct’ contents of the SETUP message *)
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements:
– Speech supported for Full rate version 1 (GSM FR) (TSPC_AddInfo_Full_rate_version_1)
– Speech supported for Half rate version 1 (GSM HR) (TSPC_AddInfo_Half_rate_version_1)
PIXIT statements:
– Way to indicate mobile originated alerting
– Way to display the called number
Foreseen Final State of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Test procedure
The following test is performed for all rates (full rate/half rate) supported by the MS:
A teleservice is selected that is supported by the MS; if the MS supports speech version 1, the selected teleservice is speech. If necessary, the MS is configured for that teleservice.
The MS is made to initiate a call. The call is established with early assignment. Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
1 minute.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The "called number" is entered. |
|
2 |
MS |
If supported, the MS must display the called number in the way defined in PIXIT. |
|
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is "originating call and the network does not set the NECI bit to 1". |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
SS |
SS starts ciphering. |
|
11 |
MS -> SS |
SETUP |
|
12 |
SS -> MS |
CALL PROCEEDING |
|
13 |
SS -> MS |
ASSIGNMENT COMMAND |
|
14 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
15 |
SS -> MS |
ALERTING |
|
16 |
MS |
Depending on the PIXIT, an alerting indication is given. |
|
17 |
SS -> MS |
CONNECT |
|
18 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
19 |
MS |
The appropriate bearer channel is through connected in both directions. |
|
20 |
SS -> MS |
DISCONNECT |
|
21 |
MS -> SS |
RELEASE |
|
22 |
SS -> MS |
RELEASE COMPLETE |
|
23 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
None.
26.9.3 Structured procedures / MS originated call / late assignment
26.9.3.1 Conformance requirement
1) An MS in MM state "idle, updated" and in RR idle mode with a TMSI assigned, when made to initiate a call for a selected teleservice that is supported by the MS , shall start to initiate an immediate assignment procedure by sending the CHANNEL REQUEST message with correct establishment cause.
2) Upon receipt of the ASSIGNMENT COMMAND message, the Mobile Station initiates a local end release of link layer connections, disconnects the physical channels, commands the switching to the assigned channels and initiates the establishment of lower layer connections (this includes the activation of the channels, their connection and the establishment of the data links). After the main signalling link is successfully established, the MS returns an ASSIGNMENT COMPLETE message, specifying cause "normal event", to the network on the main DCCH.
3, 4) The call control entity of the Mobile Station in the "call initiated" state, in the "mobile originating call proceeding" state or in the "call delivered" state, shall, upon receipt of a CONNECT message:
– attach the user connection to the radio path;
– return a CONNECT ACKNOWLEDGE message.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.3.1.1
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.4.3.1 and 3.4.3.2.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.1.6.
26.9.3.2 Test purpose
1) To verify that the MS in MM state "idle, updated" and in RR idle mode with a TMSI assigned, when made to initiate a call for a selected teleservice that is supported by the MS as declared in a PICS/PIXIT statement, starts to initiate an immediate assignment procedure by sending the CHANNEL REQUEST message.
2) To verify that subsequently after receipt of an IMMEDIATE ASSIGNMENT message allocating an SDCCH, after completion of establishment of the main signalling link, after having sent a CM SERVICE REQUEST message, after having successfully performed authentication and cipher mode setting procedures, after having sent a SETUP message, after having received a CALL PROCEEDING message followed by an ALERTING message and an ASSIGNMENT COMMAND message allocating an appropriate TCH, the MS sends an ASSIGNMENT COMPLETE message.
3) To verify that subsequently, after the suite of actions specified in test purposes 1 and 2, the MS after receiving a CONNECT message returns a CONNECT ACKNOWLEDGE message.
4) To verify that after the suite of actions specified in test purposes 1 and 2, the MS after receiving a CONNECT message attaches the user connection to the radio path. (This is checked by verifying that there is a point in time after transmission of the first L2 frame containing the (complete) CONNECT message, where the MS is sending appropriate speech or data frames whenever it does not have to transmit or acknowledge an I frame on layer 2 of the FACCH.)
These test purposes are tested for all rates supported by the MS (full rate/half rate).
26.9.3.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements:
– Speech supported for Full rate version 1 (GSM FR) (TSPC_AddInfo_Full_rate_version_1)
– Speech supported for Half rate version 1 (GSM HR) (TSPC_AddInfo_Half_rate_version_1)
PIXIT statements:
– Way to indicate mobile originated alerting
-. Way to display the called number
Foreseen Final State of the MS
The MS has a MO call in state U10, "active".
Test procedure
The following test is performed for all rates (full rate/half rate) supported by the MS:
A teleservice is selected that is supported by the MS; if the MS supports speech version 1, the selected teleservice is speech. If necessary, the MS is configured for that teleservice.
The MS is made to initiate a call. The call is established with late assignment.
Maximum Duration of Test
30 s.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The "called number" is entered. |
|
2 |
MS |
||
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is "originating call and the network does not set the NECI bit to 1". |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
SS |
SS starts ciphering. |
|
11 |
MS -> SS |
SETUP |
|
12 |
SS -> MS |
CALL PROCEEDING |
|
13 |
SS -> MS |
ALERTING |
|
14 |
MS |
Depending on the PIXIT, an alerting indication is given. |
|
15 |
SS -> MS |
ASSIGNMENT COMMAND |
|
16 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
17 |
SS -> MS |
CONNECT |
|
18 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
19 |
MS |
The appropriate bearer channel is through connected in both directions. |
Specific Message Contents:
None.
26.9.4 Structured procedures / MS terminated call / early assignment
26.9.4.1 Conformance requirements
1) The MS shall acknowledge the SETUP message with a CALL CONFIRMED message, if compatibility checking was successful, the MS is not busy, and the user does not refuse the call.
2, 3) Upon receipt of the ASSIGNMENT COMMAND message the MS continues a mobile terminating call establishment with early establishment of the traffic channel
a) by replying to the ASSIGNMENT COMMAND with an ASSIGNMENT COMPLETE message, and
b) if the MS supports immediate connect, by continuing the call establishment by through-connecting the traffic channel in both directions, or if the MS does not support immediate connect, by sending an ALERTING message
4) An MS indicates acceptance of a MT call by sending CONNECT.
5)
For speech calls:
The mobile station shall attach the user connection at latest when sending the connect message, except if there is no compatible radio resource available at this time. In this case the attachment shall be delayed until such a resource becomes available.
For data calls:
The mobile station shall attach the user connection when receiving the CONNECT ACKNOWLEDGE message from the network.
6) The MS initiates call clearing of an active call by sending a DISCONNECT message.
7) The MS in this phase of call release, upon receipt of a RELEASE message, shall return a RELEASE COMPLETE message.
8) Subsequently the MS, upon receipt of a CHANNEL RELEASE message, shall disconnect the main signalling link.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.3.1.
Conformance requirements 2, 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.2.3.2,
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.3.1.
Conformance requirement 4: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 5.2.2.5.
Conformance requirement 5: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.2.6 and 5.2.2.9.
Conformance requirements 6, 7, 8: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.4.
26.9.4.2 Test purpose
1) To verify that the MS in MM state "idle, updated" and in RR idle mode with a TMSI assigned, after being paged by the network on the correct paging subchannel, after initiating the immediate assignment procedure by sending the CHANNEL REQUEST message, after receipt of an IMMEDIATE ASSIGNMENT message allocating an SDCCH, after having sent a PAGING RESPONSE message on the allocated SDCCH, after having performed successful authentication and cipher mode setting procedures, after receipt of a SETUP message not containing a signal information element, returns a CALL CONFIRMED message.
2) To verify that subsequently, the SS sending an ASSIGNMENT COMMAND message, the MS successfully continues a mobile terminating call establishment with early assignment of traffic channel:
a) by replying to the ASSIGNMENT COMMAND with an ASSIGNMENT COMPLETE message, and
b) by continuing the call establishment by either:
– sending a CONNECT messages and through connecting the TCH in both directions; or
– sending an ALERTING message.
3) To verify that if after sending a CALL PROCEEDING message, the MS sends an ALERTING message during MTC establishment with early assignment, it generates an alerting indication.
4) To verify that if an ALERTING had been sent, subsequently, when the user accepts the call (possibly internal action as declared in PIXIT statement), the MS returns a CONNECT message.
5) To verify that the MS:
– if the call is a speech call: after sending the CONNECT message has through connected the TCH in both directions (this is checked by verifying that after transmission of the first L2 frame containing the (complete) CONNECT message, the MS is sending appropriate speech or data frames whenever it does not have to transmit or acknowledge an I frame on layer 2 of the FACCH.)
– if the call is a data call: after receipt of a subsequent CONNECT ACKNOWLEDGE message through connects the TCH in both directions (this is checked by verifying that there is a point in time after transmission of the first L2 frame containing the (complete) CONNECT ACKNOWLEDGE message, where the MS is sending appropriate speech or data frames whenever it does not have to transmit or acknowledge an I frame on layer 2 of the FACCH.)
6) To verify that subsequently, the MS can initiate call clearing by sending a DISCONNECT message.
7) To verify that the MS in this phase of call release, upon receipt of a RELEASE message, returns a RELEASE COMPLETE message.
8) To verify that subsequently the MS, upon receipt of a CHANNEL RELEASE message, disconnects the main signalling link.
These test purposes are tested for all rates supported by the MS (full rate/half rate).
26.9.4.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements:
– Speech supported for Full rate version 1 (GSM FR) (TSPC_AddInfo_Full_rate_version_1).
– Speech supported for Half rate version 1 (GSM HR) (TSPC_AddInfo_Half_rate_version_1)
– Immediate connect supported for all circuit switched basic services. (TSPC_AddInfo_ImmConn)
PIXIT statements:
– Way to indicate alerting.
– Way to make the MS accept an incoming call after alerting.
Foreseen Final State of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Test procedure
The following test is performed for all rates (full rate/half rate) supported by the MS:
A teleservice is selected that is supported by the MS; if the MS supports speech version 1, the selected teleservice is speech. If necessary, the MS is configured for that teleservice.
The MS is paged and the resulting call is established. Having reached the active state, the MS is made to clear the call.
Maximum Duration of Test
1 minute.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging subchannel. |
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM. |
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
9 |
SS |
SS starts ciphering. |
|
10 |
SS -> MS |
SETUP |
Message does not contain the signal IE. |
11 |
MS -> SS |
CALL CONFIRMED |
|
If the MS supports immediate connect then branch A applies. If the MS does not support immediate connect then branch B applies |
|||
A12 |
MS -> SS |
CONNECT |
sent on the old channel |
A13 |
SS -> MS |
ASSIGNMENT COMMAND |
|
A14 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
B12 |
SS -> MS |
ASSIGNMENT COMMAND |
|
B13 |
MS -> SS |
ASSIGNMENT COMPLETE |
sent on the new channel |
B14 |
MS -> SS |
ALERTING |
|
B15 |
MS |
An alerting indication as defined in a PIXIT statement is given by the MS |
|
B16 |
MS |
The MS is made to accept the call in the way described in a PIXIT statement |
|
B17 |
MS -> SS |
CONNECT |
|
18 |
MS |
If the call is a speech call, the TCH shall be through connected in both directions. |
|
19 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
20 |
MS |
If the call is a data call, the TCH shall be through connected in both directions. |
|
21 |
MS |
The MS is made to release the call. |
|
22 |
MS -> SS |
DISCONNECT |
|
23 |
SS -> MS |
RELEASE |
|
24 |
MS -> SS |
RELEASE COMPLETE |
|
25 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
None.
26.9.5 Structured procedures / MS terminated call / late assignment
26.9.5.1 Conformance requirement
TP1, TP2: The MS shall acknowledge the SETUP message with a CALL CONFIRMED message, if compatibility checking was successful, the MS is not busy, and the user does not refuse the call. The MS on acceptance of the call sends a CONNECT, otherwise user alerting is initiated.
TP3: The MS indicates acceptance of a call by sending a CONNECT message.
TP4: ASSIGNMENT COMMAND is answered by ASSIGNMENT COMPLETE.
TP5: For speech calls:
The mobile station shall attach the user connection at latest when sending the connect message, except if there is no compatible radio resource available at this time. In this case the attachment shall be delayed until such a resource becomes available.
For data calls:
The mobile station shall attach the user connection when receiving the CONNECT ACKNOWLEDGE message from the network.
Requirement reference:
Conformance requirements 1, 2, 3: 3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.2.3.1, 5.2.2.3.2 and 5.2.2.5.
Conformance requirement 4: 3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.3.1.
Conformance requirement 5: 3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.2.9.
26.9.5.2 Test purpose
1) To verify that the MS in "Idle, Updated" state with a TMSI assigned, after being paged by the network on the correct paging subchannel, after initiating the immediate assignment procedure by sending the CHANNEL REQUEST message, after receipt of an IMMEDIATE ASSIGNMENT message allocating an SDCCH, after having established the main signalling link, after having sent a PAGING RESPONSE message, after having performed successful authentication and cipher mode setting procedures, after receipt of a SETUP message containing a signal information element, returns a CALL CONFIRMED message followed by:
– an ALERTING message;
– or a CONNECT message.
2) To verify that in the situation of test purpose 1, if the MS sends an ALERTING message, the MS generates an alerting indication in the way described in a PIXIT statement.
3) To verify that subsequently the MS, if it had not yet sent a CONNECT message, upon acceptance of the call, sends a CONNECT message.
4) To verify that subsequently after receipt of an ASSIGNMENT COMMAND, the MS sends an ASSIGNMENT COMPLETE message.
5) To verify that subsequently the MS:
– if the call is a speech call: after sending the ASSIGNMENT COMPLETE message has through connected the TCH in both directions (this is checked by verifying that after transmission of the first L2 frame containing the (complete) ASSIGNMENT COMPLETE message, the MS is sending appropriate speech or data frames whenever it does not have to transmit or acknowledge an I frame on layer 2 of the FACCH.)
– if the call is a data call: after receipt of a subsequent CONNECT ACKNOWLEDGE message through connects the TCH in both directions (this is checked by verifying that there is a point in time after transmission of the first L2 frame containing the (complete) CONNECT ACKNOWLEDGE message, where the MS is sending appropriate speech or data frames whenever it does not have to transmit or acknowledge an I frame on layer 2 of the FACCH.)
These test purposes are tested for all rates supported by the MS (full rate/half rate).
26.9.5.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements:
– Speech supported for Full rate version 1 (GSM FR) (TSPC_AddInfo_Full_rate_version_1).
– Speech supported for Half rate version 1 (GSM HR) (TSPC_AddInfo_Half_rate_version_1)
– Immediate connect supported for all circuit switched basic services. (TSPC_AddInfo_ImmConn)
PIXIT statements:
– Way to indicate alerting.
– Way to make the MS accept an incoming call after alerting.
Foreseen Final State of the MS
CC state U10-call active.
Test procedure
The following test is performed for all rates (full rate/half rate) supported by the MS:
– A teleservice is selected that is supported by the MS; if the MS supports speech version 1, the selected teleservice is speech. If necessary, the MS is configured for that teleservice.
– The MS is paged and a MT call is established with late assignment (after CONNECT).
Maximum Duration of Test
40 s.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging subchannel. |
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "answer to paging". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM. |
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
9 |
SS |
SS starts ciphering. |
|
10 |
SS -> MS |
SETUP |
Message contains the signal IE. |
11 |
MS -> SS |
CALL CONFIRMED |
|
A12 |
MS -> SS |
CONNECT |
|
B12 |
MS -> SS |
ALERTING |
|
B13 |
MS |
An alerting indication as defined in an PIXIT statement is given by the MS. |
|
B14 |
MS |
The MS is made to accept the call in the way described in a PIXIT statement. |
|
B15 |
MS -> SS |
CONNECT |
|
16 |
SS -> MS |
ASSIGNMENT COMMAND |
|
17 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
18 |
MS |
If the call is a speech call, the TCH shall be through connected in both directions. |
|
19 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
20 |
MS |
If the call is a data call, the MS shall through connect the TCH in both directions. |
Specific Message Contents:
None.
26.9.6 Structured procedures / emergency call
Emergency call establishment can be initiated by an MS whether location updating has been successful or not and whether a SIM is inserted into the MS or not; but only if the MS is equipped for speech.
If the procedures tested in this subclause are not correctly implemented in the MS, establishment, maintenance and clearing of connections might fail in the essential case of emergency calls.
26.9.6.1 Structured procedures / emergency call / idle updated
26.9.6.1.1 Structured procedures / emergency call / idle updated / preferred channel rate
26.9.6.1.1.1 Conformance requirement
1) For R97/98 MS: The MS in the "idle, updated" state, as after a successful location update, after the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in USA and Canada), or 08 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in Mexico) has been entered by user, shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
For R99 MS: When a SIM/USIM containing stored emergency numbers is present, those numbers are identified as emergency numbers. As an optional requirement, the ME shall also identify 112 and 911 as emergency numbers irrespective of whether these are stored in the SIM/USIM. Any other emergency numbers stored in the ME shall be ignored.
When no emergency numbers are stored within the SIM the following numbers shall be stored in the ME for use as emergency numbers: 112, and 911.
When no emergency numbers are stored within the USIM the following numbers shall be stored in the ME for use as emergency numbers: 112, and 911.
2) After assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel shall be a CM SERVICE REQUEST message specifying the correct CKSN and TMSI , with CM Service Type "emergency call establishment".
3) Authentication and cipher mode setting shall be performed successfully.
4) After cipher mode setting acceptance by the network, the MS shall send an EMERGENCY SETUP message.
5), 6) The emergency call shall be correctly established. The assignment procedure shall be correctly performed.
7) After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call the TCH shall be through connected in both directions if an appropriate TCH is available.
8) The call shall be cleared correctly.
Requirement Reference:
For conformance requirement 1 and 2:
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.3.1.1,
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.1 and 4.5.1.5,
3GPP TS 02.30 clause 4,
3GPP TS 22.101 clauses 8.
For conformance requirement 3:
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.7,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.3.2.
For conformance requirement 4:
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.1.1.
For conformance requirement 5 and 6:
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.1.1,
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3.
For conformance requirement 7:
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.1.6 and 5.1.3.
For conformance requirement 8:
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.4.
26.9.6.1.1.2 Test purpose
1) To verify that an R97/R98 MS supporting speech in the MM state "idle, updated", when made to call the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in USA and Canada), or 08 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in Mexico), sends a CHANNEL REQUEST message with establishment cause "emergency call".
To verify that an R99 MS supporting speech (or a R97/98 MS using the R99 Emergency Numbers) in the MM state "idle, updated", when made to call the number 112 or 911, sends a CHANNEL REQUEST message with establishment cause "emergency call".
2) To verify that after assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel is a CM SERVICE REQUEST message specifying the correct CKSN and TMSI, with CM Service Type "emergency call establishment".
3) To verify that authentication and cipher mode setting are performed successfully.
4) To verify that after cipher mode setting acceptance by the SS, the MS sends an EMERGENCY SETUP message.
5) To verify that subsequently, the SS having sent a CALL PROCEEDING message and then an ALERT message and having initiated the assignment procedure of an appropriate speech traffic channel, which, if the MS supports both TCH/FS and TCH/HS, is at the preferred rate, the MS performs correctly that assignment procedure.
6) To verify subsequent correct performance of a connect procedure.
7) To verify that subsequently the MS has through connected the TCH in both directions.
8) To verify that the call is cleared correctly.
26.9.6.1.1.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements:
– Speech supported for Half rate version 1 (GSM HR) (TSPC_AddInfo_Half_rate_version_1)
– Use of R99 Emergency numbers (TSPC_R99_Emerg)
PIXIT statements:
– .
Foreseen Final State of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Test procedure
The MS is made to initiate an emergency call. The call is established with late assignment. Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
1 minute.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The appropriate emergency call number is entered. |
|
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is emergency call establishment. |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
SS |
SS starts ciphering. |
|
11 |
MS -> SS |
EMERGENCY SETUP |
If half rate speech version 1 is supported, the message must contain one bearer capability IE indicating in the radio channel requirement field "dual rate/half rate preferred" or "dual rate/full rate preferred". If half rate speech version 1 is not supported, the message must either contain no bearer capability IE or contain one bearer capability IE indicating in the radio channel requirement field "full rate channel". If the emergency category IE is included, then SS verifies that the Emergency Service Category IE bit 6 and bit 7 is not set to 1 |
12 |
SS -> MS |
CALL PROCEEDING |
|
13 |
SS -> MS |
ALERTING |
|
14 |
SS -> MS |
ASSIGNMENT COMMAND |
The rate of the channel is that one indicated by the EMERGENCY SETUP message, if that message did not offer a choice, and the rate is the preferred one else. |
15 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
16 |
SS -> MS |
CONNECT |
|
17 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
18 |
MS |
The TCH is through connected in both directions. |
|
19 |
SS -> MS |
DISCONNECT |
|
20 |
MS -> SS |
RELEASE |
|
21 |
SS -> MS |
RELEASE COMPLETE |
|
23 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Note: According to the conformance requirements there is no need to execute the test case by dialling the number 08 for an R99 MS (or a R97/98 MS using the R99 Emergency numbers)
Specific Message Contents:
None.
26.9.6.1.2 Structured procedures / emergency call / idle updated, non-preferred channel rate
This test is identical to the test in subclause 26.9.6.1.1 except that in step 14 the assigned TCH has the non-preferred rate.
26.9.6.1.3 Structured procedures / emergency call / idle updated / EAB active
26.9.6.1.3.1 Conformance requirement
The preliminary access barring check shall indicate network access is barred if all of the following conditions are satisfied:
- the establishment cause for the request received from the MM sublayer is not "emergency call".
- the SYSTEM INFORMATION TYPE 21 message is broadcast in the cell and includes EAB information;
- the mobile station is a member of a subcategory of mobile stations targeted by the EAB information;
- the EAB Authorization Mask sent in the EAB information indicates the mobile station’s access class is not authorized;
- the mobile station is not a member of any of the authorized special access classes (i.e. an Access Class in the range 11-15) permitted by the network;
An MS configured for NAS signalling low priority indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured to NAS signalling low priority" except for the following cases in which the MS shall set the low priority indicator to "MS is not configured for NAS signalling low priority":
– the MS is performing an attach for emergency bearer services;
– the MS has a PDN connection for emergency bearer services established and is performing mobility management procedures, or is establishing a PDN connection for emergency bearer services;
– the MS is accessing the network with access class 11 – 15; or
– the MS is responding to paging.
Reference:
3GPP TS 44.018 subclause 3.3.1.4, 3GPP TS 24.008 subclause 1.8
26.9.6.1.3.2 Test purpose
To verify that the MS, configured for Extended Access class Barring can initiate an emergency call when EAB is being broadcast
To verify that the Low Access Priority indicator is set in the Service Request message
26.9.6.1.3.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
The SYSTEM INFORMATION TYPE 3 message indicates that the SYSTEM INFORMATION TYPE 21 is sent on the BCCH by setting the SYSTEM INFORMATION 21 Indicator in the SI3 Rest Octet IE.
The SYSTEM INFORMATION TYPE 21 is sent on the BCCH. The SI 21 Rest Octets information element is configured with: EAB Authorization Mask set to”xxxxxxxxx1” and EAB Subcategory set to “00”.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.¨
The MS is configured for “Extended Access Barring” and “low access priority”
The MS belong to access class 0
Specific PICS statements:
–
PIXIT statements:
–
Foreseen Final State of the MS
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Test procedure
The SS waits until all system information messages, including SYSTEM INFORMATION TYPE 21, is sent. The SI 21 Rest Octets information element is configured with: EAB Authorization Mask set to”xxxxxxxxx1” and EAB Subcategory set to “00” in SYSTEM INFORMATION TYPE 21.
The MS is made to initiate an emergency call. The call is established with late assignment. Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
1 minute.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
The SS waits until it has sent all system information messages |
||
2 |
MS |
The appropriate emergency call number is entered. |
|
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is emergency call establishment. |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". The Device properties IE indicates “NAS signalling low priority” |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
SS |
SS starts ciphering. |
|
11 |
MS -> SS |
EMERGENCY SETUP |
If the emergency category IE is included, then SS verifies that the Emergency Service Category IE bit 6 and bit 7 is not set to 1 |
12 |
SS -> MS |
CALL PROCEEDING |
|
13 |
SS -> MS |
ALERTING |
|
14 |
SS -> MS |
ASSIGNMENT COMMAND |
|
15 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
16 |
SS -> MS |
CONNECT |
|
17 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
18 |
MS |
The TCH is through connected in both directions. |
|
19 |
SS -> MS |
DISCONNECT |
|
20 |
MS -> SS |
RELEASE |
|
21 |
SS -> MS |
RELEASE COMPLETE |
|
23 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
SYSTEM INFORMATION TYPE 3 broadcast in the cell:
Same as default content except
Information Element |
Value/remark |
SI 3 Rest Octets |
|
SYSTEM INFORMATION 21 Indicator |
H (SYSTEM INFORMATION TYPE 21 message is available) |
SI21_POSITION |
0 (SYSTEM INFORMATION TYPE 21 message is sent on BCCH Norm) |
SYSTEM INFORMATION TYPE 21 broadcast by Cell A initially and in steps 11 and 20:
Same as default content except
Information Element |
Value/remark |
SI 21 Rest Octets |
|
EAB Authorization Mask |
‘xxxxxxxxx1’ (MSs configured for EAB and a member of Access Class 0 are barred) |
EAB Subcategory |
‘00’ (applicable to all mobile stations configured for EAB) |
26.9.6.2 Structured procedures / emergency call / idle, no IMSI
26.9.6.2.1 Structured procedures / emergency call / idle, no IMSI / accept case
26.9.6.2.1.1 Conformance requirement
1) The MS in the "idle, updated" state, as after a successful location update, after the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in USA and Canada), or 08 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in Mexico) has been entered by user, shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2) After assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel shall be a CM SERVICE REQUEST message specifying the correct IMEI and a non-available CKSN, with CM Service Type "emergency call establishment".
3) After cipher mode setting acceptance by the network, the MS shall send an EMERGENCY SETUP message.
4),5) The emergency call shall be correctly established. The assignment procedure shall be correctly performed.
6) After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call the TCH shall be through connected in both directions if an appropriate TCH is available.
7) The call shall be cleared correctly.
Requirement Reference:
For conformance requirement 1 and 2:
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.3.1.1,
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.1 and 4.5.1.5,
3GPP TS 02.30 clause 4.
For conformance requirement 3:
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.1.1.
For conformance requirements 4 and 5:
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.2.1.1,
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3.
For conformance requirement 6:
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.1.6 and 5.1.3.
For conformance requirement 7:
3GPP TS 04.08 / 3GPP TS 24.008, subclause 5.4.
26.9.6.2.1.2 Test purpose
1) To verify that the MS in the "idle, no IMSI" state (no SIM inserted) when made to call the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in USA and Canada), or 08 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in Mexico), sends a CHANNEL REQUEST message with establishment cause "emergency call".
2) To verify that after assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel is a CM SERVICE REQUEST message in which the cipher key sequence number IE indicates "no key is available", the CM service type IE indicates "emergency number establishment", and the mobile identity IE specifies the IMEI of the MS.
3) To verify that after receipt of a CM SERVICE ACCEPT message from the SS, the MS sends an EMERGENCY SETUP message.
4) To verify that subsequently, the SS having sent a CALL PROCEEDING message and then an ALERT message and having initiated the assignment procedure of an appropriate speech traffic channel, which, if the MS supports both TCH/FS and TCH/HS, is at the preferred rate, the MS performs correctly that assignment procedure.
5) To verify subsequent correct performance of a connect procedure.
6) To verify that subsequently the MS has through connected the TCH in both directions.
7) To verify that the call is cleared correctly.
26.9.6.2.1.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, no IMSI", no SIM inserted.
Specific PICS statements:
– .
PIXIT statements:
– .
Foreseen Final State of the MS
The MS is in MM-state "idle, no IMSI", no SIM inserted.
Test procedure
The MS is made to initiate an emergency call. The call is established without authentication, without ciphering, with late assignment. Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
1 minute.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The appropriate emergency call number is entered. |
|
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is "emergency call". |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". The mobile identity IE specifies the IMEI of the MS. The cipher key sequence number IE indicates "no key is available". |
4 |
SS -> MS |
CM SERVICE ACCEPT |
|
11 |
MS -> SS |
EMERGENCY SETUP |
If the emergency category IE is included, then SS verifies that the Emergency Service Category IE bit 6 and bit 7 is not set to 1 |
12 |
SS -> MS |
CALL PROCEEDING |
|
13 |
SS -> MS |
ALERTING |
|
14 |
SS -> MS |
ASSIGNMENT COMMAND |
The rate of the channel is one indicated by the EMERGENCY SETUP message. |
15 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
16 |
SS -> MS |
CONNECT |
|
17 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
18 |
MS |
The TCH is through connected in both directions. |
|
19 |
SS -> MS |
DISCONNECT |
|
20 |
MS -> SS |
RELEASE |
|
21 |
SS -> MS |
RELEASE COMPLETE |
|
23 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
None.
26.9.6.2.2 Structured procedures / emergency call / idle, no IMSI / reject case
26.9.6.2.2.1 Conformance requirement
1) The MS in the "idle, no IMSI" state (no SIM inserted), after the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in USA and Canada), or 08 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in Mexico) has been entered, shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2) After assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel shall be a CM SERVICE REQUEST message specifying the correct IMEI and a non-available CKSN, with CM Service Type "emergency call establishment".
3) In the situation at the end of test purpose 2, when the MS receives a CM SERVICE REJECT message, it shall abandon the emergency call.
Requirement Reference:
For conformance requirement 1 and 2:
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.3.1.1,
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.1 and 4.5.1.5,
3GPP TS 02.30 clause 4.
For conformance requirement 3:
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.7,
3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.5.1.1.
26.9.6.2.2.2 Test purpose
1) To verify that the MS in the "idle, no IMSI" state (no SIM inserted) when made to call the number 112, (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in USA and Canada), or 08 (for GSM 710, GSM 750, T-GSM 810, GSM 850 and PCS 1 900 MS in Mexico) sends a CHANNEL REQUEST message with establishment cause "emergency call".
2) To verify that after assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel is a CM SERVICE REQUEST message in which the cipher key sequence number IE indicates "no key is available", the CM service type IE indicates "emergency call establishment", and the mobile identity IE specifies the IMEI of the MS.
3) To verify that after receipt of a CM SERVICE REJECT message from the SS, the MS abandons the emergency call establishment.
26.9.6.2.2.3 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, no IMSI", no SIM inserted.
Specific PICS statements:
– .
PIXIT statements:
– .
Foreseen Final State of the MS
The MS is in MM-state "idle, no IMSI", no SIM inserted.
Test procedure
The MS is made to initiate an emergency call. The call is established without authentication, without ciphering, with early assignment. The SS responds to the CM SERVICE REQUEST from the MS with a CM SERVICE REJECT message specifying in the reject cause IE the reject cause value "IMEI not accepted". The SS then verifies for during 5 s that the MS does not send a layer 3 message. Then the call is cleared by the SS. The SS verifies during 20 s after disconnection of the main signalling link that the MS does not initiate an RR connection establishment.
Maximum Duration of Test
1 minute.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The appropriate call number is entered. |
|
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is "emergency call". |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". The mobile identity IE specifies the IMEI of the MS. The cipher key sequence number IE indicates "no key is available". |
4 |
SS -> MS |
CM SERVICE REJECT |
the reject cause IE specifies reject cause value #5, "IMEI not accepted". |
5 |
SS |
During 5 s, the SS verifies that the MS does not send L3 messages. |
|
6 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
7 |
SS |
During 20 s, the SS verifies that the MS does not initiate an RR connection establishment. |
Specific Message Contents:
–
26.9.6a Structured Calls /eCall
eCall establishment can be initiated by a MS whether location updating has been successful or not, but only if the MS supports eCall capability and has a valid USIM provisioned for the eCall service.
If the procedures tested in this clause are not correctly implemented in the MS, establishment, maintenance or clearing of connections might fail in the essential case of eCall.
Note: eCall functionality has to be tested with Test USIM as defined in Annex 4a.
26.9.6a.1 eCall with USIM
26.9.6a.1.1 Void
26.9.6a.1.2 Test eCall using eCall capable MS with ’eCall only’ subscription on USIM
26.9.6a.1.2.1 Conformance Requirement
The eCall inactivity procedure is applicable only to an eCall only mobile station (as determined by information configured in USIM).
[..]
While in eCALL INACTIVE state, the mobile station maintains awareness of a potential serving cell in a potential serving network but initiates no MM signalling with the network and ignores any paging requests.
The mobile station shall leave eCALL INACTIVE state only when one of the following events occur:
[..]
– if there is a CM request for a call to an HPLMN designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services: the mobile station attempts normal location updating. Once this is complete, further MM and CM procedures are used to establish the non-emergency call.
Reference(s)
3GPP TS 24.008 subclauses 4.4.7
26.9.6a.1.2.2 Test purpose
1. Verify that the eCall only capable MS is capable of making a test eCall.
26.9.6a.1.2.3 Method of test
Initial conditions
The eCall only capable MS is equipped with eCall enabled USIM.
System Simulator
1 cell, default parameters, Ciphering Off
T3212 set to 12 Minutes. ATT flag set to 1 (IMSI ATTACH/DETACH shall be performed in the cell)
Mobile Station
The MS is equipped with a Test USIM containing default values except for those listed below.
USIM field |
Contents |
EFUST |
Service n°2 Fixed Dialling Numbers (FDN) and Service n°89 eCall Data available |
EFFDN |
Display two FDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
EFEST |
Enabled Services Table |
Specific PICS statement(s)
–
Specific PIXIT Statement(s)
–
Test procedure
a. MS is powered on. SS monitors to verify that MS does not attempt to register for a period of 120 seconds.
b. MS is made to initiate a Test eCall in accordance with manufacturer’s instructions . SS checks that MS performs registration before starting Test eCall.
c. Having reached the active state, the call is cleared by the SS. SS monitors to verify that MS remains registered and send a periodic LAU message as T3212 timer is set to 12 minutes.
Maximum Duration of Test
20 minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is switched on. |
|
2 |
SS |
The SS verifies for 120 sec that the MS does not send RACH or any other message. |
|
3 |
MS |
MS is made to initiate a Test eCall (The first number stored in the EFFDN field) |
|
4 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to Location updating. |
5 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
LOCATION UPDATING REQUEST |
"Location Updating Type" = Normal location updating/IMSI Attach. |
7 |
SS->MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
10 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
11 |
SS -> MS |
CHANNEL RELEASE |
|
12 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to “originating call” |
13 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
14 |
MS -> SS |
CM SERVICE REQUEST |
|
15 |
SS -> MS |
CM SERVICE ACCEPT |
|
16 |
MS -> SS |
SETUP |
Verify called number is the test eCall number. (The first number stored in the EFFDN field) |
17 |
SS -> MS |
CALL PROCEEDING |
|
18 |
SS -> MS |
ALERTING |
|
19 |
MS |
Depending on the PIXIT, an alerting indication is given. |
|
20 |
SS -> MS |
ASSIGNMENT COMMAND |
|
21 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
22 |
SS -> MS |
CONNECT |
|
23 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
24 |
MS |
Traffic channel is kept active for at least 5 seconds. |
|
25 |
SS -> MS |
DISCONNECT |
|
26 |
MS -> SS |
RELEASE |
|
27 |
SS -> MS |
RELEASE COMPLETE |
|
28 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
29 |
SS |
SS verifies that MS sends periodic Location Update Request after 12 minutes (5% margin is allowed). |
Specific Message Contents
None
26.9.6a.1.3 Manually initiated eCall using eCall capable MS with ’eCall only’ subscription on USIM
26.9.6a.1.3.1 Conformance Requirement
1. When in state MM IDLE and service state eCALL INACTIVE, the mobile station shall:
– not perform periodic updating;
– not perform IMSI detach;
– reject any requests from CM entities for MM connections except for emergency calls and calls to a non-emergency MSISDN for test and terminal reconfiguration services;
– not perform normal location updating; and
– not respond to paging.
2. An eCall only mobile station (as determined by information configured in USIM), shall start timer T3242 if the return to MM IDLE state is subsequent to an emergency services call and shall start timer T3243 if the return to MM IDLE state is subsequent to a call to a non-emergency MSISDN for test and terminal reconfiguration services, as described in subclause 4.4.7
Reference(s)
3GPP TS 24.008 subclauses 4.2.2.9, 4.2.3
26.9.6a.1.3.2 Test purpose
Verify that the eCall capable mobile equipped with USIM subscription restricted to eCall only
1. Able to make eCall
2. Registers to the NW as an eCall is initiated.
26.9.6a.1.3.3 Method of test
Initial conditions
The eCall capable MS is equipped with USIM subscription restricted to eCall only.
System Simulator
1 cell, default parameters, Ciphering Off
ATT flag set to 1 (IMSI ATTACH/DETACH shall be performed in the cell)
Mobile Station
The MS is equipped with a Test USIM containing default values except for those listed below.
USIM field |
Contents |
EFUST |
Service n°2 Fixed Dialling Numbers (FDNDN) and Service n°89 eCall Data available |
EFFDN |
Display two FDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
EFEST |
Enabled Services Table |
Specific PICS statement(s)
–
Specific PIXIT statement(s)
–
Test procedure
a) MS is powered on. SS monitors to verify that MS does not attempt to register for a period of 120 seconds.
b) MS is made to initiate an eCall in accordance with manufacturer’s instructions. SS checks that MS performs registration before starting an eCall.
c) Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
5minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is switched on. |
|
2 |
SS |
The SS verifies for 120 sec that the MS does not send RACH or any other message. |
|
3 |
MS |
MS is made to initiate a manual eCall |
|
4 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to Location updating. |
5 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS ->SS |
LOCATION UPDATING REQUEST |
"Location Updating Type" = Normal location updating/IMSI Attach. |
7 |
SS->MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
9 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
10 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
11 |
SS -> MS |
CHANNEL RELEASE |
|
12 |
MS -> SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with “Establishment cause is emergency call establishment” |
13 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
14 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
15 |
SS -> MS |
CM SERVICE ACCEPT |
|
16 |
MS -> SS |
EMERGENCY SETUP |
SS verifies that optional IE “Service category” should be present and bit 6 should be set to 1 and bit 7 should be set to 0. |
17 |
SS -> MS |
CALL PROCEEDING |
|
18 |
SS -> MS |
ALERTING |
|
19 |
SS -> MS |
ASSIGNMENT COMMAND |
|
20 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
21 |
SS -> MS |
CONNECT |
|
22 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
23 |
MS |
Traffic channel is kept active for at least 5 seconds. |
|
24 |
SS -> MS |
DISCONNECT |
|
25 |
MS -> SS |
RELEASE |
|
26 |
SS -> MS |
RELEASE COMPLETE |
|
27 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
None
26.9.6a.1.4 Manually initiated eCall using eCall capable MS with eCall capable USIM
26.9.6a.1.4.1 Conformance Requirement
1. eCall and Normal call support
Requirement: Service n° 89 and Service n° 4 are "available".
Request: The ME performs the reading procedure with EFSDN.
If eCall and normal calls are supported, then the last two entries of EFSDN shall contain the eCall test number and the eCall reconfiguration number respectively. A terminal in eCall and normal mode performs the SDN related procedures.
2. TBD
Table 10.5.135d/3GPP TS 24.008: Service Category information element
Emergency Service Category Value (octet 3)
The meaning of the Emergency Category Value is derived from the following settings (see 3GPP TS 22.101 [8] clause 10):
Bit 1 Police
Bit 2 Ambulance
Bit 3 Fire Brigade
Bit 4 Marine Guard
Bit 5 Mountain Rescue
Bit 6 manually initiated eCall
Bit 7 automatically initiated eCall
Bit 8 is spare and set to "0"
Mobile station may set one or more bits to "1"
If more than one bit is set to "1", routing to a combined Emergency centre (e.g. ambulance and fire brigade in Japan) is required. If the MSC can not match the received service category to any of the emergency centres, it shall route the call to an operator defined default emergency centre.
If no bit is set to "1", the MSC shall route the Emergency call to an operator defined default emergency centre.
A mobile station initiating an eCall shall set either bit 6 or bit 7 to “1”. The network may use the information indicated in bit 6 and bit 7 to route the manually or automatically initiated eCall to an operator defined emergency call centre.
Reference(s)
TS31.102 clause 5.3.40.2, TS 24.008 subclauses10.5.4.33
26.9.6a.1.4.2 Test purpose
Verify that the eCall capable mobile equipped with eCall and non eCall subscription on USIM
1. Performs LAU when Switched on
2. Able to make eCall.
26.9.6a.1.4.3 Method of test
Initial conditions
The eCall capable MS is equipped with eCall and non eCall subscription on USIM.
System Simulator
1 cell, default parameters, ciphering off
ATT flag set to 1 (IMSI ATTACH/DETACH shall be performed in the cell)
Mobile Station
The MS is equipped with a Test USIM containing default values except for those listed below.
USIM field |
Contents |
EFUST |
Service n°4 Service Dialling Numbers (SDN) and Service n°89 eCall Data available |
EFSDN |
Display two SDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
EFEST |
Enabled Services Table |
Specific PICS statement(s)
–
Specific PIXIT statement(s)
–
Test procedure
a) MS is powered on.
b) SS checks that MS successfully performs LAU.
c) MS is made to initiate an eCall in accordance with manufacturer’s instructions.
d) Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
5 minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is switched on. |
|
2 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to Location updating within 60 sec. |
3 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS ->SS |
LOCATION UPDATING REQUEST |
"Location Updating Type" = Normal Location Updating/IMSI attach. |
5 |
SS->MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
8 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
9 |
SS -> MS |
CHANNEL RELEASE |
|
10 |
MS |
MS is made to initiate a manual eCall |
|
11 |
MS -> SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with “Establishment cause is emergency call establishment” |
12 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
13 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
14 |
SS -> MS |
CM SERVICE ACCEPT |
|
15 |
MS -> SS |
EMERGENCY SETUP |
SS verifies that optional IE “Service category” should be present and bit 6 should be set to 1 and bit 7 should be set to 0. |
16 |
SS -> MS |
CALL PROCEEDING |
|
17 |
SS -> MS |
ALERTING |
|
18 |
SS -> MS |
ASSIGNMENT COMMAND |
|
19 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
20 |
SS -> MS |
CONNECT |
|
21 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
22 |
MS |
Traffic channel is kept active for at least 5 seconds. |
|
23 |
SS -> MS |
DISCONNECT |
|
24 |
MS -> SS |
RELEASE |
|
25 |
SS -> MS |
RELEASE COMPLETE |
|
26 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
None
26.9.6a.1.5 eCall Inactivity State after T3242 expires
26.9.6a.1.5.1 Conformance Requirement
1. When in state MM IDLE and service state eCALL INACTIVE, the mobile station shall:
– not perform periodic updating;
– not perform IMSI detach;
– reject any requests from CM entities for MM connections except for emergency calls and calls to a non-emergency MSISDN for test and terminal reconfiguration services;
– not perform normal location updating; and
– not respond to paging.
2. An eCall only mobile station (as determined by information configured in USIM), shall start timer T3242 if the return to MM IDLE state is subsequent to an emergency services call and shall start timer T3243 if the return to MM IDLE state is subsequent to a call to a non-emergency MSISDN for test and terminal reconfiguration services, as described in subclause 4.4.7.
3. The mobile station shall leave eCALL INACTIVE state only when one of the following events occur:
– if the SIM or USIM is removed, the mobile station enters the NO IMSI state;
– if coverage is lost, the mobile station enters PLMN SEARCH state;
– if the mobile station is deactivated (e.g. powered off) by the user: the mobile station enters the NULL state;
– if there is a CM request for an emergency services call: the MS uses the MM and CM procedures to establish the emergency call; or
– if there is a CM request for a call to an HPLMN designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services: the mobile station attempts normal location updating. Once this is complete, further MM and CM procedures are used to establish the non-emergency call.
Reference(s)
3GPP TS 24.008 subclauses 4.2.2.9, 4.2.3, 4.4.7
26.9.6a.1.5.2 Test purpose
Verify that the eCall capable mobile equipped with USIM subscription restricted to eCall only
1. Able to make eCall
2. Registers to the NW as an eCall is initiated.
3. Remains registered on the network for a duration of T3242 following completion of an eCall.
4. Detaches from network upon expiry of T3242.
5. Comes out of the eCall Inactive state when eCall is initiated (MS should register back to NW and then initiate eCall)
26.9.6a.1.5.3 Method of test
Initial conditions
The eCall capable MS is equipped with USIM subscription restricted to eCall only.
System Simulator
1 cell, default parameters, ciphering off
T3212 set to 252 Minutes. ATT flag set to 1 (IMSI ATTACH/DETACH shall be performed in the cell)
Mobile Station
The MS is equipped with a Test USIM containing default values except for those listed below.
USIM field |
Contents |
EFUST |
Service n°2 Fixed Dialling Numbers (FDN) and Service n°89 eCall Data available |
EFFDN |
Display two FDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
EFEST |
Enabled Services Table |
Specific PICS statement(s)
–
Specific PIXIT statement(s)
–
Test procedure
a) MS is powered on. SS monitors to verify that MS does not attempt to register for a period of 120 seconds.
b) MS is made to initiate an eCall in accordance with manufacturer’s instructions. SS checks that MS performs registration before starting an eCall.
c) Having reached the active state, the call is cleared by the SS. SS monitors to verify that MS remains registered for the duration of T3242 and send LAU messages every 252 mins (as T3212 timer is set to 252 minutes).
d) Upon expiry of timer T3242 the MS shall perform IMSI detach.
e) MS is made to initiate an eCall. SS checks that MS performs registration before starting an eCall.
f) Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
12 hours 20 minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is switched on. |
|
2 |
SS |
The SS verifies for 120 sec that the MS does not send RACH or any other message. |
|
3 |
MS |
MS is made to initiate a manual eCall |
|
4 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to Location updating. |
5 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS ->SS |
LOCATION UPDATING REQUEST |
"Location Updating Type" = Normal location updating/IMSI Attach. |
7 |
SS->MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
10 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
11 |
SS -> MS |
CHANNEL RELEASE |
|
12 |
MS -> SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with “Establishment cause is emergency call establishment” |
13 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
14 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
15 |
SS -> MS |
CM SERVICE REQUEST |
|
16 |
MS -> SS |
EMERGENCY SETUP |
SS verifies that optional IE “Service category” should be present and bit 6 should be set to 1 and bit 7 should be set to 0. |
17 |
SS -> MS |
CALL PROCEEDING |
|
18 |
SS -> MS |
ALERTING |
|
19 |
SS -> MS |
ASSIGNMENT COMMAND |
|
20 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
21 |
SS -> MS |
CONNECT |
|
22 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
23 |
MS |
Traffic channel is kept active for at least 5 seconds. |
|
24 |
SS -> MS |
DISCONNECT |
|
25 |
MS -> SS |
RELEASE |
|
26 |
SS -> MS |
RELEASE COMPLETE |
|
27 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
28 |
SS |
For next 12 hours 10 mins SS verifies that 1. MS sends Location Update Request periodically every 252 minutes( 5% margin is allowed). 2. MS performs IMSI detach after timer T3242 expires (12 hours) 1% margin is allowed. |
|
29 |
MS |
MS is made to initiate a manual eCall |
|
30 |
SS |
MS should perform LAU. |
|
31 |
MS -> SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with “Establishment cause is emergency call establishment” |
32 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
33 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
34 |
SS -> MS |
CM SERVICE ACCEPT |
|
35 |
MS -> SS |
EMERGENCY SETUP |
SS verifies that optional IE “Service category” should be present and bit 6 should be set to 1 and bit 7 should be set to 0. |
36 |
SS -> MS |
CALL PROCEEDING |
|
37 |
SS -> MS |
ALERTING |
|
38 |
SS -> MS |
ASSIGNMENT COMMAND |
|
39 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
40 |
SS -> MS |
CONNECT |
|
41 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
42 |
MS |
The TCH is connected in both directions. |
|
43 |
SS |
Traffic channel is kept active for at least 5 seconds. |
|
44 |
SS -> MS |
DISCONNECT |
|
45 |
MS -> SS |
RELEASE |
|
46 |
SS -> MS |
RELEASE COMPLETE |
|
47 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
None
26.9.6a.1.6 Automatically initiated eCall
26.9.6a.1.6.1 Conformance Requirement
[..]
Table 10.5.135d/3GPP TS 24.008: Service Category information element
Emergency Service Category Value (octet 3)
The meaning of the Emergency Category Value is derived from the following settings (see 3GPP TS 22.101 [8] clause 10):
Bit 1 Police
Bit 2 Ambulance
Bit 3 Fire Brigade
Bit 4 Marine Guard
Bit 5 Mountain Rescue
Bit 6 manually initiated eCall
Bit 7 automatically initiated eCall
Bit 8 is spare and set to "0"
Mobile station may set one or more bits to "1"
If more than one bit is set to "1", routing to a combined Emergency centre (e.g. ambulance and fire brigade in Japan) is required. If the MSC can not match the received service category to any of the emergency centres, it shall route the call to an operator defined default emergency centre.
If no bit is set to "1", the MSC shall route the Emergency call to an operator defined default emergency centre.
A mobile station initiating an eCall shall set either bit 6 or bit 7 to “1”. The network may use the information indicated in bit 6 and bit 7 to route the manually or automatically initiated eCall to an operator defined emergency call centre.
Reference(s)
3GPP TS 24.008 subclauses10.5.4.33
26.9.6a.1.6.2 Test purpose
Verify that the eCall capable mobile equipped with eCall and non eCall subscription on USIM
1. Performs LAU when Switched on
2. Able to make an Automatic eCall.
3. MS provides appropriate Service Category information to the network when Automatic eCall is initiated.( Bit 7 should be set to 1 and Bit 6 should be set to 0).
26.9.6a.1.6.3 Method of test
Initial conditions
The eCall capable MS is equipped with eCall and non eCall subscription on USIM.
System Simulator
1 cell, default parameters, ciphering off
ATT flag set to 1 (IMSI ATTACH/DETACH shall be performed in the cell)
Mobile Station
The MS is equipped with a Test USIM containing default values except for those listed below
USIM field |
Contents |
EFUST |
Service n°4 Service Dialling Numbers (SDN) and Service n°89 eCall Data available |
EFSDN |
Display two SDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
EFEST |
Enabled Services Table |
Specific PICS statement(s)
–
Specific PIXIT statement(s)
–
Test procedure
a) MS is powered on.
b) SS checks that MS successfully performs LAU.
c) MS is made to initiate an automatic eCall in accordance with manufacturer’s instructions. SS verifies that MS provides appropriate Service Category information to the network. ( Bit 7 should be set to 1 and Bit 6 should be set to 0).
d) Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
5 minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is switched on. |
|
2 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to Location updating within 60 sec. |
3 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS ->SS |
LOCATION UPDATING REQUEST |
"Location Updating Type" = Normal Location Updating/IMSI attach. |
5 |
SS->MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
7 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
8 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
9 |
SS -> MS |
CHANNEL RELEASE |
|
10 |
MS |
MS is made to initiate an Automatic eCall |
|
11 |
MS -> SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with “Establishment cause is emergency call establishment” |
12 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
13 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
14 |
SS -> MS |
CM SERVICE ACCEPT |
|
15 |
MS -> SS |
EMERGENCY SETUP |
SS verifies that optional IE “Service category” should be present and bit 6 should be set to 0 and bit 7 should be set to 1. |
16 |
SS -> MS |
CALL PROCEEDING |
|
17 |
SS -> MS |
ALERTING |
|
18 |
SS -> MS |
ASSIGNMENT COMMAND |
|
19 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
20 |
SS -> MS |
CONNECT |
|
21 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
22 |
MS |
Traffic channel is kept active for at least 5 seconds. |
|
23 |
SS -> MS |
DISCONNECT |
|
24 |
MS -> SS |
RELEASE |
|
25 |
SS -> MS |
RELEASE COMPLETE |
|
26 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
None
26.9.6a.1.7 Reconfiguration eCall using eCall capable MS with ‘eCall only’ subscription on USIM
26.9.6a.1.7.1 Conformance Requirement
The eCall inactivity procedure is applicable only to an eCall only mobile station (as determined by information configured in USIM).
[..]
While in eCALL INACTIVE state, the mobile station maintains awareness of a potential serving cell in a potential serving network but initiates no MM signalling with the network and ignores any paging requests.
The mobile station shall leave eCALL INACTIVE state only when one of the following events occur:
[..]
– if there is a CM request for a call to an HPLMN designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services: the mobile station attempts normal location updating. Once this is complete, further MM and CM procedures are used to establish the non-emergency call.
Reference(s)
3GPP TS 24.008 subclauses 4.4.7
26.9.6a.1.7.2 Test purpose
1. Verify that the eCall capable MS is capable of making a reconfiguration eCall.
26.9.6a.1.7.3 Method of test
Initial conditions
The eCall capable MS is equipped with eCall only enabled USIM.
System Simulator
1 cell, default parameters, Ciphering Off
Mobile Station
The MS is equipped with a Test USIM containing default values except for those listed below.
USIM field |
Contents |
EFUST |
Service n°2 Fixed Dialling Numbers (FDN) and Service n°89 eCall Data available |
EFFDN |
Display two FDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
EFEST |
Enabled Services Table |
Specific PICS statement(s)
–
Specific PIXIT Statement(s)
–
Test procedure
a. MS is powered on. SS monitors to verify that MS does not attempt to register for a period of 120 seconds.
b. MS is made to initiate a reconfiguration eCall in accordance with manufacturer’s instructions . SS checks that MS performs registration before starting reconfiguration eCall.
c. Having reached the active state, the call is cleared by the SS.
Maximum Duration of Test
5 minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is switched on. |
|
2 |
SS |
The SS verifies for 120 sec that the MS does not send RACH or any other message. |
|
3 |
MS |
MS is made to initiate a reconfiguration eCall (The second number stored in the EFFDN field) |
|
4 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to Location updating. |
5 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
LOCATION UPDATING REQUEST |
"Location Updating Type" = Normal location updating/IMSI Attach. |
7 |
SS->MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
10 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
11 |
SS -> MS |
CHANNEL RELEASE |
|
12 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to “originating call” |
13 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
14 |
MS -> SS |
CM SERVICE REQUEST |
|
15 |
SS->MS |
CM SERVICE ACCEPT |
|
16 |
MS -> SS |
SETUP |
Verify called number is the reconfiguration eCall number. (The second number stored in the EFFDN field) |
17 |
SS -> MS |
CALL PROCEEDING |
|
18 |
SS -> MS |
ALERTING |
|
19 |
MS |
Depending on the PIXIT, an alerting indication is given. |
|
20 |
SS -> MS |
ASSIGNMENT COMMAND |
|
21 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
22 |
SS -> MS |
CONNECT |
|
23 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
24 |
MS |
Traffic channel is kept active for at least 5 seconds. |
|
25 |
SS -> MS |
DISCONNECT |
|
26 |
MS -> SS |
RELEASE |
|
27 |
SS -> MS |
RELEASE COMPLETE |
|
28 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
None
26.9.6a.1.8 eCall Inactivity State after T3243 expires
26.9.6a.1.8.1 Conformance Requirement
1. When in state MM IDLE and service state eCALL INACTIVE, the mobile station shall:
– not perform periodic updating;
– not perform IMSI detach;
– reject any requests from CM entities for MM connections except for emergency calls and calls to a non-emergency MSISDN for test and terminal reconfiguration services;
– not perform normal location updating; and
– not respond to paging.
2. An eCall only mobile station (as determined by information configured in USIM), shall start timer T3242 if the return to MM IDLE state is subsequent to an emergency services call and shall start timer T3243 if the return to MM IDLE state is subsequent to a call to a non-emergency MSISDN for test and terminal reconfiguration services, as described in subclause 4.4.7.
3. The mobile station shall leave eCALL INACTIVE state only when one of the following events occur:
– if the SIM or USIM is removed, the mobile station enters the NO IMSI state;
– if coverage is lost, the mobile station enters PLMN SEARCH state;
– if the mobile station is deactivated (e.g. powered off) by the user: the mobile station enters the NULL state;
– if there is a CM request for an emergency services call: the MS uses the MM and CM procedures to establish the emergency call; or
– if there is a CM request for a call to an HPLMN designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services: the mobile station attempts normal location updating. Once this is complete, further MM and CM procedures are used to establish the non-emergency call.
Reference(s)
3GPP TS 24.008 subclauses 4.2.2.9, 4.2.3, 4.4.7
26.9.6a.1.8.2 Test purpose
Verify that the eCall capable mobile equipped with USIM subscription restricted to eCall only
1. Able to make a test eCall.
2. Registers to the NW as a test eCall is initiated.
3. Remains registered on the network for a duration of T3243 following completion of a test eCall.
4. Detaches from network upon expiry of T3243.
5. Comes out of the eCall Inactive state when a test eCall is initiated (MS should register back to NW and then initiate test eCall).
26.9.6a.1.8.3 Method of test
Initial conditions
The eCall capable MS is equipped with USIM subscription restricted to eCall only.
System Simulator
1 cell, default parameters, ciphering off
T3212 set to 252 Minutes. ATT flag set to 1 (IMSI ATTACH/DETACH shall be performed in the cell)
Mobile Station
The MS is equipped with a Test USIM containing default values except for those listed below.
USIM field |
Contents |
EFUST |
Service n°2 Fixed Dialling Numbers (FDN) and Service n°89 eCall Data available |
EFFDN |
Display two FDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
EFEST |
Enabled Services Table |
Specific PICS statement(s)
–
Specific PIXIT statement(s)
–
Test procedure
a) MS is powered on. SS monitors to verify that MS does not attempt to register for a period of 120 seconds.
b) MS is made to initiate a Test eCall in accordance with manufacturer’s instructions. SS checks that MS performs registration before starting an Test eCall.
c) Having reached the active state, the call is cleared by the SS. SS monitors to verify that MS remains registered for the duration of T3243 and send LAU messages every 252 mins (as T3212 timer is set to 252 minutes).
d) Upon expiry of timer T3243 the MS shall perform IMSI detach.
Maximum Duration of Test
12 hours 20 minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
The MS is switched on. |
|
2 |
SS |
The SS verifies for 120 sec that the MS does not send RACH or any other message. |
|
3 |
MS |
MS is made to initiate a Test eCall (The first number stored in the EFFDN field) |
|
4 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to Location updating. |
5 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
6 |
MS -> SS |
LOCATION UPDATING REQUEST |
"Location Updating Type" = Normal location updating/IMSI Attach. |
7 |
SS->MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
10 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
11 |
SS -> MS |
CHANNEL RELEASE |
|
12 |
MS->SS |
CHANNEL REQUEST |
The SS verifies that the MS sends RACH Request with "Establishment cause" set to “originating call” |
13 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
14 |
MS -> SS |
CM SERVICE REQUEST |
|
15 |
SS -> MS |
CM SERVICE ACCEPT |
|
16 |
MS -> SS |
SETUP |
Verify called number is the Test eCall number. (The first number stored in the EFFDN field) |
17 |
SS -> MS |
CALL PROCEEDING |
|
18 |
SS -> MS |
ALERTING |
|
19 |
MS |
Depending on the PIXIT, an alerting indication is given. |
|
20 |
SS -> MS |
ASSIGNMENT COMMAND |
|
21 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
22 |
SS -> MS |
CONNECT |
|
23 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
24 |
MS |
Traffic channel is kept active for at least 5 seconds. |
|
25 |
SS -> MS |
DISCONNECT |
|
26 |
MS -> SS |
RELEASE |
|
27 |
SS -> MS |
RELEASE COMPLETE |
|
28 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
29 |
SS |
SS verifies that MS sends periodic Location Update Request every 252 minutes (5% margin is allowed). |
|
30 |
SS |
IMSI DETACH INDICATION |
SS verifies that MS performs IMSI detach after T3243 expires. (After 12 hours of completing step 28). 1% margin is allowed |
Specific Message Contents
None
26.9.7 Directed Retry / Mobile Originated Call
26.9.7.1 Conformance requirements
The MS shall correctly apply the Directed Retry procedure from SDCCH/8 (with frequency hopping) or SDCCH/4 to TCH/F or TCH/H with or without frequency hopping in the non-synchronized case during call establishment. The call control entity of the Mobile Station in the "mobile originating call proceeding" state shall, upon receipt of a CONNECT message, attach the appropriate user connection to the radio path and return a CONNECT ACKNOWLEDGE message to the SS.
References
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.4,
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 5.2.1.6. and 9.1.15.
3GPP TS 04.13, subclause 5.2.6.2.
26.9.7.2 Test purpose
To test that, when the MS is ordered to perform a non-synchronized handover after the CALL PROCEED message, it continuously sends access bursts on the main DCCH (and optionally on the SACCH) until it receives a PHYSICAL INFORMATION message from the SS. To test that the MS correctly takes the values of the Timing Advance information element in the PHYSICAL INFORMATION message into account. To test that the MS activates the new channel correctly and transmits the HANDOVER COMPLETE message without undue delay. To test that the call control entity of the Mobile Station in the "mobile originating call proceeding" state, upon receipt of a CONNECT message, attaches the appropriate user connection to the radio path and returns a CONNECT ACKNOWLEDGE message to the SS.
26.9.7.3 Method of test
Initial Conditions
System Simulator:
2 cells A and B with same LAI, default parameters, except:
Cell A has:
BCCH ARFCN = See the table below.
Cell Allocation = (See the table below.
PLMN colour code, NCC = as defaults.
BS colour code, BCC = as defaults.
PLMN_PERM = 00001010.
Cell B has:
BCCH ARFCN = See the table below.
Cell Allocation = See the table below.
PLMN colour code, NCC = 3.
BS colour code, BCC = 0.
Band |
Cell A |
Cell B |
Both Cells |
||
BCCH ARFCN |
Cell Allocation |
BCCH ARFCN |
Cell Allocation |
Format |
|
GSM 450 |
263 |
259, 261, 263, 265, 267, 269, 271, 273, 275, 277, 279, 281, 283, 285, 287, 289, 291 |
274 |
260, 262, 264, 266, 268, 270, 272, 274, 276, 279, 281, 283, 285, 287, 289, 291 |
Range 128 |
GSM 480 |
310 |
306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326, 328, 330, 332, 334, 336, 338 |
321 |
307, 309, 311, 313, 315, 317, 319, 321, 323, 326, 328, 330, 332, 334, 336, 338 |
Range 128 |
GSM 710 |
457 |
447, 454, 457, 463, 471, 479, 482 ,483 ,489, 496, 498, 500, 501, 502, 503, 506, 508 |
477 |
451, 455, 459, 461, 467, 468, 475, 477, 497, 498, 500, 501, 502, 503, 506, 508 |
Range 128 |
GSM 750 |
457 |
447, 454, 457, 463, 471, 479, 482 ,483 ,489, 496, 498, 500, 501, 502, 503, 506, 508 |
477 |
451, 455, 459, 461, 467, 468, 475, 477, 497, 498, 500, 501, 502, 503, 506, 508 |
Range 128 |
T-GSM 810 |
457 |
447, 454, 457, 463, 471, 479, 482 ,483 ,489, 496, 498, 500, 501, 502, 503, 506, 508 |
477 |
451, 455, 459, 461, 467, 468, 475, 477, 497, 498, 500, 501, 502, 503, 506, 508 |
Range 128 |
GSM 850 |
147 |
137, 144, 147, 153, 161, 169, 172, 173, 179, 186, 193, 200, 201, 202, 203, 235, 241 |
167 |
141, 145, 149, 151, 157, 158, 165, 167, 187, 193, 200, 201, 202, 203, 235, 241 |
Range 128 |
GSM 900 |
20 |
10, 17, 20, 26, 34, 42, 45, 46, 52, 59, 66, 73, 74, 75, 76, 108, 114 |
40 |
14, 18, 22, 24, 30, 31, 38, 40, 60, 66, 73, 74, 75, 76, 108, 114 |
Bitmap 0 |
DCS 1 800 |
747 |
734, 741, 747, 754, 759, 762, 766, 767, 773, 775, 779, 782, 791, 798, 829, 832, 844 |
764 |
739, 743, 746, 749, 756, 758, 761, 764, 771, 779, 782, 791, 798, 829, 832, 844 |
Range 512 |
PCS 1 900 |
647 |
634, 641, 647, 654, 659, 662, 666, 667, 673, 675, 679, 682, 691, 698, 729, 732, 744 |
664 |
639, 643, 646, 649, 656, 658, 661, 664, 671, 679, 682, 691, 698, 729, 732, 744 |
Range 512 |
The timebase of Cells A and B shall be such that the edges of their timeslots are not coincident at the antenna connector.
For execution counter M = 1 a combined CCH/SDCCH is used.
For execution counter M = 2 a non-combined SDCCH is used.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated and camped on cell A.
Specific PICS statements:
– Speech supported for Half rate version 1 (GSM HR) (TSPC_AddInfo_Half_rate_version_1)
PIXIT statements:
– Way to indicate mobile originated alerting.
Foreseen Final State of the MS
"Idle, updated" with TMSI allocated and camped on cell B.
Test Procedure
This procedure is repeated for execution counter M = 1..2.
A teleservice is selected that is supported by the MS; if the MS supports speech, the selected teleservice is speech. If necessary, the MS is configured for that teleservice.
The MS is made to initiate a call on Cell A. After the SS has sent the CALL PROCEEDING message the SS sends a HANDOVER COMMAND message, ordering the MS to switch to cell B. The MS shall then begin to send access bursts on the new DCCH (and optionally on the SACCH) to cell B. The SS observes the access bursts and after receiving n (n being arbitrarily chosen between values according to table 26.6‑2 of subclause 26.6.5) access bursts, the SS sends one PHYSICAL INFORMATION message with an arbitrarily chosen Timing Advance. The MS shall activate the channel in sending and receiving mode. The MS shall establish a signalling link. The MS shall be ready to transmit a HANDOVER COMPLETE message before x ms after the end of the PHYSICAL INFORMATION message, but not before a UA frame has been sent by the SS. After the successful handover procedure the SS sends the ALERTING message. The correct alerting indication shall be given to the user (only applicable if the MS supports this feature). The SS sends the CONNECT message indicating that the call has been answered. The appropriate bearer channel shall be through connected in both directions. The MS shall send then the CONNECT ACKNOWLEDGE message as the response on the CONNECT message. Having reached the active state, the call is cleared by the SS.
The term "ready to transmit" is defined in 3GPP TS 04.13. The value of "x" depends upon the target channel and is specified in the specific message contents section.
Maximum Duration of Test
2 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
The sequence is performed for execution counter M = 1..2 (unless a particular TCH is not supported).
Step |
Direction |
Message |
Comments |
1 |
——– |
——– |
A MO call is initiated on cell A. |
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is "originating call and the network does not set the NECI bit to 1". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
See specific message contents. |
4 |
MS -> SS |
CM SERVICE REQUEST |
CM Service Type = Mobile Originating Call Establishment. |
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
9 |
SS |
SS starts ciphering. |
|
10 |
MS -> SS |
SETUP |
|
11 |
SS -> MS |
CALL PROCEEDING |
|
12 |
SS -> MS |
HANDOVER COMMAND |
See specific message contents. |
13 |
MS -> SS |
HANDOVER ACCESS |
Repeated on every burst of the uplink main DCCH (and optionally on the SACCH) until reception of PHYSICAL INFORMATION. Handover Reference as included in the HANDOVER COMMAND. |
14 |
SS -> MS |
PHYSICAL INFORMATION |
Sent after reception of n HANDOVER ACCESS message. Timing Advance is arbitrarily chosen. |
15 |
MS -> SS |
SABM |
Sent without information field. |
16 |
SS -> MS |
UA |
|
17 |
MS -> SS |
HANDOVER COMPLETE |
This message shall be ready to be transmitted before "x" ms after the completion of step 14. |
18 |
SS -> MS |
ALERTING |
|
19 |
MS |
Depending on the PIXIT, an alerting indication is given. |
|
20 |
SS -> MS |
CONNECT |
|
21 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
22 |
MS |
The appropriate bearer channel is through connected in both directions. |
|
23 |
SS -> MS |
DISCONNECT |
|
24 |
MS -> SS |
RELEASE |
|
25 |
SS -> MS |
RELEASE COMPLETE |
|
26 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents For Mobiles Supporting Speech
M = 1:
IMMEDIATE ASSIGNMENT
Information Element |
value/remark |
As default message contents. |
HANDOVER COMMAND
Information Element |
value/remarks |
As default message contents, except: |
|
Cell Description |
|
– Network Colour Code |
3 |
– Base Station Colour Code |
0 |
– BCCH Carrier Number |
See the table below |
Channel Description |
|
– Channel Type |
TCH/F + ACCHs |
– TDMA offset |
Chosen arbitrarily. |
– Timeslot number |
Chosen arbitrarily but not zero. |
– Training Sequence Code |
Chosen arbitrarily. |
– Hopping |
RF hopping channel. |
– MAIO |
Chosen arbitrarily from the set (0, 1 to N‑1), where N is the number of frequencies encoded in the Frequency List IE. |
– HSN |
Zero (this gives cyclic hopping). |
Synchronization Indication IE is not included |
|
Frequency list after time |
|
– Frequency List |
Encode frequencies as per the table below. |
Channel Mode IE |
Speech (full rate version 1 or half rate version 1). |
Step 17: "x" = 500.
HANDOVER COMMAND |
|||
Band |
Frequency Short List |
BCCH Carrier Number |
|
Format |
ARFCNs |
ARFCN |
|
GSM 450 |
Range 128 |
260, 262, 264, 266, 268, 270, 272, 276, 279, 281, 283, 285, 287, 289, 291 |
274 |
GSM 480 |
Range 128 |
307, 309, 311, 313, 315, 317, 319, 323, 326, 328, 330, 332, 334, 336, 338 |
321 |
GSM 710 |
Range 128 |
451, 455, 459, 461, 467, 468, 475, 497, 498, 500, 501, 502, 503, 506, 508 |
477 |
GSM 750 |
Range 128 |
451, 455, 459, 461, 467, 468, 475, 497, 498, 500, 501, 502, 503, 506, 508 |
477 |
T-GSM 810 |
Range 128 |
451, 455, 459, 461, 467, 468, 475, 497, 498, 500, 501, 502, 503, 506, 508 |
477 |
GSM 850 |
Range 128 |
141, 145, 149, 151, 157, 158, 165, 187, 193, 200, 201, 202, 203, 235, 241 |
167 |
GSM 900 |
Range 128 |
14, 18, 22, 24, 30, 31, 38, 60, 66, 73, 74, 75, 76, 108, 114 |
40 |
DCS 1 800 |
Range 128 |
746, 779 |
764 |
PCS 1 900 |
Range 128 |
646, 679 |
664 |
M = 2:
IMMEDIATE ASSIGNMENT
Information Element |
value/remark |
As default message contents except: |
|
L2 pseudo length |
See the table below. |
Channel Description |
|
– Channel Type |
SDCCH/8 |
– TDMA offset |
As default message contents. |
– Timeslot number |
Arbitrary value, but not zero. |
– Training Sequence Code |
Chosen arbitrarily. |
– Hopping |
RF hopping channel. |
– MAIO |
Chosen arbitrarily from the set (0, 1 to N‑1), where N is the number of frequencies encoded in the Mobile Allocation. |
– HSN |
Zero (this gives cyclic hopping). |
Mobile Allocation |
|
– Length |
3 octets. |
– Contents |
See the table below. |
IMMEDIATE ASSIGNMENT |
||
Band |
Mobile Allocation |
L2 pseudo length |
GSM 450 |
281, 283, 285 |
14 octets (11 + contents of the MA) |
GSM 480 |
328, 330, 332 |
14 octets (11 + contents of the MA) |
GSM 710 |
500, 501, 502 |
14 octets (11 + contents of the MA) |
GSM 750 |
500, 501, 502 |
14 octets (11 + contents of the MA) |
T-GSM 810 |
500, 501, 502 |
14 octets (11 + contents of the MA) |
GSM 850 |
200, 201, 202 |
14 octets (11 + contents of the MA) |
GSM 900 |
73, 74, 75 |
14 octets (11 + contents of the MA) |
DCS 1 800 |
Indicates all of the CA of cell A except ARFCNs 747 and 767. |
|
PCS 1 900 |
Indicates all of the CA of cell A except ARFCNs 647 and 667 |
HANDOVER COMMAND
As default message contents, except: |
|
Cell Description |
|
– Network Colour Code |
3 |
– Base Station Colour Code |
0 |
– BCCH Carrier Number |
See the table below |
Channel Description |
|
– Channel Type |
TCH/H + ACCHs |
– TDMA offset |
Chosen arbitrarily. |
– Timeslot number |
Chosen arbitrarily but not zero. |
– Training Sequence Code |
Chosen arbitrarily. |
– Hopping |
RF hopping channel. |
– MAIO |
Chosen arbitrarily from the set (0, 1 to N‑1), where N is the number of frequencies encoded in the Mobile Allocation. |
– HSN |
Chosen arbitrarily from the set (1, 2.. 63). |
Synchronization Indication |
|
– Report Observed Time Difference |
Shall not be included. |
– Synchronization Indication |
"Non synchronized". |
– Normal Cell Indication |
Ignore out of range timing advance. |
Cell Channel Description |
Encode frequencies as per the table below |
Mobile Allocation after time |
indicates channels as per the table below only |
Channel Mode IE |
speech (full rate version 1 or half rate version 1). |
Step 17: "x" = 750.
HANDOVER COMMAND |
||||
Band |
BCCH Carrier Number |
Cell Channel Description |
Mobile Allocation after time |
|
ARFCN |
Format |
ARFCNs |
||
GSM 450 |
274 |
Range 128 |
274, 279, 281, 283, 285, 287, 289, 291 |
281, 283, 285 |
GSM 480 |
321 |
Range 128 |
321, 326, 328, 330, 332, 334, 336, 338 |
328, 330, 332 |
GSM 710 |
477 |
Range 128 |
477, 498, 500, 501, 502, 503, 506, 508 |
500, 501, 502 |
GSM 750 |
477 |
Range 128 |
477, 498, 500, 501, 502, 503, 506, 508 |
500, 501, 502 |
T-GSM 810 |
477 |
Range 128 |
477, 498, 500, 501, 502, 503, 506, 508 |
500, 501, 502 |
GSM 850 |
167 |
Range 128 |
167, 193, 200, 201, 202, 203, 235, 241 |
200, 201, 202 |
GSM 900 |
40 |
Bitmap 0 |
40, 66, 73, 74, 75, 76, 108, 114 |
73, 74, 75 |
DCS 1 800 |
764 |
Range 512 |
761, 764, 771, 779, 782, 791, 798, 829, 832 |
791, 798, 829 |
PCS 1 900 |
664 |
Range 512 |
661, 664, 671, 679, 682, 691, 698, 629, 632 |
679, 682, 691 |
Specific Message Contents For Mobiles not Supporting Speech
The message contents shall be the same as for a Mobile Station supporting speech, except for:
For M = 1 (TCH/F):
HANDOVER COMMAND
Information Element |
value/remarks |
Mode of first channel |
Arbitrary from those supported (12, 6, 3.6 kbps). |
For M = 2 (TCH/H):
HANDOVER COMMAND
Information Element |
value/remarks |
Mode of first channel |
Arbitrary from those supported (6, 3.6 kbps). |
26.9.8 Directed Retry / Mobile Terminated Call
This test is applicable to all MS which support at least one MT circuit switched basic service.
26.9.8.1 Conformance requirements
The MS shall correctly apply the Directed Retry procedure from SDCCH/8 (with frequency hopping) or SDCCH/4 to TCH/F or TCH/H with or without frequency hopping in the non-synchronized case during call establishment. The call control entity of the Mobile Station in the "call delivered" state shall, if the MS supports immediate connect, continue the call establishment by through-connecting the traffic channel in both directions, or if the MS does not support immediate connect, send an ALERTING message. The MS indicates acceptance of a MT call by sending CONNECT.
For speech calls the mobile station shall attach the user connection at latest when sending the CONNECT message, except if there is no compatible radio resource available at this time. In this case the attachment shall be delayed until such a resource becomes available.
For Data Calls the mobile station shall attach the user connection when receiving the CONNECT ACKNOWLEDGE message from the network.
References
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.4,
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 5.2.2.5, 5.2.2.6, 5.2.2.9 and 9.1.15.
3GPP TS 04.13, subclause 5.2.6.2.
26.9.8.2 Test purpose
To test that when the MS is ordered to perform a non-synchronized handover after the CALL CONFIRM message, it continuously sends access bursts on the main DCCH (and optionally on the SACCH) until it receives a PHYSICAL INFORMATION message from the SS. To test that the MS correctly takes the values of the Timing Advance information element in the PHYSICAL INFORMATION message into account. To test that the MS activates the new channel correctly and transmits the HANDOVER COMPLETE message without undue delay. To test that the call control entity of the Mobile Station in the "call delivered" state, if the MS supports immediate connect, continues the call establishment by through-connecting the traffic channel in both directions, or if the MS does not support immediate connect, sends an ALERTING message. To test that the MS indicates acceptance of a MT call by sending CONNECT.
To test that for speech calls the mobile station attaches the user connection at latest when sending the CONNECT message, except if there is no compatible radio resource available at this time. To test that in this case the attachment is delayed until such a resource becomes available.
To test that for Data Calls the mobile station attaches the user connection when receiving the CONNECT ACKNOWLEDGE message from the network.
26.9.8.3 Method of test
Initial Conditions
System Simulator:
2 cells A and B with same LAI, default parameters, except:
Cell A has:
BCCH ARFCN = See the table below.
Cell Allocation = See the table below.
PLMN colour code, NCC = as defaults.
BS colour code, BCC = as defaults.
PLMN_PERM = 00001010.
Cell B has:
BCCH ARFCN = See the table below.
Cell Allocation = See the table below.
PLMN colour code, NCC = 3.
BS colour code, BCC = 0.
Band |
Cell A |
Cell B |
Both Cells |
||
BCCH ARFCN |
Cell Allocation |
BCCH ARFCN |
Cell Allocation |
Format |
|
GSM 450 |
263 |
259, 261, 263, 265, 267, 269, 271, 273, 275, 277, 279, 281, 283, 285, 287, 289, 291 |
274 |
260, 262, 264, 266, 268, 270, 272, 274, 276, 279, 281, 283, 285, 287, 289, 291 |
Range 128 |
GSM 480 |
310 |
306, 308, 310, 312, 314, 316, 318, 320, 322, 324, 326, 328, 330, 332, 334, 336, 338 |
321 |
307, 309, 311, 313, 315, 317, 319, 321, 323, 326, 328, 330, 332, 334, 336, 338 |
Range 128 |
GSM 710 |
457 |
447, 454, 457, 463, 471, 479, 482 ,483 ,489, 496, 498, 500, 501, 502, 503, 506, 508 |
477 |
451, 455, 459, 461, 467, 468, 475, 477, 497, 498, 500, 501, 502, 503, 506, 508 |
Range 128 |
GSM 750 |
457 |
447, 454, 457, 463, 471, 479, 482 ,483 ,489, 496, 498, 500, 501, 502, 503, 506, 508 |
477 |
451, 455, 459, 461, 467, 468, 475, 477, 497, 498, 500, 501, 502, 503, 506, 508 |
Range 128 |
T-GSM 810 |
457 |
447, 454, 457, 463, 471, 479, 482 ,483 ,489, 496, 498, 500, 501, 502, 503, 506, 508 |
477 |
451, 455, 459, 461, 467, 468, 475, 477, 497, 498, 500, 501, 502, 503, 506, 508 |
Range 128 |
GSM 850 |
147 |
137, 144, 147, 153, 161, 169, 172, 173, 179, 186, 193, 200, 201, 202, 203, 235, 241 |
167 |
141, 145, 149, 151, 157, 158, 165, 167, 187, 193, 200, 201, 202, 203, 235, 241 |
Range 128 |
GSM 900 |
20 |
10, 17, 20, 26, 34, 42, 45, 46, 52, 59, 66, 73, 74, 75, 76, 108, 114 |
40 |
14, 18, 22, 24, 30, 31, 38, 40, 60, 66, 73, 74, 75, 76, 108, 114 |
Bitmap 0 |
DCS 1 800 |
747 |
734, 741, 747, 754, 759, 762, 766, 767, 773, 775, 779, 782, 791, 798, 829, 832, 844 |
764 |
739, 743, 746, 749, 756, 758, 761, 764, 771, 779, 782, 791, 798, 829, 832, 844 |
Range 512 |
PCS 1 900 |
647 |
634, 641, 647, 654, 659, 662, 666, 667, 673, 675, 679, 682, 691, 698, 729, 732, 744 |
664 |
639, 643, 646, 649, 656, 658, 661, 664, 671, 679, 682, 691, 698, 729, 732, 744 |
Range 512 |
The timebase of Cells A and B shall be such that the edges of their timeslots are not coincident at the antenna connector.
For execution counter M = 1 a combined CCH/SDCCH is used.
For execution counter M = 2 a non-combined SDCCH is used.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated and camped on cell A.
Specific PICS statements:
– Speech supported for Half rate version 1 (GSM HR) (TSPC_AddInfo_Half_rate_version_1)
– Immediate connect supported for all circuit switched basic services. (TSPC_AddInfo_ImmConn)
PIXIT statements:
– Way to indicate alerting.
– Way to make the MS accept an incoming call after alerting.
Foreseen Final State of the MS
"Idle, updated" with TMSI allocated and camped on cell B.
Test Procedure
This procedure is repeated for execution counter M = 1..2.
A teleservice is selected that is supported by the MS; if the MS supports speech, the selected teleservice is speech. If necessary, the MS is configured for that teleservice.
The MS is paged on Cell A. The MS responds to the PAGING REQUEST message and establishes a mobile terminated call on Cell A. If the MS supports immediate connect, it continues the call establishment by through-connecting the traffic channel in both directions, or if the MS does not support immediate connect, it sends an ALERTING message. The MS indicates acceptance of a MT call by sending CONNECT.
After the MS has sent the CALL CONFIRMED message (if the MS supports immediate connect then the MS sends the CONNECT message after the CALL CONFIRMED message on the old channel) the SS sends a HANDOVER COMMAND message, ordering the MS to switch to cell B. The MS shall then begin to send access bursts on the new DCCH (and optionally on the SACCH) to cell B. The SS observes the access bursts and after receiving n (n being arbitrarily chosen between values according to table 26.6‑2 of subclause 26.6.5) access bursts, the SS sends one PHYSICAL INFORMATION message with an arbitrarily chosen Timing Advance. The MS shall activate the channel in sending and receiving mode. The MS shall establish a signalling link. The MS shall be ready to transmit a HANDOVER COMPLETE message before x ms after the end of the PHYSICAL INFORMATION message, but not before a UA frame has been sent by the SS. After the successful handover procedure the MS sends the ALERTING message (if the MS runs the immediate connect procedure then the MS does not send an ALERTING message). The correct alerting indication shall be given to the user (only applicable if the MS supports the feature or if the MS is not using the immediate connect procedure). After the MS sent the CONNECT message the appropriate bearer channel shall be through connected in both directions. The SS sends then the CONNECT ACKNOWLEDGE message as the response on the CONNECT message. Having reached the active state, the call is cleared by the SS.
The term "ready to transmit" is defined in 3GPP TS 04.13. The value of "x" depends upon the target channel and is specified in the specific message contents section.
Maximum Duration of Test
2 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
The sequence is performed for execution counter M = 1..2 (unless a particular TCH is not supported).
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging subchannel on cell A. |
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
See specific message contents. |
4 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM. |
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
9 |
SS |
SS starts ciphering. |
|
10 |
SS -> MS |
SETUP |
|
11 |
MS -> SS |
CALL CONFIRMED |
|
If the MS supports immediate connect then branch A applies. If the MS does not support immediate connect then branch B applies |
|||
A12 |
MS -> SS |
CONNECT |
sent on the old channel |
A13 |
SS -> MS |
HANDOVER COMMAND |
See specific message contents. |
A14 |
MS -> SS |
HANDOVER ACCESS |
Repeated on every burst of the uplink main DCCH (and optionally on the SACCH) until reception of PHYSICAL INFORMATION. Handover Reference as included in the HANDOVER COMMAND. If the HANDOVER COMMAND includes a starting time IE then the first HANDOVER ACCESS message shall be transmitted in the indicated frame (unless the indicated frame is not used by that channel, in which case the next frame used by that channel shall be used). |
A15 |
SS -> MS |
PHYSICAL INFORMATION |
Sent after reception of n HANDOVER ACCESS message. Timing Advance is arbitrarily chosen. |
A16 |
MS -> SS |
SABM |
Sent without information field. |
A17 |
SS -> MS |
UA |
|
A18 |
MS -> SS |
HANDOVER COMPLETE |
This message shall be ready to be transmitted before "x" ms after the completion of step A15. |
B12 |
SS -> MS |
HANDOVER COMMAND |
See specific message contents. |
B13 |
MS -> SS |
HANDOVER ACCESS |
Repeated on every burst of the uplink main DCCH (and optionally on the SACCH) until reception of PHYSICAL INFORMATION. Handover Reference as included in the HANDOVER COMMAND. If the HANDOVER COMMAND includes a starting time IE then the first HANDOVER ACCESS message shall be transmitted in the indicated frame (unless the indicated frame is not used by that channel, in which case the next frame used by that channel shall be used). |
B14 |
SS -> MS |
PHYSICAL INFORMATION |
Sent after reception of n HANDOVER ACCESS message. Timing Advance is arbitrarily chosen. |
B15 |
MS -> SS |
SABM |
Sent without information field. |
B16 |
SS -> MS |
UA |
|
B17 |
MS -> SS |
HANDOVER COMPLETE |
This message shall be ready to be transmitted before "x" ms after the completion of step B14. |
B18 |
MS -> SS |
ALERTING |
|
B19 |
MS |
Gives an alerting indication as defined in a PIXIT statement is given by the MS |
|
B20 |
MS |
The MS is made to accept the call in the way described in a PIXIT statement |
|
B21 |
MS -> SS |
CONNECT |
|
22 |
MS |
If the call is a speech call, the TCH shall be through connected in both directions. |
|
23 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
24 |
MS |
If the call is a data call, the TCH shall be through connected in both directions. |
|
25 |
SS -> MS |
DISCONNECT |
|
26 |
MS -> SS |
RELEASE |
|
27 |
SS -> MS |
RELEASE COMPLETE |
|
28 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents For Mobiles Supporting Speech
M = 1:
IMMEDIATE ASSIGNMENT
Information Element |
value/remark |
As default message contents. |
HANDOVER COMMAND
Information Element |
value/remarks |
As default message contents, except: |
|
Cell Description |
|
– Network Colour Code |
3 |
– Base Station Colour Code |
0 |
– BCCH Carrier Number |
See the table below |
Channel Description |
|
– Channel Type |
TCH/F + ACCHs |
– Timeslot number |
Zero. |
– Training Sequence Code |
Chosen arbitrarily. |
– Hopping |
Single RF Channel. |
– ARFCN |
Chosen arbitrarily from the Cell Allocation of Cell B, but not the BCCH carrier of Cell B. |
Synchronization Indication IE not included. |
|
Mode of First Channel |
Speech (full rate version 1 or half rate version 1). |
Band |
BCCH Carrier Number |
GSM 450 |
274 |
GSM 480 |
321 |
GSM 710 |
477 |
GSM 750 |
477 |
T-GSM 810 |
477 |
GSM 850 |
167 |
GSM 900 |
40 |
DCS 1 800 |
764 |
PCS 1 900 |
664 |
Step A18 / B17: "x" = 500.
M = 2:
IMMEDIATE ASSIGNMENT
Information Element |
value/remark |
As default message contents except: |
|
L2 pseudo length |
See the table below |
Channel Description |
|
– Channel Type |
SDCCH/8 |
– TDMA offset |
As default message contents. |
– Timeslot number |
Arbitrary value, but not zero. |
– Training Sequence Code |
Chosen arbitrarily. |
– Hopping |
RF hopping channel. |
– MAIO |
Chosen arbitrarily from the set (0, 1 to N‑1), where N is the number of frequencies encoded in the Mobile Allocation. |
– HSN |
Chosen arbitrarily from the set (1,2,..63). |
Mobile Allocation |
|
– Length |
3 octets. |
– Contents |
Indicates only three frequencies, as per the table below |
IMMEDIATE ASSIGNMENT |
||
Band |
Mobile Allocation |
L2 pseudo length |
GSM 450 |
281, 283, 285 |
14 octets (11 + contents of the MA) |
GSM 480 |
328, 330, 332 |
14 octets (11 + contents of the MA) |
GSM 710 |
500, 501, 502 |
14 octets (11 + contents of the MA) |
GSM 750 |
500, 501, 502 |
14 octets (11 + contents of the MA) |
T-GSM 810 |
500, 501, 502 |
14 octets (11 + contents of the MA) |
GSM 850 |
200, 201, 202 |
14 octets (11 + contents of the MA) |
GSM 900 |
73, 74, 75 |
14 octets (11 + contents of the MA) |
DCS 1 800 |
773, 775, 779 |
|
PCS 1 900 |
673, 675, 679 |
HANDOVER COMMAND
Information Element |
value/remarks |
As default message contents, except: |
|
Cell Description |
|
– Network Colour Code |
3 |
– Base Station Colour Code |
0 |
– BCCH Carrier Number |
See the table below |
Channel Description |
|
– Channel Type |
TCH/H + ACCHs |
– TDMA offset |
Chosen arbitrarily. |
– Timeslot number |
Chosen arbitrarily, but not Zero. |
– Training Sequence Code |
Chosen arbitrarily. |
– Hopping |
RF hopping channel. |
– MAIO |
Chosen arbitrarily from the set (0, 1 to N‑1), where N is the number of frequencies encoded in the Frequency List IE. |
– HSN |
Zero (this gives cyclic hopping). |
Frequency List after time |
|
– Frequency List |
Encode the frequencies as per the table below. |
Synchronization Indication |
|
– Report Observed Time Difference |
Shall not be included. |
– Synchronization Indication |
"Non synchronized". |
– Normal Cell Indication |
Ignore out of range timing advance. |
Mode of First Channel |
Speech (full rate version 1 or half rate version 1). |
Starting Time |
Indicates the frame number of cell B. that will occur approximately 1,1 seconds (238 frames have elapsed) after the HANDOVER COMMAND is sent by cell A. |
HANDOVER COMMAND |
|||
Band |
BCCH Carrier Number |
Cell Channel Description |
|
ARFCN |
Format |
ARFCNs |
|
GSM 450 |
274 |
Range 128 |
260, 262, 264, 266, 276, 279, 281, 283, 285, 287, 289, 291 |
GSM 480 |
321 |
Range 128 |
307, 309, 311, 313, 323, 326, 328, 330, 332, 334, 336, 338 |
GSM 710 |
477 |
Range 128 |
451, 455, 459, 461, 497, 498, 500, 501, 502, 503, 506, 508 |
GSM 750 |
477 |
Range 128 |
451, 455, 459, 461, 497, 498, 500, 501, 502, 503, 506, 508 |
T-GSM 810 |
477 |
Range 128 |
451, 455, 459, 461, 497, 498, 500, 501, 502, 503, 506, 508 |
GSM 850 |
167 |
Range 128 |
141, 145, 149, 151, 187, 193, 200, 201, 202, 203, 235, 241 |
GSM 900 |
40 |
Bitmap 0 |
14, 18, 22, 24, 60, 66, 73, 74, 75, 76,108, 114 |
DCS 1 800 |
764 |
Range 512 |
749, 758, 761, 764, 771, 779, 782, 791, 798, 829, 832, 844 |
PCS 1 900 |
664 |
Range 512 |
649, 658, 661, 664, 671, 679, 682, 691, 698, 729, 732, 744 |
Step A18 / B17: "x" = 750.
Specific Message Contents For Mobiles not Supporting Speech
The message contents shall be the same as for a Mobile Station supporting speech, except for:
For M = 1 (TCH/F):
HANDOVER COMMAND
Information Element |
value/remarks |
Mode of first channel |
Arbitrary from those supported (12, 6, 3.6 kbps). |
For M = 2 (TCH/H):
HANDOVER COMMAND
Information Element |
value/remarks |
Mode of first channel |
Arbitrary from those supported (6, 3.6 kbps). |
26.9.9 Default contents of messages
ALERTING (mobile station to network direction)
Information element |
Value/remark |
Facility |
Not checked |
User-user |
Not checked |
SS version |
Not checked |
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 26.1.1 |
Frequency list |
Omitted |
Cell channel description |
Omitted |
Mode of the first channel |
appropriate for one 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 |
normal event |
AUTHENTICATION REQUEST
Information element |
Value/remark |
Ciphering key sequence number |
Arbitrary |
Spare half octet |
(spare bits) |
Authentication parameter RAND |
Arbitrary |
AUTHENTICATION RESPONSE
Information element |
Value/remark |
Authentication parameter SRES |
Correct for given SRES |
CALL CONFIRMED
Information element |
Value/remark |
Repeat indicator |
Omitted |
Bearer capability 1 |
The bearer capability 1 information element shall be included if and only if at least one of the following cases holds: ‑ the mobile station wishes another bearer capability than that given by the bearer capability 1 information element of the incoming SETUP message; ‑ the bearer capability 1 information element received in the SETUP message is accepted and the "radio channel requirement" of the Mobile Station is other than "full rate support only mobile station". – the bearer capability 1 information element received in the SETUP message indicates speech and is accepted and the Mobile Station supports other speech versions than GSM full rate version 1/ half rate version 1. |
Bearer capability 2 |
Omitted |
Cause |
Omitted |
CC Capabilities |
may be present |
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 teleservice (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 RELEASE
Information element |
Value/remark |
RR cause |
Normal event |
CHANNEL REQUEST
Information element |
Value/remark |
Establishment cause |
Answer to paging (100) |
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
Information element |
Value/remark |
Mobile equipment identity |
Omitted |
CM SERVICE ACCEPT
Information element |
Value/remark |
none but message head |
CM SERVICE REQUEST
Information element |
Value/remark |
CM service type |
Mobile originating call establishment or packet mode connection establishment |
Ciphering key sequence number |
CKSN of the MS |
Mobile station classmark 2 |
Not checked |
Mobile identity |
TMSI of MS |
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)
Information element |
Value/remark |
Facility |
Not checked |
Connected subaddress |
Not checked |
User-user |
Not checked |
SS version |
Not checked |
CONNECT ACKNOWLEDGE
Information element |
Value/remark |
none but message head |
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 |
|
Coding standard |
GSM |
Location |
User |
Cause value |
Normal clearing |
Facility |
Not checked |
User-user |
Not checked |
SS version |
Not checked |
EMERGENCY SETUP
Information element |
Value/remark |
Bearer Capability |
May be present or omitted. If present, it shall indicate speech, the appropriate speech version(s) and have the appropriate value of radio channel requirement field |
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 |
N51, N32, N26 |
Corresponding to frame number of the CHANNEL REQUEST |
Timing advance |
Arbitrary |
Mobile allocation |
Empty (L=0) |
Starting time |
Omitted |
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
Information element |
Value/remark |
Ciphering key sequence number |
Value assigned to MS in the initial conditions |
Spare half octet |
(spare bits) |
Mobile station classmark 2 |
Not checked |
Mobile identity |
specifies TMSI of MS |
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)
Information element |
Value/remark |
Cause |
Not checked |
Second cause |
Not checked |
Facility |
Not checked |
User-user |
Not checked |
SS version |
Not checked |
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)
Information element |
Value/remark |
Cause |
Not checked |
Facility |
Not checked |
User-user |
Not checked |
SS version |
Not checked |
SETUP (MS to SS)
Information element |
Value/remark |
BC Repeat indicator |
Omitted |
Bearer capability 1 |
Appropriate for the teleservice selected for the test |
Bearer capability 2 |
Omitted |
Facility |
Not checked |
Calling party subaddress |
Not checked |
Called party BCD number |
As entered |
Called party subaddress |
Omitted |
LLC repeat indicator |
Omitted |
Low layer compatibility I |
Appropriate for teleservice selected for the test |
Low layer compatibility II |
Omitted |
HLC repeat indicator |
Omitted |
High layer compatibility i |
Appropriate for teleservice selected for the test |
High layer compatibility ii |
Omitted |
User-user |
Not checked |
SS version |
Not checked |
CLIR suppression |
Not checked |
CC Capabilities |
may be present |
SETUP (SS to MS)
Information element |
Value/remark |
BC repeat indicator |
Omitted |
Bearer capability 1 |
Appropriate for teleservice selected for the test |
Bearer capability 2 |
Omitted |
Facility |
Omitted |
Progress indicator |
Omitted |
Signal |
Omitted |
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 teleservice selected for the test |
Low layer compatibility II |
Omitted |
HLC repeat indicator |
Omitted |
High layer compatibility i |
Appropriate for the teleservice selected for the test |
High layer compatibility ii |
Omitted |
User-user |
Omitted |