8 Medium Access Control (MAC) Procedures in Packet Transfer Mode

04.603GPPGeneral Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 1999TS

8.0 General

The MAC procedures defined in this sub-clause are applicable in packet transfer mode. They are applicable in dual transfer mode, if both the network and the mobile station support DTM.

The procedures in this clause (sub-clause 8) shall not be used to change the frequency allocation of the mobile station in dual transfer mode. None of the PACKET DOWNLINK ASSIGNMENT, the PACKET UPLINK ASSIGNMENT or the PACKET TIMESLOT RECONFIGURE messages shall include the Frequency Parameters IE when they are sent to a mobile station in dual transfer mode.

NOTE: The network may use the DTM procedures on the main DCCH (the DTM ASSIGNMENT COMMAND message), if the radio resources for the RR connection and one or more TBF(s) need to be changed, see 3GPP TS 04.18.

8.1 Transfer of RLC data blocks

8.1.0 Medium access mode

The transfer of RLC data blocks is governed by different principles on both uplink and downlink for each of the defined medium access modes: dynamic allocation, extended dynamic allocation, fixed allocation and exclusive allocation. Fixed allocation may be operated in half duplex mode.

The medium access mode the mobile station is to use, except when exclusive allocation is applied in dual transfer mode, is given by the MAC_MODE parameter. The MAC_MODE parameter is included in the downlink assignment (e.g., PACKET DOWNLINK ASSIGNMENT) message. In the uplink assignment (e.g., PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) message, the MAC_MODE parameter is given indirectly by the presence of either the Dynamic Allocation struct or the Fixed Allocation struct and, respectively, by the EXTENDED_DYNAMIC_ALLOCATION and the HALF_DUPLEX_MODE parameters. The value of the MAC_MODE parameter may be changed between dynamic allocation and extended dynamic allocation while the mobile station is in packet transfer mode or dual transfer mode. Other changes of the MAC_MODE parameter are not allowed in packet transfer mode or dual transfer mode.

The exclusive allocation is applicable only in dual transfer mode. The exclusive allocation shall be used in dual transfer mode in configurations with a half-rate PDCH.

When the conditions for exclusive allocation are fulfilled, the mobile station shall store the value of the MAC_MODE parameter. The MAC_MODE parameter has no effect as long as the exclusive allocation is used. When the conditions for exclusive allocation are not fulfilled, the mobile station shall use the medium access mode given by the value of the MAC_MODE parameter.

8.1.1 Uplink RLC data block transfer

Prior to the initiation of RLC data block transfer on the uplink, the network assigns the following parameters to characterise the uplink TBF in the uplink assignment (e.g., PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) message:

– a Temporary Flow Identity (TFI). The mobile station shall set the TFI field of each uplink RLC data block to the TFI value assigned to the mobile station for the uplink TBF.

– a set of PDCHs to be used for the uplink transfer;

– a TBF Starting Time indication (optional in case of a dynamic or extended dynamic allocation).

All the RLC data blocks of an uplink TBF initiated by one phase access shall each contain a TLLI field in the RLC data block header until the contention resolution is completed on the mobile station side (see sub-clause 7.1.2.3). After the reaction time specified in 3GPP TS 05.10 no other RLC data blocks shall contain a TLLI field, except for those retransmitted RLC data blocks that originally contained a TLLI, which will be repeated including the same TLLI (see sub-clause 7.1.2.3a). The TLLI_BLOCK_CHANNEL_CODING parameter in the PACKET UPLINK ASSIGNMENT message indicates whether a RLC data block containing a TLLI field in the RLC data block header shall be encoded using CS‑1, or correspondingly MCS-1 in EGPRS TBF mode, or using the commanded modulation and channel coding scheme (see 3GPP TS 05.03). In GPRS TBF mode, the mobile station shall send all other RLC data blocks using the commanded channel coding scheme.

In EGPRS TBF mode, RLC data blocks that are transmitted for the first time shall be transmitted with the commanded MCS, except if the commanded mode is MCS-5-7, in which case the data block shall be transmitted with MCS‑5, or if the commanded mode is MCS-6-9, in which case the data block shall be transmitted with MCS-6. In EGPRS TBF mode, a MS may choose an alternate MCS than the one commanded, for the initial transmission of the last RLC data blocks of the TBF under the following conditions:

– The alternate MCS is more robust than the commanded MCS;

– The alternate MCS has already been commanded by the network during the TBF or was available for selection by the MS during the TBF according to the MCS selection rules for retransmissions; and

– The TBF requires no more radio blocks for initial transmission of the RLC data blocks using the alternate MCS than would be required when using the commanded MCS.

A RESEGMENT bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT and PACKET TIMESLOT RECONFIGURE messages. For initial transmissions of new RLC blocks the channel coding commanded is applied. The RESEGMENT bit is used to set the ARQ mode to type I or type II (incremental redundancy) for uplink TBFs. For retransmissions, setting the RESEGMENT bit to ‘1’ (type I ARQ) requires the mobile station to use an MCS within the same family as the initial transmission and the payload may be split (refer to table 5.5.2.1.4.1). For retransmissions, setting the RESEGMENT bit to ‘0’ (type II ARQ) requires the mobile station to use an MCS within the same family as the initial transmission without splitting the payload even if the network has commanded it to use MCS‑1, MCS‑2 or MCS‑3 for subsequent RLC blocks (refer to table 8.1.1.1), see note.

NOTE: This bit is particularly useful for networks with uplink IR capability since it allows combining on retransmissions.

Table 8.1.1.1: Choice of MCS for retransmissions with re-segmentation

Scheme used for initial transmission

Scheme to use for retransmissions after switching to a different MCS

MCS-9 Commanded

MCS-8 Commanded

MCS-7 Commanded

MCS-6-9 Commanded

MCS-6 Commanded

MCS-5-7 Commanded

MCS-5 Commanded

MCS-4 Commanded

MCS-3 Commanded

MCS-2 Commanded

MCS-1 Commanded

MCS-9

MCS-9

MCS-6

MCS-6

MCS-6

MCS-6

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-8

MCS-8

MCS-8

MCS-6
(pad)

MCS-6
(pad)

MCS-6
(pad)

MCS-3
(pad)

MCS-3
(pad)

MCS-3
(pad)

MCS-3
(pad)

MCS-3
pad)

MCS-3
(pad)

MCS-7

MCS-7

MCS-7

MCS-7

MCS-5

MCS-5

MCS-5

MCS-5

MCS-2

MCS-2

MCS-2

MCS-2

MCS-6

MCS-9

MCS-6

MCS-6

MCS-9

MCS-6

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-5

MCS-7

MCS-7

MCS-7

MCS-5

MCS-5

MCS-7

MCS-5

MCS-2

MCS-2

MCS-2

MCS-2

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-1

MCS-1

MCS-1

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

Table 8.1.1.1: MCS to use for retransmissions when re-segmentation (RESEGMENT bit set to ‘1’) is carried out (specified as a function of the scheme used for the initial transmission).

Table 8.1.1.2: Choice of MCS for retransmissions without re-segmentation

Scheme used for

Initial transmission

Scheme to use for retransmissions after switching to a different MCS

MCS-9

Commanded

MCS-8

Commanded

MCS-7

Commanded

MCS-6-9 Commanded

MCS-6

Commanded

MCS-5-7 Commanded

MCS-5

Commanded

MCS-4

Commanded

MCS-3

Commanded

MCS-2

Commanded

MCS-1

Commanded

MCS-9

MCS-9

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-8

MCS-8

MCS-8

MCS-6

(pad)

MCS-6

(pad)

MCS-6

(pad)

MCS-6

(pad)

MCS-6

(pad)

MCS-6

(pad)

MCS-6

(pad)

MCS-6

(pad)

MCS-6

(pad)

MCS-7

MCS-7

MCS-7

MCS-7

MCS-5

MCS-5

MCS-5

MCS-5

MCS-5

MCS-5

MCS-5

MCS-5

MCS-6

MCS-9

MCS-6

MCS-6

MCS-9

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-6

MCS-5

MCS-7

MCS-7

MCS-7

MCS-5

MCS-5

MCS-7

MCS-5

MCS-5

MCS-5

MCS-5

MCS-5

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-4

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-3

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-2

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

MCS-1

Table 8.1.1.2: MCS to use for retransmissions when re-segmentation is not (RESEGMENT bit set to ‘0’) allowed (specified as a function of the scheme used for the initial transmission).

If these rules require a transmission (either original transmission or retransmission) in a) MCS-7 or b) MCS-8 or MCS-9, but there is only one RLC block that can be transmitted in that MCS, the MS shall send that block in either MCS-5 for case a) or MCS-6 for case b).

Upon receipt of a command from the network to change channel coding scheme, the mobile station shall react in accordance with the time specified in 3GPP TS 05.10.

Upon receipt of any message containing an uplink assignment (e.g., PACKET UPLINK ASSIGNMENT, TIMESLOT RECONFIGURE or PACKET UPLINK ACK/NACK message), the mobile station shall be ready to transmit in accordance with the requirements given in 3GPP TS 05.10.

The mobile station shall transmit RLC/MAC blocks with the following priority:

– RLC/MAC control blocks, except Packet Uplink Dummy Control Blocks;

– RLC data blocks;

– RLC/MAC control blocks containing Packet Uplink Dummy Control Blocks.

During the TBF, if the countdown procedure has not started, the mobile station shall ask for new or different radio resources, by sending a PACKET RESOURCE REQUEST message (sub-clauses 8.1.1.1.2 and 8.1.1.3.2), in the following cases;

– When the mobile station has more blocks to send than indicated in the PACKET CHANNEL REQUEST message with access type short access;

– When the mobile station has indicated Page Response, Cell update or Mobility Management procedure as access type in the PACKET CHANNEL REQUEST and it has data to send;

– When the mobile station has data to send with a lower priority than indicated in the PACKET CHANNEL REQUEST message;

– When the mobile station has indicated ‘Signalling’ as access type in the EGPRS PACKET CHANNEL REQUEST and it has data to send.

8.1.1.1 Dynamic allocation uplink RLC data block transfer

This sub-clause specifies mobile station behaviour for dynamic allocation uplink RLC data block transfer while in packet transfer mode or dual transfer mode.

When the mobile station receives a uplink assignment that does not contain a TBF starting time, the mobile station shall begin monitoring the assigned PDCHs for the assigned USF value for each assigned PDCH within the reaction time defined in 3GPP TS 05.10. If a TBF starting time information element is present and no uplink TBF is in progress, but a downlink TBF is in progress, the mobile station shall wait until the starting time before beginning to monitor the USFs. While waiting for the starting time, the mobile station shall monitor the assigned PDCHs. If an uplink TBF is already in progress, the mobile station shall continue to use the assigned parameters of the uplink TBF until the TDMA frame number indicated by the TBF starting time occurs, at which time the mobile station shall immediately begin to use the newly assigned uplink TBF parameters. If while waiting for the frame number indicated by the TBF starting time the mobile station receives another uplink assignment, the mobile station shall act upon the most recently received uplink assignment and shall ignore the previous uplink assignment.

If the uplink assignment (e.g., PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) message contains the RLC_DATA_BLOCKS_GRANTED field, the TBF is a close-ended TBF. Otherwise the TBF is open-ended.

During a close-ended TBF the mobile station shall transmit at the most the number of RLC data blocks indicated in the RLC_DATA_BLOCKS_GRANTED field. In the case the access type in Channel Request was ‘Short Access’ (see 7.1.2), only the number of RLC data blocks requested in the Channel Request are allowed to be transmitted within the TBF, unless additional resources have been requested and assigned before the countdown procedure has started. Transmission of RLC/MAC control blocks and retransmissions of RLC data blocks do not count toward the limit. When the mobile station nears the end of the close-ended TBF, it shall begin the count down procedure so that it sends the last RLC data block when CV = 0 (see sub-clause 9.3.1). The mobile station and network shall then follow the appropriate procedure for release of TBF defined in sub-clause 9.3.2.3 or sub-clause 9.3.3.3. Upon receipt of a PACKET TBF RELEASE message during a closed-end TBF, the mobile station shall follow the procedure in sub-clause 8.1.1.4. If the number of RLC data blocks granted is not sufficient to empty the mobile station’s send buffer, the mobile station shall attempt to establish a new uplink TBF for the transmission of the outstanding LLC frames following the end of the close-ended TBF.

Whenever the mobile station detects an assigned USF value on an assigned PDCH, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH. The time relation between an uplink block, which the mobile station shall use for transmission, and the occurrence of the USF value is defined in 3GPP TS 05.02. The number of RLC/MAC blocks to transmit is controlled by the USF_GRANULARITY parameter characterising the uplink TBF.

When the mobile station transmits an RLC/MAC block to the network, it shall start timer T3180. When the mobile station detects an assigned USF value on an assigned PDCH, the mobile station shall restart timer T3180. If timer T3180 expires, the mobile station shall perform the abnormal release with access retry procedure (see sub-clause 8.7.2).

Whenever the network receives a valid RLC/MAC block from the mobile station, it shall reset counter N3101. The network shall increment counter N3101 for each radio block, allocated to that mobile station, for which no data is received. If N3101 = N3101max, the network shall stop the scheduling of RLC/MAC blocks from the mobile station and start timer T3169. When T3169 expires, the network may reuse the USF and TFI.

8.1.1.1.1 PACCH operation

The mobile station shall attempt to decode every downlink RLC/MAC block on all assigned PDCHs. 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.

Whenever the mobile station detects an assigned USF value on any assigned PDCH, the mobile station may transmit a PACCH block on the same PDCH in the next block period (see 3GPP TS 05.02). The mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see sub-clause 10.4.4).

8.1.1.1.2 Resource Reallocation for Uplink

The mobile station and the network are not allowed to change the RLC mode nor TBF mode of an already established TBF during resource reallocation. Change of RLC mode or TBF mode shall be achieved through release of on-going TBF and establishment of a new TBF with the newly requested RLC mode or TBF mode.

During an uplink packet transfer, upper layers may request to transfer another LLC PDU with a different PFI, a different Radio Priority, a different peak throughput class or a different RLC mode than the one which is in transfer. An LLC PDU containing signalling shall be treated as having the highest Radio Priority, and the acknowledged RLC mode shall be used.

If the mobile station has not started the countdown procedure and the new LLC PDU has the same RLC mode as the current uplink TBF and either a higher radio priority or the same radio priority but a higher peak throughput class, the mobile station shall immediately request a resource reallocation for uplink according to the new Radio Priority and peak throughput class of the new LLC PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168. Then the mobile station shall complete the transmission of the current LLC PDU.

If the new LLC PDU has the same RLC mode as the current uplink TBF and either a lower Radio Priority or the same radio priority but a lower peak throughput class, the mobile station shall first complete the sending of the LLC PDU in transfer. When the sending of LLC PDUs at the higher Radio Priority or the same radio priority but higher peak throughput class stops, without waiting for the acknowledgement from the network if in RLC acknowledged mode, the mobile station shall then perform the request of a resource reallocation for uplink for any remaining LLC PDU(s) by sending a PACKET RESOURCE REQUEST message on the PACCH and start timer T3168.

If the new LLC PDU does not have the same RLC mode as the current uplink TBF but has a higher radio priority, the mobile station shall complete the transmission of the current LLC PDU using the countdown procedure including acknowledgement from the network, if in RLC acknowledged mode. The mobile station shall then release the TBF and establish a new uplink TBF for transmission of the new LLC PDU. When the sending of LLC PDUs with a higher radio priority is completed using the countdown procedure, including acknowledgement from the network if in RLC acknowledged mode, the mobile station shall try to establish an uplink TBF for the transmission of any remaining LLC PDU(s).

If the mobile station has not started the countdown procedure and the new LLC PDU does not have the same PFI as the current uplink TBF, the mobile station shall immediately request a resource reallocation for uplink with the new PFI by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168. Then the mobile station shall complete the transmission of the current LLC PDU.

On receipt of the PACKET RESOURCE REQUEST the network shall respond by sending a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE or a PACKET ACCESS REJECT message to the mobile station on the downlink PACCH.

After the transmission of the PACKET RESOURCE REQUEST message with the reason for changing PFI, the priority or peak throughput class of an assigned uplink TBF the mobile station shall continue to use the currently assigned uplink TBF assuming that the requested priority or peak throughput class is already assigned to that TBF.

On receipt of a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message the mobile station shall stop timer T3168 and switch to the assigned PDCHs.

The mobile station is then not allowed to send new PACKET RESOURCE REQUEST messages until either a new packet transfer request is received from the upper layers or when sending of LLC PDU(s) at a lower Radio Priority has to be continued.

On expiry of timer T3168 the mobile station shall retransmit the PACKET RESOURCE REQUEST message unless the PACKET RESOURCE REQUEST has already been transmitted four times in which case the mobile station shall indicate a packet access failure to upper layer and perform an abnormal release without retry (see sub-clause 8.7.1).

If no PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message is received before the mobile station has completed its currently assigned TBFs the mobile station shall stop timer T3168.

The network may at any time during the uplink TBF initiate a change of resources by sending on the downlink PACCH monitored by the MS, an unsolicited PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message to the mobile station. During the reallocation TFI is allowed to be changed.

On receipt of a PACKET ACCESS REJECT message , the mobile station shall stop timer T3168 if running, and abort the uplink TBF and indicate a packet access failure to upper layer. If no downlink TBF exists, the mobile station in packet transfer mode shall return to packet idle mode; the mobile station in dual transfer mode shall return to dedicated mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5.

If the PACKET ACCESS REJECT message contains a WAIT_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall

– start timer T3172 and if the mobile station has additional RLC data blocks to transmit, it shall initiate a new uplink TBF establishment, but the mobile station is not allowed to make a new attempt for an uplink TBG establishment in the same cell until timer T3172 expires, it may, however, attempt an uplink TBG establishment in an other cell after successful cell reselection. The mobile station may attempt to enter the dedicated mode in the same cell before timer T3172 has expired. During the time T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging request to trigger RR connection establishment.

The value of the WAIT_INDICATION field (i.e. timer T3172) relates to the cell from which it was received.

8.1.1.1.2.1 Abnormal cases

The following abnormal cases apply:

– if the mobile station receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message and detects an invalid Frequency Parameters information element in the message, the mobile station shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information.

– if the mobile station receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message specifying frequencies that are not all in one frequency band then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– if the mobile station receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message assigning fixed allocation MAC mode, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information in the PACKET UPLINK ASSIGNMENT does not properly specify an uplink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify an uplink and downlink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– if the mobile station receives a PACKET UPLINK ASSIGNMENT message containing a Frequency Parameters information element specifying a frequency that is in a frequency band not supported by the mobile station then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a mobile station in dual transfer mode receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

NOTE: A PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message received by a multi-band mobile station shall not be considered invalid if it indicates new frequencies that are all in a different frequency band to that of the PDCH(s) on which the assignment was received. The assignment may however be rendered invalid for some other reason.

8.1.1.1.3 Establishment of Downlink TBF

During uplink transfer, the network may initiate a downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT message, or a PACKET TIMESLOT RECONFIGURE, to the mobile station on the PACCH. If a PACKET TIMESLOT RECONFIGURE message is sent, then the message shall contain the DOWNLINK_TFI_ASSIGNMENT field. The multislot restrictions of the mobile station shall be observed.

A mobile allocation or reference frequency list, received as part of a downlink assignment, replaces the previous parameters and shall be used until a new assignment is received or the mobile station has released all TBFs.

The downlink radio resource is assigned to the mobile station in a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message. On receipt of an assignment message, and after the TBF starting time, if present, the mobile station shall switch to the assigned PDCHs, and start timer T3190. The operation of the downlink TBF follows the procedures in sub-clause 8.1.2 with the following additions:

– the mobile station shall prioritise transmission of RLC/MAC control blocks associated with the downlink TBF over RLC/MAC control blocks associated with the uplink TBF;

– if a timer or counter expiry causes the uplink TBF to be aborted in the mobile station, the mobile station shall also abort the downlink TBF and perform an abnormal release with access retry (see sub-clause 8.7.2).

– If uplink and downlink TBFs are already established, then the network may send a PACKET TIMESLOT RECONFIGURE message without DOWNLINK_TFI_ASSIGNMENT. The mobile station shall interpret this as a reassignment of the timeslot allocations of the concurrent uplink and downlink TBFs and the downlink TFI is not changed.

8.1.1.1.3.1 Abnormal cases

If a failure occurs on the mobile station side before the new TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions:

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify an uplink and downlink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If uplink and downlink TBFs are not already established and the PACKET TIMESLOT RECONFIGURE message does not include a DOWNLINK_TFI_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a mobile station in dual transfer mode receives a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET TIMESLOT RECONFIGURE is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET DOWNLINK ASSIGNMENT is due to any reason, the mobile station shall abort the procedure and continue the normal operation of the uplink TBF.

8.1.1.2 Extended Dynamic Allocation uplink RLC data block transfer

The Extended Dynamic Allocation medium access method extends the Dynamic Allocation medium access method to allow higher uplink throughput.

This sub-clause defines the extensions to the Dynamic Allocation medium access method. All procedures defined in sub-clause 8.1.1.1 apply, except where this sub-clause defines a new procedure. In cases where this sub-clause conflicts with sub-clause 8.1.1.1, this sub-clause takes precedence.

8.1.1.2.1 Uplink PDCH Allocation

The PACKET UPLINK ASSIGNMENT message allocates to the mobile station a subset of 1 to N PDCHs, where N depends on the MSs multislot class.

The mobile station shall monitor its assigned PDCHs starting with the lowest numbered PDCH, then the next lowest numbered PDCH, etc. Whenever the mobile station detects an assigned USF value on an assigned PDCH, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH and all higher numbered assigned PDCHs. The time relation between an uplink block, which the mobile station shall use for transmission, and the occurrence of the USF value is defined in 3GPP TS 05.02. The number of RLC/MAC blocks to transmit on each PDCH is controlled by the USF_GRANULARITY parameter characterising the uplink TBF. The mobile station need not monitor and shall disregard the USF on those higher numbered PDCHs during the block period where the assigned USF value is detected and the block period(s) in which the mobile station obtains permission to transmit.

If the network reduces the number of PDCHs allocated to a mobile station per block period, the network shall not allocate any resources to that mobile station for one block period following the block period with the higher number of PDCHs allocated.

When an uplink radio block is allocated on a PDCH via the polling mechanism (see sub-clause 10.4.4), the mobile station shall monitor the USF on that PDCH but need not monitor USF on the subsequent (higher numbered) PDCHs during the same block period.

8.1.1.2.2 PACCH operation

The mobile station shall attempt to decode every downlink RLC/MAC block on the lowest numbered timeslot in the PDCH allocation. 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.

The network shall transmit all PACCH messages on the PDCH carried on the lowest numbered timeslot in the allocation.

Whenever the mobile station detects an assigned USF value on any assigned PDCH, the mobile station may transmit a PACCH block on the same PDCH in the next block period. The mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see sub-clause 10.4.4).

8.1.1.2.3 Neighbour cell power measurements

The mobile station shall perform neighbour cell measurements during any unused PDCH or group of unused PDCHs where the MS’s Measurement Capabilities indicate that the mobile station is capable of making a neighbour cell measurement.

The network shall ensure that there are sufficient gaps as to allow the necessary number of measurements based upon the MS’s Measurement Capabilities.

8.1.1.3 Fixed Allocation uplink RLC data block transfer

A fixed allocation TBF can be operated as a close-ended TBF or as an open-ended TBF. A close-ended TBF occurs when the MS sends a PACKET RESOURCE REQUEST or PACKET DOWNLINK ACK/NACK message containing an RLC_OCTET_COUNT field that contains a value different from ‘0’. An open-ended TBF occurs when the RLC_OCTET_COUNT field contains the value ‘0’.

A close-ended TBF transfers the number of octets specified in the RLC_OCTET_COUNT field. The mobile station shall signal the number of RLC data octets plus the number of RLC data block length octets to be transferred. The MS is allowed to exceed the requested value only for the extra octets needed for LLC boundaries. The network will automatically provide sufficient resources for the number of octets requested. The mobile station does not need to send further PACKET RESOURCE REQUEST messages to the network. If the mobile station sends a subsequent PACKET RESOURCE REQUEST message to the network, the TBF becomes an open-ended TBF. A close-ended TBF may be ended by the network before the number of requested octets has been transferred. In this case the TBF ends when the network sends a FINAL_ALLOCATION indication in a fixed allocation assignment message or a PACKET ACCESS REJECT message to the mobile station

An open-ended TBF transfers an arbitrary number of octets. The mobile station is required to send a PACKET RESOURCE REQUEST message for each fixed allocation. Each time the mobile station receives a fixed allocation, if it wishes to continue the TBF, it must then send another PACKET RESOURCE REQUEST to the network. The open-ended TBF ends when the network sends a FINAL_ALLOCATION indication in a fixed allocation assignment message or a PACKET ACCESS REJECT message to the mobile station, or when the mobile has exhausted its supply of data to be transmitted and has executed the countdown procedure.

In a one phase access, the TBF shall be operated as an open-ended TBF.

8.1.1.3.1 Transfer of RLC/MAC blocks

The PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message contains a Fixed Allocation struct when signalling a fixed allocation.

The TIMESLOT_ALLOCATION shall assign from 1 to 8 PDCHs to the fixed allocation. The multislot restrictions of the mobile station shall be observed.

If the BLOCKS_OR_BLOCK_PERIODS field indicates blocks, then the bits in the ALLOCATION_BITMAP correspond to radio blocks. Bits are included in the bitmap only for radio blocks on assigned PDCHs. Each bit in the bitmap indicates whether the corresponding radio block is assigned to the fixed allocation. The mobile station shall transmit an RLC/MAC block in each radio block assigned by the ALLOCATION_BITMAP. If the number of bits in the ALLOCATION_BITMAP is not an integral multiple of the number of timeslots assigned in the TIMESLOT_ALLOCATION field, then the mobile station shall add to the end of the bitmap (bit number indexes < 0, see sub-clause 12.4) the minimum number of bits needed to form an integral multiple of the number of assigned timeslots, with the value set to ‘0’.

If the BLOCKS_OR_BLOCK_PERIODS field indicates block periods, then the bits in the bitmap indicate which block periods are assigned to the allocation. The mobile station shall transmit an RLC/MAC block on each timeslot assigned in the TIMESLOT_ALLOCATION field in each block period assigned to the allocation.

The ALLOCATION_BITMAP_LENGTH field, if present, indicates the length of the ALLOCATION_BITMAP field. If not present, the ALLOCATION_BITMAP continues until the end of the message.

The network shall acknowledge packet transfers by sending PACKET UPLINK ACK/NACK messages on the PACCH during gaps in the uplink allocation. The network shall allocate additional resources for the retransmissions with a PACKET UPLINK ACK/NACK or an unsolicited PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message. The mobile station shall not request resources or adjust its RLC_OCTET_COUNT for retransmissions requested in the PACKET UPLINK ACK/NACK (see sub-clause 8.1.1.3.2). The mobile station may retransmit erroneous blocks in any allocated uplink block.

During a close-ended TBF the network automatically sends sufficient fixed allocation resources for the mobile station to transmit the number of octets specified in the RLC_OCTET_COUNT of the initial PACKET RESOURCE REQUEST or PACKET_DOWNLINK ACK/NACK message. The network signals the end of the close-ended TBF to the mobile by setting the FINAL_ALLOCATION bit to ‘1’ in the PACKET UPLINK ASSIGNMENT, the PACKET TIMESLOT RECONFIGURE, or the PACKET UPLINK ACK/NACK, or by sending the PACKET ACCESS REJECT message or the PACKET TBF RELEASE message to the mobile station.

Upon receipt of a uplink assignment containing a fixed allocation and with the field FINAL_ALLOCATION set to 1, the mobile station shall execute the countdown procedure such that the countdown ends before the current allocation is exhausted.

Upon receipt of a PACKET ACCESS REJECT message, the mobile station shall release the TBF using the procedures in 9.3.2.3 or 9.3.3.3, such that the countdown ends within the current allocation. Then, if the mobile station has additional RLC data blocks to transfer, it shall initiate a new uplink TBG establishment.

Upon receipt of a PACKET TBF RELEASE message, the mobile station shall follow the procedure in sub-clause 8.1.1.4.

During a close-ended TBF the mobile station may change the Radio Priority of the TBF or extend the TBF by sending a PACKET RESOURCE REQUEST message or a PACKET DOWNLINK ACK/NACK containing a Channel Request Description IE. The close-ended TBF then becomes an open-ended TBF and the procedures in sub-clause 8.1.1.3.2 apply.

8.1.1.3.2 Reallocation for open-ended TBF

The mobile station and the network are not allowed to change the RLC mode nor TBF mode of an already established TBF during resource reallocation. Change of RLC mode or TBF mode shall be achieved through release of on-going TBF and establishment of a new TBF with the newly requested RLC mode or TBF mode.

During an uplink packet transfer, upper layers may request to transfer another LLC PDU with a different PFI, a different Radio Priority, a different peak throughput class or a different RLC mode than the one which is in transfer. An LLC PDU containing signalling shall be treated as having the highest Radio Priority, and the acknowledged RLC mode shall be used.

If the mobile station has not started the countdown procedure and the new LLC PDU has the same RLC mode as the current uplink TBF and either a higher radio priority or the same radio priority but a higher peak throughput class, the mobile station shall immediately request a resource reallocation for uplink according to the new Radio Priority and peak throughput class of the new LLC PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168. Then the mobile station shall complete the transmission of the current LLC PDU. If the new LLC PDU has the same RLC mode as the current uplink TBF and either a lower Radio Priority or the same radio priority but a lower peak throughput class, the mobile station shall first complete the sending of the LLC PDU in transfer. When the sending of LLC PDUs at the higher Radio Priority or the same radio priority but higher peak throughput class stops, without waiting for the acknowledgement from the network if in RLC acknowledged mode, the mobile station shall then perform the request of a resource reallocation for uplink for any remaining LLC PDU(s) by sending a PACKET RESOURCE REQUEST message on the PACCH and start timer T3168.

If the new LLC PDU does not have the same RLC mode as the current uplink TBF but has a higher radio priority, the mobile station shall complete the transmission of the current LLC PDU using the countdown procedure including acknowledgement from the network, if in RLC acknowledged mode. The mobile station shall then release the TBF and establish a new uplink TBF for transmission of the new LLC PDU. When the sending of LLC PDUs with a higher radio priority is completed using the countdown procedure, including acknowledgement from the network if in RLC acknowledged mode, the mobile station shall try to establish an uplink TBF for the transmission of any remaining LLC PDU(s).

If the mobile station has not started the countdown procedure and the new LLC PDU does not have the same PFI as the current uplink TBF, the mobile station shall immediately request a resource reallocation for uplink with the new PFI by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168. Then the mobile station shall complete the transmission of the current LLC PDU.

On receipt of the PACKET RESOURCE REQUEST the network shall respond by sending a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE or a PACKET ACCESS REJECT message to the mobile station on the downlink PACCH.

After the transmission of the PACKET RESOURCE REQUEST message with the reason for changing PFI, the priority or peak throughput class of an assigned uplink TBF the mobile station shall continue to use the currently assigned uplink TBF assuming that the requested priority or peak throughput class is already assigned to that TBF.

On receipt of a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message the mobile station shall stop timer T3168 and switch to the assigned PDCHs.

The mobile station is then not allowed to send new PACKET RESOURCE REQUEST messages until either a new packet transfer request is received from the upper layers or when sending of LLC PDU(s) at a lower Radio Priority has to be continued.

On expiry of timer T3168, the mobile station shall retransmit the PACKET RESOURCE REQUEST message unless the PACKET RESOURCE REQUEST message has already been transmitted four times. In that case, the mobile station shall indicate packet access failure to upper layer and perform an abnormal release without retry (see sub-clause 8.7.1).

If no PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message is received before the mobile station has completed its currently assigned TBFs the mobile station shall stop timer T3168.

The network may at any time during the uplink TBF initiate a change of resources by sending on the downlink PACCH monitored by the MS, an unsolicited PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE, or an uplink resource reassignment in a PACKET UPLINK ACK/NACK message to the mobile station. During the reallocation TFI is allowed to be changed.

On receipt of a PACKET ACCESS REJECT message, the mobile station shall stop timer T3168 if running, abort the uplink TBF and indicate a packet access failure to upper layer. If no downlink TBF exists, the mobile station in packet transfer mode shall return to packet idle mode; the mobile station in dual transfer mode shall return to dedicated mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5.

If the PACKET ACCESS REJECT message contains a WAIT_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall:

– start timer T3172 and if the mobile station has additional RLC data blocks to transmit, it shall initiate a new uplink TBF establishment, but the mobile station is not allowed to make a new attempt for an uplink TBF establishment in the same cell until timer T3172 expires, it may, however, attempt an uplink TBF establishment in an other cell after successful cell reselection. The mobile station may attempt to enter the dedicated mode in the same cell before timer T3172 has expired. During the time T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging request to trigger RR connection establishment.

The value of the WAIT_INDICATION field (i.e. timer T3172) relates to the cell from which it was received.

8.1.1.3.2.1 At the beginning of each fixed allocation

At the beginning of each allocation of an open-ended TBF the mobile station shall either request to continue the TBF by transmitting a PACKET RESOURCE REQUEST or a PACKET DOWNLINK ACK/NACK containing a Channel Request Description IE message on the uplink PACCH, or the mobile station shall begin the countdown procedure so that it ends within the current allocation.

The mobile station shall signal the number of RLC data octets ready to transmit, plus the number of RLC data block length octets ready to transmit, in the RLC_OCTET_COUNT field of the PACKET RESOURCE REQUEST or PACKET DOWNLINK ACK/NACK message. The mobile station shall always indicate the current state of its transmit buffer at the time the message is sent. In RLC acknowledged mode, previously transmitted but currently unacknowledged octets shall not be included in the RLC_OCTET_COUNT.

8.1.1.3.2.2 Upon receipt of the reallocation request

Upon receipt of the PACKET RESOURCE REQUEST or PACKET DOWNLINK ACK/NACK with a Channel Request Description IE, the network shall continue the TBF by sending a PACKET UPLINK ASSIGNMENT or PACKET UPLINK ACK/NACK containing a fixed allocation to the mobile station, or shall end the TBF by sending a PACKET ACCESS REJECT message. Alternatively, the network may end the TBF by sending an uplink assignment containing a fixed allocation with the FINAL_ALLOCATION bit set to 1.

Upon receipt of a uplink assignment containing an ALLOCATION_BITMAP, the mobile station shall begin transmitting on the new resources at the indicated TBF Starting Time. If there is a conflict between a previous allocation and the new allocation, the new allocation shall take precedence.

Upon receipt of a PACKET UPLINK ACK/NACK with a REPEAT_ALLOCATION, the mobile station shall start a new allocation when the current allocation ends. This new allocation shall begin immediately after the current allocation ends and shall use the most recently received ALLOCATION_BITMAP. If the mobile station receives multiple PACKET UPLINK ACK/NACK messages with REPEAT_ALLOCATION during an allocation, the mobile shall repeat the ALLOCATION_BITMAP only once. If the mobile receives a PACKET UPLINK ACK/NACK without the REPEAT_ALLOCATION indication, the mobile station shall transmit to the end of its current allocation without repeating the allocation, regardless of any previous REPEAT_ALLOCATION indications that may have been received.

The network may also specify a TS_OVERRIDE indication in the PACKET UPLINK ACK/NACK. The TS_OVERRIDE applies to the next allocation after the current allocation expires. The TS_OVERRIDE field is a bitmap with a bit corresponding to each timeslot. For each bit set in the TS_OVERRIDE, the mobile shall disregard the ALLOCATION_BITMAP for that timeslot and shall transmit on all uplink radio blocks for that timeslot for the duration of the next allocation. If a bit is not set in the TS_OVERRIDE field, then the ALLOCATION_BITMAP shall apply to that timeslot.

8.1.1.3.2.3 Upon exhaustion of the current allocation

If the mobile station exhausts its assigned fixed allocation and has more RLC data blocks to transmit, it shall start timer T3188 and monitor the downlink of all assigned PDCHs. If the mobile station receives an assignment message containing a fixed allocation, the mobile station shall stop timer T3188 and use the new allocation at the assigned starting time.

If the mobile station receives a PACKET UPLINK ACK/NACK with a REPEAT ALLOCATION after its current allocation has been exhausted, it shall stop timer T3188, wait until the next repeated allocation boundary and then begin transmitting using the repeated ALLOCATION_BITMAP.

If timer T3188 expires, the mobile station shall perform an abnormal release with access retry (see 8.7.2).

8.1.1.3.2.4 Ending the TBF

Upon receipt of a PACKET ACCESS REJECT message, the mobile station shall stop timer T3188, if running, release the TBF using the procedures in 9.3.2.3 or 9.3.3.3, such that the countdown ends within the current allocation. Then, if the mobile station has additional RLC data blocks to transfer, it shall initiate a new uplink TBF establishment.

Upon receipt of a uplink assignment containing a fixed allocation and with the field FINAL_ALLOCATION set to 1, the mobile station shall execute the countdown procedure such that the countdown ends before the current allocation is exhausted.

8.1.1.3.2.5 Abnormal Cases

The following abnormal cases apply:

– If the mobile station receives an assignment message containing an allocation other than a fixed allocation, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information in the PACKET UPLINK ASSIGNMENT does not properly specify an uplink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify an uplink and downlink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a mobile station receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message and detects an invalid Frequency Parameters information element in the message, the mobile station shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information.

– if the mobile station receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message specifying frequencies that are not all in one band then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a mobile station in dual transfer mode receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

NOTE: A PACKET UPLINK ASSIGNMENT message received by a multi-band mobile station shall not be considered invalid if it indicates new frequencies that are all in a different frequency band to that of the PDCH(s) on which the assignment was received. The assignment may however be rendered invalid for some other reason.

8.1.1.3.3 Neighbour cell power measurements

The mobile station shall signal its measurement capabilities in the PACKET resource request message.

If the multislot capabilities and the assigned multislot configuration (see 3GPP TS 05.02) would prevent the mobile station from making normal neighbour cell power measurement according to 3GPP TS 05.08, the network shall leave sufficient gaps in the uplink allocation bitmap to allow the mobile station to make the required neighbour cell power measurements.

The mobile station shall make neighbour cell power measurements whenever a sufficient gap is available according to its Measurement Capabilities. If normal monitoring of downlink PACCH is not possible (see sub-clause 8.1.1.3.4), PACCH monitoring in the gaps shall take precedence over the measurements, but any remaining part of a gap shall be used for measurements if possible.

8.1.1.3.4 PACCH operation

A mobile station shall monitor one PDCH in the allocation for downlink PACCH The network shall indicate that PDCH on uplink resource assignment (DOWNLINK_CONTROL_TIMESLOT parameter). DOWNLINK_CONTROL_TIMESLOT parameter shall always indicate a timeslot number that is used for TBF uplink and, if possible, according to mobile station’s multislot class.

If, for a multislot class type 1 mobile station, the multislot capabilities and the assigned multislot configuration (see 3GPP TS 05.02) would prevent the mobile station from monitoring all PACCH blocks, it shall monitor PACCH whenever a sufficient gap in the allocation is available according to its multislot capabilities.

The network shall leave such sets of gaps in the uplink fixed allocation for the purpose of transmission of the downlink PACCH.

A multislot class type 2 mobile station shall monitor all assigned PDCHs for PACCH, unless the mobile station also has current downlink TBF, in which case PDCH assigned for the downlink TBF shall take precedence.

After the fixed allocation is exhausted, the mobile station shall continue to monitor all assigned PDCH(s) that it is able to monitor according to its multislot class.

In the case of simultaneous uplink and downlink TBFs, the mobile station shall monitor all assigned downlink PDCHs and any uplink PDCHs it is able to monitor.

The mobile station may transmit a PACCH block on any uplink radio block allocated via the ALLOCATION_BITMAP.

In the case of simultaneous uplink and downlink TBFs, the mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see sub-clause 10.4.4).

8.1.1.3.5 Establishment of Downlink TBF

During an uplink fixed allocation TBF, the network may initiate a downlink TBF by sending the PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message on the PACCH.

The downlink radio resource is assigned to the mobile station in a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message. The assigned timeslot configuration of the simultaneous uplink and downlink TBF must be compliant with the mobile station’s multislot class, and must allow the performing of neighbour cell power measurements as described in 8.1.2.7.

On receipt of an assignment message the mobile station shall follow the procedure below.

If a mobile station is not assigned to operate in half duplex mode the network may send a PACKET TIMESLOT RECONFIGURE message. If a PACKET TIMESLOT RECONFIGURE message is sent, then the message shall contain the DOWNLINK_TFI_ASSIGNMENT field.

If the mobile station is not assigned to operate half duplex mode, the mobile station shall, after expiry of the TBF starting time, if present, act upon the downlink assignment, and start timer T3190.

If the mobile station is assigned to operate in half duplex mode, the network shall wait for the mobile station to finish its current uplink resource allocation, and for the TBF starting time to elapse, if present, before sending RLC data blocks on the downlink.

If the mobile station is operating the uplink TBF in half duplex mode and receives a PACKET TIMESLOT RECONFIGURE message it shall exit half duplex mode and act on the PACKET TIMESLOT RECONFIGURE.

Whenever a mobile station operating on an uplink TBF in half duplex mode receives a assignment on the PACCH the mobile station shall complete the currently assigned fixed allocation. If the uplink TBF is not completed the mobile station shall, after expiry of the TBF starting time, if present, or if the TBF starting time has already expired, save the RLC state variables associated with the uplink TBF and suspend and save the state of the following timers :

T3182 Wait for Acknowledgement

T3184 No Ack/Nack Received

T3188 Allocation Exhausted

Whenever a mobile station operating on an uplink TBF in half duplex mode receives a downlink assignment on the PACCH and has previously saved the state of the downlink TBF and has not since entered idle mode, the mobile station shall restore the saved downlink RLC state variables and timer values.

The mobile station shall then act upon the PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message.

8.1.1.3.5.1 Abnormal cases

If a failure occurs on the mobile station side before the new TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions:

– If the information available in the mobile station, after the reception of a PACKET DOWNLINK ASSIGNMENT message does not satisfactorily define a PDCH, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message.

– If a failure in the PACKET DOWNLINK ASSIGNMENT is due to any other reason, then the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT.

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify an uplink and downlink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the PACKET TIMESLOT RECONFIGURE does not include a DOWNLINK_TFI_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET TIMESLOT RECONFIGURE is due to any other reason, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the mobile station is not operating the uplink TBF in half duplex mode and receives a PACKET DOWNLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for the uplink TBF, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message and continue normal operation of the uplink TBF.

– If the mobile station is operating the uplink TBF in half duplex mode and receives a PACKET DOWNLINK ASSIGNMENT message that does not indicate half duplex mode, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT.

– If a mobile station in dual transfer mode receives a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the failure is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2).

8.1.1.3a Exclusive allocation RLC data block transfer

8.1.1.3a.1 General

This sub-clause specifies mobile station behaviour for exclusive allocation of radio resources for uplink RLC data block transfer. The exclusive allocation is applicable only in dual transfer mode (for half-rate PDCHs only). The conditions for using exclusive allocation are specified in sub-clause 8.1.0.

When the mobile station receives an uplink assignment that does not contain a TBF starting time, the mobile station shall switch to the assigned PDCHs and be ready to transmit within the reaction time defined in 3GPP TS 05.10. If a TBF starting time is present, the mobile station shall wait until the starting time before it switches to the assigned PDCHs and starts to transmit. If a TBF starting time is present and an uplink TBF is already in progress, the mobile station shall continue to use the previously assigned resources for the uplink TBF until the TBF starting time occurs. If the mobile station receives another uplink assignment, while waiting for the TBF starting time, the mobile station shall act upon the most recently received uplink assignment and shall ignore the previous one.

When mobile station has received the uplink assignment and granted the right to transmit using exclusive allocation, the mobile station shall start timer T3184 and transmit an RLC/MAC block in every uplink radio block on the PDCHs assigned for the TBF. The timer T3184 shall be restarted every time the mobile station receives a PACKET UPLINK ACK/NACK message.

The timer T3184 shall be stopped at the release of the TBF. The timer T3184 shall also be stopped if the resources for the TBF are reallocated, such that the conditions for exclusive allocation are no longer fulfilled and the TBF continues using dynamic or extended dynamic allocation (see sub-clause 8.1.0).

8.1.1.3a.2 Radio link failure

If timer T3184 expires (see sub-clause 8.1.1.3a.1), the mobile station shall regard that as a radio link failure and perform an abnormal release with access retry (see sub-clause 8.7.2).

The network shall increment counter N3101 for each radio block allocated to the mobile station for which no RLC/MAC block is received. Whenever the network receives an RLC/MAC block from the mobile station, it shall reset counter N3101. If N3101 reaches the value N3101max, the network shall stop sending PACKET UPLINK ACK/NACK messages to the mobile station and start timer T3169. If an RLC/MAC block is received from the mobile station when timer T3169 is running, the network shall stop timer T3169 and resume sending PACKET UPLINK ACK/NACK messages to the mobile station. When T3169 expires, the network may consider the TBF as released and reuse the TFI value.

8.1.1.3a.3 Open-ended and close-ended TBF

If the uplink assignment contains the RLC_DATA_BLOCKS_GRANTED field, the uplink TBF is a close-ended TBF. Otherwise the TBF is open-ended.

During a close-ended TBF, the mobile station shall transmit at the most the number of RLC data blocks indicated in the RLC_DATA_BLOCKS_GRANTED field. Transmission of RLC/MAC control blocks and retransmissions of RLC data blocks do not count towards the limit.

During an open-ended TBF, the mobile station may transmit the number of RLC data blocks that are required to empty the RLC/MAC send buffer.

When the mobile station nears the end of the uplink TBF, it shall begin the countdown procedure, so that it sends the last RLC data block when CV = 0 (see sub-clause 9.3.1), thereby terminating the last LLC PDU of the uplink TBF. The mobile station and network shall then follow the appropriate procedure for release of the uplink TBF, as defined in sub-clause 9.3.2.3 or sub-clause 9.3.3.3.

If the number of RLC data blocks granted during the uplink TBF is not sufficient to empty the RLC/MAC send buffer, the mobile station shall attempt to establish a new uplink TBF for the transmission of the remaining LLC PDUs after the release of the first uplink TBF.

8.1.1.3a.4 PACCH operation

The mobile station shall attempt to decode every downlink RLC/MAC block on the PDCH with the lowest timeslot number assigned for the uplink TBF. 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 is a distribution message or a non-distribution message that addresses the mobile station, the mobile station shall act on the message.

During the transmission on the uplink TBF, the mobile station may use any uplink RLC/MAC block, assigned for the uplink TBF, for the transmission of an RLC/MAC control block (PACCH). The mobile station shall not transmit an RLC data block in any uplink RLC/MAC block allocated to the mobile station via the polling mechanism (see sub-clause 10.4.4).

8.1.1.3a.5 Resource Reallocation for Uplink
8.1.1.3a.5.1 General

The reallocation of radio resources may take place during an uplink TBF, due to a change of service demand from the mobile station, or due to reasons determined by the network. This procedure shall not be used to change neither the RLC mode nor the TBF mode of the uplink TBF. A change of RLC mode or TBF mode shall be achieved through the release of the uplink TBF and establishment of a new TBF.

8.1.1.3a.5.2 Change of service demand

During an uplink packet transfer, upper layers may request the transfer an LLC PDU with a different PFI, a different radio priority, a different peak throughput class or a different RLC mode than the one, which is in transfer. In case of an LLC PDU containing signalling information, it shall be transferred with the highest radio priority and acknowledged RLC mode.

If the mobile station, at the change of service demand, has started the countdown procedure (see sub-clause 9.3.1) in order to release the uplink TBF, the mobile station shall perform the release of the uplink TBF as normal. The mobile station may then establish a new uplink TBF, according to the new service demand.

If the countdown procedure has not been started and the new LLC PDU shall be transferred with the same RLC mode as the current uplink TBF, the mobile station shall indicate a change of service demand to the network by sending a PACKET RESOURCE REQUEST message on PACCH.

If the change of service demand is a change pf PFI, an increase of the radio priority or the same radio priority but an increase of the peak throughput class, the PACKET RESOURCE REQUEST message shall be sent as early as possible. If the PFI is not changed and the change of service demand is a decrease of the radio priority or the same radio priority but a decrease of the peak throughput class, the PACKET RESOURCE REQUEST message shall be sent immediately before, or as early as possible following the first RLC data block that contains information with the new (lower) service demand. When the PACKET RESOURCE REQUEST message is sent, the mobile station shall start timer T3168.

If the new LLC PDU shall be transmitted with a different RLC mode than the current uplink TBF, the mobile station may complete the transmission of the preceding LLC PDUs and shall then release the TBF and establish a new uplink TBF for transmission of the new LLC PDU.

After the transmission of the PACKET RESOURCE REQUEST message, the mobile station shall continue to use the currently assigned uplink TBF, assuming that the network grants the requested service demand.

On receipt of the PACKET RESOURCE REQUEST message the network shall respond by either the reallocation of radio resources for an uplink TBF (sub-clause 8.1.1.3a.2.2) or the rejection of service demand (sub-clause 8.1.1.3a.2.3).

The mobile station shall stop timer T3168 at the receipt of a PACKET UPLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message, or when the mobile station has completed its currently assigned TBFs. If timer T3168 expires, the mobile station shall retransmit the PACKET RESOURCE REQUEST message and again start timer T3168.

8.1.1.3a.5.3 Reallocation of radio resources for an uplink TBF

The network may reallocate the radio resources for an uplink TBF by sending a PACKET UPLINK ASSIGNMENT message to the mobile station. If there is a concurrent downlink TBF and the radio resources for the downlink TBF are also affected, the network shall use a PACKET TIMESLOT RECONFIGURE message for the reallocation.

On receipt of the PACKET UPLINK ASSIGNMENT or the PACKET TIMESLOT RECONFIGURE message, the mobile station shall treat the message as an uplink assignment, as defined in sub-clause 8.1.1.3a. On receipt of the PACKET TIMESLOT RECONFIGURE message, the mobile station shall, in addition, treat the message as a downlink assignment, as defined in sub-clause 8.1.2.1.

8.1.1.3a.5.4 Rejection of new service demand

On the receipt of a PACKET RESOURCE REQUEST message from the mobile station indicating a change of service demand, the network may reject the service demand by sending a PACKET ACCESS REJECT message to the mobile station.

On receipt of the PACKET ACCESS REJECT message, the mobile station shall stop timer T3168 if running, abort the uplink TBF and indicate a packet access failure to upper layers. If no downlink TBF exists, the mobile station in dual transfer mode shall return to dedicated mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5.

The PACKET ACCESS REJECT message may contain a wait indication (i.e., the WAIT_INDICATION field) in the Reject structure addressed to the mobile station. In that case, the mobile station shall start timer T3172 with the indicated value. The mobile station shall not attempt to establish a new uplink TBF in the same cell while timer T3172 is running. If a successful cell reselection is performed, the mobile station shall stop timer T3172 and may establish an uplink TBF in the new cell.

While timer T3172 is running, the mobile station shall ignore any PACKET PAGING REQUEST message that may be received, except paging requests to trigger RR connection establishment.

8.1.1.3a.5.5 Abnormal cases

The following abnormal cases apply:

– If timer T3168 expires and the PACKET RESOURCE REQUEST message has already been transmitted four times, the mobile station shall indicate a packet access failure to upper layers and perform an abnormal release without retry (see sub-clause 8.7.1).

– If the mobile station receives a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

8.1.1.3a.6 Establishment of Downlink TBF
8.1.1.3a.6.1 General

During an uplink TBF using exclusive allocation, the network may initiate a downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message to the mobile station on the PACCH. The PACKET TIMESLOT RECONFIGURE message shall be used if the timeslot allocation for the on-going uplink TBF needs to be changed.

On receipt of the PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message, the mobile station shall switch to the assigned PDCHs. If the assigning message includes a TBF starting time, the mobile station shall first wait until the indicated starting time and then switch to the assigned PDCHs. If the assigning message does not include a TBF starting time, or the TBF starting time has already passed when the assigning message is received, the mobile station shall switch to the assigned PDCHs within the reaction time specified in 3GPP TS 05.10.

When the mobile station switches to the assigned PDCHs, it starts timer T3190. The operation of the downlink TBF then follows the procedures defined in sub-clause 8.1.2, with the following additions:

– The mobile station shall prioritise transmission of RLC/MAC control blocks associated with the downlink TBF over RLC/MAC control blocks associated with the uplink TBF.

– If a timer or counter expiry causes the uplink TBF to be aborted in the mobile station, the mobile station shall perform an abnormal release according to the procedure defined for the uplink TBF, which may cause also the downlink TBF to be aborted.

– When concurrent uplink and downlink TBFs are established, the network may send a PACKET TIMESLOT RECONFIGURE message without the UPLINK_TFI_ASSIGNMENT field. The mobile station shall interpret this as a reassignment of the concurrent uplink and downlink TBFs. The TFI of the uplink TBF is not changed.

8.1.1.3a.6.2 Abnormal cases

If a failure occurs on the mobile station side before the downlink TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions:

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify an uplink and downlink PDCH or violates the multislot capabilities of the mobile station, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a downlink TBFs is not already established and the PACKET TIMESLOT RECONFIGURE message does not include a DOWNLINK_TFI_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a mobile station in dual transfer mode receives a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET TIMESLOT RECONFIGURE is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET DOWNLINK ASSIGNMENT is due to any reason, the mobile station shall abort the procedure and continue the normal operation of the uplink TBF.

8.1.1.4 Network initiated release of uplink TBF

The network may initiate release of an uplink TBF by transmitting a PACKET TBF RELEASE message to the mobile station on the PACCH. A cause value indicates the reason for release.

If the cause value is "Normal release" the mobile station shall continue to the next LLC PDU boundary, starting the count down procedure (see sub-clause 9.3.1) at whatever value of CV is appropriate to count down to zero at the LLC PDU boundary, and then release the uplink TBF according to the procedures in sub-clause 9.3.2.3 or 9.3.3.3. If the mobile station has more LLC PDU(s) to send, the mobile station may initiate the establishment of a new uplink TBF as defined in sub-clause 7.1 or 8.1.2.5.

If the cause value is "Abnormal Release" the mobile station shall abort the uplink TBF and perform an abnormal release with access retry (see sub-clause 8.7.2). If a valid RRBP field is received as part of the PACKET TBF RELEASE message, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified.

8.1.1.5 Abnormal cases

The following abnormal cases apply:

– if the mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, or a PACKET DOWNLINK ASSIGNMENT message with an invalid Frequency Parameters information element, the mobile station shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information.

– if the mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, or a PACKET DOWNLINK ASSIGNMENT message specifying frequencies that are not all in one band then the mobile shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a mobile station in dual transfer mode receives a PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– if the mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, or a PACKET UPLINK ACK/NACK with an ALLOCATION_BITMAP whose TBF starting time has elapsed, the mobile station shall use whatever portion of the fixed allocation remains. If none of the fixed allocation remains, the mobile station shall ignore the message.

– if the mobile station receives a PACKET UPLINK ACK/NACK with missing mandatory fields, the MS shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– if the mobile station has not started or has not completed the countdown procedure and it receives a Packet Uplink Ack/Nack with the Final Ack Indicator set, it shall perform an abnormal release with access retry (see sub-clause 8.7.2).

NOTE: A PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, or a PACKET DOWNLINK ASSIGNMENT message sent to a multi-band mobile station shall not be considered invalid if it indicates new frequencies that are all in a different frequency band to that of the ARFCN of the serving cell.

8.1.2 Downlink RLC data block transfer

Prior to the initiation of RLC data block transfer on the downlink, the network assigns the following parameters to the downlink TBF in the downlink assignment (e.g., PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) message:

– a Temporary Flow Identity (TFI). The TFI applies to all radio blocks transferred in regards to the downlink Temporary Block Flow (TBF).

– a set of PDCHs to be used for the downlink transfer;

– optionally, a TBF starting time indication.

For each TBF, the network shall prioritise RLC/MAC control blocks, not containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message, to be transmitted ahead of RLC data blocks for that TBF. If the network has no other RLC/MAC block to transmit, but wishes to transmit on the downlink, the network shall transmit an RLC/MAC control block containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message.

8.1.2.1 Downlink RLC data block transfer

This sub-clause specifies mobile station behaviour for downlink RLC data block transfer while in packet transfer mode or dual transfer mode.

Upon reception of a downlink assignment that does not contain a TBF starting time the mobile station shall start timer T3190 and within the reaction time defined in 3GPP TS 05.10, it shall attempt to decode every downlink block on its assigned PDCHs. If the PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message contains a TBF starting time information element and there is no downlink TBF in progress, but an uplink TBF is in progress, the mobile station shall remain on the assigned PDCHs until the TDMA frame number indicated by the TBF starting time, at which time the mobile station shall start timer T3190 and immediately begin decoding the assigned downlink PDCH(s). If the PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message contains a TBF starting time and there is a downlink TBF already in progress, the mobile station shall continue to use the parameters of the downlink TBF in progress until the TDMA frame number indicated in the TBF starting time occurs, at which time the mobile station shall immediately begin to use the new assigned downlink TBF parameters. If while waiting for the frame number indicated by the TBF starting time the mobile station receives another downlink assignment, the mobile station shall act upon the most recently received downlink assignment and shall ignore the previous downlink assignment. Procedures on receipt of a PACKET DOWNLINK ASSIGNMENT message while no TBF is in progress are specified in sub-clause 7.2.1.1.

If the mobile station receives a valid RLC data block addressed to itself, the mobile station shall restart timer T3190. If timer T3190 expires, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

Upon receipt of a PACKET TBF RELEASE referring to the downlink TBF, the mobile station shall follow the procedure in sub-clause 8.1.2.8.

8.1.2.1.1 Abnormal cases

If a failure occurs on the mobile station side before the new TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions:

– If a mobile station receives a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message and detects an invalid Frequency Parameters information element in the message, it shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information.

– If a mobile station in dual transfer mode receives a PACKET DOWNLINK ASSIGNMENT message including the Frequency Parameters information element, the mobile station shall abort the procedure. If an uplink TBF exists, the mobile station shall continue the normal operation of the uplink TBF. If an uplink TBF does not exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

– If a mobile station in dual transfer mode receives a PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify an uplink and downlink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the PACKET TIMESLOT RECONFIGURE does not include a DOWNLINK_TFI_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET TIMESLOT RECONFIGURE is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information available in the mobile station, after the reception of a PACKET DOWNLINK ASSIGNMENT message does not satisfactorily define a PDCH, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message.

– If the mobile station is not operating an uplink TBF in half duplex mode and receives a PACKET DOWNLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for the uplink TBF, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message and continue normal operation of the uplink TBF.

– If the mobile station is operating an uplink TBF in half duplex mode and receives a PACKET DOWNLINK ASSIGNMENT message that does not indicate half duplex mode, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT.

– If a failure in the PACKET DOWNLINK ASSIGNMENT is due to any other reason, the mobile station shall abort the procedure. If an uplink TBF exists, the mobile station shall continue the normal operation of the uplink TBF. If an uplink TBF does not exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

8.1.2.2 Polling for Packet Downlink Ack/Nack

Whenever the mobile station receives an RLC data block addressed to itself and with a valid RRBP field in the RLC data block header (i.e., is polled), the mobile station shall transmit a Packet Downlink ACK/NACK message in the uplink radio block specified by the RRBP field whatever the BSN value of the received RLC data block, unless another RLC/MAC control message is waiting to be transmitted, in which case the other RLC/MAC control message shall be sent. However, the mobile station shall transmit an RLC/MAC control message other than a PACKET DOWNLINK ACK/NACK message at most every second time it is polled. Furthermore the mobile station shall not transmit an RLC/MAC control message other than a PACKET DOWNLINK ACK/NACK message if the PACKET DOWNLINK ACK/NACK message would contain a Final Ack Indicator or Channel Request Description IE. The mobile station shall not send a PACKET CONTROL ACKNOWLEDGEMENT message unless otherwise specified.

Whenever the network receives a valid RLC/MAC control message from the mobile station, it shall reset counter N3105. The network shall increment counter N3105 for each radio block, allocated to that mobile station with the RRBP field, for which no RLC/MAC control message is received. If N3105 = N3105max, the network shall release the downlink TBF internally and start timer T3195. When T3195 expires, the network may reuse the TFI.

The PACKET DOWNLINK ACK/NACK message contains a Channel Quality Report (see 3GPP TS 05.08). The optional I_LEVEL measurement results shall be included in at least every other PACKET DOWNLINK ACK/NACK message.

In the case of simultaneous uplink and downlink TBFs, the transmission of the polling response takes precedence over the transmission of allocated uplink radio blocks.

A mobile station of multislot class 1 to 12 need not respond to the poll if it is not compliant with the mobile station’s multislot class (see 3GPP TS 05.02).

A mobile station of multislot class 13 to 18 shall always respond to the poll.

A mobile station of multislot class 19 to 29 may omit the allocated downlink PDCHs with timeslot numbers greater than n+1, while transmitting the polling response on timeslot number n. If the remaining configuration is not compliant with the mobile station’s multislot class (see 3GPP TS 05.02), the mobile station need not respond to the poll.

NOTE: The mobile station is required to make neighbour cell measurements while transmitting the polling response (see 3GPP TS 05.08).

In case of simultaneous uplink and downlink TBFs and extended dynamic allocation (see sub-clause 8.1.1.2), the network may apply polling in downlink RLC data blocks only when sent on a PDCH common for both reception and transmission (see3GPP TS 05.02). A mobile station operating with extended dynamic allocation need to respond to polling in downlink RLC data blocks only when received on a PDCH common for both reception and transmission.

8.1.2.3 (void)

8.1.2.4 Resource Reassignment for Downlink

The network initiates resource reassignment by sending a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message on the downlink PACCH. This message indicates a change in resources in the same TBF. The Control Ack bit in the message shall be set to ‘0’. During the reassignment TFI is allowed to be changed. Mobile shall use the TFI indicated in the PACKET DOWNLINK ASSIGNMENT when using the resource indicated in the message.

The network is not allowed to change the RLC mode nor TBF mode of an already established TBF during resource reallocation. Change of RLC mode or TBF mode shall be achieved through release of on-going TBF and establishment of a new TBF with the newly requested RLC mode or TBF mode using the procedures described in sub-clause 9.3.2.5 or 9.3.3.5.

On receipt of a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message, and after the TBF starting time, if present, the mobile station shall switch to the assigned PDCHs. Upon switching to the new PDCHs the mobile station shall restart timer T3190.

When the mobile station receives an RLC/MAC block addressed to itself on any of the new assigned resources it shall restart timer T3190. If timer T3190 expires, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

8.1.2.4.1 Abnormal cases

These abnormal cases apply during establishment of downlink TBF after downlink TBF release (see sub-clause 8.1.2.4a).

If a failure occurs on the mobile station side before the new TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions:

– If a mobile station receives a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message and detects an invalid Frequency Parameters information element in the message, the mobile station shall perform an abnormal release with system information (see sub-clause 8.7.3), performing a partial acquisition of system information messages containing frequency information.

– If a mobile station in dual transfer mode receives a PACKET DOWNLINK ASSIGNMENT message including the Frequency Parameters information element, the mobile station shall abort the downlink TBF. If an uplink TBF exists, the mobile station shall continue the normal operation of the uplink TBF. If an uplink TBF does not exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

– If a mobile station in dual transfer mode receives a PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify an uplink and downlink PDCH or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET TIMESLOT RECONFIGURE is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the information available in the mobile station, after the reception of a PACKET DOWNLINK ASSIGNMENT message does not satisfactorily define a PDCH, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message.

– If the mobile station is not operating the uplink TBF in half duplex mode and receives a PACKET DOWNLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for the uplink TBF, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message and continue normal operation of the uplink TBF.

– If the mobile station is operating the uplink TBF in half duplex mode and receives a PACKET DOWNLINK ASSIGNMENT message that does not indicate half duplex mode, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT.

– If a failure in the PACKET DOWNLINK ASSIGNMENT is due to any other reason, the mobile station shall abort the procedure. If an uplink TBF exists, the mobile station shall continue the normal operation of the uplink TBF. If an uplink TBF does not exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

8.1.2.5 Establishment of uplink TBF

The mobile station may request establishment of an uplink transfer during a downlink TBF by including a Channel Request Description information element in the PACKET DOWNLINK ACK/NACK message Initiation is triggered by a request from upper layers to transfer a LLC PDU. The request from upper layers specifies a Radio Priority to be associated with the packet transfer. Upon such a request,

– if access to the network is allowed, according to the latest values for authorised special access classes that the mobile station has received (see sub-clause 7.1.1), the mobile station shall initiate the packet access procedure.

– otherwise, the RR sublayer in the mobile station shall reject the request.

The mobile station initiates the packet access procedure by sending the Channel Request Description information element in the PACKET DOWNLINK ACK/NACK message on the PACCH and starting timer T3168.

On receipt of a Channel Request Description information element in the PACKET DOWNLINK ACK/NACK message, the network may assign radio resources to the mobile station on one or more PDCHs by transmitting a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message on the PACCH, or may reject the request by sending a PACKET ACCESS REJECT message on the PACCH. If the PACKET TIMESLOT RECONFIGURE message is sent, then the message shall contain the UPLINK_TFI_ASSIGNMENT field.

A mobile allocation or reference frequency list, when received in the Frequency Parameters IE, as part of an uplink assignment, replaces the previous parameters and shall be used until a new assignment is received or the mobile station has released all TBFs.

On receipt of a PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message the mobile station shall follow the procedure below. On reception of an uplink assignment the mobile station shall stop timer T3168.

If the mobile station is not assigned to operate half duplex mode, the mobile station shall, after expiry of the TBF starting time, if present, act upon the uplink assignment.

If the mobile station is assigned to operate in half duplex mode, the mobile station shall, after expiry of the TBF starting time, if present, stop the downlink TBF, save the RLC state variables associated with the downlink TBF and save the state of the following timers:

T3190 Wait for Valid Downlink Data Received from the Network

T3192 Wait for Release of the TBF after reception of the final block

Whenever a mobile station operating on a downlink TBF in half duplex mode receives a uplink assignment on the PACCH and has previously saved the state of the uplink TBF and not since entered idle mode, the mobile station shall restore the saved uplink RLC state variables and timer values.

If the mobile station is operating the downlink TBF in half duplex mode and receives a PACKET TIMESLOT RECONFIGURE message it shall exit half duplex mode and act on the PACKET TIMESLOT RECONFIGURE.

The mobile station shall then switch to the assigned uplink PDCHs and begin to send RLC data blocks on the assigned PDCH(s). The TLLI shall not be included in any of the uplink RLC data blocks in that case.

On receipt of a PACKET ACCESS REJECT message that contains a Reject structure addressed to the mobile station, the mobile station shall stop timer T3168 and indicate a packet access failure to upper layer.

If the PACKET ACCESS REJECT message contains a WAIT_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall start timer T3172 with the indicated value (Wait Indication). The mobile station is not allowed to make a new attempt for uplink TBF establishment in the same cell until timer T3172 expires, but it may attempt uplink TBF establishment in an other cell after successful cell reselection.

If timer T3168 expires, the mobile station shall retransmit the Channel Request Description information element in the next PACKET DOWNLINK ACK/NACK message unless it has been transmitted four times in which case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If the downlink TBF is released, including expiry of timer T3192, before expiry of timer T3168 the mobile station shall stop timer T3168 and perform an abnormal release with access retry (see sub-clause 8.7.2).

8.1.2.5.1 Abnormal cases

If a failure occurs on the mobile station side before the new TBF has been successfully established, the newly reserved resources are released. The subsequent behaviour of the mobile station depends on the type of failure and previous actions.

– If the information in the PACKET UPLINK ASSIGNMENT violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the mobile station is not operating the downlink TBF in half duplex mode and receives a PACKET UPLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for the downlink TBF, the mobile station shall ignore the PACKET UPLINK ASSIGNMENT message, continue normal operation of the downlink TBF, and reinitiate the access unless it has already been attempted 4 times, in which case, the mobile station shall perform the abnormal release with access retry (see sub-clause 8.7.2).

– If the mobile station is operating the downlink TBF in half duplex mode and receives a PACKET UPLINK ASSIGNMENT message that does not indicate half duplex mode, the mobile station shall ignore the PACKET UPLINK ASSIGNMENT.

– If a mobile station in dual transfer mode receives a PACKET UPLINK ASSIGNMENT message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET UPLINK ASSIGNMENT is due to any other reason, the mobile station shall abort the procedure and continue the reception of downlink PDUs.

– If the information in the PACKET TIMESLOT RECONFIGURE does not properly specify a set of uplink and downlink PDCH(s) or violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the PACKET TIMESLOT RECONFIGURE does not include a correct UPLINK_TFI_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a mobile station in dual transfer mode receives a PACKET TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If a failure in the PACKET TIMESLOT RECONFIGURE is due to any other reason, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).

– If the failure is due to any other reason, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2).

8.1.2.6 (void)

8.1.2.7 Fixed allocation neighbour cell power measurements

A mobile station operating in half duplex mode may be directed by the network to perform neighbour cell power measurements in predefined gaps via the Measurement Mapping parameters. The location in time and the size of the gaps are signalled by the following parameters:

– the starting time of the first TDMA frame of the first gap;

– a bitmap indicating the timeslots that are part of the gap; and

– the number of RLC/MAC block periods between gaps.

If the mobile has received the Measurement Mapping parameters, the mobile station need not decode the radio blocks(s) comprising the gap during each occurrence of the gap.

A mobile station operating in half duplex mode or that has not received the Measurement Mapping parameters, shall perform a neighbour cell power measurement in 24 of 26 TDMA frames. If the mobile station’s multislot class and the assigned timeslot configuration for uplink TBF and downlink TBF simultaneously in progress prevent the mobile station from making these measurements (Tra and Ttb requirements should be fulfilled), the downlink TBF assignment shall be considered invalid and the procedures of sub-clause 8.1.1.1.3.1 apply.

8.1.2.8 Network initiated abnormal release of downlink TBF

The network may initiate immediate abnormal release of a downlink TBF by transmitting a PACKET TBF RELEASE message to the mobile station on the PACCH.

The mobile station shall immediately stop monitoring its assigned downlink PDCHs. If a valid RRBP field is received as part of the PACKET TBF RELEASE message, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGMENT message in the uplink radio block specified.

If there is no on-going uplink TBF, the mobile station in packet transfer mode shall enter packet idle mode; the mobile station in dual transfer mode shall enter dedicated mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5.

8.1.3 Concurrent TBF procedures for half duplex operation

8.1.3.1 (void)

8.1.3.2 General

A mobile station of multislot class 19 through 29 (see 3GPP TS 05.02) not operating in half duplex mode shall follow the procedures of sub-clauses 8.1.1.3.5 and 8.1.2.5. If uplink and downlink TBFs are already established, the network may send a PACKET TIMESLOT RECONFIGURE message in order to change the uplink and downlink resource allocation of the on-going TBFs. In the message the network may assign a new downlink and/or uplink TFI to be used for the TBFs. For multislot class 19 through 29 (see 3GPP TS 05.02), if the assignment message indicates half duplex mode operation, the procedures defined in this sub-clause shall be followed.

Procedures are defined to:

– allow the network and mobile station to save the state of one TBF to allow data transfer in the other TBF; and

– allow a TBF whose state has been saved to be restored at release of the active TBF.

8.1.3.2.1 Saving downlink TBF state and initiating uplink TBF

A mobile station operating using the fixed allocation medium access mode may initiate an uplink TBF during a downlink TBF using the procedure defined in sub-clause 8.1.2.5.

8.1.3.2.2 Saving downlink TBF state and restoring uplink TBF state

During a downlink TBF the mobile station may indicate that it wishes to transfer RLC data on the uplink TBF by initiating the procedure defined in sub-clause 8.1.2.5.

8.1.3.2.3 Ending downlink TBF and restoring uplink TBF state

If the network sends an RLC data block with the FBI field set to indicate the last RLC data block of the TBF and an associated uplink TBF for the mobile station exists, the network shall also transmit a PACKET UPLINK ASSIGNMENT message on the downlink PACCH to the mobile station.

If a mobile station receives an RLC data block with the FBI set to indicate the last RLC data block of the TBF and an associated uplink TBF for the mobile station exists, the mobile station shall follow the downlink TBF release procedures defined in sub-clause 9.3.2.5 or sub-clause 9.3.3.5. If the mobile station receives an uplink assignment during the release procedure and a conflict exists between the downlink and uplink allocations, the mobile station shall first complete the downlink TBF procedures and then the mobile station shall act upon the uplink assignment.

8.1.3.2.4 Saving uplink TBF state and initiating downlink TBF

The network may initiate a downlink TBF during an uplink TBF to a mobile station operating using the fixed allocation medium access mode by using the procedure defined in sub-clause 8.1.1.3.5.

8.1.3.2.5 Saving uplink TBF state and restoring downlink TBF state

The mobile station sending RLC data on an uplink TBF and with an active but saved downlink TBF may be commanded by the network to save the state of the uplink TBF and restore the state of the downlink TBF and then operate the downlink TBF. Upon receipt of a PACKET DOWNLINK ASSIGNMENT message, the mobile station shall follow the procedure in sub-clause 8.1.1.3.5.

8.1.3.2.6 Ending uplink TBF and restoring downlink TBF state

A mobile station operating in the fixed allocation medium access mode shall, if a downlink TBF exists, release its uplink TBF by following the procedures in sub-clause 9.3.2.3 or sub-clause 9.3.3.5 and immediately begin to monitor the downlink PDCH(s) allocated in its downlink TBF.

8.2 Packet PDCH Release

The network may broadcast the PACKET PDCH RELEASE message on PACCH to indicate one or more timeslots is no longer available for packet data service.

When a mobile station receives a PACKET PDCH RELEASE message, it shall immediately stop transmitting and receiving on all assigned PDCHs, which are indicated as not present in the TIMESLOTS_AVAILABLE field, remove those PDCHs from its list of assigned PDCHs.

If an uplink TBF in fixed allocation mode was in progress and if one of timeslots that are being released is its downlink PACCH timeslot, the mobile station shall temporarily read all downlink blocks that it is able to decode according to its multislot capability, on all of its remaining assigned PDCHs, and act upon any RLC/MAC control message that is addressed to it, until another downlink PACCH timeslot is assigned. If the mobile station’s multislot capability does not allow it to monitor the downlink of any of its assigned PDCHs, it shall perform an abnormal release with access retry (see sub-clause 8.7.2).

If all of the mobile station’s assigned PDCHs are removed from its list of assigned PDCH, and, if an uplink TBF was in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If no uplink TBF was in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

8.3 Procedure for measurement report sending in Packet Transfer mode

The procedure for NC measurement report sending shall be initiated by the mobile station at expiry of the NC measurement report interval timer T3158 (see sub-clause 5.6.1). At expiry of the timer T3158 the mobile station shall restart the timer T3158, perform the measurements and send either the PACKET MEASUREMENT REPORT message containing the ‘NC measurement report struct’ or the PACKET ENHANCED MEASUREMENT REPORT on PACCH.

An EXT measurement report shall only be reported if the measurements have been collected when the mobile station enters packet transfer mode(see 3GPP TS 05.08).

Following a downlink TBF establishment, the PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message shall not be sent on the uplink PACCH associated with this TBF until two PACKET DOWNLINK ACK/NACK messages has been sent to the network.

8.4 Network controlled cell reselection procedure

A cell reselection is made controlled either by the mobile station or by the network.

When the cell reselection is made controlled by the mobile station, the mobile station shall apply the cell reselection procedure defined in sub-clause 5.5.1.1.

When a cell reselection is initiated by the network for an individual mobile station, the cell change order procedure is started by sending a PACKET CELL CHANGE ORDER message to the mobile station on the PCCCH or PACCH.

The PACKET CELL CHANGE ORDER message contains:

– The characteristics of the new cell that are necessary to identify it (i.e. BSIC + BCCH frequency);

– The NC measurement parameters valid for the mobile station in the new cell (NETWORK_CONTROL_ORDER and optionally: NC_NON_DRX_PERIOD, NC_REPORTING_PERIOD_I and NC_REPORTING_PERIOD_T).

– The IMMEDIATE_REL parameter.

For a multi-RAT mobile station, the PACKET CELL CHANGE ORDER message may contain information on a 3G target cell, together with the IMMEDIATE_REL parameter; in the case of UTRAN establishment of UTRAN channel(s) and subsequent measurement reporting are defined in 3GPP TS 25.331.

Upon receipt of the PACKET CELL CHANGE ORDER message the mobile station shall start timer T3174 and apply the cell reselection procedure defined in sub-clause 5.5.1.1. with the additional rule that an immediate abort of operation in the old cell may be required by the network through the IMMEDIATE_REL field, except for the acknowledgement, by means of a PACKET CONTROL ACKNOWLEDGEMENT message, of a valid RRBP field possibly included in the PACKET CELL CHANGE ORDER message. The mobile station shall obey the PACKET CELL CHANGE ORDER message irrespective of whether or not the mobile station has any knowledge of the relative synchronisation of the target cell to the serving cell. A UTRAN capable mobile station shall obey the command irrespective of whether the cell is know or not known (see 3GPP TS 25.133 and 3GPP TS 25.123).

If the timers related to measurement reporting expire while the reselection procedure has not yet been completed, these timers shall be restarted so that the mobile station resumes the measurement reporting procedures once camped on the new cell.

8.4.1 Network controlled cell reselection completion

The mobile station regards the procedure as completed when it has received a successful response to its CHANNEL REQUEST or PACKET CHANNEL REQUEST message on the new cell. The CHANNEL REQUEST may be for establishing a dedicated connection or an uplink TBF. It shall then stop timer T3174.

If the mobile station is unable to synchronise to the new cell (see 3GPP TS 05.08), or, if timer T3174 expires before a response to the CHANNEL REQUEST or PACKET CHANNEL REQUEST message has been received on the new cell, or, if an IMMEDIATE ASSIGNMENT REJECT or PACKET ACCESS REJECT message is received from the new cell, or, if the contention resolution procedure fails on the new cell, then the mobile station shall start timer T3176 and return to the old cell. If the mobile station was in packet idle mode or in downlink packet transfer mode before the cell change, the mobile station shall initiate a random access on the old cell, with access type "single block without TBF establishment", and then transmit the PACKET CELL CHANGE FAILURE message on the single block. If the mobile station was in uplink packet transfer mode or in a simultaneous uplink and downlink packet transfer mode before the cell change, the mobile station shall establish a new uplink TBF and send the PACKET CELL CHANGE FAILURE message on this TBF. The mobile station shall then resume its uplink transfer on this TBF. When the mobile station has sent a PACKET CELL CHANGE FAILURE message, timer T3176 shall be stopped. If T3176 expires and the mobile station was previous in an uplink packet transfer mode or in a simultaneous uplink and downlink packet transfer mode on the old cell, the mobile station shall perform the abnormal release with access retry (see sub-clause 8.7.2). If the mobile station was previous in a downlink packet transfer mode only on the old cell the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

8.4.1b Network controlled cell reselection completion (UTRAN target Cell)

For a UTRAN target cell, the mobile station regards the procedure as completed when it has received a successful response to its RRC Connection Request message, see 3GPP TS 25.331. It shall then stop timer T3174.

If the mobile station is unable to synchronise to the new cell (see 3GPP TS 05.08), or, if timer T3174 expires before a response to the RRC Connection Request message has been received on the new cell, or if a RRC Connection Reject message including Inter-RAT info set to ‘GSM’ is received from the new cell, then the mobile station shall start timer T3176 and return to the old cell. If the mobile station was in packet idle mode or in downlink packet transfer mode before the cell change, the mobile station shall initiate a random access on the old cell, with access type "single block without TBF establishment", and then transmit the PACKET CELL CHANGE FAILURE message on the single block. If the mobile station was in uplink packet transfer mode or in a simultaneous uplink and downlink packet transfer mode before the cell change, the mobile station shall establish a new uplink TBF and send the PACKET CELL CHANGE FAILURE message on this TBF. The mobile station shall then resume its uplink transfer on this TBF. When the mobile station has sent a PACKET CELL CHANGE FAILURE message, timer T3176 shall be stopped. If T3176 expires and the mobile station was previously in an uplink packet transfer mode or in a simultaneous uplink and downlink packet transfer mode on the old cell, the mobile station shall perform the abnormal release with access retry (see sub-clause 8.7.2). If the mobile station was previous in a downlink packet transfer mode only on the old cell the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

8.4.2 Abnormal cases

On the mobile station side, if the PACKET CELL CHANGE ORDER message instructs the mobile station to use a frequency that it is not capable of using, then the mobile station shall return a PACKET CELL CHANGE FAILURE message with cause "frequency not implemented"

If the PACKET CELL CHANGE ORDER message is received by the mobile while the mobile station is not in dual transfer mode but a circuit switched connection is on-going, then the mobile station shall return a PACKET CELL CHANGE FAILURE message with the cause "on-going CS connection".

A mobile station shall ignore a PACKET CELL CHANGE ORDER message received while in dual transfer mode (see 3GPP TS 04.18).

If the PACKET CELL CHANGE ORDER message is received while the mobile is in GMM Standby state, the mobile shall return a PACKET CELL CHANGE FAILURE,

– if the GMM Ready timer has a negotiated value equal to zero, with the cause set to "Forced to the Standby state",

– if the GMM Ready timer has a negotiated value not equal to zero, with the cause set to "GMM Standby state".

The message PACKET CELL CHANGE FAILURE is sent on the PACCH if an uplink TBF exist.

If no TBF exists, the mobile station shall initiate a random access, with access type "single block without TBF establishment", and then transmit the PACKET CELL CHANGE FAILURE message on the single block.

If a TBF exist, the mobile station shall remain on the current PDCH(s).

On the network side, lower layer failures occurring on the old channels after the sending of the PACKET CELL CHANGE ORDER message are ignored.

8.5 Measurement Order procedures in Packet Transfer mode

The network may initiate the measurement order procedure by sending a PACKET MEASUREMENT ORDER message on the PACCH to a mobile station in packet transfer mode.The PACKET MEASUREMENT ORDER message overrides a broadcast PSI5 message.

The PACKET MEASUREMENT ORDER message may also contain the following optional parameters:

– NC Measurement Parameters (NETWORK_CONTROL_ORDER; NC_NON_DRX_PERIOD; NC_REPORTING_PERIOD_I; NC_REPORTING_PERIOD_T; NC_FREQUENCY_LIST);

– EXT Measurement Parameters (EXT_MEASUREMENT_ORDER; EXT_REPORTING_TYPE; EXT_REPORTING_PERIOD; INT_FREQUENCY; EXT_FREQUENCY_LIST).

– Enhanced measurement reporting.

Upon receipt of the PACKET MEASUREMENT ORDER message, the mobile station shall store the received parameters and obey the NETWORK_CONTROL_ORDER and the EXT_MEASUREMENT_ORDER as specified in 3GPP TS 05.08 and in sub-clause 5.6.

8.6 PACKET CONTROL ACKNOWLEDGEMENT

A PACKET CONTROL ACKNOWLEDGEMENT message shall always be sent in the uplink block specified by the corresponding valid RRBP field of a downlink RLC/MAC control block, and not in any other uplink block that may be allocated to the mobile station. However the transmission of the PACKET CONTROL ACKNOWLEDGEMENT takes precedence over the transmission of allocated uplink radio blocks or the reception of PCCCH or assigned PDTCH radio blocks. If transmission of the PACKET CONTROL ACKNOWLEDGEMENT would result in more than the maximum Tx timeslots per TDMA frame allowed by the multislot class, transmission of the highest numbered PDCH(s) shall be omitted.

8.7 Abnormal cases

The following abnormal cases apply:

– If a mobile station receives a PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message assigning a MAC mode violating the restrictions defined in sub-clause 8.1.0 for changing the MAC mode in packet transfer mode and dual transfer mode, the assignment message shall be ignored.

– If the PDCH containing the mobile station’s only assigned TAI value is removed, the mobile station shall, if it is performing an uplink TBF, perform an abnormal release with access retry (see sub-clause 8.7.2), and otherwise shall perform an abnormal release without retry (see sub-clause 8.7.1).

– If the Measurement Parameters (NC and/or EXT) are sent in more than one instance of the PACKET MEASUREMENT ORDER message, the mobile station shall not obey the measurement order until all instances of the message has been correctly received.

– If the mobile station receives a Timing Advance Index and a Timing Advance Timeslot Number for one direction within a PACKET POWER CONTROL/TIMING ADVANCE message and the corresponding TBF does not exist, the Timing Advance Index and the Timing Advance Timeslot Number for that direction shall be ignored.

– While a TBF is in progress, if a mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET UPLINK ACK/NACK or PACKET TIMESLOT RECONFIGURE message with message escape bit indicating EGPRS (resp. GPRS) contents whereas the current TBF mode is GPRS (resp. EGPRS), the mobile station shall ignore the message.

– While a TBF is in progress, if a mobile station receives a PACKET DOWNLINK ASSIGNMENT message without extension message content related to R99 whereas the current TBF mode is EGPRS, the mobile station shall ignore the message.

– While a TBF is in progress, if a mobile station receives a PACKET DOWNLINK ASSIGNMENT message with extension message content related to R99 whereas the current TBF mode is GPRS, the mobile station shall ignore the EGPRS related information and act as a GPRS MS not supporting EGPRS.

8.7.1 Abnormal release without retry

The mobile station shall abort all TBFs in progress and report an RLC/MAC failure to upper layers. The mobile station in packet transfer mode shall return to packet idle mode; the mobile station in dual transfer mode shall return to dedicated mode. The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5.

8.7.2 Abnormal release with access retry

The mobile station shall abort all TBFs in progress. The mobile station in packet transfer mode shall return to packet idle mode and initiate the establishment of a new uplink TBF, using the procedures on CCCH or PCCCH, as defined in sub-clause 7.1.

The mobile station in dual transfer mode shall return to dedicated mode and initiate the establishment of a new uplink TBF using the appropriate DTM procedure on the main DCCH, defined in 3GPP TS 04.18.

In case the mobile station fails to establish a new uplink TBF, the mobile station shall report an RLC/MAC failure to upper layers. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5.

8.7.3 Abnormal release with system information

The mobile station shall abort the TBF and its associated resources, immediately return to the BCCH and reread all relevant BCCH and PBCCH information. If the mobile station was performing an uplink TBF when the abnormal release occurred, the mobile station shall then perform an abnormal release with access retry (see sub-clause 8.7.2). Otherwise the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).