3GPP TS 45.010
3GPP TS 45.010
3GPP TS 45.010
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this
Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 13 2 3GPP TS 45.010 V13.4.0 (2016-12)
Keywords
GSM, radio, synchronization
3GPP
Postal address
Internet
http://www.3gpp.org
Copyright Notification
2016, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS is a Trade Mark of ETSI registered for the benefit of its members
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 13 3 3GPP TS 45.010 V13.4.0 (2016-12)
Contents
Foreword..........................................................................................................................................................
1 Scope......................................................................................................................................................
1.1 References...........................................................................................................................................................
1.2 Definitions and abbreviations..............................................................................................................................
2 General description of synchronization system......................................................................................
3 Timebase counters..................................................................................................................................
3.1 Timing state of the signals...................................................................................................................................
3.2 Relationship between counters............................................................................................................................
4 Timing of transmitted signals.................................................................................................................
5 BTS Requirements for Synchronization...............................................................................................
5.0 General...............................................................................................................................................................
5.1 Frequency source...............................................................................................................................................
5.2 Timebase counters.............................................................................................................................................
5.3 Internal BTS carrier timing................................................................................................................................
5.4 Initial Timing advance estimation......................................................................................................................
5.5 Maximum timing advance value........................................................................................................................
5.6 Delay tracking....................................................................................................................................................
5.6.1 For circuit switched channels.......................................................................................................................
5.6.2 For packet switched channels......................................................................................................................
5.6.3 Delay assessment error................................................................................................................................
5.6.4 Pico-BTS and Local Area multicarrier BTS delay tracking........................................................................
5.7 Timeslot length..................................................................................................................................................
5.7.0 Implementation options................................................................................................................................
5.7.1 Regular implementation with timeslot lengths of non-integral symbol periods.........................................
5.7.2 Implementation option for reduced symbol period bursts when integral symbol period option is
used for normal symbol period bursts..........................................................................................................
5.8 Range of Timing advance..................................................................................................................................
6 MS Requirements for Synchronization.................................................................................................
6.0 General...............................................................................................................................................................
6.1 MS carrier frequency.........................................................................................................................................
6.2 Internal timebase................................................................................................................................................
6.3 Assessment of BTS timing................................................................................................................................
6.4 Timing of transmission......................................................................................................................................
6.5 Application of Timing Advance........................................................................................................................
6.5.1 For circuit switched channels.......................................................................................................................
6.5.2 For packet switched channels......................................................................................................................
6.6 Access to a new BTS.........................................................................................................................................
6.7 Temporary loss of signal....................................................................................................................................
6.8 Timing of channel change..................................................................................................................................
6.9 Application of new Timing Advance value.......................................................................................................
6.10 Definition of "ready to transmit within x ms"...................................................................................................
6.11 Definition of additional reaction times for GPRS mobile stations....................................................................
6.11.1 Uplink and downlink assignment reaction times.........................................................................................
6.11.2 Change in channel coding scheme commanded by network.......................................................................
6.11.3 Contention resolution reaction time.............................................................................................................
6.11.4 Reaction time in response to other commanding messages.........................................................................
6.11.5 PAN related reaction times...........................................................................................................................
6.11.6 DTR related reaction times..........................................................................................................................
6.12 Observed Frequency Offset (OFO) reported by the CTS-MS...........................................................................
6.13 Timing of inter-RAT channel change from GSM to UTRAN...........................................................................
6.13a Timing of inter-RAT channel change from GSM to E-UTRAN.......................................................................
6.14 Timing of combined intracell channel change and packet assignment.............................................................
7 CTS-FP Requirements for Synchronization..........................................................................................
7.1 Frequency source default requirements.............................................................................................................
3GPP
Release 13 4 3GPP TS 45.010 V13.4.0 (2016-12)
3GPP
Release 13 5 3GPP TS 45.010 V13.4.0 (2016-12)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following
formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the
TSG with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 13 6 3GPP TS 45.010 V13.4.0 (2016-12)
1 Scope
The present document defines the requirements for synchronization on the radio sub-system of the digital cellular
telecommunications systems GSM. However, it does not define the synchronization algorithms to be used in the
Base Transceiver Station (BTS), CTS Fixed Part (CTS-FP) and Mobile Station (MS). These are up to the
manufacturer to specify.
1.1 References
The following documents contain provisions which, through reference in this text, constitute provisions of the
present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document
(including a GSM document), a non-specific reference implicitly refers to the latest version of that document
in the same Release as the present document.
[2] 3GPP TS 25.123: Requirements for support of radio resource management (TDD).
[3] 3GPP TS 25.133: Requirements for support of radio resource management (FDD).
[5] 3GPP TS 43.052: Lower layers of the Cordless Telephony System (CTS) Radio Interface;
Stage 2.
[6] 3GPP TS 43.059: Functional stage 2 description of Location Services (LCS) in GERAN.
[7] 3GPP TS 43.064: Overall description of the GPRS radio interface; Stage 2.
[8] 3GPP TS 44.018: Mobile radio interface layer 3 specification, Radio Resource Control
Protocol.
[9] 3GPP TS 44.060: General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station
System (BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC) protocol.
[10] 3GPP TS 45.002: Multiplexing and multiple access on the radio path.
[16] 3GPP TS 36.133: Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management.
[17] 3GPP TS 36.211: Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels
and Modulation.
3GPP
Release 13 7 3GPP TS 45.010 V13.4.0 (2016-12)
Current Serving BTS: BTS on one of whose channels (TCH, DCCH, CCCH or PDCH) the MS is currently
operating.
Current Serving CTS-FP: CTS-FP on one of whose channels (TCH or CTS control channels) the CTS-MS is
currently operating.
FANR (Fast Ack/Nack Reporting): Fast Ack/Nack Reporting enables the use of a PAN field within an RLC/MAC
block for EGPRS data transfer or for EGPRS2 data transfer. FANR enables the mobile station to transmit in the
uplink direction a PAN field corresponding to a downlink TBF. Similarly FANR enables the network to transmit in
the downlink direction a PAN field corresponding to an uplink TBF.
MS timing offset: delay of the received signal relative to the expected signal from an MS at zero distance under
static channel conditions with zero timing advance. This is accurate to 1 symbol, and reported once per SACCH or
after a RACH as. required (i.e. at the same rate as timing advance). For example, for an MS with a round trip
propagation delay of P symbols, but with a timing advance of T symbols, the reported timing offset will be P-T
quantized to the nearest symbol. For GPRS the MS timing offset is not reported.
Normal Symbol Period: duration of a symbol for bursts using a modulating symbol rate of 1625/6 ksymb/s (see
3GPP TS 45.004); it is equal to 48/13 s. This symbol duration is used for transmission of GMSK, 8PSK, 16QAM
and 32QAM modulated bursts on downlink and GMSK, 8PSK and 16QAM modulated bursts on uplink (see 3GPP
TS 45.004).
Observed Frequency Offset (OFO): difference of frequency of signals received by a CTS-MS from a CTS-FP and
a BTS. The Observed Frequency Offset is measured and reported by the CTS-MS on CTS-FP requirement. The
Observed Frequency Offset is expressed in ppm with an accuracy of 1/64 ppm (i.e. about 0,016 ppm).
Quarter symbol number: timing of quarter symbol periods (12/13 s or 10/13 s depending on the actual symbol
period used) within a timeslot. A symbol can represent 1 to 5 bits depending upon modulation.
Reduced Latency: refers to the use of FANR either in BTTI configuration or in RTTI configuration for EGPRS and
EGPRS2.
Reduced Symbol Period: duration of a symbol for bursts using a modulating symbol rate of 325 ksymb/s (see
3GPP TS 45.004); it is equal to 40/13 s. This symbol duration is used for transmission of QPSK, 16QAM and
32QAM modulated bursts on uplink and downlink (see 3GPP TS 45.004).
Symbol Period: symbol period is the duration of a symbol and shall refer to normal symbol period unless explicitly
clarified to be the reduced symbol period.
TDMA frame number: count of TDMA frames relative to an arbitrary start point.
Timebase counters: set of counters which determine the timing state of signals transmitted by a BTS or MS.
Time group (TG): used for compact, time groups shall be numbered from 0 to 3 and a particular time group shall
be referred to by its time group number (TG) (see 3GPP TS 45.002).
3GPP
Release 13 8 3GPP TS 45.010 V13.4.0 (2016-12)
Timing Advance: signal sent by the BTS to the MS which the MS uses to advance its timings of transmissions to
the BTS so as to compensate for propagation delay.
Timing Advance Index: Timing Advance Index TAI used for GPRS, which determines the position of the
subchannel on PTCCH (see 3GPP TS 45.002) used by the MS to send an access burst, from which the network can
derive the timing advance.
The BTS sends signals on the BCCH carrier or, for COMPACT on the CPBCCH carrier, to enable the MS to
synchronize itself to the BTS and if necessary correct its frequency standard to be in line with that of the BTS. The
signals sent by the BTS for these purposes are:
b) Synchronization bursts.
The timings of timeslots, TDMA frames, TCH frames, control channel frames, and (for COMPACT) the rotation of
time groups are all related to a common set of counters which run continuously whether the MS and BTS are
transmitting or not. Thus, once the MS has determined the correct setting of these counters, all its processes are
synchronized to the current serving BTS.
The MS times its transmissions to the BTS in line with those received from the BTS. The BTS sends to each MS a
"timing advance" parameter (TA) according to the perceived round trip propagation delay BTS-MS-BTS. The MS
advances its timing by this amount, with the result that signals from different MS's arriving at the BTS and
compensated for propagation delay. This process is called "adaptive frame alignment".
Additionally, synchronization functions may be implemented in both the MS and the BTS to support the so-called
pseudo synchronization scheme for circuit-switched handovers. The support of this scheme is optional except that
MS shall measure and report the Observed Timing Difference (OTD), which is a mandatory requirement. The
detailed specifications of the pseudo-synchronization scheme for circuit-switched handovers are included in annex
A.
While in dual transfer mode an MS performs all the tasks of dedicated mode. In addition, upper layers can require
the release of all the packet resources, which triggers the transition to dedicated mode, or the release of the RR
resources, which triggers the transition either to idle mode and packet idle mode or, depending upon network and
MS capabilities, to packet transfer mode.
When handed over to a new cell, the MS leaves the dual transfer mode, enters the dedicated mode where it switches
to the new cell, may read the system information messages sent on the SACCH and may then enter dual transfer
mode in the new cell (see 3GPP TS 44.060).
In CTS, the CTS-FP sends signals on the CTSBCH to enable the MS to synchronize itself to the CTS-FP and if
necessary correct its frequency standard to be in line with that of the CTS-FP.
b) Synchronization bursts.
The timings of timeslots, TDMA frames, CTSBCH, CTSARCH, CTSAGCH and CTSPCH frames are all related to
a first common set of counters which run continuously whether the CTS-MS and CTS-FP are transmitting or not.
Thus, once the CTS-MS has determined the correct setting of these first counters, the CTS-MS is able to attach to
the current serving CTS-FP. In addition, during CTS-MS attachment, the CTS-FP sends to the CTS-MS the
remaining counters for SACCH and TCH frames. Then, all processes of the CTS-MS are synchronized to the current
serving CTS-FP.
The CTS-MS times its transmissions to the CTS-FP in line with those received from the CTS-FP. The timing
advance parameter is set to zero for CTS.
3GPP
Release 13 9 3GPP TS 45.010 V13.4.0 (2016-12)
Additionally, the CTS-FP may be assisted by a CTS-MS to adjust its frequency source. When required by the CTS-
FP, the CTS-MS estimates if possible and reports the Observed Frequency Offset of the CTS-FP with a specified
BTS. The CTS-FP may then adjust its frequency source according to this value.
3 Timebase counters
In CTS, the CTS-MS shall manage different sets of counters for CTS operation and GSM operation.
Alternatively, in case of transmission using reduced symbol period, for a BTS or an MS the following counters have
the following ranges:
- QN increments every 12/13 s for normal symbol period and every 10/13s for Reduced Symbol Period;
- TN increments whenever QN changes from count 624 to 0 for normal symbol periodand whenever QN
changes from count 749 to 0 for reduced symbol period;
i) The MS can use the timing of receipt of the synchronization burst to set up its timebase counters as follows:
FN = 51 ((T3-T2) mod (26)) + T3 + 51 x 26 x T1 when the synch burst is received,(where T3 = (10 x T3') +
1, T1, T2 and T3' being contained in information fields in synchronization burst).
3GPP
Release 13 10 3GPP TS 45.010 V13.4.0 (2016-12)
ii) For Compact, the MS can use the timing of receipt of the synchronization burst to set up its timebase counters
as follows:
FN = (R1 x 51 + R2) x 52 + 51 when the synch burst is received (where R1 and R2 are contained in
information fields in synchronization burst);
TNis determined from TG as described in 3GPP TS 45.002, where TG is contained in information fields in
synchronization burst.
FN = (51 ((T3-T2) mod (26)) + T3 + 51 x 26 x T1) mod (2715648) when the CTS-MS receives the last
CTSAGCH burst of the non-hopping access procedure, where T2 = T4 mod (26), and T1 and T3 being
contained in this CTS immediate assignment message.
iv) For EC-GSM-IoT, the MS may use the timing of receipt of the synchronization burst on EC-SCH to set up its
timebase counters as follows:
where,
RFNQH = FN within a quarter hyperframe = (51 x 52 x T1') + (4 x 51 x T2' + 51 x T2'') + T3 when the
synch burst is received,
T1', T2' is contained from information fields in the synchronization burst, and,
T2'' is signalled through the cyclic shift pattern used on the EC-SCH, see 3GPP TS 45.003.
T3 is determined e.g. by the device through the identification of the mapping of the FCCH, or EC-
SCH, onto the specific TDMA frames within the 51-multiframe.
NOTE: Depending on the coverage condition, the MS may optionally use the timing of receipt of the
synchronization burst (SCH) to set up its timebase counters as described in i).
(When adjacent BTS's are being monitored for handover purposes, or for cell reselection purposes in group receive
mode, the MS may choose to store the values of QN, TN and FN for all the BTS's whose synchronization bursts
have been detected relative to QN, TN and FN for its current serving BTS).
5.0 General
The conditions under which the requirements of subclauses 5.4 and 5.6 must be met shall be 3 dB below the
reference sensitivity level or input level for reference performance, whichever applicable, in 3GPP TS 45.005 and
3 dB less carrier to interference ratio than the reference interference ratios in 3GPP TS 45.005.
3GPP
Release 13 11 3GPP TS 45.010 V13.4.0 (2016-12)
For EC-GSM-IoT, the conditions shall be met at the input level for reference performance of EC-RACH, and at the
reference carrier to interference ratio of the EC-RACH, for the highest coverage class, as defined in 3GPP
TS 45.005 for the supported TS option(s) of EC-RACH.
For the pico-BTS and Local Area multicarrier BTS classes the absolute accuracy requirement is relaxed to 0.1ppm.
NOTE: BTS frequency source stability is one factor relating to E-OTD LCS performance and the reader is
referred to Annex C for the relationship between BTS frequency source stability and E-OTD LCS
performance characteristics.
For COMPACT inter base station time synchronization is required such that timeslot number (TN) = i (i = 0 to 7)
and frame number (FN) with FN mod 208 =0 shall occur at the same time in all cells. The timebase counters of
different BTSs shall be synchronized together such that the timing difference between different BTSs shall be less
than 1 symbol period, 48/13 s (which can be 1 or 3 bits depending upon modulation) measured at the BTS antenna.
If a cell defines a COMPACT cell in its neighbour list, time synchronization is required such that timeslot number
(TN) = i (i = 0 to 7) and frame number (FN) with FN mod 208 =0 shall occur at the same time in both cells.
When extended DRX (eDRX) is supported in a routing area (RA) time synchronization is required such that any
given timeslot number (TN) and frame number (FN) shall occur at the same time in all cells within the RA subject to
an allowed tolerance. The timebase counters of different BTSs shall be synchronized together such that the timing
difference between different BTSs (allowed tolerance) shall be less than 4 seconds measured at the BTS antenna.
For pico-BTS and Local Area multicarrier BTS, the timing difference between different carriers shall be less than
2 symbol periods, measured at the BTS antenna.
For the pico-BTS and Local Area multicarrier BTS, there is no requirement to measure this timing advance.
However, either this measured value or a programmable value of timing advance shall be included in the response
from the BTS when a timing advance value needs to be sent.
3GPP
Release 13 12 3GPP TS 45.010 V13.4.0 (2016-12)
NOTE: The timing advance is always calculated in terms of number of symbols with normal symbol period
irrespective of the actual symbol period used on the uplink.
Restricting the change in timing advance to 1 symbol period at a time gives the simplest implementation of the BTS.
However the BTS may use a larger change than this but great care must then be used in the BTS design.
The BTS shall update the timing advance values in the next downlink signalling message following the access burst.
The BTS may also monitor the delay of the normal bursts and access bursts sent by the MS on PDTCH and PACCH.
Whenever an updating of TA is needed, the BTS may send the new TA value in a power control/timing advance
message (see 3GPP TS 44.060).
For an MS in dual transfer mode the BTS shall follow the procedure described in subclause 5.6.1.
The control loop for the timing advance shall be implemented in such a way that it will cope with MSs moving at a
speed up to 500 km/h, except for EC-GSM-IoT MS when it enters EC operation, where [50] km/h applies.
A BTS shall follow the implementation option of timeslot length with integer symbol periods for normal symbol
periods, see subclause 5.7.2, on all transceivers in case EC-channels (EC-SCH, EC-BCCH, EC-CCCH, EC-PDTCH,
or EC-PACCH) are mapped onto one or more transceiver resources.
3GPP
Release 13 13 3GPP TS 45.010 V13.4.0 (2016-12)
Figure 5.7.2: Implementation using non integral number of symbol periods in both Normal Symbol
Period burst and Reduced Symbol Period bursts.
Irrespective of the symbol duration used, the centre of the training sequence shall occur at the same point in time.
This is illustrated in Figure 5.7.3 below. This means that the active part of a reduced symbol period burst shall start
12/13 s (which is a quarter of a normal symbol period) later in time and ends 12/13 s earlier.
Figure 5.7.3: Timing alignment between normal symbol period and reduced symbol period bursts
The duration of various components of the timeslot are illustrated in Table 5.7.1.
3GPP
Release 13 14 3GPP TS 45.010 V13.4.0 (2016-12)
160 144
Tail (left) 4 3
13 13
2760 2784
Encrypted symbols (left) 69 58
13 13
1240 1248
Training sequence 31 26
13 13
2760 2784
Encrypted symbols (right) 69 58
13 13
160 144
Tail (right) 4 3
13 13
420 396
Guard period 10.5 8.25
13 13
7500 7500
Total 187.5 156.25
13 13
Figure 5.7.4: Implementation allowing integral number of symbol periods for normal symbol
period bursts
3GPP
Release 13 15 3GPP TS 45.010 V13.4.0 (2016-12)
The different burst lengths shall be obtained by changing the guard period lengths to values other than what is
described in Table 5.7.1. The guard period lengths on adjacent timeslots shall be as described in Table 5.7.2.
6.0 General
The MS shall only start to transmit to the BTS if the requirements of subclauses 6.1 to 6.4 are met.
The conditions under which the requirements of subclauses 6.1 to 6.4 must be met shall be 3 dB below the reference
sensitivity level or input level for reference performance, whichever applicable, in 3GPP TS 45.005 and 3 dB less
carrier to interference ratio than the reference interference ratios or the interference ratios for reference performance,
whichever applicable, in 3GPP TS 45.005. For EC-GSM-IoT, the conditions shall be met at the input signal level
and at the interference ratio of EC-SCH at reference performance, as defined in 3GPP TS 45.005.
In discontinuous reception (DRX), the MS should meet the requirements of subclauses 6.1 to 6.3 during the times
when the receiver is required to be active.
For CTS, the CTS-MS shall fulfil all the requirements of subclauses 6.1 to 6.4, 6.7, 6.8, 6.10 and 6.11 where BTS
designates the CTS-FP. The CTS-MS shall always use a TA value of zero. The CTS-MS shall only start to transmit
to the CTS-FP if the requirements of subclauses 6.1 to 6.4 are met. The conditions under which the requirements of
subclauses 6.1 to 6.4 must be met shall be 3 dB below the reference sensitivity level or input level for reference
performance, whichever applicable, in 3GPP TS 45.005 and 3 dB less carrier to interference ratio than the reference
3GPP
Release 13 16 3GPP TS 45.010 V13.4.0 (2016-12)
interference ratios in 3GPP TS 45.005. In discontinuous reception (DRX), the CTS-MS should meet the
requirements of subclauses 6.1 to 6.3 during the times when the receiver is required to be active.
In case of a multislot configuration, the MS shall use a common timebase for transmission of all channels. In this
case, if the MS, not in EC operation, does not support transmission of reduced symbol period bursts, it may
optionally use a timeslot length of 157 normal symbol periods on timeslots TN = 0 and 4, and 156 normal symbol
periods on timeslots with TN = 1, 2, 3, 5, 6 and 7, rather than 156,25 normal symbol periods on all timeslots. An
EC-GSM-IoT MS, when in EC operation, shall use the timeslot length with integer symbol periods, see subclause
5.7.2.
If the MS supports reduced symbol period transmissions, it shall use a timeslot length of 187.5 reduced symbol
periods or a timeslot of length 156.25 normal symbol periods. When there is a pair of different symbol period bursts
on adjacent timeslots, then the guard period between the two bursts shall be 8.5 normal symbol periods which equals
10.2 reduced symbol periods. The active part of a reduced symbol period burst shall start a quarter of a normal
symbol period later compared to a normal symbol period burst as shown in Figure 5.7.3.
In case of a circuit switched multislot configuration, the common timebase shall be derived from the main channel
and the TA values received on other channels shall be neglected. In case of a packet switched multislot configuration
the common timebase shall be derived from all timeslots monitored by the MS. In this case, the MS may assume
that the BTS uses a timeslot lengthof156,25normalsymbolperiodsonalltimeslotsusingnormalsymbolperiod
andatimeslotlengthof187,5reducedsymbolperiodsonalltimeslotsusingreducedsymbolperiod.Inthecaseofa
combinationofcircuitandpacketswitchedchannelconfigurationtheMSmayderivethecommontimebasefrom
thecircuitswitchedchannelonly.
3GPP
Release 13 17 3GPP TS 45.010 V13.4.0 (2016-12)
Within the packet resource assignments (see 3GPP TS 44.018 and 3GPP TS 44.060) for uplink or downlink
messages the MS gets the Timing Advance Index (TAI). If a PTCCH subchannel is assigned to the MS, the MS shall
send access bursts on the subchannel defined by the TAI on the PTCCH. These access bursts received on PTCCH
are used by the BTS to derive the timing advance. PTCCH shall not be assigned in case of an EC-GSM-IoT capable
MS in EC operation.
When the MS receives the updated value of TA from the BTS on the downlink PTCCH, it shall always use the last
received TA value for the uplink transmission of normal bursts.
If an MS is allocated different TAI values for simultaneous uplink and downlink packet transfer, the MS may choose
to use any one or both PTCCH subchannels. If two subchannels are used, the MS shall always use the received TA
value corresponding to the last transmitted PTCCH uplink burst. If the MS has been assigned TAIs for both UL and
DL and if either the last UL or the last DL TBF is released, the MS shall use the TAI assigned for the remaining
direction of data transfer.
If the MS receives a packet resource assignment or power control/timing advance message (see 3GPP TS 44.018
and 3GPP TS 44.060) without a TAI for the corresponding UL or DL TBFs, the MS shall not use the old assigned
TAI for the continuous timing advance procedure for that direction of data transfer. If no more TAIs are valid the
MS shall not perform the continuous timing advance procedure at all.
Upon initiation of the continuous timing advance procedure the MS shall disregard the TA values on PTCCH until it
has sent its first access burst on PTCCH.
The network may request the MS to send 4 access bursts to calculate a new TA value. For this purpose the network
sets the system information element CONTROL_ACK_TYPE to indicate that the MS is to respond with a
PACKET_CONTROL_ACKNOWLEDGEMENT consisting of 4 access bursts (see 3GPP TS 44.060), and sends a
PACKET_POLLING_REQUEST to the MS. In this case, the MS shall transmit 4 consecutive access bursts on the
assigned resources.
If the MS receives a packet resource assignment or power control/timing advance message (see 3GPP TS 44.018
and 3GPP TS 44.060), the MS shall use the included TA value for normal burst transmissions until it receives a new
value on PTCCH. If the message does not contain a TA value, the MS shall not change its TA value.
When entering packet transfer mode or broadcast/multicast receive mode, the MS is not allowed to transmit normal
bursts until it has received a valid TA value by any of the methods described above.
An MS in dual transfer mode shall follow the procedures described in subclause 6.5.1. If the CS connection is
released and the MS leaves dual transfer mode to enter packet transfer mode, the MS shall follow the procedures
described in the present subclause. The MS shall perform the continuous timing advance procedure if a TAI is
contained in the packet CS release indication message (see 3GPP TS 44.060). The mobile station shall use the last
value of the timing advance received whilst in dual transfer mode until a new value of the timing advance is
determined from the continuous timing advance procedure or is received from the network.
3GPP
Release 13 18 3GPP TS 45.010 V13.4.0 (2016-12)
- the MS shall use a TA value of 0 for the Random Access burst sent. When a TA is received from the BTS
that TA shall be used.
- after the HANDOVER ACCESS bursts which shall be sent with a TA value of 0 the MS shall use a TA
calculated as specified in annex A. When a TA is received from the new BTS that TA shall be used. The
transmission of the HANDOVER ACCESS bursts is optional if so indicated by the BTS.
- after the PS HANDOVER ACCESS bursts which shall be sent with a TA value of 0 the MS shall use a TA
calculated as specified in annex A. When a TA is received from the new BTS that TA shall be used. The
transmission of the PS HANDOVER ACCESS bursts is optional if so indicated by the BTS.
In those cells that support extended TA values if TA value in new cell is greater than 63 and the HANDOVER
COMMAND message indicates that the transmission of four HANDOVER ACCESS messages is optional the MS
shall not transmit these four messages.
- the MS shall use a TA value of 0 for the HANDOVER ACCESS bursts sent. When a TA is received in a
PHYSICAL INFORMATION message that TA shall be used. Before a TA is received from the new BTS
no valid "used TA" shall be signalled to the new BTS.
- the MS shall use a TA value of 0 for the PS HANDOVER ACCESS bursts sent. When a TA is received in
a PACKET PHYSICAL INFORMATION message that TA shall be used. Before a TA is received from
the new BTS no valid "used TA" shall be signalled to the new BTS.
- after the HANDOVER ACCESS bursts which shall be sent with a TA value of 0 the MS shall use a TA as
specified in the HANDOVER COMMAND message by the old BTS, or a default value of 1, if the old
BTS did not provide a TA value. The transmission of the HANDOVER ACCESS bursts is optional if so
indicated by the BTS.
- after the PS HANDOVER ACCESS bursts which shall be sent with a TA value of 0 the MS shall use a TA
as specified in the PS HANDOVER COMMAND message by the old BTS, or a default value of 1, if the
old BTS did not provide a TA value. The transmission of the PS HANDOVER ACCESS bursts is optional
if so indicated by the BTS.
In those cells that support extended TA values if TA value in new cell is greater than 63 and the HANDOVER
COMMAND message (respectively PS HANDOVER COMMAND message) indicates that the transmission of four
HANDOVER ACCESS messages (respectively PS HANDOVER ACCESS messages) is optional the MS shall not
transmit these four messages.
3GPP
Release 13 19 3GPP TS 45.010 V13.4.0 (2016-12)
When the MS receives a new or updated TA value on the downlink PTCCH or downlink PACCH, the MS shall be
ready to transmit using the new TA value within 40 ms of the end of the last timeslot of the message block
containing the new TA value.
- the first burst of the first TCH or control channel block that occurs after the x ms, in case of an intracell
channel change;
- the first burst of the TCH or control channel that occurs after the x ms, in case of a handover;
- the first burst of the PDTCH, EC-PDTCH or control channel that occurs after the x ms;
- the first allowed uplink frame (see 3GPP TS 25.212 and 3GPP TS 25.214 for FDD and 3GPP TS
25.222 for TDD), that occurs after the x ms, in case of an inter-RAT handover to a UTRAN cell.
- the first uplink PRACH frame or (for TDD only) UpPTS field (see 3GPP TS 36.211) that occurs after the x
ms, in case of an inter-RAT handover to a E-UTRAN cell.
NOTE: The MS shall keep the timings of the neighbour GSM cells that it is monitoring (according to 3GPP
TS 45.008) to an accuracy of 1 normal symbol periods.
with FANR activated (see 3GPP TS 44.060) shall be ready to transmit and receive using the new assignment in the
TDMA frame indicated in Table 6.11.1.1 where N = the last TDMA frame of the downlink block containing the
assignment message.
Table 6.11.1.1: Assignment Reaction Time for a TBF with FANR activated
If the MS is required to transmit a PACKET CONTROL ACKNOWLEDGEMENT, or, in case of EC operation, the
MS is required to transmit an EC PACKET CONTROL ACKNOWLEDGEMENT, subsequent to an assignment
message (see 3GPP TS 44.060), the MS shall be ready to transmit and receive, or in case of EC operation transmit or
receive, on the new assignment (i.e. after transmitting the PACKET CONTROL ACKNOWLEDGMENT, or, in case
of EC operation, the EC PACKET CONTROL ACKNOWLEDGEMENT, using the old assignment) as follows:
- For a TBF operating in BTTI configuration or an EC TBF not using blind physical layer transmissions
(CC1), no later than the next occurrence of block B((x+2) mod 12) where block B(x) is the radio block
containing the PACKET CONTROL ACKNOWLEDGEMENT or EC PACKET CONTROL
ACKNOWLEDGEMENT, respectively.
- For an EC TBF using blind physical layer transmissions the same reaction times as for BTTI configuration
apply, where B(x) refers to the last BTTI period used by the blind physical layer transmissions of the EC
PACKET CONTROL ACKNOWLEDGEMENT. For example, if the blind physical layer transmissions occur
during two BTTI periods, the reaction time is measured from the last BTTI period used by the blind physical
layer transmissions.
- For a TBF operating in RTTI configuration, no later than the next occurrence of block B((x+1) mod 12)b
where block Bxa is the radio block containing the PACKET CONTROL ACKNOWLEDGEMENT or no later
than the next occurrence of block B((x+2) mod 12)a where block Bxb is the radio block containing the
PACKET CONTROL ACKNOWLEDGEMENT (see 3GPP TS 45.002 [10] for an explanation of RTTI radio
block indexing applicable to the RTTI configuration).
- If the assignment message changes the TBF from BTTI to RTTI configuration, no later than the next
occurrence of block B((x+2) mod 12)a, where block Bx is the radio block containing the PACKET
CONTROL ACKNOWLEDGEMENT.
- If the assignment message changes the TBF from RTTI to BTTI configuration, no later than the next
occurrence of block B((x+2) mod 12), where block Bxa or Bxb is the radio block containing the PACKET
CONTROL ACKNOWLEDGEMENT (see NOTE).
NOTE: This is to ensure the reaction time falls on a BTTI radio block boundary.
The reaction time applies also for the reception of the first USF for dynamic uplink assignment and extended
dynamic uplink assignment, including when Shifted USF operation is used.
For a TBF operating in BTTI configuration, or an EC TBF not using blind physical layer transmissions
(CC1), no later than the next occurrence of block B((x+3) mod 12) where block B(x) is the radio block
containing the command. For an EC TBF using blind physical layer transmissions, B(x) refers to the last
BTTI period used by the blind physical layer transmissions of the block containing the command to change
the channel coding scheme. For example, if the blind physical layer transmissions occur during two BTTI
periods, the reaction time is measured from the last BTTI period used by the blind physical layer
transmissions.
For a TBF operating in RTTI configuration, no later than the next occurrence of block B((x+2) mod 12)b
where block Bxa is the radio block containing the command or no later than the next occurrence of block
B((x+3) mod 12)a where block Bxb is the radio block containing the command (see 3GPP TS 45.002 [10]
for an explanation of RTTI radio block indexing applicable to the RTTI configuration).
3GPP
Release 13 21 3GPP TS 45.010 V13.4.0 (2016-12)
For a TBF operating in BTTI configuration, or an EC TBF not using blind physical layer transmissions
(CC1), no later than the next occurrence of block B((x+3) mod 12) where block B(x) is the radio block
containing the contention resolution message (see 3GPP TS 44.060). For an EC TBF using blind physical
layer transmissions, B(x) refers to the last BTTI period used by the blind physical layer transmissions of
the contention resolution message. For example, if the blind physical layer transmissions occur during two
BTTI periods, the reaction time is measured from the last BTTI period used by the blind physical layer
transmissions.
For a TBF operating in RTTI configuration, no later than the next occurrence of block B((x+2) mod 12)b
where block Bxa is the radio block containing the contention resolution message or no later than the next
occurrence of block B((x+3) mod 12)a where block Bxb is the radio block containing the contention
resolution message (see 3GPP TS 45.002 [10] for an explanation of RTTI radio block indexing applicable
to the RTTI configuration).
For a TBF operating in BTTI configuration, or an EC TBF not using blind physical layer transmissions
(CC1), no later than the next occurrence of block B((x+6) mod 12), where block B(x) is the radio block
containing the commanding message or indication from the network. For an EC TBF using blind physical
layer transmissions the B(x) refers to the last BTTI period used by the blind physical layer transmissions of
the commanding message. For example, if the blind physical layer transmissions occur during two BTTI
periods, the reaction time is measured from the last BTTI period used by the blind physical layer
transmissions.
For a TBF operating in RTTI configuration, no later than the next occurrence of block B((x+5) mod 12)b
where block Bxa is the radio block containing the commanding message/indication from the network or no
later than the next occurrence of block B((x+6) mod 12)a where block Bxb is the radio block containing the
commanding message/indication from the network (see 3GPP TS 45.002 [10] for an explanation of RTTI
radio block indexing applicable to the RTTI configuration).
A mobile station that detects a missing/erroneous RLC data block for a downlink TBF with FANR activated (see
3GPP TS 44.060) shall be ready to send an uplink RLC/MAC block for data transfer with a PAN or an EGPRS
PACKET DOWNLINK ACK/NACK or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message (in the case
that there is no uplink RLC data ready for transmission) reflecting the missing/erroneous block in the TDMA frame
indicated in Table 6.11.5.2 where N = the last TDMA frame of the downlink block in which the MS detected the
problem.
3GPP
Release 13 22 3GPP TS 45.010 V13.4.0 (2016-12)
Table 6.11.6.1: Assignment Reaction Time for leaving DTR MS supports FANR
Table 6.11.6.2: Assignment Reaction Time for leaving DTR MS does not support FANR
A mobile station shall enter DTR mode within the reaction time as specificied in Table 6.11.6.3 or Table 6.11.6.4
where N = the last TDMA frame of the radio block period in which all conditions for entering DTR were met.
Table 6.11.6.3: Assignment Reaction Time for entering DTR MS supports FANR
Table 6.11.6.4: Assignment Reaction Time for entering DTR MS does not support FANR
3GPP
Release 13 23 3GPP TS 45.010 V13.4.0 (2016-12)
cell shall not exceed Tinterrupt. Tdelay and Tinterrupt are defined in table 6.13.1 for the case of inter-RAT handover
to a single UTRAN cell assuming good radio conditions.
In addition, the MS shall be ready to transmit and receive using the packet assignment within T_GSM_delay of the
last timeslot of the message block containing the command, unless the access is delayed to an indicated starting
time, in which case it shall be ready to transmit on the new channel at the designated starting time, or within
T_GSM_Delay, whichever is the later. This applies also for the reception of the first USF for dynamic uplink
assignment.
The requirements for using the packet assignment apply also when the MS receives a stand-alone packet assignment
(on the main DCCH), causing the transition from dedicated mode into dual transfer mode (see 3GPP TS 44.018).
3GPP
Release 13 24 3GPP TS 45.010 V13.4.0 (2016-12)
However, if the Observed Frequency Offset is greater than 2 ppm, the CTS-FP frequency source correction shall
have a slope of 0,1 ppm for 936 TDMA frames, i.e. 4,320 seconds.
3GPP
Release 13 25 3GPP TS 45.010 V13.4.0 (2016-12)
Annex A (normative):
Additional requirements for pseudo-synchronization,
synchronized handovers and pseudo-synchronized
handovers
A.1.1 Conventions
The following conventions are adopted in this annex:
- all timing values are considered for descriptive purposes as real numbers modulo the largest period defined in
the system i.e. 3394560000T. When transmitted over the air interface, such a value shall be rounded to the
nearest integer multiple of a symbol period T/2 and that integer shall either be reduced mod some integer
multiple of 256 or the full value shall be used as defined in 3GPP TS 44.018;
- the Timing Advance (TA) value, when the distance between the base station and the MS is equal to or less
than 35 km, or in the case of GSM 400 is equal to or less than 120 km, represents the estimated two way
propagation delay in T units. For the purpose of the calculations in this annex the timing advance values are
considered to represent the estimated one way propagation delay in T/2 units which is equivalent to twice the
delay in T units.
A.1.2 Definitions
Assuming that some MS has to perform handover from BTS 0 (the "current" or "old" BTS) to BTS 1 (the "new"
BTS), the following quantities are defined.
- t0 (resp. t1) denotes the one way line of sight propagation delay between the MS and BTS 0 (resp. BTS 1).
- RTD (Real Time Difference) denotes the value of the local system time in BTS 0 minus that of BTS 1.
- OTD (Observed Time Difference) denotes the timing difference between BTS 0 and BTS 1 as measured by
the MS with the same sign conventions as for RTD.
All these four values are slowly time-varying due to the MS movement and oscillators drift in the BTS's, but they
are defined here just prior handover execution.
OTD = RTD + t1 - t0
- for the pseudo synchronized circuit-switched handover, it is assumed that RTD is known to BTS 0 and MS
supports the scheme, BTS 0 may order pseudo-synchronized handover to BTS 1, including RTD in the
"HANDOVER COMMAND" message;
- for the synchronized circuit-switched or packet-switched handovers, BTS 0 may order synchronized
handover to BTS 1, and the MS sets RTD as defined in subclause A.3.3;
3GPP
Release 13 26 3GPP TS 45.010 V13.4.0 (2016-12)
- under normal operating conditions, t0 should be closely related to the latest received Timing Advance sent by
BTS 0 to the MS; since the MS must have got synch to BTS 1 before performing handover, OTD, RTD and
t0 are available to the MS, hence the value of t1 that can be used to set the new Timing Advance parameter
without receiving it from BTS 1;
The BTS shall maintain synchronization with a set of neighbouring BTS. In this context, synchronization means that
the timing of the TDMA frame at the BTSs is the same, i.e. the timeslot zeros from the BTS transmitted are
synchronous with the timeslot zeros of the carriers on the set of neighbouring BTSs. However, the frame numbers
need not be the same. All timings are to be referenced at the BTS.
3GPP
Release 13 27 3GPP TS 45.010 V13.4.0 (2016-12)
A.3 MS requirements
The MS shall comply to the following requirements.
- if the initial timing advance value calculated is greater than TAmax, the cell shall be considered as out of range.
The MS shall, if it attempts to transmit on the new cell, use a timing advance value of TAmax as the initial
timing advance value. Whether the MS transmits on the new cell or not depends on the NCI bit as specified
in 3GPP TS 44.018;
- if the initial timing advance value calculated is less than 0, the MS shall use a timing advance value of 0 as
the initial timing advance value.
3GPP
Release 13 28 3GPP TS 45.010 V13.4.0 (2016-12)
Annex B (informative):
CTSBCH timeslot shifting properties for CTS-MS
synchronization
The determination of TN for CTS-MS synchronization is eased by specific properties of the CTSBCH timeslot
shifting procedure. Three successive CTSBCH detection and decoding are always sufficient to set TN.
The CTSBCH shifting procedure may be either active or not. This is signalled by a flag in the CTSBCH-SB (see
3GPP TS 45.002).
1) the CTS-MS detects 3 successive CTSBCH-FB, decodes the three associated CTSBCH-SB and stores the
two timeslot shifts values between the three successive CTSBCH-FB;
2) the CTS-MS checks that the three FPBI (see 3GPP TS 45.002) extracted from the three CTSBCH-SB are
identical and that the three CTSBCH shifting flags all indicate CTSBCH shifting active;
3) the CTS-MS extracts the TNSCN from the FPBI according to the rule defined in 3GPP TS 45.002;
4) the CTS-MS uses timeslot number series couple (TNSTNSCN,0, TNSTNSCN,1) (see 3GPP TS 45.002) and the two
stored CTSBCH shift values to determine the three timeslot numbers of the three observed CTSBCH. Due
to specific properties of the shifting series, only one mapping is possible.
3GPP
Release 13 29 3GPP TS 45.010 V13.4.0 (2016-12)
Annex C (informative):
BTS frequency source stability and E-OTD LMU reporting
periods for LCS
in which is the speed of the waves (usually taken as c , the speed of light in vacuum) and C p is a constant
which sets the percentile 100 p associated with rmax . (When the TIE has a Gaussian distribution C 67% 1.0
, C 95% 2.0 , and C 99.7% 3.0 .) In practice, the BTS frequency source stability TIE rms and required E-
OTD range accuracy rmax are likely to be given and table C.3.1 allows the corresponding value of the E-OTD
reporting period T to be read off.
3GPP
Release 13 30 3GPP TS 45.010 V13.4.0 (2016-12)
For example given the requirement for r max @ 95% shall be better than 60m and an observed frequency stability is
0,00072 s/sec then the resulting E-OTD Reporting Period () from the LMU making the observations will be no
greater than 100 seconds.
3GPP
Release 13 31 3GPP TS 45.010 V13.4.0 (2016-12)
Annex D (informative):
Change history
05.10 s25 A015 R97 6.0.0 6.1.0 GPRS, Missing Timing Advance Updates on PTCCH
05.10 s26 A016 R97 6.1.0 6.2.0 Correction to timing advance for GPRS
05.10 s27 A017 R97 6.2.0 6.3.0 Packet polling procedure for calculating new TA
05.10 s28 A021 R97 6.3.0 6.4.0 Correction of Timing Advance Procedure
05.10 s28 A023 R97 6.3.0 6.4.0 Definition of additional GPRS related reaction times
05.10 s28 A026 R97 6.3.0 6.4.0 Continuous timing advance procedure failure
05.10 s28 A018 R98 6.4.0 7.0.0 Harmonization between GSM and PCS 1900 standard
05.10 s28 A019 R98 6.4.0 7.0.0 Synchronization requirements for CTS
05.10 s28 A025 R98 6.4.0 7.0.0 Synchronization requirements for the control of the CTS
service range
05.10 s29 A027 R98 7.0.0 7.1.0 Correction of CTS-FP frequency source correction slope
05.10 s29 A033 R98 7.0.0 7.1.0 Timing advance for access bursts on PTCCH/U
05.10 s29 A036 R98 7.0.0 7.1.0 Reaction time after contention resolution during one phase
access
05.10 s30 A038 R99 7.1.0 8.0.0 EDGE Compact logical channels
05.10 s30 A042 R99 7.1.0 8.0.0 Definition of other reaction times
05.10 s30b A039 R99 8.0.0 8.1.0 Extended range TA information added in 05.10
05.10 s30b A043 R99 8.0.0 8.1.0 Synchronization of 52-multiframes in EGPRS COMPACT
05.10 s30b A049 R99 8.0.0 8.1.0 Defining the MS carrier frequency accuracy value for GSM
400 MS
05.10 s31 A051 R99 8.1.0 8.2.0 Timegroup definition removal from 05.10
05.10 s31b A054 R99 8.2.0 8.3.0 EGPRS Classic to COMPACT BTS synchronization
3GPP
Release 13 32 3GPP TS 45.010 V13.4.0 (2016-12)
05.10 s31b A056 R99 8.2.0 8.3.0 BTS Synchronization, Location Accuracy and LMU update
rates
05.10 s32 A058 R99 8.3.0 8.4.0 Class A Dual Transfer Mode (DTM)
September 2000 - TSG-GERAN#1
05.10 G01 A059 R99 8.4.0 8.5.0 Correction of assignment reaction time
05.10 G01 A061 R99 8.4.0 8.5.0 Addition of the switching requirement for the GSM to
UTRAN
November 2000 - TSG-GERAN#2
05.10 G02 A065 R99 8.5.0 8.6.0 Corrections to synchronised handover
05.10 G02 A066 R99 8.5.0 8.6.0 Reaction time at packet assignment with polling request
8.6.0 8.6.1 Front page layout correction
January 2001 - TSG-GERAN#3
05.10 G03 A067 8.6.1 8.7.0 Delay requirements for blind handover to UTRAN
05.10 G03 A069 8.6.1 8.7.0 Timing requirements for Blind Handover 2G2G
April 2001 - TSG-GERAN#4
05.10 G04 A073 1 8.7.0 8.8.0 Updates to GSM-UTRAN Handover Interruption Times
3GPP
Release 13 33 3GPP TS 45.010 V13.4.0 (2016-12)
Change history
Date TSG GERAN# TSG Doc. CR Rev Subject/Comment Old New
2001-04 04 Version for Release 4 4.0.0
2001-04 07 GP-012776 001 1 Correction of references to relevant 3GPP TSs 4.0.0 4.1.0
2002-02 08 GP-020453 002 1 Clarification to Requirements for Synchronization 4.1.0 4.2.0
at DTM operation
2002-06 10 GP-021930 005 1 Correction to inter system handover interruption 4.2.0 4.3.0
times
2002-06 10 Version for release 5 4.3.0 5.0.0
2002-08 11 GP-022216 007 Editorial clean up of references 5.0.0 5.1.0
2003-02 13 GP-030215 009 Timing of DTM assignment 5.1.0 5.2.0
2003-02 13 GP-030439 011 2 Correction of interruption times for GSM to 5.1.0 5.2.0
UTRAN handover
2003-04 14 GP-030884 016 Clarification on continuous TA procedure 5.2.0 6.0.0
2003-06 15 GP-031547 020 Clarification on USF decoding reaction time on 6.0.0 6.1.0
reception of a new assignment
2003-08 16 GP-032117 022 1 Clarification of reaction times for Extended 6.1.0 6.2.0
Dynamic Allocation and Shifted USF operation
2003-08 16 GP-032284 025 2 Correction of definition of "ready to transmit" for 6.1.0 6.2.0
inter-RAT handover
2003-08 16 GP-032186 028 1 MS reaction time upon reception of assignment 6.1.0 6.2.0
message on CCCH
2004-11 22 GP-042881 030 1 Timing Advance behaviour for DTM to Packet 6.2.0 6.3.0
Transfer mode transition
2005-01 23 GP-050139 031 Timing Advance for multiple TBFs in Packet 6.3.0 6.4.0
Transfer mode
2005-01 23 GP-050289 032 Timing advance for MBMS 6.3.0 6.4.0
2005-04 24 GP-050862 033 Clarification of MS requirements for 6.4.0 6.5.0
synchronization
2005-11 27 GP-052749 0034 1 Introduction of PS handover 6.5.0 6.6.0
2007-02 33 GP-070200 0035 Clarifications and editorial corrections 6.6.0 7.0.0
2007-05 34 GP-070716 0036 PAN Reaction Times 7.0.0 7.1.0
2007-08 35 GP-071546 0038 2 Introduction of Reduced Symbol Duration 7.1.0 7.2.0
2007-11 36 GP-071967 0039 1 Removal of RL-EGPRS TBF mode 7.2.0 7.3.0
2008-02 37 GP-080370 0042 1 Clarifying Radio Block Specific Reaction Times 7.3.0 7.4.0
2008-05 38 GP-080780 0044 1 Time synchronisation 7.4.0 7.5.0
2008-05 38 GP-080580 0046 Timing requirements for PS Handover to UTRAN 7.4.0 7.5.0
2008-05 38 GP-080663 0049 Reduced Latency terminology alignments 7.4.0 7.5.0
2008-05 38 GP-080919 0050 1 Clarification to the PDAN reaction times when 7.4.0 7.5.0
operating in event based FANR
2008-05 38 GP-080582 0048 Editorial corrections 7.5.0 8.0.0
2008-08 39 GP-081141 0047 1 Timing requirements for PS Handover to E- 8.0.0 8.1.0
UTRAN
2008-08 39 GP-081344 0052 2 Assignment reaction time when the TTI 8.0.0 8.1.0
configuration of a TBF is changed
2008-11 40 GP-081562 0053 Corrections to the timing requirements for PS 8.1.0 8.2.0
Handover to E-UTRAN
2009-02 41 GP-090148 0054 Corrections to the timing requirements for PS 8.2.0 8.3.0
Handover to E-UTRAN
2009-05 42 GP-090611 0055 Removal of brackets 8.3.0 8.4.0
2009-11 44 GP-092185 0060 Modification of PAN Related Reaction Times 8.4.0 8.5.0
2009-11 44 GP-091962 0056 Introduction of MTD reporting on Hyperframe level 8.5.0 9.0.0
2010-11 48 GP-102064 0061 2 Reaction times for DTR 9.0.0 10.0.0
2011-03 49 GP-110245 0062 DTR Reaction times: removal of square brackets 10.0.0 10.1.0
2012-08 55 GP-120925 0063 Synchronization requirements for Local Area 10.1.0 11.0.0
multicarrier BTS
2012-11 56 GP-121260 0064 3 Impact from rSRVCC from GERAN to E-UTRAN 11.0.0 11.1.0
2014-09 63 Version for release 12 (frozen at SP-65) 11.1.0 12.0.0
2015-11 68 GP-151216 0065 5 Introduction of EC-EGPRS 12.0.0 13.0.0
2015-11 68 GP-151218 0066 2 Introduction of Power Efficient Operation 12.0.0 13.0.0
2016-02 69 GP-160182 0067 1 Miscellaneous corrections 13.0.0 13.1.0
2016-02 69 GP-160100 0068 Miscellaneous corrections to eDRX 13.0.0 13.1.0
3GPP
Release 13 34 3GPP TS 45.010 V13.4.0 (2016-12)
Change history
Date Meeting TDoc CR Rev Cat Subject/Comment New
version
2016-05 70 GP- 0069 2 F Clarifications and miscellaneous corrections to EC-GSM-IoT 13.2.0
160462 (including name change)
2016-09 73 RP-161392 0070 2 F Corrections to EC-GSM-IoT 13.3.0
2016-12 74 RP-162070 0072 - F Miscellaneous corrections to EC-GSM-IoT 13.4.0
3GPP