6 Mapping of logical channels onto physical channels

3GPP45.002GSM/EDGE Multiplexing and multiple access on the radio pathRelease 17TS

6.1 General

The detailed mapping of logical channels onto physical channels is defined in the following sections. Subclause 6.2 defines the mapping from TDMA frame number (FN) to radio frequency channel (RFCH). Subclause 6.3 defines the mapping of the physical channel onto TDMA frame number. Subclause 6.4 lists the permitted channel combinations and subclause 6.5 defines the operation of channels and channel combinations.

In case of VAMOS subchannels, the mapping of the logical channels onto the physical channels in uplink and downlink is done as defined for the corresponding TCH channels in subclauses 6.2 and 6.3. In downlink if 2 VAMOS subchannels have bursts scheduled for transmission on a given timeslot in a given TDMA frame and on a given ARFCN, then the bits from the 2 VAMOS subchannels are mapped on to AQPSK symbols (see subclause 5.2.3).

6.2 Mapping in frequency of logical channels onto physical channels

6.2.1 General

The parameters used in the function which maps TDMA frame number onto radio frequency channel are defined in subclause 6.2.2. The definition of the actual mapping function, or as it is termed, hopping sequence generation is given in subclause 6.2.3.

In CTS, the specific mapping in frequency depends on the start condition defined by the parameters given in subclause 6.2.2. The hopping sequence generation for CTS is given in subclause 6.2.3.

6.2.2 Parameters

The following parameters are required in the mapping from TDMA frame number to radio frequency channel for a given assigned channel.

General parameters of the BTS, specific to one BTS, and broadcast in the (EC-)BCCH, (EC-)SCH and FCCH:

i) CA: Cell allocation of radio frequency channels.

ii) FN: TDMA frame number, derived from information,

Broadcast in the SCH, see subclause 3.3.2.2.1.

For COMPACT: Broadcast in the CSCH, see subclause 3.3.2.2.2.

For EC-GSM-IoT: Broadcast in the EC-SCH, derived from the timing of FCCH bursts, and included within assignment message, see subclause 3.3.2.2.3.

Specific parameters of the channel, defined in the channel assignment message:

i) MA: Mobile allocation of radio frequency channels, defines the set of radio frequency channels to be used in the mobiles hopping sequence. The MA contains N radio frequency channels, where 1  N  64.

For COMPACT, the reduced MA (see 3GPP TS 44.060) shall be used for a fixed amount of data blocks, see section 6.2.4.

For EC-GSM-IoT, the EC_MA_NUMBER (see 3GPP TS 44.060) is included in the channel assignment message. The EC_MA_NUMBER is defined in EC SI where the MA is included.

ii) MAIO: Mobile allocation index offset.(0 to N‑1, 6 bits).

For COMPACT, MAIO_2 shall be used for the data blocks using the reduced MA.

For EC-GSM-IoT, the EC_MA_NUMBER (see 3GPP TS 44.060) is included in the channel assignment message. The EC_MA_NUMBER is defined in EC SI where the MAIO is included.

iii) HSN: Hopping sequence (generator) number (0 to 63, 6 bits).

For EC-GSM-IoT, the EC_MA_NUMBER (see 3GPP TS 44.060) is included in the channel assignment message. The EC_MA_NUMBER is defined in EC SI where the HSN is included.

In CTS, the following parameters are required in the mapping to radio frequency channel for a CTS-FP and CTS-MS pair. They are given by the CTS-FP to the CTS-MS during the non-hopping access procedure :

i) VA: the vector a defines the elements which are used from the shift register to generate the codeword. The vector a shall be randomly chosen upon up to 16 non-repeating integer elements where 0 £ a_i < 16 and a_i ¹ a_j for i ¹ j.

ii) VV: the elements of vector v are added modulo 2 to the codeword from the shift register. For vector v, up to 16 binary elements shall be chosen randomly.

NOTE: The length of the vectors a and v is dependent on the number of frequencies used for the hopping and can be truncated according to the number of frequencies used (see vi) below).

iii) CSR: current shift register contents. In order that a CTS-MS is able to synchronize on a running hopping sequence the CTS-FP transmits the CSR.

iv) TFHC1: value of counter TFHC1.

v) TFHC2: value of counter TFHC2.

vi) TFH carrier list (see 3GPP TS 45.056): ordered list of frequencies, with 1^st freq referenced by the frequency index 1, 2^nd frequency referenced by the frequency index 2, etc.

The number of frequencies in the TFH carrier list, NF shall be computed. The number of elements to be taken from the vectors a and v shall be determined by the function élog₂NFù

vii) VC: the vector c is the base sequence to map the codeword. It shall be randomly chosen upon NF non-repeating integer elements:
c = {c₀, c₁, … , c_NF-1}, 0 £ c_i < NF and c_i ¹ c_j for i ¹ j.

6.2.3 Hopping sequence generation

For a given set of parameters, the index to an absolute radio frequency channel number (ARFCN) within the mobile allocation (MAI from 0 to N‑1, where MAI=0 represents the lowest ARFCN in the mobile allocation, ARFCN is in the range 0 to 1023 and the frequency value can be determined according to 3GPP TS 45.005), is obtained with the following algorithm:

if HSN = 0 (cyclic hopping) then:

MAI, integer (0 .. N‑1) : MAI = (FN + MAIO) modulo N

else:

M, integer (0 .. 152) : M = T2 + RNTABLE((HSN xor T1R) + T3)

S, integer (0 .. N‑1) : M’ = M modulo (2 ^ NBIN)

T’ = T3 modulo (2 ^ NBIN)

if M’ < N then:

S = M’

else:

S = (M’+T’) modulo N

MAI, integer (0 .. N‑1) : MAI = (S + MAIO) modulo N

NOTE: Due to the procedure used by the mobile for measurement reporting when DTX is used, the use of cyclic hopping where (N)mod 13 = 0 should be avoided.

where:

T1R: time parameter T1, reduced modulo 64 (6 bits)

T3: time parameter, from 0 to 50 (6 bits)

T2: time parameter, from 0 to 25 (5 bits)

NBIN: number of bits required to represent N = INTEGER(log2(N)+1)

^: raised to the power of

xor: bit‑wise exclusive or of 8 bit binary operands

RNTABLE: Table of 114 integer numbers, defined below:

Address	Contents
000…009:	48,	98,	63,	1,	36,	95,	78,	102,	94,	73,
010…019:	0,	64,	25,	81,	76,	59,	124,	23,	104,	100,
020…029:	101,	47,	118,	85,	18,	56,	96,	86,	54,	2,
030…039:	80,	34,	127,	13,	6,	89,	57,	103,	12,	74,
040…049:	55,	111,	75,	38,	109,	71,	112,	29,	11,	88,
050…059:	87,	19,	3,	68,	110,	26,	33,	31,	8,	45,
060…069:	82,	58,	40,	107,	32,	5,	106,	92,	62,	67,
070…079:	77,	108,	122,	37,	60,	66,	121,	42,	51,	126,
080…089:	117,	114,	4,	90,	43,	52,	53,	113,	120,	72,
090…099:	16,	49,	7,	79,	119,	61,	22,	84,	9,	97,
100…109:	91,	15,	21,	24,	46,	39,	93,	105,	65,	70,
110…113:	125,	99,	17,	123,

The hopping sequence generation algorithm is represented diagrammatically in figure 6.

This algorithm applies also to COMPACT and EC-GSM-IoT, whereby the parameters T1, T2 and T3 shall be calculated from FN.

In CTS, the general structure of the hopping sequence generation algorithm is shown in figure 6a, with the example of vector a = (a₀, a₁, a₂, a₃) = (5, 8, 2, 11) and NF = 9. It consists of a 16 bit linear feedback shift register and two counters. The shift register in the CTS-FP shall be initialized with a random number which shall not be zero. The counter TFHC1 counts modulo NF the number of TDMA frames. The overflow of this counter causes a shift in the shift register. The counter TFHC2 counts modulo NF the number of shifts.

The elements which are used from the shift register to generate the codeword are defined by the vector a. The codeword is built using a modulo 2 addition of these elements and the elements of vector v . Before mapping the codeword into a sequence, the value of the counter TFHC2 is added modulo NF. The mapping is done by a modulo NF addition to the base sequence c. This results in a sequence containing NF elements, each element representing one frequency index in the TFH list. The value of counter TFHC1 points to the current frequency index to use.

6.2.4 Specific cases

On the RFCH carrying a BCCH (C0), frequency hopping is not permitted on any timeslot supporting a BCCH according to table 3 of clause 7. A non‑hopping radio frequency channel sequence is characterized by a mobile allocation consisting of only one radio frequency channel, i.e. with N=1, MAIO=0. In this instance sequence generation is unaffected by the value of the value HSN.

For COMPACT, frequency hopping is not permitted on CPBCCH or CPCCCH for a specific amount of N_CCCH_NH blocks according to the ordered list described in subclause 6.3.2.1. If CPCCCH is defined as frequency hopping, those blocks use MAI = MAIO.

For COMPACT, on other frequency hopping channels, the reduced MA and MAIO_2 shall be used for a specific amount of N_CCCH_NH blocks according to the ordered list described in subclause 6.3.2.1.

For COMPACT, in case the optional information elements reduced MA and MAIO_2 are not present in the assignment message and the MA and MAIO information elements are present in the assignment message, then the MS shall hop in all allocated time slots according to the MA and MAIO.

6.2.5 Change in the frequency allocation of a base transceiver station

The consequence of adding or removing a number of radio frequency channels in a base transceiver station is a modification of the cell allocation (CA) and the mobile allocation (MA). In order to achieve this without disruption to mobile stations with currently assigned channels it is necessary to send a message to all mobiles with assigned channels. The message, as defined in 3GPP TS 44.018, will contain a new cell allocation (if necessary), mobile allocation and a time (in the form of a TDMA frame number) at which the change is to occur. A new cell allocation may not be necessary if channels are only being removed, and not added.

6.2.6 Frequency assignment in CTS

The CTSBCH (CTSBCH-FB and CTSBCH-SB) shall always be mapped on the CTSBCH RF channel (designated as C0 in table 8 of clause 7).

The CTSPCH, CTSARCH and CTSAGCH shall be mapped on the predefined set of carriers called TFH carrier list (designated by C0… Cn in Clause 7 Table 8) by the CTS frequency hopping algorithm specified in subclauses 6.2.2 and 6.2.3. However, the CTSARCH and CTSAGCH shall be mapped on the CTSBCH RF channel for the specific case of the non-hopping access procedure specified in 3GPP TS 44.056; the block TDMA frame mapping for these exceptions is specified in clause 7 table 8. The methods for the determination of the CTSBCH RF channel and the TFH carrier list are defined in 3GPP TS 45.056.

The TCH, FACCH and SACCH used for a CTS dedicated connection shall always be mapped on the TFH carrier list (C0..Cn) by the CTS frequency hopping algorithm. However, one exception is specified in the case of the CTS enrolment and attachment of a CTS-MS (see 3GPP TS 44.056), where a non-hopping access procedure is used; in these particular cases, the dedicated connection shall be used in non-hopping mode and the TCH, FACCH and SACCH shall be mapped on the CTSBCH RF channel (C0).

6.2.7 Mapping restrictions in downlink multi-carrier configurations

In DLMC configurations, restrictions of the mapping in frequency of logical channels onto physical channels may apply. The restrictions apply on a radio block basis to the carriers that are not selected. In case one or more of the assigned carriers belong to a group of selected carriers in a certain radio block period, the mobile shall monitor the assigned PDCHs on these carriers.

Which carriers that are selected is determined in each radio block period. I.e. all carriers where PDCHs are assigned during the radio block period are included in the carrier selection method. The carrier selection method is thus independent on the number of PDCHs assigned to any given carrier.

Whether or not any restrictions apply is dependent on the maximum DLMC carrier frequency spacing supported by the mobile station (see 3GPP TS 45.005) and the ARFCNs used by the assigned carriers during a given radio block period.

The method that determines which carriers belong to the group of selected carriers is defined below. All carriers with assigned numbers (see 3GPP TS 44.060) in the returned interval, selected_min to selected_max, belong to the group of selected carriers in the applicable radio block period.

In case carriers are assigned in two frequency bands, the method applies separately to each frequency band.

In case of non-contiguous intra-band reception, the method shall be first called with 2 * max_sep as the last argument to check if all carriers can be received. If this is the case, nothing more needs to be done. Otherwise the method shall be called twice with max_sep as the last argument, excluding the carriers selected by the first call (by different arfcn and num_carriers parameters) in the second call.

The method is exemplified in Annex F.

CARRIER_SELECTION (arfcn, num_tdma_frames, num_carriers, max_sep)

selected_min = selected_max = anchor = 1

while anchor <= num_carriers

current_min = current_max = anchor

for i = 1 to num_tdma_frames

min_arfcn[i] = max_arfcn[i] = arfcn[i][anchor]

for candidate = anchor + 1 to num_carriers

for i = 1 to num_tdma_frames

if max(max_arfcn[i], arfcn[i][candidate]) – min(min_arfcn[i], arfcn[i][candidate]) > max_sep

i = num_tdma_frames + 1

break

if i == num_tdma_frames

for j = 1 to num_tdma_frames

min_arfcn[j] = min(min_arfcn[j], arfcn[j][candidate])

max_arfcn[j] = max(max_arfcn[j], arfcn[j][candidate])

current_max = current_max + 1

else

break

if current_max – current_min > selected_max – selected_min

selected_min = current_min

selected_max = current_max

anchor = candidate

return (selected_min, selected_max)

where:

– arfcn[1..num_tdma_frames][1..num_carriers]: Two-dimensional vector containing the ARFCNs for all carriers subject to selection in each TDMA frame. The carriers are ordered according to the assigned carrier number (see 3GPP TS 44.060) with the lowest numbered carrier in arfcn[1..num_tdma_frames][1], and the highest numbered carrier in arfcn[1..num_tdma_frames][num_carriers].

– num_tdma_frames: Number of TDMA frames per radio block period, 4 in case of BTTI mode, 2 in case of RTTI mode.

– num_carriers: Number of carriers where PDCHs are assigned in a DLMC configuration.

– max_sep: Maximum DLMC carrier frequency spacing supported by the MS (see 3GPP TS 45.005).

6.3 Mapping in time of logical channels onto physical channels

6.3.1 Mapping in time of circuit switched logical channels onto physical channels

6.3.1.1 General

The mapping in time of circuit switched logical channels is defined in the tables of clause 7, which also defines the relationship of the air interface frames to the multiframe.

If assigned to a mobile station indicating support for VAMOS (see 3GPP TS 24.008), the traffic channel and its associated control channels shall be mapped as described in the table below:

Table 6.3-1. Mapping of traffic and associated control channels onto TDMA frames for VAMOS mobiles.

VAMOS mobile support level	Assigned TSC set	Mapping of traffic and associated control channels on to TDMA frames
VAMOS I	TSC set 1, 2, 3 or 4	Table 1 in clause 7
VAMOS II/III	TSC set 1 or 3	Table 1 in clause 7
VAMOS II/III	TSC set 2 or 4	Table 1a in clause 7
NOTE: The use of TSC set 3 and TSC set 4 is only applicable for mobile stations indicating support for Extended TSC sets, see 3GPP TS 24.008.

6.3.1.2 Key to the mapping table of clause 7

The following relates to the tables of clause 7. The columns headed:

i) "Channel designation" gives the precise acronym for the channel to which the mapping applies.

ii) "Sub‑channel number" identifies the particular sub‑channel being defined where a basic physical channel supports more than one channel of this type.

iii) "Direction" defines whether the mapping given applies identically to downlink and uplink (D&U), or to downlink (D) or uplink (U) only.

iv) "Allowable timeslots assignments" defines whether the channel can be supported on, or assigned to, any of the timeslots, or only on specific timeslots.

v) "Allowable RF channel assignments" defines whether the channel can use any or all of the radio frequency channels in the cell allocation (CA), or only the BCCH carrier (C0). It should be noted that any allocated channel Cx within CA could be any radio frequency channel, and that no ordering of radio frequency channel number is implied. For example, allocated channel C0 need not have the lowest radio frequency channel number of the allocation.

vi) "Burst type" defines which type of burst as defined in clause 5.2 is to be used for the physical channel.

vii) "Repeat length in TDMA frames" defines how many TDMA frames occur before the mapping for the interleaved blocks repeats itself e.g. 51.

viii) "Interleaved block TDMA frame mapping" defines, within the parentheses, the TDMA frames used by each interleaved block (e.g. 0..3). The numbers given equate to the TDMA frame number (FN) modulo the number of TDMA frames per repeat length; Therefore, the frame is utilized when:

TDMA frame mapping number = (FN)mod repeat length given

Where there is more than one block shown, each block is given a separate designation e.g. B0, B1. Where diagonal interleaving is employed then all of the TDMA frames included in the block are given, and hence the same TDMA frame number can appear more than once (see 3GPP TS 45.003). Also, for E-TCH/F28.8, E-TCH/F32.0 and E-TCH/F43.2, the same frame number appears for the inband signalling message and for several interleaved blocks. It should be noted that the frame mapping for the SACCH/T channel differs according to the timeslot assigned in order to lower the peak processing requirements of the BSS.

6.3.1.3 Mapping of BCCH data

In order to facilitate the MS operation, it is necessary to transmit some System Information messages in defined multiframes and defined blocks within one multiframe, as follows (where TC = (FN DIV 51) mod (8)). Also for some System Information messages, the position where they are transmitted is contained in other System Information messages:

Table 6.3-2.System Information messages in defined multiframes and defined blocks within one multiframe.

System Information Message	Sent when TC =	Allocation
Type 1	0	BCCH Norm
Type 2	1	BCCH Norm
Type 2 bis	5	BCCH Norm
Type 2 ter	5 or 4	BCCH Norm
Type 2 quater	5 or 4 or 5	BCCH Norm BCCH Ext
Type 2n	4 or 4	BCCH Norm BCCH Ext
Type 3	2 and 6	BCCH Norm
Type 4	3 and 7	BCCH Norm
Type 7	7	BCCH Ext
Type 8	3	BCCH Ext
Type 9	4	BCCH Norm
Type 13	4 or 0	BCCH norm BCCH Ext
Type 13 alt	4 or 0	BCCH norm BCCH Ext
Type 15	4 or 1	BCCH Norm BCCH Ext
Type 16	6	BCCH Ext
Type 17	2	BCCH Ext
Type 18	Not fixed	Not fixed
Type 19	Not Fixed	Not Fixed
Type 20	Not fixed	Not fixed
Type 21	4 or 4	BCCH Norm BCCH Ext
Type 22	2 and 6	BCCH Ext
Type 23	1 or 5	BCCH Ext

This subclause defines requirements on minimum scheduling: the network may send any System Information message when sending of a specific System Information message is not required. The following rules apply:

i) BCCH Ext may share the resource with PCH and AGCH (see subclause 6.5.1).

ii) System Information Type 1 needs to be sent if frequency hopping is in use or when the NCH is present in a cell. If the MS finds another message on BCCH Norm when TC = 0, it can assume that System Information Type 1 is not in use.

iii) System information type 2 bis or 2 ter messages are sent if needed, as determined by the system operator. If only one of them is needed, it is sent when TC = 5. If both are needed, 2bis is sent when TC = 5 and 2ter is sent at least once within any of 4 consecutive occurrences of TC = 4. A SI 2 message will be sent at least every time TC = 1. System information type 2 quater is sent if needed, as determined by the system operator. If sent on BCCH Norm, it shall be sent when TC = 5 if neither of 2bis and 2ter are used, otherwise it shall be sent at least once within any of 4 consecutive occurrences of TC = 4. If sent on BCCH Ext, it is sent at least once within any of 4 consecutive occurrences of TC = 5.

iv) The definitions of BCCH Norm and BCCH Ext are given in table 3 of clause 7.

v) Use of System Information type 7 and 8 is not always necessary. It is necessary if System Information type 4 does not contain all information needed for cell selection and reselection.

vi) System Information type 9 is sent in those blocks with TC = 4 which are specified in system information type 3 as defined in 3GPP TS 44.018.

vii) System Information type 13 is only related to the GPRS service. System Information Type 13 need only be sent if GPRS support is indicated in one or more of System Information Type 3 or 4 or 7 or 8 messages. These messages also indicate if the message is sent on the BCCH Norm or if the message is transmitted on the BCCH Ext. In the case that the message is sent on the BCCH Norm, it is sent at least once within any of 4 consecutive occurrences of TC=4.

viii) System Information type 16 and 17 are only related to the SoLSA service. They should not be sent in a cell where network sharing is used (see rule xv).

ix) System Information type 18 and 20 are sent in order to transmit non-GSM broadcast information. The frequency with which they are sent is determined by the system operator. System Information type 9 identifies the scheduling of System Information type 18 and 20 messages.

x) System Information Type 19 is sent if COMPACT neighbours exist. If System Information Type 19 is present, then its scheduling shall be indicated in System Information Type 9.

xi) System Information Type 15 is broadcast if dynamic ARFCN mapping is used in the PLMN. If sent on BCCH Norm, it is sent at least once within any of 4 consecutive occurrences of TC = 4. If sent on BCCH Ext, it is sent at least once within any of 4 consecutive occurrences of TC = 1.

xii) System Information type 13 alt is only related to the GERAN Iu mode. System Information Type 13 alt need only be sent if GERAN Iu mode support is indicated in one or more of System Information Type 3 or 4 or 7 or 8 messages and SI 13 is not broadcast. These messages also indicate if the message is sent on the BCCH Norm or if the message is transmitted on the BCCH Ext. In the case that the message is sent on the BCCH Norm, it is sent at least once within any of 4 consecutive occurrences of TC = 4.

xiii) System Information Type 2n is optionally sent on BCCH Norm or BCCH Ext if needed, as determined by the system operator. In the case that the message is sent on the BCCH Norm, it is sent at least once within any of 4 consecutive occurrences of TC = 4. If the message is sent on BCCH Ext, it is sent at least once within any of 2 consecutive occurrences of TC = 4.

xiv) System Information Type 21 is optionally sent on BCCH Norm or BCCH Ext, as determined by the system operator. If Extended Access Barring is in use in the cell then this message is sent at least once within any of 4 consecutive occurrences of TC = 4 regardless if it is sent on BCCH Norm or BCCH Ext. If BCCH Ext is used in a cell then this message shall only be sent on BCCH Ext.

xv) System Information Type 22 is sent if network sharing is in use in the cell. It should not be sent in a cell where SoLSA is used (see rule viii). System Information Type 22 instances shall be sent on BCCH Ext within any occurrence of TC =2 and TC=6.

xvi) System Information Type 23 is sent if network sharing is in use in the cell, according to System Information Type 22 indication. System Information Type 23 instances shall be sent on BCCH Ext at least twice within any of 4 consecutive occurrences of either TC=1 or TC=5.

All the allowable timeslot assignments in a frame (see table 3 of clause 7) shall contain the same information.

6.3.1.4 Mapping of SID Frames

When the DTX mode of operation is active, it is required to transmit Silence Descriptor (SID) information, or equivalent dummy information, during the SACCH/T block period (104 TDMA frames). As the SID frames do not constitute a logical channel and their use is specific to DTX operation, the mapping of SID frames onto the TDMA frames is specified in 3GPP TS 45.008.

6.3.2 Mapping in time of packet logical channels onto physical channels

6.3.2.1 General

A physical channel allocated to carry packet logical channels is called a packet data channel (PDCH). A PDCH shall carry packet logical channels only.

In RTTI configuration, physical channels are paired, forming PDCH-pairs. The two physical channels shall have the same parameters (see subclause 5.6.3) except for the timeslot number (TN). The two PDCHs constituting a PDCH-pair shall be located on the same carrier. The two PDCHs constituting a PDCH-pair need not be contiguous. In each direction, physical channels shall be assigned so that PDCH-pairs do not partially overlap.

On a given PDCH, PDTCHs in both BTTI configuration and RTTI configuration (assigned to different MSs) may be carried. Alternatively, both PDCHs forming a PDCH-pair may be assigned to only carry PDTCHs in RTTI configuration.

Packet switched logical channels are mapped dynamically onto a 52-multiframe.

– For a PDCH/F in BTTI configuration the 52-multiframe consists of 12 blocks of 4 consecutive frames, 2 idle frames and 2 frames used for the PTCCH (see 3GPP TS 45.010), as shown in Figure 9. Table 6 in clause 7, indicates the frame numbers for each of the blocks (B0…B11) transmitted in the multiframe. The ordered list of block is defined as B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11.

– For PDCH/H, the 52-multiframe consists of 6 blocks of 4 frames each, and two idle frames. Table 6 in clause 7 indicates the frame numbers for each of the blocks (B0…B5) transmitted in the multiframe.

– For a PDCH-pair in RTTI configuration the 52-multiframe consists of 24 RTTI blocks of 2 consecutive frames, plus 2 idle frames and 2 frames used for the PTCCH (see 3GPP TS 45.010) on each PDCH of the PDCH-pair, as shown in Figure 9a. Table 6 in clause 7 indicates the frame numbers for each of the 24 RTTI blocks (B0_a, B0_b, …B11_a, B11_b) transmitted in the 52-multiframe.

– For a PDCH/F, when in EC operation, the 52-multiframe consists of 12 BTTI blocks of 4 consecutive frames, and 4 idle frames, as shown in Figure 9b. In case blind physical layer transmissions for EC-PDTCH/F or EC-PACCH/F are used, either one BTTI block (for Coverage Class 2) or multiple BTTI blocks (for Coverage Classes higher than 2) constitute the block that is mapped onto the physical channel, see Figure 9b. For an uplink EC TBF assigned two PDCHs, compact burst mapping shall be used (see 3GPP TS 45.001). In this case, the block that is mapped onto the physical channel is not an aggregate of BTTI blocks constructed using bursts from 4 consecutive TDMA frames. Table 6a in clause 7 indicates the frame numbers of each of the blocks depending on the downlink Coverage Class or uplink Coverage Class respectively.

– Depending on the intended coverage range, EC-PDTCH/F and EC-PACCH/F are defined for different Coverage Classes (CCs), see 3GPP TS 43.064. Depending on the CC and the number of PDCHs assigned for EC operation (see 3GPP 44.018 and 3GPP 44.060) one EC-PDTCH/F and/or EC-PACCH/F are mapped onto different number of PDCHs according to:

– CC1: 1 PDCH

– CC2, CC3, CC4: 4 PDCHs or 2 PDCHs

The PDCHs that an EC-PDTCH/F and/or EC-PACCH/F are mapped to are contiguous, see Table 6a in clause 7.

A block allocated to a given logical channel comprises one radio block, or in the case of uplink only, 4 random access bursts. The type of channel may vary on a block-by-block basis. In case of EC operation a block allocated to an EC-channel can consist of blind physical layer transmissions of a radio block. The number of blind physical layer transmissions is dependent on the assigned Coverage Class.

In the downlink direction, the logical channel type shall be indicated by the message type contained in the block header part for GPRS, or indicated by Stealing Flags for EGPRS and EGPRS2, or detected by the MS in case of EC operation.

In the uplink part for channels other than (EC-)PACCH transmitted as access bursts or PRACH, or CPRACH or (EC-)RACH, the logical channel type shall be indicated by the message type contained in the block header part for GPRS, or indicated by Stealing Flags for EGPRS and EGPRS2, or known by the BTS in case of EC operation. For (EC-)PACCH transmitted as access bursts, the logical channel type is indicated by the corresponding polling message on the downlink (see 3GPP TS 44.060). For the PRACH or CPRACH case the logical channel type is indicated by the USF (see 3GPP TS 44.060), set on the downlink on a block by block basis.

For COMPACT, timeslot mapping and rotation of the control channels is used such that control channels belonging to a serving time group are rotated over odd timeslot numbers as follows: 7, 5, 3, 1, 7, 5  . The rotation occurs between frame numbers (FN) mod 52 = 3 and 4. The mapping of the control channels on timeslot numbers is defined by the following formula:

– for 0  FN mod 52  3, TN = ((6 x ((FN div 52) mod 4)) + 1 + (2 x TG)) mod 8;

– for 4  FN mod 52  51, TN = ((6 x ((FN div 52) mod 4)) + 7 + (2 x TG)) mod 8.

Packet switched logical channels PDTCH, PACCH, and PTCCH are never rotated.

6.3.2.2 Mapping of the uplink channels

6.3.2.2.1 Mapping of (EC-)PDTCH/U and (EC-)PACCH/U

6.3.2.2.1.1 BTTI configuration

The PDCH’s where the MS may expect occurrence of its (EC-)PDTCH/U(s) or (EC-)PACCH/U for a mobile originated transfer is indicated in resource assignment messages (see 3GPP TS 44.060 and 3GPP 44.018). (EC-)PACCH/U shall be allocated respecting the resources assigned to the MS and the MS multislot class. For each PDCH assigned to the MS, an Uplink State Flag (R0… R7) is given to the MS. An exception is when using Fixed Uplink Allocation where the Uplink State Flag is not used to allocate resources, and hence no Uplink State Flag is given to the MS.

In case of USF based allocation, the occurrence of the PDTCH/U and/or the PACCH/U at given block(s) Bx (where Bx = B0…Bn; n=5 for the PDTCH/HU and n=11 for the PDTCH/FU) in the 52-multiframe structure for a given MS on a given PDCH shall be indicated by the value of the Uplink State Flag (USF) contained in the header of the preceding block transmitted in the downlink of the same PDCH (or in the case of shifted USF on the downlink of a PDCH with a relationship to the uplink PDCH as defined in 3GPP TS 44.060), that is to say B(x-1) in the same multiframe if x1 or B(n) in the previous multiframe if x=0. If the USF in block B(x‑1) indicates that block B(x) shall be used by an MS for which the USF_GRANULARITY is set to 1 (corresponding to 4 blocks) in the last assignment message, that MS shall also use the three following blocks. The USF corresponding to the last three blocks shall be set to an unused value. The MS may transmit a PDTCH block or a PACCH block on any of the uplink blocks used by the MS. The occurrence of the PACCH/U associated to a PDTCH/D shall be indicated by the network by polling the MS (see 3GPP TS 44.060).

In case of Fixed Uplink Allocation, the occurrence of the EC‑PDTCH/U at given block(s) in the 52-multiframe structure for a given MS on given PDCH(s) shall be indicated by an EC Immediate Assignment Type 1, EC-Immediate Assignment Type 2, EC Packet Uplink Ack/Nack or EC Packet Uplink Assignment message. The number of blocks available per 52-multiframe depends on the uplink Coverage Class and the number of PDCHs assigned for EC operation as shown in table 6.3-2. The mapping of each block onto the 52-multiframe is shown in table 6a, and illustrated in figure 9b, figure 9c, figure 9d and figure 9e.

Table 6.3-3: Blocks per 52-multiframe depending on uplink Coverage Class for EC-GSM-IoT

Uplink Coverage Class	Number of PDCH assigned	Number of blocks per 52-multiframe
1	1	12
2	4	12
3	4	6
4	4	3
5	4	1
2	2	6
3	2	3
4	2	3/21
5	2	1/22
Note 1: This corresponds to 3 blocks per 2*52-multiframes. Note 2: This corresponds to 1 block per 2*52-multiframes.

The occurrence of the EC-PACCH/U associated with EC-PDTCH/D shall be indicated by the network by polling the MS (see 3GPP TS 44.060).

NOTE 1: This subclause specifies how the network shall signal that the MS is allowed to use the uplink. The operation of the MS is specified in 3GPP TS 44.060. In particular cases of extended dynamic allocation or exclusive allocation, the MS may not need to monitor the USF on all the downlink timeslots corresponding to the assigned uplink PDCHs. In case of Fixed Uplink Allocation the MS shall not monitor the USF.

NOTE 2: The PDCH/HU is only assigned in exclusive allocation (see 3GPP TS 44.060).

NOTE 3: A MS using packet uplink traffic channels mapped to the same physical channel than an uplink PCCCH in extended dynamic allocation MAC mode is not required to check if allocated uplink PDTCH/U or PACCH/U blocks also belong to the PRACH.

In a dual carrier or a DLMC configuration, the uplink block(s) shall be allocated on the corresponding physical channel on which the USF or poll (see 3GPP TS 44.060) is received. Uplink blocks shall not be allocated on physical channels having different frequency domain descriptions (see subclause 5.4) simultaneously in the same block period.

For COMPACT, USF_GRANULARITY should be set to 0 (corresponding to 1 block) for dynamic allocation for the following cases:

i) for odd timeslot numbers (TN) 1, 3, 5, and 7 in nominal and large cells;

ii) for even timeslot numbers (TN) 0, 2, 4, and 6 in large cells.

6.3.2.2.1.2 RTTI configuration

The PDCH-pairs where the MS may expect occurrence of its PDTCH/U(s) or PACCH/U for a mobile originated transfer are indicated in resource assignment messages (see 3GPP TS 44.060). PACCH/U shall be allocated respecting the resources assigned to the MS and the MS multislot class.

For each PDCH-pair assigned to the MS, one or two USFs (R0… R7) are given to the MS. For each assigned uplink PDCH-pair the network may signal in resource assignment messages a "corresponding downlink PDCH-pair" where the USF is monitored. The timeslot numbers of the PDCHs constituting the corresponding downlink PDCH-pair may be different from those of the PDCHs constituting the uplink PDCH-pair. If no indication is provided, the corresponding downlink PDCH-pair shall be the one with the same timeslot numbers as the uplink PDCH-pair.

For an assigned uplink PDCH-pair, for the transmission of the USF the network can use one of two modes:

– BTTI USF mode: USFs are sent in a basic radio block period, i.e. a USF is mapped on four bursts transmitted on one of the PDCHs of a downlink PDCH-pair during four consecutive TDMA frames;

– RTTI USF mode: a USF is sent in a reduced radio block period, i.e. a USF is mapped on four bursts transmitted on both PDCHs of a downlink PDCH-pair during two consecutive TDMA frames.

The network shall signal the USF mode in the resource assignment messages (see 3GPP TS 44.060). The USF mode shall be the same for all the uplink PDCH-pairs assigned to one mobile station. Also, on a given downlink PDCH-pair, all USFs shall be sent with the same USF mode.

If the BTTI USF mode is used, for each PDCH-pair assigned to the MS the network shall give two USFs (R0… R7) to the MS, one for each PDCH of the corresponding downlink PDCH-pair. If the RTTI USF mode is used, for each PDCH-pair assigned the network shall give to the MS one Uplink State Flag (R0… R7) to the MS.

When a given downlink PDCH is configured to provide USFs for PDTCHs operating in RTTI configuration (as part of a corresponding downlink PDCH-pair) and PDTCHs operating in BTTI configuration, the BTTI USF mode shall be used on both PDCHs of the corresponding downlink PDCH-pair to schedule uplink blocks for mobile stations using RTTI configuration. Additionally, if any of the downlink PDTCHs mapped onto either PDCH of a corresponding PDCH-pair operates in BTTI configuration, the BTTI USF mode shall be used on both PDCHs. In this case, if x1, the first uplink RTTI radio block Bx_a shall be allocated by the USF contained in block B(x-1) of the downlink PDCH having the lowest TN and the second uplink RTTI radio block Bx_b shall be allocated by the USF contained in block B(x-1) of the highest numbered PDCH TN of the "corresponding downlink PDCH-pair" to the uplink PDCH-pair (see Figure 9a and 3GPP TS 44.060). If x=0 the corresponding USFs will be carried within block B11 of the previous 52-multiframe. In case of dual carrier or a DLMC configuration in the downlink, this same relationship between USFs and uplink RTTI radio blocks shall apply. If the USF_GRANULARITY is set to 1 (corresponding to 4 blocks) in the last assignment message, the MS shall also use the next three consecutive RTTI radio blocks of sub-index a or sub-index b (according to the PDCH in which the USF was received), see 3GPP TS 44.060. The USF corresponding to the last three blocks shall be set to an unused value.

When on a downlink PDCH belonging to a PDCH-pair a USF is sent scheduling an uplink block belonging to an MS in BTTI configuration, the USF on the other PDCH of the "corresponding PDCH-pair" shall also schedule an uplink block belonging to an MS in BTTI configuration.

When both PDCHs of a corresponding downlink PDCH-pair are configured to provide USFs for uplink PDTCHs all operating in RTTI configuration, and when all the downlink PDTCHs mapped onto both PDCHs operate in RTTI configuration, the RTTI USF mode shall be used on both PDCHs. In this case, if x1, the uplink RTTI radio block Bx_a shall be allocated by the USF contained in RTTI block B(x-1)_b and uplink RTTI radio block Bx_b shall be allocated by the USF contained in RTTI block Bx_a of the "corresponding downlink PDCH-pair" to the uplink PDCH-pair (see Figure 9a and 3GPP TS 44.060). If x=0 the USFs will be carried within RTTI block B11_b of the previous 52-multiframe and B0_a respectively. If the USF_GRANULARITY is set to 1 (corresponding to 4 blocks) in the last assignment message, the MS shall also use the next three consecutive RTTI radio blocks, see 3GPP TS 44.060. The USF corresponding to the last three blocks shall be set to an unused value.

The MS may transmit a PDTCH block or a PACCH block on any of the uplink blocks allocated to the MS. The occurrence of the PACCH/U associated to a PDTCH/D shall be indicated by the network by polling the MS (see 3GPP TS 44.060).

6.3.2.2.2 Mapping of the Packet Timing Advance Control Channel (PTCCH/U)

The PDCH carrying the PTCCH/U of one MS is defined in the resource assignment message (see 3GPP TS 44.060). PTCCH/U shall be mapped to one of the time slots where PDTCH(s) are allocated to the MS. PTCCH/U shall be allocated respecting the resources assigned to the MS and the MS multislot class. An MS shall be allocated a sub-channel of the PTCCH/U (0…15) as defined in table 6 of clause 7, where the sub-channel number is equal to the Timing Advance Index (TAI) indicated in the resource allocation message (see 3GPP TS 44.060).

In a dual carrier or a DLMC configuration, an MS shall be assigned a PTCCH/U sub-channel on a physical channel having one frequency domain description (see subclause 5.4) only.

In RTTI configuration, an MS shall be assigned a PTCCH/U on only one of the physical channels comprising an uplink PDCH-pair (see subclause 6.3.2.1).

6.3.2.2.3 Mapping of the uplink PCCCH i.e. PRACH

The mapping of the PRACH is defined in table 6 of clause 7, where the possible blocks are indicated. The PRACH is dynamically allocated in groups of four PRACH blocks By (y=4x+i, i=0 ,.., 3) corresponding to one PDCH block Bx (x=0,…,11), indicated by USF=FREE in the same way as defined for PDTCH/U (see subclause 6.3.2.2.1).

Optionally, a subset of the blocks Bx can be allocated to PRACH in a fixed way. The number of allocated blocks is indicated by the parameter BS_PRACH_BLKS broadcast on the PBCCH, where BS_PRACH_BLKS=0…12. The blocks are allocated according to the ordered list defined in subclause 6.3.2.1. The blocks shall also be indicated by the USF=FREE. The MS may choose to use the BS_PRACH_BLKS or USF to determine the fixed allocated part of PRACH.

6.3.2.2.3a Mapping of the COMPACT uplink CPCCCH i.e. CPRACH

The CPRACH is dynamically or fixed allocated in the same way as defined for PRACH (see subclause 6.3.2.2.3. USF should be set equal to FREE for downlink block B0 on a serving time group when 4 time groups are assigned. Uplink blocks (other than block B1 on a serving time group) that are preceded by CPBCCH and CPCCCH blocks should be prioritized for use as CPRACH.

See Annex D for examples based on sixteen prioritized CPRACH blocks.

6.3.2.2.4 Mapping of the MBMS uplink MPRACH

The mapping of the MPRACH is defined in table 6 of clause 7, where the possible blocks are indicated. The MPRACH is dynamically allocated in groups of four MPRACH blocks By (y=4x+i, i=0 ,.., 3) corresponding to one PDCH block Bx (x=0,…,11), indicated by a value of the USF, in the same way as defined for PDTCH/U (see subclause 6.3.2.2.1). The value of the USF is signalled in the MBMS notification message (see 3GPP TS 44.060).

6.3.2.2.5 Void

6.3.2.2.6 Mapping of Overlaid CDMA sub channels

In case overlaid CDMA is used on dedicated channels (EC-PDTCH and EC-PACCH), see 3GPP TS 43.064 [6], up to four MS can be multiplexed on the same physical resource, simultaneously transmitting, using different orthogonal codes assigned by the network if four PDCHs are assigned for EC operation, see 3GPP 44.018 [10] and 3GPP TS 44.060 [11]. Else if two PDCHs are assigned for EC operation, two MS can be multiplexed on the same physical resource. The codes are applied per burst over the assigned PDCHs for EC-PDTCH and EC-PACCH in each TDMA frame from the lowest to the highest numbered assigned TN, according to Table 6.3-3, and are only applied in case blind physical layer transmissions are used (i.e. for CC2, CC3 and CC4). The code value is either 0 or 1. In case 0 is used, the burst is transmitted as if no code was applied. In case 1 is used, the whole burst is shifted in phase by  radians, see 3GPP TS 45.004 [14]. Since the code is applied over the blind physical layer transmissions within the TDMA frame, and CC2, CC3, CC4 all map to four or two PDCHs in a TDMA frame, there is no restriction on the pairing of MS on the same physical resources, of different Coverage Classes, as long as blind physical layer transmissions are used (CC2, CC3 and CC4) and the same number of PDCHs (i.e. four or two) are assigned for these MS assigned on those resources. Overlaid CDMA is only applied for transmissions on the uplink, i.e. for EC-PACCH/U and EC-PDTCH/U.

Overlaid CDMA is also specified for EC-RACH in CC5 using EDAB in the 2 TS EC-RACH format with TS7, see sub-clause 5.2.11. The first burst (burst with equal size to the active part of the normal burst) and the second burst (burst with equal size to the active part of the access burst) are transmitted using the code sequence ’01’ according to Table 6.3-3.

NOTE: This enables the network to segregate transmissions in CC4, using the 2 TS EC-RACH format without phase shift, from transmissions in CC5, since both transmissions use the same synchronization sequence TS7, see sub-clause 5.2.7.

Table 6.3-4. Overlaid CDMA codes

Overlaid CDMA code1	Code sequence2	Code sequence3
0	0000	00
1	0101	014
2	0011	–
3	0110	–
NOTE1: see 3GPP TS 44.060 [11] NOTE2: The first number in the sequence is applied to the lowest numbered assigned PDCH. The second number to the second lowest numbered assigned PDCH etc, in case four PDCHs are assigned for EC operation. NOTE 3: The first number in the sequence is applied to the lower numbered assigned PDCH and the second number to the higher numbered assigned PDCH. This code sequence is used if two PDCHs are assigned for EC operation. NOTE 4: The code sequence ’01’ applies also for EC-RACH for CC5 using EDAB in the 2 TS EC-RACH format, see sub-clause 5.2.11.

6.3.2.3 Mapping of the downlink channels

6.3.2.3.1 Mapping of the (EC-)PDTCH/D and (EC-)PACCH/D

The PDCH(s) in BTTI configuration or the PDCH-pair(s) in RTTI configuration where the MS may expect occurrence of its (EC-)PDTCH/D(s) for a mobile terminated transfer or its (EC-)PACCH/D, for both mobile originated and mobile terminated transfer, are indicated in resource assignment messages (see 3GPP TS 44.060). (EC-)PDTCH/D and (EC‑)PACCH/D can be mapped dynamically on all blocks except those used for PBCCH (see subclause 6.3.2.3.3). The logical channel type shall be indicated in the block header for GPRS, it shall be indicated by Stealing Flags for EGPRS and EGPRS2, and it shall be detected by the MS in case of EC operation. The mobile owner of the (EC‑)PDTCH/D or (EC‑)PACCH/D shall be indicated by the TFI (Temporary Flow Identity) (see 3GPP TS 44.060).

For EC-PDTCH/D and EC-PACCH/D the number of blocks available per 52-multiframe depends on the downlink Coverage Class and the number of PDCHs assigned for EC operation, and is the same as for uplink shown in table 6.3-3.

If PDTCH/D is mapped on blocks, which may be used for PCCCH and where paging may appear, the network shall only use coding schemes CS-1 to CS-4.

NOTE: This restriction is needed to avoid the expiry of the downlink signalling counter (DSC) for non-EGPRS capable mobile stations in case the network uses MCS-1 to MCS-9. CS-1 should be favoured, as it provides the strongest error protection.

6.3.2.3.2 Mapping of the PTCCH/D

The PTCCH/D is mapped as defined in table 6 of clause 7. The PTCCH/D carries signalling messages including timing advance information for MSs sharing the PTCCH/U on the same PDCH.

In a dual carrier or a DLMC configuration, an MS shall be assigned a PTCCH/D channel on a physical channel having one frequency domain description (see subclause 5.4) only.

In RTTI configuration, an MS shall be assigned a PTCCH/D on only one of the physical channels comprising a downlink PDCH-pair (see subclause 6.3.2.1). When only an uplink PDTCH is assigned to the MS, the PTCCH shall be assigned on one of the PDCHs comprising the "corresponding downlink PDCH-pair" for the uplink PDTCH (see subclause 6.3.2.2.1.2).

6.3.2.3.3 Mapping of the PBCCH

The PBCCH is mapped onto one PDCH only, indicated in the BCCH. The PBCCH is mapped on BS_PBCCH_BLKS blocks (where 1BS_PBCCH_BLKS4) per multiframe, according to the ordered list described in subclause 6.3.2.1. The blocks allocated are specified in table 6 of clause 7. The parameter BS_PBCCH_BLKS is broadcast on PBCCH in block B0 (see subclause 3.3.2.4).

6.3.2.3.3a Mapping of the COMPACT CPBCCH

The CPBCCH is mapped onto a primary COMPACT carrier on the time group indicated by TG on CSCH (see subclause 3.3.2.2). This time group is known as the serving time group and rotates over odd timeslot numbers (see subclause 6.3.2.1). The CPBCCH is mapped on BS_PBCCH_BLKS blocks (where 1BS_PBCCH_BLKS4) per multiframe, according to the ordered list described in subclause 6.3.2.1. The blocks allocated are specified in table 9 of clause 7. The parameters BS_PBCCH_BLKS is broadcast on CPBCCH in block B0 (see subclause 3.3.2.4).

See Annex D for examples based on one CPBCCH block.

When USF=FREE in downlink block B0 on a serving time group, the CPRACH is allocated in uplink block B1 after timeslot rotation. When USF has any other value in downlink block B0 on a serving time group, the uplink allocation of B1 is valid for the same timeslot, irrespective of timeslot rotation.

6.3.2.3.3b Void

6.3.2.3.4 Mapping of the PCCCH

The PCCCH and its different logical channels (PAGCH, PPCH) can be mapped dynamically and are identified by the message header. The configuration is partly fixed by some parameters broadcast by the PBCCH and defined in subclause 3.3.2.4:

a) BS_PBCCH_BLKS, that defines the number of PBCCH blocks per multiframe, according to the ordered list described in subclause 6.3.2.1, on the PDCH that carries PBCCH;

b) BS_PAG_BLKS_RES, that defines the number of blocks in addition to BS_PBCCH_BLKS, according to the ordered list described in subclause 6.3.2.1, where PPCH shall not occur on every PDCH that carries PCCCH.

PCCCH (except PPCH) can be mapped on all blocks except those used for PBCCH.

If PBCCH is allocated on timeslot k, PCCCHs shall be allocated only on timeslots n where n>k-4 and 0£n£7 in order to provide time for the MS to switch from PBCCH to PCCCH.

6.3.2.3.4a Mapping of the COMPACT CPCCCH

The CPCCCH and its different logical channels (CPAGCH, CPPCH) can be mapped dynamically and are identified by the message header. The configuration is partly fixed by some parameters broadcast by the CPBCCH and defined in subclause 3.3.2.4:

a) BS_PBCCH_BLKS, that defines the number of CPBCCH blocks per multiframe, according to the ordered list described in subclause 6.3.2.1, on the radio frequency channel that carries CPBCCH;

b) BS_PAG_BLKS_RES, that defines the number of blocks in addition to BS_PBCCH_BLKS, where CPPCH shall not occur on every radio frequency channel that carries CPCCCH. These blocks without CPPCH are allocated after CPPCH blocks according to the ordered list described in subclause 6.3.2.1.

CPCCCH (except CPPCH) can be mapped on all blocks except those used for CPBCCH.

For primary COMPACT carriers, CPCCCHs shall be allocated on the same time group as CPBCCH. CPCCCHs on secondary COMPACT carrier(s) shall be allocated on same time group as for primary COMPACT carrier.

See Annex D for examples based on three CPCCCH blocks.

6.3.2.3.4b Void

6.3.2.4 Mapping of PBCCH data

In order to facilitate the MS operation, the network is required to transmit certain types of Packet System Information (PSI) messages in specific multiframes and specific PBCCH blocks within the multiframes. The occurrence of the PSI1 message is defined by TC = (FN DIV 52) mod PSI1_REPEAT_PERIOD, where PSI1_REPEAT_PERIOD (range 1 – 16) is indicated in the SI13 message on BCCH, the PSI 1 message on PBCCH and, if present, in the Neighbour Cell parameters in PSI3 and PSI3bis messages sent on serving cell PBCCH.

The PSI1 message is transmitted at TC = 0 according to rule i) and ii) below.

The PSI messages other than the PSI1 message are divided into two groups of PSI messages. One group of PSI messages is transmitted with a low repetition rate and a second group is transmitted with a high repetition rate.

The number of PSI message instances sent with high repetition rate is indicated by the parameter PSI_COUNT_HR (range 0 to 16) in the PSI1 message. The PSI messages in this group are sent according to rule iii) below.

The number of PSI message instances sent with low repetition rate is indicated by the parameter PSI_COUNT_LR (range 0 to 63) in the PSI1 message. The PSI messages in this group are sent according to rule iv) below.

The following rules apply:

i) PSI1 shall be sent in block B0 when TC = 0;

ii) if the value of the parameter BS_PBCCH_BLKS is greater than 1, the PSI1 shall also be sent in block B6 when TC = 0;

iii) the PSI messages in the group sent with high repetition rate shall be sent in a sequence determined by the network and starting at TC = 0, using the PBCCH blocks within each multiframe, in the order of occurrence, which are not occupied according to rule i) or ii). The sequence of these PSI messages shall be repeated starting at each occurrence of TC = 0;

iv) the PSI messages in the group sent with low repetition rate shall be sent in a sequence determined by the network and continuously repeated, using the PBCCH blocks within each multiframe, in the order of occurrence, which are not occupied according to rules i) to iii) . The sequence of these PSI messages shall be restarting at FN = 0.

If there are multiple instances of a particular type of PSI message (see 3GPP TS 44.060), they shall all be sent within same group of PSI messages according to either rule iii) or iv) above. They shall be sent in a single sequence in the ascending order of the message instance number of that type of PSI message.

The same PSI message shall not occur twice within the lists defined by PSI_COUNT_LR and PSI_COUNT_HR

A full set of Packet System Information messages contains one consistent set of the messages included in PSI_COUNT_LR and one consistent set of the messages included in PSI_COUNT_HR plus the PSI1 message.

NOTE: The parameters BS_PBCCH_BLKS and PSI1_REPEAT_PERIOD_shall be selected by the network such that all PSI message present in the cell can be sent according to rules i) to iv) above. It is the responsibility of the network to optimise the broadcast of the PSI messages so that the MS can find the important parameters for cell re-selection and access as fast as possible without unnecessary power consumption. The PSI mapping scheme information can be utilised by the MS to estimate the actual minimum cell reselection time.

6.3.2.4a Mapping of COMPACT CPBCCH data

See subclause 6.3.2.4, with the exception that the CPBCCH is a stand-alone packet control channel for COMPACT.

6.3.2.4b Void

6.3.3 Mapping in time of CTS control channels onto physical channels

The mapping in time of CTS control channels is defined in table 8 of clause 7, which also defines the relationship of the air interface TDMA frames to the multiframe.

The timeslot assignment of the CTS control channel is defined hereafter.

6.3.3.1 CTSBCH timeslot assignment

For the CTSBCH, a procedure of timeslot shifting from one 52-multiframe to another is defined. The usage of this procedure is mandatory in CTS idle mode and optional in CTS dedicated mode. When the shifting procedure is not applied, the CTSBCH timeslot number shall be equal to the TNC broadcast in the current 52-multiframe CTSBCH-SB.

The following parameters are required for the timeslot shifting procedure.

Parameters broadcast in the CTSBCH-SB:

a) TNI: initial timeslot number (0 to 7, 3 bits), defined by the three LSBs (BN3, BN2, BN1) of the FPBI (specified in 3GPP TS 23.003);

b) TNSCN: timeslot number series couple number (0 to 31, 5 bits), defined by the 5 bits (BN8, …, BN4) of the FPBI. Defines the couple of timeslot number circular series (TNS_TNSCN,0, TNS_TNSCN,1) to be used to form the timeslot shifting sequence. See timeslot number series (TNS) definition in table below.

Table 1 (subclause 6.3.3): TNS_i,j definition

TNSCN	TNSTNSCN,0	TNSTNSCN,1	TNSCN	TNSTNSCN,0	TNSTNSCN,1
0	( 0, 1, 2, 4, 7, 5, 6, 3 ),	( 0, 3, 5, 7, 6, 2, 1, 4 )	16	( 0, 1, 5, 6, 7, 4, 3, 2 ),	( 0, 4, 7, 6, 2, 5, 1, 3 )
1	( 0, 1, 2, 5, 3, 6, 7, 4 ),	( 0, 4, 1, 5, 7, 6, 3, 2 )	17	( 0, 2, 1, 3, 6, 7, 5, 4 ),	( 0, 3, 7, 4, 1, 5, 6, 2 )
2	( 0, 1, 2, 6, 5, 3, 7, 4 ),	( 0, 3, 6, 7, 5, 2, 4, 1 )	18	( 0, 2, 1, 5, 6, 7, 4, 3 ),	( 0, 4, 7, 5, 1, 3, 6, 2 )
3	( 0, 1, 2, 6, 7, 5, 4, 3 ),	( 0, 3, 7, 4, 6, 2, 5, 1 )	19	( 0, 2, 3, 4, 7, 6, 5, 1 ),	( 0, 3, 1, 5, 2, 6, 7, 4 )
4	( 0, 1, 3, 2, 5, 6, 7, 4 ),	( 0, 4, 7, 6, 2, 1, 5, 3 )	20	( 0, 2, 3, 6, 7, 5, 1, 4 ),	( 0, 4, 7, 6, 3, 5, 2, 1 )
5	( 0, 1, 3, 6, 7, 5, 2, 4 ),	( 0, 3, 7, 4, 2, 6, 5, 1 )	21	( 0, 2, 3, 7, 5, 6, 4, 1 ),	( 0, 3, 6, 2, 1, 5, 7, 4 )
6	( 0, 1, 4, 2, 5, 6, 7, 3 ),	( 0, 2, 6, 3, 7, 5, 4, 1 )	22	( 0, 2, 4, 7, 3, 6, 5, 1 ),	( 0, 3, 5, 6, 7, 4, 1, 2 )
7	( 0, 1, 4, 2, 5, 7, 6, 3 ),	( 0, 4, 7, 3, 5, 6, 2, 1 )	23	( 0, 2, 5, 3, 6, 7, 4, 1 ),	( 0, 3, 7, 6, 5, 1, 2, 4 )
8	( 0, 1, 4, 2, 6, 5, 7, 3 ),	( 0, 2, 1, 5, 3, 6, 7, 4 )	24	( 0, 2, 5, 3, 7, 6, 4, 1 ),	( 0, 3, 5, 1, 2, 6, 7, 4 )
9	( 0, 1, 4, 5, 7, 3, 6, 2 ),	( 0, 3, 7, 6, 5, 2, 4, 1 )	25	( 0, 2, 6, 3, 1, 5, 7, 4 ),	( 0, 3, 4, 7, 6, 5, 1, 2 )
10	( 0, 1, 4, 6, 5, 7, 3, 2 ),	( 0, 4, 7, 5, 1, 2, 6, 3 )	26	( 0, 2, 6, 5, 1, 4, 7, 3 ),	( 0, 4, 5, 7, 6, 3, 1, 2 )
11	( 0, 1, 4, 7, 3, 5, 6, 2 ),	( 0, 4, 2, 1, 5, 7, 6, 3 )	27	( 0, 2, 6, 5, 3, 7, 4, 1 ),	( 0, 3, 6, 7, 5, 1, 2, 4 )
12	( 0, 1, 4, 7, 6, 3, 5, 2 ),	( 0, 4, 2, 1, 5, 6, 7, 3 )	28	( 0, 3, 5, 1, 2, 6, 7, 4 ),	( 0, 4, 7, 6, 5, 2, 3, 1 )
13	( 0, 1, 5, 2, 4, 7, 6, 3 ),	( 0, 3, 7, 5, 1, 4, 6, 2 )	29	( 0, 3, 5, 2, 6, 7, 4, 1 ),	( 0, 4, 7, 3, 6, 5, 1, 2 )
14	( 0, 1, 5, 2, 6, 4, 7, 3 ),	( 0, 3, 4, 5, 7, 6, 2, 1 )	30	( 0, 3, 6, 7, 4, 2, 5, 1 ),	( 0, 4, 1, 2, 6, 5, 7, 3 )
15	( 0, 1, 5, 6, 2, 4, 7, 3 ),	( 0, 3, 7, 6, 4, 5, 2, 1 )	31	( 0, 3, 7, 5, 6, 2, 4, 1 ),	( 0, 4, 7, 6, 3, 5, 1, 2 )

Parameters sent on a dedicated connection during the CTS-MS attachment:

a) TNSCO : TNS couple order (1 bit), defines together with TNSCN the ordered couple (TNS1, TNS2).

if TNSCO = 0 then (TNS1, TNS2) = (TNS_TNSCN,0, TNS_TNSCN,1)

if TNSCO = 1 then (TNS1, TNS2) = (TNS_TNSCN,1, TNS_TNSCN,0)

b) parameters to be used to form the timeslot shifting sequence.

x0 : 0 to 7, 3 bits

x1 : 0 to 7, 3 bits

x2 : 0 to 7, 3 bits

x3 : 0 to 7, 3 bits

For a given set of parameters, a unique timeslot shifting sequence of length of 8 x 51 52-multiframes is defined. The shifting sequence is repeated 128 times over the duration of a GSM hyperframe. It is divided into 8 sets of 51 52-multiframes. The structure of a set is explicitly shown on figure below :

Figure 1 (subclause 6.3.3): Structure of timeslot shifting sequence

A set is formed by interleaving segments of TNS1 and TNS2. The mapping of TNS1 and TNS2 segments onto a set is defined by the parameters x0, x1, x2, x3 as follows :

for (FN div 52) mod 51 = 0 to 7 a TNS1 segment is used

for (FN div 52) mod 51 = 8 to 7+x3 a TNS2 segment is used

for (FN div 52) mod 51 = 8+x3 to 7+x3+x2 a TNS1 segment is used

for (FN div 52) mod 51 = 8+x3+x2 to 7+x3+x2+x1 a TNS2 segment is used

for (FN div 52) mod 51 = 8+x3+x2+x1 to 7+x3+x2+x1+x0 a TNS1 segment is used

for (FN div 52) mod 51 = 8+x3+x2+x1+x0 to 15+x3+x2+x1+x0 a TNS2 segment is used

for (FN div 52) mod 51 = 16+x3+x2+x1+x0 to 23+x3+x2+x1 a TNS1 segment is used

for (FN div 52) mod 51 = 24+x3+x2+x1 to 31+x3+x2 a TNS2 segment is used

for (FN div 52) mod 51 = 32+x3+x2 to 39+x3 a TNS1 segment is used

for (FN div 52) mod 51 = 40+x3 to 47 a TNS2 segment is used

for (FN div 52) mod 51 = 48 to 50 a TNS1 segment is used

The TNS1 and TNS2 segments are extracted from TNS1 and TNS2 according to the following rules :

a) The first CTSBCH TN used in a shifting sequence shall be the TNI.

b) Two consecutive CTSBCH TN shall be separated by single circular shifts along TNS1 and TNS2.

c) When changing from a TNSi segment to a TNSj segment, the last timeslot obtained from TNSi shall be followed by its immediate successor in TNSj.

NOTE: The first timeslot of a set is obtained by three circular shifts in TNS1 with regard to the first timeslot of the previous set.

An example of the mapping of TNS1 and TNS2 onto the first set of the generated shifting sequence is given in annex C.

6.3.3.2 CTSPCH, CTSARCH and CTSAGCH timeslot assignment

For the CTSPCH, CTSARCH and CTSAGCH, the timeslot shall be assigned by the CTS-FP for each 52-multiframe. The timeslot number used for CTSPCH, CTSARCH and CTSAGCH shall be the TNC broadcast in the previous 52‑multiframe CTSBCH-SB.

6.3.4 Mapping in time of Extended Coverage control channels onto physical channels

6.3.4.1 General

The mapping in time of Extended Coverage control channels is defined in table 6a of clause 7, and is illustrated in figure 11 to figure 17. The table and figures also define the relationship of the air interface TDMA frames to the multiframe.

In addition to the information in table 6a and figures 11 to 18, further information is provided for EC-CCCH in subclause 6.3.4.2 and 6.3.4.3, and for the mapping of the EC-BCCH data in subclause 6.3.4.4.

6.3.4.2 Mapping of the downlink Extended Coverage CCCH (EC-CCCH/D)

The EC-CCCH and its different logical channels (EC-AGCH, EC-PCH) can be mapped dynamically and are identified by the message header. The mapping is as defined in table 6a of clause 7 and is illustrated in figure 13, figure 14 and figure 15.The EC-CCCH blocks constitute different number of blind physical layer transmissions depending on the downlink Coverage Class used, see table 6a, and illustration in figure 13, figure 14 and figure 15. One, eight, sixteen or thirty-two corresponding EC-CCCH CC1 blocks (an EC-CCCH CC1 block is defined as EC-CCCH/D/1 in TS 45.003 consisting of 2 bursts) are used to form a CC1, CC2, CC3 or CC4 EC-CCCH block, respectively. In case of CC2 and CC3, the bursts are mapped over two 51-multiframes, and for CC4 over four 51-multiframes. For CC1 each block is contained in a single 51-multiframe.

6.3.4.3 Mapping of the uplink Extended Coverage CCCH (EC-CCCH/U)

The mapping of the EC-RACH (EC-CCCH/U) is defined in table 6a of clause 7 and illustrated in figure 16 and figure 17, where the possible blocks are indicated for each uplink Coverage Class (CC1 to CC5). Furthermore, two different EC-RACH mappings exist. The mapping to be used is signalled on cell level in EC SI, see 3GPP TS 44.018. The EC-RACH is either mapped onto a single TS, or over 2 consecutive TS for CC2, CC3, CC4 and CC5. CC1 EC-RACH is always mapped onto 1 TS.

The EC-RACH is fixed allocated in the full 51-multiframe. The EC-RACH blocks constitute different number of EC-RACH bursts depending on the uplink Coverage Class used, see table 6a and illustration in figure 16 and figure 17. One, four, sixteen, fourty-eight bursts are used for CC1, CC2, CC3 and CC4 EC-RACH blocks respectively. For ESAB sixty-six ESABs are used for the CC5 EC-RACH block, for EDAB sixty-six EDABs are used for the CC5 EC-RACH block. In case of CC5 the bursts are mapped over three 51-multiframes, for CC4 the bursts are mapped over two 51-multiframes, and for Coverage Classes CC1 to CC3 each block is contained in a single 51-multiframe.

6.3.4.4 Mapping of EC-BCCH data

In order to facilitate the MS operation, the network is required to transmit EC System Information (EC SI) messages on EC-BCCH blocks, each EC-BCCH block mapped onto 8 consecutive TDMA frames in each of 8 consecutive 51‑multiframes, see table 6a and figure 12. An EC SI message may consist of one or more message instances (see 3GPP TS 44.018) where each EC SI message instance is transmitted in one EC-BCCH block (one EC-BCCH block consisting of 16 blind physical layer transmissions of an EC SI message instance as described in 3GPP TS 45.003).

The following rules apply:

i)    An EC SI message instance is started in the 51-multiframe when TC = (FN DIV 51) mod 8 = 0,

ii) The EC SI messages (see 3GPP TS 44.018) shall be sent in sequence in ascending order according to the EC SI message type (EC SI 1, EC SI 2, EC SI 3 and EC SI 4) without repeating any given EC SI message or EC SI message instance (except for blind physical layer transmissions within an EC-BCCH block) before all instances of all EC SI messages have been sent.

iii) When there are multiple EC SI message instances of an EC SI message each EC SI message instance shall be sent in ascending order according to the value of the EC SI N_INDEX (N=1 to 4) included in each message instance (see 3GPP TS 44.018)

iv) A full set of EC SI messages includes a single transmission of each EC SI message/message instance sent according to ii) and iii).

An example is provided below where it is assumed that EC SI message 1, 2, 3 and 4 are sent by the network, and where EC SI 3 contains two EC SI message instances. In this case, the full set of EC SI messages would be transmitted using the following sequence:

EC SI 1; EC SI 2; EC SI 3(EC SI 3_INDEX=0) ; EC SI3(EC SI 3_INDEX=1); EC SI 4

6.4 Permitted channel combinations

6.4.1 Permitted channel combinations onto a basic physical channel

The following are the permitted ways, as defined by 3GPP TS 44.003, in which channels can be combined onto basic physical channels for one or several MSs.

The following definitions are used in the list of combinations below.

Combination designation	Channel combination
SUB_TA	TCH/H + FACCH/H + SACCH/TH
SUB_T	TCH/H
SUB_PA	PDTCH/H + PACCH/H
SUB_TE	TCH/H + FACCH/H + SACCH/TPH + EPCCH/H
SUB_OTA	O-TCH/H + O-FACCH/H + SACCH/TH
SUB_OT	O-TCH/H
SUB_OTE	O-TCH/H + O-FACCH/H + SACCH/TPH + EPCCH/H

Numbers appearing in parenthesis after channel designations indicate sub‑channel numbers. (0..n) shall be interpreted as subchannel 0, 1,…, n-1 and n. Channels and sub‑channels need not necessarily be assigned.

i) TCH/F + FACCH/F + SACCH/TF

ii) O-TCH/F + O-FACCH/F + SACCH/TF

iii)

iv) FCCH + SCH + BCCH + CCCH

v) FCCH + SCH + BCCH + CCCH + SDCCH/4(0..3) + SACCH/C4(0..3)

vi) BCCH + CCCH

vii) SDCCH/8(0 .7) + SACCH/C8(0 . 7)

viii) TCH/F + FACCH/F + SACCH/M

ix) TCH/F + SACCH/M

x) TCH/FD + SACCH/MD

xi) PBCCH + PCCCH + PDTCH/F + PACCH/F + PTCCH/F

xii) PCCCH + PDTCH/F + PACCH/F + PTCCH/F

xiii) PDTCH/F + PACCH/F + PTCCH/F

xiv) CTSBCH + CTSPCH + CTSARCH + CTSAGCH

xv) CTSPCH + CTSARCH + CTSAGCH

xvi) CTSBCH

xvii) CTSBCH + TCH/F + FACCH/F + SACCH/CTS

xviii) E-TCH/F + E-IACCH/F + E-FACCH/F + SACCH/TF

xix) E-TCH/F + E-IACCH/F + E-FACCH/F + SACCH/M

xx) E-TCH/F + E-IACCH/F + SACCH/M

xxi) E-TCH/FD + E-IACCH/F + SACCH/MD

xxii) CFCCH + CSCH + CPBCCH + CPCCCH + PDTCH/F + PACCH/F + PTCCH/F

xxiii) CPCCCH + PDTCH/F + PACCH/F + PTCCH/F

xiv) O-TCH/F + O-FACCH/F + SACCH/TPF + EPCCH/F

xxv) TCH/F + FACCH/F + SACCH/TPF + EPCCH/F

xxvi) TCH/F + FACCH/F + SACCH/MP + EPCCH/M

xxvii) TCH/F + SACCH/MP + EPCCH/M

xxviii) TCH/FD + SACCH/MPD + EPCCH/MD

xxix) PDTCH/F + PACCH/F + SACCH/TF

xxx) PDTCH/F + PACCH/F + SACCH/TPF + EPCCH/F

xxxi) PDTCH/F + PACCH/F + SACCH/M

xxxii) PDTCH/FD + PACCH/FD + SACCH/MD

xxxiii) PDTCH + PACCH/F + SACCH/M + EPCCH/M

xxxiv) PDTCH + PACCH/F + SACCH/M + EPCCH/MD

xxxv) PRACH + PDTCH/U + PACCH/U + PTCCH/U + MPRACH

xxxvi) PDTCH/U + PACCH/U + PTCCH/U + MPRACH

xxxvii) EC-SCH + EC-BCCH + EC-CCCH

xxxviii) FCCH + SCH + BCCH + CCCH + EC-CCCH/U

xxxix) EC-CCCH

xl) BCCH + CCCH + EC-CCCH/U

xli) EC-PDTCH/F + EC-PACCH/F

xlii) EC-PDTCH/F + EC-PACCH/F + PDTCH/F + PACCH/F + PTCCH/F

The following combinations of half rate channels are allowed on a basic physical channel for a single mobile, where the second half rate channel need not be assigned:

a1) SUB_TA + SUB_T (Lm + Lm configuration)

a2) SUB_TA + SUB_OT (Lm + Lm configuration)

a3) SUB_TA + SUB_PA (DTM single slot)

a4) SUB_TE + SUB_T (Lm + Lm configuration)

a5) SUB_TE + SUB_OT (Lm + Lm configuration)

a6) SUB_TE + SUB_PA (DTM single slot)

a7) SUB_OTA + SUB_OT (Lm + Lm configuration)

a8) SUB_OTA + SUB_T (Lm + Lm configuration)

a9) SUB_OTA + SUB_PA (DTM single slot)

a10) SUB_OTE + SUB_OT (Lm + Lm configuration)

a11) SUB_OTE + SUB_T (Lm + Lm configuration)

a12) SUB_OTE + SUB_PA (DTM single slot)

The following combinations of half rate channels are allowed on a basic physical channel for two mobiles:

b1) SUB_TA + SUB_TA

b2) SUB_TA + SUB_TE

b3) SUB_TA + SUB_OTA

b4) SUB_TA + SUB_OTE

b5) SUB_TE + SUB_TE

b6) SUB_TE + SUB_OTA

b7) SUB_TE + SUB_OTE

b8) SUB_OTA + SUB_OTA

b9) SUB_OTA + SUB_OTE

b10) SUB_OTE + SUB_OTE

The following combinations of full rate channels are allowed on a basic physical channel capable of VAMOS for two mobiles in VAMOS mode (where the 2 full rate channels constitute a VAMOS pair):

c11) i) + i)

c12) i) + xxv)

c13) xxv) + xxv)

The following combinations of full rate and half rate channels are allowed on a basic physical channel capable of VAMOS for three mobiles in VAMOS mode (where the half rate channel on sub-channel number 0 and the full rate channel constitute one VAMOS pair whilst the half rate channel on sub-channel number 1 and the full rate channel constitute a different VAMOS pair on the same basic physical channel capable of VAMOS)

d1) SUB_TA + SUB_TA + i)

d2) SUB_TA + SUB_TA + xxv)

d3) SUB_TA + SUB_TE + i)

d4) SUB_TA + SUB_TE + xxv)

d5) SUB_TE + SUB_TE + i)

d6) SUB_TE + SUB_TE + xxv)

The following combinations of half rate channels are allowed on a basic physical channel capable of VAMOS for 3 mobiles of which 2 are in VAMOS mode (where the pair of half rate channels sharing the same sub-channel number constitutes the VAMOS pair whilst the other half rate channel is not in VAMOS mode)

e1) SUB_TA + SUB_TA + SUB_TA

e2) SUB_TA + SUB_TA + SUB_TE

e3) SUB_TE + SUB_TE + SUB_TA

e4) SUB_TE + SUB_TE + SUB_TE

The following combinations of half rate channels are allowed on a basic physical channel capable of VAMOS for four mobiles in VAMOS mode (where the pair of half rate channels on the sub-channel number 0 constitutes one VAMOS pair and the other pair of half rate channels on the sub-channel number 1 constitutes the other VAMOS pair):

f1) SUB_TA + SUB_TA + SUB_TA + SUB_TA

f2) SUB_TA + SUB_TA + SUB_TA + SUB_TE

f3) SUB_TA + SUB_TA + SUB_TE + SUB_TE

f4) SUB_TA + SUB_TE + SUB_TE + SUB_TE

f5) SUB_TE + SUB_TE + SUB_TE + SUB_TE

NOTE 0: CCCH = PCH+ RACH + AGCH + NCH.

EC-CCCH = EC-PCH+EC-RACH+EC-AGCH.

PCCCH = PPCH+PRACH+PAGCH

CPCCCH = CPPCH + CPRACH + CPAGCH

EC-CCCH/U = EC-RACH

NOTE 1: Where the SMSCB is supported, the CBCH replaces SDCCH number 2 in cases v) and vii) above.

NOTE 2: A combined CCCH/SDCCH allocation (case v) above) may only be used when no other CCCH channel is allocated.

NOTE 3: Combinations viii), ix), x), xix), xx), xxi), xxix), xxx), xxxi) and xxxii) are used without EPC in multislot configurations as defined in subclause 6.4.2.

NOTE 4: Combinations xiv), xv), xvi) and xvii) shall be used in CTS; combinations xiv), xvi) and xvii) shall be mutually exclusive; combinations xiv) and xv) shall also be mutually exclusive.

NOTE 5: Combinations xxii) and xxiii) shall be used for COMPACT on serving time groups.

NOTE 6: Combinations i), ii), xiii), xxv), xxiv) or any of a1) to a12) shall be used for single timeslot operation in DTM.

NOTE 7: A unidirectional TCH combination i), viii), ix) or x) may be combined with the corresponding E-TCH combination xviii), xix), xx) or xxi) respectively in the other direction.

NOTE 8: Combinations xxvi), xxvii), xxviii) , xxxii), xxxiii) and xxxiv) are used with EPC in multislot configurations as defined in subclause 6.4.2.

NOTE 9: The basic physical channel onto which channels can be combined according to combinations i), ii), viii), ix), x), xviii), xix), xx), xxi), xxiv), xxv), xxvi), xxvii), xxviii), xxix), xxx), xxxi), xxxii), xxxiii) and xxxiv) is referred to as dedicated basic physical subchannel full rate (DBPSCH/F) in Iu mode.

NOTE 10: The basic physical channel onto which channels can be combined according to combinations xi), xii) and xiii) is referred to as shared basic physical subchannel full rate (SBPSCH/F) in Iu mode.

NOTE 11: The part of the basic physical channel onto which channels can be combined according to combinations SUB_TA, SUB_T, SUB_PA, SUB_TE, SUB_OTA, SUB_OT, SUB_OTE is referred to as dedicated basic physical subchannel half rate (DBPSCH/H) in Iu mode.

NOTE 12: The part of the basic physical channel onto which channels can be combined according to combination SUB_PA is referred to as shared basic physical subchannel half rate (SBPSCH/H) in Iu mode.

NOTE 13: The parts of the basic physical channel onto which SDCCH and SACCH can be combined according to combination v) are referred to as dedicated basic physical subchannels for SDCCH/4 and SACCH/C4 (DBPSCH/S4) in Iu mode.

NOTE 14: The parts of the basic physical channel onto which SDCCH and SACCH can be combined according to combination vii) are referred to as dedicated basic physical subchannels for SDCCH/8 and SACCH/C8 (DBPSCH/S8) in Iu mode.

NOTE 15: Combinations xxxv) and xxxvi) are used only for MBMS.

NOTE 16: In RTTI configuration only combination xiii) shall be used.

NOTE 17: Combinations xxxviii) and xl) are only applicable if 2 TS EC-RACH mapping is used, and in that case to the lower numbered timeslot.

NOTE 18: Combinations xli) and xlii) with EC-PDTCH/F apply also to EC-PDTCH/2TS/F using 2 PDCHs for blind physical layer transmissions.

6.4.2 Multislot configurations

6.4.2.1 General

A multislot configuration consists of multiple circuit or packet switched traffic channels together with associated control channels, assigned to the same MS or, in the case of point-to-multipoint transmission, a group of MSs. As an exception if blind physical layer transmissions are used in EC operation, a multislot configuration consists of a single EC-PDTCH and/or EC-PACCH (the associated control channel) mapped onto multiple physical channels.

The multislot configuration occupies up to 8 basic physical channels, with different timeslots numbers (TN) but with the same frequency parameters (ARFCN or MA, MAIO and HSN) and the training sequence with the same training sequence code (TSC) which may be selected from different TSC Sets in case of multislot configurations for dual transfer mode in A/Gb mode (see subclause 6.4.2.3). For a mobile station supporting the extended TSC set, up to two training sequences may be used on the same timeslot number with the same frequency parameters for packet switched traffic channels. In this case the training sequences are chosen from different TSC sets.

6.4.2.1 Multislot configurations for circuit switched connections in A/Gb mode

In A/Gb mode, two types of multislot configurations exist, symmetric and asymmetric. The symmetric case consists of only bi-directional channels. The asymmetric case consists of both bi-directional and unidirectional downlink channels.

The occupied physical channels shall consist of the following channel combinations as defined in subclause 6.4.1.

one main channel of type viii) or xix) +

x secondary channels of type ix) or xx) +

y secondary channels of type x) or xxi)

When in EPC mode (see 3GPP TS 45.008) the occupied physical channels shall consist of the following channel combinations as defined in subclause 6.4.1.

one main channel of type xxvi) +

x secondary channels of type xxvii) +

y secondary channels of type xxviii)

where 0<= x <= 7, y = 0 for symmetric multislot configuration

0<= x <= 6, 1 <= y <= 7, x+y <= 7 for asymmetric multislot configuration

The main channel is the bi-directional channel that carries the main signalling (FACCH and SACCH) for the multislot configuration. The position of the main channel is indicated by the assignment message (3GPP TS 44.018). Secondary channels may be added or removed without changing the main channel.

The assignment of channels to a Multislot Configuration must always consider the multislot capability of the MS, as defined by the multislot class described in annex B.

There is no limitation in this TS to the possible TCH types (see subclause 3.2) which may be used in a Multislot Configuration.

High Speed Circuit Switched Data (HSCSD) is one case of multislot configuration. The full rate traffic channels of a HSCSD configuration shall convey the same user bit rate (see subclause 3.2.3).

NOTE: For the maximum number of timeslots to be used for a HSCSD, see 3GPP TS 23.034.

6.4.2.2 Multislot configurations for packet switched connections in A/Gb mode

In A/Gb mode, an MS may be assigned several (EC-)PDTCH/Us or (EC-)PDTCH/Ds for one mobile originated or one mobile terminated communication respectively, mapped onto a corresponding number of PDCHs in BTTI configuration or a corresponding number of PDCH-pairs in RTTI configuration. An exception applies for EC operation when CC2, CC3 or CC4 has been assigned in which case only one EC-PDTCH/U or one EC-PDTCH/D is mapped onto four consecutive PDCHs in BTTI configuration.

The total number of assigned uplink PDCHs and downlink PDTCHs shall not exceed the total number of uplink and downlink timeslots that can be used by the MS per TDMA frame (i.e., the parameter ‘Sum’ specified in Annex B). An exception is the case of EC operation where uplink and downlink PDCHs are not allocated simultaneously in the same TDMA frame (for details see Annex B.1) and hence the number of assigned uplink and downlink PDCHs shall not exceed the maximum number of receiving and transmitting timeslots respectively, that can be used by the MS per TDMA frame (i.e. the parameters ‘Rx’ and ‘Tx’ respectively in Annex B). In this context "assignment" refers to the list of PDCH given in the assignment message and that may dynamically, or in the case of EC operation in the UL, by Fixed Uplink Allocation, carry the (EC-)PDTCHs for that specific MS.

Alternatively, for a multislot class type 1 MS supporting Flexible Timeslot Assignment (see 3GPP TS 24.008) the network may assign a total number of uplink and downlink PDCHs exceeding the parameter ‘Sum’ specified in Annex B, provided that the number of assigned downlink PDCHs shall not exceed the number of downlink timeslots that can be used by the MS per TDMA frame (i.e., the parameter ‘Rx’ specified in Annex B) and the number of assigned uplink PDCHs shall not exceed the number of uplink timeslots that can be used by the MS per TDMA frame (i.e., the parameter ‘Tx’ specified in Annex B). In this case, the network shall ensure that, in each radio block period, the total number of uplink and downlink PDCHs that have been allocated to the MS does not exceed the total number of uplink and downlink timeslots that can be used by the MS per TDMA frame (i.e., the parameter ‘Sum’ specified in Annex B).

Alternatively, when Enhanced Flexible Timeslot Assignment, EFTA, is used (see 3GPP TS 24.008) the network shall follow the same procedure as for Flexible Timeslot Assignment as described above with the exception that, during any given radio block period, the total number of uplink and downlink PDCHs that have been allocated to the MS may exceed the total number of uplink and downlink timeslots defined by the parameter ‘Sum’ specified in Annex B.

NOTE 1: In the downlink, a PDCH is ‘allocated’ to an MS in a radio block period if the network transmits an RLC/MAC block for the MS on that PDCH during that radio block period.

In RTTI configuration, PDCHs shall be assigned in pairs.

If there are m timeslots assigned for reception and n timeslots assigned for transmission:

– For a multislot class type 1 MS, there shall be Min(m,n,2) reception and transmission timeslots with the same TN;

– For a multislot class type 2 MS, there shall be Min(m,n) reception and transmission timeslots with the same TN.

In the case of downlink dual carrier or DLMC configurations, if timeslots with the same timeslot number are assigned on more than one carrier, in calculating the value of m they shall be counted as one timeslot.

The mapping of (EC-)PACCH onto the assigned downlink PDCHs or the allocated uplink PDCHs is specified in 3GPP TS 44.060.

For multislot class type 1 MS, Table 6.4.2.2.1 lists the number of timeslots (in a dual carrier configuration or a DLMC configuration the numbe of timeslots apply on a per radio frequency basis) that are possible to assign (provided that it is supported by the MS according to its multislot class) for different medium access modes (see 3GPP TS 44.060). It also indicates if the network (or the MS in case of EFTA) shall apply T_ra or T_ta (see annex B), and if Shifted USF operation shall apply (see 3GPP TS 44.060). Additionally, it indicates which configurations can also be used for allocation (provided that they are compatible with the number of timeslots assigned to the MS). For a MS in EC operation Table 6.4.2.2.1 does not apply since all assignments according to its multislot class are possible. T_ra and T_ta (see Annex B) do not apply in EC operation.

NOTE 2: In case of extended dynamic allocation, the MS needs to support USF monitoring on the downlink PDCHs corresponding to (i.e. with the same timeslot number as) all assigned uplink PDCHs as defined in 3GPP TS 44.060.

In a dual carrier or a DLMC configuration, all the downlink timeslots on all radio frequency channels shall be assigned within a window of size ‘d’ and all the uplink timeslots on all radio frequency channels shall be assigned within a window of size ‘u’ where ‘d’ and ‘u’ are defined in Table 6.4.2.2.1.

In a dual carrier configuration the maximum number of timeslots that may be assigned (uplink and downlink) depends on the multislot class of the MS (or the Equivalent multislot class if different from the Signalled multislot class as described in B.4) and the multislot capability reduction for downlink dual carrier.

In a DLMC configuration the maximum number of timeslots that may be assigned (uplink and downlink) depends on the multislot class of the MS and the supported Maximum Number of Downlink Timeslots, see 3GPP TS 24.008.

The maximum number of radio frequency channels on which downlink timeslots may be assigned in a DLMC configuration is dependent on the supported Maximum Number of Downlink Carriers, see 3GPP TS 24.008.

In a dual carrier or a DLMC configuration, Shifted USF operation shall be determined per carrier according to the number of downlink and uplink timeslots assigned on each carrier

Table 6.4.2.2.1: Multislot configurations for packet switched connections in A/Gb mode

Medium access mode	No of Slots (Note 0)	Tra shall apply	Tta shall apply	Applicable Multislot classes (see Note 7)	Note
Downlink, any mode	d = 1-6	Yes	–	1-12, 19-45
	d = 7-8	No	–	24-29	1,2
Uplink, Dynamic	u = 1-2	Yes	–	1-12, 19-45	10
	u = 2	–	Yes	12, 36-39	11
	u = 3		Yes	12, 37-39	9
	u = 2-3	Yes	–	31-34, 41-45	9
Uplink, Ext. Dynamic	u = 1-3	Yes	–	1-12, 19-45
	u = 4	–	Yes	12, 22-23, 27-29	2
	u = 4	Yes	–	33-34, 38-39, 43-45	2
	u = 5	Yes	–	34, 39	2,3,5
	u = 5	–	Yes	44-45	2,4
	u = 4	Yes	–	30-39	12
	u = 4	–	Yes	40-45	12
	u = 5	Yes	–	30-39	5, 12
	u = 5	–	Yes	40-45	5, 12
	u = 6	–	Yes	45	2,4,5
Down + up, Dynamic	d+u = 2-5, u < 3	Yes	–	1-12, 19-45	10
	d+u = 6, u<3	Yes	–	30-45	2,3
	d+u = 7, u<3	–	Yes	40-45	2,4
	d = 2, u = 3	Yes	–	32-34, 42-45	9
	d+u = 5, u = 2 – 3	–	Yes	12,36-39	9
	d+u = 6, u = 3-4	Yes	–	32-34,37-39,42-45	2,3,9
	d+u = 7, u = 3-4	–	Yes	42-45	2,4,9
	d = 4, u = 4	Yes	–	33-34,38-39,43-45	2,3,8,9
	d = 4, u = 5	–	Yes	44-45	2,4,8,9
	d+u = 8-10, u<3	Yes	–	30-45	12
Down + up, Ext. Dynamic	d+u = 2-4	Yes	–	1-12, 19-45
	d+u = 5, d > 1	Yes	–	8-12, 19-45
	d+u = 6-7, u<4	Yes	–	10-12	8
	d = 1, u = 4	–	Yes	12, 22-23, 27-29	2
	d>1, u = 4	–	Yes	12	2,8
	d = 1, u = 4	Yes	–	33-34, 38-39, 43-45	2,6
	d+u = 6, d>1	Yes	–	30-45	2,3
	d = 1, u = 5	Yes	–	34,39	2,3,5
	d+u = 7-9, u<5	Yes	–	31-34, 36-39	2,3,8
	d=2-5, u = 5	Yes	–	34,39	2,3,5,8
	d = 1, u = 5	–	Yes	44-45	2,4
	d+u = 7, d>1	–	Yes	40-45	2,4
	d = 1, u = 6	–	Yes	45	2,4,5
	d+u = 8-11, u<6	–	Yes	41-45	2,4,8
	d=2-6, u = 6	–	Yes	45	2,4,5,8
	d=6-8, u=1-4	Yes	–	30-39	12
	d=6-8, u=5	Yes	–	34,39	5,12
	d=7-8, u=1-4	–	Yes	40-45	12
	d=7-8, u=5-6	–	Yes	44-45	5,12
Note 0 If the downlink timeslots assigned (allocated) to the mobile station are not contiguous, d shall also include the number of downlink timeslots not assigned (allocated) to the mobile station that are located between assigned (allocated) downlink timeslots. Similarly, if the uplink timeslots assigned (allocated) to the mobile station are not contiguous, u shall also include the number of uplink timeslots not assigned (allocated) to the mobile station that are located between assigned (allocated) uplink timeslots. Note 1 Normal measurements are not possible (see 3GPP TS 45.008). Note 2 Normal BSIC decoding is not possible (see 3GPP TS 45.008) except e.g. in case of a downlink dual carrier capable MS operating in single carrier mode using its second receiver for BSIC decoding. Note 3 TA offset required for multislot classes 35-39. Note 4 TA offset required for multislot classes 40-45. Note 5 Shifted USF operation shall apply (see 3GPP TS 44.060). Note 6 The network may fallback to a lower multislot class and may not apply Tra. A multislot class 38 or 39 MS shall in this case use Tta for timing advance values below 31. Note 7 For dual carrier operation the Applicable Multislot class is the Signalled multislot class or the Equivalent multislot class (if different from the Signalled multislot class) as defined in Table B.2. For EFTA operation the Applicable Multislot class is the Signalled multislot class. Note 8 These configurations can only be used for assignment to an MS supporting Flexible Timeslot Assignment (see 3GPP TS 24.008). For allocation additional restrictions apply. Note 9 These configurations can be used only in RTTI configuration. Note 10 These configurations can be used in RTTI configurations only when the timeslots of the corresponding downlink PDCH-pair are contiguous. Note 11 These configurations can be used only in RTTI configurations when the timeslots of the corresponding downlink PDCH-pair are not contiguous. Note 12 These configurations can only be used for assignment to an MS for which Enhanced Flexible Timeslot Assignment with extended receive capability is used (see Annex B.5 and 3GPP TS 44.060). Whether normal measurements (see 3GPP TS 45.008) and/or normal BSIC decoding (see 3GPP TS 45.008) are possible will be dependent on the allocation or on the use of a second receiver for this purpose.

For multislot class type 2 MS, all assignments according to its multislot class are possible independent of the MAC mode.

For GPRS and EGPRS; the occupied physical channels shall consist of a combination of configurations xi, xii, xiii and xlii) as defined in subclause 6.4.1. For COMPACT, the occupied physical channels shall consist of a combination of configurations xiii), xxii), and xxiii), as defined in subclause 6.4.1. For EC-GSM-IoT, the occupied physical channels shall consist of a combination of configurations xli) or xlii).

The network shall leave a gap of at least one radio block period between the old and the new configuration, when the assignment is changed and PDCHs with the lowest numbered timeslot are not the same in the old and new configuration. For multislot class type 1 MS, the gap shall be left in both uplink and downlink when the lowest numbered timeslot for the combined uplink and downlink configuration is changed. For multislot class type 2 MS, the gap shall be left in the link (uplink and/or downlink) where the lowest numbered timeslot has been changed.

6.4.2.3 Multislot configurations for dual transfer mode in A/Gb mode

For DTM in A/Gb mode, a multislot configuration consists of a single traffic channel (TCH, O-TCH or E-TCH) and one or more packet data traffic channels (PDTCH) together with associated control channels assigned to the same mobile station. The mix of full and half rate packet data channels is not allowed in the uplink. This mix is only defined for the downlink direction and only supported by mobile stations indicating Extended GPRS DTM Multi Slot Class or Extended EGPRS DTM Multi Slot Class capability (see 3GPP TS 24.008). The PDTCH/H is only allowed on the time slot assigned for half rate circuit switched connection.

NOTE: In the case of extended dynamic allocation, the MS needs to support USF monitoring on the downlink PDCHs corresponding to (i.e. with the same timeslot number as) all assigned uplink PDCHs, as defined in 3GPP TS 44.060. This also restricts multislot configurations where USF monitoring is not possible for all assigned uplink PDCHs because of the presence of the dedicated channel. As an exception, if the mobile station indicates support of DTM high multislot class capability, the network may assign a multislot configuration where USF monitoring is not possible for all assigned uplink PDCHs because of the presence of the dedicated channel. In this case, the mobile station behaves as described in 3GPP TS 44.060.

A mobile station indicating support of Flexible Timeslot Assignment (see 3GPP TS 24.008) shall support Flexible Timeslot Assignment while in dual transfer mode. A mobile station indicating support of Enhanced Flexible Timeslot Assignment (see 3GPP TS 24.008) shall support Enhanced Flexible Timeslot Assignment while in dual transfer mode.

The network shall leave a gap of at least one radio block between the old and the new configuration, when the assignment is changed and PDCHs with the lowest numbered timeslot are not the same in the old and new configuration. For multislot class type 1 MS, the gap shall be left in both uplink and downlink when the lowest numbered timeslot for the combined uplink and downlink configuration is changed.

A mobile station indicating support for VAMOS I, VAMOS II or VAMOS III (see 3GPP TS 24.008) shall support VAMOS mode of operation while in dual transfer mode. In case of DTM in A/Gb mode the training sequence for the packet data traffic channels (PDTCH) together with associated control channels shall have the same training sequence code (TSC) as the TSC of the traffic channel together with the associated control channels and shall be selected from TSC Set 1. In case the mobile station indicates support for extended TSC sets, the TSC shall be selected from TSC set 1 or TSC set 2, except for GMSK modulation where the TSC is selected from TSC set 1 or TSC set 3.

6.4.2.3a Multislot configurations for MBMS in A/Gb mode

In A/Gb mode, the network may assign several PDTCH/Ds for one broadcast/multicast session (see 3GPP TS 44.060). The total number of assigned PDTCH/Ds for one broadcast/multicast session shall not exceed 5 (4 if the MS must listen to the (P)BCCH and (P)CCCH in addition to the timeslots allocated for MBMS data transfer). In this context "assignment" refers to the list of PDCHs given in the assignment message and that may dynamically carry the PDTCHs. The PACCH/D may be mapped onto any of the assigned PDCHs.

An MBMS capable mobile station shall be capable of receiving one or more broadcast/multicast sessions on up to 5 contiguous timeslots within a TDMA frame (4 if the MS must listen to the (P)BCCH and (P)CCCH in addition to the timeslots assigned for MBMS data transfer). If the timeslots are not contiguous, the number of downlink timeslots not listened to by the mobile station that are located between downlink timeslots that are listened to shall also be included in this number.

NOTE 1: When receiving multiple broadcast/multicast sessions, the number of sessions that the mobile station can simultaneously receive depends on the radio resources assignment for the corresponding MBMS radio bearers.

As an exception in the case where the mobile station needs to listen to the (P)BCCH and (P)CCCH in addition to the timeslots assigned for MBMS data transfer, if PBCCH is present in the cell and BS_PCC_CHANS=1, the total number of PDTCH/Ds assigned for one broadcast/multicast session may equal 5 (including the PDTCH/D carried on the PDCH where PBCCH/PCCCH is mapped on). An MBMS capable mobile station shall then be capable of receiving one or more broadcast/multicast sessions on up to 5 contiguous timeslots within a TDMA frame, and in addition listen to the (P)BCCH and (P)CCCH, if the following conditions are met:

– the PDCH where PBCCH/PCCCH is mapped on is adjacent to the other PDCHs assigned for the MBMS radio bearer(s); and

– the same frequency parameters apply over the 5 PDCHs.

Additionally, up to one uplink timeslot per broadcast/multicast session may be assigned for PACCH/U. The timeslot allocated for transmission shall have the same TN as one of the timeslots used for reception. A multislot class type 1 MS receiving more than one broadcast/multicast session may transmit on up to two uplink timeslots, depending on the radio resources assigned for the MBMS radio bearers. The number (m) of timeslots listened to by the mobile station for the reception of one or more broadcast/multicast sessions and the number (n) of timeslots used by the mobile station for the transmission on PACCH/U within a TDMA frame shall be such that the sum of m and n does not exceed 6 (5 in case the mobile station needs to listen to the (P)BCCH and (P)CCCH in addition to the timeslots assigned for MBMS data transfer and the exception described in this sub-clause does not apply).

While in broadcast/multicast receive mode, an MBMS-capable MS shall be capable of receiving, in addition to the timeslots assigned for data transfer, on at least one further timeslot in order to read the BCCH and CCCH or the PBCCH and PCCCH (with the exception described in this sub-clause, where the timeslot carrying the PBCCH and PCCCH is one of the timeslots assigned for data transfer). This requirement does however not apply when the network transmits system information and paging messages on the PACCH of the MBMS radio bearer (see sub-clause 6.5.1, item xxii). The maximum number of timeslots that an MS is required to receive upon within a TDMA frame is 5, and the timeslots shall be assigned within a window of maximum size Rx=6. The number of PDTCH/Ds assigned and their TN shall be such that an MS receiving a given broadcast/multicast session shall be able to read the BCCH and CCCH or the PBCCH and PCCCH without interrupting the reception of the broadcast/multicast session and the transmission on the uplink timeslot, if assigned, unless system information and paging messages are sent on the PACCH of the MBMS radio bearer. Depending on the number of CCCH or PCCCH allocated in the cell, the network may need to restrict the number of PDTCH/Ds assigned to one broadcast/multicast session.

For an MBMS capable mobile station, the minimum requirements shall be Rx=6, Tx=2, Sum=6, T_ta=T_tb=T_ra=T_rb=1.

6.4.2.4 Multislot configurations for DBPSCH in Iu mode

6.4.2.4.1 TCHs assigned

For a multislot class type 1 MS supporting MBMS, the values of T_tb and T_ra shall be equal to 1 (i.e. multislot classes 31-34, 41-45, see Annex B).

NOTE 2: Multislot classes 30 and 40 are not included since the corresponding mobile stations cannot transmit on up to two uplink timeslots.

6.4.2.4.2 PDTCHs assigned

In Iu mode, two types of multislot configurations exist, symmetric and asymmetric. The symmetric case consists of only bi-directional basic physical subchannels. The asymmetric case consists of both bi-directional and unidirectional downlink basic physical subchannels.

The occupied physical channels shall consist of the following channel combinations as defined in subclause 6.4.1.

x channels of type xxxi) +

y channels of type xxxii)

When in EPC mode (see 3GPP TS 45.008) the occupied physical channels shall consist of the following channel combinations as defined in subclause 6.4.1.

x channels of type xxxiii) +

y channels of type xxxiv)

where 1<= x <= 8, y = 0 for symmetric multislot configuration

1<= x <= 7, 1 <= y <= 7, x+y <= 8 for asymmetric multislot configuration

The assignment of channels to a Multislot Configuration must always consider the multislot capability of the MS, as defined by the multislot class described in annex B.

6.4.2.4.3 TCHs and PDTCHs assigned

Multislot configurations for DBPSCH may consist of a mixed assignment of TCHs and PDTCHs. The multislot configurations for TCH and PDTCH on DBPSCH in Iu mode are defined in sections 6.4.2.4.1 and 6.4.2.4.2.

6.4.2.5 void

6.4.2.6 Multislot configurations for SBPSCH in Iu mode

The multislot configurations for SBPSCH in Iu mode are equivalent to the multislot configurations for packet switched connections in A/Gb mode, which are defined in section 6.4.2.2.

6.4.2.7 Multislot configurations for dual transfer mode in Iu mode

For dual transfer mode in Iu mode, a multislot configuration comprises one or more DBPSCHs and one or more SBPSCH/F. The mobile station shall support every combination of these basic physical subchannels consistent with its multislot capability signalled to the GERAN (See TS 44.118).

The network shall leave a gap of at least one radio block between the old and the new configuration, when the assignment is changed and SBPSCHs with the lowest numbered timeslot are not the same in the old and new configuration. For multislot class type 1 MS, the gap shall be left in both uplink and downlink when the lowest numbered timeslot for the combined uplink and downlink configuration is changed.

6.5 Operation of channels and channel combinations

6.5.1 General

i) A base transceiver station must transmit a burst in every timeslot of every TDMA frame in the downlink of radio frequency channel C0 of the cell allocation (to allow mobiles to make power measurements of the radio frequency channels supporting the BCCH, see 3GPP TS 45.008). In order to achieve this requirement a dummy burst is defined in subclause 5.2.6 which shall be transmitted by the base transceiver station on all timeslots of all TDMA frames of radio frequency channel C0 for which no other channel requires a burst to be transmitted.

ii) Timeslot number 0 of radio frequency channel C0 of the cell allocation must support either channel combinations iv), v) or xxxviii) in subclause 6.4.1. No other timeslot or allocated channel from the cell allocation is allowed to support channel combinations iv), v) and xxxviii) in subclause 6.4.1.

iii) The parameter BS_CC_CHANS in the BCCH defines the number of basic physical channels supporting common control channels (CCCHs). All shall use timeslots on radio frequency channel C0 of the cell allocation. The first CCCH shall use timeslot number 0, the second timeslot number 2, the third timeslot number 4 and the fourth timeslot number 6. Each CCCH carries its own CCCH_GROUP of mobiles in idle mode. Mobiles in a specific CCCH_GROUP will listen for paging messages and make random accesses only on the specific CCCH to which the CCCH_GROUP belongs. The method by which a mobile determines the CCCH_GROUP to which it belongs is defined in subclause 6.5.2.

iv) The parameter BS_CCCH_SDCCH_COMB in the BCCH (see subclause 3.3.2) defines whether the common control channels defined are combined with SDCCH/4(0.3) + SACCH/C4(0.3) onto the same basic physical channel. If they are combined then the number of available random access channel blocks (access grant channel blocks and paging channel blocks; see following), are reduced as defined in table 5 of clause 7.

v) The PCH, AGCH, NCH and BCCH Ext may share the same TDMA frame mapping (considered modulo 51) when combined onto a basic physical channel. The channels are shared on a block by block basis, and information within each block, when de‑interleaved and decoded allows a mobile to determine whether the block contains paging messages, notification message, system information messages or access grants. However, to ensure a mobile satisfactory access to the system a variable number of the available blocks in each 51-multiframe can be reserved for access grants and system information messages, only. The number of blocks not used for paging (BS_AG_BLKS_RES) starting from, and including block number 0 is broadcast in the BCCH (see subclause 3.3.2). As above the number of paging blocks per 51-multiframe considered to be "available" shall be reduced by the number of blocks reserved for access grant messages.

The number of paging blocks per 51-multiframe shall be the same for all cells in a routing area where eDRX is supported to ensure the nominal paging group of a MS that uses eDRX (see 3GPP TS 44.018 [10]) occurs at the same location (i.e. in the same paging block) within the set of 51-multiframes comprising its eDRX cycle in all cells in that routing area.

If system information messages are sent on BCCH Ext, BS_AG_BLKS_RES shall be set to a value greater than zero.

Table 5 of clause 7 defines the access grant blocks and paging blocks available per 51-multiframe.

vi) Another parameter in the BCCH, BS_PA_MFRMS indicates the number of 51-multiframes between transmissions of paging messages to mobiles in idle mode of the same paging group. The "available" paging blocks per CCCH are then those "available" per 51-multiframe on that CCCH (determined by the two above parameters) multiplied by BS_PA_MFRMS. An exception case is where eDRX is supported in a given routing area in which case all cells therein shall have the same number of paging blocks per 51-multiframe (see 3GPP TS 44.018 [10]). In this exception case the "available" paging blocks per eDRX cycle on a CCCH is determined by multiplying the number of paging blocks per 51-multiframe by the number of 51-multiframes per eDRX cycle (BS_ePA_MFRMS) (see Table 6.5.6a-1). Mobiles are normally only required to monitor every Nth block of their paging channel, where N equals the number of "available" blocks in total (determined by the above BCCH parameters) on the paging channel of the specific CCCH which their CCCH_GROUP is required to monitor. Note that when eDRX is used then N is determined using BS_ePA_MFRMS which is not a parameter sent on the BCCH but is derived directly from the eDRX cycle length negotiated by the mobile station with the network (see sub-clause 6.5.2a and Table 6.5.6a-1). Other paging modes (e.g. page reorganize or paging overload conditions described in 3GPP TS 44.018) may require the mobile to monitor paging blocks more frequently than this. All the mobiles listening to a particular paging block are defined as being in the same PAGING_GROUP. The method by which a particular mobile determines to which particular PAGING_GROUP it belongs and hence which particular block of the available blocks on the paging channel is to be monitored is defined in subclause 6.5.2 and 6.5.2a.

vii) An MS which has its membership of at least one voice group or voice broadcast call group set to the active state shall, in addition to monitoring the paging blocks as described above, monitor the notification channel, NCH. This logical channel is always mapped onto contiguous blocks reserved for access grants, in a position and number as given by the parameter NCP, defined in 3GPP TS 44.018, broadcast on the BCCH. The channel may be present when a cell supports voice group or voice broadcast calls. The coding of the various structural parameters described above in this subclause is not changed. Information within a block, when deinterleaved and decoded, allows the MS to determine whether the block contains access grant messages or notification messages.

viii) In presence of PCCCH, the parameter BS_PCC_CHANS in the PBCCH defines the number of physical channels for packet data (PDCH) carrying PCCCH. The (P)BCCH shall in addition indicate the physical description of those channels. Each PCCCH carries its own PCCCH_GROUP of MSs in GPRS attached mode. MS in a specific PCCCH_GROUP will listen for paging messages and make random accesses only on the specific PCCCH to which the PCCCH_GROUP belongs. The method by which an MS determines the PCCCH_GROUP to which it belongs is defined in subclause 6.5.6.

ix) In CTS, the CTSBCH (CTSBCH-SB and CTSBCH-FB) shall always be transmitted by the CTS-FP according to the rules defined in Clause 6 and table 8 of clause 7.

In CTS idle mode, a CTS-MS shall be assigned a CTS_PAGING_GROUP, as specified in subclause 6.5.7. Several CTS-MS can be assigned the same CTS_PAGING_GROUP. The CTS-MS shall determine the specific 52-multiframe where a paging block may be sent to it according to the rule defined in subclause 6.5.7, and shall listen to the CTSBCH of the previous 52-multiframe. In this 52-multiframe, the CTS-MS shall decode the CTSBCH-SB information bits : if the flag indicating the presence of a CTSPCH in the next 52-multiframe is properly set (see 3GPP TS 44.056), the CTS-MS shall listen to the next CTSPCH and read the paging block. With this method, it is not necessary to maintain on the physical channel the CTSPCH : the CTSPCH shall only be transmitted when a paging message shall be addressed to one or several CTS-MS in a CTS paging group.

When using the CTSARCH, the CTS-MS shall send two bursts on the CTSARCH: these two bursts shall be sent on two successive frames and shall fulfil the mapping defined in table 8 of clause 7, with the requirement of the first burst being sent in a TDMA frame with even FN. They shall contain the same access request message, which is specified in 3GPP TS 44.056. The first sent burst can be used by the CTS-FP to assess the path loss between the CTS-MS and itself, in order to effectively decode the second burst.

x) For COMPACT, the base transceiver station shall transmit a burst in a PDCH allocated to carry CPBCCH, in all TDMA Frames where CPBCCH, CFCCH, CSCH is allocated or where CPPCH can appear. In TDMA Frames where CPPCH can appear on the physical channel where CPBCCH is allocated, the base transceiver station shall transmit a dummy block in case no block is required to be transmitted.

xi) For COMPACT, a base station does not transmit a burst in every timeslot of every TDMA frame in the downlink of the COMPACT control carrier (i.e., discontinuous transmission is used).

xii) For COMPACT, inter base station time synchronization is required. 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.

xiii) For the primary COMPACT carrier, timeslot numbers (TN) 1, 3, 5, and 7 shall support channel combination xxii) in subclause 6.4.1. TNs 0, 2, 4, and 6 shall support channel combination xiii).

xiv) For the secondary COMPACT carrier(s) carrying CPCCCH, timeslot numbers (TN) 1, 3, 5, and 7 shall support channel combination xxiii) in subclause 6.4.1. TNs 0, 2, 4, and 6 shall support channel combination xiii). CPCCCHs on secondary COMPACT carrier(s) shall be allocated on same time group as for primary COMPACT carrier.

xv) For the secondary COMPACT carrier(s) not carrying CPCCCH, timeslot numbers (TN) 0 through 7 shall support channel combination xiii) in subclause 6.4.1.

xvi) For COMPACT, BS_PAG_BLKS_RES shall be less than or equal to 8 and less than or equal to 10-BS_PBCCH_BLKS.

xvii) For COMPACT, CFCCH, CSCH, CPBCCH, and CPCCCH are rotated as described in subclause 6.3.2.1. PDTCH, PACCH, and PTCCH do not rotate.

xviii) For COMPACT, the parameters NIB_CCCH_0, NIB_CCCH_1, NIB_CCCH_2, and NIB_CCCH_3 shall not be broadcast for a serving time group.

xix) For the COMPACT, NIB_CCCH_0, NIB_CCCH_1, NIB_CCCH_2, and NIB_CCCH_3 blocks shall be idle for non-serving time groups and rotate in accordance with the non-serving time groups.

The downlink position of the NIB_CCCH idle blocks is based on the ordered list as defined in subclause 6.3.2.1. The MS shall ignore these downlink idle blocks and shall interpret this action as not having detected an assigned USF value on an assigned PDCH.

xx) For COMPACT large cells, NIB_CCCH_0, NIB_CCCH_1, NIB_CCCH_2, and NIB_CCCH_3 blocks shall be idle on timeslots immediately preceding and succeeding non-serving time groups and rotate in accordance with the non-serving time groups. The MS shall ignore these downlink idle blocks and shall interpret this action as not having detected an assigned USF value on an assigned PDCH.

The downlink position of the NIB_CCCH idle blocks is based on the ordered list as defined in subclause 6.3.2.1.

xxi) For COMPACT, the MS attempts uplink random access on its designated serving time group (TG) by monitoring for USF=FREE in every downlink block.

For dynamic allocation, while in the uplink transfer state, the MS monitors all of the downlink non-idle blocks of its assigned PDCH for uplink assignments. The MS shall ignore downlink idle blocks and shall interpret this action as not having detected an assigned USF value on an assigned PDCH.

USF should be set equal to FREE for downlink non-idle blocks B0 on timeslot numbers (TN) 1, 3, 5, and 7.

xxii) While in broadcast/multicast receive mode (see 3GPP TS 45.008), the MS shall continue to monitor system information either on the BCCH or, if present, on the PBCCH unless the network has indicated that system information and paging messages are sent on the PACCH for the MBMS radio bearer the MS listens to. If the network has not indicated that system information and paging messages are sent on the PACCH, or if the MS does not have an MS_ID, the MS shall additionally read paging messages either from the CCCH or, if the PBCCH is present, from the PCCCH. The MS shall then monitor the same paging group as in packet idle mode, i.e. shall determine the paging blocks to monitor using the methods described in subclause 6.5.2 or subclause 6.5.6. If the location of the MBMS radio bearer with respect to the control channels does not allow the mobile station to satisfy this requirement, the mobile station shall not read those radio blocks of the MBMS radio bearer that would prevent the monitoring of its paging group on the paging channel(s).

xxiii) For a mobile in DLMC configuration, fallback to reception of a single carrier, irrespective of the number of assigned carriers, is performed with regular periodicity. The periodicity is based on BS_PA_MFRMS, which indicates the number of 52-multiframes between two fallback periods. A mobile belongs to a particular single carrier fallback group which identifies a specific basic radio block period, or in case of RTTI mode two consecutive reduced radio block periods, within the set of "available" single carrier fallback blocks, during which it performs single carrier fallback. The single carrier fallback applies to all assigned PDCHs (or PDCH pairs, in case of RTTI mode) on the carrier where single carrier fallback is performed.

The method by which a particular mobile determines to which single carrier fallback group it belongs is defined in subclause 6.5.8. Single carrier fallback is performed on the carrier where the PTCCH is assigned. In case no PTCCH is assigned the single carrier fallback is performed on the carrier with the lowest number (see 3GPP TS 44.060 for numbering of carriers). Irrespective of which carrier is used, the single carrier fallback applies to all assigned PDCHs (in BTTI configuration)/PDCH-pairs (in RTTI configuration) on that carrier. In case of inter-band reception, the single carrier fallback only applies in one frequency band.

xxiv) For EC-GSM-IoT, timeslot number 1 of radio frequency channel C0 of the cell allocation must support channel combination xxxvii) in subclause 6.4.1. No other timeslot or allocated channel from the cell allocation is allowed to support channel combination xxxvii).

xxv) For EC-GSM-IoT, the parameter EC_BS_CC_CHANS in the EC SI on EC-BCCH defines the number of basic physical channels supporting extended coverage common control channels (EC-CCCHs). All shall use timeslots on radio frequency channel C0 of the cell allocation and shall support channel combination xxxvii) (timeslot number 1) or xxxix) (timeslot number 3,5, or 7) in subclause 6.4.1. The first EC-CCCH shall use timeslot number 1, the second timeslot number 3, the third timeslot number 5 and the fourth timeslot number 7. Each EC-CCCH carries its own EC_CCCH_GROUP of mobiles in idle mode. Mobiles in a specific EC_CCCH_GROUP will listen for paging messages and make random accesses only on the specific EC-CCCH to which the EC_CCCH_GROUP belongs. In case 2 TS EC-RACH mapping is configured by the network in EC SI (see 3GPP TS 44.018), the physical resources where the EC-RACH is mapped for CC2, CC3, CC4 and CC5 shall be the physical channel used by EC_CCCH_GROUP and one timeslot number lower, see table 6a. In this case the network shall ensure that channel combination xxxviii) is used on the lower timeslot number. The method by which a mobile determines the EC_CCCH_GROUP to which it belongs is defined in subclause 6.5.2b. In case the RACH is used (RACH Access Control in 3GPP TS 44.018) by a MS in EC operation, then channel combination shall be used xxxviii), and timeslot number 0 shall be used.

xxvi) For EC-GSM-IoT, the EC-AGCH and EC-PCH may share the same TDMA frame mapping (considered modulo 51) when combined onto a basic physical channel. The channels are shared on a block by block basis, and information within each block, when de‑interleaved and decoded allows a mobile to determine whether the block contains paging messages or access grants. Table 6a of clause 7 defines the access grant blocks and paging blocks available per 51-multiframe for each Coverage Class respectively. For a given Coverage Class, the same number of paging blocks are always available per 51-multiframe. The number of access grant blocks can differ depending on if the basic physical channel for EC-CCCH is timeslot number 1 or not.

xxvii) For EC-GSM-IoT, the "available" paging blocks per eDRX cycle on an EC-CCCH is Coverage Class specific. It is determined by BS_ePA_MFRMS, see Table 6.5.6a-1, and the downlink Coverage Class of the MS, see subclause 6.5.2b. A mobile station selects one of the "available" paging blocks per eDRX cycle as its PAGING_GROUP based on IMSI. All MSs belonging to the same Coverage Class, using the same eDRX cycle and that has selected the same paging block are defined as being in the same PAGING_GROUP. The method by which a particular mobile determines to which particular PAGING_GROUP it belongs and hence which particular block of the "available" paging blocks on the paging channel is to be monitored is defined in subclause 6.5.2b.

6.5.2 Determination of CCCH_GROUP and PAGING_GROUP for MS in idle mode

This sub-clause applies to the case where a MS is not using extended DRX cycles.

CCCH_GROUP (0 .. BS_CC_CHANS‑1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) div N

PAGING_GROUP (0 .. N‑1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) mod N

where

N = number of paging blocks "available" on one CCCH = (number of paging blocks "available" in a 51-multiframe on one CCCH) x BS_PA_MFRMS.

IMSI = International Mobile Subscriber Identity, as defined in 3GPP TS 23.003.

mod = Modulo.

div = Integer division.

6.5.2a Determination of CCCH_GROUP, PAGING_GROUP_MF and PAGING_GROUP_PCH for MS in idle mode when using extended DRX cycles

The CCCH on which a MS will listen for paging messages and make random accesses is determined by CCCH_GROUP, defined by:

CCCH_GROUP (0 … BS_CC_CHANS‑1) = (I div M) mod BS_CC_CHANS

where

BS_CC_CHANS = Number of CCCHs, ranges from 1 to 4, determined using CCCH_CONF broadcast in SI.

I = IMSI mod 10000000 (IMSI defined in 3GPP TS 23.003)

M = Number of 51-MF per negotiated eDRX Cycle = BS_ePA_MFRMS (see Table 6.5.6a-1)

The 51-multiframe where the paging group occurs on the applicable CCCH_GROUP is determined by:

PAGING_GROUP_MF (0 .. M-1) =  I mod M

The paging group within the 51-multiframe is determined by:

PAGING_GROUP_PCH (0 … L-1) = (I div (BS_CC_CHANS x M)) mod L where

L = number of paging blocks per 51-MF, determined using BS_AG_BLKS_RES broadcast in SI.

The paging group within the negotiated eDRX cycle is derived according to:

PAGING_GROUP (0 … N‑1) = L x PAGING_GROUP_MF + PAGING_GROUP_PCH

where

N = number of paging groups on one CCCH within a given eDRX cycle = BS_ePA_MFRMS x L (see Table 6.5.6a-1).

The procedure for when the MS shall monitor the CCCH is described in 3GPP TS 44.018.

For determination of specific paging multiframe and paging block index when using extended DRX cycles, see subclause 6.5.3b.

6.5.2b Determination of EC_CCCH_GROUP and PAGING_GROUP for MS in idle mode for EC-GSM-IoT

The EC-CCCH on which a MS will listen for paging messages and make random accesses is determined by EC_CCCH_GROUP, defined by:

EC_CCCH_GROUP (0 … EC_BS_CC_CHANS‑1) = (I div M) mod EC_BS_CC_CHANS

where

EC_BS_CC_CHANS = Number of EC-CCCHs, ranges from 1 to 4, broadcast in EC SI.

I = IMSI mod 10000000 (IMSI defined in 3GPP TS 23.003)

M = Number of 51-multiframes per negotiated eDRX Cycle = BS_ePA_MFRMS (see Table 6.5.6a-1)

The paging group is determined by the eDRX value and the downlink Coverage Class.

The 51-multiframe where the paging group occurs on the applicable EC_CCCH_GROUP is determined by:

EC_PAGING_GROUP_MF (0 .. M-1) = I mod M

The paging group within the 51-multiframe is determined by:

EC_PAGING_GROUP_PCH (0 .. L-1) = (I div (EC_BS_CC_CHANS x M)) mod L

where

L = 16 (number of CC1 paging groups per 51-multiframe)

The paging group within the negotiated eDRX cycle is derived by first assuming downlink Coverage Class 1 (CC1), irrespective of the downlink CC selected by the MS according to:

PAGING_GROUP_CC1 (0 … N‑1) = L x EC_PAGING_GROUP_MF + EC_PAGING_GROUP_PCH

where

N = number of paging groups for CC1 on one EC-CCCH within a given eDRX cycle = BS_ePA_MFRMS x 16 (see Table 6.5.6a-1).

In case the MS belongs to another downlink coverage class than CC1 (i.e. CC2, CC3 or CC4), the paging group shall be derived assuming that the physical resource of PAGING_GROUP_CC1 is contained within the physical resource of PAGING_GROUP for the downlink CC selected by the MS and is derived per Coverage Class according to the procedures below.

For CC1:

PAGING_GROUP (0 .. M‑1) = PAGING_GROUP_CC1

For CC2:

PAGING_GROUP (0 .. M‑1) = (PAGING_GROUP_CC1 div 4) mod 4 + 4 x (PAGING_GROUP_CC1 div 32)

For CC3:

PAGING_GROUP (0 .. M‑1) = (PAGING_GROUP_CC1 div 8) mod 2 + 2 x (PAGING_GROUP_CC1 div 32)

For CC4:

PAGING_GROUP (0 .. M‑1) = (PAGING_GROUP_CC1 div 8) mod 2 + 2 x (PAGING_GROUP_CC1 div 64)

where

M = N div CC_DIV

Table 6.5.2-1. CC_DIV.

CC1	CC2	CC3	CC4
1	8	16	32

The procedure for when the MS shall monitor the EC-CCCH is described in 3GPP TS 44.018.

Example assuming a single EC-CCCH: a MS that uses eDRX, where eDRX cycle value = "0000" (BS_ePA_MFRMS=8) has been negotiated between the MS and the network (see Table 6.5.6a-1), and that belongs to CC4, will first derive PAGING_GROUP_CC1 according to 16 x (I mod 8) + (I div 8) mod 16 where I= IMSI mod 10000000. As a second step the PAGING_GROUP for the applicable downlink coverage class (CC4) is derived as (PAGING_GROUP_CC1 div 8) mod 2 + 2 x (PAGING_GROUP_CC1 div 64).

For determination of specific paging multiframe and paging block index for EC-GSM-IoT, see subclause 6.5.3a.

6.5.3 Determination of specific paging multiframe and paging block index

This sub-clause applies to the case where a MS is not using extended DRX cycles.

The required 51-multiframe occurs when:

PAGING_GROUP div (N div BS_PA_MFRMS) = (FN div 51) mod (BS_PA_MFRMS)

The index to the required paging block of the "available" blocks in the 51-multiframe:

Paging block index = PAGING_GROUP mod (N div BS_PA_MFRMS)

where the index is then used with the look‑up table 5 of clause 7 to determine the actual paging channel interleaved block to be monitored.

In GPRS non-DRX mode, the MS shall listen to all blocks of the CCCH channel.

6.5.3a Determination of specific paging multiframe and paging block index for EC-GSM-IoT

6.5.3a.1 CC1

The 51-multiframe where the paging block is mapped for CC1 occurs when:

PAGING_GROUP div 16 = (RFN_QH div 51) mod (BS_ePA_MFRMS)

where

RFN_QH is the TDMA frame number known with an accuracy of a quarter hyperframe (see sub-clause 3.3.2.2.3)

The index to the required paging block of the "available" blocks in the 51-multiframe:

Paging block index = PAGING_GROUP mod 16

where the index is then used with the look‑up table 6a of clause 7 (also illustrated in figure 13) to determine the actual paging channel interleaved block to be monitored.

6.5.3a.2 CC2

The two 51-multiframes where the paging block is mapped for CC2 occurs when:

PAGING_GROUP div 4 = (RFN_QH div 102) mod (BS_ePA_MFRMS div 2)

The index to the required paging block of the "available" blocks in the 51-multiframe:

Paging block index = PAGING_GROUP mod 4

where the index is then used with the look‑up table 6a of clause 7 (also illustrated in figure 13) to determine the actual paging channel interleaved block to be monitored.

6.5.3a.3 CC3

The two 51-multiframes where the paging block is mapped for CC3 occurs when:

PAGING_GROUP div 2 = (RFN_QH div 102) mod (BS_ePA_MFRMS div 2)

The index to the required paging block of the "available" blocks in the 51-multiframe:

Paging block index = PAGING_GROUP mod 2

where the index is then used with the look‑up table 6a of clause 7 (also illustrated in figure 13) to determine the actual paging channel interleaved block to be monitored.

6.5.3a.4 CC4

The four 51-multiframes where the paging block is mapped for CC4 occurs when:

PAGING_GROUP div 2 = (RFN_QH div 204) mod (BS_ePA_MFRMS div 4)

The index to the required paging block of the "available" blocks in the 51-multiframe:

Paging block index = PAGING_GROUP mod 2

where the index is then used with the look‑up table 6a of clause 7 (also illustrated in figure 13) to determine the actual paging channel interleaved block to be monitored.

6.5.3b Determination of specific paging multiframe and paging block index when using extended DRX cycles

The 51-multiframe where the paging block is mapped occurs when:

PAGING_GROUP div L = (FN div 51) mod (BS_ePA_MFRMS)

The index to the required paging block of the "available" blocks in the 51-multiframe:

Paging block index = PAGING_GROUP mod L

where the index is then used with the look‑up table 5 of clause 7 (also illustrated in figure 13) to determine the actual paging channel interleaved block to be monitored.

6.5.3c Determination of EC-PICH block for EC-GSM-IoT

For CC4, two EC-PICH blocks occur in every four 51-multiframes and for CC3 one EC-PICH block occurs in every two 51-multiframes. The location of the EC-PICH blocks is specified in Table 6a.

The MS in CC4 coverage condition, after determining the four 51-multiframes where the paging block occurs and the paging block index within four 51-multiframes, as specified in subclause 6.5.3a4, monitors the EC-PICH block for a paging indication corresponding to its paging block, with the EC-PICH block occurring before the actual paging block. The mapping of EC-PICH block to the paging block number in four 51-multiframe is provided in Table 6.5.8-1.

Table 6.5.8-1. Mapping of EC-PICH block to Paging block number for CC4

TN Number of EC-CCCH	Paging block number	EC-PICH block number
1	0	B0 of same 4*51-multiframe of the paging block
1	1	B1 of same 4*51-multiframe of the paging block
3,5,7	0	B1 of the previous 4*51 multiframe of the 4*51 paging mutiframe of the pagin block
3,5,7	1	B0 of the same 4*51-multiframe of the paging block

The MS in CC3 coverage condition, after determining the two 51-multiframes where the paging block occurs and the paging block index within two 51-multiframes, as specified in subclause 6.5.3a3, monitors the EC-PICH block for a paging indication corresponding to its paging block, with the EC-PICH block occurring before the actual paging block. The EC-PICH block occurs in previous two 51-multiframes indicating the paging for both paging blocks.

6.5.4 Short Message Service Cell Broadcast (SMSCB)

When a short message service cell broadcast (SMSCB) message is to be sent, the message shall be sent on one of the two cell broadcast channels (CBCH): the basic and the extended cell broadcast channel in four consecutive multiframes using the block defined in table 3 of clause 7. The multiframes used for the basic cell broadcast channel shall be those in which TB = 0,1,2 and 3. The multiframes used for the extended cell broadcast channel shall be those in which TB = 4, 5, 6 and 7 where:

TB = (FN DIV 51)mod(8)

The SMSCB header shall be sent in the multiframe in which TB = 0 for the basic, and TB = 4 for the extended cell broadcast channel. When SMSCB is in use, this is indicated within the BCCH data (see 3GPP TS 44.018), and the parameter BS_AG_BLKS_RES shall be set to one or greater. When the CBCH is mapped onto a CCCH+SDCCH/4 channel, use of SMSCB does not place any constraint on the value of BS_AG_BLKS_RES.

NOTE 1: The MS reading of the extended CBCH is occasionally interrupted by MS idle mode procedures.

NOTE 2: For a certain network configuration the MS reading of the primary CBCH is occasionally interrupted by MS idle mode procedures when the MS is GPRS attached and in packet idle mode.

6.5.5 Voice group and voice broadcast call notifications

When mobile stations are to be alerted on a voice group or voice broadcast call, notification messages shall be sent on the notification channel (NCH), using the blocks defined in subclause 6.5.1.

When the NCH is in use, the parameter BS_AG_BLKS_RES shall be set to a value not lower than the number of blocks used for the NCH, see subclause 6.5.1 vii).

6.5.6 Determination of PCCCH_GROUP and PAGING_GROUP for MS in GPRS attached mode

This sub-clause applies to the case where a MS is not using extended DRX cycles.

If PCCCH is present, then it shall be used in the GPRS attached mode for paging and access. It shall also be used by an MS performing the GPRS attach procedure for access and monitoring of network response. In absence of PCCCH, CCCH shall be used for paging and access. If the determination of the specific paging multiframe and paging block index as specified in this subclause is not supported on CCCH by both the MS and the BTS, the method defined in subclause 6.5.2 and 6.5.3 shall be used. This is negotiated at GPRS attach.

PCCCH_GROUP (0 .. KC‑1) = ((IMSI mod 1000) mod (KC* N)) div N

PAGING_GROUP (0 … M-1) = ( ( (IMSI mod1000) div(KC*N) ) * N +

(IMSI mod 1000) mod N +
Max((m * M) div SPLIT_PG_CYCLE, m)) mod M
for m = 0, … , Min(M, SPLIT_PG_CYCLE) -1

where

KC = number of (P)CCCH in the cell =

BS_PCC_CHANS for PCCCH
BS_CC_CHANS for CCCH

M = number of paging blocks "available" on one (P)CCCH =
(12 – BS_PAG_BLKS_RES – BS_PBCCH_BLKS) * 64 for PCCCH
(9 – BS_AG_BLKS_RES) * 64 for CCCH not combined
(3 – BS_AG_BLKS_RES) * 64 for CCCH + SDCCH combined

N=

1 for PCCCH

(9 – BS_AG_BLKS_RES)*BS_PA_MFRMS for CCCH not combined
(3 – BS_AG_BLKS_RES)*BS_PA_MFRMS for CCCH/SDCCH combined

SPLIT_PG_CYCLE is an MS specific parameter negotiated at GPRS attach (see 3GPP TS 44.060)

IMSI = International Mobile Subscriber Identity, as defined in 3GPP TS 23.003.

mod = Modulo.

div = Integer division.

The MS shall receive paging and perform access on a single (P)CCCH identified by the PCCCH_GROUP parameter (see subclause 6.5.1).

In non-DRX mode, depending whether there is or not PCCCH channel(s) in the cell, the MS shall listen :

– to all M blocks per multiframe where paging may appear on a PCCCH channel, or

– to all blocks on a CCCH channel.

In DRX mode, the MS shall listen to the blocks corresponding to its paging group as defined by the different PAGING_GROUP values.

The required multiframe occurs when:

PAGING_GROUP div (M div 64) = (FN div MFL) mod 64

where

MFL = multiframe length = 51 for CCCH or 52 for PCCCH

The index to the required paging block of the "available" blocks in the multiframe:

Paging block index = PAGING_GROUP mod (M div 64)

where the index is then used with look‑up tables of clause 7 to determine the actual PPCH block to be monitored. Table 5 is used for CCCH and table 7 for PCCCH.

For CCCH, if SPLIT_PG_CYCLE>32 is negotiated, SPLIT_PG_CYCLE=32 shall be used, in order to provide the MS enough time for BSIC and System Information decoding.

NOTE: On BCCH, the operator should limit DRX_TIMER_MAX (see 3GPP TS 44.060) to 4 seconds of the same reason.

6.5.6a Determination of extended DRX cycle for MS in GPRS attached mode

A MS that uses eDRX (see 3GPP TS 44.018 [10]) indicates an eDRX cycle value from Table 6.5.6a-1 when negotiating eDRX with the network (see 3GPP TS 24.008 [21] and 3GPP TS 23.060 [22]). After power on and cell selection but before negotiating an eDRX cycle with the network a MS is not required to monitor the (EC-)PCH. After cell reselection from a cell where eDRX was used but before acquiring System Information in the new cell a MS shall monitor the (EC-)PCH according to its last negotiated eDRX cycle.

Table 6.5.6a-1: Set of eDRX Cycles Supported

eDRX cycle value	eDRX cycle length	Number of 51-MF per eDRX cycle (BS_ePA_MFRMS)	eDRX cycles per hyperframe
0000	~1.9 seconds	8	6656
0001	~3.8 seconds	16	3328
0010	~7.5 seconds	32	1664
0011	~12.2 seconds	52	1024
0100	~24.5 seconds	104	512
0101	~49 seconds	208	256
0110	~1.63 minutes	416	128
0111	~3.25 minutes	832	64
1000	~6.5 minutes	1664	32
1001	~13 minutes	3328	16
1010	~26 minutes	6656	8
1011	~52 minutes	13312	4
Note 1: 53248 51-multiframes occur with the TDMA FN space (2715648 TDMA frames) Note 2: All remaining eDRX Cycle Values are reserved

6.5.7 Determination of CTS_PAGING_GROUP and specific paging 52-multiframe for MS in CTS mode

CTS_PAGING_GROUP = (CTS-MSI mod N)

where:

CTS-MSI = CTS Mobile Subscriber Identity as defined in 3GPP TS 23.003

N = number of CTS paging groups defined in the CTS-FP and given to the CTS-MS during the attachment procedure (see 3GPP TS 44.056).

The required 52-multiframe where a paging message may be sent to the CTS-MS occurs when:

(FN div 52) mod N = CTS_PAGING_GROUP

6.5.8 Determination of single carrier fallback group

For a mobile in DLMC configuration the single carrier fallback group is determined by:

SINGLE_CARRIER_FALLBACK_GROUP (0 .. N‑1) = (TLLI mod 1000) mod N

The specific 52-multiframe during which an MS applies single carrier fallback occurs when:

SINGLE_CARRIER_FALLBACK_GROUP div (N div BS_PA_MFRMS) = (FN div 52) mod (BS_PA_MFRMS)

The required single carrier fallback block index is the specific basic radio block period (in case of RTTI configuration, the basic radio block period corresponds to two consecutive RTTI radio block periods) in the specific 52-multiframe during which an MS applies single carrier fallback and occurs when:

Single carrier fallback block index = SINGLE_CARRIER_FALLBACK_GROUP mod (N div BS_PA_MFRMS)

where

N = number of single carrier fallback blocks "available" on one PDTCH = (number of single carrier fallback blocks "available" in a 52-multiframe on one PDTCH) x BS_PA_MFRMS.

Number of single carrier fallback blocks "available" in a 52-multiframe on one PDTCH = 12.

TLLI = Temporary Logical Link Identity, as defined in 3GPP TS 23.003.

mod = Modulo.

div = Integer division.