41.8 EC-GSM-IoT procedures

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

41.8.1 EC-GSM-IoT / Packet Access

41.8.1.1 EC-GSM-IoT / Packet Access / EC-BCCH CHANGE MARK

41.8.1.1.1 Conformance requirements

A MS that has enabled EC operation shall have read a complete EC-SI message set no longer than 24 hours prior to attempting packet access. In addition, if the mobile station detects a change to the EC- BCCH CHANGE MARK field when reading the EC-SCH it shall re-acquire one ore more EC-SI (as determined by the EC SI_CHANGE_MARK field in the first received EC-SI message) before attempting packet access (see sub-clause 3.5.2a). […]

Reference

3GPP TS 44.018 subclause 3.10.4

A mobile station that has enabled EC operation uses its currently estimated uplink coverage class to determine the number of blind physical layer transmissions to use when sending an EC PACKET CHANNEL REQUEST message (see sub-clause 3.5.2a) and includes an estimate of its downlink coverage class in the message (see sub-clause 9.1.65).

Reference

3GPP TS 44.018 subclause 3.10.5

On receipt of an EC-IMMEDIATE ASSIGNMENT TYPE 2 message corresponding to its last EC PACKET CHANNEL REQUEST message, the mobile station stops T3146 (if running), stops sending EC PACKET CHANNEL REQUEST messages, and switches to the assigned PDCH(s).

Reference

3GPP TS 44.018 subclause 3.5.2.1.3a.1

41.8.1.1.2 Test purpose

To verify that a change of EC-BCCH CHANGE MARK detected when initiating uplink packet access triggers an EC-System Information acquisition prior to performing the uplink packet access.

To verify that the EC-GSM-IoT capable mobile station uses the correct procedures for packet access.

41.8.1.1.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported

1TS EC-RACH Mapping used:

– Access Timeslots field in EC_SI2 set to ‘0’.

CC used: CC1 in downlink and uplink.

– CC1 used in the downlink: Signal level for FCCH and EC-SCH set-up such that the estimated received signal level parameter (C_VALUE) is greater than BT_Threshold_DL. BT_Threshold_DL is broadcast in EC_SI2 message. See 3GPP TS 45.008 §6.10.2.

– CC1 used in the uplink: Signal level for FCCH and EC-SCH set-up such that the estimated uplink received signal strength (BS_RX_PWR) is greater than BT_Threshold_UL. This requires proper setting of BT_Threshold_UL, MSPWR, MS_TXPWR_MAX_CCH, BSPWR. MS_TXPWR_MAX_CCH and BSPWR are broadcast in EC_SI2 message. See 3GPP TS 45.008 §6.10.3.

Mobile Station:

The MS is GPRS attached in packet idle mode. PDP context 2 has been established.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The EC-BCCH CHANGE MARKfield is set updated to 001’ in EC-SCH. The parameter EC_MAX_RETRANS is changed to 2 retransmissions in EC-SI 2.

The MS is triggered to send uplink data (2 MCS-1 coded RLC data blocks using normal priority). The MS checks the EC-BCCH CHANGE MARK on EC-SCH, notices the change and re-acquires the EC System Information Type 2 message.

The MS then sends an EC PACKET CHANNEL REQUEST.

The SS ignores first EC PACKET CHANNEL REQUEST message and acts on the second EC PACKET CHANNEL REQUEST message (verifies that 2 retransmissions of the EC PACKET CHANNEL REQUEST are done)

Maximum duration of the test

Expected sequence

Step

Direction

Message

Comments

1

SS

EC-SCH update with EC-BCCH CHANGE MARK set to ‘1’,

EC_MAX_RETRANS set to 2 retransmission in EC-SI2, Access_Timeslots field in EC_SI2 set to ‘0’ and EC SI_CHANGE_MARK set to indicate that only EC-SI 2 has changed

2

MS

Trigger to UL data send data

3

MS ->SS

EC PACKET CHANNEL REQUEST

1TS-Mapping, sent on EC-RACH

EGPRS-Priority = ‘0’

EC-NumberOfBlocks = ‘01’

DL Coverage Class: a CC1 codepoint

4

SS

SS verifies that MS repeats the EC PACKET CHANNEL REQUEST transmission twice

5

SS

SS verifies than no more access is done for 5 s

Specific message contents:

41.8.1.2 EC-GSM-IoT / Packet Access / EC-GSM-IoT / RACH Access allowed / Packet Access on RACH

41.8.1.2.1 Conformance requirements

An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT attempts packet access by:

– transmitting an EC PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or

Reference

3GPP TS 44.018 subclause 3.10.1

RACH Access Control is a 1 bit field and is coded as follows:

0: A mobile station using CC1 in both the uplink and downlink shall not use timeslot 0

1: A mobile station using CC1 in both the uplink and downlink shall use timeslot 0

Reference

3GPP TS 44.018 subclause 9.1.30c.

41.8.1.2.2 Test purpose

To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message on RACH when RACH access is allowed and it is using CC1 in both downlink and uplink.

41.8.1.2.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported

RACH Access to be used:

– RACH Access allowed (CC1)

– CC1 used in the downlink

– CC1 used in the uplink

Mobile Station:

The MS is GPRS attached and in EC mode.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS determines CC1 is used in both uplink and downlink. The MS is triggered to send uplink data (Normal Report consisting of 2 MCS-1 coded RLC data blocks, neither NAS Signalling or Exception Report). The MS issues a EC PACKET CHANNEL REQUEST message on RACH. The SS verifies the EC PACKET CHANNEL REQUEST is received on RACH.

Maximum duration of the test

1 minute.

Expected sequence

Step

Direction

Message

Comments

1

SS

Access_Timeslots field sent in EC-SI2 = 0, RACH Access Control field in SCH set to ‘1’

2

MS

Trigger to UL data send data

3

MS -> SS

EC PACKET CHANNEL REQUEST

The MS sends EC PACKET CHANNEL REQUEST on RACH with:

TS3 or TS4 (depending on the MS 8PSK capability)

EC-NumberOfBlocks = ‘0 1 1’

EC Priority = ‘0’

Random Bits = 3 random bits

Signal Strength = any value according to the MS measurement

Specific message contents

41.8.1.3 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 1TS EC-RACH Mapping / CC1

41.8.1.3.1 Conformance requirements

The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a and sub-clause 9.1.65) as follows:

– Using the 1TS EC-RACH Mapping method if using CC1 on the uplink or if the Access Timeslots field sent in EC-SI2 = 0.

Reference

3GPP TS 44.018 subclause 3.5.2.5.2a.

41.8.1.3.2 Test purpose

To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 1TS EC-RACH Mapping when RACH access is not allowed though using CC1 in both downlink and uplink.

41.8.1.3.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported.

RACH Access not allowed (CC1)

4 DL coverage classes are indicated as supported

1TS EC-RACH Mapping to be used:

– Access Timeslots field in EC_SI2 set to ‘1’.

– CC1 used in the downlink

– CC1 used in the uplink

Mobile Station:

The MS is GPRS attached and in EC mode.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS determines CC1 in both uplink and downlink. The MS is triggered to send uplink data (Normal Report consisting of 2 MCS-1 coded RLC data blocks, neither NAS Signalling or Exception Report). The MS issues a EC PACKET CHANNEL REQUEST message using the 1TS EC-RACH mapping. The SS verifies the EC PACKET CHANNEL REQUEST received is using the 1TS EC-RACH mapping.

Maximum duration of the test

1 minute.

Expected sequence

Step

Direction

Message

Comments

1

MS

Trigger to send UL data

2

MS -> SS

EC PACKET CHANNEL REQUEST

The MS sends EC PACKET CHANNEL REQUEST on EC-RACH using 1TS Mapping with:

TS3 or TS4 (depending on the MS 8PSK capability)

EC-NumberOfBlocks = ‘0 1 1’

EC Priority = ‘0’

Random Bits = 3 random bits

Selected DL Coverage Class = any value in the range from ‘0 1 1’ to ‘1 1 1’ depending on the MS measurement

3

SS

SS verifies that the EC PACKET CHANNEL REQUEST message is received on EC-RACH, using 1TS Mapping, with the correct content (see above)

Specific message contents

41.8.1.4 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 1TS EC-RACH Mapping / Access Timeslots field = 0

41.8.1.4.1 Conformance requirements

The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC-EGPRS PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a.1 and sub-clause 9.1.65) as follows:

– Using the 1TS EC-RACH Mapping method if using CC1 on the uplink or if the Access Timeslots field sent in EC-SI2 = 0.

The mapping of the EC-RACH (EC-CCCH/U) is defined in table 6a of clause 7 and illustrated in figure 16 and figure 17, where the possible blocks are indicated for each uplink Coverage Class. Furthermore, two different EC-RACH mappings exist. The mapping to be used is signalled on cell level in EC SI, see 3GPP TS 44.018. The EC-RACH is either mapped onto a single TS, or over 2 consecutive TS for CC2, CC3 and CC4. CC1 EC-RACH is always mapped onto 1 TS.

Reference

3GPP TS 44.018 subclause 3.5.2.5.2a.

3GPP TS 45.002 subclause 6.3.4.3.

41.8.1.4.2 Test purpose

To verify that the GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 1TS EC-RACH Mapping when Access Timeslots field sent in EC-SI2 = 0.

41.8.1.4.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported.

RACH Access not allowed (CC1)

4 DL coverage classes are indicated as supported

1TS EC-RACH Mapping to be used:

– Access Timeslots field in EC_SI2 set to ‘0’

CC1 not used in the uplink

Cell power: -90dBm (to ensure uplink CC2)

Mobile Station:

The MS is GPRS attached and in EC mode.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS determines CC2, in UL. The MS is triggered to send uplink data (accessing the network for the purpose of NAS signalling low priority and is not sending an exception report). The MS issues an EC PACKET CHANNEL REQUEST message using the 1TS EC-RACH mapping. The SS verifies the EC PACKET CHANNEL REQUEST received is using the 1TS EC-RACH mapping.

Maximum duration of the test

1 minute.

Expected sequence

Step

Direction

Message

Comments

1

MS

Trigger to send UL data

2

MS -> SS

EC PACKET CHANNEL REQUEST

The MS sends EC PACKET CHANNEL REQUEST on EC-RACH using 1TS Mapping with:

TS5, TS6 or TS7 (depending whether the coverage class in uplink is CC2, CC3 or CC4, respectively)

EC-NumberOfBlocks = ‘0 1 1’

EC-EGPRS Priority = ‘0’

Random Bits = 3 random bits

Selected DL Coverage Class = any value depending on the MS measurement

3

SS

SS verifies that the EC PACKET CHANNEL REQUEST message is received on EC-RACH, using 1TS Mapping, with the correct content (see above)

Verified 4 identical bursts (CC2 Uplink), 0n TS1 on 4 consecutive frames

Specific message contents

41.8.1.5 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 2TS EC-RACH Mapping

41.8.1.5.1 Conformance requirements

The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a.1 and sub-clause 9.1.65) as follows:

– Using the 2TS EC-RACH Mapping method if using CC2, CC3 or CC4 on the uplink and the Access Timeslots field sent in EC-SI2 = 1.

– When the 2TS EC-RACH Mapping method is used the EC PACKET CHANNEL REQUEST messages sent across 2 timeslots on the EC-RACH shall be identical and shall use the same training sequence code (i.e. one of TS5, TS6 or TS7 is used according to the uplink CC).

Reference

3GPP TS 44.018 subclause 3.5.2.5.2a.

41.8.1.5.2 Test purpose

To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 2TS EC-RACH Mapping when using CC2 in uplink and when Access Timeslots field sent in EC-SI2 = 1.

41.8.1.5.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported.

RACH Access not allowed (CC1)

4 DL coverage classes are indicated as supported

2TS EC RACH Mapping to be used:

– Access Timeslots field in EC_SI2 set to ‘1’ (i.e. 2TS EC-RACH mapping).

– UL coverage as CC2.

Cell power: -90dBm (to ensure uplink CC2)

Mobile Station:

The MS is GPRS attached and in EC mode.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS determines CC2 in UL. The MS is triggered to send uplink data (accessing the network for the purpose of NAS signalling low priority and is not sending an exception report). The MS issues an EC PACKET CHANNEL REQUEST message using the 2TS EC-RACH mapping. The SS verifies the EC PACKET CHANNEL REQUEST messages received across 2 timeslots are identical and use the same TSC (according to the uplink CC).

Maximum duration of the test

1 minute.

Expected sequence

Step

Direction

Message

Comments

1

SS

Trigger to send UL data

2

MS -> SS

EC-EGPRS PACKET CHANNEL REQUEST

The MS sends EC PACKET CHANNEL REQUEST on EC-RACH using 2TS Mapping with:

TS5 (corresponding to CC2 in uplink)

EC-NumberOfBlocks = ‘0 1 0’

EC-EGPRS Priority = ‘0’

Random Bits = 3 random bits

Selected DL Coverage Class = any value depending on the MS measurement

3

SS

SS verifies that the EC PACKET CHANNEL REQUEST message is received on EC-RACH, using 2TS Mapping, same training sequence

Verify 2TS meaning

Verified 4 identical bursts (CC2 Uplink), TS 0 and TS1 on 2 consecutive frames

Specific message contents

41.8.1.6 EC-GSM-IoT / Packet Access / Implicit Reject

41.8.1.6.1 Conformance requirements

An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT operation may perform NAS signalling to negotiate the use of a power saving feature. An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT operation attempts packet access by:

– transmitting an EC PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or

– transmitting an EC PACKET CHANNEL REQUEST message using the 1TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a); or

– transmitting an EC PACKET CHANNEL REQUEST message using the 2TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a).

A mobile station that is accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008 [79]) and is not sending an exception report (see sub-clause 9.1.65), shall read the Implicit Reject Status (IRS) field, EC-BCCH CHANGE MARK field and RACH Access Control field sent in the EC-SCH INFORMATION message (see Figure 9.1.30c.1 and 3GPP TS 45.002) prior to accessing the network. If a change of EC-BCCH CHANGE MARK is detected it shall read one or more EC-SYSTEM INFORMATION messages as needed (see sub-clause3.10.4). The MS then proceeds as follows:

– If the IRS field indicates the access attempt is rejected the mobile station shall abort the packet access procedure and initiate the EC Implicit Reject procedure (see sub-clause 3.5.2a.2).

– If the IRS field indicates the access attempt is not rejected, the RACH Access Control field indicates that RACH usage on timeslot number 0 is not allowed it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a.

– If the IRS field indicates the access attempt is not rejected, the RACH Access Control field indicates that RACH usage on timeslot number 0 is allowed and the mobile station has selected CC1 in both uplink and downlink, see 3GPP TS 45.008 [34], it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2.

– If the IRS field indicates the access attempt is not rejected and the mobile station has selected CC2, CC3 or CC4 in the uplink and/or downlink (see 3GPP TS 45.008 [34]) then it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a.

The EC-GSM-IoT preliminary access barring check shall indicate network access is barred for a MS that has enabled EC operation if any of the following conditions are satisfied:

  • A MS that is a member of an Access Class in the range 0-9 is attempting to send a normal report (see sub-clause 9.1.65) and determines that the corresponding AC0 to AC9 bit in the EC_Access_Control_Class field sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell) is not authorized.
  • A MS that is a member of an Access Class in the range 0-9 is attempting to send an exception report (see sub-clause 9.1.65) and determines that the Exception_Report_Status field sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell) is not authorized.

A MS that is a member of one or more of a special Access Class in the range 11-15 is attempting to send a normal report or an exception report and determines the AC11 to AC15 bit in the EC_Access_Control_Class field corresponding to its special Access Class sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell) is not authorized. References

3GPP TS 44.018, subclauses 3.10.1, 3.5.2a and 3.5.2a.1

41.8.1.6.2 Test purpose

To verify that the EC-EGPRS capable mobile station, accessing the network for the purpose of NAS signalling low priority and is not sending an exception report, checks the Implicit Reject Status (IRS) field before attempting packet access.

41.8.1.6.3 Method of test

Initial Conditions

System Simulator:

1 cell, EC-GSM-IoT supported, MS is in GPRS attached state. Routing area T3312=6min.

Mobile Station:

The MS is configured for “NAS signalling low access priority” and is configured for one of Access Class 0 to 9.

Specific PICS Statements

PIXIT Statements

Test Procedure

The MS attached to the EC-GSM-IoT cell is expected to trigger a Periodic Routing Area Procedure.

At least 1min before the Periodic Timer expiry, the Implicit Reject Status on EC-SCH is set to 11 (all MS barred) in order to give the MS enough time to identify the barred status.

The SS then checks that the MS shall not access the network for the Periodic Routing Area procedure until the EC-SCH Implicit Reject Status is unbarred. The MS access is then expected for the duration of T3236.

Maximum Duration of Test

8 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

SS

EC-SCH updated with Implicit Reject Status set to: 11 (all MS are barred)

2

SS

Wait 1min to ensure barred.

3

MS

SS checks for 5 min (Periodic Routing Area Timer) that no access is done by the MS

4

SS

EC-SCH updated with Implicit Reject Status set to: 00 (No barring)

5

SS

EC-Packet channel request

SS verifies that the MS Periodic Routing area update is initiated by the MS.

Shall be sent within 200 seconds (maximum of T3236).

Specific Message Contents

41.8.1.7 EC-GSM-IoT / Packet Access / Legacy Implicit Reject

41.8.1.7.1 Conformance requirements

– transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or

An EC-EGPRS capable mobile station in a cell that supports EC-EGPRS attempts packet access by:

– transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the 1TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a); or

– transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the 2TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a)

A mobile station accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008), when attempting to establish a PS connection, shall, while ignoring MS identities included within PAGING REQUEST messages, start listening to the downlink CCCH until successfully decoding one of the RR messages listed in sub-clause 3.3.1.1.1a. A MS that has enabled PEO shall read the PEO_BCCH_CHANGE_MARK field within the successfully decoded RR message. If a change of PEO BCCH CHANGE MARK is detected it shall first read SI13 before proceeding with the packet access procedure. If the RR message indicates an implicit reject for the PS domain (see sub-clause 3.3.1.1.1a) the mobile station shall abort the packet access procedure and initiate the implicit reject procedure (see sub-clause 3.3.1.1.3.2a). An exception case is where the mobile station has enabled EC-EGPRS operation and is sending an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2a) in which case it proceeds with the packet access without first checking the status of the PEO_BCCH_CHANGE_MARK field or implicit reject information sent in an RR message.

A mobile station that has enabled EC-EGPRS operation and is accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008) and is not sending an exception report, shall examine the Implicit Reject Status (IRS) field, EC-EGPRS BCCH CHANGE MARK field and RACH Access Control field sent as part of the 25 bit EC-SCH payload space (see Figure 9.1.30c.1 and 3GPP TS 45.002). If a change of EC-EGPRS BCCH CHANGE MARK is detected it shall first read one or more EC-SI messages (see sub-clause3.10.4) and then proceed as follows:

– If the IRS field indicates the access attempt is rejected the mobile station shall abort the packet access procedure and initiate the EC-EGPRS Implicit Reject procedure (see sub-clause 3.5.2.1.6).

– If the access attempt is not rejected and the RACH Access Control field indicates that RACH usage is not allowed it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a.

– If the access attempt is not rejected, the RACH Access Control field indicates that RACH usage is allowed and the mobile station is in normal coverage (i.e. it uses CC1 for both the uplink and downlink) it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2.

The EC-EGPRS preliminary access barring check shall indicate network access is barred for a MS that has enabled EC-EGPRS operation if any of the following conditions are satisfied:

– A MS that is a member of an Access Class in the range 0-9 is attempting to send a normal report and determines that the Normal Access Barring field sent in EC-SI2 is not authorized.

– A MS that is a member of an Access Class in the range 0-9 is attempting to send an exception report and determines that the Exception Report Status field sent in EC-SI2 is not authorized.

– A MS that is a member of an Access Class in the range 0-9 and one or more of a special Access Class in the range 11-15 is attempting to send a normal report and determines the Special Access Barring field corresponding to its special Access Class sent in EC-SI2 is not authorized.

– A MS that is a member of an Access Class in the range 0-9 and one or more of a special Access Class in the range 11-15 is attempting to send an exception report and determines that the Special Access Barring field corresponding to its special Access Class is not authorized and the Exception Report Status field is not authorized.

References

3GPP TS 44.018, subclauses 3.10.1, 3.5.2, 3.5.2a and 3.5.2a.1

41.8.1.7.2 Test purpose

To verify that the EC-EGPRS capable mobile station, accessing the network for the purpose of NAS signalling low priority ignores the checks the Implicit Reject Status (IRS) field when sending an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH.

41.8.1.7.3 Method of test

Initial Conditions

System Simulator:

1 cell, EC-GSM-IoT supported, Implicit reject flag enabled and RACH Access Control = 1 in EC-SCH

Mobile Station:

The MS is configured for “NAS signalling low access priority”

The MS is GPRS attached and have acquired the EC-SI message

Specific PICS Statements

PIXIT Statements

Test Procedure

The MS, configured for low access priority, is triggered to initiate a “NAS signalling low priority” packet uplink data transfer on an EC-GSM-IoT capable Cell.

Before accessing the network, the MS reads the EC-SCH SYNCHRONIZATION CHANNEL INFORMATION, indicating that the Implicit Reject Status is set to 11 (all mobile stations barred) and that the RACH Access Control flag is set to 1.

The SS verifies that the MS ignore the Implicit Reject flag and send the EC PACKET CHANNEL REQUEST on RACH.

The MS transfers the NAS message to the SSMaximum Duration of Test

8 minutes.

Expected Sequence

Step

Direction

Message

Comments

2

MS

The MS is triggered to initiate “NAS signalling low priority” packet uplink data transfer

3

MS -> SS

EC PACKET CHANNEL REQUEST

Verify received on RACH

4

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 1

CC1 to be used

5

MS -> SS

UPLINK RLC DATA BLOCKS

Transporting: NAS message send with low priority indication

6

SS -> MS

EC PACKET UPLINK ACK/NACK

acknowledge the received RLC data block, Final Ack Indicator = ‘1’, a valid RRBP

7

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

acknowledge the RLC data

Specific Message Contents

41.8.2 EC-GSM-IoT / Paging

41.8.2.1 EC-GSM-IoT / Paging / normal paging

41.8.2.1.1 Conformance requirements

The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]). The MS shall not request the use of PSM during:

– an attach for emergency bearer services procedure;

– a routing area updating procedure for initiating a PDN connection for emergency bearer services; or

– a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.

The MS can request the use of extended idle mode DRX cycle (eDRX) during an attach or routing area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682 [11A] and 3GPP TS 23.060 [74]). The MS shall not request the use of eDRX during:

– an attach for emergency bearer services procedure;

– a routing area updating procedure for initiating a PDN connection for emergency bearer services; or

– a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.

The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannels on EC-CCCH corresponding to the paging groups determined for it in packet idle mode, as specified in 3GPP TS 45.002. The messages sent on EC-CCCH may contain an EC-GSM-IoT Page Extension field.

The network initiates the paging procedure by sending an EC-PAGING REQUEST message on an appropriate paging subchannel on EC-CCCH. Paging initiation using a paging subchannel on EC-CCCH is used when sending paging information to a mobile station that has enabled EC-EGPRS operation.

A mobile station that has enabled EC operation in a cell that supports EC-GSM-IoT that wants to use eDRX selects an eDRX cycle value from the set of available eDRX cycles (see 3GPP TS 45.002 [32]) and indicates it as its preferred eDRX cycle length when registering with the network (see 3GPP TS 24.008 [79]). The mobile station selects a nominal paging group on the EC-PCH of its selected EC-CCCH (see 3GPP TS 45.002 [32]) using IMSI, its negotiated eDRX cycle and its estimated downlink coverage class and monitors pages thereon (see 3GPP TS 45.002 [32]). A mobile station that has enabled EC operation but has not negotiated the use of PSM or eDRX shall support paging based reachability using the lowest eDRX cycle when the Ready timer is running.

….

A mobile station that has enabled EC operation where eDRX is used wakes up to read its nominal paging group according to its negotiated eDRX cycle (see 3GPP TS 45.002) when in Idle mode and the Ready timer is not running or supports reachability while the Ready timer is running using the lowest eDRX. If it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, if it receives any other message and the EC-EGPRS Page Extension field is included therein (sub-clause 9.1.60), it shall proceed as follows:

A MS that has enabled EC operation where PSM with eDRX is used supports reachability while in packet idle mode when the Ready timer or Active timer is running as described in sub-clause 3.9.2 for the case of a mobile station that uses PEO with PSM and eDRX A MS that has enabled EC operation where PSM without eDRX is used supports reachability while the Active timer is running using the lowest eDRX cycle.

References

3GPP TS 24.008, subclauses 4.7.2.9 and 4.7.2.10

3GPP TS 44.018, subclauses 3.5.1a, 3.5.1a.1, 3.5.2.1.2, 3.10.1, 3.10.2

3GPP TS 45.002, subclause 6.5.6a.

41.8.2.1.2 Test purpose

1. To verify that the mobile station in packet idle mode can receive and analyse the paging messages sent on the paging subchannels on EC-CCCH

2. To verify that the mobile station can activate both PSM and eDRX when in EC operation.

3. To verify that the mobile station that has enabled EC operation with both PSM and eDRX is reachable with the eDRX cycle negotiated during the PSM active timer

41.8.2.1.3 Method of test

Initial Conditions

System Simulator:

– 1 cell, EC-GSM-IoT, PSM and eDRX supported

Mobile Station:

– The MS is switched off.

Specific PICS Statements

PIXIT Statements

Test Procedure

The MS is triggered to initiate the GPRS attach procedure on an EC-GSM-IoT capable Cell but does not include eDRX or PSM related parameters in the GPRS Attach Request. The SS checks that the MS does not indicate any value for eDRX.

Once the device is GPRS attached, in packet idle mode with Ready Timer expired the SS pages the MS according to the lowest eDRX cycle. There should be no answer from the MS as the MS has not negotiated the use of an eDRX cycle (i.e. the MS is unreachable when the neither the Ready timer nor Active timer is running).

The MS is then paged according to the lowest eDRX cycle and should answer the Paging Request. The Paging request contains the EC-GSM-IoT Page Extension IE set to CC1. The SS reject the MS access.

The MS is then paged according to the second lowest eDRX cycle and should answer the Paging Request.

Expected Sequence

Step

Direction

Message

Comments

1

MS

The MS is turned on and triggered to initiate the GPRS attach procedure

2

MS -> SS

EC PACKET CHANNEL REQUEST

DL Coverage Class: CC1

3

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

Request Reference = pertaining to the message received in step 2. Fixed link assignment, sent on EC-AGCH

4

MS -> SS

UPLINK RLC DATA BLOCKS

Transporting: ATTACH REQUEST

5

SS -> MS

EC PACKET UPLINK ACK/NACK

acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. Sent on EC-PACCH

6

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

acknowledge the RLC data. Received on EC-PACCH

7

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

For downlink TBF, sent 1 s. after step 6 on EC-AGCH

8

SS -> MS

DOWNLINK RLC DATA BLOCKS

Transporting:

ATTACH ACCEPT.

Last block containing a valid RRBP field and FBI set.

9

MS -> SS

EC PACKET DOWNLINK ACK/NACK

Not including Channel Request Description

10

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH

11

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

Request Reference = pertaining to the message received in step 10. Fixed link assignment, sent on EC-AGCH

11

MS -> SS

UPLINK RLC DATA BLOCKS

Transporting:

ATTACH COMPLETE

12

SS -> MS

PACKET UPLINK ACK/NACK

Including valid RRBP field

13

MS -> SS

PACKET CONTROL ACKNOWLEDGMENT

14

Wait for 1 minute for Ready Timer to expire

15

SS -> MS

EC PAGING REQUEST

Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the second lowest eDRX cycle

16

There Should be no response from MS as the eDRX Cycle is set to the lowest eDRX cycle. This is verified for the duration of T3315

17

SS -> MS

EC PAGING REQUEST

Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the lowest eDRX cycle

Including the EC-EGPRS Page Extension IE set to ‘1 X X X’

18

MS -> SS

EC PACKET CHANNEL REQUEST

received on EC-RACH

19

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 18.

Sent on EC-AGCH.

20

SS -> MS

EC PAGING REQUEST

Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the second lowest eDRX cycle

21

MS -> SS

EC PACKET CHANNEL REQUEST

received on EC-RACH

Specific Message Contents

41.8.2.2 EC-GSM-IoT / Paging / normal paging / with eDRX or eDRX and PSM

41.8.2.2.1 Conformance requirements

The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]). The MS shall not request the use of PSM during:

– an attach for emergency bearer services procedure;

– a routing area updating procedure for initiating a PDN connection for emergency bearer services; or

– a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.

The MS can request the use of extended idle mode DRX cycle (eDRX) during an attach or routing area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682 [11A] and 3GPP TS 23.060 [74]). The MS shall not request the use of eDRX during:

– an attach for emergency bearer services procedure;

– a routing area updating procedure for initiating a PDN connection for emergency bearer services; or

– a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.

The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannels on EC-CCCH corresponding to the paging groups determined for it in packet idle mode, as specified in 3GPP TS 45.002. The messages sent on EC-CCCH may contain an EC-EGPRS Page Extension field.

The network initiates the paging procedure by sending an EC PAGING REQUEST message on an appropriate paging subchannel on EC-CCCH. Paging initiation using a paging subchannel on EC-CCCH is used when sending paging information to a mobile station that has enabled EC-GSM-IoT operation.

An EC-GSM-IoT capable mobile station that has enabled EC operation in a cell that supports EC-EGPRS that wants to use eDRX selects an eDRX cycle value from the set of available eDRX cycles (see 3GPP TS 45.002 [32]) and indicates it as its preferred eDRX cycle length when registering with the network (see 3GPP TS 24.008 [79]). The mobile station selects a nominal paging group on the EC-PCH of its selected EC-CCCH (see 3GPP TS 45.002 [32]) using IMSI, its negotiated eDRX cycle and its estimated downlink coverage class and monitors pages thereon (see 3GPP TS 45.002 [32]). A mobile station that has enabled EC operation but has not negotiated the use of PSM or eDRX shall support paging based reachability using the lowest eDRX cycle.

….

A mobile station that has enabled EC operation where eDRX is used wakes up to read its nominal paging group according to its negotiated eDRX cycle (see 3GPP TS 45.002) or the lowest eDRX cycle if it has not negotiated the use of PSM or eDRX. If it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, if it receives any other message and the EC-EGPRS Page Extension field is included therein (sub-clause 9.1.60), it shall proceed as follows:

A MS that has enabled EC operation where PSM with eDRX is used supports reachability while in packet idle mode when the Ready timer or Active timer is running as described in sub-clause 3.9.2 for the case of a mobile station that uses PEO with PSM and eDRX except that the MS always uses the lowest eDRX cycle when the Ready timer is running.

References

3GPP TS 24.008, subclauses 4.7.2.9 and 4.7.2.10

3GPP TS 44.018, subclauses 3.5.1a, 3.5.1a.1, 3.5.2.1.2, 3.10.1, 3.10.2

3GPP TS 45.002, subclause 6.5.6a.

41.8.2.1.2 Test purpose

1. To verify that the mobile station in packet idle mode can receive and analyse the paging messages sent on the paging subchannels on EC-CCCH

2. To verify that the mobile station can activate both PSM and eDRX when in EC operation.

3. To verify that the mobile station that has enabled EC operation with both PSM and eDRX is reachable with the eDRX cycle negotiated during the PSM active timer.

41.8.2.2.3 Method of test

Initial Conditions

System Simulator:

– 1 cell, EC-GSM-IoT, PSM and eDRX supported

Mobile Station:

– The MS is switched off.

Specific PICS Statements

  • Support of PSM (TSPC_PSM)

PIXIT Statements

Test Procedure

The MS is triggered to initiate the GPRS attach procedure on an EC-GSM-IoT (eDRX & PSM) capable Cell. The MS send either eDRX only or both PSM and eDRX values in the ATTACH REQUEST.

Either eDRX or both PSM and eDRX values are sent by the SS, depending on what the MS sent in the ATTACH REQUEST, as well as the DL CC received by the SS during the GPRS attach procedure (i.e. EC operation is enabled). The eDRX value shall not be the lowest eDRX value but shall be selected so that only one eDRX cycle fits within the time period determined by the Active timer (T3324).

Once the device is GPRS attached, in packet idle mode with Ready Timer expired the SS pages the MS according to the lowest eDRX cycle. There should be no answer from the MS as the eDRX cycle negotiated is higher.

The MS is then paged according to its negotiated eDRX cycle and should answer the Paging Request. The SS reject the MS access.

When the T3324 timer expire the MS is paged according to its negotiated eDRX cycle. If the MS indicated that PSM is supported there should be no answer from the MS.

Maximum Duration of Test

13 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

MS

The MS is turned on and triggered to initiate the GPRS attach procedure

2

MS -> SS

EC PACKET CHANNEL REQUEST

DL Coverage Class: CC1

3

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

Request Reference = pertaining to the message received in step 2. Fixed link assignment, sent on EC-AGCH

4

If the MS only supports eDRX, step 4a shall be performed.

If the MS supports both eDRX and PSM, step 4b shall be performed

4a

MS -> SS

UPLINK RLC DATA BLOCKS

Transporting: ATTACH REQUEST

It is Verified that eDRX IE is included

4b

MS -> SS

UPLINK RLC DATA BLOCKS

Transporting: ATTACH REQUEST

It is Verified that eDRX and T3324 IE are included.

5

SS -> MS

EC PACKET UPLINK ACK/NACK

acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. Sent on EC-PACCH

6

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

acknowledge the RLC data. Received on EC-PACCH

7

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

For downlink TBF, sent 1 s. after step 6 on EC-AGCH

8

SS -> MS

DOWNLINK RLC DATA BLOCKS

Transporting:

ATTACH ACCEPT.

Including the Extended DRX value and T3324 Value set to:

eDRX Value: 0111 (3.25 min)

T3324 Value (PSM): 8 minutes

Last block containing a valid RRBP field and FBI set.

9

MS -> SS

EC PACKET DOWNLINK ACK/NACK

Not including Channel Request Description

10

MS -> SS

EC PACKET CHANNEL REQUEST

TS3 or TS4, received on EC-RACH

11

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

Request Reference = pertaining to the message received in step 10. Fixed link assignment, sent on EC-AGCH

11

MS -> SS

UPLINK RLC DATA BLOCKS

Transporting:

ATTACH COMPLETE

12

SS -> MS

PACKET UPLINK ACK/NACK

Including valid RRBP field

13

MS -> SS

PACKET CONTROL ACKNOWLEDGMENT

14

Wait for 1 minute for Ready Timer to expire

15

SS -> MS

EC PAGING REQUEST

Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the lowest eDRX cycle

16

There Should be no response from MS as the eDRX Cycle is now set to eDRX Value: 0111. This is verified for the duration of T3315

17

SS -> MS

EC PAGING REQUEST

Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the negotiated eDRX cycle

18

MS -> SS

EC PACKET CHANNEL REQUEST

received on EC-RACH

19

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 18.

Sent on EC-AGCH.

20

SS -> MS

EC PAGING REQUEST

Sent on EC-PCH according to the negotiated eDRX cycle, on the next paging occasion after T3324 expiry

21

If the MS only supports eDRX, step 21a shall be performed.

If the MS supports both eDRX and PSM, step 21b shall be performed

21a

MS -> SS

EC PACKET CHANNEL REQUEST

received on EC-RACH

21b

There should be no response from MS, as it shall have entered PSM mode. This is verified for the duration of T3315

Specific Message Contents

41.8.3

41.8.4 EC-GSM-IoT / Coverage Class

41.8.4.0 EC-GSM-IoT / Coverage Class / Default Conditions

All default conditions, message contents and macros are defined in section 40, except for the parameters as described in this subclause. These parameters are applicable to the whole section 41.8, they shall be transmitted by the system simulator and are required to be received by the MS under test.

By default, DL_CC_Selection is set to RLA_EC based coverage class selection unless otherwise stated.

For RLA_EC based coverage class selection, the RxLev of the serving cell is adjusted in relation to EC_RXLEV_ACCESS_MIN, BT_Threshold_DL and CCx_Range_DL in order to select the expected coverage class.

For SLA based coverage class selection (tests 41.8.4.4 and 41.8.4.6), as per TS 45.008 subclause 6.9.4, the following radio conditions are used for test purposes:

BT_Threshold_DL = 18 (8 dB), CC2_Range_DL = 5 (6 dB), CC3_Range_DL = 5 (6 dB). Serving GSM cell at RXLEV= -70 dBm with two non-serving cells at -84 dBm, at -78 dBm, at -72 dBm, and at -66 dBm, for the MS to select CC1, CC2, CC3 and CC4, respectively.

41.8.4.1 EC-GSM-IoT / Coverage Class / Paging Extension

41.8.4.1.1 Conformance requirement

A mobile station that has enabled EC operation and has successfully negotiated eDRXdeterminess its nominal paging group as defined for EC operation (see 3GPP TS 45.002) according to its negotiated eDRX cycle and selected downlink coverage class . A mobile station that has enabled EC operation but has not negotiated eDRX determines its nominal paging group as defined for EC operation according to the lowest eDRX cycle, its IMSI and its selected downlink CC (see 3GPP TS 45.002). If it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, if it receives any other message on the EC-PCH and the EC Page Extension field is included therein it shall proceed as follows:

– If the EC Page Extension field indicates paging extension is enabled for its downlink coverage class it shall attempt to read one additional paging message using a paging group determined according to its coverage class as shown in Table 3.5.1a.1.

– If it finds a matching paging message therein it shall act on that message as described in sub-clause 3.5.1.2.

– If paging extension is not enabled or it does not find a matching paging message when attempting to read one additional paging message it sets its eDRX cycle to the negotiated eDRX cycle, remains in packet idle mode and waits for the next instance of its nominal paging group.

– A mobile station that has enabled EC operation and has successfully negotiated eDRX shall, upon re-selecting to a cell in the same Routing Area that does not support EC operation, determine its nominal paging group as defined for PEO (see 3GPP TS 45.002 [32]) using its negotiated eDRX cycle length.

Table 3.5.1a.1: Page Extension Using Fixed Offset

Downlink Coverage Class of Ongoing Transmission

CC1

CC2

CC3

CC4

Downlink CC of MS Requiring Page Extension

CC1

PG1 + 2

PG1 + 4

PG1 + 8

PG1 + 8

CC2

PG1 + 4

PG1 + 4

PG1 + (2 or 6)2

CC3

PG1 + 2

PG1 + (1 or 3)3

CC4

PG1 + 2

Note 1: PG (Paging Group) represents the start of the coverage class specific EC-PCH block corresponding to the nominal paging group of an MS (see 3GPP TS 45.002 [32]). The start of the coverage class specific EC-PCH block used for page extension is expressed as an offset relative to PG (where the value of the offset indicates the number of coverage class specific EC-PCH blocks comprising the offset).

Note 2: Page Extension is determined using PG + 2 when a CC2 MS reading its nominal paging group in TDMA frames 35 to 42 (CC2 B2) or in TDMA frames 43 to 50 (CC2 B3) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 35 to 50 in MF N/N+1/N+2/N+3. Page Extension is determined using Paging Group PG + 6 when a CC2 MS reading its nominal paging group in TDMA frames 19 to 26 (CC2 B0) or in TDMA frames 27 to 34 (CC2 B1) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 19 to 34 in MF N/N+1/N+2/N+3.

Note 3: Page Extension is determined using Paging Group PG + 1 when a CC3 MS reading its nominal paging group in TDMA frames 35 to 50 (CC3 B1) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 35 to 50 in MF N/N+1/N+2/N+3. Page Extension is determined using Paging Group PG + 3 when a CC3 MS reading its nominal paging group in TDMA frames 19 to 34 (CC3 B0) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 19 to 34 in MF N/N+1/N+2/N+3.

Reference

3GPP TS 44.018 subclause 3.5.1a.1

41.8.4.1.2 Test purpose

To verify that in EC operation, an MS will correctly consider the EC Paging extension field acquired when reading a message sent within its nominal paging group:

– If the EC Page Extension field indicates paging extension is enabled for its downlink coverage class, one additional paging group shall be considered,

– If the EC Page Extension field indicates paging extension is enabled for another downlink coverage class than the MS Coverage class, no additional paging group is considered by the MS.

41.8.4.1.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported

DL_CC_Selection = 0 (RLA_EC based coverage class selection)

BT_Threshold_DL = 0 (-87 dBm)

BT_Threshold_UL = 20 (-110 dBm)

CC2_Range_DL = CC3_Range_DL = 5 (6 dB)

Mobile Station:

The MS is GPRS attached in packet idle mode. eDRX cycle negotiated to 0100 (~ 24.5 sec)

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

An immediate assignment, not addressing the MS, is sent on the MS paging group with the EC Page Extension field enabled for the selected DL Coverage class of the MS. The MS is then paged on the fixed offset paging block according to its selected DL coverage class and shall answer the paging.

At the next paging occurrence, a new Paging request not addressing the MS is sent with the EC Page Extension field enabled for a coverage class different than the MS one. The SS verified that it is not taken into account by the MS with a new Paging request addressing the MS on the fixed offset paging block according to its selected DL coverage class,.

The procedure is repeated for all the DL coverage class (k= 1 to 4).

Maximum duration of the test

Expected sequence

The test sequence is repeated for k = 1 … 4.

Step

Direction

Message

Comments

1

SS

The test is run with the following kx configurations:

k=1: -80 dBm, RxLev of the serving cell to ensure CC1 as DL coverage class

k=2: -90 dBm, RxLev of the serving cell to ensure CC2 as DL coverage class

k=3: -96, dBm RxLev of the serving cell to ensure CC3 as DL coverage class

k=4: -102 dBm RxLev of the serving cell to ensure CC4 as DL coverage class

2

MS

The MS is attached on Cell A

3

SS -> MS

EC IMMEDIATE ASSIGNMENT Type 2

On the MS paging group but not addressing the MS

EC Page Extension set to the MS Coverage class according to k configuration defined in Step 1

3a

SS -> MS

EC PAGING REQUEST

Sent on the additional EC-PCH block, according to Table 3.5.1a.1 of TS 44.018 (i.e. PG1 + 2 for CC1 / CC3 and CC4, and PG1 + 4 for CC2)

4

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

DL Coverage class indicated by the MS shall match k configuration.

5

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 4.

Sent on EC-AGCH.

6

SS -> MS

EC PAGING REQUEST

Sent on next EC-PCH according to the negotiated eDRX cycle (i.e. ~ 24.5 seconds after step 3) but not addressing the MS

EC Page Extension set to a different coverage class than the MS Coverage class according to k configuration defined in Step 1

6a

SS -> MS

EC PAGING REQUEST

Sent on the additional EC-PCH block, addressing the MS, according to Table 3.5.1a.1 of TS 44.018 (i.e. PG1 + 2 for CC1 / CC3 and CC4, and PG1 + 4 for CC2)

7

SS

SS checks that no response form the MS is sent.

8

SS -> MS

EC PAGING REQUEST

Sent on next EC-PCH according to the negotiated eDRX cycle (i.e. ~ 24.5 seconds after step 6)

9

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

Coverage class indicated by the MS shall match k configuration.

Specific message contents:

41.8.4.2 EC-GSM-IoT / Coverage Class / UL Coverage Class selection

41.8.4.2.1 Conformance requirement

The MS shall select the uplink CC to use on (EC-)RACH according to table 6.10.3-1, based on the uplink received signal strength, estimated as

BS_RX_PWR = RLA_EC + min(MSPWR, MS_TXPWR_MAX_CCH) – BSPWR.

MSPWR is the nominal maximum output power of the MS. MS_TXPWR_MAX_CCH is the maximum TX power level an MS is allowed to use when accessing the system. BSPWR is the output power of the BTS used on FCCH and EC-SCH. MS_TXPWR_MAX_CCH and BSPWR are broadcast in EC SI 2 (see 3GPP TS 44.018 [17]).

Table 6.10.3-1: Uplink CC selection

Uplink CC

Upper limit of BS_RX_PWR

Lower limit of BS_RX_PWR

1

BT_Threshold_UL

2

BT_Threshold_UL

BT_Threshold_UL +

CC2_Range_UL

3

BT_Threshold_UL +

CC2_Range_UL

BT_Threshold_UL +

CC2_Range_UL +

CC3_Range_UL

4

BT_Threshold_UL +

CC2_Range_UL +

CC3_Range_UL

(see note)

NOTE: There is no explicit lower limit for selection of uplink CC4 but the C1 criterion (see subclause 6.4.1) will trigger a cell re-selection.

BT_Threshold_UL indicates the BS_RX_PWR (in dBm) below which blind physical layer transmissions are used on EC-RACH. CC2_Range_UL and CC3_Range_UL indicate the BS_RX_PWR range (in dB) of uplink CC 2 and 3, respectively. BT_Threshold_UL is broadcast in EC SI 2 while CC2_Range_UL and CC3_Range_UL are optionally broadcast in EC SI 2 (see 3GPP TS 44.018 [17]). If either of CC2_Range_UL and CC3_Range_UL is not present, its value shall be set to 0 and the corresponding uplink CC not used. If BS_RX_PWR is on the limit between two CC, the MS shall select the higher CC.

Reference

3GPP TS 45.008 subclause 6.10.3

This message may be sent by an EC capable mobile station attempting system access using the EC-RACH (see sub-clause 3.5.2.1.2a) in which the message format is as shown in Tables 9.1.65.1 and 9.1.65.2.

Table 9.1.65.1: EC PACKET CHANNEL REQUEST message content (EC-RACH)

Training sequence (see 3GPP TS 45.002)

bits
11……1

Packet Channel Access

TS3

< EC PACKET CHANNEL REQUEST message content >

Uplink CC1 MS – GMSK and 8PSK capability in uplink and downlink

TS4

< EC PACKET CHANNEL REQUEST message content >

Uplink CC1 MS – Only GMSK capability in uplink and downlink

TS5

< EC PACKET CHANNEL REQUEST message content >

Uplink CC2 MS

TS6

< EC PACKET CHANNEL REQUEST message content >

Uplink CC3 MS

TS7

< EC PACKET CHANNEL REQUEST message content >

Uplink CC4 MS

Reference

3GPP TS 44.008 9.1.65

41.8.4.2.2 Test purpose

To verify that an MS making an EC packet channel request will select the uplink CC to use on (EC-)RACH based on the uplink received signal strength, and the associated parameters.

41.8.4.2.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported

RLA_EC based coverage class selection.

BT_Threshold_UL = 0 (-90 dBm)

BT_Threshold_DL = 18 (-105 dBm)

CC2_Range_UL = CC3_Range_UL = 3 (4 dB)

Access_Timeslots = 0 to use 1TS EC_RACH Mapping

EC_Max_Retrans = 0 (1 retransmission)

CC_Access_Adaptation = 0

Mobile Station:

The MS is off.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS is turned on with the cell at different power level. The EC-RACH access should be done according to the estimated Uplink Coverage Class.

The procedure is repeated for all the UL coverage class (k= 1 to 4).

Maximum duration of the test

Expected sequence

The test sequence is repeated for k = 1 … 4.

Step

Direction

Message

Comments

1

SS

The test is run with the following kx configurations:

k=1: -80 dBm RxLev of the serving cell to ensure CC1 as UL coverage class

k=2: -92 dBm RxLev of the serving cell to ensure CC2 as UL coverage class

k=3: -96 dBm RxLev of the serving cell to ensure CC3 as UL coverage class

k=4: -101 dBm RxLev of the serving cell to ensure CC4 as UL coverage class (not lower than -105 dBm)

2

MS

The MS is powered on

3

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

UL coverage class (i.e. Training Sequence used) indicated by the MS shall match kx configuration.

Selected DL coverage Class shall be CC1

4

SS

It is verified that the EC PACKET CHANNEL REQUESTED is properly repeated for the blind repetition cases k=2, 3 or 4 (i.e. UL CC > CC1) according to TS 45.002

5

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH. Sent as EC_Max_Retrans=0

UL coverage class (i.e. Training Sequence used) indicated by the MS shall match kx configuration.

DL coverage Class shall be CC1

6

SS

It is verified that the EC PACKET CHANNEL REQUESTED is properly repeated for the blind repetition cases k=2, 3 or 4 (i.e. UL CC > CC1) according to TS 45.002

7

SS

Check for 10 sec that no more EC-RACH access are done

Specific message contents:

41.8.4.3 EC-GSM-IoT / Coverage Class / DL Coverage Class selection / RLA_EC

41.8.4.3.1 Conformance requirement

The MS shall select the downlink CC based on either RLA_EC or SLA, as indicated by the DL_CC_Selection parameter sent in EC SI 2 (see 3GPP TS 44.018 [17]), according to table 6.10.2-1 and indicate it to the network in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]). The network shall apply the indicated downlink CC on EC-AGCH.

Table 6.10.2-1: Downlink CC selection

Downlink CC

Upper limit of RLA_EC or SLA

Lower limit of RLA_EC or SLA

CC1

BT_Threshold_DL

CC2

BT_Threshold_DL

BT_Threshold_DL –

CC2_Range_DL

CC3

BT_Threshold_DL –

CC2_Range_DL

BT_Threshold_DL –

CC2_Range_DL –

CC3_Range_DL

CC4

BT_Threshold_DL –

CC2_Range_DL –

CC3_Range_DL

(see note)

NOTE: There is no explicit lower limit for selection of downlink CC4 but the C1 criterion (see subclause 6.4.1) will trigger a cell re-selection if RLA_EC ≤ EC_RXLEV_ACCESS_MIN + Max(MS_TXPWR_MAX_CCH – MSPWR,0), which implicitly sets a lower limit if CC selection is based on RLA_EC.

BT_Threshold_DL indicates the RLA_EC (in dBm) or SLA (in dB) below which blind physical layer transmissions are used on EC-AGCH. CC2_Range_DL and CC3_Range_DL indicate the RLA_EC range (in dB) of downlink CC2 and CC3, respectively.

BT_Threshold_DL and EC_RXLEV_ACCESS_MIN are broadcast in EC SI 2 (see 3GPP TS 44.018 [17]).

CC2_Range_DL and CC3_Range_DL are optionally broadcast in EC SI 2. If either of CC2_Range_DL and CC3_Range_DL is not broadcast, its value shall be set to 0 and the corresponding downlink CC is not supported by the network.

If RLA_EC or SLA (whichever is applicable) is on the limit between two CC, the MS shall select the higher CC.

In case downlink CC1 is selected, the MS shall further indicate in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]) the margin of the measured RLA_EC (or SLA) relative to BT_Threshold_DL. The parameter DL_Signal_Strength_Step_Size broadcast in EC SI 2 (see 3GPP TS 44.018 [17]) is used to quantize the margin to report in the EC Packet Channel Request message. The maximum margin that can be reported is dependent on the number of Coverage Classes supported in the cell, and whether or not the access is initiated on RACH or EC-RACH, see 3GPP TS 44.018 [17].

NOTE: When TX diversity (antenna hopping) is active a MS may underestimate RLA_EC. This can be compensated for by the NW in an adjustment of the BT_Threshold_DL.

Reference

3GPP TS 45.008 subclause 6.10.2

[…]

Table 3.5.2.1.2a.2: Values of parameters Scc and Tcc

Scc

Tcc

CC1

Sm

Tm

CC2

Sm

Tm

CC3

2*Sm

2*Tm

CC4

4*Sm

2*(Tm+1)

The value for Sm is sent in the EC SYSTEM INFORMATION TYPE 2 message and is used for determining the Scc value applicable for monitoring the EC-AGCH according to the selected downlink coverage class of the mobile station

[…]

After sending the first EC PACKET CHANNEL REQUEST message or a subsequent retransmission, the mobile station shall start reading the EC-AGCH (according to the downlink coverage class indicated within the corresponding EC PACKET CHANNEL REQUEST message) in an attempt to find a response matching its last transmission.

– A MS that has selected downlink CC1 shall begin looking for a matching response starting within downlink 51-multiframe N (i.e. N = TDMA FN div 51) if it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message and there is at least one remaining valid CC1 reception opportunity in downlink 51-multiframe N. If a matching response is not found or there are no remaining valid CC1 reception opportunities within downlink 51-multiframe N it shall start reading 51-multiframe N+1in an attempt to find a matching response. The total number of downlink 51-multiframes it reads (excluding downlink 51-multiframe N) in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).

– A MS that has selected downlink CC2 shall begin looking for a matching response starting within downlink 51-multiframe N if it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message, N mod 2 = 0 and there is at least one remaining valid CC2 reception opportunity that starts in downlink 51-multiframe N. If a matching response is not found using downlink 51-multiframes N and N+1 or there are no remaining valid CC2 reception opportunities that start within downlink 51-multiframe N it shall start reading downlink 51-multiframe N+1 (respectively N+2) if N mod 2 = 1 (respectively N mod 2 = 0). The total number of downlink 51-multiframes it reads (excluding downlink 51-multiframe N) in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).

– A MS that has selected downlink CC3 shall begin looking for a matching response starting with downlink 51-multiframe N+1 (respectively N+2) when it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message where N mod 2 = 1 (respectively N mod 2 = 0). The total number of downlink 51-multiframes it reads in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).

– A MS that has selected downlink CC4 shall begin looking for a matching response starting with downlink 51-multiframe N+1 (respectively N+2, N+3, N+4) when it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message where N mod 4 = 3 (respectively N mod 4 = 2, 1, 0). The total number of downlink 51-multiframes it reads in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).

Reference

– 3GPP TS 44.018 subclause 3.5.2.1.2a

41.8.4.3.2 Test purpose

To verify that an MS make an EC operation access request shall select the downlink CC to use on EC-RACH, based on the downlink received signal strength and the associated parameters if the DL_CC_Selection indicates the RLA_EC based method.

41.8.4.3.3 Method of test

Initial conditions

System Simulator:

1 Serving cell, EC-GSM-IoT supported

DL_CC_Selection = 0 (RLA_EC based coverage class selection)

BT_Threshold_DL = 0 (-87 dBm)

BT_Threshold_UL = 20 (-110 dBm)

CC2_Range_DL = CC3_Range_DL = 3 (4 dB)

Access_Timeslots = 0 to use 1TS EC_RACH Mapping

EC_Max_Retrans = 0 (1 retransmission)

DL_Signal_Strength_Step_Size = 0 (2dB)

Mobile Station:

The MS is off.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS is turned on with the cell at different power level. The EC-RACH access should indicate the proper DL coverage class or the proper margin if CC1 is indicated.

The Assignment message sent, once only, randomly on one of the EC-AGCH blocks according to the requested DL Coverage Class. The reception level being good enough for a one time only decoding, without blind physical layer transmissions, the MS shall then continue its GPRS attach procedure.

The procedure is repeated for all the DL coverage class. (k= 1 to 5).

Maximum duration of the test

Expected sequence

The test sequence is repeated for k = 1 … 5.

Step

Direction

Message

Comments

1

SS

The test is run with the following kx configurations:

k=1: -70 dBm RxLev of the serving cell to ensure CC1 as DL coverage class

k=2: -80 dBm RxLev of the serving cell to ensure CC1 as DL coverage class

k=3: -89 dBm RxLev of the serving cell to ensure CC2 as DL coverage class

k=4: -93 dBm RxLev of the serving cell to ensure CC3 as DL coverage class

k=5: -100 dBm RxLev of the serving cell to ensure CC4 as DL coverage class (not lower than -105 dBm)

2

MS

The MS is powered on

3

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1

Selected DL coverage Class shall be set according to k configuration

For k=1 and 2, two different margins, at least 2 steps apart shall be reported

For k= 3 to 5, CC2, CC3 and CC4 shall be reported respectively

4

SS -> MS

EC IMMEDIATE ASSIGNMENT Type 2

Sent on EC-AGCH, once only, randomly on one of the blocks scheduled for the initial transmission or a potential blind repetition

5

MS -> SS

UPLINK RLC DATA BLOCKS

Transporting: ATTACH REQUEST

Specific message contents:

41.8.4.4 EC-GSM-IoT / Coverage Class / DL Coverage Class selection / SLA

41.8.4.4.1 Conformance requirement

The MS shall select the downlink CC based on either RLA_EC or SLA, as indicated by the DL_CC_Selection parameter sent in EC SI 2 (see 3GPP TS 44.018 [17]), according to table 6.10.2-1 and indicate it to the network in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]). The network shall apply the indicated downlink CC on EC-AGCH.

Table 6.10.2-1: Downlink CC selection

Downlink CC

Upper limit of RLA_EC or SLA

Lower limit of RLA_EC or SLA

CC1

BT_Threshold_DL

CC2

BT_Threshold_DL

BT_Threshold_DL –

CC2_Range_DL

CC3

BT_Threshold_DL –

CC2_Range_DL

BT_Threshold_DL –

CC2_Range_DL –

CC3_Range_DL

CC4

BT_Threshold_DL –

CC2_Range_DL –

CC3_Range_DL

– (see note)

NOTE: There is no explicit lower limit for selection of downlink CC4 but the C1 criterion (see subclause 6.4.1) will trigger a cell re-selection if RLA_EC ≤ EC_RXLEV_ACCESS_MIN + Max(MS_TXPWR_MAX_CCH – MSPWR,0), which implicitly sets a lower limit if CC selection is based on RLA_EC.

BT_Threshold_DL indicates the RLA_EC (in dBm) or SLA (in dB) below which blind physical layer transmissions are used on EC-AGCH. CC2_Range_DL and CC3_Range_DL indicate the RLA_EC range (in dB) of downlink CC2 and CC3, respectively.

BT_Threshold_DL and EC_RXLEV_ACCESS_MIN are broadcast in EC SI 2 (see 3GPP TS 44.018 [17]).

CC2_Range_DL and CC3_Range_DL are optionally broadcast in EC SI 2. If either of CC2_Range_DL and CC3_Range_DL is not broadcast, its value shall be set to 0 and the corresponding downlink CC is not supported by the network.

If RLA_EC or SLA (whichever is applicable) is on the limit between two CC, the MS shall select the higher CC.

In case downlink CC1 is selected, the MS shall further indicate in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]) the margin of the measured RLA_EC (or SLA) relative to BT_Threshold_DL. The parameter DL_Signal_Strength_Step_Size broadcast in EC SI 2 (see 3GPP TS 44.018 [17]) is used to quantize the margin to report in the EC Packet Channel Request message. The maximum margin that can be reported is dependent on the number of Coverage Classes supported in the cell, and whether or not the access is initiated on RACH or EC-RACH, see 3GPP TS 44.018 [17].

NOTE: When TX diversity (antenna hopping) is active a MS may underestimate RLA_EC. This can be compensated for by the NW in an adjustment of the BT_Threshold_DL.

Reference

3GPP TS 45.008 subclause 6.10.2

41.8.4.4.2 Test purpose

To verify that an MS make an EC operation access request shall select the downlink CC to use on EC-RACH, based on the SINR and the associated parameters if the DL_CC_Selection indicates the SLA based method.

41.8.4.4.3 Method of test

Initial conditions

System Simulator:

1 Serving cell EC-GSM-IoT supported, RxLev -70dBm

2 non-serving cells (same ARFCN than the serving Cell), with RxLev set as per test configuration.

DL_CC_Selection = 1 (SLA based coverage class selection)

BT_Threshold_DL = 18 (8 dB)

BT_Threshold_UL = 20 (-110 dBm)

CC2_Range_DL = CC3_Range_DL = 5 (6 dB)

Access_Timeslots = 0 to use 1TS EC_RACH Mapping

EC_Max_Retrans = 0 (1 retransmission)

DL_Signal_Strength_Step_Size = 0 (2dB)

Mobile Station:

The MS is off.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS is turned on with the non-serving cell at different power level to modify the SINR. The EC-RACH access should indicate the proper DL coverage class or the proper margin if CC1 is indicated.

The procedure is repeated for all the DL coverage class. (k= 1 to 5)

Maximum duration of the test

Expected sequence

The test sequence is repeated for k = 1 … 5.

Step

Direction

Message

Comments

1

SS

The test is run with the following kx configurations:

k=1: -90 dBm RxLev of the non-serving cells to ensure CC1 as DL coverage class

k=2: -84 dBm RxLev of the non-serving cells to ensure CC1 as DL coverage class

k=3: -78 dBm RxLev of the non-serving cells to ensure CC2 as DL coverage class

k=4: -72 dBm RxLev of the non-serving cells to ensure l ensure CC3 as DL coverage class

k=5: -66 dBm RxLev of the non-serving cells to ensure CC4 as DL coverage class

2

MS

The MS is powered on

3

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1

Selected DL coverage Class shall be set according to k configuration

For k=1 and 2, two different margins, at least 2 steps apart shall be reported

For k= 3 to 5, CC2, CC3 and CC4 shall be reported respectively

Specific message contents:

41.8.4.5 EC-GSM-IoT / Coverage Class / UL Coverage Class Adaptation

41.8.4.5.1 Conformance requirement

If CC adaptation on EC-RACH and EC-AGCH is allowed (as indicated by the CC_Access_Adaptation parameter broadcast in EC-SI2), the MS shall gradually increase its CC as described in 3GPP TS 44.018 and use it as its selected uplink or downlink CC.

Reference

3GPP TS 45.008 subclause 6.10.4

A mobile station accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008) that has sent one or more EC PACKET CHANNEL REQUEST messages shall proceed as follows:

[…]

– When scheduling another EC PACKET CHANNEL REQUEST message the MS uses the “CC_Access_Adaptation” parameter (broadcast in EC SYSTEM INFORMATION TYPE 2 message) to determine if it is allowed to increment both its uplink CC and downlink CC to the next CC supported by the network (unless it is already using CC4).

– Upon incrementing its uplink/downlink CC the number of subsequent EC PACKET CHANNEL REQUEST message transmission attempts that may occur before it is allowed to increment its uplink/downlink CC once again is the same as when sending the first EC PACKET CHANNEL REQUEST message (i.e. determined by the “EC_Max_Retrans” parameter).

– When sending up to M + 1 EC PACKET CHANNEL REQUEST messages the MS may increment its uplink CC and downlink CC a maximum of 2 times if CC adaptations are allowed according to the “CC_Access_Adaptation” parameter.

Reference

– 3GPP TS 44.018 subclause 3.5.2.1.2a

41.8.4.5.2 Test purpose

To verify that an MS make an access for NAS low priority may gradually increment its coverage class if it is allowed by the network (based on CC_Access_Adaptation), it cannot be done more than 2 times

41.8.4.5.3 Method of test

Initial conditions

System Simulator:

1 cell EC-GSM-IoT supported

RLA_EC based coverage class selection.

BT_Threshold_UL = 0 (-90 dBm)

BT_Threshold_DL = 18 (-105 dBm)

CC2_Range_UL = CC3_Range_UL = 3 (4 dB)

Access_Timeslots = 0 to use 1TS EC_RACH Mapping

EC_Max_Retrans = 11 (7 retransmissions)

CC_Access_Adaptation = 1

Mobile Station:

The MS is off, configured for Low Priority.

Specific PICS Statements

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS is turned on and shall trigger an access for NAS signalling low priority.

Maximum duration of the test

Expected sequence

Step

Direction

Message

Comments

1

SS

The test is run with the following kx configurations:

k=1: -80 dBm RxLev of the serving cell to ensure CC1 as UL coverage class

2

MS

The MS is powered on

3

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

UL coverage class (i.e. Training Sequence used) indicated by the MS shall match CC1 configuration.

Selected DL coverage Class shall be CC1

4

SS

No response from the network

5

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH as retransmissions are allowed

UL coverage class (i.e. Training Sequence used) indicated by the MS shall match the previous request or be one coverage class higher.

DL coverage Class shall match the previous configuration or a be one coverage class higher.

Both or none of the coverage classes shall be incremented.

6

SS

Step 5 is repeated 6 times (7 retransmissions).

It is check that no more than 2 increases are requested.

If CC2 or higher is requested, it is checked that the blind physical layers transmissions are properly sent according to TS 45.002.

6A

If the MS does not increase any Coverage Class request, the test case is considered as not applicable

Specific message contents:

41.8.4.6 EC-GSM-IoT / Coverage Class / DL Coverage Class Update

41.8.4.6.1 Conformance requirement

An EC capable MS whose last uplink transmission was in a cell that does not support EC-GSM-IoT may choose to enable EC operation upon reselection to a cell that supports EC-GSM-IoT. In this case it shall perform an uplink transmission (e.g. a cell update) to update the network (i.e. addition of Coverage Class information) and therefore be reachable for pages on the EC-PCH.

Reference

– 3GPP TS 44.018 subclause 3.5.1a.1

For the purpose of paging block monitoring on EC-PCH, the MS shall keep the network informed about the selected downlink CC (see subclause 6.10.2). The MS shall indicate the selected downlink CC using the DL Coverage Class field in the EC Packet Channel Request message. This shall be done in advance of the next occurrence of the paging group of the MS, and at least if any of the following conditions are fulfilled:

– the selected downlink CC is higher than the last downlink CC communicated to the network;

– the selected downlink CC is CC1 and the last downlink CC communicated to the network is CC4; or

– the MS has completed an uplink data transfer in a cell not supporting EC-GSM-IoT since the last time it communicated a downlink CC to the network.

The MS shall consider the network to be informed about the selected downlink CC at the completion of the uplink data transfer.

The network shall apply the indicated downlink CC on EC-PCH messages sent to that MS.

Reference

– 3GPP TS 45.005 subclause 6.10.5

41.8.4.6.2 Test purpose

To verify that an MS updates the network appropriately if the selected downlink coverage class is modified.

For EC Capable MS supporting GPRS, it is verified that the MS will inform the network, of its DL coverage class when the last uplink transmission was done in a cell not supporting EC-GSM-IoT.

41.8.4.6.3 Method of test

Initial conditions

System Simulator:

1 Serving cell EC-GSM-IoT supported, RxLev -70dBm

1 GPRS Cell, turned Off

2 non-serving cells (same ARFCN than the serving Cell), with RxLev set at -78dBm to ensure DL CC2 is used.

DL_CC_Selection = 1 (SLA based coverage class selection)

BT_Threshold_DL = 18 (8 dB)

BT_Threshold_UL = 20 (-110 dBm)

CC2_Range_DL = CC3_Range_DL = 7 (6 dB)

Access_Timeslots = 0 to use 1TS EC_RACH Mapping

EC_Max_Retrans = 0 (1 retransmission)

DL_Signal_Strength_Step_Size = 0 (2dB)

Mobile Station:

The MS is GPRS attached in packet idle mode. eDRX cycle negotiated to 0101 (~ 49 sec)

Specific PICS Statements

– GPRS Supported (TSPC_GPRS)

PIXIT Statements

Foreseen final state of the MS

Test procedure

The MS is attached to the EC-GSM-IoT cell with DL coverage class CC2 conditions.

The SINR is decreased in order to trigger DL CC4 conditions. Before its next paging occasion, the MS should inform the network about the new DL CC.

The network conditions are then enhanced for CC1 to be selected as DL coverage Class. Before its next paging occasion, the MS should inform the network about the new DL CC.

If the MS support also GPRS, the MS is forced to move to a GPRS Cell and answer a paging. The MS is then moved again the EC-GSM-IoT cell and should inform the network of its coverage class.

Maximum duration of the test

Expected sequence

Step

Direction

Message

Comments

1

The MS is GPRS and the DL coverage Class CC2 was used during the Attach procedure.

2

SS -> MS

EC PAGING REQUEST

Sent on the MS EC-PCH block, according to TS 45.002 (CC2)

3

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

DL Coverage class indicated by the MS shall be CC2

4

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 3

Sent on EC-AGCH according to TS 45.002

5

The RxLev of the non-serving cells is increased to -66 dBm to ensure CC4 as DL coverage class.

6

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

Payload: “Cell Update”

UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1

Selected DL coverage Class shall be CC4

This message should be sent within one eDRX cycle (49 sec) of step 1.

6a

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 6

Sent on EC-AGCH according to TS 45.002 (with blind repetitions as CC4 is used)

7

SS -> MS

EC PAGING REQUEST

Sent on the MS EC-PCH block, according to TS 45.002 (CC4)

8

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

DL Coverage class indicated by the MS shall be CC4

9

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 8

Sent on EC-AGCH according to TS 45.002 (with blind repetitions as CC4 is used)

10

The RxLev of the non-serving cells is decreased to -84 dBm to ensure CC1 as DL coverage class.

11

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

Payload: “Cell Update”

UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1

Selected DL coverage Class shall be CC1

This message should be sent within one eDRX cycle (49 sec) of step 7.

11a

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 11

Sent on EC-AGCH according to TS 45.002 (no Blind repetition as CC1 is used)

12

SS -> MS

EC PAGING REQUEST

Sent on the MS EC-PCH block, according to TS 45.002 (CC1)

13

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

DL Coverage class indicated by the MS shall be CC1

14

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 13

Sent on EC-AGCH according to TS 45.002 (no Blind repetition as CC1 is used)

Next step are only applicable for EC Capable MS supporting GPRS (TSPC_GPRS)

15

The EC-GSM-IoT cell is turned Off and the GPRS cell is turned on (RxLev = -80dBm)

16

Wait for 30 sec.

17

SS -> MS

PAGING REQUEST Type 1

1st Mobile Identity contains IMSI of the MS, second Mobile Identity not present. Packet page indication indicates packet paging procedure. Sent on PCH.

18

MS -> SS

CHANNEL REQUEST

Establishment Cause = = "one phase packet access". Received on RACH.

19

SS -> MS

IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 18

Sent on AGCH

20

The EC-GSM-IoT cell is turned on (RxLev = -70dBm) and the GPRS cell is turned off

21

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

Payload: “Cell Update”

UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1

Selected DL coverage Class shall be CC1

This message should be sent within before next paging opportunity

21a

SS -> MS

EC IMMEDIATE ASSIGNMENT REJECT

Request Reference = pertaining to the message received in step 21

Sent on EC-AGCH according to TS 45.002 (no Blind repetition as CC1 is used)

22

SS -> MS

EC PAGING REQUEST

Sent on the MS EC-PCH block, according to TS 45.002 (CC1)

23

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

DL Coverage class indicated by the MS shall be CC1

Specific message contents: