13 Timers and counters
3GPP44.060General Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 17TS
The tables in sub-clause 13.1 and 13.2 specify the timers used in RLC/MAC protocol signalling. The denotation of columns is defined as follows:
timer ::= name of the timer;
started ::= under which conditions the timer is started;
stopped ::= under which conditions the timer is stopped;
action at expiry ::= which actions the GPRS entity shall perform at expiry;
value ::= the duration between setting the timer and expiry of the timer ("s" denotes
"second(s)" "xx – yy" means that any value between xx and yy is permitted).
13.1 Timers on the Mobile Station side
For each timer, it is shown whether one timer instance is needed per MS, per TBF/MBMS radio bearer, per MS_ID or per RLC/MAC control message.
For EC-GSM-IoT, where blind physical layer transmissions are used, if a timer expires during an ongoing transmission opportunity, that transmission opportunity shall be considered as having occurred prior to the expiry of the timer.
Table 13.1.1: Specification of timers used in GPRS on the Mobile Station side
timer |
started |
stopped |
action at expiry |
value |
---|---|---|---|---|
T3158 (per MS) |
Started when ordered by a NETWORK_CONTROL_ORDER and then restarted each time a Network Controlled (NC) Measurement is performed in MM Ready state and in packet idle or packet transfer mode in A/Gb mode and in RRC-Cell_Shared state and MAC-Idle or MAC-Shared state in Iu mode. |
See 3GPP TS 45.008 |
Restart the timer, perform the measurement and send a NC Measurement report. The timer shall be restarted with either of the parameters NC_REPORTING_PERIOD_I when in packet idle mode or MAC-Idle state or with the parameter NC_REPORTING_PERIOD_T when in packet transfer mode or MAC-Shared state |
Defined by the parameter or by a random value (see 3GPP TS 45.008) |
T3162 (per MS) |
On receipt of a PACKET QUEUING NOTIFICATION |
On receipt of a PACKET UPLINK ASSIGNMENT |
Abort packet access procedure; indicate packet access failure to upper layers and return to packet idle mode or MAC-Idle state listening to its paging subchannel |
5 s |
T3164 (per TBF) |
On receipt of a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message. A separate instance of T3164 is started for each TBF for which resources were assigned. |
At sending of the first RLC/MAC block |
See sub-clause 7.1.4. (A/Gb mode). |
5 s |
T3166 (per MS) |
At sending of the first RLC/MAC block at one phase access |
On receipt of a PACKET UPLINK ACK/NACK |
Immediately stop transmitting on the assigned TBF; a TBF establishment failure has occurred or the contention resolution procedures has failed |
5 s |
T3168 (per TBF) |
At sending the PACKET RESOURCE REQUEST message, (Extended) Channel Request Description IE in PACKET DOWNLINK ACK/NACK or the PACKET CONTROL ACKNOWLEDGEMENT message requesting new TBF. A separate instance of T3168 is started for each TBF for which resources were requested. For an EC TBF, started at sending the EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the EC Channel Request Description IE. |
On receipt of a PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message that assigns resources to an uplink TBF for which T3168 is running. On receipt of a PACKET ACCESS REJECT or EC PACKET ACCESS REJECT message that rejects one or more uplink TBFs for which T3168 is running. For an EC TBF, restarted at a new transmission of an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message with the EC Channel Request Description IE. |
Reinitiate the packet access procedure or retransmit the PACKET RESOURCE REQUEST or PACKET DOWNLINK ACK/NACK for the TBFs that have not been assigned resources. A mobile station in EC operation 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. For a mobile station in EC operation that has included the EC Channel Request Description IE in an EC PACKET DOWNLINK ACK/NACK message with the Final Ack Indicator bit set to ‘1’, release the TBF resources, unless timer T3192 is still running. The packet access procedure may then be reinitiated on the (EC-)CCCH. |
Set to 2 times the value of T3168 sent as part of system broadcast information if the total number of TBFs requested is greater than 1. Otherwise, it shall be set to the value of T3168 sent as part of system broadcast information (on BCCH or EC-BCCH). For a mobile station in EC operation, if the value of T3168 was not provided in the EC SI, the value 0 (500 ms) shall be used. |
T3170 (per MS) |
After having made M + 1 attempts to send a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST message (if at least one message was transmitted by the mobile station), or on receipt of a PACKET ACCESS REJECT message. |
On receipt of a PACKET UPLINK ASSIGNMENT or PACKET DOWNLINK ASSIGNMENT or PACKET QUEUING NOTIFICATION message. |
Abort packet access procedure. In case of the expiry after having made M+1 attempts to send a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST message, indicate a random access failure to upper layers and perform autonomous cell re-selection. In case of the expiry following the receipt of a PACKET ACCESS REJECT message, indicate a packet access failure to upper layers and return to packet idle mode or MAC-Idle state. |
Defined by parameters TX_INT and S |
T3172 (per TBF) |
On receipt of an (EC) PACKET ACCESS REJECT message an instance of T3172 is started for each of the TBFs that have been rejected. |
On receipt of a PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT message or MULTIPLE TBF UPLINK ASSIGNMENT that assigns resources to the TBF for which T3172 is running. |
Packet Access in the cell no longer prohibited |
assigned in message |
T3174 (per MS) |
On receipt of a PACKET CELL CHANGE ORDER message |
On the successful completion or the occurrence of an abnormal condition in the network controlled cell reselection procedure |
Return to old cell, perform cell update (or other GMM specific procedure) and send PACKET CELL CHANGE FAILURE |
15 s |
T3176 (per MS) |
Expiry of T3174 or other abnormal condition in the network controlled cell reselection procedure |
After sending of PACKET CELL CHANGE FAILURE message |
Stop handling of abnormal condition in the network controlled cell reselection procedure. |
15 s |
T3180 (per TBF) |
When transmitting an RLC/MAC block to the network an instance of T3180 is started for the TBF for which the block was intended. It is also started for each uplink TBF allocated by the PS HANDOVER COMMAND message/DTM HANDOVER COMMAND message upon successful completion of the PS handover/DTM handover from Iu mode to A/Gb mode. |
When detecting an assigned USF value on assigned PDCH |
Abnormal release with access retry may be performed under certain conditions (see sub-clause 8.1.1.1) |
5 s |
T3182 (per TBF) |
After sending the last data block (with CV = 0), or upon detecting a transmit window stall condition an instance of T3182 is started for the TBF for which the condition has occurred. |
On receipt of the PACKET UPLINK ACK/NACK message |
Abnormal release with access retry may be performed under certain conditions (see sub-clauses 9.3.2.3 and 9.3.3.3) |
5 s |
T3184 (per TBF) |
On receipt of a PACKET UPLINK ACK/NACK message (in exclusive allocation) |
On receipt of PACKET UPLINK ACK/NACK message |
Abnormal release with access retry may be performed under certain conditions (see sub-clause 8.1.1.3a.2). |
5 s |
T3186 (per MS) |
When packet access procedure is started |
Either stopped when receiving any message from the network in response to the (EGPRS) PACKET CHANNEL REQUEST message or after M+1 attempts to send (EGPRS) PACKET CHANNEL REQUEST messages on the PRACH channel or |
Abort packet access procedure. If at least one message was transmitted by the mobile station, indicate random access failure to upper layers and perform autonomous cell re-selection; otherwise, indicate packet access failure to upper layers and return to packet idle mode or MAC-Idle state. |
5 s |
T3188 |
When a mobile station that supports multiple TBF procedures requests two or more uplink TBFs in a Packet Resource Request message during a two-phase access. |
When a mobile station that supports multiple TBF procedures receives a MULTIPLE TBF UPLINK ASSIGNMENT message. |
A mobile station that supports multiple TBF procedures considers its’ two-phase access to have failed |
Set to the value of T3168 included as part of system broadcast information. |
T3190 (per TBF/ MBMS radio bearer) |
At reception of a downlink assignment message an instance of T3190 is started for each TBF/MBMS radio bearer that has been assigned resources. It is also started for each downlink TBF allocated by the PS HANDOVER COMMAND message/DTM HANDOVER COMMAND message upon successful completion of the PS handover/DTM handover from Iu mode to A/Gb mode. |
Restarted on receipt of data on the TBF/MBMS radio bearer |
Abnormal release without retry may be performed under certain conditions (see sub-clauses 8.1.2.1 and 8.1.2.4). The MBMS packet access procedure may be initiated as specified in sub-clause 7.7.1. |
5 s |
T3192 (per TBF/ per RLC (NOTE 1)) |
At sending the (EC) PACKET DOWNLINK ACK/NACK with the Final Ack Indicator=1, or at sending the PACKET CONTROL ACK as a response to final RLC data block in unacknowledged mode. |
Restarted at sending the (EC) PACKET DOWNLINK ACK/NACK with the Final Ack Indicator=1, or at sending the PACKET CONTROL ACK as a response to final RLC data block in unacknowledged mode. Stopped at the reception of a PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message that assigns resources to the TBF for which T3192 was started. For an EC TBF, stopped at the reception of an EC PACKET DOWNLINK ASSIGNMENT or EC PACKET UPLINK ASSIGNMENT message. |
If the mobile station is in packet transfer mode or MAC-Shared state it shall release the resources, stop monitoring the PDCHs, and begin to monitor the paging channel if there are no other ongoing TBFs. The mobile station in dual transfer mode respectively MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. (see sub-clauses 9.3.2.6 and 9.3.3.5). A mobile station with an EC TBF shall release the resources, stop monitoring the EC-PDTCH(s)/EC-PACCH(s) and return to packet idle mode, unless timer T3168 is still running. |
assigned in system information For a mobile station in EC operation, if the value of T3192 was not provided in the EC SI, the timer shall be set to 0 ms. |
T3194 (per TBF) |
At the sending of a RLC data block on a radio block that has been stolen (i.e. intended for a different radio bearer). |
On receipt of the USF for the radio bearer for which the radio block was stolen. |
Restart the timer unless it has expired four times, in which case a link failure is reported to the RRC layer. |
200 ms |
T3196 |
When the RR connection request is received from the upper layer. |
Upon receipt of the PACKET CS COMMAND message. |
Release of all ongoing TBFs and start RR connection establishment as specified in 3GPP TS 44.018. |
1.5 s |
T3200 (per RLC/MAC control message) |
On receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message |
On receipt of an RLC/MAC control block containing a segment of an RLC/MAC control message such that the mobile station now has the complete control message |
Discard and ignore all segments of the partially received RLC/MAC control message |
see sub-clause 9.1.12b |
T3204 (per MS) |
The first attempt to send a PACKET CHANNEL REQUEST during a packet access procedure. The PACKET CHANNEL REQUEST was attempted indicating ‘Single block without TBF establishment’ and the purpose of the packet access procedure is to send a PACKET PAUSE message. |
Upon receipt of a PACKET UPLINK ASSIGHNMENT. |
The packet pause procedure (sub-clause 7.6) is aborted (A/Gb mode only). |
1 s |
T3206 (per MS) |
When entering CCN mode |
When the PACKET CELL CHANGE NOTIFICATION message is transmitted or when CCN is no longer enabled. |
Leave CCN mode and continue according to current NC mode |
400 ms |
T3208 (per MS) |
When the PACKET CELL CHANGE NOTIFICATION message is transmitted for the first time |
Upon receipt of a PACKET CELL CHANGE CONTINUE or a PACKET CELL CHANGE ORDER message or when CCN is no longer enabled.. |
Leave CCN mode and continue according to current NC mode |
0,96 s |
T3210 (per MS) |
When the PACKET CELL CHANGE NOTIFICATION message is transmitted for the first time |
Upon receipt of a PACKET NEIGHBOUR CELL DATA message, or a PACKET CELL CHANGE CONTINUE message or a PACKET CELL CHANGE ORDER message or when CCN is no longer enabled. |
Retransmit the PACKET CELL CHANGE NOTIFICATION message at the first uplink opportunity. |
0,3 s |
T3214 |
When the MBMS SERVICE REQUEST message is transmitted or when receiving MBMS notification, for an MBMS session the mobile station is required to receive, with no MBMS p-t-m channel description and indicating that no counting shall be performed. |
Upon receipt of the MBMS ASSIGNMENT message addressing the same session that started this timer or any other procedure on (P)CCCH not related to MBMS is triggered or a notification is received for a higher priority session. |
Mobile station in packet idle mode or MAC-Idle state: Return to DRX mode. Mobile station in broadcast/multicast receive mode: Remain in broadcast/multicast receive mode |
60 s |
T3216 (per MS) |
Upon transmission of the PS HANDOVER ACCESS message (see sub-clause 8.10.4.4.4). |
Upon receipt of the PACKET PHYSICAL INFORMATION message |
The MS returns to the old cell and attempts to resume packet data transmission (see sub-clause 8.10.5). |
1 s |
T3218 (per MS) |
On receipt of PS HANDOVER COMMAND message or Handover from UTRAN Command message or MobilityFromEUTRACommand message. |
Upon detecting of the first USF for any uplink TBF assigned to the MS in the new cell. |
The MS returns to the old cell and attempts to resume packet data transmission (see sub-clause 8.10.5). |
1 s |
T3220 |
When the PACKET PAGING REQUEST message containing MBMS pre-notification parameters, for an MBMS session the mobile station is required to receive, is received. |
Upon receipt of the PACKET PAGING REQUEST message containing MBMS notification parameters of the same session that started this timer or any other procedure on PCCCH not related to MBMS is triggered or a notification is received for a higher priority session. |
Mobile station in packet idle mode or MAC-Idle state: Return to DRX mode. Mobile station in broadcast/multicast receive mode: Remain in broadcast/multicast receive mode |
46 s |
T3222 |
When the PACKET MBMS ANNOUNCEMENT message is received indicating an MBMS broadcast service or an MBMS multicast service to which the mobile station has subscribed and an MBMS session the mobile station has not received, and including the Restriction Timer or the Estimated Session Duration. |
When the mobile station enters packet idle mode, if the PACKET MBMS ANNOUNCEMENT message included the Estimated Session Duration. When the mobile station enters packet idle mode and completes the Transfer non-DRX mode period, if the PACKET MBMS ANNOUNCEMENT message included the Restriction Timer. |
The MBMS related information stored upon receipt of the corresponding PACKET MBMS ANNOUNCEMENT message is deleted. |
See sub-clause 6.3.2.2 |
T3226 |
When the last allocated RLC data block has been transmitted according to a fixed uplink allocation (as received in an EC IMMEDIATE ASSIGNMENT, EC PACKET UPLINK ACK/NACK, EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION or EC PACKET UPLINK ASSIGNMENT message). |
None |
Timer T3228 is started and the mobile station starts to continuously read the downlink EC-PACCH for reception of an RLC/MAC control message. |
assigned in EC system information If the value of T3226 was not provided in the EC SI, the timer shall be set to 0 ms in EC operation |
T3228 |
At expiry of timer T3226. |
Upon receipt of an EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with the uplink TBF. |
The TBF shall be released and abnormal release with access retry may be performed, unless T3248 is used, i.e. it has a value > 0. If timer T3248 is used, it shall be started at expiry of T3228. The next higher CC shall then be used when monitoring the DL EC-PACCH, as long as T3248 is running. |
5 s minus the value for T3248 timer |
T3238 |
At reception of an EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to ‘1’ and indicating that the mobile station shall continue monitoring the EC-PACCH. |
At reception of an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station, or at reception of another RLC/MAC control message triggering the release of the uplink TBF. |
The mobile station shall leave the uplink TBF and return to packet idle mode. |
Assigned in message |
T3248 |
At expiry of timer T3228. |
Upon receipt of an EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with the uplink TBF. |
The TBF shall be released. Abnormal release with access retry may be performed. |
assigned in EC system information (EC SI) If assignment of timer value is not included in EC SI it has the value 0 and is thus not used |
T3290 (per MS_ID on an MBMS radio bearer) |
At reception of a downlink assignment (i.e. MBMS ASSIGNMENT, MBMS MS_ID ASSIGNMENT) message assigning an MS_ID to a mobile station receiving an MBMS radio bearer. |
Restarted on receipt of an RLC/MAC block including the corresponding MBMS Bearer Identity and the MS_ID in the TFI field. |
The mobile station considers the MS_ID as released, i.e. it no longer answers when polled with the MS_ID. |
5 s |
T3230 (per MS) |
When the PACKET CELL CHANGE ORDER or PACKET MEASUREMENT ORDER message containing individual priorities, is received. |
Upon occurrence of one of the conditions specified in subclause 5.5.1.1c.3. |
The MS shall delete the individual priorities value. |
Assigned in message |
T3232 (per MS) |
At reception of a PACKET PAGING REQUEST message on the PPCH carrying a segment of an ETWS Primary Notification message. |
At reception of the complete ETWS Primary Notification message or upon initiating cell reselection or connection establishment procedures. |
The mobile station shall enter DRX mode. |
5 s |
NOTE 1: Timer per RLC entity if EMST is used. |
T3158: Wait for sending measurement reports for network controlled cell reselection.
This timer is used on the mobile station side to define the period for performing NC-measurements and send measurement reports in either packet idle or packet transfer mode in A/Gb mode and MAC-Idle or MAC-Shared state in Iu mode (see 3GPP TS 45.008).
T3162: Wait for Packet Uplink Assignment after reception of Packet Queuing Notification
This timer is used on the mobile station side after received Packet Queuing Notification to define when to stop waiting for a Packet Uplink Assignment.
T3164: Wait for Uplink State Flag After Assignment
This timer is used on the mobile station side to define when to stop waiting for the USF determining the assigned portion of the uplink channel and repeat the procedure for random access. In multislot operation, it is enough that the assigned USF is noted on one of the uplink PDCHs.
T3166: Wait for Packet Uplink ACK/NACK after sending of first data block
This timer is used on the mobile station side to define when to stop waiting for a Packet Uplink ACK/NACK after sending of the first data block.
T3168: Wait for PACKET UPLINK ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT, Multiple TBF Uplink Assignment, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message
This timer is used on the mobile station side to define when to stop waiting for a Packet Uplink Assignment, EC PACKET UPLINK ASSIGNMENT, Multiple TBF Uplink Assignment, PACKET TIMESLOT RECONFIGURE or a MULTIPLE TBF TIMESLOT RECONFIGURE message after sending of a Packet Resource request message, a PACKET DOWNLINK ACK/NACK message, an EC PACKET DOWNLINK ACK/NACK or EC PACKET DOWNLINK ACK/NACK HIGHER CC message or a PACKET CONTROL ACKNOWLEDGEMENT message requesting new TBF.
T3170: Wait for Packet Uplink Assignment message after having done (M+1) Packet Channel Requests or after reception of a PACKET ACCESS REJECT message.
This timer is used on the mobile station side when having made M + 1 attempts to send a Packet Channel Request or EGPRS Packet Channel Request or MPRACH PACKET CHANNEL REQUEST message (if at least one message was transmitted by the mobile station) or after reception of a PACKET ACCESS REJECT message. At expiry of timer T3170 when having made M+1 attempts to send a PACKET CHANNEL REQUEST or EGPRS Packet Channel Request or MPRACH PACKET CHANNEL REQUEST message, the mobile station shall abort the packet access procedure, indicate a random access failure to upper layers and perform autonomous cell re-selection according to 3GPP TS 43.022. At expiry of timer T3170 after receiving a PACKET ACCESS REJECT message, the mobile station shall abort the packet access procedure, indicate a packet access failure to upper layers and return to packet idle mode or MAC-Idle state.
The value of this timer is equal to the time taken by T+2S TDMA frames, T and S are defined in sub-clause 7.1.2.1.1.
T3172: Prohibit packet access in the cell after (EC) Packet Access Reject message has been received.
This timer is used on the mobile station side on receipt of a Packet Access Reject message corresponding to one of the mobile station’s 3 last Packet Channel Request messages. If T3172 expires before receiving an assignment message, the mobile station returns to packet idle mode or MAC-Idle state.
After T3172 expiry packet Access is no longer prohibited in the cell but no Channel Request message shall be sent as a response to a page until a Paging Request message for the mobile station is received.
T3174: Wait for successful packet access in new cell after Packet Cell Change Order.
This timer is used on the mobile station side on receipt of a PACKET CELL CHANGE ORDER message. The timer is stopped upon successful completion of packet access in the new cell. On expiry, the mobile station returns to the old cell, performs cell update (or other GMM specific procedure) and sends PACKET CELL CHANGE FAILURE message.
T3176: Stop handling of abnormal condition in the network controlled cell reselection procedure.
This timer is started when T3174 expires or another abnormal condition occurs in the network controlled cell reselection procedure. The timer is stopped upon transmission of the PACKET CELL CHANGE FAILURE message. On expiry, the mobile station stops handling of abnormal condition in the network controlled cell reselection procedure.
T3180: Wait for Uplink State Flag After Data Block
This timer is used on the mobile station side to define when to stop waiting for the USF determining the assigned portion of the uplink channel after the previous RLC/MAC block is sent. In multislot operation, it is enough that the assigned USF is noted on one of the uplink PDCHs. If expired, the mobile station repeats the procedure for random access if there are no remaining TBFs. If it expires and there are one or more remaining TBFs the MS may reattempt the establishment of the corresponding uplink TBF.
T3182: Wait for Acknowledgement
This timer is used on the mobile station side to define when to stop waiting for temporary Packet Uplink Ack/Nack after the last RLC data block has been sent for the current send window or for the entire Temporary Block Flow.
T3184: No Ack/Nack Received
At exclusive allocation, this timer is used to detect a radio link failure condition. If expired, the mobile station performs an abnormal release with access retry.
T3186: Supervision of the random access procedure
This timer is used on the mobile station side to define the maximum allowed time to repeat the sending of all PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST or MPRACH PACKET CHANNEL REQUEST messages. At expiry of timer T3186, the mobile station shall abort the packet access procedure. If at least one message was transmitted by the mobile station, it shall indicate a random access failure to upper layers and perform autonomous cell re-selection according to 3GPP TS 43.022; otherwise, it shall indicate a packet access failure to upper layers and return to packet idle mode or MAC-Idle state.
T3188: This timer is used by a mobile station that supports multiple TBF procedures to define when to stop waiting for a MULTIPLE TBF UPLINK ASSIGNMENT message after sending a Packet Resource request message during a two-phase access that requests two or more uplink TBFs.
T3190: Wait for Valid Downlink Data Received from the Network
This timer is used on the mobile station side to stop waiting for the valid data from the network side either following the initial Packet Downlink Assignment/MBMS Assignment or after some previous downlink RLC data block.
T3192: Wait for release of the TBF after reception of the final block
This timer is used on the mobile station side when the mobile station has received all of the RLC data blocks. When timer T3192 expires the mobile station shall release the resources associated with the TBF (e.g. TFI) and begin to monitor its paging channel, except if the mobile station is in EC operation with timer T3168 running.
T3194: Minimum time between stolen radio blocks for a given radio bearer.
Following stealing a radio block for a given radio bearer, the mobile station shall expect to have this radio bearer scheduled via its USF within an interval defined by four times the duration of T3194, else link failure is reported to RRC.
T3196 Wait for Packet CS COMMAND message.
This timer is used on the mobile station side to define when to stop waiting for the Packet CS COMMAND message. At expiry of timer T3196, the mobile station shall release all ongoing TBFs and start RR connection establishment as specified in 3GPP TS 44.018.
T3200 RLC/MAC control message reassembly guard
T3200 is used by the mobile station to control when it will discard segments of a partially received RLC/MAC control message. The mobile station shall have one instance of timer T3200 for each segmented RLC/MAC control message that the mobile station is capable of receiving in parallel.
T3204: Wait for Packet Uplink Assignment after the first attempt to send a Packet Channel Request during a packet access procedure. The Packet Channel Request was attempted indicating ‘Single block without TBF establishment’ and the purpose of the packet access procedure is to send a PACKET PAUSE message.
This timer is used by a mobile station with non-GSM capabilities to stop waiting for a PACKET UPLINK ASSIGNMENT message. At expiry of timer T3204, the Packet Pause procedure (sub-clause 7.6) is aborted.
T3206 Wait for sending of the PACKET CELL CHANGE NOTIFICATION message after entering CCN mode
This timer is used to control that the MS in CCN mode is not prevented to proceed with a cell re-selection for too long if it cannot send the PACKET CELL CHANGE NOTIFICATION message (e.g. T3192 is running and there is no uplink block granted to the MS).
T3208 Maximum delay of the MS initiated cell re-selection after the point in time when the MS has sent the PACKET CELL CHANGE NOTIFICATION message in CCN mode.
T3208 is used by the mobile station in CCN mode to decide when to stop waiting for network assistance for the cell reselection (see sub-clause 5.5.1.1a).
T3210 Wait for retransmitting the PACKET CELL CHANGE NOTIFICATION message after having sent the PACKET CELL CHANGE NOTIFICATION message for the first time (see sub-clause 5.5.1.1a).
This timer is used to request the mobile station to retransmit the PACKET CELL CHANGE NOTIFICATION message in the case it has not received any PACKET NEIGHBOUR CELL DATA message nor PACKET CELL CHANGE CONTINUE message nor PACKET CELL CHANGE ORDER message nor the PS HANDOVER COMMAND message in response to the sending of the PACKET CELL CHANGE NOTIFICATION message sent for the first time. It can reduce the cell re-selection delay implied by entering CCN mode in case the first PACKET CELL CHANGE NOTIFICATION message was not received by the network.
T3214 Wait for MBMS ASSIGNMENT message.
This timer is used on the mobile station side to define when to stop waiting for the MBMS ASSIGNMENT message. At expiry of timer T3214, a mobile station in packet idle mode or MAC-Idle state shall return to DRX mode. A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode.
T3216 Wait for the PACKET PHYSICAL INFORMATION message.
This timer is used on the mobile station side to define when to stop waiting for the PACKET PHYSICAL INFORMATION message in the non-synchronized cell PS handover case (see sub-clause 8.10.4.4.4). At expiry of timer T3216, the mobile station shall abort the PS handover procedure, return to the old cell, send a Packet Cell Change Failure message using the first available uplink transmission opportunity (if PS handover from A/Gb mode was attempted) and attempt to continue all TBFs/RABs that were ongoing prior to the reception of the PS HANDOVER COMMAND message/Handover from UTRAN Command message or MobilityFromEUTRACommand message (see sub-clause 8.10.5).
T3218 Wait for the first USF for any uplink TBF assigned to the MS after receiving the PS HANDOVER COMMAND message or Handover from UTRAN Command message or MobilityFromEUTRACommand message.
This timer is used on the mobile station side to define when to stop waiting for a USF of any uplink TBF assigned to the MS in the new cell.
At expiry of timer T3218, the mobile station shall abort the PS handover procedure, return to the old cell, send a Packet Cell Change Failure message using the first available uplink transmission opportunity (if PS handover from A/Gb mode was attempted) and attempt to continue all TBFs or RABs that were ongoing prior to the reception of the PS HANDOVER COMMAND message or Handover from UTRAN Command message or MobilityFromEUTRACommand message (see sub-clause 8.10.5).
T3220 Wait for PACKET PAGING REQUEST message.
This timer is used to ensure that the mobile station stops waiting for a PACKET PAGING REQUEST message containing an MBMS notification part. At expiry of the T3220, the mobile station in packet idle mode or MAC-Idle state shall return to DRX mode unless it is already engaged in any other MBMS session and remaining in broadcast/multicast receive mode.
T3222 An instance of the timer may be used during the notification of MBMS for mobile stations in packet transfer mode or in dual transfer mode. An instance of this timer may be started at the receipt of a PACKET MBMS ANNOUNCEMENT message when in packet transfer mode or in dual transfer mode.
The instance of this timer is stopped either when the mobile station enters packet idle mode, if the PACKET MBMS ANNOUNCEMENT message included the Estimated Session Duration, or when the mobile station enters packet idle mode and completes the Transfer non-DRX mode period, if the PACKET MBMS ANNOUNCEMENT message included the Restriction Timer.
At expiry of an instance of this timer, the mobile station discards the MBMS related information stored upon receipt of the corresponding PACKET MBMS ANNOUNCEMENT message.
T3226 The timer is used to determine how long the mobile station may wait, after the last allocation in a fixed uplink allocation received in an uplink EC TBF, before starting to monitor the DL EC-PACCH for an RLC/MAC control message.
At expiry the mobile station shall start timer T3228 and start monitoring the DL EC-PACCH for reception of an RLC/MAC control message.
T3228 The timer is used to control the time period during which the mobile station shall monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, following a fixed uplink allocation.
When the mobile station receives an EC PACKET UPLINK ACK/NACK 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.
At expiry 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 timer value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH. The next higher DL Coverage Class shall then be used, if such exists.
T3238 The timer is used to control the length of the period where the mobile station monitors the EC-PACCH of its uplink EC TBF after reception of the EC PACKET UPLINK ACK/NACK message with Final Ack Indicator set to ‘1’, with an indication that the mobile station shall continue monitoring the EC-PACCH. The uplink EC TBF is then kept during this time interval.
It is stopped at reception of an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station, or at reception of another RLC/MAC control message triggering the release of the uplink TBF.
At expiry the mobile station shall leave the uplink TBF and return to packet idle mode.
T3248 The timer is used to control the time period during which the mobile station shall monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, following a fixed uplink allocation. The next higher Coverage Class compared to the assigned DL CC shall then be used, if such exists. The timer is started at expiry of timer T3228.
When the mobile station receives an EC PACKET UPLINK ACK/NACK 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 T3248.
At expiry the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed.
T3290 Wait for Downlink Data identified with the assigned MS_ID during an MBMS radio bearer.
This timer is used on the mobile station side to stop answering to polling during an MBMS radio bearer.
T3290 has the same value as the one specified for T3190.
T3230 The timer is used to control the validity period of the individual priorities. It is started on receipt of the individual priorities included in the PACKET CELL CHANGE ORDER or PACKET MEASUREMENT ORDER message for cell reselection or on inter-RAT reselection to GERAN if the corresponding timer in the source RAT (i.e, T320 in E-UTRA, T322 in UTRA) was running when reselection occurred.
When one of the conditions specified in subclause 5.5.1.1c.3 is met, the MS shall stop T3230 and delete the corresponding individual priorities.
At expiry the mobile station shall delete the corresponding individual priorities.
T3232 The timer is used to control the length of the non-DRX mode period in which the mobile station is acquiring an ETWS Primary Notification message. It is started when receiving a PACKET PAGING REQUEST message on the PPCH carrying a segment of an ETWS Primary Notification message.
It is stopped at reception of the complete ETWS Primary Notification message or upon initiating cell reselection or connection establishment procedures.
At expiry the mobile station shall enter DRX mode.
13.2 Timers on the network side
For each timer, it is shown whether one timer instance is needed per MS, per TBF/MBMS radio bearer, per MS_ID or per RLC/MAC control message.
For EC-GSM-IoT, where blind physical layer transmissions are used, if a timer expires during an ongoing transmission opportunity, that transmission opportunity shall be considered as having occurred prior to the expiry of the timer.
Table 13.2.1: Specification of timers used in GPRS on the Network side
timer |
started |
stopped |
action at expiry |
typical value |
T3169 (per TBF) |
If counter N3101 = N3101_MAX, or if counter N3103 = N3103_MAX an instance of T3169 is started for this TBF |
None |
The network releases USF and TFI resources. |
5 s |
T3191 (per TBF/ per RLC (NOTE 1)) (per MBMS radio bearer) |
When the last RLC data block is sent with the FBI bit set to ‘1’ an instance of T3191 is started for this TBF When the PACKET TBF RELEASE message is sent |
When the final (EC) PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT is received Restarted at the transmission of an RLC data block with the FBI bit set to ‘1’. Restarted at the transmission of a further PACKET TBF RELEASE message |
The network releases TFI resources. The network releases all the TFIs related to the MBMS radio bearer |
5 s |
T3193 (per TBF/ per RLC (NOTE 1)) |
When the final (EC) PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT is received an instance of T3193 is started for this TBF |
Stopped when the network establishes a new downlink TBF using the same TFI value. For an EC TBF, stopped when the network establishes a new downlink EC TBF or a new uplink EC TBF. Restarted at the reception of the final (EC) PACKET DOWNLINK ACK/NACK or PACKET CONTROL ACKNOWLEDGEMENT. |
The network releases TFI resources. |
Greater than T3192 |
T3195 (per TBF) (per MS_ID on an MBMS radio bearer) |
If counter N3105 = N3105_MAX an instance of T3195 is started for this TBF If counter N3105 = N3105_MBMS_MAX an instance of T3195 is started |
None |
The network may reuse the TFI resources. The network may reuse the MS_ID on the corresponding MBMS radio bearer. |
5 s |
T3197 |
When PACKET CS RELEASE INDICATION message is transmitted. |
On receipt of PACKET SI STATUS or PACKET PSI STATUS message indicating that the mobile station has received system information to maintain its radio resources after the release of the RR connection. |
The network shall send CHANNEL RELEASE message (specified in 3GPP TS 44.018) to the mobile station. |
2 s |
T3199 (per MS_ID on an MBMS radio bearer) |
If counter N3109 = N3109_MAX an instance of T3199 is started for this MS_ID. At the point in time denoted by the Current MS_ID Expiry Time while no PACKET CONTROL ACKNOWLEDGEMENT message has been received, an instance of T3199 is started for this MS_ID. |
None |
The network releases the MS_ID on the corresponding MBMS radio bearer. |
5 s |
T3227 |
After the last allocated RLC data block of a fixed uplink allocation. In case more than one blind physical layer transmission is used on the uplink EC-PDTCH, the timer shall be started after the last of those transmissions. |
None |
Timer T3229 is started and the network may transmit DL RLC/MAC control messages to the mobile station on the EC-PACCH. |
Same as T3226 |
T3229 |
At expiry of timer T3227. |
On receipt of uplink data on the resources that are part of the fixed uplink allocation, which were allocated in an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message sent to the mobile station while timer T3229 was running. |
If timer T3249 is not used, i.e. it has the value = 0, the network may release the TBF and reuse the TFI resource if no uplink data is received in fixed uplink allocations, which were allocated in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages sent to the mobile station before expiry of timer T3229. If timer T3249 is used, i.e. it has a value > 0, the network shall start timer T3249 and use the next higher CC, if such exists, on the DL EC-PACCH, as long as T3249 is running. |
Same as T3228 |
T3237 |
The timer shall be (re)started at transmission of an EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to ‘1’ and indicating that the mobile station shall continue monitoring the EC-PACCH |
None |
The network may release the TBF and reuse the TFI resource. |
6 s |
T3249 |
At expiry of timer T3229. |
On receipt of uplink data on the resources that are part of the fixed uplink allocation, which were allocated in an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message sent to the mobile station while timer T3249 (or preceding T3229) was running. |
The network may release the TBF and reuse the TFI resource if no uplink data is received in fixed uplink allocations, which were allocated in EC PACKET UPLINK ACK/NACK or EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION messages sent to the mobile station before expiry of timer T3249 (or preceding T3229). |
Same as T3248 |
NOTE 1: Timer per RLC entity if EMST is used. |
T3169: Wait for Reuse of USF and TFI(s) after the mobile station uplink assignment for this TBF is invalid
This timer is used on the network side to define when the current uplink assignment for this TBF is surely invalid on the mobile station side so that the assigned USF(s) and TFI can be reused on the uplink. During that period the corresponding USF(s) is not broadcast.
Its value is network dependent. The value of T3169 should be greater than T3180, T3182 and (for exclusive allocation) T3184.
T3191: Wait for reuse of TFI(s) after sending of the last RLC Data Block on this TBF. Wait for reuse of TFI(s) after sending the PACKET TBF RELEASE for an MBMS radio bearer.
This timer is used on the network side to define when the current assignment for this TBF/MBMS is surely invalid on the mobile station side so that the TFI(s) can be reused.
Its value is network dependent.
T3193: Wait for reuse of TFI(s) after reception of the final (EC) PACKET DOWNLINK ACK/NACK from the mobile station for this TBF.
This timer is used on the network side to define when timer T3192 on the mobile station side has surely expired so that the TFI can be reused.
Its value is network dependent.
T3195: Wait for reuse of TFI(s) when there is no response from the MS (radio failure or cell change) for this TBF/MBMS radio bearer.
This timer is used on the network side to define when the current assignment for this TBF/MS_ID on an MBMS radio bearer is surely invalid on the mobile station side so that the TFI can be reused.
Its value is network dependent.
T3197: Wait for the indication from the mobile station that it has received needed system information messages.
This timer is used on the network side to delay the release of RR connection release in order to maintain radio resources before the mobile station has indicated the receipt of system information messages specified in sub-clause 5.5.1.2 or 5.5.1.3.
T3199: Wait for reuse of MS_ID on an MBMS radio bearer.
This timer is used on the network side to define for a given MBMS radio bearer when a(n) (re)assigned MS_ID is surely invalid on the mobile station side so that this MS_ID can be reused. During that period the corresponding MS_ID is not used.
Its value is network dependent.
T3227: Wait for mobile station to be reachable on the DL EC-PACCH.
This timer is used on the network side to determine when the mobile station can be reached on the DL EC-PACCH following a fixed uplink allocation. The mobile station is not reachable while the timer is running. When the timer expires, timer T3229 is started and the network may transmit RLC/MAC control messages to the mobile station on the DL EC-PACCH.
Its value is network dependent.
T3229: This timer is used on the network side to determine how long the mobile station is reachable on the DL EC-PACCH following a fixed uplink allocation and the corresponding expiry of timer T3227. When the timer expires, the mobile station is no longer reachable on the DL EC-PACCH based on the corresponding fixed uplink allocation, unless timer T3249 is used, i.e. it has a timer value > 0. At transmission of an EC PACKET UPLINK ACK/NACK or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message, containing a new fixed uplink allocation, to the mobile station while timer T3229 is running, timers T3227 and T3229 will be started following that fixed uplink allocation.
Its value is network dependent.
T3237: Wait for reuse of the TFI for the uplink EC TBF.
This timer is used on the network side to control the length of the period where the mobile station monitors the EC-PACCH of the uplink EC TBF after transmission of the EC PACKET UPLINK ACK/NACK message with Final Ack Indicator set to ‘1’ and with an indication that the mobile station shall continue monitoring the EC-PACCH. The uplink EC TBF shall be kept during this time interval.
Its value is network dependent.
T3249: This timer is used on the network side to determine how long the mobile station is reachable on the DL EC-PACCH after expiry of timer T3229. The mobile station is then reachable using the next higher DL Coverage Class, compared to the assigned one, if such exists. When the timer expires, the mobile station is no longer reachable on the DL EC-PACCH based on the corresponding fixed uplink allocation.
Its value is network dependent.
13.3 Counters on the Mobile Station side
N3102 At each cell reselection the mobile station shall set the counter N3102 to the value defined by the optional broadcast parameter PAN_MAX. Whenever the mobile station receives a Packet Ack/Nack that allows the advancement of V(S), the mobile station shall increment N3102 by the broadcast value PAN_INC, however N3102 shall never exceed the value PAN_MAX. Each time T3182 expires the mobile station shall decrement N3102 by the broadcast value PAN_DEC. When N3102 £ 0 is reached, the mobile station shall perform an abnormal release with cell re-selection.
N3104 When the mobile station sends the first RLC/MAC block the counter N3104 shall be initialized to 1. For each new RLC/MAC block the mobile station sends it shall increment N3104 by 1 until the first correct PACKET UPLINK ACK/NACK message is received. Then N3104 shall not be further incremented. If the N3104 counter is equal to N3104_MAX and no correct PACKET UPLINK ACK/NACK message has been received, the contention resolution fails and the mobile station behaves as specified in sub-clause 7.1.2.3.
N3104_MAX shall have the value:
N3104_MAX = 3 * (BS_CV_MAX + 3) * number of uplink timeslots assigned.
N3106 N3106 is used in Iu mode on the mobile station side to detect link failures that may occur for a given uplink RLC entity and shall be reported to the RRC layer. It is incremented each time a response to a given request is not received before a specified response time. It is reset upon reception of a response within the response time requirements. If the counter N3106 is equal to N3106max, a link failure has occurred that shall be reported to the RRC layer. There is one N3106 instance per uplink RLC entity in TCH or DCCH TBF mode.
N3106max shall have the value: 5.
13.4 Counters on the Network side
N3101: When the network after setting USF for a given TBF, receives a valid data block of this TBF from the mobile station in a block assigned for this USF, it will reset counter N3101. If PS Handover is not ongoing, the network will increment counter N3101 for each USF for which no data is received for this TBF. N3101max shall be greater than 8. If N3101 = N3101max, the network shall stop the scheduling of RLC/MAC blocks from the mobile station for this USF and start timer T3169.
During extended uplink TBF mode, counter N3101 shall not be incremented if the network does not require a mobile station to send PACKET UPLINK DUMMY CONTROL BLOCK messages when there is no other RLC/MAC block ready to send for this TBF in uplink radio blocks allocated by the network (see sub-clause 9.3.1b.2).
The use of N3101 during PS Handover is implementation specific.
N3103: N3103 is reset when transmitting the final (EC) PACKET UPLINK ACK/NACK message within a TBF (final ack indicator set to 1). If the network does not receive the (EC) PACKET CONTROL ACKNOWLEDGEMENT message in the scheduled block for this TBF, it shall increment counter N3103 and retransmit the (EC) PACKET UPLINK ACK/NACK message. If counter N3103 exceeds its limit, the network shall start timer T3169.
N3105: When the network after sending a RRBP field in the downlink RLC data block or in Iu mode also RLC/MAC control block, receives a valid RLC/MAC control message from the mobile station, it will reset counter N3105. The network will increment counter N3105 for each allocated data block for which no RLC/MAC control message is received for this TBF. The value of N3105max is network dependent.
During an MBMS data transfer, whenever the network receives a valid RLC/MAC control message from a mobile station identified by a given 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. The value of N3105_MBMS_MAX is network dependent
N3107 N3107 is used in Iu mode on the network side to detect link failures that may occur for a given RLC entity and that shall be reported to the RRC layer. It is incremented each time a response to a given request is not received before a specified response time. It is reset upon reception of a response within the response time requirements. If the counter N3107 is equal to N3107max, a link failure has occurred that shall be reported to the RRC layer. There is one N3107 instance per downlink RLC entity in TCH or DCCH TBF mode. The value of N3107max is network dependent.
N3109: N3109 for a given MS_ID on an MBMS radio bearer is reset when transmitting for the first time the MBMS MS_ID ASSIGNMENT message including a polling request. If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the scheduled block, it shall increment counter N3109 for that MS_ID and may retransmit the MBMS MS_ID ASSIGNMENT message. If counter N3109 = N3109_MAX, the network shall start timer T3199 for that MS_ID. The value of N3109_MAX is network dependent.
Annex A (informative):
Bibliography
1) ITU-T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
2) ITU-T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities".
3) ISO/IEC 8886: "Information technology – Open Systems Interconnection – Data link service definition".
4) ISO/IEC 10022: "Information technology – Open Systems Interconnection – Physical Service Definition".
5) ISO/IEC 10039: "Information technology – Open Systems Interconnection – Local area networks – Medium Access Control (MAC) service definition".
6) ISO/IEC 4335: "Information technology – Telecommunications and information exchange between systems – High‑level data link control (HDLC) procedures – Elements of procedures".
7) ISO/IEC 7478: "Information processing systems – Data communication – Multilink procedures".
8) ISO/IEC 7498: "Information technology – Open Systems Interconnection – Basic Reference Model".
Annex B (informative):
RLC data block encoding
B.1 Example 1
Figure B.1 provides an example of the use of the Length indicator in conjunction with the M and E bits. In the example, LLC PDU 1 continues from a previous RLC data block and ends in the RLC data block shown. LLC PDU 2 follows LLC PDU 1 and is completely contained within the RLC data block. LLC PDU 3 follows LLC PDU 2, beginning in the RLC data block shown, and continues into the next RLC data block.
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
RRBP |
S/P |
USF |
MAC header |
|||||
PR |
TFI |
FBI |
Octet 1 |
||||||
BSN |
E = 0 |
Octet 2 |
|||||||
Length indicator = 11 |
M = 1 |
E = 0 |
Octet 3 |
LLC PDU 1 |
|||||
Length indicator = 26 |
M = 1 |
E = 1 |
Octet 4 |
||||||
Octet 5 |
|||||||||
LLC PDU 1 (cont) |
. . . |
||||||||
Octet 15 |
|||||||||
Octet 16 |
|||||||||
Octet 17 |
|||||||||
LLC PDU 2 |
. . . |
LLC PDU 2 |
|||||||
Octet 41 |
|||||||||
Octet 42 |
|||||||||
Octet 43 |
|||||||||
LLC PDU 3 |
. . . |
LLC PDU 3 |
|||||||
Octet N-1 |
|||||||||
Octet N |
|||||||||
Figure B.1: Length indicator (LI) example
B.2 Example 2
Figure B.2 provides an example of the use of the Length indicator when the end of an LLC PDU would fit within an RLC data block but the addition of the length indicator octet (to indicate the LLC PDU boundary) causes the LLC PDU to extend into another RLC data block. In the example, LLC PDU 1 continues from a previous RLC data block and has 20 remaining octets. The first 19 octets are placed into RLC data block N, the Length Indicator is set to 0 (to indicate that the LLC PDU does not end within the current RLC data block), and the 20th octet is placed in RLC data block N+1.
RLC data block N |
|||||||||
bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
RRBP |
S/P |
USF |
MAC header |
|||||
PR |
TFI |
FBI |
Octet 1 |
||||||
BSN |
E = 0 |
Octet 2 |
|||||||
Length indicator = 0 |
M = 0 |
E = 1 |
Octet 3 |
||||||
Octet 4 |
|||||||||
LLC PDU 1 (cont) |
. . . |
LLC PDU 1 |
|||||||
Octet 22 |
|||||||||
RLC data block N + 1 |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
RRBP |
S/P |
USF |
MAC header |
|||||
TFI |
FBI |
Octet 1 |
|||||||
BSN |
E = 0 |
Octet 2 |
|||||||
Length indicator = 1 |
M = 1 |
E = 1 |
Octet 3 (optional) |
||||||
LLC PDU 1 (cont) |
Octet 4 |
||||||||
LLC PDU 2 |
. . . |
LLC PDU 2 |
|||||||
Octet 22 |
Figure B.2: Length indicator (LI) example
B.3 Example 3
Figure B.3 provides an example of the use of the Length indicator when the end of an LLC PDU fits precisely into an RLC data block. In the example, LLC PDU 1 continues from a previous RLC data block and ends in the RLC data block shown. LLC PDU 2 follows LLC PDU 1 and fills precisely the RLC data block shown.
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
RRBP |
S/P |
USF |
MAC header |
|||||
PR |
TFI |
FBI |
Octet 1 |
||||||
BSN |
E = 0 |
Octet 2 |
LLC PDU 1 |
||||||
Length indicator = 7 |
M = 1 |
E = 0 |
Octet 3 |
||||||
Length indicator = 11 |
M = 0 |
E = 1 |
Octet 4 |
||||||
Octet 5 |
|||||||||
LLC PDU 1 (cont) |
. . . |
||||||||
Octet 11 |
|||||||||
Octet 12 |
|||||||||
LLC PDU 2 |
. . . |
LLC PDU 2 |
|||||||
Octet 22 |
|||||||||
Figure B.3: Length indicator (LI) example
B.4 Example 4
Figure B.4 provides an example when the Length indicator is not used. As the example does not contain any LLC frame boundaries, no Length Indicator octets are needed. 20 octets is used for LLC data in each RLC data block.
RLC data block N |
|||||||||
bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
RRBP |
S/P |
USF |
MAC header |
|||||
PR |
TFI |
FBI |
Octet 1 |
||||||
BSN |
E = 1 |
Octet 2 |
|||||||
Octet 3 |
|||||||||
. |
|||||||||
LLC PDU 1 (cont) |
. . . |
LLC PDU 1 |
|||||||
Octet 22 |
|||||||||
RLC data block N + 1 |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
RRBP |
S/P |
USF |
MAC header |
|||||
TFI |
FBI |
Octet 1 |
|||||||
BSN |
E = 1 |
Octet 2 |
|||||||
Octet 3 |
LLC PDU 1 |
||||||||
LLC PDU 1 (cont) |
. . . |
||||||||
Octet 22 |
|||||||||
Figure B.4: Example when Length indicator (LI) can be omitted
B.5 Example 5
Figure B.5 provides an example when the final LLC PDU (FBI=1) of a downlink TBF fills the RLC data block precisely in which case the Length indicator can be omitted. In the example, LLC PDU 1 continues from a previous RLC data block and ends in and fills precisely the RLC data block shown.
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
RRBP |
S/P |
USF |
MAC header |
|||||
PR |
TFI |
FBI=1 |
Octet 1 |
||||||
BSN |
E = 1 |
Octet 2 |
LLC PDU 1 |
||||||
Octet 3 |
|||||||||
Octet 4 |
|||||||||
LLC PDU 1 (cont) |
. . . |
||||||||
. . . |
|||||||||
Octet 22 |
|||||||||
Figure B.5: Example when Length indicator (LI) can be omitted
B.6 Example 6
Figure B.6 provides an example when the final LLC PDU (CV=0) of an uplink TBF fills the RLC data block precisely in which case the Length indicator can be omitted. In the example, LLC PDU 1 continues from a previous RLC data block and ends in and fills precisely the RLC data block shown.
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
Countdown value = 0 |
SI |
R |
MAC header |
|||||
spare |
TFI |
TI |
Octet 1 |
||||||
BSN |
E = 1 |
Octet 2 |
LLC PDU 1 |
||||||
Octet 3 |
|||||||||
Octet 4 |
|||||||||
LLC PDU 1 (cont) |
. . . |
||||||||
. . . |
|||||||||
Octet 22 |
|||||||||
Figure B.6: Example when Length indicator (LI) can be omitted
B.7 Example 7
Figure B.7 provides an example when the Length indicator can be omitted. As the LLC PDU 1 begins in the RLC data block N and continues to the next one, no Length octet is needed.
RLC data block N |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
Countdown value |
SI |
R |
MAC header |
|||||
spare |
TFI |
TI |
Octet 1 |
||||||
BSN |
E = 1 |
Octet 2 |
|||||||
Octet 3 |
|||||||||
Octet 4 |
|||||||||
LLC PDU 1 |
. . . |
LLC PDU 1 |
|||||||
. . . |
|||||||||
Octet 22 |
|||||||||
RLC data block N+1 |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Payload Type |
Countdown value |
SI |
R |
MAC header |
|||||
spare |
TFI |
TI |
Octet 1 |
||||||
BSN |
E = 0 |
Octet 2 |
|||||||
LI=10 |
M=1 |
E=1 |
Octet 3 |
||||||
Octet 4 |
|||||||||
LLC PDU 1 (cont) |
. Octet 13 |
||||||||
LLC PDU 2 |
. . . |
LLC PDU 2 |
|||||||
Octet 22 |
|||||||||
Figure B.7: Example when Length indicator (LI) can be omitted
B.8 RLC data block delimitation for EGPRS
B.8.1 Example 1
Figure B.8 shows the first 2 RLC blocks of a TBF (Down-link). Only the last segment of a LLC PDU requires a length indicator.
1st RLC Block |
LLC PDU |
||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=0 |
E = 0 |
||||||||
Length indicator = 11 |
E = 0 |
Octet 1 |
|||||||
Length indicator = 26 |
E = 1 |
Octet 2 |
|||||||
Octet 3 |
|||||||||
LLC PDU 1 (cont) |
. . . |
LLC PDU 1 1st PDU of the TBF |
|||||||
Octet 13 |
|||||||||
Octet 14 |
|||||||||
Octet 15 |
|||||||||
LLC PDU 2 |
. . . |
LLC PDU 2 |
|||||||
Octet 39 |
|||||||||
Octet 40 |
|||||||||
Octet 41 |
|||||||||
LLC PDU 3 |
. . . |
LLC PDU 3 |
|||||||
Octet N2 |
|||||||||
2nd RLC block of the TBF |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=0 |
E = 0 |
||||||||
Length indicator = 11 |
E = 0 |
Octet 1 |
LLC PDU 3 |
||||||
Length indicator = 26 |
E = 1 |
Octet 2 |
|||||||
Octet 3 |
|||||||||
LLC PDU 3 (cont) |
. . . |
||||||||
Octet 13 |
|||||||||
Octet 14 |
|||||||||
Octet 15 |
|||||||||
LLC PDU 4 |
. . . |
LLC PDU 4 |
|||||||
Octet 39 |
|||||||||
Octet 40 |
|||||||||
Octet 41 |
|||||||||
LLC PDU 5 |
. . . |
LLC PDU 5 |
|||||||
Octet N2-1 |
|||||||||
Octet N2 |
|||||||||
Figure B.8: Example for the case when a LLC PDU stretches over more
than 2 consecutive in sequence RLC data blocks (LLC PDU 3 and LLC PDU 5).
B.8.2 Example 2
Figure B.9 shows the last 3 RLC blocks of a TBF consisting of N blocks (Downlink). When an LLC PDU fills an RLC data block precisely and adding an LI for it would push the LLC PDU into the next in sequence RLC data block, then the LLC PDU is present in this RLC data block without a corresponding length indicator. If this LLC PDU is not the last LLC PDU of the TBF, its delimitation is indicated by the first length indicator of the next in sequence RLC data block with value LI=0. In case when the LLC PDU, or the last segment of it, does not fill the RLC data block, a length indicator with value 127 is added as the last length indicator of the RLC data block.
RLC Block with BSN=N-2 (mod SNS) |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=0 |
E = 0 |
Octet 1 |
LLC PDU J+1 |
||||||
Length indicator = N2-13 |
E = 1 |
Octet 2 |
|||||||
Octet 3 |
|||||||||
LLC PDU J+1 (continue) |
. . . |
||||||||
Octet N2-11 |
|||||||||
Octet N2-10 |
|||||||||
LLC PDU J+2 |
. . . |
LLC PDU J+2 |
|||||||
Octet N2 |
RLC Block with BSN=N-1 (mod SNS) |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=0 |
E = 0 |
Octet 1 |
|||||||
Length indicator = 0 |
E = 0 |
Octet 2 |
|||||||
Length indicator= 7 |
E =0 |
Octet 3 |
|||||||
Length indicator= N2-11 |
E=1 |
Octet 4 |
|||||||
Octet 5 |
LLC PDU J+3 |
||||||||
LLC PDU J+3 |
. . . |
||||||||
Octet 11 |
|||||||||
Octet 12 |
|||||||||
LLC PDU J+4 |
. . . |
LLC PDU J+4 |
|||||||
Octet N2 |
RLC Block with BSN=N (mod SNS) |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=1 |
E=0 |
Octet 1 |
|||||||
Length indicator=6 |
E=0 |
Octet 2 |
|||||||
Length indicator=12 |
E=0 |
Octet 3 |
|||||||
Length indicator=127 |
E=1 |
Octet 4 |
|||||||
Octet 5 |
LLC PDU J+5 |
||||||||
LLC PDU J+5 |
. . . |
||||||||
Octet 10 |
|||||||||
Octet 11 |
|||||||||
LLC PDU J+6 |
. . . |
LLC PDU J+6 |
|||||||
Octet 22 |
|||||||||
Filling Octets |
|||||||||
Octet N2 |
Figure B.9: Example for the case when the LLC PDU fills exactly the RLC data block
(LLC PDU J+2 and LLC PDU J+4) and when the last LLC PDU cannot not fill
the last RLC data block(LLC PDU J+6)
B.8.3 Example 3
Figure B.10 shows a TBF of one LLC PDU which fills exactly the RLC data block (Downlink).
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=1 |
E = 1 |
Octet 1 |
|||||||
Octet 2 |
LLC PDU 1 |
||||||||
LLC PDU 1 |
. . . |
||||||||
Octet N2 |
Figure B.10: Example for the case when a LLC PDU fills the RLC data block precisely.
B.8.4 Example 4
Figure B.11 shows 2 RLC blocks of a TBF during RLC non-persistent mode of operation. When an LLC PDU ends in the previous RLC data block, a length indicator with value=126 is added in the next in sequence RLC data block to indicate the start of the next LLC PDU.
RLC Block with BSN=N (mod SNS) |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=0 |
E = 0 |
Octet 1 |
|||||||
Length indicator= 7 |
E =0 |
Octet 2 |
|||||||
Length indicator= 12 |
E =0 |
Octet 3 |
|||||||
Length indicator= 127 |
E=1 |
Octet 4 |
|||||||
Octet 5 |
|||||||||
LLC PDU J |
. . . |
LLC PDU J |
|||||||
Octet 11 |
|||||||||
Octet 12 |
|||||||||
LLC PDU J+1 |
. . . |
LLC PDU J+1 |
|||||||
Octet 23 |
|||||||||
Octet 24 |
|||||||||
Filling Octets |
|||||||||
Octet N2 |
RLC Block with BSN=N+1 (mod SNS) |
|||||||||
Bit |
|||||||||
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
FBI=0 |
E=0 |
Octet 1 |
|||||||
Length indicator=126 |
E=0 |
Octet 2 |
|||||||
Length indicator=19 |
E=0 |
Octet 3 |
|||||||
Length indicator=127 |
E=1 |
Octet 4 |
|||||||
Octet 5 |
|||||||||
LLC PDU J+2 |
. . . |
LLC PDU J+2 |
|||||||
Octet 23 |
|||||||||
Filling Octets |
|||||||||
Octet N2 |
Figure B.11: Example for the case when the LLC PDU J+1 ends in the previous RLC data block and the start of the next LLC PDU J+2 is in the next RLC data block which is indicated using LI=126 as the first LI in that RLC data block.
Annex C (informative):
Message Sequence Diagrams
The following figures illustrate message sequences for:
– one phase mobile originated access (figure C.1); and
– network originated access (figure C.2).
Figure C.1: Message Sequence Diagram for one phase packet access
Figure C.2: TBF establishment initiated by the network
Annex D (informative):
(void)
Annex E (informative):
(void)
Annex F (informative):
Examples of Countdown procedure operation
This annex presents several examples of the countdown procedure operation.
The following parameters are used in the following examples:
TBC = total number of RLC data blocks that will be transmitted in the TBF;
BSN’ = absolute block sequence number of the RLC data block, with range from 0 to (TBC – 1);
NTS = number of timeslots assigned to the uplink TBF in the assignment message, with range 1 to 8.
F.1 Example 1
In this example, shown in the first column, the total number of RLC data blocks in the TBF (TBC) is 155, the number of timeslots (NTS) is 1, and BS_CV_MAX is 15. The second column shows the same example with BS_CV_MAX = 6.
TBC |
155 |
TBC |
155 |
|||||||
NTS |
1 |
NTS |
1 |
|||||||
BS_CV_MAX |
15 |
BS_CV_MAX |
6 |
|||||||
BSN’ |
CV |
BSN’ |
CV |
|||||||
137 |
15 |
137 |
15 |
|||||||
138 |
15 |
138 |
15 |
|||||||
139 |
15 |
139 |
15 |
|||||||
140 |
14 |
140 |
15 |
|||||||
141 |
13 |
141 |
15 |
|||||||
142 |
12 |
142 |
15 |
|||||||
143 |
11 |
143 |
15 |
|||||||
144 |
10 |
144 |
15 |
|||||||
145 |
9 |
145 |
15 |
|||||||
146 |
8 |
146 |
15 |
|||||||
147 |
7 |
147 |
15 |
|||||||
148 |
6 |
148 |
6 |
|||||||
149 |
5 |
149 |
5 |
|||||||
150 |
4 |
150 |
4 |
|||||||
151 |
3 |
151 |
3 |
|||||||
152 |
2 |
152 |
2 |
|||||||
153 |
1 |
153 |
1 |
|||||||
154 |
0 |
154 |
0 |
Figure F.1: Example 1
F.2 Example 2
In this example, shown in the first column, the total number of RLC data blocks in the TBF (TBC) is 155, the number of timeslots (NTS) is 3, and BS_CV_MAX is 6. Note that the RLC data block with BSN’ = 154 arbitrarily occurs in timeslot 2. In the second column, the same example is shown with the RLC data block with BSN’ = 154 occuring in timeslot 0.
TBC 155
NTS 3
BS_CV_MAX 6
TS0 |
TS1 |
TS2 |
TS0 |
TS1 |
TS2 |
|||||||
BSN’ |
CV |
BSN’ |
CV |
BSN’ |
CV |
BSN’ |
CV |
BSN’ |
CV |
BSN’ |
CV |
|
125 |
15 |
126 |
15 |
127 |
15 |
127 |
15 |
128 |
15 |
129 |
15 |
|
128 |
15 |
129 |
15 |
130 |
15 |
130 |
15 |
131 |
15 |
132 |
15 |
|
131 |
15 |
132 |
15 |
133 |
15 |
133 |
15 |
134 |
15 |
135 |
15 |
|
134 |
15 |
135 |
15 |
136 |
6 |
136 |
6 |
137 |
6 |
138 |
6 |
|
137 |
6 |
138 |
6 |
139 |
5 |
139 |
5 |
140 |
5 |
141 |
5 |
|
140 |
5 |
141 |
5 |
142 |
4 |
142 |
4 |
143 |
4 |
144 |
4 |
|
143 |
4 |
144 |
4 |
145 |
3 |
145 |
3 |
146 |
3 |
147 |
3 |
|
146 |
3 |
147 |
3 |
148 |
2 |
148 |
2 |
149 |
2 |
150 |
2 |
|
149 |
2 |
150 |
2 |
151 |
1 |
151 |
1 |
152 |
1 |
153 |
1 |
|
152 |
1 |
153 |
1 |
154 |
0 |
154 |
0 |
Figure F.2: Example 2
F.3 Example 3
In this example, the channel coding scheme is changed at BSN’ = 149, resulting in more RLC data blocks being required to complete the TBF. The value of TBC is changed from 155 to 165 at BSN’ = 149.
TBC 155
NTS 3
BS_CV_MAX 6
TS0 |
TS1 |
TS2 |
|||
BSN’ |
CV |
BSN’ |
CV |
BSN’ |
CV |
125 |
15 |
126 |
15 |
127 |
15 |
128 |
15 |
129 |
15 |
130 |
15 |
131 |
15 |
132 |
15 |
133 |
15 |
134 |
15 |
135 |
15 |
136 |
6 |
137 |
6 |
138 |
6 |
139 |
5 |
140 |
5 |
141 |
5 |
142 |
4 |
143 |
4 |
144 |
4 |
145 |
3 |
146 |
3 |
147 |
3 |
148 |
2 |
149 |
5 |
150 |
5 |
151 |
5 |
152 |
4 |
153 |
4 |
154 |
4 |
155 |
3 |
156 |
3 |
157 |
3 |
158 |
2 |
159 |
2 |
160 |
2 |
161 |
1 |
162 |
1 |
163 |
1 |
164 |
0 |
Figure F.3: Example 3
Annex G (informative):
Handling of erroneous protocol data, examples
Procedures for the handling of erroneous protocol data are defined in sub-clause 11.1. These procedures define error labels for the treatment of syntactical errors in a received message.
G.1 Application of error labels
An RLC/MAC control message description could have an error label included, as shown in the examples below.
< Packet XXX message content > ::= < FIELD_1 : bit (3) > < FIELD_2 : bit (16) > … < padding bits > ! < Ignore : bit (*) = < no string > > ; |
In the case of a complete message, the contents of the received syntactically incorrect message can be ignored.
Or
< PRECEDING_FIELD : bit (3) > … { 00 < FIELD_1 : bit (10) > | 01 < FIELD_2 : bit (10) > ! < Ignore : bit (2+10) = < no string > > } … < FOLLOWING_FIELD : bit (8) > |
The syntactically incorrect description within the { } brackets can be ignored, the correctly received descriptions preceding and following the { } brackets shall be accepted.
Or
< Structure 1 struct > ::= < FIELD_1: bit (3) > { 1 < FIELD_2 : bit (8) > } ** 0 … ! < Ignore : bit (*) = < no string > > ; |
The above description indicates that the syntactically incorrect structure can be ignored. (Note: When this structure is included in the description of a message, any description following the structure must allow truncation.)
G.2 Application of the ‘Message escape’ error label
The ‘Message escape’ branch protects the comprehension of the description following bit ‘0’, as shown in the example below.
< Packet YYY message content > ::= — Protocol version 1 < FIELD_1 : bit (3) > { 0 < FIELD_2 : bit (16) > … < padding bits > ! < Message escape : 1 bit (*) = <no string> > } ; |
The comprehension of ‘FIELD_2’ is required. If the receiver detects bit ‘1’, the ‘Message escape’ branch is called and the remaining part of the message can be ignored.
The ‘Message escape’ branch may be used to introduce an new alternative coding of the message in a later version of the protocol.
< Packet YYY message content > ::= — Protocol version 2 < FIELD_1 : bit (3) > { 0 < FIELD_2 : bit (16) > … < padding bits > | 1 — New code option, replacing old ‘Message escape’: { 00 < FIELD_3 : bit (12) > … < padding bits > ! < Message escape : { 01 | 10 | 11 } bit (*) = <no string> > } } ; |
An alternative coding, including ‘FIELD_3’, is introduced following ‘bit 1’ in the former ‘Message escape’ branch. A new ‘Message escape’ is defined, this time using to control bits to allow future modification.
A receiver implemented according to the original syntax will not accept the new coding. The original ‘Message escape’ branch will be called and the remaining part of the message, including ‘FIELD_3’ is ignored. The content of ‘FIELD_1’ (e.g. information to identify the receiver) is accepted and can be used to determine appropriate condition handling.
G.3 Application of truncated concatenation including ‘padding bits’
The truncated concatenation may include ‘padding bits’ at the end of a message. In that case, the resulting concatenation shall fit exactly with the received message length, otherwise the message is syntactically incorrect.
The construction is useful, e.g. when a message ends with a sequence of optional components, where the transmitter may need to truncate tailing bits ‘0’, indicating optional components not included in the message.
< Packet ZZZ message content > ::= … { { 0 | 1 < Optional component 1 > } { 0 | 1 < Optional component 2 > } … { 0 | 1 < Optional component N > } < padding bits > } // ; |
If the optional components from k to N are not needed in the message, the transmitter may use the full message length for the components up to optional component k – 1. The receiver accepts this message and assumes that the choice bits for optional components from k to N are all set to zero (i.e. these components are not present).
However, if the receiver detects a syntactical error within one optional component which is indicated as present in the message, that results in a truncated concatenation which does not fit with the received message length. In this case, the receiver shall not accept the message as being syntactically correct.
An error label may be provided within a truncated concatenation to allow the receiver to accept part of a concatenation in case of a syntactical error within it. This is useful for recurring components at the end of a message.
< Packet TTT message content > ::= … { { 1 { < Recurring component > ! < Ignore : bit (*) = < no string > > } } ** 0 < padding bits > } // ; |
If one of the recurring components is syntactically incorrect, the error branch is called. The error branch expands to the end of the message. The tail bit ‘0’, terminating the recursion, and the ‘spare padding’ are truncated. The receiver accepts any syntactically correct instance of the recurring component preceding the syntactically incorrect one in the message.
G.4 Message extension using ‘padding bits’
The bit ‘0’ in the first bit position of the ‘padding bits’, see sub-clause 11, may be altered into a bit ‘1’ in future versions of the present document, in order to indicate an extension of the message content. When a message is received with bit ‘1’ in this position, a receiver implemented according to the current version of the present document shall ignore the remaining part of the message.
The example show how a message can be extended, relying on the fact that the ‘padding bits’ are defined with bit ‘0’ in the first bit position.
< Packet UUU message content > ::= — Current version of the present document < contents defined in current version > < padding bits > ; |
The presence of the extension of the message content is indicated by bit ‘1’. The transmitter shall send a bit ‘1’ in this position if any content is defined for the remaining part of the message. If a bit ‘0’ is received in this position by a receiver in the new version, it shall ignore the remaining part of the message.
< Packet UUU message content > ::= — Future version of the present document < contents defined in current version > { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Bit ‘1’ sent by transmitter in new version < contents defined in a future version > < padding bits > } ; — New ‘padding bits’ allows further extension |
G.5 Message extension using the Extension Bits IE
The Extension Bits IE defined in sub-clause 12.26 may be used in some messages or information elements as a placeholder for future extension when an extension at the end of the message is less suitable. The Extension Bits IE is usually included as an optional or conditional information element. When included, it provides a length indication and a corresponding set of ‘spare bits’, which may be used in future versions of the protocol to carry an extension of the message contents.
When this extension mechanism is applied, the original Extension Bits IE shall be removed from the message and replaced by a new information element or a new construction, carrying an extension by up to 64 bits of the message contents. An example is given below.
< Packet VVV message content > ::= — Current (original) version of the present document … { 0 | 1 < Extension Bits : Extension Bits IE > } — sub-clause 12.26 … < padding bits > ; |
The Extension Bits IE is replaced by a new construction named ‘VVV Extension Info’. The new construction includes extensions introduced in Rel-M and Rel-N. In order to enable backward compatibility, truncation of the extension information may occur between released versions of the protocol. The receiver shall assume the value zero of any truncated bits. In order to enable forward compatibility, additional ‘spare bits’ may occur after the defined extensions.
< Packet VVV message content > ::= — Future version of the present document; extensions in Rel-M and Rel-N … { 0 | 1 < VVV Extension length : bit (6) > < bit (val(VVV Extension length) + 1) & { < VVV Extension Info > ! { bit** = <no string> }} > } … < padding bits > ; |
< VVV Extension Info > ::= { { — Rel-M extension < Extension in Rel-M > } { — Rel-N extension < Extension in Rel-N > } < spare bit >** } // ; — Truncation may occur between released versions of the protocol — The receiver shall assume the value zero of any truncated bits |
Annex H (informative):
(void)
Annex I (informative):
EGPRS RLC Window Sizes
Although for each multislot allocation, the selected window size could preferably be the maximum, a smaller window size may be selected in order to optimize e.g. the number of (multislot) users and network memory consumption.
However, for each MS, in order to meet a performance which corresponds to the number of timeslots assigned to this MS, the selected window size shall not be smaller than a minimum window size for this particular multislot allocation.
For each network, the round-trip delay has a direct implication on the performance, hence on the definition of the minimum window sizes. Consequently, no generic minimum window sizes are suggested. However, for information, the table below lists the window size ranges recommended with a round-trip delay of about 120 ms.
For a mobile station in DLMC configuration the downlink window size is the same as the supported buffer size (see Table 9.1.9.3.2) whereas uplink window sizes shall still be managed as per EGPRS TBF mode without a DLMC configuration (see sub-clause 9.1.9.3).
Window size |
Coding |
Timeslots assigned (Multislot capability) |
|||||||
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8-16 |
||
64 |
00000 |
Min |
|||||||
96 |
00001 |
Min |
|||||||
128 |
00010 |
||||||||
160 |
00011 |
Min |
Min |
||||||
192 |
00100 |
Max |
|||||||
224 |
00101 |
Min |
|||||||
256 |
00110 |
Max |
|||||||
288 |
00111 |
||||||||
320 |
01000 |
Min |
|||||||
352 |
01001 |
Min |
|||||||
384 |
01010 |
Max |
|||||||
416 |
01011 |
||||||||
448 |
01100 |
||||||||
480 |
01101 |
||||||||
512 |
01110 |
Max |
Min |
||||||
544 |
01111 |
||||||||
576 |
10000 |
||||||||
608 |
10001 |
||||||||
640 |
10010 |
Max |
|||||||
672 |
10011 |
||||||||
704 |
10100 |
||||||||
736 |
10101 |
||||||||
768 |
10110 |
Max |
|||||||
800 |
10111 |
||||||||
832 |
11000 |
||||||||
864 |
11001 |
||||||||
896 |
11010 |
Max |
|||||||
928 |
11011 |
||||||||
960 |
11100 |
||||||||
992 |
11101 |
||||||||
1024 |
11110 |
Max |
|||||||
Reserved |
11111 |
x |
X |
x |
x |
x |
x |
x |
X |
Annex J (informative):
An example of MCS-8 retransmission
This example shows the radio blocks of an MCS-8 RLC data block retransmitted using MCS-6 (padding) and MCS-3 (padding).
The following hypothesis are used:
– Uplink block;
– The MCS-8 RLC data block contains three LLC PDU: last part of LLC1 (last 40 octets), the whole LLC2 (length 60 octets) and the first part of LLC3 (first 34 octets);
– No TLLI nor PFI is present.
J.1 Original MCS-8 RLC data block
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Octet |
TFI |
Countdown Value |
SI |
R |
1 (header) |
||||
BSN1 |
TFI |
2 (header) |
||||||
BSN 2 |
BSN 1 |
3 (header) |
||||||
BSN2 |
4 (header) |
|||||||
Spare |
PI |
RSB |
CPS |
5 (header) |
||||
Spare |
(See note |
|||||||
TI |
E |
below) |
||||||
Length indicator = 40 |
E |
1 (RLC data 1) |
||||||
LLC1 (octet 1) |
2 (RLC data 1) |
|||||||
LLC1 (octet 2) |
3 (RLC data 1) |
|||||||
: : |
: |
|||||||
LLC1 (octet 39) |
40 (RLC data 1) |
|||||||
LLC1 (octet 40) |
41 (RLC data 1) |
|||||||
LLC2 (octet 1) |
42 (RLC data 1) |
|||||||
LLC2 (octet 2) |
43 (RLC data 1) |
|||||||
: : |
: |
|||||||
LLC2 (octet 26) |
67 (RLC data 1) |
|||||||
LLC2 (octet 27) |
68 (RLC data 1) |
|||||||
TI |
E |
(See note below) |
||||||
Length indicator = 33 |
E |
1 (RLC data 2) |
||||||
LLC2 (octet 28) |
2 (RLC data 2) |
|||||||
LLC2 (octet 29) |
3 (RLC data 2) |
|||||||
: : |
: |
|||||||
LLC2 (octet 59) |
33 (RLC data 2) |
|||||||
LLC2 (octet 60) |
34 (RLC data 2) |
|||||||
LLC3 (octet 1) |
35 (RLC data 2) |
|||||||
LLC3 (octet 2) |
36 (RLC data 2) |
|||||||
: : |
: |
|||||||
LLC3 (octet 33) |
67 (RLC data 2) |
|||||||
LLC3 (octet 34) |
68 (RLC data 2) |
NOTE: At this row, only a few bits are sent (not a full octet).
J.2 Retransmission in two MCS-6 RLC data blocks
When this RLC data block is repeated using MCS-6 (padding), the two radio blocks have the following format:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Octet |
TFI |
Countdown value |
SI |
R |
1 (header) |
||||
BSN 1 |
TFI |
2 (header) |
||||||
CPS |
BSN 1 |
3 (header) |
||||||
Spare |
PI |
RSB |
CPS |
4 (header) |
||||
Spare |
(See note below) |
|||||||
Padding |
1 (RLC data) |
|||||||
: : |
: |
|||||||
Padding |
6 (RLC data) |
|||||||
TI |
E |
(See note below) |
||||||
Length indicator = 40 |
E |
7 (RLC data) |
||||||
LLC1 (octet 1) |
8 (RLC data) |
|||||||
LLC1 (octet 2) |
9 (RLC data) |
|||||||
: : |
: |
|||||||
LLC1 (octet 39) |
46 (RLC data) |
|||||||
LLC1 (octet 40) |
47 (RLC data) |
|||||||
LLC2 (octet 1) |
48 (RLC data) |
|||||||
LLC2 (octet 2) |
49 (RLC data) |
|||||||
: : |
: |
|||||||
LLC2 (octet 26) |
73 (RLC data) |
|||||||
LLC2 (octet 27) |
74 (RLC data) |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Octet |
TFI |
Countdown value |
SI |
R |
1 (header) |
||||
BSN 1 |
TFI |
2 (header) |
||||||
CPS |
BSN 1 |
3 (header) |
||||||
Spare |
PI |
RSB |
CPS |
4 (header) |
||||
Spare |
(See note below) |
|||||||
Padding |
1 (RLC data) |
|||||||
: : |
: |
|||||||
Padding |
6 (RLC data) |
|||||||
TI |
E |
(See note below) |
||||||
Length indicator = 33 |
E |
7 (RLC data) |
||||||
LLC2 (octet 28) |
8 (RLC data) |
|||||||
LLC2 (octet 29) |
9 (RLC data) |
|||||||
: : |
: |
|||||||
LLC2 (octet 59) |
39 (RLC data) |
|||||||
LLC2 (octet 60) |
40 (RLC data) |
|||||||
LLC3 (octet 1) |
41 (RLC data) |
|||||||
LLC3 (octet 2) |
42 (RLC data) |
|||||||
: : |
: |
|||||||
LLC3 (octet 33) |
73 (RLC data) |
|||||||
LLC3 (octet 34) |
74 (RLC data) |
NOTE: At this row, only a few bits are sent (not a full octet).
J.3 Retransmission in four MCS-3 RLC data blocks
When the original RLC data block is repeated using MCS-3, the four radio blocks have the following format:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Octet |
TFI |
Countdown value |
SI |
R |
1 (header) |
||||
BSN 1 |
TFI |
2 (header) |
||||||
CPS |
BSN 1 |
3 (header) |
||||||
Spare |
PI |
RSB |
SPB |
CPS |
(See note 1 below) |
|||
Padding |
1 (RLC data) |
|||||||
: : |
: |
|||||||
Padding |
6 (RLC data) |
|||||||
TI |
E |
(See note 1 below) |
||||||
Length indicator = 40 |
E |
7 (RLC data) |
||||||
LLC1 (octet 1) |
8 (RLC data) |
|||||||
LLC1 (octet 2) |
9 (RLC data) |
|||||||
: : |
: |
|||||||
LLC1 (octet 29) |
36 (RLC data) |
|||||||
LLC1 (octet 30) |
37 (RLC data) |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Octet |
TFI |
Countdown value |
SI |
R |
1 (header) |
||||
BSN 1 |
TFI |
2 (header) |
||||||
CPS |
BSN 1 |
3 (header) |
||||||
Spare |
PI |
RSB |
SPB |
CPS |
(See note 1 below) |
|||
TI |
E |
(See note 2 below) |
||||||
LLC1 (octet 31) |
1 (RLC data) |
|||||||
LLC1 (octet 32) |
2 (RLC data) |
|||||||
: : |
: |
|||||||
LLC1 (octet 39) |
9 (RLC data) |
|||||||
LLC1 (octet 40) |
10 (RLC data) |
|||||||
LLC2 (octet 1) |
11 (RLC data) |
|||||||
LLC2 (octet 2) |
12 (RLC data) |
|||||||
: : |
: |
|||||||
LLC2 (octet 26) |
36 (RLC data) |
|||||||
LLC2 (octet 27) |
37 (RLC data) |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Octet |
TFI |
Countdown value |
SI |
R |
1 (header) |
||||
BSN 1 |
TFI |
2 (header) |
||||||
CPS |
BSN 1 |
3 (header) |
||||||
Spare |
PI |
RSB |
SPB |
CPS |
(See note 1 below) |
|||
Padding |
1 (RLC data) |
|||||||
: : |
: |
|||||||
Padding |
6 (RLC data) |
|||||||
TI |
E |
(See note 1 below) |
||||||
Length indicator = 33 |
E |
7 (RLC data) |
||||||
LLC2 (octet 28) |
8 (RLC data) |
|||||||
LLC2 (octet 29) |
9 (RLC data) |
|||||||
: : |
: |
|||||||
LLC2 (octet 56) |
36 (RLC data) |
|||||||
LLC2 (octet 57) |
37 (RLC data) |
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
Octet |
TFI |
Countdown value |
SI |
R |
1 (header) |
||||
BSN 1 |
TFI |
2 (header) |
||||||
CPS |
BSN 1 |
3 (header) |
||||||
Spare |
PI |
RSB |
SPB |
CPS |
(See note 1 below) |
|||
TI |
E |
(See note 2 below) |
||||||
LLC2 (octet 58) |
1 (RLC data) |
|||||||
LLC2 (octet 59) |
2 (RLC data) |
|||||||
LLC2 (octet 60) |
3 (RLC data) |
|||||||
LLC3 (octet 1) |
4 (RLC data) |
|||||||
LLC3 (octet 2) |
5 (RLC data) |
|||||||
: : |
: |
|||||||
LLC3 (octet 33) |
36 (RLC data) |
|||||||
LLC3 (octet 34) |
37 (RLC data) |
NOTE 1: At this row, only a few bits are sent (not a full octet).
NOTE 2: In this radio block, the bits TI / E are meaningless.
Annex K (informative):
Signalling uplink assignments for Downlink Dual Carrier and/or RTTI or MTTI configurations
In the PACKET UPLINK ASSIGNMENT and PACKET TIMESLOT RECONFIGURE, uplink assignments may include the Dynamic Allocation 2 struct.
The maximum number of USFs, timeslots and PDCH pairs for which allocations are made (i.e. the maximum value of N_USF + 1, N_TS + 1 and N_PAIRS + 1, respectively), and hence the maximum number of repetitions of the subsequent fields and structures, are as follows:
Assignment Type |
RTTI/MTTI configuration |
USF mode (applicable to RTTI configurations only) |
Maximum value of (N_USF + 1) |
Maximum value of (N_TS + 1) |
Maximum value of (N_PAIRS + 1) |
Single Carrier Assignment (Note 1) |
No |
8 |
8 |
n/a |
|
Yes |
RTTI |
4 |
n/a |
4 |
|
Yes |
BTTI |
8 |
n/a |
4 |
|
Dual Carrier Assignment |
No |
16 |
16 |
n/a |
|
Yes |
RTTI |
8 |
n/a |
8 |
|
Yes |
BTTI |
16 |
n/a |
8 |
|
NOTE 1: This applies when the Assignment Type field indicates "Assignment on single carrier only" or "Modification of Existing Assignment" |
The order of USF assignment for RTTI assignments is as shown in the table below. PNx stands for PDCH pair number x, where PDCH pairs are ordered according to the timeslot numbers of their constituent PDCHs. The prefixes C1 and C2 indicate the resources on carrier 1 and carrier 2 respectively. The subscript ‘a’ (respectively ‘b’) indicates that the USF applies to the first two (respectively second two) TDMA frames of the following basic radio block period (see sub-clauses 8.1.1.1, 8.1.1.2.1).
Assignment Type |
RTTI configuration |
Order of USF assignments |
Order of USF assignments (RTTI mode with BTTI USF, without power control parameters) |
Single Carrier Assignment (Note 1) |
No |
TN0, …TN7 |
n/a |
Single Carrier Assignment (Note 1) |
Yes |
PN0, ..PN3 (Note 2) |
PN0a, PN0b, PN1a, … PN3b (Note 2) |
Dual Carrier Assignment |
No |
C1/TN0, …C1/TN7, C2/TN0, …C2/TN7 |
n/a |
Dual Carrier Assignment |
Yes |
C1/PN0, …C1/PN3, C2/PN0, …C2/PN3 (Note 2) |
C1/PN0a, C1/PN0b, C1/PN1a, … C1/PN3b, C2/PN0a, C2/PN0b, C2/PN1a, … C2/PN3b (Note 2) |
NOTE 1: This applies when the Assignment Type field is included and indicates "Assignment on single carrier only" or "Modification of Existing Assignment" NOTE 2: In a RTTI configuration, the table assumes a default PDCH pair configuration on each carrier (see sub-clause 7.1.3.6). If fewer than four PDCH pairs are configured on a carrier the maximum value of N_USF or N_PAIRS is correspondingly reduced and the list contains only the PDCH pairs in the PDCH pair configuration, e.g. if there are 3 PDCH pairs configured on each carrier, the order of USF assignments for a Downlink Dual Carrier, RTTI configuration is C1/PN0 … C1/PN2, C2/PN0 … C2/PN2. |
If the value of (N_USF + 1), (N_TS + 1) or (N_PAIRS + 1) is lower than the maximum, then the list of USF assignments is truncated, and there is (implicitly) no assignment for the timeslots/PDCH pairs for which no corresponding value is present.
For MTTI configurations, the order of USF assignments for PDCH-pairs is as shown above for RTTI assignments. In addition, the last assigned USF(s) applies to the PDCH on carrier 1 (if assigned) and then to the PDCH on carrier 2 (if assigned).
Annex L (informative):
MultislotClassGroup in EGPRS Packet Channel Request
In the EGPRS PACKET CHANNEL REQUEST message with cause "One Phase Access Request by Reduced Latency MS", the mobile station multislot class is signalled by the MultislotClassGroup. The MultislotClassGroup indicates the set of the EGPRS multislot classes to which the mobile station belongs. Supported multislot class configurations are limited by the maximum transition times (Tta, Ttb, Tra, Trb) and the minimum number of RX, TX and SUM slots common to the multislot classes in each set as follows (see also 3GPP TS 45.002)
MultislotClassGroup |
Maximum number of slots |
Minimum number of slots |
|||||
|
Rx |
Tx |
Sum |
Tta |
Ttb |
Tra |
Trb |
0 0 0 |
2 |
2 |
4 |
3 |
1 |
3 |
1 |
0 0 1 |
3 |
2 |
5 |
3 |
1 |
2 |
1 |
0 1 0 |
5 |
2 |
6 |
2 |
1 |
1+to |
1 |
0 1 1 |
4 |
3 |
5 |
2 |
1 |
2 |
1 |
1 0 0 |
5 |
4 |
6 |
2 |
1 |
1 |
1 |
1 0 1 |
5 |
4 |
6 |
2 |
1 |
1+to |
1 |
1 0 1 |
6 |
5 |
7 |
1 |
1 |
1 |
to |
1 1 1 |
reserved |
Annex M (informative):
MTTI Assignments and allocations
MTTI assignments are described in sub-clause 7.1.3.7. Examples of valid MTTI assignments are shown in Figures M.1 and M.2. The examples shown in Figure M.1 may be used for either uplink or downlink TBFs. Examples of MTTI assignments that are not permitted and cannot be assigned are shown in Figure M.3.
Figure M.1: Valid MTTI assignments (single TBF)
Figure M.2: Valid MTTI assignment (1 uplink TBF & 1 downlink TBF)
Figure M.3: Invalid MTTI assignments
Figure M.4: Example MTTI assignments
Figure M.4 shows two reduced radio block periods for each of two possible MTTI configurations, during which the mobile station may be allocated resources to transmit RTTI radio blocks (A,B,D,E for Assignment 1 and G,H,I and J for Assignment 2) and/or BTTI radio blocks (C for Assignment 1 and F for Assignment 2). Tables M.1 and M.2 show which radio block(s) are allocated, depending on the timeslot(s) in the previous basic radio block period on which assigned USF(s) were received.
Table M.1: Example MTTI allocations – BTTI USF mode with EDA : Assignment 1
Assigned USF received on TN: |
Allocated blocks |
||||
A |
B |
C |
D |
E |
|
1 |
X |
X |
X |
||
2 |
X |
X |
|||
3 |
X |
X |
|||
4 |
X |
||||
5 |
X |
Table M.2: Example MTTI allocations – BTTI USF mode with EDA : Assignment 2
Assigned USF received on TN |
Allocated blocks |
||||
F |
G |
H |
I |
J |
|
1 |
X |
X |
X |
X |
X |
2 |
X |
X |
|||
3 |
X |
X |
|||
4 |
X |
||||
5 |
X |
Annex N (normative):
Uplink Radio Block Transmission order for EFTA
A mobile station with an uplink TBF operating in BTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCHs allocated by the USF. If the mobile station has P RLC/MAC blocks ready for transmission, then this subset is defined as the first P number of the allocated uplink PDCHs arranged according to the specific timeslot numbers order as specified in Table N.1 below. Tra or Trb, whichever is applicable, is the switching time from transmission to reception (see 3GPP TS 45.002).
Table N.1: Uplink timeslots transmission order for EFTA
Lowest Numbered Downlink Timeslot the MS Needs to Monitor |
Tra or Trb, whichever is applicable |
||
0 |
1 |
2 |
TN0 |
4,3,2,1,0,5,6,7 |
3,2,1,0,4,5,6,7 |
2,1,0,3,4,5,6,7 |
TN1 |
5,4,3,2,1,0,6,7 |
4,3,2,1,0,5,6,7 |
3,2,1,0,4,5,6,7 |
TN2 |
6,5,4,3,2,1,0,7 |
5,4,3,2,1,0,6,7 |
4,3,2,1,0,5,6,7 |
TN3 |
7,6,5,4,3,2,1,0 |
6,5,4,3,2,1,0,7 |
5,4,3,2,1,0,6,7 |
TN4 |
7,6,5,4,3,2,1,0 |
7,6,5,4,3,2,1,0 |
6,5,4,3,2,1,0,7 |
TN5 |
7,6,5,4,3,2,1,0 |
7,6,5,4,3,2,1,0 |
7,6,5,4,3,2,1,0 |
TN6 |
7,6,5,4,3,2,1,0 |
7,6,5,4,3,2,1,0 |
7,6,5,4,3,2,1,0 |
TN7 |
7,6,5,4,3,2,1,0 |
7,6,5,4,3,2,1,0 |
7,6,5,4,3,2,1,0 |
A mobile station with an uplink TBF operating in RTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCH-pairs allocated by the USF in the same manner as specified above. For this case the specific timeslot number order shall be seen as indicating the lowest numbered timeslot of the uplink PDCH-pair.
NOTE: The above described rule determine the subset of the allocated uplink PDCHs or PDCH-pairs on which uplink transmissions shall be performed when EFTA is used. This procedure however, does not define which uplink PDCHs or PDCH-pairs that shall be allocated by the USF. Nor does the procedure define the individual ordering of any transmitted RLC/MAC blocks on these resources, which shall remain the same as for the case when EFTA is not used.
A mobile station with an uplink TBF for which EFTA is used shall perform the transmission of any uplink PACCH message allocated via the polling mechanism (see sub-clauses 10.4.4b and 10.4.5) on the first of the assigned uplink PDCHs or PDCH-pairs arranged according to the specific timeslot number order as described by Table N.1 above, regardless of which resources are allocated by the USF. The switching time Tra or Trb shall be interpreted according to its value at the time the poll was received.
The following example is considered for illustration of the above rules:
– A mobile station is assigned an uplink TBF in BTTI configuration for which EFTA is used.
– This mobile station is allocated uplink PDCHs on TN0, TN1, TN2 and TN3 during the radio block period considered.
– This mobile station only has 3 RLC/MAC blocks available for transmission, out of which one is a PACCH message allocated via the polling mechanism.
– The lowest numbered downlink timeslot the mobile station has to monitor is TN0 and that the applicable switching time Trb is 1.
According to the above description, the mobile station shall then transmit its PACCH message on TN3, whereas the remaining RLC/MAC blocks shall be transmitted on TN1 and TN2 respectively.
Annex O (informative):
Change History
Date |
TSG# |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New |
2015-12 |
Generation of Rel-13 version based on version 12.5.0 |
13.0.0 |
|||||
GP-68 |
GP-151192 |
1607 |
4 |
Introduction of Power Efficient Operation |
13.0.0 |
||
GP-68 |
GP-151193 |
1618 |
– |
Introduction of EC-EGPRS |
13.0.0 |
||
2016-02 |
GP-69 |
GP-160170 |
1619 |
3 |
EC-EGPRS Control Messages |
13.1.0 |
|
GP-69 |
GP-160168 |
1610 |
6 |
EC-EGPRS – TBF Establishment procedures |
13.1.0 |
||
GP-69 |
GP-160148 |
1611 |
4 |
EC-EGPRS – MAC procedures in packet transfer mode |
13.1.0 |
||
GP-69 |
GP-160140 |
1612 |
5 |
EC-EGPRS – RLC procedures |
13.1.0 |
||
GP-69 |
GP-160135 |
1615 |
2 |
EC-EGPRS – RLC/MAC block structure |
13.1.0 |
||
GP-69 |
GP-160186 |
1622 |
– |
Corrections to overlaid CDMA |
13.1.0 |
||
GP-69 |
GP-160144 |
1621 |
1 |
Miscellaneous corrections to eDRX |
13.1.0 |
||
2016-06 |
GP-70 |
GP-160414 |
1625 |
1 |
B |
EC-GSM-IoT RLC/MAC Block Structure and Control Messages, Miscellaneous Corrections |
13.2.0 |
2016-06 |
GP-70 |
GP-160403 |
1624 |
1 |
F |
Miscellaneous corrections to eDRX_GSM |
13.2.0 |
2016-06 |
GP-70 |
GP-160420 |
1626 |
2 |
F |
EC-GSM-IoT Procedures and Timers, Miscellaneous Corrections |
13.2.0 |
2016-09 |
RP-73 |
RP-161392 |
1628 |
1 |
F |
Miscellaneous EC-GSM-IoT Changes |
13.3.0 |
2016-09 |
RP-73 |
RP-161393 |
1629 |
2 |
F |
Clarification of PEO Code Point Usage |
13.3.0 |
2016-09 |
RP-73 |
RP-161392 |
1630 |
4 |
F |
Miscellaneous corrections to EC-GSM-IoT |
13.3.0 |
2016-09 |
Editorial clean-up |
13.3.1 |
|||||
2016-12 |
RP-74 |
RP-162070 |
1634 |
– |
F |
Miscellaneous corrections to EC-GSM-IoT |
13.4.0 |
2017-03 |
RP-75 |
RP-170063 |
1640 |
– |
F |
Clarifying Order of B11 to B1 in in 11 Bit Access |
13.5.0 |
2017-03 |
RP-75 |
RP-170061 |
1635 |
2 |
B |
Introduction of Alternative Mappings for Higher Coverage Classes with 2 PDCHs |
14.0.0 |
2017-06 |
RP-76 |
RP-170923 |
1631 |
7 |
B |
Introduction of Multilateration |
14.1.0 |
2017-06 |
RP-76 |
RP-170924 |
1639 |
4 |
B |
Introduction of new UL coverage class CC5 for UL MCL improvement |
14.1.0 |
2017-06 |
RP-76 |
RP-170925 |
1641 |
2 |
F |
Introduction of enhanced DECOR for GERAN |
14.1.0 |
2017-09 |
RP-77 |
RP-171593 |
1642 |
1 |
F |
Handling of PCCN message including a 3G CCN Measurement Report with no available 3G neighbour cell report |
14.2.0 |
2017-09 |
RP-77 |
RP-171597 |
1643 |
– |
A |
Removing References to 44.160 and 44.118 (Iu mode) |
14.2.0 |
2017-09 |
RP-77 |
RP-171594 |
1646 |
1 |
F |
Corrections to Figures 10.3a.2.1.1 and 10.3a.2.2.1 |
14.2.0 |
2017-09 |
RP-77 |
RP-171593 |
1647 |
1 |
F |
Clarification of DL PACCH DRX in Extended Uplink TBF Mode |
14.2.0 |
2018-06 |
RP-80 |
RP-180822 |
1648 |
2 |
B |
Security enhancement for MTA in network configuration without LLC security |
15.0.0 |
2020-07 |
RP-88e |
– |
– |
– |
– |
Upgrade to Rel-16 version without technical change |
16.0.0 |
2022-03 |
RP-95e |
– |
– |
– |
– |
Upgrade to Rel-17 version without technical change |
17.0.0 |