8 Medium Access Control (MAC) procedures on SBPSCH

3GPP44.160General Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocol Iu modeRelease 16TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.1 General

The MAC procedures defined in this sub-clause are applicable in MAC-Shared state and MAC-DTM state.

The full set of downlink assignment messages comprises the PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT and MULTIPLE TBF TIMESLOT RECONFIGURE messages.

The full set of uplink assignment messages comprises the PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF UPLINK ASSIGNMENT and MULTIPLE TBF TIMESLOT RECONFIGURE messages.

The network may choose to send either single assignment messages (PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE) or multiple TBF assignment messages (MULTIPLE TBF DOWNLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE) on the PACCH. The network shall only use the multiple TBF assignment messages when assigning or reallocating the mobile station with more than one uplink TBF and/or more than one downlink TBF.

8.1a Resource stealing (SFACCH)

The use of SFACCH in MAC-Shared state for SRBs 1 through 4 is specified in sub-clause 5.6.2.2.

The use of SFACCH in MAC-DTM state for SRBs 3 and 4 is specified in sub-clause 5.6.2.3. SFACCH shall not be used for SRBs 1 and 2 in MAC-DTM state.

If the mobile station has data to send for an SRB that can be sent on SFACCH, and neither a TBF nor a TBF establishment request is ongoing for this SRB, the following procedure applies:

– The mobile station may select a current TBF on an SBPSCH, construct an uplink RLC data block that includes octet 3 (this octet contains the SRBid), and send the SRB data at the TBF’s next scheduled transmission opportunity for an RLC data block. GERAN shall use the SRBid to route the SRB data to the correct RLC instance.

– Otherwise, the mobile station shall initiate a new TBF operating on an SBPSCH (see sub-clause 8.2.2.0.2).

If the mobile station has data to send for an SRB, and a TBF exists for this SRB, the following procedure applies:

– The mobile station shall construct an uplink RLC data block that does not include octet 3 and send the SRB data on the TBF.

If GERAN has data to send for an SRB that can be sent on SFACCH, and no TBF exists for this SRB, the following procedure applies:

– GERAN may select a current TBF on an SBPSCH, construct a downlink RLC data block that includes octet 3, and send the SRB data at the TBF’s next scheduled transmission opportunity for an RLC data block. The mobile station shall use the SRBid to route the SRB data to the correct RLC instance.

– Otherwise, GERAN shall establish a new TBF operating on an SBPSCH (see sub-clause 8.2.2.0.2).

If GERAN has data to send for an SRB, and a TBF exists for this SRB, the following procedure applies:

– GERAN shall construct a downlink RLC data block that does not include octet 3 and send the SRB data on the TBF.

8.2 Transfer of RLC data blocks

8.2.1 Medium access mode

The transfer of RLC data blocks on SBPSCH is governed by different principles on both uplink and downlink for each of the defined medium access modes: dynamic allocation, extended dynamic allocation, and exclusive allocation.

The medium access mode the mobile station is to use, except when exclusive allocation is applied in MAC-DTM state, is given by the MAC_MODE parameter. The MAC_MODE parameter is included in the downlink assignment (e.g. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) message, whereas in the uplink the MAC_MODE parameter is given by the EXTENDED_DYNAMIC_ALLOCATION parameter. The value of the MAC_MODE parameter shall not be changed while the mobile station is in MAC-Shared state or MAC-DTM state.

Exclusive allocation is applicable only in MAC-DTM state when a single TBF is allocated on 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 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.2.2 Uplink RLC data block transfer

8.2.2.0 General

8.2.2.0.1 General

See 3GPP TS 44.060 sub-clause 8.1.1.

8.2.2.0.2 Establishment of additional uplink TBF(s)

When the mobile station has data to send that does not have the same radio bearer identity as (any of) the uplink TBF(s) or TBF request(s) in progress, the mobile station shall request uplink resources through one of the following procedures:

– If the data belongs to a signalling radio bearer

– Use the SFACCH (see sub-clause 8.1a)

– Establish an additional TBF (sub-clause 8.2.2.1.2)

– If the mobile station cannot support the establishment of an additional TBF, then the network may release an on-going TBF in order to establish a new TBF (sub-clause 8.2.2.1.2)

– If the data belongs to a user radio bearer

– Establish an additional TBF (sub-clause 8.2.2.1.2)

– If the mobile station cannot support the establishment of an additional TBF, then the network may release an on-going TBF in order to establish a new TBF (sub-clause 8.2.2.1.2)

8.2.2.0.3 Uplink resource reallocation / reconfiguration

Neither the mobile station nor the network are allowed to modify the RLC mode, TBF mode or radio bearer identity of an already established TBF. If the mobile station has data to send that requires a modification of existing uplink resources, an uplink resource request shall be sent, see sub-clause 8.2.2.0.2.

If no modifications to the uplink resources are required, the network may reallocate existing resources through one of the following procedures:

– The network may send a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message to the mobile station on the PACCH to reallocate uplink (and also downlink) resources, see sub-clause 8.2.2.1.2.2.

– The network may send a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message to the mobile station on the PACCH to reallocate uplink resources, see sub-clause 8.2.2.1.2.2.

8.2.2.0.4 Establishment of downlink TBF(s)

During uplink data transfer, the network may initiate downlink data transfer for one or more TBFs by sending a downlink assignment message to the mobile station on the downlink PACCH.

The network initiates assignment of a single downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message. The network initiates assignment of more than one downlink TBF by sending a MULTIPLE TBF DOWNLINK ASSIGNMENT or a MULTIPLE TBF TIMESLOT RECONFIGURE message.

The procedure to be followed is described in sub-clause 8.2.2.1.3.

8.2.2.1 Dynamic Allocation uplink RLC data block transfer

See 3GPP TS 44.060 sub-clause 8.1.1.1.

8.2.2.1.1 PACCH operation

See 3GPP TS 44.060 sub-clause 8.1.1.1.1.

8.2.2.1.2 Resource Allocation / Reallocation for Uplink

8.2.2.1.2.1 General

The mobile station shall initiate the uplink resource (re)allocation procedure by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168 for each TBF request included in the Iu mode Channel Request Description IE.

8.2.2.1.2.2 On receipt of the PACKET RESOURCE REQUEST

On receipt of the PACKET RESOURCE REQUEST message the network shall respond by sending one or more uplink assignment messages (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET TIMESLOT RECONFIGURE) and/or a PACKET ACCESS REJECT message and/or a PACKET TBF RELEASE message to the mobile station on the downlink PACCH.

When the mobile station has already been allocated the maximum number of TBFs in the uplink direction that it can support, the network shall respond with either a PACKET ACCESS REJECT message, or a PACKET TBF RELEASE message followed by an uplink assignment message.

On receipt of an uplink assignment message the mobile station shall stop timer T3168 for each uplink TBF assigned in the assignment message and switch to the assigned SBPSCHs. A new assignment shall not terminate the previous assignment unless the uplink assignment message explicitly contains a reassignment for an on-going TBF.

On expiry of timer T3168 the mobile station shall retransmit the PACKET RESOURCE REQUEST message for the TBF(s) for which T3168 has expired unless the PACKET RESOURCE REQUEST message has already been transmitted four times for this TBF 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 uplink assignment message is received for a TBF for which timer T3168 is running before the mobile station has completed its currently assigned TBF(s), the mobile station shall stop timer T3168 for that TBF, return to MAC-Idle state and start the packet access procedure on the PCCCH.

The network may at any time during an uplink TBF initiate a change of resources or allocation of new resources by sending on the downlink PACCH monitored by the MS, an unsolicited uplink assignment message to the mobile station.

On receipt of a PACKET ACCESS REJECT message, the mobile station shall stop timer T3168, if running, for each TBF request rejected in the PACKET ACCESS REJECT message and indicate a packet access failure to the upper layer. If no other uplink or downlink TBFs exist, the mobile station in MAC-Shared state shall return to MAC-Idle state; the mobile station in MAC-DTM state shall return to MAC-Dedicated state. 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 for each TBF request rejected in the message (listed by radio bearer identity). The mobile station is not allowed to make a new attempt for an uplink TBF establishment for this radio bearer in the same cell until this instance of timer T3172 expires. It may attempt a TBF establishment for another radio bearer while T3172 is running. It may attempt an uplink TBF establishment in another cell after successful cell reselection. While T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages.

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

8.2.2.1.2.3 Abnormal cases

The following abnormal cases apply:

– If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF 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.8.4), performing a partial acquisition of system information messages containing frequency information.

– If the information in the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message incorrectly specifies one or more uplink PDCHs, the mobile station shall perform an abnormal release with access retry of the uplink TBF(s) with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments.

– If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message incorrectly specifies one or more uplink and/or downlink PDCHs, the mobile station shall perform an abnormal release with access retry of the uplink TBF(s) with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments.

– If the information in the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

– If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF 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.8.3).

– If the mobile station receives a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF 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.8.3).

– If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message containing assignments such that more than one radio bearer is mapped onto one TBF, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

– If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, or MULTIPLE TBF TIMESLOT RECONFIGURE message assigns the same USF to more than one TBF on the same timeslot, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message specifies a RB Id that is not assigned to the mobile station, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

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

– If the MULTIPLE TBF UPLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE message does not specify a Channel Coding scheme for one or more of the uplink TBFs that it is assigning, then the mobile station shall perform an abnormal release with access retry of the uplink TBFs with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments.

– If the PACKET ACCESS REJECT message does not specify a G-RNTI_extension field in the Iu mode Reject structure for each G-RNTI included in the TLLI / G-RNTI field in the Reject structure, then the mobile station shall ignore the message.

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

A PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF 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.2.2.1.3 Establishment of downlink TBF

8.2.2.1.3.1 General

During uplink transfer, the network may initiate one or more downlink TBFs by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT, MULTIPLE TBF 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.

On receipt of a downlink assignment message, and after the TBF starting time, if present, the mobile station shall switch to the assigned SBPSCHs, and start timer T3190 for each TBF. The operation of the downlink TBF follows the procedures in sub-clause 8.2.3 and 3GPP TS 44.060 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 triggering an abnormal release with access retry on PCCCH (see sub-clause 8.8.3), the mobile station shall also abort all downlink TBF(s). The mobile station shall not abort the downlink TBF(s) in case an abnormal release with access retry on PACCH is triggered;

– If both uplink and downlink TBFs are already established and if more than one TBF is already established in either/both direction(s), then the network may send a MULTIPLE TBF TIMESLOT RECONFIGURE message. If this message contains a change in frequency in the frequency parameters and does not contain a reassignment for one or more of the mobile station’s TBFs, these TBFs are to be released upon moving to the new frequency. If no change in frequency parameters is included, the TBFs not explicitly reconfigured shall continue according to their original assignment.

8.2.2.1.3.2 Abnormal cases

In the following abnormal cases it is assumed that at least one uplink TBF exists. The subsequent behaviour of the mobile station depends on the type of failure and previous actions:

– If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message incorrectly specifies an uplink and/or downlink PDCH, the mobile station shall perform an abnormal release of the downlink TBF(s) with erroneous assignments (see sub-clause 8.8.6). The mobile station shall act upon the valid assignments.

– If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

– If a downlink TBF 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 (sub-clause 8.8.3).

– If a downlink TBF is not already established and the MULTIPLE TBF TIMESLOT RECONFIGURE message does not assign any downlink TBFs, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If the mobile station receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message containing assignments such that more than one radio bearer is mapped onto a TBF, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

– If the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message specifies a RB Id not assigned to the mobile station, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If a mobile station in MAC-DTM state receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message is due to any other reason, the mobile station shall abort the procedure. If other uplink TBFs exist, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3). If only downlink TBFs exist, the mobile station shall continue the normal operation of these TBFs. If no other TBFs exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2).

8.2.2.2 Extended Dynamic Allocation uplink RLC data block transfer

8.2.2.2.0 General

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.2.2.1 apply, except where this sub-clause defines a new procedure. In cases where this sub-clause conflicts with sub-clause 8.2.2.1, this sub-clause takes precedence.

8.2.2.2.1 Uplink PDCH Allocation

See 3GPP TS 44.060 sub-clause 8.1.1.2.1.

8.2.2.2.2 PACCH operation

See 3GPP TS 44.060 sub-clause 8.1.1.2.2.

8.2.2.2.3 Neighbour cell power measurements

See 3GPP TS 44.060 sub-clause 8.1.1.2.3.

8.2.2.2.4 Shifted USF operation

See 3GPP TS 44.060 sub-clause 8.1.1.2.4.

8.2.2.3 Exclusive Allocation uplink RLC data block transfer

See 3GPP TS 44.060 sub-clause 8.1.1.3a.

8.2.2.3.1 (void)

8.2.2.3.2 (void)

8.2.2.3.3 (void)

8.2.2.3.4 (void)

8.2.2.3.5 (void)

8.2.2.3.6 (void)

8.2.2.4 Network initiated release of uplink TBF

See 3GPP TS 44.060 sub-clause 8.1.1.4.

8.2.2.5 Abnormal cases

The following additional abnormal cases are applicable to an uplink transfer:-

– if the mobile station receives a PACKET UPLINK ACK/NACK message with missing mandatory fields, the mobile station shall perform an abnormal release with access retry of the uplink TBF (sub-clause 8.8.5) associated with this message.

– if the mobile station receives a PACKET UPLINK ACK/NACK message that contains a RB Id that is not assigned to the mobile station or that is assigned to the mobile station but without any corresponding uplink TBF, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

8.2.3 Downlink RLC data block transfer

8.2.3.1 General

8.2.3.1.0 General

The network initiates assignment of a single downlink TBF by sending a PACKET DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message on the downlink PACCH. The network initiates assignment of more than one downlink TBF by sending a MULTIPLE TBF DOWNLINK ASSIGNMENT or a MULTIPLE TBF TIMESLOT RECONFIGURE message on the downlink PACCH. 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 message:

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

– a radio bearer identity (RB Id). There is a one-to-one mapping between the TFI and the RB Id of the radio bearer for which the downlink TBF is established.

– 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.2.3.1.1 Downlink resource reallocation

Neither the mobile station nor the network are allowed to modify the RLC mode, TBF mode or radio bearer identity of an already established TBF.

If no modifications to the downlink resources are required, the network may reallocate existing resources through one of the following procedures:

– The network may send a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message to the mobile station on the PACCH to reallocate downlink (and also uplink) resources, see sub-clause 8.2.3.2.

– The network may send a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message to the mobile station on the PACCH to reallocate downlink resources, see sub-clause 8.2.3.2.

8.2.3.1.2 (void)

8.2.3.2 Downlink RLC data block transfer procedure

8.2.3.2.0 General

Upon reception of a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE) that does not contain a TBF starting time the mobile station shall start timer T3190 for each downlink TBF assigned in the downlink assignment message and, within the reaction time defined in 3GPP TS 45.010, it shall attempt to decode every downlink block on its assigned SBPSCH(s). If the downlink assignment message contains a TBF starting time information element and there are no downlink TBFs in progress, but one or more uplink TBFs are in progress, the mobile station shall remain on the assigned SBPSCHs until the TDMA frame number indicated by the TBF starting time, at which time the mobile station shall start timer T3190 for each downlink TBF assigned in the downlink assignment message and immediately begin decoding the assigned downlink SBPSCH(s).

If the downlink assignment message contains a TBF starting time and there are one or more downlink TBFs already in progress, the mobile station shall continue to use the parameters of the downlink TBFs 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 for the same TBF, the mobile station shall act upon the most recently received downlink assignment and shall ignore the previous downlink assignment. Procedures on receipt of a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT message) while no TBF is in progress are specified in sub-clause sub-clause 7.3.2.1 and 3GPP TS 44.060 sub-clause 7.2.1.1.

If the mobile station receives a valid RLC data block addressed to (one of) its TBF(s), the mobile station shall restart timer T3190 for that TBF. If timer T3190 expires for a TBF and if one or more uplink TBFs are in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3, 3GPP TS 44.060 sub-clause 8.7.2). If no other TBFs are in progress, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1).

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

8.2.3.2.1 Abnormal cases

The following abnormal cases apply:

– If a mobile station receives a PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT 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.8.4), performing a partial acquisition of system information messages containing frequency information.

– If the information in the PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message incorrectly specifies one or more downlink PDCHs, the mobile station shall perform an abnormal release of the downlink TBF(s) with erroneous assignments (see sub-clause 8.8.6). The mobile station shall act upon the valid assignments.

– If the information in the PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message incorrectly specifies one or more uplink and/or downlink PDCHs, the mobile station shall perform an abnormal release of the downlink TBF(s) with erroneous assignments (see sub-clause 8.8.6). The mobile station shall act upon the valid assignments.

– If the information in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message violates the mobile station’s multislot capabilities, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2).

– If a mobile station in MAC-DTM state receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message including the Frequency Parameters information element, the mobile station shall abort the procedure. If another TBF exists on a SBPSCH, the mobile station shall continue the normal operation of these TBFs. If no other TBF exists, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2).

– If a mobile station in MAC-DTM state receives a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2).

– If one or more uplink TBFs are already established and the mobile station receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for the uplink TBF(s), the mobile station shall ignore the received message and continue normal operation of the existing TBFs.

– If the mobile station receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message containing assignments such that more than one radio bearer is mapped onto a TBF, then the mobile station shall perform an abnormal release without retry (see sub-clause 8.8.2).

– If the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message specifies an RB Id that is not assigned to the mobile station, then the mobile station shall perform an abnormal release without retry (sub-clause 8.8.2).

– If the mobile station receives a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT message so that the total amount of downlink TBFs assigned to the mobile station (i.e. new and existing TBFs) is larger than the maximum number of downlink TBFs the mobile station supports, the mobile station shall ignore the message and continue normal operation of the existing TBFs.

– If the mobile station receives a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message so that the total amount of TBFs assigned to the mobile station (i.e. new and existing TBFs) in any direction is larger than the maximum number of TBFs the mobile station supports in any direction, the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

8.2.3.3 Polling for Packet Downlink Ack/Nack

Whenever the mobile station receives an RLC data block addressed to (one of) its TBF(s) with a valid RRBP field in the RLC data block header (i.e. is polled), the mobile station may transmit one of the following messages in the uplink radio block specified by the RRBP field whatever the BSN value of the received RLC data block, according to the subsequent decreasing order of priority:

1) (EGPRS) PACKET DOWNLINK ACK/NACK message containing a Final Ack Indicator,

2) PACKET CELL CHANGE NOTIFICATION, if such a message is waiting to be transmitted,

3) (EGPRS) PACKET DOWNLINK ACK/NACK message containing a Channel Request Description IE,

4) any other RLC/MAC control message, if such a message is waiting to be transmitted, other than a (EGPRS) PACKET DOWNLINK ACK/NACK,

5) (EGPRS) PACKET DOWNLINK ACK/NACK message not containing a Final Ack Indicator or a Channel Request Description IE.

However, the mobile station shall transmit an RLC/MAC control message other than a (EGPRS) PACKET DOWNLINK ACK/NACK message at most every second time it is polled for that TBF.

The mobile station shall not send a PACKET CONTROL ACKNOWLEDGEMENT message unless otherwise specified.

In EGPRS TBF mode the mobile station shall react on a poll inside an erroneously received RLC data block for which the header is correctly received and which addresses the mobile station.

Whenever the network receives a valid RLC/MAC control message from the TBF, it shall reset counter N3105. The network shall increment counter N3105 for each radio block allocated to that TBF 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 for that TBF. When T3195 expires, the network may reuse the TFI.

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

The EGPRS PACKET DOWNLINK ACK/NACK message may contain an EGPRS Channel Quality Report (see 3GPP TS 45.008).

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 45.002).

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

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

8.2.3.4 Resource Reassignment for downlink

The network initiates downlink resource reassignment by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF DOWNLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE) to the mobile station on the PACCH.

If the mobile station has a TBF for which T3192 is running, the network may choose to reallocate this existing TBF and reuse the TFI value for the new data by setting the Control Ack bit to ‘1’ as specified in 3GPP TS 44.060 sub-clauses 9.3.2.6 and 9.3.3.5.

On receipt of a downlink assignment message and after the TBF starting time, if present, the mobile station shall switch to the assigned SBPSCHs. Upon switching to the new SBPSCHs the mobile station shall restart timer T3190 for each newly assigned downlink TBF.

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

8.2.3.5 Establishment of uplink TBF

8.2.3.5.0 General

The mobile station initiates the packet access procedure by sending the Iu mode Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message on the PACCH and starting timer T3168 for each TBF requested.

On receipt of an Iu mode Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message, the network may assign radio resources to the mobile station on one or more SBPSCHs by transmitting an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF UPLINK ASSIGNMENT or MULTIPLE TBF 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 an uplink assignment message the mobile station shall follow the procedure below. On reception of an uplink assignment message the mobile station shall stop timer T3168 for each TBF assigned in the message.

The mobile station shall, after expiry of the TBF starting time, if present, act upon the uplink assignment.

The mobile station shall then switch to the assigned uplink SBPSCHs and begin to send RLC data blocks on the assigned SBPSCH(s). The G-RNTI shall not be included in any of the uplink RLC data blocks.

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 for each TBF rejected in the PACKET ACCESS REJECT message and indicate a packet access failure to the 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 for each TBF rejected with the indicated value (Wait Indication). The mobile station is not allowed to make a new attempt for an uplink TBF establishment in the same cell until all instances of timer T3172 expire, but it may attempt uplink TBF establishment in another cell after successful cell reselection.

If timer T3168 expires for a TBF, the mobile station shall:

– if the mobile station has no existing uplink TBF:

– retransmit the Iu mode Channel Request Description information element in the next (EGPRS) PACKET DOWNLINK ACK/NACK message unless the Iu mode Channel Request Description has already been transmitted four times for that TBF in which case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3, 3GPP TS 44.060 sub-clause 8.7.2).

– if the mobile station has at least one uplink TBF:

– proceed with uplink TBF establishment as defined in sub-clause 8.2.2.1.2.

If the downlink TBF is released, including expiry of timer T3192, before expiry of timer T3168, the mobile station shall stop timer T3168 for each TBF and perform an abnormal release with access retry (see sub-clause 8.8.3, 3GPP TS 44.060 sub-clause 8.7.2).

8.2.3.5.1 Abnormal cases

In the following abnormal cases it is assumed that at least one downlink TBF exists. The subsequent behaviour of the mobile station depends on the type of failure and previous actions.

– If the mobile station receives a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message containing different frequency parameters than are currently in effect for its existing TBFs, the mobile station shall ignore the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message, continue normal operation of the existing TBFs, and reinitiate the establishment of the new uplink TBFs unless the establishment of any of these TBFs has already been attempted four times, in which case, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

– If a mobile station in MAC-DTM state receives a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

– If an uplink TBF is not already established and the PACKET TIMESLOT RECONFIGURE message does not include a UPLINK_TFI_ASSIGNMENT field, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If an uplink TBF is not already established and the MULTIPLE TBF TIMESLOT RECONFIGURE message does not assign any uplink TBFs, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If the mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message contains assignments such that more than one radio bearer is mapped onto a TBF, then the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

– If the MULTIPLE TBF UPLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE message does not specify a Channel Coding scheme for all of the uplink TBFs that it is assigning, then the mobile station shall perform an abnormal release with access retry of the uplink TBFs with erroneous assignments (see sub-clause 8.8.5). The mobile station shall act upon the valid assignments.

– If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF TIMESLOT RECONFIGURE message assigns the same USF to more than one TBF on the same timeslot, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE message specifies a RB Id that is not assigned to the mobile station, then the mobile station shall perform an abnormal release with access retry (sub-clause 8.8.3).

– If the PACKET ACCESS REJECT message includes one or more RB Id fields in the Iu mode Reject structure which were not included by the mobile station in the Iu mode Channel Request Description structure, then the mobile station shall perform abnormal release with access retry (see sub-clause 8.8.3).- If a mobile station in MAC-DTM state receives a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including the Frequency Parameters information element, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.8.3).

8.2.3.6 Network initiated abnormal release of downlink TBF

See 3GPP TS 44.060 sub-clause 8.1.2.8.

8.3 Packet PDCH Release

See 3GPP TS 44.060 sub-clause 8.2.

8.4 Procedure for measurement report sending in MAC-Shared state

See 3GPP TS 44.060 sub-clause 8.3.

8.5 Network Controlled cell reselection procedures in MAC-Shared state

See 3GPP TS 44.060 sub-clause 8.4.

8.6 Measurement Order procedures in MAC-Shared state

See 3GPP TS 44.060 sub-clause 8.5.

8.7 PACKET CONTROL ACKNOWLEDGEMENT

See 3GPP TS 44.060 sub-clause 8.6.

8.8 Abnormal cases

8.8.1 General

See 3GPP TS 44.060 sub-clause 8.7.0.

8.8.2 Abnormal release without retry

See 3GPP TS 44.060 sub-clause 8.7.1.

8.8.3 Abnormal release with access retry

The mobile station shall abort all TBFs in progress. The mobile station in MAC-Shared state shall return to MAC-Idle state and initiate the establishment of a new uplink TBF on SBPSCH(s), using the procedures on PCCCH, as defined in sub-clause 7.2.

The mobile station in MAC-DTM state shall return to MAC-Dedicated state and initiate the establishment of a new uplink TBF on SBPSCH(s) using DTM procedures on SRB2, as defined in 3GPP TS 44.118.

In case the mobile station fails to establish a new uplink TBF on SBPSCH(s), 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.4.1.8.

8.8.4 Abnormal release with system information

See 3GPP TS 44.060 sub-clause 8.7.3.

8.8.5 Abnormal release of an Uplink TBF with access retry

The mobile station shall abort the uplink TBF.

If there are no remaining TBFs on SBPSCHs and the mobile station was in MAC-Shared state, then it shall return to MAC-Idle state and reinitiate the establishment of the uplink TBF on SBPSCH(s) using the procedures on PCCCH, as defined in sub-clause 7.2. In the case that this TBF was not the last remaining TBF on SBPSCHs, the mobile station shall reinitiate the establishment of the TBF on SBPSCHs, using the procedures defined on PACCH, as defined in sub-clauses 8.2.3 and 8.3.3.

If there are no remaining TBFs on SBPSCHs and the mobile station was in MAC-DTM state, then it shall return to MAC-Dedicated state and initiate the establishment of the uplink TBF on SBPSCH(s) using DTM procedures on SRB2, as defined in 3GPP TS 44.118. In the case that this TBF was not the last remaining TBF on SBPSCHs, the mobile station shall initiate the establishment of the TBF on SBPSCHs, using the procedures defined on PACCH, as defined in sub-clauses 8.2.3 and 8.3.3

In case the mobile station fails to establish the new uplink TBF on SBPSCH(s), 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.4.1.8.

8.8.6 Abnormal release of a Downlink TBF

The mobile station shall abort the downlink TBF.

If there are no remaining TBFs on SBPSCHs and the mobile station was in MAC-Shared state, then it shall return to MAC-Idle state.

If there are no remaining TBFs on SBPSCHs and the mobile station in MAC-DTM state, then it shall return to MAC-Dedicated state.

If there is a TBF remaining on SBPSCHs, then the mobile station shall remain in its current state.

The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5, 3GPP TS 44.160 sub-clause 5.4.1.8.

8.9 Network Assisted Cell Change procedures in MAC-Shared state

See 3GPP TS 44.060 sub-clause 8.8.