42.10 EC-GSM-IoT

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

42.10.1 EC-GSM-IoT / Packet Uplink Assignment

42.10.1.1 EC-GSM-IoT / Packet Uplink Assignment /Successful / CCCH

42.10.1.1.1 Conformance requirements

The establishment of an EC Temporary Block Flow (EC TBF), for a mobile station that has enabled EC operation, is performed on the EC-CCCH. It can be initiated by either the mobile station or the network. The establishment of an EC TBF can also be performed on the CCCH if the mobile station has selected Coverage Class 1 in both the uplink and downlink directions, see 3GPP TS 45.008 and 3GPP TS 44.018.

When the mobile station receives a Fixed Uplink Allocation, FUA, in e.g. the EC PACKET UPLINK ASSIGNMENT or EC PACKET UPLINK ACK/NACK message it shall perform uplink transmissions according to that allocation.

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. This message can also be sent using the RACH (see sub-clause 3.5.2.1.2) in which the message format is as shown in Tables 9.1.65.3 and 9.1.65.4.

In case overlaid CDMA is used, see 3GPP TS 43.064 [6], up to four MS can be multiplexed on the same physical resource, simultaneously transmitting, using different orthogonal codes assigned by the network, see 3GPP TS 44.060 [11]. The codes are applied per burst over the assigned PDCHs for EC-PDTCH and EC-PACCH in each TDMA frame from the lowest to the highest numbered assigned TN, according to Table 6.3-2, and are only applied in case blind physical layer transmissions are used (i.e. for CC2, CC3 and CC4).

When EC operation is enabled the packet uplink resource is assigned to the mobile station in an EC IMMEDIATE ASSIGNMENT TYPE 1 message sent in unacknowledged mode on the same CCCH timeslot on which the network received the EC PACKET CHANNEL REQUEST message (see Table 3.5.2.1.2.3). Timer T3141 is started on the network side.

References

3GPP TS 44.060, subclauses 7a.1, 8.1.1.3b

3GPP TS 44.018, subclauses 3.5.1a, 3.5.1a.1, 3.5.2.1.3.1, 9.1.65

3GPP TS 45.002 subclause 6.3.2.2.6

42.10.1.1.2 Test purpose

1. The MS is triggered to initiate packet uplink transfer data in EC operation with FUA

2. Overlaid CDMA

3. Verify CCCH is used instead of EC-CCCH

42.10.1.1.3 Method of test

Initial Conditions

System Simulator:

– 1 cell, EC-GSM-IoT. The MS is GPRS attached. RACH Access Control =1 in EC-SCH

Mobile Station:

– The MS is switched off.

Specific PICS Statements

PIXIT Statements

Test Procedure

To verify that the MS:

1. Sends the EC-RACH on RACH channel due to RACH access control configured to 1

2. MS sends Overlaid CDMA using CC2 and code 1

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

MS

The MS is triggered to send uplink data

2

MS -> SS

EC PACKET CHANNEL REQUEST

Verify received on RACH

3

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 1

Overlaid CDMA configured to be used Code 1

UL CC2 to be used

Fixed uplink assignment, sent on AGCH.

3 RLC Blocks to be sent

4

MS -> SS

UPLINK RLC DATA BLOCKS

Verify MS sends Overlaid Code 1

5

MS -> SS

UPLINK RLC DATA BLOCKS

Verify MS sends Overlaid Code 1

6

MS -> SS

UPLINK RLC DATA BLOCKS

Verify MS sends Overlaid Code 1

7

The messages in steps 4-6 are mapped according to UL CC2

8

SS -> MS

EC PACKET UPLINK ACK/NACK

acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. UL CC1 to be used.

Sent on EC-PACCH.

9

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

acknowledge the RLC data. Received on EC-PACCH

Specific Message Contents

Step 2: EC IMMEDIATE ASSIGNMENT TYPE 1

TBD

42.10.1.2 EC-GSM-IoT / Packet Uplink Assignment /Successful / During Downlink ongoing

42.10.1.2.1 Conformance requirements

When the mobile station receives a Fixed Uplink Allocation, FUA, in e.g. the EC PACKET UPLINK ASSIGNMENT or EC PACKET UPLINK ACK/NACK message it shall perform uplink transmissions according to that allocation. The uplink resources are allocated with respect to a BTTI configuration, the mobile station uplink coverage class, the assigned MCS, the number of RLC data blocks required for the EC TBF as indicated by the mobile station and with respect to the latest ack/nack status as perceived by the network, if such exists, and transmitted to the mobile station in the message containing the FUA. The uplink resources will be allocated according to the coverage class dependent resource mapping (see 3GPP TS 45.002) and the mobile station shall transmit accordingly.

When the mobile station has an ongoing downlink EC TBF, it may initiate an uplink EC TBF by including the EC Channel Request Description information element in the EC PACKET DOWNLINK ACK/NACK message on the EC-PACCH and start timer T3168. The network may then establish an uplink EC TBF by sending an EC PACKET UPLINK ASSIGNMENT message to the mobile station, in which case the downlink EC TBF is released.

In EC operation, the downlink EC TBF is released at establishment of the uplink EC TBF.

In case overlaid CDMA is used, see 3GPP TS 43.064 [6], up to four MS can be multiplexed on the same physical resource, simultaneously transmitting, using different orthogonal codes assigned by the network, see 3GPP TS 44.060 [11]. The codes are applied per burst over the assigned PDCHs for EC-PDTCH and EC-PACCH in each TDMA frame from the lowest to the highest numbered assigned TN, according to Table 6.3-2, and are only applied in case blind physical layer transmissions are used (i.e. for CC2, CC3 and CC4).

…–

References

3GPP TS 44.060, subclauses 8.1.1.3b ,8.1.2.5

3GPP TS 45.002 subclause 6.3.2.2.6

42.10.1.2.2 Test purpose

1. The MS is triggered to initiate packet uplink transfer data in EC operation with FUA during an ongoing downlink TBF

2. Overlaid CDMA

42.10.1.2.3 Method of test

Initial Conditions

System Simulator:

1 cell, EC-GSM-IoT. CC2 used.

Mobile Station:

The MS is GPRS attached.

Specific PICS Statements

PIXIT Statements

Test Procedure

To verify that the MS:

1. Uplink is established during an ongoing downlink

2. Verify DL TBF terminates immediately after the UL TBF is requested

3. Overlaid CDMA used with code 1 during CC2

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1a

SS -> MS

EC IMMEDIATE ASSIGNMENT

For downlink TBF, Sent on EC-PCH.

1b

SS -> MS

EC PACKET DOWNLINK ASSIGNMENT

Triggers the MS to switch to the assigned PDCH. (no starting time)

With valid RRBP field

2

MS->SS

EC PACKET CONTROL ACK

4 access bursts. Sent in the block specified by RRBP field in step 1.

3

SS -> MS

RLC DATA BLOCK

2 blocks after the previous message, with valid RRBP field, on assigned PDCH, addressed to MS.

4

MS -> SS

EC PACKET DOWNLINK ACK/NACK

MS acknowledges on PACCH the RLC data block sent in step 3.

5

SS -> MS

X * RLC DATA BLOCK

Repeat sending data blocks and PDAN’s until step 7 occurs

6

MS -> SS

X * EC PACKET DOWNLINK ACK/NACK

Repeat sending data blocks and PDAN’s until step 7 occurs

7

MS

Trigger MS to send data

8

MS -> SS

EC PACKET DOWNLINK ACK/NACK

PDAN including a request for a Fixed Uplink Allocation

9

SS -> MS

EC PACKET UPLINK ASSIGNMENT

PUA including a Fixed Uplink Allocation

Overlaid CDMA configured to be used Code 1

UL CC2 to be used

3 RLC Blocks to be sent

10

MS -> SS

UPLINK RLC DATA BLOCKS

Received on the assigned PDTCH.

Verify MS sends Overlaid Code 1

11

MS -> SS

UPLINK RLC DATA BLOCKS

Received on the assigned PDTCH.

Verify MS sends Overlaid Code 1

12

MS -> SS

UPLINK RLC DATA BLOCKS

Received on the assigned PDTCH.

Verify MS sends Overlaid Code 1

13

The messages in steps 10-12 are mapped according to UL CC2

14

SS -> MS

EC PACKET UPLINK ACK/NACK

acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. UL CC1 to be used

Sent on EC-PACCH.

15

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

acknowledge the RLC data. Received on EC-PACCH.

Specific Message Contents

Step 9: EC PACKET UPLINK ASSIGNMENT

TBD

42.10.1.3 EC-GSM-IoT / Packet Uplink Assignment /Resource Assignment

42.10.1.3.1 Conformance requirements

STARTING_DL_TIMESLOT_OFFSET (2 bit field)

This field defines the timeslot number of the lowest timeslot included in the assignment that is used for transfer of downlink RLC/MAC control messages on the EC-PACCH during the UL EC TBF. The number of additional timeslots that are included in the downlink assignment depends on the assigned DL Coverage Class. The assigned timeslots are contiguous, starting with the timeslot number indicated in the STARTING_DL_TIMESLOT_OFFSET field. The STARTING_DL_TIMESLOT_OFFSET field is encoded as an offset to the timeslot assigned with the STARTING_UL_TIMESLOT field. The encoding of the field is dependent of the value of the UL_COVERAGE_CLASS and DL_COVERAGE_CLASS fields in the same message.

References

3GPP TS 44.018, table 9.1.60.2

42.10.1.3.2 Test purpose

To verify that the parameter STARTING_DL_TIMESLOT_OFFSET is properly used when uplink and downlink coverage classes are different and at least one of them is CC1.

42.10.1.3.3 Method of test

Initial Conditions

System Simulator:

1 cell, EC-GSM-IoT

Mobile Station:

The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)

Specific PICS Statements

PIXIT Statements

Test Procedure

The MS triggers and uplink data transfer. A downlink data transfer is requested by the network and different type of coverage class combination and values of STARTING_DL_TIMESLOT_OFFSET are tested.

The EC PACKET UPLINK ACK/NACK requested a Packet control acknowledgement is sent according to the STARTING_DL_TIMESLOT_OFFSET. For DL CC2 where 4 slots are used for the transmission of this message, the last 3 blocks are corrupted.

The procedure is repeated different combination of coverage classes (k= 1 to 2).

Maximum duration of the test

5 min

Expected sequence

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

Step

Direction

Message

Comments

1

The NW is configured as follow:

k=1, Uplink CC1, DL CC2

k=2, Uplink CC2, DL CC1

2

TMS is triggered to send 50 Octets of data.

3

MS -> SS

EC PACKET CHANNEL REQUEST

Verify received on EC-RACH

X blocks requested

UL and DL CC1

4

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

Fixed uplink assignment, sent on EC-AGCH

See specific message content

5

MS -> SS

UPLINK RLC DATA BLOCKS

6

MS

Step 4 is repeated X-1 times.

Branch A is done for k=1 (DL CC2)

Branch B is done for k=2 (DL CC1)

7- A

SS -> MS

EC PACKET UPLINK ACK/NACK

k=1

Acknowledge all the UL RLC data. Received on EC-PACCH on DL timeslot defined in step 4. Corrupted data sent of the next 3 DL TS allocated

EC Packet Control Ack requested with a valid RRBP.

7-B

SS -> MS

EC PACKET UPLINK ACK/NACK

k=2

Sent on EC-PACCH on TimeSlot = STARTING_UL_TIMESLOT.

No UL RLC Data block acknowledged

The MS shall not see this message.

7bis-B

SS -> MS

EC PACKET UPLINK ACK/NACK

Acknowledge all the UL RLC data. Received on EC-PACCH on DL timeslot defined in step 4.

EC Packet Control Ack requested with a valid RRBP.

8

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

Sent according to UL CC1

Specific Message Contents

EC IMMEDIATE ASSIGNMENT TYPE 2 message in step 4:

UL_COVERAGE_CLASS

00 UL CC1 for k=1

01 UL CC2 for k=2

DL_COVERAGE_CLASS

01 DL CC2 for k=1

00 DL CC1 for k=2

EC Fixed Uplink Allocation

STARTING_UL_TIMESLOT

Uplink_TFI_Assignment

STARTING_DL_TIMESLOT_OFFSET

011 Timeslot 3

00001

01 STARTING_UL_TIMESLOT – 1 for k=1

01 STARTING_UL_TIMESLOT + 1 for k=2

42.10.1.4 EC-GSM-IoT / Packet Uplink Assignment /Resource Assignment / Gap

42.10.1.4.1 Conformance requirements

The mobile station in EC TBF mode may include an EC Channel Request Description in the EC PACKET DOWNLINK ACK/NACK message in order to request an uplink TBF. The network may then establish an uplink EC TBF for the mobile station by sending an EC PACKET UPLINK ASSIGNMENT message, in which case the downlink EC TBF is released.

TIMESLOT_MULTIPLICATOR (3 bit field)
This field defines how many UL timeslots that the assignment contains when the assigned UL Coverage Class, according to the UL_COVERAGE_CLASS field, is CC1.

Values other than ‘000’ can only be used if supported by the mobile station, as indicated by its multislot capability, see 3GPP TS 45.002. If the assigned uplink Coverage Class > CC1 (according to the UL_COVERAGE_CLASS field), the mobile station shall consider the TIMESLOT_MULTIPLICATOR field as not valid

START_FIRST_UL_RLC_DATA_BLOCK (4 bit field)
This field indicates the starting position of the resources for the first allocated RLC Data block in the fixed uplink allocation. The starting position is relative to the first TDMA frame (N) of the downlink block containing the last blind physical layer transmission of this EC PACKET UPLINK ASSIGNMENT message, according to the USED_DL_COVERAGE_CLASS field. The encoding of the field is dependent of the value of the UL_COVERAGE_CLASS and the TIMESLOT_MULTIPLICATOR fields in the same message.

DELAY_NEXT_UL_RLC_DATA_BLOCK (3 bit field)
This field indicates the position of the next allocated RLC Data block in the fixed uplink allocation. The position is calculated as the number of transmission opportunities from the previous uplink allocation, according to the UL_COVERAGE_CLASS and TIMESLOT_MULTIPLICATOR fields in the same assignment message, where the next uplink allocation for the mobile station is placed and where the mobile station thus shall transmit the next RLC data block. In the transmission opportunity/ies between the previous uplink allocation and this allocation the mobile station is not allocated any resource, and shall thus not transmit.

References

3GPP TS 44.060, subclauses 9.3.2.6 and table 11.2.58.2

42.10.1.4.2 Test purpose

To verify that the Timeslot allocation and position in the TDMA Frame used to transmit the UL RLC data block are done according the defined parameters in the EC PACKET UPLINK ASSIGNMENT

42.10.1.4.3 Method of test

Initial Conditions

System Simulator:

– 1 cell, EC-GSM-IoT.

Mobile Station:

– The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)

Specific PICS Statements

PIXIT Statements

Test Procedure

An uplink transfer is triggered during an EC DL TBF.

The SS sends an EC PACKET UPLINK ASSIGNMENT to handle the MS requests

The procedure is repeated different combination of parameters (k= 1 to 3).

Maximum duration of the test:

5 min

Expected sequence

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

Step

Direction

Message

Comments

1

SS -> MS

EC IMMEDIATE ASSIGNMENT

For downlink TBF, Sent on EC-PCH.

2

SS -> MS

EC PACKET DOWNLINK ASSIGNMENT

Triggers the MS to switch to the assigned EC-PDCH. Valid RRBP field

3

MS->SS

EC PACKET CONTROL ACK

4 access bursts. Sent in the block specified by RRBP field in step 2

4

SS -> MS

RLC DATA BLOCK

2 blocks after the previous message, with valid RRBP field, on assigned EC-PDCH, addressed to MS

5

MS -> SS

EC PACKET DOWNLINK ACK/NACK

MS acknowledges on EC-PACCH the RLC data block sent in step 4.

6

MS

The MS is triggered to send 50 Octets of Data

7

Steps 4 and 5 are repeated until an UL transfer Request is done in the EC PACKET DOWNLINK ACK/NACK

8

SS -> MS

EC PACKET UPLINK ASSIGNMENT

See specific message content for k=1,2 or 3

9

MS -> SS

UPLINK RLC DATA BLOCKS

Send on the EC-PDTCH defined in step 8 (according to UL_COVERAGE_CLASS , TIMESLOT_MULTIPLICATOR and START_FN_FIRST_UL_RLC_DATA_BLOCK)

10

MS -> SS

UPLINK RLC DATA BLOCKS

Sent on the EC-PDTCH defined in step 8 (according to DELAY_NEXT_UL_RLC_DATA_BLOCK)

Step 10 is repeated until the last block is transmitted

13

SS -> MS

EC PACKET UPLINK ACK/NACK

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

14

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

Specific Message Contents

EC IMMEDIATE ASSIGNMENT TYPE 2 message in step 4:

UL_COVERAGE_CLASS

TIMESLOT_MULTIPLICATOR

START_FN_FIRST_UL_RLC_DATA_BLOCK

DELAY_NEXT_UL_RLC_DATA_BLOCK

00 (CC1) for k=1 and k=2

10 (CC3) for k=3

0 0 0 1 timeslot assigned for k=1

0 1 0 3 timeslots assigned for k=2

1 1 0 7 timeslots assigned for k=3

1 1 0 0 for k=1

0 0 1 0 for k=2

0 1 0 1 for k=3

0 0 0 In the 2nd next transmission opportunity for k=1 and k=3

0 0 1 In the 3rd next transmission opportunity for k=2

42.10.1.5 EC-GSM-IoT / Packet Uplink Assignment /Downlink Coverage Class Adaptation/ T3248

42.10.1.5.1 Conformance requirements

When timer T3226 expires, the mobile station shall monitor the EC-PACCH according to its assigned downlink coverage class and, as long as T3228 is running, attempt to decode every downlink RLC/MAC block on the PDCHs corresponding to the downlink assigned EC-PACCH resources.

Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message addresses the mobile station, the mobile station shall act on the message.

If timer T3228 expires, the mobile station shall release the ongoing uplink TBF and may perform an abnormal release with access retry, unless timer T3248 (sent in EC-SI) is used. If T3248 is used, i.e. it has a value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH using the next higher DL Coverage Class, if such exists. If no higher DL CC than the assigned DL CC exists, the mobile station shall continue to monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message according to the last assigned DL CC until T3248 expires.

The assigned resources (timeslots) to be used for the downlink EC-PACCH according to the next higher DL Coverage Class are either the same as the assigned timeslots for the uplink EC-PDTCH or given in the assignment message. If no valid resources for the next higher Coverage Class are assigned, the mobile station shall continue to monitor the downlink EC-PACCH using the assigned DL Coverage Class while timer T3248 is running.

When the mobile station receives an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with its uplink TBF it shall stop T3228, if running. If timer T3248 was running at reception of the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message (and thus not T3228), the timer T3248 shall be stopped.

References

3GPP TS 44.060, subclauses 8.1.1.3b.1

42.10.1.5.2 Test purpose

To verify that in EC operation, if T3248 is used and running, the MS will monitor the DL EC_PACCH using the next higher DL coverage Class (if any).

42.10.1.5.3 Method of test

Initial Conditions

System Simulator:

1 cell, EC-GSM-IoT. T3248 set to 3 secs

Mobile Station:

The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)

Specific PICS Statements

PIXIT Statements

Test Procedure

The MS is set to trigger an UL data transfer.

Following the last radio block transmitted according to the fixed uplink allocation, the MS should then T3226 then T3228 and start to monitor the EC-PACCH according to its DL CC.

The SS does not send the corresponding EC PACKET UPLINK ACK/NACK.

At the expiry of T3228, the MS should start T3248 and monitor the EC-PACCH with DL CC2 configuration.

The SS then sends the expected EC PACKET UPLINK ACK/NACK.

The UL transfer is then complete and no retransmission is expected.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

The MS is triggered to send 50 Octets of data

2

MS -> SS

EC PACKET CHANNEL REQUEST

Verify received on EC-RACH

UL and DL CC1 should be requested.

X blocks requested

3

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

Fixed uplink assignment, sent on EC-AGCH according to DL CC1

MCS1

STARTING_DL_TIMESLOT_OFFSET same as STARTING_UL_TIMESLOT

4

MS -> SS

UPLINK RLC DATA BLOCKS

5

MS

Step 4 is repeated X-1 times.

6

Wait for T3226 + T3228 + 1 sec

7

SS -> MS

EC PACKET UPLINK ACK/NACK

Acknowledge all the UL RLC data. Received on EC-PACCH during T3248. Mapped according to DL CC2 (see TS 45.002) on 4 slots.

EC Packet Control Ack requested with a valid RRBP.

8

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

Sent according to UL CC1

Specific Message Contents

42.10.1.6 EC-GSM-IoT / Packet Uplink Assignment /Downlink Coverage Class Adaptation/ T3248 or T3228 Expiry

42.10.1.6.1 Conformance requirements

If timer T3228 expires, the mobile station shall release the ongoing uplink TBF and may perform an abnormal release with access retry, unless timer T3248 (sent in EC-SI) is used. If T3248 is used, i.e. it has a value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH using the next higher DL Coverage Class, if such exists. If no higher DL CC than the assigned DL CC exists, the mobile station shall continue to monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message according to the last assigned DL CC until T3248 expires.

At expiry of T3248, the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed.

References

3GPP TS 44.060, subclauses 8.1.1.3b.1

42.10.1.6.2 Test purpose

To verify that in EC operation, if T3248 is used and running, the MS will monitor the DL EC_PACCH using the next higher DL coverage Class (if any).

42.10.1.6.3 Method of test

Initial Conditions

System Simulator:

1 cell, EC-GSM-IoT. T3248 set to 3 secs

Mobile Station:

The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)

Specific PICS Statements

PIXIT Statements

Test Procedure

The MS is set to trigger an UL data transfer.

Following the last radio block transmitted according to the fixed uplink allocation, the MS should then T3226 then T3228 and start to monitor the EC-PACCH according to its DL CC.

The SS does not send the corresponding EC PACKET UPLINK ACK/NACK.

At the expiry of T3228, the MS should start T3248 and monitor the EC-PACCH with DL CC2 configuration.

The SS then sends an EC PACKET UPLINK ACK/NACK not addressing the MS (i.e. wrong Uplink_TFI) during T3248. The Ms should not consider the acknowledgment.

The SS checks that no acknowledgement is sent by the MS.

At expiry of T3248, the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

The MS is triggered to send 50 Octets of data

2

MS -> SS

EC PACKET CHANNEL REQUEST

Verify received on EC-RACH

UL and DL CC1 should be requested.

X blocks requested

3

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 2

Fixed uplink assignment, sent on EC-AGCH according to DL CC1

MCS1

STARTING_DL_TIMESLOT_OFFSET same as STARTING_UL_TIMESLOT

4

MS -> SS

UPLINK RLC DATA BLOCKS

5

MS

Step 4 is repeated X-1 times.

6

Wait for T3226 + T3228 + 1 sec

7

SS -> MS

EC PACKET UPLINK ACK/NACK

Received on EC-PACCH during T3248. Mapped according to DL CC2 (see TS 45.002) on 4 slots but not using the MS Uplink TFI (i.e. not addressing the MS).

A valid RRBP is indicated

8

SS

SS checks that no EC PACKET CONTROL ACK is received.

This is checked for 3 seconds.

9

SS

SS check that a new EC PACKET CHANNEL REQUEST might be sent as per T3248 expiry, the MS should abort the ongoing TBF and may trigger an abnormal release with access retry.

Specific Message Contents

42.10.2 EC-GSM-IoT / Packet Downlink Assignment

42.10.2.1 EC-GSM-IoT / Packet Downlink Assignment / Successful / T3238

42.10.2.1.1 Conformance requirements

The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of upper layer PDUs in the direction from the network to the mobile station. The procedure is triggered by a request from upper layers on the network side to transfer an upper layer PDU to a mobile station in packet idle mode that has enabled EC operation. Upon such a request, the network shall initiate a packet downlink assignment procedure on the EC-CCCH as described in 3GPP TS 44.018.

For a TBF in BTTI configuration, prior to the initiation of RLC data block transfer on the downlink, the network assigns the following parameters in a downlink assignment.

in case of a downlink EC TBF, the network also assigns the following parameters:

– uplink and downlink coverage classes;

– a set of PDCHs to be used for transmission of uplink RLC/MAC control messages.

If the mobile station, in the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to ‘1’, has been indicated to continue monitoring the EC-PACCH, it shall start timer T3238. The mobile station shall then monitor the EC-PACCH, according to its assigned downlink Coverage Class of the TBF, after an initial waiting time as indicated in the EC PACKET UPLINK ACK/NACK message. The mobile station shall then monitor the EC-PACCH, using a monitoring pattern as indicated in the EC PACKET UPLINK ACK/NACK message, until timer T3238 expires or until a downlink RLC/MAC control message triggering the release of the TBF is received. When timer T3238 expires, the mobile station shall leave the TBF and return to packet idle mode.

If the mobile station receives an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station while listening to the EC-PACCH, it shall stop timer T3238, release the uplink TBF and act on the assigned resources.

An uplink EC TBF is released when the network has received all RLC data blocks for a TBF, as indicated by the mobile station, and sent the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to ‘1’. An exception is when the mobile station, in the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to ‘1’, is ordered to continue monitoring the EC-PACCH, see sub-clause 9.3.2.4.3

References

3GPP TS 44.060, subclauses 7a.3,8.1.2, 8.1.2.5, 9.3.2.4.3, 9.3.1.4

42.10.2.1.2 Test purpose

To verify that the MS:

1. Start a Uplink TBF

2. Send FAI for the Uplink with a value of the T3238

3. Establish a downlink TBF before expire of T3238

42.10.2.1.3 Method of test

Initial Conditions

System Simulator:

1 cell, EC-GSM-IoT.

Mobile Station:

The MS is GPRS attached.

Specific PICS Statements

PIXIT Statements

Test Procedure

The MS triggers an UL data transfer in EC Operation mode. The SS acknowledges all the UL data blocks and activate T3238.

The MS shall monitor the DL EC-PACCH for a Downlink transfer when T3228 is used.

The SS then sends an EC DOWNLINK ASSIGNMENT before T3238 expiry.

The MS shall proceed with the DL transfer

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

MS -> SS

EC PACKET CHANNEL REQUEST

Verify received on RACH

2

SS -> MS

EC IMMEDIATE ASSIGNMENT TYPE 1

Fixed uplink assignment, sent on EC-AGCH.

5 RLC Blocks to be sent

3

MS -> SS

UPLINK RLC DATA BLOCKS

Received on the assigned PDTCH

4

MS -> SS

UPLINK RLC DATA BLOCKS

Received on the assigned PDTCH

5

MS -> SS

UPLINK RLC DATA BLOCKS

Received on the assigned PDTCH

6

SS -> MS

EC PACKET UPLINK ACK/NACK

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

T3238 set to 96s

7

SS

Wait 20s

12

SS -> MS

EC PACKET DOWNLINK ASSIGNMENT

Triggers the MS to switch to the assigned PDCH. (no starting time)

With valid RRBP field

Started before T3238 expired

Meaning verify EC-PACCH channel still monitored by MS as T3238 not expired

13

MS->SS

EC PACKET CONTROL ACK

4 access bursts. Sent in the block specified by RRBP field in step 1.

14

SS -> MS

RLC DATA BLOCK

2 blocks after the previous message, with valid RRBP field, on assigned PDCH, addressed to MS.

15

MS -> SS

EC PACKET DOWNLINK ACK/NACK

MS acknowledges on PACCH the RLC data block sent in step 3.

MS<->SS

Completion of macro {Downlink data transfer}

SS completes downlink transfer of 200 octets of data.

Specific Message Contents

Step 12: EC PACKET DOWNLINK ASSIGNMENT

TBD

42.10.3.1 EC-GSM-IoT / Contention resolution / Enhanced Access Burst procedure

The contention resolution is completed on the mobile station side when the mobile station receives a PACKET UPLINK ASSIGNMENT message with the same TLLI as the mobile station has included in the PACKET RESOURCE REQUEST message.

42.10.3.1.1 Conformance requirements

The TLLI is used to uniquely identify the mobile station when sending on the uplink. A mobile station, that has enabled EC operation, includes its TLLI in one or several of the uplink blocks that are transmitted during the establishment of an EC TBF, depending on what packet access procedure is used.

The contention resolution is described for the different packet access procedures in the following sub-clauses:

– using Access Burst procedure, with inclusion of the full TLLI in each RLC data block that is sent on the TBF until contention resolution is completed, described in 7a.2.1.1;

– using Enhanced Access Burst procedure, with inclusion of the full TLLI in only the first RLC data block that is sent on the TBF and then inclusion of a limited part of the TLLI in the subsequent RLC data blocks that are sent until contention resolution is completed, described in 7a.2.1.2.

The network indicates in the EC Immediate Assignment message which of the procedures that shall be used for the contention resolution, see 3GPP TS 44.018.

When the Enhanced Access Burst procedure is used, only the first RLC data block that is sent on the TBF shall include the TLLI of the mobile station. If MCS-7, MCS-8 or MCS-9 is used for the transmission of the TLLI (i.e. the RLC/MAC block is carrying two RLC data blocks), the TLLI shall be inserted in both RLC data blocks that are included in the first RLC/MAC block. Every RLC data block that is sent on the TBF, except the first one, shall include the reduced TLLI (rTLLI) of the mobile station until the mobile station receives an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message or an EC PACKET UPLINK ACK/NACK message addressing the mobile station with the TFI value associated with the uplink TBF and containing either the TLLI or the rTLLI of the mobile station. The reduced TLLI (rTLLI) consists of the 4 least significant bits of the TLLI of the mobile station. The rTLLI shall not be included in the RLC/MAC header if the TLLI is included in the RLC Data block. The rTLLI value shall thus not be included in the RLC/MAC header of the first RLC Data block of a TBF, with BSN=0 and, if MCS-7, MCS-8 or MCS-9 is used for the transmission, with BSN=1, since the TLLI of the mobile station is included in the RLC data block(s).

If the failure is due to a TLLI mismatch, or to the expiry of timers T3166 or T3168, or to the fact that the counter N3104 reached its maximum value in the contention resolution procedure, and repetition as described in subclause 7.1.3.3 has been performed, the mobile station shall remain in packet idle mode, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continued.

Reference

3GPP TS 44.060 subclauses 7a.2.1, 7a.2.1.2.

42.10.3.1.2 Test purpose

To verify that the MS uses the Enhanced Access Burst procedure when indicated by the network.

42.10.3.1.3 Method of test

Initial conditions

System Simulator:

1 cell, EC-GSM-IoT supported

Mobile Station:

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

Specific PICS Statements

PIXIT Statements

Test procedure

The MS is triggered to initiate uplink data transfer. The SS responds with EC IMMEDIATE ASSIGNMENT TYPE 2 message that request fixed link assignment, sent on EC-AGCH, with Enhanced Access Burst value set to 1..

The MS shall then send the first RLC data block including the TLLI. The SS responds with EC PACKET UPLINK ACK/NACK with the same TLLI.

The MS then sends two additional RLC data blocks with a reduced TLLI. The SS then acknowledge the received data blocks with the EC PACKET UPLINK ACK/NACK message. The MS acknowledge with the EC PACKET CONTROL ACKNOWLEDGEMENT message.

Maximum duration of the test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is triggered to initiate packet uplink transfer of three RLC data blocks.

2

MS -> SS

EC PACKET CHANNEL REQUEST

Received on EC-RACH.

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

Enhanced Access Burst value: 1 (The Enhanced Access Burst procedure shall be used)

4

MS -> SS

UPLINK RLC DATA BLOCK

MS sends the 1st RLC data block including its TLLI

5

SS -> MS

EC PACKET UPLINK ACK/NACK

The SS transmits the MS TLLI in order to solve the contention and indicates that the 1st RLC data block has been received.

6

MS -> SS

UPLINK RLC DATA BLOCK

MS sends the 2nd RLC data block including its reduced TLLI (rTLLI) that is set to the 4 least significant bits of the TLLI of the mobile station

7

MS -> SS

UPLINK RLC DATA BLOCK

MS sends the 3rd RLC data block including its reduced TLLI (rTLLI) that is set to the 4 least significant bits of the TLLI of the mobile station

8

SS -> MS

EC PACKET UPLINK ACK/NACK

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

9

MS -> SS

EC PACKET CONTROL ACKNOWLEDGEMENT

MS acknowledge the RLC data. Received on EC-PACCH

Specific message contents

None.