8.1 Transfer of RLC data blocks
3GPP44.060General Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 17TS
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, exclusive allocation and fixed uplink allocation.
The exclusive allocation is applicable only in dual transfer mode and MAC-DTM state and shall be used on a half-rate PDCH. The fixed uplink allocation is applicable only for an uplink EC TBF.
8.1.1 Uplink RLC data block transfer
For a TBF operating in BTTI configuration, 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, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION) 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 that uplink TBF,
– or in case EMST is used, to the TFI value assigned to the corresponding RLC entity on that uplink TBF,
– or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on 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 and not applicable for dual carrier, multi carrier, BTTI with FANR activated, EGPRS2 configurations and EC TBFs);
– the PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures, or in case EMST is used, the PFI associated with each RLC entity on the allocated TBF, or in case EMSR is enabled for one or more RLC entities of the allocated TBF, the PFI associated with each PFC supported by these RLC entities.
– in case of an uplink EC TBF, the network also assigns the following parameters:
– a set of PDCHs to be used for transmission of downlink RLC/MAC control messages
– uplink and downlink coverage classes.
In case the RTTI configuration is supported by the network and the mobile station and an uplink TBF operating in RTTI configuration is assigned, the following parameters shall be provided by the network in the assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION).
– 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 that uplink TBF,
– or in case EMST is used, to the TFI value assigned to the corresponding RLC entity on that uplink TBF,
– or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on the uplink TBF;
– one or more PDCH-pairs to be used for the uplink transfer;
– the PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures, or in case EMST is used, the PFI associated with each RLC entity on the allocated TBF, or in case EMSR is enabled for one or more RLC entities of the allocated TBF, the PFI associated with each PFC supported by these RLC entities;
– BTTI USF or RTTI USF mode to be used when receiving USFs.
For each PDCH-pair forming part of an assignment for an uplink TBF operating in RTTI configuration, the network may additionally assign a corresponding downlink PDCH-pair which shall be monitored by the mobile station for the USF (see sub-clause 7.1.3.6).
The network may, at any time during uplink packet transfer, change the TTI configuration or USF mode (BTTI USF mode or RTTI USF mode) as well as the corresponding downlink PDCH-pairs of an already established uplink TBF by sending on the downlink PACCH, an uplink TBF assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). The mobile station shall begin using the new parameters within the reaction time defined in 3GPP TS 45.010.
In a Downlink Dual Carrier configuration, one or more PDCHs are assigned to a single mobile station on each of two different radio frequency channels. In a DLMC configuration, one or more PDCHs are assigned to a single mobile station on one or more of the uplink radio frequency channels that correspond to the downlink radio frequency channels assigned for the DLMC configuration. A mobile station with a Downlink Dual Carrier configuration or a DLMC configuration shall not be allocated radio blocks on multiple radio frequency channels during any given radio block period.
All the RLC data blocks of an uplink TBF initiated by one phase access, or for a mobile station in EC operation using the access burst procedure, see sub-clause 7a.2.1.1, shall each contain a TLLI (in A/Gb mode) or a G-RNTI (in Iu mode) 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, 7a.2.1.1. A mobile station in EC operation using the enhanced access burst procedure, see sub-clause 7a.2.1.2, shall only include the TLLI in the first RLC data block of the uplink TBF and the rTLLI in the RLC/MAC headers of the remaining RLC data blocks until the contention resolution is completed (see sub-clause 7a.2.1.2).After the reaction time specified in 3GPP TS 45.010 no other RLC data blocks shall contain a TLLI/rTLLI field (in A/Gb mode) or a G-RNTI (in Iu mode), except for those retransmitted RLC data blocks that originally contained a TLLI/rTLLI (in A/Gb mode) or a G-RNTI (in Iu mode), which will be repeated including the same TLLI/rTLLI (in A/Gb mode) or G-RNTI (in Iu mode) (see sub-clause 7.1.2.3a, 7a.2.1. The TLLI_BLOCK_CHANNEL_CODING parameter in the PACKET UPLINK ASSIGNMENT or in the MULTIPLE TBF UPLINK ASSIGNMENT message indicates whether a RLC data block containing a TLLI (in A/Gb mode) or a G-RNTI (in Iu mode) field in the RLC data block header shall be encoded using CS‑1 in GPRS TBF mode, or MCS-1 in EGPRS TBF mode, or using the commanded modulation and channel coding scheme (see 3GPP TS 45.003). 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 EC TBF mode, the first RLC data block shall be transmitted with the commanded MCS, except if the commanded mode is MCS-5-7, in which case the first RLC data block shall be transmitted with MCS‑5, or if the commanded mode is MCS-6-9, in which case the first RLC data block shall be transmitted with MCS-6. In the case of a Downlink Dual Carrier configuration or a DLMC configuration the commanded MCS shall apply to all of the uplink carriers for which PDCH resources have been assigned. 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.
For a TBF with FANR activated, if the commanded MCS is MCS-9 (respectively MCS-4), the initial transmission of the RLC data block(s) shall be done with MCS-8 (respectively MCS-3) if a PAN field is included in the radio block.
When EMST is used, the commanded MCS shall apply to the RLC entity on the TBF identified by the TFI included in the header of the RLC/MAC block.
A RESEGMENT bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message. In EC TBF mode a RESEGMENT bit is included in the EC PACKET UPLINK ACK/NACK or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message if it includes a Fixed Uplink Allocation. 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 when retransmissions are needed. 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 8.1.1.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.2), see note. In RLC unacknowledged mode, RESEGMENT bit shall be ignored and default value 0 should be used.
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 (EGPRS/EC-GSM-IoT)
|
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 |
MCS-6 |
MCS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
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 |
|
NOTE: 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 (EGPRS/EC-GSM-IoT)
|
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 |
|
NOTE: 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). |
|||||||||||
Table 8.1.1.3: Choice of modulation and coding scheme for retransmissions with re-segmentation (EGPRS2-A)
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UAS) |
||||||||||
|
UAS-11 Commanded |
UAS-10 Commanded |
UAS-9 Commanded |
UAS-8 Commanded |
UAS-7 Commanded |
MCS-6 Commanded |
MCS-5 Commanded |
MCS-4 Commanded |
MCS-3 Commanded |
MCS-2 Commanded |
MCS-1 Commanded |
|
|
UAS-11 |
UAS-11 |
UAS-8 |
UAS-8 |
UAS-8 |
MCS-6 (pad) |
MCS-6 (pad) |
MCS-3 (pad) |
MCS-3 (pad) |
MCS-3 (pad) |
MCS-3 (pad) |
MCS-3 (pad) |
|
UAS-10 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
MCS-5 |
MCS-5 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
|
UAS-9 |
UAS-9 |
UAS-9 |
UAS-9 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
UAS-8 |
UAS-11 |
UAS-8 |
UAS-8 |
UAS-8 |
MCS-6 |
MCS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
UAS-7 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
MCS-5 |
MCS-5 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
|
MCS-6 |
UAS-9 |
UAS-9 |
UAS-9 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
MCS-5 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
MCS-5 |
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.4: Choice of modulation and coding scheme for retransmissions without re-segmentation (EGPRS2-A)
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UAS) |
||||||||||
|
UAS-11 Commanded |
UAS-10 Commanded |
UAS-9 Commanded |
UAS-8 Commanded |
UAS-7 Commanded |
MCS-6 Commanded |
MCS-5 Commanded |
MCS-4 Commanded |
MCS-3 Commanded |
MCS-2 Commanded |
MCS-1 Commanded |
|
|
UAS-11 |
UAS-11 |
UAS-8 |
UAS-8 |
UAS-8 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UAS-10 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
|
UAS-9 |
UAS-9 |
UAS-9 |
UAS-9 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UAS-8 |
UAS-11 |
UAS-8 |
UAS-8 |
UAS-8 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UAS-7 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
|
MCS-6 |
UAS-9 |
UAS-9 |
UAS-9 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
MCS-5 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
MCS-5 |
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.5: Choice of modulation and coding scheme for retransmissions with re-segmentation (EGPRS2-B)
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UBS) |
|||||||||||
|
UBS-12 Commanded |
UBS-11 Commanded |
UBS-10 Commanded |
UBS-9 Commanded |
UBS-8 Commanded |
UBS-7 Commanded |
UBS-6 Commanded |
UBS-5 Commanded |
MCS-4 Commanded |
MCS-3 Commanded |
MCS-2 Commanded |
MCS-1 Commanded |
|
|
UBS-12 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
UBS-11 |
UBS-11 |
UBS-11 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
UBS-10 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
|
UBS-8 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
UBS-7 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
|
UBS-6 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
UBS-5 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-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-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-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-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 |
MCS-1 |
Table 8.1.1.6: Choice of modulation and coding scheme for retransmissions without re-segmentation (EGPRS2-B)
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UBS) |
|||||||||||
|
UBS-12 Commanded |
UBS-11 Commanded |
UBS-10 Commanded |
UBS-9 Commanded |
UBS-8 Commanded |
UBS-7 Commanded |
UBS-6 Commanded |
UBS-5 Commanded |
MCS-4 Commanded |
MCS-3 Commanded |
MCS-2 Commanded |
MCS-1 Commanded |
|
|
UBS-12 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
UBS-11 |
UBS-11 |
UBS-11 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
UBS-10 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
|
UBS-8 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
UBS-7 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
|
UBS-6 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
UBS-5 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-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-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-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-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 |
MCS-1 |
In EGPRS (EGPRS TBF) or in EC operation (EC TBF), if these rules require a transmission (either original transmission or retransmission) in a) MCS-7 or b) MCS-8 or c) 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) or case c). In case b), padding is permitted.
In EGPRS2, if these rules require a transmission (either original transmission or retransmission) in a modulation and coding scheme where there are fewer than the maximum number of RLC blocks that can be transmitted, the mobile station shall use the modulation and coding scheme specified in tables 8.1.1.7 and 8.1.1.8.
Table 8.1.1.7: Retransmissions with fewer RLC blocks (EGPRS2-A)
|
Modulation and Coding Scheme specified |
Modulation/Coding scheme to be used (only 1 block can be transmitted) |
Modulation/Coding scheme to be used (only 2 blocks can be transmitted) |
|
UAS-7 |
MCS-5 |
n/a |
|
UAS-8 |
MCS-6 (with padding) |
n/a |
|
UAS-9 |
MCS-6 |
n/a |
|
UAS-10 |
MCS-5 |
UAS-7 |
|
UAS-11 |
MCS-6 (with padding) |
UAS-8 |
Table 8.1.1.8: Retransmissions with fewer RLC blocks (EGPRS2-B)
|
Modulation and Coding Scheme Specified |
Modulation/Coding scheme to be used (only 1 block can be transmitted) |
Modulation/Coding scheme to be used (only 2 blocks can be transmitted) |
Modulation/Coding scheme to be used (only 3 blocks can be transmitted) |
|
UBS-7 |
UBS-5 |
n/a |
n/a |
|
UBS-8 |
UBS-6 |
n/a |
n/a |
|
UBS-9 |
UBS-5 |
UBS-7 |
n/a |
|
UBS-10 |
UBS-6 |
UBS-8 |
n/a |
|
UBS-11 |
UBS-6 (with padding) |
UBS-8 (with padding) |
UBS-10 (with padding) |
|
UBS-12 |
UBS-6 |
UBS-8 |
UBS-10 |
Modulation and coding schemes to be used for retransmissions after a transition from EGPRS to EGPRS2-A or EGPRS2-B or from EGPRS2-A or EGPRS2-B to EGPRS are specified in sub-clause 8.1.1.7.2.
For a TBF with FANR activated, if these rules require a retransmission in MCS-9 and a PAN field is included in an EGPRS RLC/MAC block for data transfer, the mobile station shall use MCS-6. If these rules require a retransmission in MCS-4, a PAN field is to be included in an EGPRS RLC/MAC block for data transfer and re-segmentation is allowed, the mobile station shall use MCS-1. If these rules require a retransmission in MCS-4 and re-segmentation is not allowed, the mobile station shall use MCS-4 and shall not include a PAN field in this retransmission.
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 45.010.
Upon receipt of any message containing an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET UPLINK ACK/NACK or PACKET CS RELEASE INDICATION message), the mobile station shall be ready to transmit in accordance with the requirements given in 3GPP TS 45.010.
The mobile station shall transmit RLC/MAC blocks with the following priority:
– RLC/MAC control blocks containing a PACKET CS REQUEST message;
– RLC/MAC control blocks containing a PACKET CELL CHANGE NOTIFICATION message;
– Other RLC/MAC control blocks, except
– Packet Uplink Dummy Control Blocks; and
– RLC/MAC control block containing an EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message, when the mobile station is polled for a PAN (see sub-clause 10.4.4a);
– RLC data blocks (including a PAN field if required. See sub-clauses 8.1.2.2, 9.1.8.2.1 and 9.1.14.3.) except RLC data blocks including a PAN which is sent in response to a poll where all the element(s) of V(B) have the value TENTATIVE_ACK or ACKED;
– when the mobile station is polled for a PAN (see sub-clause 10.4.4a), RLC/MAC control block containing an EGPRS PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 or EGPRS PACKET DOWNLINK ACK/NACK DLMC message;
– RLC data block including a PAN which is sent in response to a poll where all the elements of V(B) have the value TENTATIVE_ACK or ACKED;
– RLC/MAC control blocks containing Packet Uplink Dummy Control Blocks.
A mobile station in EC operation shall only send RLC data blocks according to the fixed uplink allocation received in the assignment message or in the EC PACKET UPLINK ACK/NACK or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message.
If an uplink TBF operating in MTTI configuration and operating in EGPRS RLC acknowledged mode is allocated RTTI and BTTI radio blocks whose transmissions start in the same TDMA frame, the mobile station shall determine which (if any) RLC data blocks to transmit on the RTTI resources according to the above rules and those in sub-clause 9.1.3.2.1 before determining which (if any) RLC data blocks to transmit on the BTTI resources, regardless of the relative numbering of the timeslots used for the RTTI and BTTI resources.
NOTE: Within the respective reaction times specified in 3GPP TS 45.010 at uplink assignment, change of coding scheme and completion of the contention resolution at one phase access, the mobile station may send RLC/MAC control blocks containing Packet Uplink Dummy Control Blocks, if there is no other block ready to be transmitted.
In A/Gb mode, during the TBF, if the countdown procedure has not started or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and multiple TBF procedures are not supported (i.e. the mobile station or the network does not support multiple TBF procedures) 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), in the following cases;
– When the mobile station has indicated Page Response, Cell update or Mobility Management procedure as access type in the PACKET CHANNEL REQUEST message 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 or EGPRS PACKET CHANNEL REQUEST message;
– When the mobile station has indicated ‘Signalling’ as access type in the EGPRS PACKET CHANNEL REQUEST message and it has data to send.
An exception is the case of a mobile station using an EC TBF where PACKET RESOURCE REQUEST is not supported.
In A/Gb mode or Iu mode, a mobile station that supports multiple TBF procedures shall send a PACKET RESOURCE REQUEST message to a network supporting multiple TBF procedures (see sub-clause 8.1.1.1.2), if it has data to send for one or more PFCs (A/Gb mode) or RBs (Iu mode) for which no uplink TBFs are established.
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, MAC-Shared State, dual transfer mode or MAC-DTM state.
When the mobile station receives an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) that does not contain a TBF starting time, if the uplink TBF is assigned in BTTI configuration the mobile station shall begin monitoring the downlink PDCHs corresponding to (i.e. with the same timeslot number as) the assigned uplink PDCHs for the assigned USF value for each assigned uplink PDCH within the reaction time defined in 3GPP TS 45.010. Alternatively, if the uplink TBF is assigned in RTTI configuration, the mobile station shall begin monitoring the downlink PDCH-pairs corresponding to the assigned uplink PDCH-pairs for the assigned USF value within the reaction time defined in 3GPP TS 45.010. If a TBF starting time information element is present and no uplink TBFs are in progress, but one or more downlink TBFs are in progress, the mobile station shall wait until the starting time before beginning to monitor the USFs and using the newly assigned uplink TBF parameters. While waiting for the starting time, the mobile station shall monitor the assigned downlink PDCHs. If a TBF starting time information element is present and one or more uplink TBFs are already in progress, the mobile station shall continue to use the assigned parameters of the ongoing uplink TBFs 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. The mobile station shall continue to use the newly assigned parameters of each uplink TBF until the TBF is either released or reconfigured. 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 a mobile station has requested multiple uplink TBFs in a PACKET RESOURCE REQUEST message, the network may allocate resources for these TBFs by sending one or more uplink assignment messages in response (see sub-clause 8.1.1.1.2). The mobile station shall act upon each successive uplink assignment message as it is received.
A mobile station that has a TBF operating in BTTI configuration shall monitor all the downlink PDCHs corresponding to the assigned uplink PDCHs except if the mobile station is in DTR mode (see sub-clause 8.1.8). When operating a TBF in RTTI configuration, the mobile station shall monitor the corresponding downlink PDCH-pairs associated with the assigned uplink PDCH-pairs that can be monitored according to the number of allocated uplink PDCH-pairs and its multislot capabilities except if the mobile station is in DTR mode (see sub-clause 8.1.8).
Whenever the mobile station detects an assigned USF value on a monitored downlink PDCH or PDCH-pair, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH or corresponding PDCH-pair for that TBF except if that TBF is running in extended uplink TBF mode, in which case the mobile station may transmit RLC/MAC block(s) for other TBFs assigned on the same PDCH or corresponding PDCH-pair (see sub-clause 9.3.1b.2). 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 45.002. The number of RLC/MAC blocks to transmit is controlled by the USF_GRANULARITY parameter characterising the uplink TBF.
For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching requirements of its multislot class (see 3GPP TS 45.002).
An uplink TBF operating in RTTI configuration may receive the assigned USFs either in RTTI USF mode or BTTI USF mode. The USF mode is indicated during the assignment of the corresponding uplink TBF.
For an uplink TBF in RTTI configuration that receives the USFs in BTTI USF mode:
– An assigned USF received on the first PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the first two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair, depending on the value of USF_GRANULARITY.
– An assigned USF received on the second PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the second two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair, depending on the value of USF_GRANULARITY.
For an uplink TBF in RTTI configuration that receives the USFs in RTTI USF mode:
– An assigned USF received on a monitored downlink PDCH-pair in the first reduced radio block period of a given basic radio block period allocates resources for one or four uplink RTTI radio blocks in the second reduced radio block period starting in the same basic radio block period and continuing with the second reduced radio block period in the following basic radio block periods on the corresponding uplink PDCH-pair, depending on the value of USF_GRANULARITY.
– An assigned USF received on a monitored downlink PDCH-pair in the second reduced radio block period of a given basic radio block period allocates resources for one or four uplink RTTI radio blocks in the first reduced radio block period starting in the next basic radio block period and continuing with the first reduced radio block period in the following basic radio block periods on the corresponding uplink PDCH-pair, depending on the value of USF_GRANULARITY.
The time relation between the uplink radio block(s) which the mobile station shall use for transmission and the occurrence of the USF value is further defined in 3GPP TS 45.002
In a Downlink Dual Carrier configuration, one or more PDCHs are assigned to a single mobile station on each of two different radio frequency channels. In a DLMC configuration, one or more PDCHs are assigned to a single mobile station on one or more of the uplink radio frequency channels that correspond to the downlink radio frequency channels assigned for the DLMC configuration. A mobile station with a Downlink Dual Carrier configuration or a DLMC configuration shall not be allocated radio blocks on more than one radio frequency channel during any given radio block period.
When the mobile station transmits an RLC/MAC block to the network, it shall start timer T3180 for the uplink TBF on which the block was sent. When the mobile station detects an assigned USF value on a downlink PDCH corresponding to an assigned uplink PDCH for that TBF, the mobile station shall restart timer T3180. If any given timer T3180 expires, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2 (A/Gb mode)).
Whenever the network receives a valid RLC/MAC block for any given TBF, it shall reset counter N3101 for that TBF. The network shall increment counter N3101 for each radio block, allocated to that TBF, for which no data is received. If N3101 = N3101max, the network shall stop the scheduling of RLC/MAC blocks for that TBF and start timer T3169. When T3169 expires, the network may reuse the USF and TFI(s) assigned to that TBF. If PS Handover is ongoing it is optional for the network to increment N3101.
8.1.1.1.1 PACCH operation
The mobile station shall attempt to decode every downlink RLC/MAC block on all the downlink PDCHs corresponding to (i.e. with the same timeslot number as) the assigned uplink PDCHs when the uplink TBF operates in BTTI configuration except if the mobile station is in DTR mode (see sub-clause 8.1.8).
In case the uplink TBF operates in RTTI configuration the mobile station shall attempt to decode every downlink RLC/MAC block on the corresponding downlink PDCH-pairs being monitored (see subclause 8.1.1.1) except if the mobile station is in DTR mode (see sub-clause 8.1.8).
Downlink PACCH blocks shall be received in the same TTI configuration as the assigned 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 addresses the mobile station, the mobile station shall act on the message.
Whenever a mobile station, that has an assigned uplink TBF operating in BTTI configuration, detects an assigned USF value on any downlink PDCH corresponding to an assigned uplink PDCH, the mobile station may transmit a PACCH block on the same PDCH in the next block period (see 3GPP TS 45.002). Whenever a mobile station, that has an assigned uplink TBF operating in RTTI configuration, detects an assigned USF value on any corresponding downlink PDCH-pair associated with an assigned uplink PDCH-pair, the mobile station may transmit a PACCH block on the PDCH-pair. The PACCH block shall be transmitted according to the USF scheduling in sub-clause 8.1.1.1. The mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see sub- clauses 10.4.4, 10.4.4a, 10.4.4b) unless the uplink TBF operates in either RTTI configuration, or in BTTI configuration with FANR activated, and the mobile station is polled for a Piggy-backed Ack/Nack (see sub-clause 10.4.4b).
In the case of a Downlink Dual Carrier configuration or a DLMC configuration, all segments belonging to each RLC/MAC control message shall be sent on PACCH blocks belonging to the same carrier.
When a mobile station in a DLMC configuration supporting more than 20 downlink timeslots sends an EGPRS Packet Downlink Ack/Nack DLMC message (see sub-clause 11.2.48) it shall be coded using CS-1 or CS-3 as indicated by the most recently received assignment message. Otherwise, if it supports 20 or less downlink timeslots, EGPRS Packet Downlink Ack/Nack DLMC messages shall be coded using CS-1.
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. If a new mode is assigned by the network for an already established TBF, the MS shall ignore the new assigned mode and shall maintain the TBF in the old mode.
During an uplink packet transfer, upper layers may request to transfer another upper layer 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 upper layer PDU containing signalling shall be treated as having the highest Radio Priority, an implementation specific peak throughput class and the acknowledged RLC mode shall be requested.
If the mobile station or the network does not support multiple TBF procedures the following procedures apply unless resource reallocation is not needed when EMSR is enabled (see sub-clause 5.12):
– If the mobile station has not started the countdown procedure or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and the new upper layer PDU has the same RLC mode as the current uplink TBF, or in case EMST is used, the new upper layer PDU has the same RLC mode as any of the RLC entities allocated on the ongoing 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 upper layer PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. Then the mobile station shall complete the transmission of the current upper layer PDU;
– If the new upper layer PDU has the same RLC mode as the current uplink TBF, or in case EMST is used, the new upper layer PDU has the same RLC mode as any of the RLC entities allocated to the ongoing 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 upper layer PDU in transfer. When the sending of upper layer 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 upper layer PDU(s) by sending a PACKET RESOURCE REQUEST message on the PACCH and start timer T3168 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. However if the upper layer PDUs at the higher Radio Priority does not completely fill the RLC data block the MS shall fill this RLC data block with payload from the new upper layer PDUs and then either transmit first the PACKET RESOURCE REQUEST message and subsequently the RLC data block or vice versa.
– If the mobile station or the network does not support EMST, and if the new upper layer 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 upper layer PDU using the countdown procedure including acknowledgement from the network, if in RLC acknowledged mode. If the TBF is operated in non-extended uplink TBF mode, the mobile station shall then release the TBF and establish a new uplink TBF for transmission of the new upper layer PDU. If the TBF is operated in extended uplink TBF mode (see sub-clause 9.3.1b), the mobile station shall use the procedure in sub-clause 8.1.1.6 for changing the RLC mode. When the sending of upper layer 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 upper layer PDU(s);
– If both the mobile station and the network support EMST, the TBF is operated in extended uplink TBF mode, and the new upper layer PDU does not have the same RLC mode as any of the RLC entities allocated to the ongoing uplink TBF, the mobile station shall immediately request a resource reallocation for uplink according to the Radio Priority and peak throughput class of the new upper layer PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. Then the mobile station shall continue the transmission of the current upper layer PDU;
– If the mobile station has not started the countdown procedure or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and the new upper layer PDU does not have the same PFI but has the same radio priority and the same peak throughput class as the current uplink TBF, or if EMST is used, as one of the current RLC entities, 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 for the uplink TBF requested in the PACKET RESOURCE REQUEST message. Then the mobile station shall complete the transmission of the current upper layer PDU.
If both the mobile station and the network support multiple TBF procedures the following procedures apply:
– The mobile station shall initiate a request for one or more new uplink TBFs when it has upper layer PDUs associated with one or more PFIs for which there are no ongoing uplink TBFs. In this case it sends a PACKET RESOURCE REQUEST message on the PACCH and starts an instance of timer T3168 for each uplink TBF requested;
– All ongoing uplink TBFs shall continue to operate using their currently allocated resources.
If both the network and the mobile station support the extended uplink TBF mode, the request from upper layers may indicate that the new upper-layer PDU is meant to pre-allocate an uplink TBF (early TBF establishment). In this case, the EARLY_TBF_ESTABLISHMENT field in the PACKET RESOURCE REQUEST message shall indicate pre-allocation is required.
On receipt of the PACKET RESOURCE REQUEST message the network shall respond by sending either an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE) or a PACKET ACCESS REJECT message to the mobile station on the downlink PACCH. If the mobile station supports RLC non-persistent mode the network may allocate one or more EGPRS TBFs that use this RLC mode.
If the mobile station or the network does not support multiple TBF procedures, then after the transmission of the PACKET RESOURCE REQUEST message with the reason for changing PFI, the radio 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 radio priority or peak throughput class is already assigned to that TBF.
If both the mobile station and the network support multiple TBF procedures, then after transmission of a PACKET RESOURCE REQUEST message the mobile station shall maintain its ongoing uplink TBFs using their currently allocated TBF parameters.
On receipt of an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) sent in response to a PACKET RESOURCE REQUEST message the mobile station shall stop timer T3168 for each uplink TBF assigned in the assignment message and switch to the assigned PDCHs. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.2.5.
If the mobile station or the network does not support multiple TBF procedures, 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 upper layer PDU(s) at a lower Radio Priority has to be continued.
If the mobile station or the network does not support multiple TBF procedures, upon 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 which case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).
If both the mobile station and the network support multiple TBF procedures, then upon expiry of all instances of timer T3168 the mobile station shall retransmit the PACKET RESOURCE REQUEST message to request resources for those uplink TBFs that did not receive an uplink assignment unless the PACKET RESOURCE REQUEST message has already been transmitted four times without receiving any uplink assignment in response. In this case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).
If no assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) addressing any requested uplink TBF is received before the mobile station has completed its currently assigned TBFs the mobile station shall stop all instances of timer T3168.
The network may at any time during uplink packet transfer initiate a change of resources by sending on the downlink PACCH monitored by the MS, an unsolicited uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) to the mobile station. During the reallocation, TFI is allowed to be changed. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.2.5.
When an uplink TBF is established in response to a PACKET RESOURCE REQUEST message with the EARLY_TBF_ESTABLISHMENT field set to indicate pre-allocation is required, a network supporting early TBF establishment should keep the uplink TBF open by means of the extended uplink TBF mode operation (see sub-clause 9.3.1b.2).
On receipt of a PACKET ACCESS REJECT message, the mobile station shall stop timer T3168, if running, for the TBFs rejected in the PACKET ACCESS REJECT message, abort the uplink TBFs and indicate a packet access failure to the upper layer associated with each rejected TBF. If no more uplink or downlink TBFs exist, 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:
– If the mobile station or the network does not support multiple TBF procedures, 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;
– If both the mobile station and the network support multiple TBF procedures the mobile station shall start one instance of timer T3172 for each uplink TBF that was rejected. All TBFs in progress that are not rejected shall be maintained. The mobile station is not allowed to attempt re-establishment of a rejected uplink TBF in the same cell until its associated instance of timer T3172 expires. It may, however, attempt re-establishment of a rejected uplink TBF in another cell after successful cell reselection. The mobile station may attempt to enter the dedicated mode in the same cell before all instances of timer T3172 have expired. During the time one or more instances of T3172 are 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 an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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 an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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 information in the PACKET UPLINK ASSIGNMENT or the MULTIPLE TBF UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), 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, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), 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 a 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.7.2);
– If a mobile station in dual transfer mode receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, 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, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message indicating a change of EGPRS level which is forbidden (see sub-clause 8.1.1.7), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support multiple TBF procedures and if any given uplink assignment message provides an uplink TBF allocation for a PFI not indicated in the PACKET RESOURCE REQUEST message and not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST or EMSR and if any given uplink assignment message provides an allocation of an RLC entity for a PFI not indicated in the PACKET RESOURCE REQUEST message and not associated with any already allocated RLC entity on the uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2);
– If a failure in the uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) is due to any other reason (including frequency parameters which do not comply with the requirements specified in sub-clause 5.5.1.7), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).
NOTE: An uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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 the establishment of one or more downlink TBFs by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET CS RELEASE INDICATION) to the mobile station on the PACCH. If a PACKET TIMESLOT RECONFIGURE or a PACKET DOWNLINK ASSIGNMENT message is sent, then the message shall contain the DOWNLINK_TFI_ASSIGNMENT field for the downlink TBF being established. If multiple TBF procedures are supported by the mobile station and the network, the network shall indicate the PFI associated with each TBF it allocates or reallocates in the downlink assignment message. The network shall not attempt to establish multiple downlink TBFs for a mobile station with only one uplink TBF unless the mobile station’s radio access capabilities are known. If EMST is used, the network shall indicate the PFI associated with each RLC entity in the downlink assignment message (i.e. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). The multislot restrictions of the mobile station shall be observed.
A mobile station that supports multiple TBF procedures shall act on the downlink assignment message as follows:
– Upon reception of a PACKET DOWNLINK ASSIGNMENT message the mobile station shall release all ongoing downlink TBFs not addressed by this message and shall act on the message. All ongoing uplink TBFs shall be maintained;
– Upon reception of a PACKET TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message;
– Upon reception of a MULTIPLE TBF DOWNLINK ASSIGNMENT message the mobile station shall maintain all ongoing TBFs not addressed by this message using its currently allocated TBF parameters and shall act on the message;
– Upon reception of a MULTIPLE TBF TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message;
– Upon reception of a PACKET CS RELEASE INDICATION message the mobile station shall release all ongoing uplink and/or downlink TBFs not addressed by this message and shall act on the message.
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.
If the network and mobile station both support Downlink Dual Carrier, the network may send a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION) to a mobile station assigning one or more TBFs with packet resources on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration.
If the assignment message contains the Assignment Info IE indicating an assignment type other than ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs on the carrier identified by the Carrier ID field. In this case, if the assignment message addresses TBFs that currently have packet resources assigned on the other carrier (i.e. the carrier not identified by the Carrier ID field) then these packet resources shall be treated as follows:
– these resources are implicitly released, if the ASSIGNMENT TYPE field (carried in the Assignment Info IE) indicates that the assignment is an ‘Assignment on single carrier only’;
– these resources are unchanged, if the ASSIGNMENT TYPE field indicates that the assignment is a ‘Modification of existing assignment’.
If the assignment message contains the Assignment Info IE indicating an assignment type of ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs.
If the network and mobile station both support Downlink Multi Carrier, the network may send a downlink assignment message (PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE) to a mobile station assigning a downlink TBF with packet resources on multiple downlink carriers and thereby establish a DLMC configuration. In this case a mobile station is assigned a set of one or more UFPSs (see 3GPP TS 45.008 [15]) that in total provide up to 16 carriers. The carriers assigned to a given UFPS shall belong to the same frequency band and Mobile Allocation. If the MS has indicated it supports inter-band reception (see 3GPP TS 24.008) the set of provided carriers shall belong to a maximum of two of the supported frequency bands. The set of UFPS in a DLMC configuration are numbered UFPS1, UFPS2, and so on, ending with UFPSM where UFPS numbering is managed as follows:
– If an assignment message is sent to a mobile station with an ongoing downlink TBF for which only a single carrier is assigned then that carrier shall be considered as UFPS1 for the case where the assignment message establishes a DLMC configuration information.
– An assignment message that assigns one or more new UFPS results in each new UFPS being numbered according to the order in which it was assigned. For example, if UFPS1 and UFPS2 are currently assigned and two new UFPS are added then the first new UFPS becomes UFPS3 and the second new UFPS becomes UFPS4.
– An assignment message that deletes one or more existing UFPS results in the remaining UFPS being renumbered to ensure sequential UFPS numbering. For example, if UFPS1, UFPS2 …UFPS5 are currently assigned and UFPS3 is deleted then UFPS4 becomes UFPS3 and UFPS5 becomes UFPS4.
The carriers associated with a DLMC configuration are numbered in ascending order beginning with C1, followed by C2, and so on, ending with CN where the carriers are sequentially numbered beginning with those in UFPS1, followed by those in UFPS2 and so on, ending with those in UFPSM. The ordering of carriers within a given UFPS reflects the order in which they have been assigned for that UFPS (i.e. C1 is first carrier assigned for UFPS1).
If PDCH-pairs are assigned for a DLMC configuration they are numbered in ascending order starting with the lowest numbered PDCH-pair on C1 and ending with the highest numbered PDCH-pair on CN:
– The RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DLMC bitmap indicates which of the PDCH pairs available on a given downlink carrier (indicated by the DOWNLINK_PDCH_PAIRS_DLMC bitmap) are assigned for DLMC configuration.
– The PDCH pairs identified by the UPLINK_PDCH_PAIRS_DLMC bitmap (if any) indicate the PDCH-pairs assigned for the uplink carrier corresponding to a given downlink carrier assigned for a DLMC configuration.
– When downlink PDCH pairs are assigned they are numbered in ascending order starting with the first PDCH-pair (PDCH-pair 1) consisting of the two lowest numbered timeslots assigned on C1, followed by the PDCH-pair consisting of the next two lowest numbered timeslots assigned on C1 (PDCH-pair 2), and so on for the remaining timeslot pairs assigned on C1 and for the assigned timeslot pairs on C2… CN.
– The highest numbered PDCH-pair consists of the two highest numbered timeslots on carrier CN.
A mobile station in a DLMC configuration may receive subsequent assignment messages (PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE) as follows:
– A PACKET UPLINK ASSIGNMENT message may be used to assign packet resources on one or more of the uplink carriers corresponding to the assigned downlink carriers (see sub-clause 8.1.1.2.1) for the case where the ongoing downlink TBF does not need to be modified.
– A PACKET DOWNLINK ASSIGNMENT message may be used for the case where there is either no uplink TBF or the ongoing uplink TBF does not need to be modified. For the case of an ongoing uplink TBF, this message is only used if all carriers on which USF is currently monitored remain assigned.
– Otherwise, the PACKET TIMESLOT RECONFIGURE message is used.
On receipt of a downlink assignment message, and after the TBF starting time, if present, the mobile station shall switch to the assigned PDCHs, and start timer T3190 for each of the TBFs assigned. The operation of the downlink TBFs 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 a downlink TBF over RLC/MAC control blocks associated with an uplink TBF;
– if a timer or counter expiry causes an uplink TBF to be aborted in the mobile station, the mobile station shall perform an abnormal release with access retry as specified in sub-clause 8.7.2 (A/Gb mode);
– If one uplink and one downlink TBF are already established, then the network may send a PACKET TIMESLOT RECONFIGURE message without DOWNLINK_TFI_ASSIGNMENT or, for a DLMC configuration, without DOWNLINK_eTFI_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(s) 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 or MULTIPLE TBF TIMESLOT RECONFIGURE message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If one uplink and one downlink TBF 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 or MAC-DTM state receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) including frequency parameters for the carrier supporting the dedicated resources, 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 or MULTIPLE TBF TIMESLOT RECONFIGURE message 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 both the mobile station and the network support multiple TBF procedures and if any given downlink assignment message provides an uplink TBF allocation for a PFI not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that does not support Downlink Dual Carrier receives a PACKET DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF DOWNLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on more than one carrier or includes the Assignment Info IE which indicates that the assignment is a ‘Modification of an existing assignment’ or a ‘Dual Carrier assignment’, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile which supports Downlink Dual Carrier receives a PACKET DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF DOWNLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on two carriers and those two carriers are not within the same frequency band, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration wherein resources are assigned on carriers in different frequency bands but does not support inter-band reception, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration with more carriers or more downlink timeslots than it supports, or assigns eTFIs or a SNS of 8192 or CS-3 for PDAN coding when the mobile station supports 20 or fewer time slots, or assigns carriers in a frequency band it does not support, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message that modifies a DLMC configuration that releases carriers on which USF is being monitored, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that assigns two or more UFPSs to the same Mobile Allocation (as defined by the DLMC Frequency Parameter IE), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET UPLINK ASSIGNMENT message that modifies a DLMC configuration by assigning an uplink carrier that does not correspond to an existing downlink carrier, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS RELEASE INDICATION message is due to any other reason (including the presence of frequency parameters which do not comply with the requirements specified in sub-clause 5.5.1.7), the mobile station shall abort the procedure and continue the normal operation of the ongoing uplink TBFs and ongoing downlink TBFs.
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 and MULTIPLE TBF UPLINK ASSIGNMENT messages assign to the mobile station a subset of 1 to N uplink PDCHs (when the uplink TBF operates in BTTI configuration) or uplink PDCH-pairs (when the uplink TBF operates in RTTI configuration), where N depends on the mobile station multislot class.
An uplink TBF that operates in RTTI configuration may receive the assigned USFs either in BTTI USF mode or in RTTI USF mode. The indication of whether BTTI USF mode or RTTI USF mode is to be used is provided during the assignment of the corresponding uplink TBF.
If a mobile station supports Downlink Dual Carrier, the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message may assign PDCHs (corresponding to any given uplink TBF) on more than one carrier frequency. If this occurs, the Extended Dynamic Allocation procedures shall operate independently on each of the two carriers.
A mobile station with a DLMC configuration shall only act on a PACKET UPLINK ASSIGNMENT message if it includes the DLMC UL Carrier Info IE (see sub-clause 11.2.29). In this case the message may reference one or more of the uplink carriers corresponding to the set of downlink carriers and indicate the following:
– The referenced uplink carrier is not part of the uplink TBF in which case all resources for that uplink carrier (if any) are released.
– The referenced uplink carrier is part of the uplink TBF. If the message assigns no resources for that carrier then its existing resources remain unchanged. Otherwise, the assigned resources shall replace the existing resources (if any) for that carrier.
– If the message does not reference an uplink carrier then all resources for that uplink carrier (if any) are released.
A mobile station that has an uplink TBF operating in BTTI configuration shall monitor the downlink PDCHs corresponding to (i.e. with the same timeslot number as) its assigned uplink PDCHs starting with the lowest numbered PDCH, then the next lowest numbered PDCH, etc., up to the one corresponding to the highest numbered assigned uplink PDCH except if the mobile station is in DTR mode. A mobile station in DTR mode shall only monitor the timeslot indicated in the DTR information (see sub-clause 8.1.8). A mobile station that has an uplink TBF operating in RTTI configuration shall monitor the downlink PDCH-pairs starting with the one corresponding to the uplink PDCH-pair with the lowest numbered timeslots, then the next uplink PDCH-pair, etc., up to the downlink PDCH-pair corresponding to the uplink PDCH-pair with the highest numbered timeslots assigned to the mobile station except if the mobile station is in DTR mode. A mobile station in DTR mode shall only monitor the downlink PDCH-pair indicated in the DTR information (see sub-clause 8.1.8). When in dual transfer mode, the network shall not assign uplink PDCHs whose corresponding downlink PDCH cannot be monitored by the mobile station because of the presence of the uplink dedicated channel. As an exception, in the case of dual transfer mode, if the mobile station indicates support of DTM high multislot class capability, the network may also assign uplink PDCHs whose corresponding downlink PDCH cannot be monitored by the mobile station. In this case, the mobile station shall monitor only those downlink PDCHs that are feasible when taking into account the position of the uplink dedicated channel and the switching requirements of its multislot class (see 3GPP TS 45.002).
Whenever a mobile station with an uplink TBF operating in BTTI configuration detects an assigned USF value on a monitored PDCH, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the corresponding uplink PDCH (i.e. with the same timeslot number as the downlink PDCH on which the USF was detected) and on all higher numbered assigned uplink PDCHs except if it is in DTR mode. A mobile station in DTR mode shall perform any necessary uplink transmissions upon the detection of its assigned USF(s) using Dynamic Allocation procedures as specified in sub-clause 8.1.1.1.
The following applies for an uplink TBF in RTTI configuration that receives USFs in BTTI USF mode:
– An assigned USF received on the first PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the first two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots.
– An assigned USF received on the second PDCH of a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the second two TDMA frames of the following basic radio block period(s) on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots.
The following applies for an uplink TBF in RTTI configuration that receives USFs in RTTI USF mode:
– An assigned USF received in the first reduced radio block period of a given basic radio block period on a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the second reduced radio block period starting in the same basic radio block period and continuing with the second reduced radio block period in the following basic radio block periods, depending on the USF granularity, on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots.
– An assigned USF received in the second reduced radio block period of a given basic radio block period on a monitored downlink PDCH-pair allocates resources for one or four uplink RTTI radio blocks in the first reduced radio block period starting in the next basic radio block period and continuing with the first reduced radio block period in the following basic radio block periods, depending on the USF granularity, on the corresponding uplink PDCH-pair and all assigned uplink PDCH-pairs with higher numbered timeslots.
The following applies for an uplink TBF operating in an MTTI configuration when BTTI USF mode is used (i.e. RTTI_USF_MODE is set to ‘0’):
– An assigned USF received on the first or second PDCH of a monitored downlink PDCH-pair allocates resources as specified above for the case of an uplink TBF in RTTI configuration where USFs are received in BTTI USF mode. In addition, if, within the MTTI configuration, the uplink BTTI resource uses a higher numbered timeslot number than the RTTI resources, an assigned USF received on the first PDCH of a monitored downlink PDCH-pair (i.e. a PDCH-pair that corresponds to an uplink PDCH-pair that is part of the uplink MTTI configuration) allocates resources for one or four uplink BTTI radio blocks using the BTTI resources within the MTTI configuration.
– An assigned USF received on the downlink PDCH that corresponds to the uplink BTTI PDCH resource allocates resources for one or four uplink BTTI radio blocks using the BTTI resources within the MTTI configuration and, if the uplink RTTI resources use higher numbered timeslots than the uplink BTTI resource, two or eight uplink RTTI radio blocks (i.e. in both the first and second reduced radio block periods in the subsequent basic radio block period(s)) for each assigned RTTI PDCH-pair within the MTTI configuration.
NOTE: Examples of allocations of MTTI resources are given in Annex M.
The following applies for an uplink TBF operating in an MTTI configuration when RTTI USF mode is used (i.e. RTTI_USF_MODE is set to ‘1’):
– An assigned USF received in RTTI USF mode (i.e. on a downlink PDCH-pair corresponding to an assigned uplink PDCH-pair) allocates resources only for the assigned uplink RTTI resources, in accordance with the specifications for RTTI-only assignments. RTTI USFs do not allocate the uplink BTTI PDCH within an MTTI configuration.
– An assigned USF received on the downlink PDCH corresponding to the uplink BTTI PDCH resource allocates resources for one or four uplink BTTI radio blocks using the BTTI resources within the MTTI configuration. In addition, if, within the MTTI configuration, the uplink BTTI resource uses a lower numbered timeslot number than the RTTI resources, then an assigned USF received on the downlink PDCH corresponding to the uplink BTTI PDCH resource allocates resources for two or eight uplink RTTI radio blocks (i.e. in both the first and second reduced radio block periods in the subsequent basic radio block period(s)) for each assigned RTTI PDCH-pair within the MTTI configuration.
For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching time requirements of its multislot class (see 3GPP TS 45.002).
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 45.002. The number of RLC/MAC blocks to transmit on each allocated uplink PDCH/PDCH-pair is controlled by the USF_GRANULARITY parameter characterising the uplink TBF. The mobile station shall, in either BTTI or RTTI configuration, ignore the USF on those higher numbered PDCHs or PDCH-pairs with higher numbered timeslots during the block period where the assigned USF value is detected. In addition, if USF_GRANULARITY is set to four blocks allocation, it may ignore the USF on all other PDCHs/PDCH-pairs during the first three block periods in which the mobile station has been granted permission to transmit. As specified in 3GPP TS 45.002, the USF corresponding to the last three blocks of a four blocks allocation shall be set to an unused value for each PDCH/PDCH-pair on which the mobile station has been granted permission to transmit.
The mobile station shall, during a basic or reduced radio block period in which it has been granted permission to transmit, monitor the assigned USF on the downlink PDCHs/PDCH-pairs corresponding to its assigned uplink PDCHs/PDCH-pairs starting with the lowest numbered PDCH or PDCH-pair with the lowest numbered timeslots up to the highest numbered PDCH or PDCH-pair with the highest numbered timeslots which the mobile is able to monitor, taking into account the PDCHs/PDCH-pairs allocated for transmission in the basic or reduced radio block period and the switching requirements of the mobile station multislot class (see 3GPP TS 45.002). A mobile station in DTR mode shall only monitor the assigned USF on the downlink PDCH/PDCH-pair indicated in DTR information (see sub-clause 8.1.8).
If the network wishes to reduce the number of PDCHs/PDCH-pairs allocated to a mobile station per basic/reduced radio block period, the network may do so, provided that this is compatible with the mobile station’s ability to monitor the assigned USF in the downlink PDCH/PDCH-pairs corresponding to the lowest numbered uplink PDCH or PDCH-pair with the lowest numbered timeslots in the new allocation. Otherwise, the network shall not allocate any resources to that mobile station for one basic/reduced radio block period following the basic/reduced radio block period with the higher number of PDCHs/PDCH-pairs allocated.
During the downlink block period where an uplink basic/reduced TTI radio block is allocated on a PDCH/PDCH-pair via the polling mechanism (see sub-clause 10.4.4), the mobile station shall monitor the assigned USF on the downlink PDCHs/PDCH-pairs corresponding to its assigned uplink PDCHs/PDCH-pairs starting with the lowest numbered PDCH or PDCH-pair with the lowest numbered timeslots up to the highest numbered PDCH or PDCH-pair with the highest numbered timeslots which is feasible when taking into account the PDCHs/PDCH-pairs allocated for transmission in the basic/reduced radio block period and the switching requirements of the mobile station multislot class (see 3GPP TS 45.002).
8.1.1.2.2 PACCH operation
The mobile station shall attempt to decode every downlink RLC/MAC block on the downlink PDCH corresponding to (i.e. with the same timeslot number as) the lowest numbered timeslot in the PDCH assignment when the uplink TBF operates in the BTTI configuration. A mobile station operating in DTR mode (see sub-clause 8.1.8) shall attempt to decode every RLC/MAC block on a downlink PDCH which the mobile station is required to monitor for the assigned USF as indicated in the DTR information as specified in sub-clause 8.1.1.2.1.
In case the uplink TBF operates in RTTI configuration the mobile station shall attempt to decode every downlink RLC/MAC block on the corresponding downlink PDCH-pair associated with the lowest numbered assigned uplink PDCH-pair (i.e. with lowest time slot numbers) in the set of assigned uplink PDCH-pairs (i.e. downlink PACCH blocks are received in the same mode as the assigned uplink TBF). A mobile station operating in DTR mode (see sub-clause 8.1.8) shall attempt to decode every RLC/MAC block on a downlink PDCH-pair which the mobile station is required to monitor for the assigned USF as indicated in the DTR information as specified in sub-clause 8.1.1.2.1.
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.
In case the uplink TBF operates in BTTI configuration then the network shall transmit all PACCH messages on the PDCH carried on the downlink timeslot corresponding to the lowest numbered timeslot in the assignment. Additionally for the concurrent TBF case, the network may transmit PACCH messages on any of the common timeslots assigned to the downlink and uplink PDCH assignment.
In case the uplink TBF operates in RTTI configuration then the network shall transmit all PACCH messages on the corresponding downlink PDCH-pair associated with the lowest numbered assigned uplink PDCH-pair. Additionally, for the concurrent TBF case, the network may transmit PACCH messages on any of the PDCH-pairs assigned that are common to the downlink and uplink PDCH-pair assignments.
In case the uplink TBF operates in MTTI configuration, then the network shall transmit all PACCH messages on the PDCH or PDCH-pair that uses the lowest numbered timeslot in the MTTI configuration. Additionally, for the case of concurrent uplink and downlink TBFs, the network may transmit PACCH messages on any PDCH or PDCH-pair which is common to the uplink and downlink resource assignments.
Whenever a mobile station, that has an assigned uplink TBF that operates in BTTI configuration, detects an assigned USF value on any monitored PDCH, the mobile station may transmit a PACCH block on the same PDCH in the next block period. Whenever a mobile station, that has an assigned uplink TBF that operates in RTTI configuration, detects an assigned USF value on any corresponding downlink PDCH-pair associated with an assigned uplink PDCH-pair, the mobile station may transmit a PACCH block on the PDCH-pair. The PACCH block shall be transmitted according to the USF scheduling in 8.1.1.2.1. The mobile station shall not transmit an RLC data block in any uplink radio block allocated via the polling mechanism (see sub-clauses 10.4.4, 10.4.4a, 10.4.4b) unless the uplink TBF operates in either RTTI configuration, or in BTTI configuration with FANR activated, and the mobile station is polled for a Piggy-backed Ack/Nack (see sub-clause 10.4.4b).
In the case of a Downlink Dual Carrier configuration or a DLMC configuration, all segments belonging to each RLC/MAC control message shall be sent on PACCH blocks belonging to the same carrier.
When a mobile station in a DLMC configuration supporting more than 20 downlink timeslots sends an EGPRS Packet Downlink Ack/Nack DLMC message (see sub-clause 11.2.48) it shall be coded using CS-1 or CS-3 as indicated by the most recently received assignment message. Otherwise, if it supports 20 or less downlink timeslots, EGPRS Packet Downlink Ack/Nack DLMC messages shall be coded using CS-1.
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.2.4 Shifted USF operation
In some instances (see 3GPP TS 45.002), Shifted USF operation shall apply.
When Shifted USF operation is used, the USF for the first assigned uplink PDCH shall be sent on the downlink PDCH corresponding to (i.e. with the same timeslot number as) the second assigned uplink PDCH. The MS shall monitor this downlink PDCH for the USF corresponding to both the first assigned uplink PDCH and the second assigned uplink PDCH. If the USF corresponding to the first assigned uplink PDCH is detected then operation shall be as described in sub-clause 8.1.1.2.1. for the case where the assigned USF was received on the downlink PDCH corresponding to the first assigned uplink PDCH. Otherwise, operation shall be as described in sub-clause 8.1.1.2.1.
The USF value corresponding to the first assigned uplink PDCH shall be different from the USF value corresponding to the second assigned uplink PDCH.
When Shifted USF operation is used, PACCH operation shall be as described in sub-clause 8.1.1.2.2 except that the network shall transmit all PACCH messages on the PDCH carried on the downlink timeslot corresponding to the second lowest numbered timeslot in the uplink assignment, and the mobile station shall attempt to decode every downlink RLC/MAC block on that downlink PDCH.
If a PACKET PDCH RELEASE message releases the second uplink PDCH in the current timeslot configuration of a mobile station using Shifted USF operation then the first uplink timeslot shall also be considered released. If any PDCHs remain in the new timeslot configuration then normal USF operation shall continue starting on the lowest available timeslot.
8.1.1.3 (void)
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) and MAC-DTM state (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 (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE) 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 45.010. 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 or one or more downlink TBFs are 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 been 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).
A mobile station supporting multiple TBF procedures and operating in DTM mode with exclusive allocation may only establish a single uplink TBF. However, one or more downlink TBFs may still be established when exclusive allocation is used for the uplink TBF. In this case the network may allocate the radio resources for the uplink TBF by sending the mobile station one of the following messages:
– A PACKET UPLINK ASSIGNMENT message if there is no more than one concurrent downlink TBF;
– A MULTIPLE TBF UPLINK ASSIGNMENT message if there are multiple concurrent downlink TBFs;
– A PACKET TIMESLOT RECONFIGURE message if there is one concurrent downlink TBF that is also being reallocated;
– A MULTIPLE TIMESLOT RECONFIGURE message if there are multiple concurrent downlink TBFs and at least one of them is being reallocated or there are multiple concurrent downlink TBFs and resources for at least one new downlink TBF are being allocated.
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 TBF 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 for that TBF. If N3101 reaches the value N3101max, the network shall stop sending PACKET UPLINK ACK/NACK messages to the mobile station for that TBF and shall start timer T3169 for the TBF. If an RLC/MAC block is received from the TBF when timer T3169 is running, the network shall stop timer T3169 and resume sending PACKET UPLINK ACK/NACK messages to the TBF. When T3169 expires, the network may consider the TBF as released and reuse the TFI value(s). If PS Handover is ongoing, it is optional for the network to increment N3101.
8.1.1.3a.3 (void)
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 an uplink TBF operating in BTTI configuration and shall attempt to decode every downlink RLC/MAC block on the PDCH-pair with the lowest timeslot numbers assigned for an uplink TBF operating in RTTI configuration. 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 upper layer 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 upper layer PDU containing signalling information, it shall be transferred with the highest radio priority and requesting acknowledged RLC mode.
If upper layers request the transfer of another upper layer 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, then the procedures as described in packet transfer mode (see sub-clause 8.1.1.1.2) shall be applied by the mobile station.
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 or the TBF is operated in the extended uplink TBF mode (see sub-clause 9.3.1b) and the new upper layer 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.
When the PACKET RESOURCE REQUEST message is sent, the mobile station shall start timer T3168.
If the new upper layer PDU shall be transmitted with a different RLC mode than the current uplink TBF, the mobile station may complete the transmission of the preceding upper layer PDUs and shall then release the TBF and establish a new uplink TBF for transmission of the new upper layer PDU. If the TBF is operated in extended TBF mode (see sub-clause 9.3.1b), the mobile station shall use the procedure in sub-clause 8.1.1.6 for changing the RLC mode.
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.5.3) or the rejection of service demand (sub-clause 8.1.1.3a.5.4).
The mobile station shall stop timer T3168 at the receipt of a PACKET UPLINK ASSIGNMENT, a MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF 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 the mobile station a PACKET UPLINK ASSIGNMENT or a PACKET CS RELEASE INDICATION message if there is no more than one concurrent downlink TBF or a MULTIPLE TBF UPLINK ASSIGNMENT or a PACKET CS RELEASE INDICATION message if there are multiple concurrent downlink TBFs. 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 or a PACKET CS RELEASE INDICATION message for the reallocation. If there are multiple concurrent downlink TBFs and the radio resources for at least one downlink TBF are also affected, the network shall use a MULTIPLE TBF TIMESLOT RECONFIGURE or a PACKET CS RELEASE INDICATION message for the reallocation.
On receipt of the PACKET UPLINK ASSIGNMENT , the MULTIPLE TBF UPLINK ASSIGNMENT, the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or the PACKET CS RELEASE INDICATION message, the mobile station shall treat the message as an uplink assignment, as defined in sub-clause 8.1.1.1.2. On receipt of the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or the PACKET CS RELEASE INDICATION 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 and paging request including MBMS notification.
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 perform an abnormal release with access retry (see sub-clause 8.7.2);
– If the mobile station receives an uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a failure in the uplink assignment (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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 the establishment of one or more downlink TBFs by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) to the mobile station on the PACCH. If multiple TBF procedures are not supported the PACKET TIMESLOT RECONFIGURE message shall be used if the timeslot allocation for the on-going uplink TBF needs to be changed. If the mobile station and network support multiple TBF procedures the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE and MULTIPLE TBF TIMESLOT RECONFIGURE messages shall be used as described in sub-clause 8.1.1.1.3.
On receipt of the downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) the mobile station shall switch to the assigned PDCHs. If the assignment 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 45.010.
When the mobile station switches to the assigned PDCHs, it starts timer T3190 for each downlink TBF assigned. The operation of the downlink TBFs 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 a 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;
– If one uplink and one downlink TBF are established, the network may send a PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), 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, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, 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, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message 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, MULTIPLE TBF DOWNLINK ASSIGNMENT message is due to any other reason, the mobile station shall abort the procedure and continue the normal operation of the ongoing uplink and downlink TBFs.
8.1.1.3b Fixed Uplink Allocation RLC data block transfer
This sub-clause specifies the behaviour for fixed uplink allocation RLC data block transfer while in packet transfer mode with an uplink EC TBF. The downlink allocation follows the procedures as described in sub-clause 8.1.2.
When the mobile station receives a Fixed Uplink Allocation, FUA, in e.g. the EC PACKET UPLINK ASSIGNMENT or EC PACKET UPLINK ACK/NACK message it shall perform uplink transmissions according to that allocation. The uplink resources are allocated with respect to a BTTI configuration, the mobile station uplink coverage class, the assigned MCS, the number of RLC data blocks required for the EC TBF as indicated by the mobile station and with respect to the latest ack/nack status as perceived by the network, if such exists, and transmitted to the mobile station in the message containing the FUA. The uplink resources will be allocated according to the coverage class dependent resource mapping (see 3GPP TS 45.002) and the mobile station shall transmit accordingly.
The uplink EC TBF assignment also includes resources for reception of control messages on EC-PACCH/D as a function of the uplink allocated resources.
Since fixed uplink allocation is used on the uplink, the network will always know the BSN transmitted by the mobile station within each RLC data block, and hence need not rely on RLC/MAC header decoding to acquire the BSN for the purpose of chase combining or incremental redundancy. One exception may apply in case the data to be transmitted by the mobile station can, due to the use of an MCS different from MCS-1, be contained in fewer RLC data blocks than allocated by the network. In that case the excessively allocated RLC data block will contain a pre-emptive uplink transmission, see 9.3.2.3
The BSN_OFFSET field in the fixed uplink allocation defines the offset, in the list of available RLC data blocks for transmission, which shall be applied by the mobile station when selecting the RLC data blocks to transmit in the fixed uplink allocation. If the BSN_OFFSET field is not present, the mobile station shall select the RLC data blocks to transmit in the resources within the fixed uplink allocation as described in sub-clause 9.1.3.4. If the BSN_OFFSET field is present, the mobile station shall apply an offset in RLC data blocks and skip one, or several, of the RLC data blocks that would be transmitted first according to the procedures in sub-clause 9.1.3.4. In case pre-emptive transmission is required for the fixed uplink allocation, see sub-clause 9.3.2.3, the skipped RLC data blocks shall still be included when selecting RLC data blocks for pre-emptive retransmission.
During the time between reception of the message containing the fixed uplink allocation until the time of transmission of the last radio block of the fixed uplink allocation, the mobile station shall not monitor the EC-PACCH on the downlink.
When the last radio block is transmitted according to the fixed uplink allocation, the mobile station shall start timer T3226. When T3226 expires the mobile station shall start T3228 and monitor the EC-PACCH, see sub-clause 8.1.1.3b.1. If the mobile station receives an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressed to it, it shall act on the message and stop timer T3228.
The network shall start timer T3227 after the last allocated RLC data block of the fixed uplink allocation. When timer T3227 expires, the network shall (re)start timer T3229. The network shall then send the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station.
The mobile station is only allowed to transmit RLC data blocks in the fixed uplink allocation resources, i.e. no RLC/MAC control messages shall be sent.
8.1.1.3b.1 EC-PACCH operation
When timer T3226 expires, the mobile station shall monitor the EC-PACCH according to its assigned downlink coverage class and, as long as T3228 is running, attempt to decode every downlink RLC/MAC block on the PDCHs corresponding to the downlink assigned EC-PACCH resources.
Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message addresses the mobile station, the mobile station shall act on the message.
If timer T3228 expires, the mobile station shall release the ongoing uplink TBF and may perform an abnormal release with access retry, unless timer T3248 (sent in EC-SI) is used. If T3248 is used, i.e. it has a value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH using the next higher DL Coverage Class, if such exists. If no higher DL CC than the assigned DL CC exists, the mobile station shall continue to monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message according to the last assigned DL CC until T3248 expires.
The assigned resources (timeslots) to be used for the downlink EC-PACCH according to the next higher DL Coverage Class are either the same as the assigned timeslots for the uplink EC-PDTCH or given in the assignment message. If no valid resources for the next higher Coverage Class are assigned, the mobile station shall continue to monitor the downlink EC-PACCH using the assigned DL Coverage Class while timer T3248 is running.
When the mobile station receives an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with its uplink TBF it shall stop T3228, if running. If timer T3248 was running at reception of the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message (and thus not T3228), the timer T3248 shall be stopped.
At expiry of T3248, the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed.
The mobile station is only reachable on the EC-PACCH once timer T3227 has expired. When timer T3227 expires, the network shall start timer T3229 and send the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station. The network may send additional EC PACKET UPLINK ACK/NACK messages or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages to the mobile station while timer T3229 is running. The network should then however take into account that the mobile station will stop monitoring the EC-PACCH at reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, addressed to it, with a fixed uplink allocation. If the network receives uplink data from the mobile station, on the resources that are part of the fixed uplink allocation, the network shall stop timer T3229, if running.
If timer T3249 (sent in EC-SI) is not used, the network may release the TBF and reuse the TFI resource when timer T3229 has expired and no uplink data has been received according to the fixed uplink allocation sent to the mobile station in an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message before expiry of timer T3229. If timer T3249 is used, i.e. it has a value > 0, it shall be started at expiry of T3229. The network may send the EC PACKET UPLINK ACK/NACK messages or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message to the mobile station using the next higher DL Coverage Class compared to the assigned DL Coverage Class, if such exists, while T3249 is running. When timer T3249 has expired and no uplink data has been received on the resources assigned in the fixed uplink allocation sent to the mobile station in an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message before expiry of timer T3249 (or preceding T3229), the network may release the TBF and reuse the TFI resource.
8.1.1.3b.2 Prolonged Resources for Uplink transmission
During an EC TBF, upper layers of the mobile station may request to transfer upper layer PDUs not accounted for in the initial resource request. The mobile station may then prolong the uplink TBF by including a Countdown Value, CV, that indicates a later end of the TBF than previously indicated, unless CV=0 has already been indicated in an RLC uplink data block, see sub-clause 9.3.1 for the countdown procedure.
8.1.1.3b.3 Abnormal cases
The following abnormal cases apply:
– If the information in the EC PACKET UPLINK ACK/NACK message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a failure in the uplink assignment message (e.g. EC PACKET UPLINK ACK/NACK 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.3b.4 Establishment of Downlink TBF
The network may establish a downlink EC TBF at release of the uplink EC TBF, as described in sub-clause 9.3.2.4.3.
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 upper layer 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 upper layer 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 multiple TBF procedures are not supported and the mobile station has more upper layer PDU(s) to send, the mobile station may initiate the establishment of a new uplink TBF as defined in sub-clause 7.1, 8.1.1. If the mobile station and network support multiple TBF procedures the mobile station may initiate the establishment of one or more new uplink TBFs as defined in sub-clause 8.1.1 and 8.1.1.1.2. If the uplink TBF is using EMST, the mobile station shall release the uplink TBF by releasing each RLC entity allocated to this TBF as specified in sub-clause 9.3.2.3 or 9.3.3.3.
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, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS RELEASE INDICATION 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, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS RELEASE INDICATION 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, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, 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 ACK/NACK, an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message with missing mandatory fields, the MS shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– if the mobile station is operating in the non-extended uplink TBF mode (see sub-clause 9.3.1b) and the mobile station has not started, or has started but not completed the countdown procedure for a given TBF and it receives a PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator set for that TBF, it shall perform an abnormal release with access retry (see sub-clause 8.7.2).
NOTE: A PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or PACKET CS RELEASE INDICATION 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.1.6 Change of RLC mode in extended uplink TBF mode
8.1.1.6.1 General
This procedure applies to a mobile station having an uplink TBF in extended uplink TBF mode. The procedure shall be used to release the ongoing uplink TBF and to setup a new TBF in another RLC mode.
8.1.1.6.2 Change of RLC mode
The mobile station shall send a PACKET RESOURCE REQUEST message on PACCH indicating the new RLC mode and start timer T3168.
If timer T3168 expires, the mobile station shall retransmit the PACKET RESOURCE REQUEST message and restart timer T3168.
On receipt of a PACKET RESOURCE REQUEST message, indicating a change of RLC mode, the network shall release the uplink TBF at a point determined by the network, using the procedure defined in sub-clause 9.5.
On receipt of PACKET UPLINK ACK/NACK with Final Ack Indicator set to ‘1’ the mobile station shall stop timer T3168 and after sending the PACKET CONTROL ACKNOWLEDGEMENT message perform the change of RLC mode by establishing a new TBF.
8.1.1.6.3 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 perform an abnormal release with access retry (see sub-clause 8.7.2).
8.1.1.7 Change of EGPRS level
8.1.1.7.1 Change of EGPRS level for downlink TBFs
The network may indicate to the mobile station that the EGPRS level applicable to a downlink TBF shall be changed. The mobile station shall not consider any transition (to or from any EGPRS level) to be an error, provided that the mobile station supports the new EGPRS level in the downlink. In EC operation the only level supported is EGPRS.
8.1.1.7.2 Change of EGPRS level for uplink TBFs
The network may indicate to the mobile station that the EGPRS level applicable to an uplink TBF shall be changed. The transitions which can be performed are shown in table 8.1.1.7.2.1.
Table 8.1.1.7.2.1: Permitted EGPRS level changes
|
Current EGPRS level |
New EGPRS Level |
|
EGPRS |
EGPRS2-A |
|
EGPRS |
EGPRS2-B |
|
EGPRS2-B |
EGPRS |
|
EGPRS2-A |
EGPRS |
In EC operation the only level supported is EGPRS.
Transitions not listed in Table 8.1.1.7.2.1 are not permitted.
The modulation and coding scheme to be used for retransmissions in case of a transition from EGPRS to EGPRS2-A (respectively EGPRS2-B) is shown in Table 8.1.1.7.2.2 (respectively Table 8.1.1.7.2.3) below.
Table 8.1.1.7.2.2: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-A)
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS2-A (MCS or UAS) |
||||
|
UAS-11 Commanded |
UAS-10 Commanded |
UAS-9 Commanded |
UAS-8 Commanded |
UAS-7 Commanded |
|
|
MCS-9 |
UAS-9 |
UAS-9 |
UAS-9 |
MCS-6 |
MCS-6 |
|
MCS-8 |
MCS-6 (NOTE 2) |
||||
|
MCS-7 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
|
MCS-6 |
UAS-9 |
UAS-9 |
UAS-9 |
MCS-6 |
MCS-6 |
|
MCS-5 |
UAS-10 |
UAS-10 |
UAS-7 |
UAS-7 |
UAS-7 |
|
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-2 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
|
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
|
NOTE 1: If MCS-1 to MCS-6 is commanded, see Table 8.1.1.1 or Table 8.1.1.2 as appropriate. NOTE 2: In this case, 6 octets of padding are used. |
|||||
Table 8.1.1.7.2.3: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-B) with re-segmentation
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS2-B (MCS or UBS) |
|||||||
|
UBS-12 Commanded |
UBS-11 Commanded |
UBS-10 Commanded |
UBS-9 Commanded |
UBS-8 Commanded |
UBS-7 Commanded |
UBS-6 Commanded |
UBS-5 Commanded |
|
|
MCS-9 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-8 |
UBS-11 |
UBS-11 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-7 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
|
MCS-6 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-5 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
|
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-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 |
|
NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.1. |
||||||||
Table 8.1.1.7.2.4a: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-B) without re-segmentation
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS2-B (MCS or UBS) |
|||||||
|
UBS-12 Commanded |
UBS-11 Commanded |
UBS-10 Commanded |
UBS-9 Commanded |
UBS-8 Commanded |
UBS-7 Commanded |
UBS-6 Commanded |
UBS-5 Commanded |
|
|
MCS-9 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-8 |
UBS-11 |
UBS-11 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-7 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
|
MCS-6 |
UBS-12 |
UBS-10 |
UBS-10 |
UBS-8 |
UBS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-5 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-9 |
UBS-7 |
UBS-7 |
UBS-5 |
UBS-5 |
|
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-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 |
Table 8.1.1.7.2.4b: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS, level changed to EGPRS2-B) without re-segmentation
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS2-B (MCS or UBS) |
|||
|
MCS-4 Commanded |
MCS-3 Commanded |
MCS-2 Commanded |
MCS-1 Commanded |
|
|
MCS-9 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-8 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-7 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
|
MCS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
UBS-6 |
|
MCS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
UBS-5 |
|
MCS-4 |
MCS-4 |
MCS-4 |
MCS-4 |
MCS-4 |
|
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
|
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
The modulation and coding scheme to be used for retransmissions in case of a transition from EGPRS2-A (respectively EGPRS2-B) to EGPRS is shown in Tables 8.1.1.7.2.5 and 8.1.1.7.2.6 (respectively Tables 8.1.1.7.2.7 and 8.1.1.7.2.8) below.
Table 8.1.1.7.2.5: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-A, level changed to EGPRS) with re-segmentation
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS (MCS) |
||||||
|
MCS-9 Commanded |
MCS-8 Commanded |
MCS-7 Commanded |
MCS-6-9 Commanded |
MCS-6 Commanded |
MCS-5-7 Commanded |
MCS-5 Commanded |
|
|
UAS-11 |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-3 (NOTE 2) |
MCS-3 (NOTE 2) |
|
UAS-10 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
UAS-9 |
MCS-9 |
MCS-6 |
MCS-6 |
MCS-9 |
MCS-6 |
MCS-3 |
MCS-3 |
|
UAS-8 |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-3 (NOTE 2) |
MCS-3 (NOTE 2) |
|
UAS-7 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
MCS-6 |
MCS-9 |
MCS-6 |
MCS-6 |
MCS-9 |
MCS-6 |
MCS-3 |
MCS-3 |
|
MCS-5 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
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-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 |
|
NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.3. NOTE 2: In this case, 10 octets of padding are used. |
|||||||
Table 8.1.1.7.2.6: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-A, level changed to EGPRS) without re-segmentation
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS (MCS) |
||||||
|
MCS-9 Commanded |
MCS-8 Commanded |
MCS-7 Commanded |
MCS-6-9 Commanded |
MCS-6 Commanded |
MCS-5-7 Commanded |
MCS-5 Commanded |
|
|
UAS-11 |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
|
UAS-10 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
UAS-9 |
MCS-9 |
MCS-6 |
MCS-6 |
MCS-9 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UAS-8 |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
MCS-6 (NOTE 2) |
|
UAS-7 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
MCS-6 |
MCS-9 |
MCS-6 |
MCS-6 |
MCS-9 |
MCS-6 |
MCS-6 |
MCS-6 |
|
MCS-5 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
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-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 |
|
NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.4. NOTE 2: In this case, 10 octets of padding are used. |
|||||||
Table 8.1.1.7.2.7: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-B, level changed to EGPRS) with re-segmentation
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS (MCS) |
||||||
|
MCS-9 Commanded |
MCS-8 Commanded |
MCS-7 Commanded |
MCS-6-9 Commanded |
MCS-6 Commanded |
MCS-5-7 Commanded |
MCS-5 Commanded |
|
|
UBS-12 |
MCS-9 |
MCS-6 |
MCS-6 |
MCS-9 |
MCS-6 |
MCS-3 |
MCS-3 |
|
UBS-11 |
MCS-8 |
MCS-8 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-3 |
MCS-3 |
|
UBS-10 |
MCS-8 / MCS-9 (NOTE 2) |
MCS-8 / MCS-6 (NOTE 2) |
MCS-6 |
MCS-9 |
MCS-6 |
MCS-3 |
MCS-3 |
|
UBS-9 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
UBS-8 |
MCS-8 / MCS-9 (NOTE 2) |
MCS-8 / MCS-6 (NOTE 2) |
MCS-6 |
MCS-9 |
MCS-6 |
MCS-3 |
MCS-3 |
|
UBS-7 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
UBS-6 |
MCS-8 / MCS-9 (NOTE 2) |
MCS-8 / MCS-6 (NOTE 2) |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-3 |
MCS-3 |
|
UBS-5 |
MCS-7 |
MCS-7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-7 |
MCS-5 |
|
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-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 |
|
NOTE 1: If MCS-1 to MCS-4 is commanded, see Table 8.1.1.5. NOTE 2: If the last transmission was with padding, then MCS-8 is used; otherwise, the alternative coding scheme specified above is used. |
|||||||
Table 8.1.1.7.2.8: Choice of modulation and coding scheme for retransmissions (initial transmission EGPRS2-B, level changed to EGPRS) without re-segmentation
|
Scheme used for Initial transmission |
Scheme to use for retransmissions after switching to EGPRS (MCS) |
||||||
|
MCS-9 or MCS-8 or MCS-7 or MCS-6-9 or MCS-6 Commanded |
MCS-5-7 Commanded |
MCS-5 Commanded |
MCS-4 Commanded |
MCS-3 Commanded |
MCS-2 Commanded |
MCS-1 Commanded |
|
|
UBS-12 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UBS-11 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UBS-10 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UBS-9 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
|
UBS-8 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UBS-7 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
|
UBS-6 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
MCS-6 |
|
UBS-5 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-7 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
MCS-5 |
|
MCS-4 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-4 |
MCS-4 |
MCS-4 |
MCS-4 |
MCS-4 |
MCS-4 |
|
MCS-3 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
MCS-3 |
|
MCS-2 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
MCS-2 |
|
MCS-1 |
MCSs defined in Table 8.1.1.7.2.7 |
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
MCS-1 |
8.1.2 Downlink RLC data block transfer
For a TBF in BTTI configuration, prior to the initiation of RLC data block transfer on the downlink, the network assigns the following parameters in a downlink assignment (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, EC PACKET DOWNLINK ASSIGNMENT, or PACKET CS RELEASE INDICATION) message:
– a Temporary Flow Identity (TFI). The TFI applies to all radio blocks transferred in regards to:
– the downlink Temporary Block Flow (TBF) ,
– or in case EMST is used, to the RLC entity allocated on the downlink TBF,
– or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on the downlink TBF;
– or for a DLMC configuration, to a downlink carrier assigned to the downlink TBF where different TFIs may be assigned for each carrier of the TBF;
– an eTFI, optionally assigned in case of a downlink TBF assigned to a MS supporting eTFI (see sub-clause 5.13);
– a set of PDCHs to be used for the downlink transfer;
– optionally, a TBF starting time indication (not applicable for dual carrier, multi carrier, BTTI with FANR activated, and EGPRS2 configurations);
– a PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures. In case EMST is supported by the network and the mobile station, the PFI associated with each allocated RLC entity. In case EMSR is enabled for one or more RLC entities of the allocated TBF, the assignment message indicates the PFI associated with each PFC supported by these RLC entities.
– in case of a downlink EC TBF, the network also assigns the following parameters:
– uplink and downlink coverage classes;
– a set of PDCHs to be used for transmission of uplink RLC/MAC control messages.
In case RTTI configuration is supported by the network and the mobile station and a downlink TBF operating in RTTI configuration is assigned, the following parameters shall be provided by the network in the assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION).
– a Temporary Flow Identity (TFI). The TFI applies to all radio blocks transferred in regards to:
– the downlink Temporary Block Flow (TBF) ,
– or in case EMST is used, to the RLC entity allocated on the downlink TBF,
– or in case EMSR is enabled for an RLC entity, to each PFC supported by that RLC entity on the downlink TBF;
– or for a DLMC configuration, to a downlink carrier assigned to the downlink TBF where different TFIs may be assigned for each carrier of the TBF;
– an eTFI, optionally assigned in case of a downlink TBF assigned to a MS supporting eTFI (see sub-clause 5.13);
– one or more downlink PDCH-pairs to be used for the downlink transfer;
– a PFI associated with each allocated TBF if the network and the mobile station both support multiple TBF procedures. In case EMST is supported by the network and the mobile station, the PFI associated with each allocated RLC entity. In case EMSR is enabled for one or more RLC entities of the allocated TBF, the assignment message indicates the PFI associated with each PFC supported by these RLC entities.
The network may, at any time during downlink packet transfer, change the TTI configuration of an already established downlink TBF by sending on the downlink PACCH a downlink TBF assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). In case of a TTI configuration change the mobile station shall begin using the new TTI configuration within the reaction time defined in 3GPP TS 45.010.
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.
For the case where EMST is used for a downlink TBF where eTFI values have been assigned, when a corresponding PAN is sent on the uplink applicable TFI and eTFI values are those associated with the RLC entity for which the PAN is sent.
A mobile station shall only attempt to decode downlink radio blocks transmitted using a TSC it has been assigned. A mobile station that supports the extended TSC sets (see 3GPP TS 45.002 [32]) can have up to two TSCs assigned for a given PDCH and shall attempt to decode a downlink radio block it receives on that PDCH using its assigned TSC(s).
8.1.2.1 Downlink RLC data block transfer
A network may send an unsolicited downlink assignment message to a mobile station. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.1.1.3.
Upon reception of a downlink assignment 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 PDCHs. If the downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) contains a TBF starting time information element and there is no downlink TBF in progress, but one or more uplink TBFs are 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 for each downlink TBF assigned in the downlink assignment message and immediately begin decoding the assigned downlink PDCH(s). If the downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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. The mobile station shall continue to use the newly assigned parameters of each downlink TBF until the TBF is either released or reconfigured. If while waiting for the frame number indicated by the TBF starting time the mobile station receives another downlink assignment for the 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 or MULTIPLE TBF DOWNLINK ASSIGNMENT message) while no TBF is in progress are specified in sub-clause 7.2.1.1.
Subsequent assignment messages may be sent to a mobile station operating in a Downlink Dual Carrier configuration or DLMC configuration as described in sub-clause 8.1.1.1.3.
A mobile station in DTR mode with a downlink TBF assigned shall monitor only one of the assigned PDCHs/PDCH-pairs, as specified in sub-clause 8.1.8.
If the mobile station receives a valid RLC data block addressed to one of its TBFs, the mobile station shall restart timer T3190 for that TBF. In EGPRS/EC TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station.
If any given timer T3190 expires, the mobile station shall release that downlink TBF. If there are one or more uplink TBFs in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If any given timer T3190 expires and there are no other ongoing uplink TBFs 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 or EC PACKET TBF RELEASE message referring to a 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 one or more new TBFs have 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 downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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, a MULTIPLE TBF DOWNLINK ASSIGNMENT, a PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1);
– If the information in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If 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 failure in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message 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, MULTIPLE TBF DOWNLINK ASSIGNMENT or EC PACKET DOWNLINK ASSIGNMENT message does not satisfactorily define a PDCH, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT/MULTIPLE TBF DOWNLINK ASSIGNMENT/ EC PACKET DOWNLINK ASSIGNMENT message;
– If the mobile station does not support Downlink Dual Carrier but receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message specifying different frequency parameters than those currently in effect for the uplink TBF (see sub-clause 5.5.1.7), the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT/ MULTIPLE TBF DOWNLINK ASSIGNMENT message and continue normal operation of the uplink TBF;
– If the mobile station supports Downlink Dual Carrier, has one or more ongoing uplink TBFs and is not in a Downlink Dual Carrier configuration, but receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message specifying frequency parameters for carrier 1 that are different from those currently in effect for the uplink TBF, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT/ MULTIPLE TBF DOWNLINK ASSIGNMENT message and continue normal operation of the uplink TBF;
– If both the mobile station and the network support multiple TBF procedures and if any given downlink assignment message provides an uplink TBF allocation for a PFI not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST or EMSR and if any given downlink assignment message provides an uplink resource allocation for a PFI not associated with any RLC entity allocated on the ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that does not support Downlink Dual Carrier receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) that assigns resources on two carriers or includes the Assignment Info IE which indicates that the assignment is a ‘Modification of an existing assignment’ or a ‘Dual Carrier assignment’, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1);
– If a mobile which supports Downlink Dual Carrier receives a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) that assigns resources on two carriers and those two carriers are not within the same frequency band, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration wherein resources are assigned on carriers in different frequency bands but does not support inter-band reception, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that establishes or modifies a DLMC configuration with more carriers or more downlink timeslots than it supports, or assigns eTFIs or a SNS of 8192 or CS-3 for PDAN coding when the mobile station supports 20 or fewer time slots, or assigns carriers in a frequency band it does not support, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message that modifies a DLMC configuration that releases carriers on which USF is being monitored, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET DOWNLINK ASSIGNMENT message or PACKET TIMESLOT RECONFIGURE message that assigns two or more UFPS to the same Mobile Allocation (as defined by the DLMC Frequency Parameter IE), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that supports Downlink Multi Carrier receives a PACKET UPLINK ASSIGNMENT message that modifies a DLMC configuration by assigning an uplink carrier that does not correspond to an existing downlink carrier, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a failure in the PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT or EC PACKET DOWNLINK ASSIGNMENT message is due to any other reason, the mobile station shall abort the establishment of the downlink TBFs indicated in the downlink assignment message. If one or more ongoing uplink or downlink TBFs exist, the mobile station shall continue the normal operation of all the ongoing uplink TBFs. If no ongoing uplink or downlink TBFs 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 one of its TBFs and with a valid RRBP field or with a valid CES/P field in the RLC data block header (i.e. is polled), the mobile station shall transmit one of the following replies in the uplink radio block specified by the RRBP field or CES/P field, whatever the BSN value of the received RLC data block, according to the subsequent decreasing order of priority:
1) a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing a Final Ack Indicator;
2) a PACKET CS REQUEST message, if such a message is waiting to be transmitted;
3) a PACKET CELL CHANGE NOTIFICATION message, if such a message is waiting to be transmitted;
4) a (EGPRS) PACKET DOWNLINK ACK/NACK message or a EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or a EGPRS PACKET DOWNLINK ACK/NACK DLMC message containing a Channel Request Description IE;
5) any other RLC/MAC control message, if such a message is waiting to be transmitted, other than a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message;
6) when FANR is activated and the mobile station is polled for a PAN (see sub-clause 10.4.4b) , a PAN field corresponding to this TBF included in an EGPRS RLC/MAC block for data transfer from one of the concurrent TBFs in uplink (see sub-clause 8.1.1.);
7) a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC 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 or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message at most every second time it is polled for the TBF. For a TBF with FANR activated, the mobile station may transmit an RLC/MAC control message other than a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message only if a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message or EGPRS RLC/MAC block for data transfer including a PAN field was transmitted as the response to the last poll.
The mobile station shall not send an EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message if not indicated as supported by the network according to the value of the EGPRS Packet Downlink Ack/Nack Type 3 Support field in assignment messages.
The mobile station shall not send a PACKET CONTROL ACKNOWLEDGEMENT message unless otherwise specified.
A mobile station in packet transfer mode in a Downlink Dual Carrier configuration or a DLMC configuration shall respond in the uplink radio block indicated by the RRBP field or by the CES/P field, on the same radio frequency channel as the one where the poll was received. A mobile station in dual transfer mode in a Downlink Dual Carrier configuration shall respond in the uplink radio block on the timeslot or on the PDCH pair indicated by the RRBP field or by the CES/P field, on the uplink radio frequency channel where the dedicated resource is assigned regardless of which downlink radio frequency channel the poll was received on. The network shall not poll the mobile station in a manner which would require the mobile station to respond on the same timeslot as that on which the dedicated resource is assigned.
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.
If EMST is used and the mobile station responds to the poll with a (EGPRS) PACKET DOWNLINK ACK/NACK message, an EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, an EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message or an EGPRS PACKET DOWNLINK ACK/NACK DLMC message or an EGPRS RLC/MAC block for data transfer with a PAN field, then the message or the PAN field shall correspond to the RLC entity identified by the TFI in the header of the downlink RLC/MAC block containing the poll.
Whenever the network receives a valid RLC/MAC control message from a TBF, it shall reset counter N3105 for that TBF. The network shall increment counter N3105 for each radio block, allocated to that TBF with the RRBP field or with the CES/P 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(s).
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).
The EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message and the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message may contain an EGPRS Channel Quality Report Type 2 (see 3GPP TS 45.008). The EGPRS PACKET DOWNLINK ACK/NACK DLMC message may contain the DLMC Channel Quality Report IE (see sub-clause 12.66).
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 or multislot class 30 to 45 need not respond to the poll if it is not compliant with the multislot class of the mobile station (see 3GPP TS 45.002).
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 multislot class of the mobile station (see 3GPP TS 45.002), 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 45.008).
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 (see 3GPP TS 45.002). 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.
The mobile station shall not send a poll response using a TTI configuration that is different from that with which the poll was received.
If a downlink TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed by the BSS (see sub-clause 11.2.7 and 3GPP TS 44.018 [11]) then EGPRS Packet Downlink Ack/Nack Type 2 and EGPRS Packet Downlink Ack/Nack Type 3 messages shall include these parameters when all downlink RLC data blocks have been received by the mobile station. The BSS uses the “MS Transmission Offset” parameter carried therein to adjust the estimated timing advance applicable to the mobile station (3GPP TS 45.010) and thereby establishes a “MultilaterationTiming Advance” value correspsonding to that mobile station. The BSS then relays the “Multilateration Timing Advance”, “Cell Identifier” of the serving cell, the “MS Sync Accuracy” and the “BTS Reception Accuracy Value” to the SMLC using the SCCP connection corresponding to the mobile station (see 3GPP TS 49.031).
8.1.2.2a Polling for EC Packet Downlink Ack/Nack or EC Packet Downlink Ack/Nack Higher CC
Whenever the mobile station receives an RLC data block addressed to its TBF and with a valid RRBP field in the RLC data block header (i.e. it is polled), the mobile station shall transmit a reply in the uplink radio block(s) specified by the RRBP field. The network can poll the mobile station in more than one downlink radio block where each valid RRBP field points to the same uplink resources to be used for transmission of the EC PACKET DOWLINK ACK/NACK message. The mobile station shall thus not automatically stop listening to the downlink when it is polled. It shall instead stop listening according to its specified reaction time, see 3GPP TS 45.010, before transmission of the EC PACKET DOWLINK ACK/NACK message. If the mobile station has not received an RLC data block containing the Final Block Indicator or it has received the Final Block Indicator but still has downlink data blocks that need to be negatively acknowledged, it shall transmit the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message including the ack/nack description accordingly. When the Final Block Indicator is received and all downlink data blocks have been correctly received, the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message shall be transmitted containing the Final Ack Indicator. If uplink data becomes available for transmission at any point in time during an ongoing downlink TBF, the mobile station can request uplink resources by including a channel request in the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message.
After completing the transmission of an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message in TDMA frame N the mobile station shall resume monitoring its assigned downlink PDCH(s). The first downlink TDMA frame monitored shall be according to its assigned downlink coverage class and may start as early downlinkTDMA frame N+1 depending on the assigned uplink and downlink coverage classes. If the first downlink TDMA frame monitored occurs in downlink TDMA frame N+1 and the mobile station is unable to monitor all of its assigned downlink PDCHs therein due to multislot class limitations on switching from transmit to receive (see 3GPP TS 45.002 [13]) it shall still attempt recovery of a RLC data block (or an EC-PACCH block) using the bursts it is able to receive therein and in subsequent downlink TDMA frames.
In EC 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 a TBF, it shall reset counter N3105 for that TBF. 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(s).
If a downlink EC TBF is established using a downlink assignment message indicating “MS Transmission Offset” and “MS Sync Accuracy” parameters are needed by the BSS (see sub-clause 11.2.52 and 3GPP TS 44.018 [11]) then EC PACKET DOWLINK ACK/NACK message shall include these parameters when all downlink RLC data blocks have been received by the mobile station. The BSS uses the “MS Transmission Offset” parameter carried therein to adjust the estimated timing advance applicable to the mobile station (3GPP TS 45.010) and thereby establishes a “MultilaterationTiming Advance” value correspsonding to that mobile station. The BSS then relays the “Multilateration Timing Advance”, the “Cell Identifier” of the serving cell, the “MS Sync Accuracy” and the “BTS Reception Accuracy Value” to the SMLC using the SCCP connection corresponding to the mobile station (see 3GPP TS 49.031).
8.1.2.3 (void)
8.1.2.4 Resource Reassignment for Downlink
The network initiates resource reassignment by sending a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) on the downlink PACCH. These messages indicate a change in resources in the same TBF. The Control Ack bit in the message shall be set to ‘0’. If multiple TBF procedures are supported by the mobile station and the network, the network shall indicate the PFI associated with each TBF it allocates or reallocates in the downlink assignment message. If EMTS is supported by the mobile station and the network, the network shall indicate the PFI associated with each RLC entity in the downlink assignment message (i.e. PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION). During the reassignment of any given TBF its associated TFI is allowed to be changed. Mobile shall use the TFI indicated in the PACKET DOWNLINK ASSIGNMENT/ MULTIPLE TBF 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 sub-clause 9.3.3.5.
On receipt of a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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 for each newly assigned downlink TBF. A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as defined in sub-clause 8.1.1.1.3.
When the mobile station receives an RLC/MAC block addressed to (one of) its downlink TBF(s) on any of the new assigned resources it shall restart timer T3190 for that TBF. If any given timer T3190 expires, and if one or more uplink TBF is in progress, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2). If any given timer T3190 expires and there are no uplink TBFs in progress, 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 9.3.2.6).
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 downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION 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 or MAC-DTM state receives a PACKET DOWNLINK ASSIGNMENT, a MULTIPLE TBF DOWNLINK ASSIGNMENT, a PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1);
– If the information in the PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message does not properly specify an uplink and downlink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), 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, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message 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 or MULTIPLE TBF DOWNLINK ASSIGNMENT message does not satisfactorily define a PDCH, the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT / MULTIPLE TBF DOWNLINK ASSIGNMENT message and maintain its ongoing TBFs;
– If the mobile station receives a PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message specifying different frequency parameters than those currently in effect for its ongoing TBFs (see sub-clause 5.5.1.7), the mobile station shall ignore the PACKET DOWNLINK ASSIGNMENT message and continue normal operation of its ongoing TBFs;
– If a failure in the PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT message is due to any other reason, the mobile station shall abort the establishment of the downlink TBFs indicated in the downlink assignment message. If one or more ongoing uplink or downlink TBFs exist, the mobile station shall continue the normal operation of all ongoing uplink TBFs. If no ongoing uplink or downlink TBFs exist, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1);
– If both the mobile station and the network support multiple TBF procedures and if any given downlink assignment message provides an uplink TBF allocation for a PFI not associated with any ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST or EMSR and if any given downlink assignment message provides an uplink resource allocation for a PFI not associated with any RLC entity allocated on the ongoing uplink TBF, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2).
8.1.2.5 Establishment of uplink TBF
The mobile station may request establishment of one or more uplink TBFs when there are one or more ongoing downlink TBFs by including a Channel Request Description or the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, or by including a Channel Request Description information element in an EGPRS PACKET DOWNLINK ACK/NACK DLMC message. Initiation is triggered by a request from upper layers to transfer an upper layer PDU. The request from upper layers specifies a Radio Priority to be associated with the packet transfer.
When multiple TBF procedures are not supported, the mobile station initiates the packet access procedure by sending the Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or EGPRS PACKET DOWNLINK ACK/NACK DLMC message on the PACCH and starting timer T3168.
When the mobile station has an ongoing downlink EC TBF, it may initiate an uplink EC TBF by including the EC Channel Request Description information element in the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message on the EC-PACCH and start timer T3168. The network may then establish an uplink EC TBF by sending an EC PACKET UPLINK ASSIGNMENT message to the mobile station, in which case the downlink EC TBF is released.
When the mobile station and the network support multiple TBF procedures the mobile station may request one or more uplink TBFs by including the Extended Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message and starting one instance of timer T3168 for each uplink TBF it requests. Each requested uplink TBF is associated with a different PFI. A mobile station shall continue to use its ongoing downlink TBFs unless re-allocated or released as a result of the uplink assignment message(s) sent in response by the network.
If both the network and the mobile station support the extended uplink TBF mode, the request from upper layers may indicate that the new upper-layer PDU is meant to pre-allocate an uplink TBF (early TBF establishment). In this case, the EARLY_TBF_ESTABLISHMENT field in the (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message shall indicate pre-allocation is required.
On receipt of an (Extended) Channel Request Description or EC Channel Request Description information element in the (EGPRS) PACKET DOWNLINK ACK/NACK, EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or a Channel Request Description information element in the EGPRS PACKET DOWNLINK ACK/NACK DLMC message, the network may assign radio resources to the mobile station on one or more PDCHs by transmitting an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) on the (EC-)PACCH, or may reject one or more of the requests by sending a PACKET ACCESS REJECT or an EC PACKET ACCESS REJECT message on the (EC-)PACCH. If the PACKET TIMESLOT RECONFIGURE message is sent, then the message shall contain the UPLINK_TFI_ASSIGNMENT field. If the mobile station supports RLC non-persistent mode the network may allocate one or more EGPRS TBFs that use this RLC mode.
In EC operation, the downlink EC TBF is released at establishment of the uplink EC TBF.
If multiple TBF procedures are supported by the mobile station and the network, the network shall indicate the PFI associated with each TBF it allocates or reallocates in the uplink assignment message.
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.
If the network and mobile station both support Downlink Dual Carrier, the network may send an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) to a mobile station specifying one or more TBFs with packet resources on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. Subsequent assignment messages may be sent to a mobile station in a Downlink Dual Carrier configuration as described in sub-clause 8.1.1.1.3.
If the network and mobile station both support Downlink Multi Carrier, the network may send a PACKET TIMESLOT RECONFIGURE message to a mobile station assigning an uplink TBF and thereby establish a DLMC configuration. Subsequent assignment messages may be sent to a mobile station in a DLMC configuration as described in sub-clause 8.1.1.1.3.
On receipt of an uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message) the mobile station shall proceed as follows:
– On reception of an uplink assignment message the mobile station shall stop the instance of timer T3168 associated with the TBF receiving a resource allocation;
– The mobile station shall, after expiry of the TBF starting time, if present, act upon the uplink assignment received for that TBF;
– The mobile station shall then switch to the assigned uplink PDCHs and begin to send RLC data blocks on the assigned PDCH(s). Neither the TLLI (in A/Gb mode) nor the G-RNTI (in Iu mode) shall be included in any of the uplink RLC data blocks in that case;
– A mobile station in EC operation, i.e. with a downlink TBF, shall release the downlink TBF at the establishment of the uplink TBF and stop timer T3192, if running.
A mobile station that supports multiple TBF procedures shall act on the uplink assignment message as follows:
– Upon reception of a PACKET UPLINK ASSIGNMENT message the mobile station shall release all ongoing uplink TBFs not addressed by this message and shall act on the message. If multiple uplink TBFs were requested then the mobile station shall consider those not addressed by this message as rejected and shall stop the corresponding T3168 timer instances. All ongoing downlink TBFs shall be maintained;
– Upon reception of a PACKET TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message. If multiple uplink TBFs were requested then the mobile station shall consider those not addressed by this message as rejected and shall stop the corresponding T3168 timer instances;
– Upon reception of a MULTIPLE TBF UPLINK ASSIGNMENT message the mobile station shall maintain all ongoing TBFs not addressed by this message using its currently allocated TBF parameters and shall act on the message. If a requested uplink TBF is not addressed by this message and the associated timer T3168 is still running the mobile station shall wait for another instance of this message;
– Upon reception of a MULTIPLE TBF TIMESLOT RECONFIGURE message the mobile station shall release all ongoing uplink and downlink TBFs not addressed by this message and shall act on the message. If multiple uplink TBFs were requested then the mobile station shall consider those not addressed by this message as rejected and shall stop the corresponding T3168 timer instances.
When an uplink TBF is established in response to a (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message with the EARLY_TBF_ESTABLISHMENT field set to indicate pre-allocation is required, a network supporting early TBF establishment should keep the uplink TBF open by means of the extended uplink TBF mode operation (see sub-clause 9.3.1b.2).
On receipt of a PACKET ACCESS REJECT or EC PACKET ACCESS REJECT message that contains a Reject structure addressed to the mobile station, the mobile station shall stop the instance of timer T3168 associated with each uplink TBF being rejected and indicate a packet access failure to the corresponding upper layers.
If the PACKET ACCESS REJECT or EC PACKET ACCESS REJECT message contains a WAIT_INDICATION field in a Reject structure addressed to the mobile station, it shall proceed as follows:
– If multiple TBF procedures are not supported 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 another cell after successful cell reselection;
– If both the mobile station and the network support multiple TBF procedures the mobile station shall start one instance of timer T3172 for each uplink TBF that was rejected. All ongoing TBFs shall be maintained. The mobile station is not allowed to attempt re-establishment of a rejected uplink TBF in the same cell until its associated instance of timer T3172 expires. It may, however, attempt re-establishment of a rejected uplink TBF in another cell after successful cell reselection. The mobile station may attempt to enter the dedicated mode in the same cell before all instances of timer T3172 have expired. During the time one or more instances of T3172 are running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging request to trigger RR connection establishment and paging request including MBMS notification.
If all instances of timer T3168 have expired, the mobile station shall retransmit the (Extended) Channel Request Description information element in the next (EGPRS) PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message or the Channel Request Description information element in the next EGPRS PACKET DOWNLINK ACK/NACK DLMC message unless the (Extended) Channel Request Description has already been transmitted four times in which case the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).
In EC operation, when the instance of timer T3168 expires, a mobile station may again include the EC Channel Request Description IE in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message. The EC Channel Request Description IE may however be included in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to ‘1’ even if timer T3168 is still running. A mobile station that included the EC Channel Request Description IE in an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the Final Ack Indicator bit set to ‘1’, shall release the TBF resources when timer T3168 expires, unless timer T3192 is still running. The packet access procedure may then be reinitiated on the (EC-)CCCH.
If all the ongoing downlink TBFs are released, including expiry of timer T3192, before expiry of all instances of timer T3168 and no uplink TBFs are either ongoing or have received an uplink assignment with a TBF starting time, the mobile station shall stop all remaining instances of 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 a 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, EC PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If the mobile station does not support Downlink Dual Carrier but receives a PACKET UPLINK ASSIGNMENT or a MULTIPLE TBF UPLINK ASSIGNMENT message specifying different frequency parameters than those currently in effect for the downlink TBF(s) (see sub-clause 5.5.1.7), the mobile station shall ignore the PACKET UPLINK ASSIGNMENT/ MULTIPLE TBF UPLINK ASSIGNMENT message, continue normal operation of the ongoing downlink TBF(s), and reinitiate the establishment of the uplink TBF(s) unless the establishment of the uplink TBF(s) has already been attempted four times, in which case, the mobile station shall perform the abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station in dual transfer mode or MAC-DTM state receives a PACKET UPLINK ASSIGNMENT or a MULTIPLE TBF UPLINK ASSIGNMENT message including frequency parameters for the carrier supporting the dedicated resources, 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, EC PACKET UPLINK ASSIGNMENT or in the MULTIPLE TBF UPLINK ASSIGNMENT message 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 information in the PACKET TIMESLOT RECONFIGURE or in the MULTIPLE TBF TIMESLOT RECONFIGURE message does not properly specify a set of uplink and downlink PDCH(s) or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If the PACKET TIMESLOT RECONFIGURE or the MULTIPLE TBF TIMESLOT RECONFIGURE message 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 or a MULTIPLE TBF TIMESLOT RECONFIGURE message including frequency parameters for the carrier supporting the dedicated resources, 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 or in the 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.7.2);
– If both the mobile station and the network support multiple TBF procedures and if any given uplink assignment message provides an uplink TBF allocation for a PFI not indicated in the request for uplink TBF sent by the mobile station , the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST and if any given uplink assignment message provides an uplink resource allocation for a PFI not indicated in the request for uplink resource sent by the mobile station, the mobile station shall abort the procedure and perform an abnormal release with access retry (see sub-clause 8.7.2);
– If both the mobile station and the network support EMST and if any given uplink assignment message includes an assignment for more RLC entities than the mobile station supports or more than one RLC entity is assigned to use same RLC mode to a TBF, the mobile station shall abort the procedure and perform abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile station that does not support Downlink Dual Carrier receives a PACKET UPLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF UPLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on two carriers, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2);
– If a mobile which supports Downlink Dual Carrier receives a PACKET DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF DOWNLINK ASSIGNMENT message or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources on two carriers and those two carriers are not within the same frequency band, 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 (void)
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 or an EC PACKET TBF RELEASE message to the mobile station on the (EC-)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 or the EC PACKET TBF RELEASE message, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGMENT or an EC PACKET CONTROL ACKNOWLEDGMENT message in the uplink resources specified.
In A/Gb mode, if there are no other on-going TBFs, the mobile station in packet transfer mode shall enter packet idle mode; the mobile station in dual transfer mode shall enter dedicated mode. If there is one or more on-going TBFs, the mobile station shall remain in its current mode i.e. packet transfer mode or dual transfer mode. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5.
In Iu mode, if no on-going TBFs on SBPSCH exist, the mobile station in MAC-Shared state shall enter the MAC-Idle State; the mobile station in MAC-DTM state shall enter the MAC-Dedicated state. If any on-going TBFs on SBPSCH exist, the mobile station shall remain in its current state, i.e. either MAC-Shared state or MAC-DTM state. The DRX mode procedures shall be applied.
8.1.3 (void)
8.1.4 RLC data block transfer during an MBMS radio bearer
8.1.4.0 General
For each MBMS radio bearer, 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 MBMS radio bearer. If the network has no other RLC/MAC block to transmit, but wishes to transmit on the downlink, the network may either follow the procedure specified in sub-clause 9.3.1a, to keep the MBMS radio bearer alive or transmit an RLC/MAC control block containing a PACKET DOWNLINK DUMMY CONTROL BLOCK message.
8.1.4.1 RLC data block transfer during an MBMS radio bearer
Procedures on receipt of a downlink assignment message (e.g. MBMS ASSIGNMENT message) are specified in sub-clause 7.7.2.2. After switching to the assigned PDCHs, the mobile station shall start a T3190 timer instance for the corresponding MBMS radio bearer and shall attempt to decode every downlink block on the assigned PDCHs.
Additionally, upon reception of an MBMS ASSIGNMENT or MBMS MS_ID ASSIGNMENT message assigning a specific MS_ID value to a mobile station, this mobile station shall start a T3290 timer instance for the corresponding MBMS radio bearer, as specified in sub-clause 7.7.2.4.
The mobile station shall restart the related T3190 timer instance whenever receiving a valid RLC/MAC block including the assigned MBMS Bearer Identity. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. A mobile station with an assigned MS_ID value shall restart the related T3290 timer instance whenever receiving a valid RLC/MAC block including the corresponding MBMS Bearer Identity and the MS_ID in the TFI field.
On expiry of a T3290 timer instance, the mobile station shall consider the MS_ID as released, i.e. it shall no longer answer when polled according to sub-clause 8.1.4.2 below. On expiry of a T3190 timer instance, the mobile station shall consider the related MBMS radio bearer as released and proceed as specified in sub-clause 7.7.1.
8.1.4.2 Polling for MBMS Downlink Ack/Nack
If an uplink feedback channel is established, the network may poll any mobile station with an assigned MS_ID value by setting the (E)S/P bit and a valid RRBP field in the RLC/MAC header of an RLC/MAC block for data transfer containing both the MBMS Bearer Identity and the corresponding MS_ID value in the TFI field. Whenever a given mobile station is polled, the mobile station shall transmit an MBMS DOWNLINK ACK/NACK message in the uplink radio block specified by the RRBP field, whatever the BSN value of the received RLC data block. In GPRS TBF mode (respectively EGPRS TBF mode), the mobile station shall include the Ack/Nack Description IE (respectively the EGPRS Ack/Nack Description IE) in the message.
The mobile station shall include in the MBMS DOWNLINK ACK/NACK message neighbouring cells measurement results as described in sub-clause 5.6.4. In EGPRS TBF mode, the number of measurement reports included is specified in sub-clause 9.1.8.2.1. In GPRS TBF mode where cell reselection criteria are not fulfilled three measurement reports shall be included.
In EGPRS TBF mode, the mobile station shall react to a poll within an RLC/MAC block for data transfer if the RLC/MAC header is correctly received and addresses the mobile station (i.e. contains both the MBMS Bearer Identity and the corresponding MS_ID value in the TFI field) regardless whether the RLC data block(s) is(are) correctly received or not.
The mobile station shall notify, whenever possible, the network of the release of the MS_ID (see note), for that MBMS radio bearer, on the mobile station side, by setting the MS_ID Release Indication bit to ‘1’ in the MBMS DOWNLINK ACK/NACK message. Any procedure triggering the release of the MS_ID on the mobile station side shall not be delayed by such release indication (otherwise such release indication shall not be sent).
NOTE: The mobile station may need to release the related MBMS session for whatever reason (e.g. due to cell re-selection, start of the reception of a higher priority MBMS session whose MBMS radio bearer description does not allow the mobile station to receive it in parallel with the current MBMS session, start of a CS connection).
Whenever the network receives a valid RLC/MAC control message containing an assigned MS_ID value, it shall reset the counter N3105 for that MS_ID. The network shall increment the counter N3105 for a given MS_ID for each radio block, allocated via the polling procedure to the mobile station identified by that MS_ID value, for which no RLC/MAC control message is received. If N3105 = N3105_MBMS_MAX, the network shall release the MS_ID (i.e. shall internally remove the association between the MS_ID value and the mobile station identified during the MBMS address assignment procedure) and start timer T3195 for that MS_ID. When T3195 elapses, the network may reuse the corresponding MS_ID value.
8.1.4.3 Reconfiguration of an MBMS radio bearer
8.1.4.3.1 Individual reassignment of an MS_ID
The network may modify or delete the MS_ID previously assigned to a given mobile station by sending an MBMS MS_ID ASSIGNMENT message on the PACCH/D, containing the current and, in case of a reassignment, the new MS_ID value.
The mobile station shall be addressed with the Global TFI, containing the DOWNLINK_TFI field, which includes the MBMS Bearer Identity of the MBMS radio bearer and the current MS_ID of the mobile station the message relates to. The size of the new MS_ID, if present, shall be equal to the one of the current MS_ID. If the new MS_ID is present, the network may include the Packet Timing Advance IE.
When modifying or deleting the current MS_ID, the MBMS MS_ID ASSIGNMENT message shall include a current MS_ID expiry time.
In response to an MBMS DOWNLINK ACK/NACK message with the MS_ID Release Indication bit set to ‘1’ (see sub-clause 8.1.4.2), the network may send an MBMS MS_ID ASSIGNMENT message to the mobile station, deleting the MS_ID previously assigned to that mobile station on that MBMS radio bearer and setting the current MS_ID expiry time to the point in time when the message is transmitted to the mobile station, without further polling the mobile station on that MBMS radio bearer. The network shall then start timer T3199 for the current MS_ID.
Upon reception of an MBMS MS_ID ASSIGNMENT message, modifying or deleting the current MS_ID, the addressed mobile station shall consider the current MS_ID as released at the point in time denoted by the current MS_ID expiry time. If a new MS_ID is included in the message, the mobile station shall consider the new MS_ID as valid and restart timer T3290 at the point in time denoted by the current MS_ID expiry time and react when polled with the new MS_ID, according to sub-clause 8.1.4.2.
If a valid RRBP field is received as part of the MBMS MS_ID ASSIGNMENT message, the mobile station shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the specified uplink radio block.
If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the specified radio block, it shall increment counter N3109 for the current MS_ID and may retransmit the MBMS MS_ID ASSIGNMENT message addressing the mobile station with the current MS_ID. If counter N3109 = N3109_MAX or at the point in time denoted by the current MS_ID expiry time without receiving a PACKET CONTROL ACKNOWLEDGEMENT message, whatever occurs first, the network shall start timer T3199 for the current MS_ID. While timer T3199 is running for the current MS_ID, the network shall not include the current MS_ID in any RLC/MAC block belonging to that MBMS radio bearer. When timer T3199 expires for the current MS_ID, the network may reuse the current MS_ID resource. At the point in time denoted by the current MS_ID expiry time the network shall start timer T3199 for the new MS_ID, if present. While timer T3199 is running for the new MS_ID, the network shall not include the new MS_ID in any RLC/MAC block belonging to that MBMS radio bearer. When timer T3199 expires for the new MS_ID, the network may reuse the new MS_ID resource.
When modifying the current MS_ID, after the point in time denoted by the current MS_ID expiry time, the network shall address the mobile station with the new MS_ID, unless counter N3109 for the current MS_ID equals N3109_MAX or within the point in time denoted by the current MS_ID expiry time the network has not received a PACKET CONTROL ACKNOWLEDGEMENT message from the polled mobile station.
8.1.4.3.2 Reassignment of the MBMS Bearer Identity
The network may reassign the MBMS Bearer Identity previously assigned to a given MBMS radio bearer by sending an MBMS ASSIGNMENT (NON-DISTRIBUTION) message on the PACCH/D, including the current MBMS Bearer Identity (in the most significant bit(s) of the DOWNLINK_TFI field contained in the Global TFI), explicitly redefining (i.e. modifying the length and/or value of) such MBMS Bearer Identity and implicitly deleting or redefining MS_IDs assigned to that MBMS radio bearer as described below.
When reassigning the MBMS Bearer Identity the network shall not reuse the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field.
If the mobile station receives more than one MBMS ASSIGNMENT (NON-DISTRIBUTION) message for a given MBMS radio bearer, it shall act upon the most recently received message and shall ignore the previous message.
If a valid RRBP field is received as part of the MBMS ASSIGNMENT (NON-DISTRIBUTION) message, the mobile station identified by the corresponding MS_ID shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the specified uplink radio block.
Any redefinition of an MBMS Bearer Identity and any deletion or redefinition of MS_IDs shall apply at the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise:
– if the new MBMS Bearer Identity field has the same length as the current one all previously assigned MS_ID values shall be considered still valid;
– if the new MBMS Bearer Identity field is x bits shorter than the current one, all previously assigned MS_ID values shall be implicitly redefined by adding x most significant bits set to zero and shall be considered all valid;
– if the new MBMS Bearer Identity field is x bits longer than the current one, all previously assigned MS_ID values characterized by their x most significant bits equal to zero shall be implicitly redefined by removing these x most significant bits and still considered valid. All other assigned MS_ID values shall be considered as invalid and discarded.
At the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise, a mobile station shall restart timer T3190 for the newly assigned MBMS Bearer Identity. The mobile station shall restart timer T3190 whenever receiving an RLC/MAC block including the new MBMS Bearer Identity. If timer T3190 expires, the mobile station shall consider the MBMS radio bearer as released and proceed as specified in sub-clause 7.7.1. At the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise, a mobile station with an assigned MS_ID value shall start timer T3290. The mobile station shall restart timer T3290 whenever receiving an RLC/MAC block including both the new MBMS Bearer Identity and the new MS_ID in the TFI field.
The following table illustrates the definition of the new MS_ID upon reassignment of the MBMS Bearer Identity:
Table 8.1.4.3.2.1: Reassignment of MBMS Bearer Identity and MS_ID
|
New Current |
Bearer ID |
MS_ID |
Bearer ID |
MS_ID |
Bearer ID |
MS_ID |
Bearer ID |
MS_ID |
Bearer ID |
MS_ID |
|
|
Bearer ID |
MS_ID |
5 bits |
– |
4 bits |
1 bit |
3 bits |
2 bits |
2 bits |
3 bits |
1 bit |
4 bits |
|
5 bits |
– |
No MS_ID |
New MS_IDs available |
New MS_IDs available |
New MS_IDs available |
New MS_IDs available |
|||||
|
4 bits |
1 bit |
Discard current MS_ID |
Keep current MS_ID |
x 0x New MS_IDs available |
x 00x New MS_IDs available |
x 000x New MS_IDs available |
|||||
|
3 bits |
2 bits |
0x x 1x Discard current MS_ID |
Keep current MS_ID |
xx 0xx New MS_IDs available |
xx 00xx New MS_IDs available |
||||||
|
2 bits |
3 bits |
00x x Other Discard current MS_ID |
0xx xx 1xx Discard current MS_ID |
Keep current MS_ID |
xxx 0xxx New MS_IDs available |
||||||
|
1 bit |
4 bits |
000x x Other Discard current MS_ID |
00xx xx Other Discard current MS_ID |
0xxx xxx 1xxx Discard current MS_ID |
Keep current MS_ID |
||||||
|
NOTE: The following notations are used: "No MS_ID": no MS_ID available. MS is not allowed to use feedback "Discard current MS_ID": MS shall discard the current MS_ID. MS is no longer allowed to use feedback "New MS_IDs available": MS_IDs are made available for incoming MSs "Keep current MS_ID": MS shall keep its current MS_ID and use feedback (i.e. reply when polled with this MS_ID) n m: current MS_ID new MS_ID. Defines the value of the new MS_ID based on the value of the current MS_ID "x" "x" means the same bit value is used |
|||||||||||
The network shall start timer T3191 at the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise. When timer T3191 expires the network may reuse the TFI values corresponding to the old MBMS Bearer Identity, i.e. the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field.
8.1.4.3.3 Resource reassignment for an MBMS radio bearer
The network may initiate resource reassignment for an MBMS radio bearer by sending the MBMS ASSIGNMENT (NON-DISTRIBUTION) message, including the MBMS Bearer Identity (in the most significant bit(s) of the DOWNLINK_TFI field contained in the Global TFI), on the PACCH/D of the MBMS radio bearer. During the reassignment of the MBMS radio bearer its associated MBMS Bearer Identity may be changed.
In case of partial or complete overlap between the old and the new resource configuration on the downlink, the MBMS Bearer Identity shall be changed.
If the MBMS Bearer Identity is changed the network shall not reuse the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field.
If the mobile station receives more than one MBMS ASSIGNMENT (NON-DISTRIBUTION) message for a given MBMS radio bearer, it shall act upon the most recently received message and shall ignore the previous message.
If a valid RRBP field is received as part of the MBMS ASSIGNMENT (NON-DISTRIBUTION) message, the mobile station identified by the corresponding MS_ID shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the specified uplink radio block.
On receipt of an MBMS ASSIGNMENT (NON-DISTRIBUTION) message, and at the point in time denoted by the MBMS radio bearer starting time, if present, the mobile station shall switch to the assigned PDCHs. Upon switching to the assigned PDCHs the mobile station shall restart timer T3190 for the newly assigned MBMS radio bearer. The mobile station shall restart timer T3190 whenever receiving a valid RLC/MAC block belonging to that MBMS radio bearer. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station.If timer T3190 expires, the mobile station shall consider the MBMS radio bearer as released and proceed as specified in sub-clause 7.7.1. Upon switching to the assigned PDCHs, a mobile station with an assigned MS_ID value shall restart timer T3290. The mobile station shall restart timer T3290 whenever receiving an RLC/MAC block including both the MBMS Bearer Identity and the MS_ID in the TFI field.
With an MBMS ASSIGNMENT (NON-DISTRIBUTION) message the network may explicitly redefine (i.e. modify the length and/or value of) the MBMS Bearer Identity of an MBMS radio bearer and implicitly delete or redefine MS_IDs assigned to that MBMS radio bearer as specified in sub-clause 8.1.4.3.2. Any redefinition of an MBMS Bearer Identity and any deletion or redefinition of MS_IDs shall only be effective as of switching to the assigned PDCHs.
After resource reassignment the mobile station shall receive system information messages and paging messages on the (P)BCCH and the (P)CCCH or on the PACCH of the MBMS radio bearer, depending on the value of the MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT (NON-DISTRIBUTION) message and on the presence of an assigned MS_ID value.
The network shall start timer T3191 at the point in time denoted by the MBMS radio bearer starting time, if present, and immediately otherwise. When timer T3191 expires the network may reuse the TFI values corresponding to the old MBMS Bearer Identity, i.e. the TFI values including the old MBMS Bearer Identity in the most significant bit(s) of the TFI field, on the old resource configuration.
8.1.4.4 Network initiated release of an MBMS radio bearer
The network may initiate the normal or abnormal release of an MBMS radio bearer by transmitting a PACKET TBF RELEASE message to the mobile station(s) on the PACCH.
The following applies when the PACKET TBF RELEASE message is used for releasing an MBMS radio bearer:
– the Global TFI shall always contain the DOWNLINK_TFI field. The most significant bit(s) of the DOWNLINK_TFI field denote(s) the MBMS Bearer Identity of the MBMS radio bearer released by the message;
– the UPLINK_RELEASE field shall be ignored by the mobile station;
– the DOWNLINK_RELEASE field shall always be set to the value ‘1’ by the network to indicate that the MBMS radio bearer is released.
NOTE: The network may retransmit the PACKET TBF RELEASE message to increase the probability of its correct reception. Timer T3191 is (re)started every time the PACKET TBF RELEASE message is sent. When timer T3191 expires for the MBMS radio bearer, then the network may reuse all the TFIs related to the MBMS radio bearer.
Upon receipt of a PACKET TBF RELEASE message referring to an MBMS radio bearer the mobile station is receiving, the mobile station shall immediately consider the MBMS Bearer Identity, and the MS_ID if assigned, as released, and stop timers T3190 and T3290.
If the mobile station in broadcast/multicast receive mode is not receiving any other MBMS radio bearers, it shall enter packet idle mode and apply the DRX mode procedures as specified in sub-clause 5.5.1.5, otherwise it shall remain in broadcast/multicast receive mode.
8.1.4.5 Suspension/Resumption of the reception of an MBMS radio bearer
In case a mobile station that supports multiple TBF procedures suspends the reception of an MBMS radio bearer for whatever reason, the mobile station may retain the MBMS bearer description for such MBMS radio bearer until the expiry of the T3190 timer instance for the corresponding MBMS radio bearer. The corresponding MBMS bearer description shall be deleted if the mobile station completes a cell reselection or the session duration timer for this MBMS session in the mobile station expires.
When the mobile station returns to packet idle mode or completes the reception of higher mobile station-specific priority MBMS session(s), preventing the mobile station from receiving the suspended MBMS session, still remaining in broadcast/multicast receive mode,
– if the MBMS bearer description is still stored in the mobile station, then the mobile station may attempt to resume the reception of the suspended MBMS session (re-entering broadcast/multicast receive mode if the mobile station has previously left it);
– otherwise the mobile station shall repeat the MBMS packet access procedure for the MBMS session, as specified in sub-clause 7.7.1, unless the session duration timer for this MBMS session in the mobile station has expired.
8.1.5 Multiple MBMS radio bearers
8.1.5.1 Transmission of multiple MBMS radio bearers
On a PDCH on which multiple MBMS radio bearers are multiplexed, the TFI value(s) including an MBMS Bearer Identity (in the most significant bit(s) of the TFI field) shall differ from all the other TFI values including any other MBMS Bearer Identity (in the most significant bit(s) of the TFI field).
8.1.5.2 Reception of multiple MBMS radio bearers
8.1.5.2.1 General
The reception of multiple MBMS radio bearers depends on the capabilities of the mobile station. If the mobile station supports multiple TBF procedures and MBMS, it shall be able to support the reception of multiple MBMS radio bearers.
In this sub-clause (and sub-clauses 8.1.5.2.2 to 8.1.5.2.7) the priority is mobile station-specific and allows for prioritisation between MBMS sessions on a per-mobile station basis. If two or more MBMS sessions have the same priority, the mobile station shall perform an implementation-dependent selection of the MBMS session with the highest priority so the resulting priorities are distinct for each MBMS session.
The mobile station shall be able, according to its capabilities, to receive as many MBMS sessions as possible in decreasing order of priority, and to transmit MBMS DOWNLINK ACK/NACK messages (when applicable) for as many MBMS sessions as possible in decreasing order of priority.
NOTE: Depending on the radio resources allocated for the MBMS radio bearers, a mobile station may not be capable of transmitting MBMS DOWNLINK ACK/NACK messages on all associated uplink feedback channels.
If a mobile station is receiving multiple MBMS radio bearers and the mobile station has an MS_ID on at least one MBMS radio bearer where the network has indicated that system information for the serving cell and paging messages are sent on the PACCH/D, then the mobile station shall not read the system information on the (P)BCCH and shall not monitor its paging group on the (P)CCCH in parallel to the MBMS radio bearers.
If a mobile station is receiving multiple MBMS radio bearers and the mobile station has no MS_ID on any of the MBMS radio bearers where the network has indicated that system information for the serving cell and paging messages are sent on the PACCH/D, then the mobile station shall not read the system information on the (P)BCCH and shall monitor its paging group on the (P)CCCH in parallel to the MBMS radio bearers.
8.1.5.2.2 Reception of notification of lower priority MBMS session whilst receiving higher priority MBMS session(s)
If the mobile station in broadcast/multicast receive mode receives a notification of a lower priority MBMS session which includes the MBMS bearer description:
– if the capabilities of the mobile station allow, the mobile station shall receive that MBMS session in parallel with the higher priority MBMS session(s), provided the requirements defined in sub-clause 8.1.5.2.1 are fulfilled;
– otherwise, the mobile station shall discard the notification.
If the mobile station in broadcast/multicast receive mode receives a notification of a lower priority MBMS session which does not include the MBMS bearer description and requests the counting procedure, the mobile station shall not perform the MBMS packet access procedure.
8.1.5.2.3 Reception of assignment of lower priority MBMS session whilst receiving higher priority MBMS session(s)
If the mobile station in broadcast/multicast receive mode receives an assignment for a lower priority MBMS session, the mobile station shall act upon the assignment provided the requirements defined in sub-clause 8.1.5.2.1 are fulfilled.
8.1.5.2.4 Reception of notification of higher priority MBMS session whilst receiving lower priority MBMS session(s)
If the mobile station in broadcast/multicast receive mode receives a notification of a higher priority MBMS session which includes the MBMS bearer description, the mobile station shall act upon the MBMS bearer description and receive in parallel other lower priority MBMS sessions according to the requirements defined in sub-clause 8.1.5.2.1.
If the mobile station in broadcast/multicast receive mode receives a notification of a higher priority MBMS session which does not include the MBMS bearer description and requests the counting procedure, then the mobile station shall suspend the reception of the lower priority MBMS session(s) and perform the MBMS packet access procedure for the higher priority MBMS session, as specified in sub-clause 7.7.1. After performing the MBMS packet access procedure, if the MBMS bearer description(s) for the suspended lower priority MBMS session(s) is (are) still stored in the mobile station, then the mobile station may attempt to resume the reception of the suspended MBMS session(s) (see sub-clause 8.1.4.5).
8.1.5.2.5 Reception of assignment of higher priority MBMS session whilst receiving lower priority MBMS session(s)
If the mobile station in broadcast/multicast receive mode receives an assignment for a higher priority MBMS session, the mobile station shall act upon the assignment and may drop lower priority MBMS sessions following the requirements defined in sub-clause 8.1.5.2.1.
8.1.5.2.6 Cell change whilst receiving multiple MBMS sessions (with MBMS supported by the network in the target cell)
When the mobile station reselects a new (target) cell, the mobile station shall according to its capabilities:
– first perform fast reception resumption (see sub-clause 8.1.6.2) of as many MBMS sessions as possible in decreasing order of priority, for the sessions for which the mobile station has received in the old cell MBMS NEIGHBOURING CELL INFORMATION messages containing the MBMS bearer description of these sessions in this target cell;
NOTE 1: The mobile station shall not perform MBMS packet access procedure for requesting an MS_ID for any MBMS session, with an associated uplink feedback channel, whose priority is lower than the priority of at least one of the MBMS sessions for which the MBMS bearer description is not known.
– then perform MBMS packet access and establishment procedure as specified in sub-clause 7.7 for the sessions for which the MBMS bearer description is not known, in decreasing order of priority. The mobile station shall not operate two concurrent MBMS packet access and establishment procedures.
NOTE 2: The MBMS packet access procedure is performed in passive mode (i.e. the mobile station notifies the network in the MBMS SERVICE REQUEST message that it shall not be counted) for any MBMS session whose priority is lower than the priority of at least one of the MBMS sessions already resumed. The mobile station may then perform MBMS packet access procedure for requesting an MS_ID for the remaining MBMS sessions, with an associated uplink feedback channel, following the requirements defined in sub-clause 8.1.5.2.1.
NOTE 3: The mobile station shall not perform an MBMS packet access procedure for an MBMS session, if the session duration timer for this MBMS session in the mobile station has expired.
8.1.5.2.7 Resource reassignment for at least one of the received MBMS radio bearers
If a mobile station is receiving multiple MBMS radio bearers and any of these is reconfigured by the network in a way that the reception of all of them is no longer consistent with the capabilities of the mobile station, then the mobile station shall continue receiving the highest priority MBMS session and as many as possible of the other MBMS sessions, following the requirements defined in sub-clause 8.1.5.2.1.
8.1.6 MBMS reception resumption after cell reselection
8.1.6.1 Default behaviour
If a mobile station in broadcast/multicast receive mode reselects a new (target) cell for which it does not have the description of (any of) the MBMS radio bearer(s) being allocated in this target cell for the MBMS session(s) the mobile station was receiving in the old serving cell, the mobile station shall follow the default behaviour in the target cell, as described in this sub-clause. Otherwise, the mobile station shall perform fast reception resumption, as described in sub-clause 8.1.6.2.
In the target cell, the mobile station shall first perform the acquisition of the system information on the (P)BCCH.
If the GPRS Cell Options IE denotes that the MBMS procedures are supported by the target cell, the mobile station shall then perform the MBMS packet access and establishment procedures, as specified in sub-clause 7.7, for the MBMS session the mobile station was receiving in the old serving cell.
In case of reception of multiple sessions, the mobile station shall obey the procedures described in sub-clause 8.1.5.2.6.
8.1.6.2 Fast reception resumption
If a mobile station in broadcast/multicast receive mode reselects a new (target) cell for which it has received the description of (at least one of) the MBMS radio bearer(s) being allocated in this target cell for the MBMS session(s) the mobile station was receiving in the old serving cell (see sub-clauses 5.5.1.1 and 7.7.3), the mobile station shall perform fast reception resumption in the target cell, as described in this sub-clause. Otherwise, the mobile station shall follow the default behaviour, as described in sub-clause 8.1.6.1.
In the target cell, the mobile station shall immediately resume the reception of the MBMS session for which the MBMS bearer description is known from the old serving cell, without first performing the acquisition of the system information. If the mobile station fails to resume the reception of the MBMS session for any reason and does not have any other MBMS bearer description known for any other MBMS session possibly received in the old serving cell, the mobile station shall then follow the default behaviour (see sub-clause 8.1.6.1).
The acquisition of the system information shall be performed simultaneously with the reception of the MBMS session. If the network has indicated that the system information for the resumed MBMS session is not sent on the PACCH (with the MBMS In-band Signalling Indicator information element included in the MBMS NEIGHBOURING CELL INFORMATION message transmitted in the old serving cell), the mobile station shall perform the acquisition of the system information on the (P)BCCH. In this case, the reception of the MBMS session may need to be suspended during such acquisition. The mobile station may then attempt to resume the reception of the suspended MBMS session, according to the requirements and the procedures described in sub-clause 8.1.4.5. If the network has indicated that the system information for the resumed MBMS session is sent on the PACCH, the mobile station shall perform the acquisition of the system information on the PACCH, as described in sub-clause 5.5.2.1.3b.
If the mobile station has received the indication (via the MBMS NEIGHBOURING CELL INFORMATION message transmitted in the old serving cell) that, for the MBMS radio bearer corresponding to the resumed MBMS session, an uplink feedback channel is established in the new cell, the mobile station initiates the MBMS packet access procedure either:
– on the MPRACH, if the mobile station is in DRX mode (e.g. it is not involved in a routeing area update procedure) and received the indication that an MPRACH is allocated on the uplink feedback channel (sub-clause 7.7.1.4), or
– on a PCCCH (sub-clause 7.7.1.2) or,
– if a packet control channel is not allocated in the cell, on a CCCH (sub-clause 7.7.1.3).
In case of reception of multiple sessions, the mobile station shall obey the procedures described in sub-clause 8.1.5.2.6.
8.1.7 Packet Application Information
8.1.7.1 General
The Packet Application Transfer procedure enables an application on the network side to transfer Application data to a mobile station.
The network may send the PACKET APPLICATION INFORMATION message to a mobile station in packet transfer mode or in dual transfer mode on the PACCH with one of the following applications:
8.1.7.2 Earthquake and Tsunami Warning System (ETWS)
The PACKET APPLICATION INFORMATION message enables the network to transfer an ETWS Primary Notification message, see 3GPP TS 23.041, to a mobile station.
A mobile station operating in packet transfer mode or in dual transfer mode may receive a PACKET APPLICATION INFORMATION message on the PACCH, Since this message may be segmented across more than two RLC/MAC control blocks, by using extended RLC/MAC control message segmentation, the mobile station shall attempt to acquire all segments of the PACKET APPLICATION INFORMATION message before attempting to decode the message. Upon receiving the complete PACKET APPLICATION INFORMATION message the ETWS Primary Notification message shall be sent to upper layers.
8.1.8 Dynamic Timeslot Reduction
8.1.8.1 General
Dynamic Timeslot Reduction (DTR) allows the network to command the mobile station in packet transfer mode to reduce the number of downlink timeslots that it is required to monitor during inactivity periods of a TBF. The network should use DTR only when extended uplink TBF mode with EXT_UTBF_NODATA set to ‘1’ and/or delayed downlink TBF release are used.
The network orders a mobile station that supports DTR to reduce the number of downlink timeslots it shall monitor during the inactivity periods of a TBF (as specified for delayed downlink TBF release and extended uplink TBF mode) by sending it DTR information as defined in sub-clause 8.1.8.2.
The mobile station shall indicate its support for DTR in the MS Radio Access Capabilities IE (see 3GPP TS 24.008).
8.1.8.2 DTR Activation
The network shall send DTR information including the TN/PDCH-pair field indicating the timeslot number (BTTI configuration) or the PDCH-pair number (RTTI configuration) and the carrier ID (if the mobile station is in dual carrier configuration) of the timeslot or the PDCH-pair the mobile station shall monitor for USFs and downlink RLC/MAC blocks while in DTR mode. A mobile station with an assigned uplink TBF shall ignore the DTR information in case the indicated timeslot or PDCH-pair is not within the timeslots assigned to the uplink TBF. A mobile station with an assigned downlink TBF shall ignore the DTR information if the indicated timeslot or PDCH-pair does not correspond to a timeslot or PDCH-pair assigned to the downlink TBF. For a DLMC configuration the network shall send DTR information including the TN/PDCH-pair field indicating the timeslot number (BTTI configuration) or the PDCH-pair number (RTTI configuration) of the timeslot or the PDCH-pair the mobile station shall monitor for radio blocks on the downlink carrier used for fall back according to a regular pre-determined interval (see sub-clause 5.13).
In addition, the DTR information may indicate the mobile station is only required to monitor a sub-set of the radio blocks on the monitored timeslot/PDCH-pair, as indicated by the DTR Blks parameter.
During a downlink TBF, the network may transmit the DTR information within downlink RLC data blocks of the TBF (see sub-clause10.3a.1). During an uplink TBF, the network may transmit the DTR information within a PACKET UPLINK ACK/NACK message. If DTR information is received in a PACKET UPLINK ACK/NACK message and an RLC data block in the same block period, the mobile station shall ignore the DTR information received in the RLC data block.
A mobile station not already in DTR mode shall enter DTR mode and start monitoring only the indicated PDCH or PDCH-pair (and if applicable, carrier) within the reaction time specified in 3GPP TS 45.010, when:
– DTR information was included in whichever of the following was the most recently received:
i) any PACKET UPLINK ACK/NACK message (applicable if the mobile station has an ongoing uplink TBF) and
ii) the RLC data block with BSN equal to V(Q) – 1 modulo SNS (applicable if the mobile station has an ongoing downlink TBF) and
– V(R) = V(Q), if the mobile station has an ongoing downlink TBF, and
– if the mobile station has an ongoing uplink TBF, the RLC data block with BSN = V(S) is not available and either:
– V(A) = V(S), or
– V(A) < V(S) mod SNS, the most recently received pre-emptive transmission bit is set to ‘0’, and no element of V(B) has the value NACKED (for RLC acknowledged mode).
NOTE 1: If the network includes DTR information in a PACKET UPLINK ACK/NACK message which includes one or more NACK indications, and the pre-emptive transmission bit is set to ‘0’, upper layer PDUs may be delayed due to the limited uplink bandwidth available when in DTR mode. In order to ensure there are no delays in the delivery of upper layer uplink PDUs, the network should not send DTR information in a PACKET UPLINK ACK/NACK message which includes multiple NACK indications.
NOTE 2: The network may not be able to determine the exact point when the mobile station enters DTR but may use appropriate means (e.g. polling on a timeslot other than the monitored timeslot) to confirm that the MS has entered DTR.
A mobile station already in DTR mode shall assume the DTR information is unchanged and shall therefore remain in DTR mode, i.e. the network shall ensure the DTR information is kept unchanged for this MS while it remains in DTR mode.
The mobile station shall respond to any poll for PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGMENT message received in radio block periods up to and including the one in which the mobile station is triggered to enter DTR mode (i.e. in which all conditions for entering DTR, as specified in this sub-clause, are met), as specified in sub-clause 8.1.2.2 and sub-clause 8.6. The mobile station shall respond to any poll for PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGMENT message if it was received on the timeslot/PDCH-pair to be monitored during DTR mode and was received during a radio block period after the one in which the mobile station is triggered to enter DTR mode.
When a mobile station operating concurrent TBFs in both directions is ordered to enter DTR mode, it shall apply DTR mode on both TBFs. The mobile station shall monitor the indicated PDCH or PDCH-pair for USFs and downlink RLC/MAC blocks.
8.1.8.3 Resumption to normal operation
The mobile station shall exit DTR mode within the reaction time specified in 3GPP TS 45.010:
– when an RLC data block with BSN equal to V(S) is transmitted and the medium access mode is Dynamic Allocation;
– when an EGPRS RLC/MAC block for data transfer including BSN higher than V(R) modulo SNS is received;
– when an RLC data block with BSN equal to V(R) not including a valid DTR information is received;
– upon reception of an assignment message (PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, PACKET CS RELEASE INDICATION) or PACKET UPLINK ACK/NACK message without a DTR information. If a TBF starting time information element is present in the received assignment message, the mobile station shall wait until the indicated TBF starting time before switching to the assigned PDCHs and exiting DTR mode;
– upon reception of a PACKET PDCH RELEASE message releasing the monitored PDCH/PDCH-pair when the mobile station shall act as specified in sub-clause 8.2.