5A.2.2a Dedicated carrier MBSFN Burst Format
25.2213GPPPhysical channels and mapping of transport channels onto physical channels (TDD)Release 17TS
In this case, there are two bursts, one is MBSFN Traffic burst (MT burst) for 7 normal timeslots, and the other is MBSFN Special burst (MS burst) for 1 short timeslot. Both of them consist of a preamble and a data symbol field, the lengths of which are different for the individual bursts. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 8A.a.
Table 8A.a: number of symbols per data field in a MBSFN burst
|
Spreading factor (Q) |
Number of symbos (N) per data field in Burst |
|
|
MT Burst |
MS Burst |
|
|
1 |
768 |
N/A |
|
2 |
384 |
N/A |
|
16 |
48 |
16 |
Note: MS burst only supports SF=16.
The support of both bursts is mandatory and only used in dedicated carrier MBSFN. The both different bursts defined here are well suited for this application, as described in the following paragraphs.
The MT burst can be used for the regular timeslots, the duration of which is 0.675ms. The data fields of the MT burst are 768 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8A.a above. The preamble of MT burst has a length of 96 chips. The MT burst is shown in Figure 18D.a. The contents of the burst fields are described in table 8B.a.
Table 8B.a: The contents of the MT burst
|
Chip number (CN) |
Length of field in chips |
Length of field in symbols |
Contents of field |
|
0-95 |
96 |
– |
Preamble |
|
96-863 |
768 |
cf table 8A.a |
Data symbols |
Figure 18D.a: Burst structure of the MT burst
The MS burst can be used for the short timeslot, the duration of which is 0.275ms. The data fields of the MS burst are 256 chips long. The corresponding number of symbols is 16, as indicated in table 8A.a above. The preamble of the MS burst has a length of 96 chips. The MS burst format is shown in Figure 18D.b. The contents of the burst fields are described in table 8B.b.
Table 8B.b: The contents of the MS burst
|
Chip number (CN) |
Length of field in chips |
Length of field in symbols |
Contents of field |
|
0-95 |
96 |
– |
Preamble |
|
96-351 |
256 |
cf table 8A.a |
Data symbols |
Figure 18D.b: Burst structure of the MS burst
5A.2.2.1 Transmission of TFCI
The traffic burst format provides the possibility for transmission of TFCI in uplink and downlink.
The transmission of TFCI is configured by higher Layers. For each CCTrCH it is indicated by higher layer signalling, which TFCI format is applied. Additionally for each allocated timeslot it is signalled individually whether that timeslot carries the TFCI or not. The TFCI is always present in the first timeslot in a radio frame for each CCTrCH. If a time slot contains the TFCI, then it is always transmitted using the physical channel with the lowest physical channel sequence number (p) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
The transmission of TFCI is done in the data parts of the respective physical channel, this means that TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. Hence the midamble structure and length is not changed.
The TFCI code word bits are equally distributed between the two subframes and the respective data fields. The TFCI code word is to be transmitted possibly either directly adjacent to the midamble or after the SS and TPC symbols. Figure 18E shows the position of the TFCI code word in a traffic burst, if neither SS nor TPC are transmitted. Figure 18F shows the position of the TFCI code word in a traffic burst , if SS and TPC are transmitted.
Figure 18E: Position of the TFCI code word in the traffic burst in case of no TPC and SS in 1.28 Mcps TDD
Figure 18F: Position of the TFCI code word in the traffic burst in case of TPC and SS in 1.28 Mcps TDD
5A.2.2.1a Transmission of TFCI for MT burst and MS burst
Both MT burst and MS burst provide the possibility for transmission of TFCI in downlink. The procedure of transmitting TFCI is the same as 5A.2.2.
The transmission of TFCI is done in the data parts of the respective physical channel, this means that TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. Hence the preamble structure and length is not changed.
The TFCI code word bits are equally distributed among the four subframes and the respective data fields. The TFCI code word is to be transmitted directly at the beginning and at the end of data symbols. Figure 18E.a shows the position of the TFCI code word in the MT burst. Figure 18E.b shows the position of the TFCI code word in the MS burst.
Note: when the modulation is 16QAM the number of the TFCI bits need be expanded. The procedure of expansion is detailed described in [7]
Figure 18E.a: Position of the TFCI code word in the MT burst format in 1.28 Mcps TDD
Figure 18E.b: Position of the TFCI code word in the MS burst format in 1.28 Mcps TDD
5A.2.2.2 Transmission of TPC
In this section, transmission of TPC over dedicated physical channels is described. Optionally, UTRAN may configure some UL CCTrCH’s to be controlled via TPC commands on PLCCH (for example in the case of HS-DSCH operation without an associated downlink DPCH). PLCCH is described in section 5A.3.13.
Within the context of this subclause, only those TPC commands not borne by PLCCH (in the DL case) nor by PLCCH-controlled physical channels (in the UL case) are considered. That is to say that those UL timeslot/CCTrCH pairs controlled by PLCCH and those DL TPC commands mapped to PLCCH are excluded from consideration when deriving the mapping between UL/DL TPC commands and the UL/DL CCTrCH’s they control. The association between PLCCH and UL timeslot/CCTrCH pair(s) is signalled by higher layers.
The burst type for dedicated channels provides the possibility for transmission of TPC in uplink and downlink.
The transmission of TPC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the SS information, which is transmitted after the midamble. Figure 18G shows the position of the TPC command in a traffic burst.
For every user the TPC information is to be transmitted at least once per 5ms sub-frame. For each allocated timeslot it is signalled individually whether that timeslot carries TPC information or not. If applied in a timeslot, transmission of TPC symbols is done in the data parts of the traffic burst and they are transmitted using the physical channel with the lowest physical channel sequence number (p) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
TPC symbols may also be transmitted on more than one physical channel in a time slot. For this purpose, higher layers allocate an additional number of NTPC physical channels, individually for each time slot. The TPC symbols shall then be transmitted using the physical channels with the NTPC+1 lowest physical channel sequence numbers (p) in that time slot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. If the rate matching function results in NRM < NTPC+1 remaining physical channels in this time slot, TPC symbols shall be transmitted only on the NRM remaining physical channels.
The TPC symbols are spread with the same spreading factor (SF) and spreading code as the data parts of the respective physical channel.
Figure 18G: Position of TPC information in the traffic burst in downlink and uplink
For the number of TPC symbols per time slot there are 3 possibilities, that can be configured by higher layers, individually for each timeslot:
1) one TPC symbol
2) no TPC symbols
3) 16/SF TPC symbols
So, in case 3), when SF=1, there are 16 TPC symbols which correspond to 32 bits (for QPSK) and 48 bits (for 8PSK).
In the following the uplink is described only. For the description of the downlink, downlink (DL) and uplink (UL) have to be interchanged.
Each of the TPC symbols for uplink power control in the DL will be associated with an UL time slot and an UL CCTrCH pair. This association varies with
– the number of allocated UL time slots and UL CCTrCHs on these time slots (time slot and CCTrCH pair) and
– the allocated TPC symbols in the DL.
In case a UE has
– more than one channelisation code
and/or
– channelisation codes being of lower spreading factor than 16 and using 16/SF SS and 16/SF TPC symbols,
the TPC commands for each ULtime slot CCTrCH pair (all channelisation codes on that time slot belonging to the same time slot and CCTrCH pair have the same TPC command) will be distributed to the following rules:
1. The ULtime slots and CCTrCH pairs the TPC commands are intended for will be numbered from the first to the last ULtime slot and CCTrCH pair allocated to the regarded UE (starting with 0). The number of a time slot and CCTrCH pair is smaller than the number of another time slot and CCTrCH pair within the same time slot if its spreading code with the lowest SC number according to the following table has a lower SC number than the spreading code with the lowest SC number of the other time slot and CCTrCH pair.
2. The commanding TPC symbols on all DL CCTrCHs allocated to one UE are numbered consecutively starting with zero according to the following rules:
a) The numbers of the TPC commands of a regarded DL time slot are lower than those of DL time slots being transmitted after that time slot
b) Within a DL time slot the numbers of the TPC commands of a regarded channelisation code are lower than those of channelisation codes having a higher spreading code number
The spreading code number is defined by the following table (see[8]):
|
SC number |
SF (Q) |
Walsh code number (k) |
|
0 |
16 |
|
|
… |
||
|
15 |
16 |
|
|
16 |
8 |
|
|
… |
||
|
23 |
8 |
|
|
24 |
4 |
|
|
… |
||
|
27 |
4 |
|
|
28 |
2 |
|
|
29 |
2 |
|
|
30 |
1 |
|
Note: Spreading factors 2-8 are not used in DL
c) Within a channelisation code numbers of the TPC commands are lower than those of TPC commands being transmitted after that time
The following equation is used to determine the UL time slot which is controlled by the regarded TPC symbol in the DL:
,
where
ULpos is the number of the controlled uplink time slot and CCTrCH pairs.
SFN’ is the system frame number counting the sub-frames. The system frame number of the radio frames (SFN) can be derived from SFN’ by
SFN=SFN’ div 2, where div is the remainder free division operation.
NUL_PCsymbols is the number of UL TPC symbols in a sub-frame (excluding those on PLCCH-controlled resources).
TPCDLpos is the number of the regarded UL TPC symbol in the DL within the sub-frame.
NULslot is the number of UL slots and CCTrCH pairs in a sub-frame (excluding those associated with PLCCH).
When one of the above parameters is changed due to higher layer reconfiguration, the new relationship between TPC symbols and controlled UL time slots shall be valid, beginning with the radio frame, for which the new parameters are set.
In Annex CB two examples of the association of TPC commands to time slots and CCTrCH pairs are shown.
Coding of TPC:
The relationship between the TPC Bits and the transmitter power control command for QPSK is the same as in the 3.84Mcps TDD cf. [5.2.2.5 ‘Transmission of TPC’].
The relationship between the TPC Bits and the transmitter power control command for 8PSK is given in table 8C
Table 8C: TPC Bit Pattern for 8PSK
|
TPC Bits |
TPC command |
Meaning |
|
000 |
‘Down’ |
Decrease Tx Power |
|
110 |
‘Up’ |
Increase Tx Power |
5A.2.2.3 Transmission of SS
In this section, transmission of SS over dedicated physical channels is described. Optionally, UTRAN may configure some UL CCTrCH’s to be controlled via SS commands on PLCCH (for example in the case of HS-DSCH operation without an associated downlink DPCH). PLCCH is described in section 5A.3.13.
Within the context of this subclause, only those SS commands not borne by PLCCH are considered. That is to say that those UL timeslots controlled exclusively by PLCCH and those SS commands carried by PLCCH are excluded from consideration when deriving the mapping between DL SS commands and the UL timeslots they control. The association between PLCCH and UL timeslot/CCTrCH pair(s) is signalled by higher layers.
The burst type for dedicated channels provides the possibility for transmission of uplink synchronisation control (ULSC).
The transmission of ULSC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The ULSC information is to be transmitted directly after the midamble. Figure 18H shows the position of the SS command in a traffic burst.
For every user the ULSC information shall be transmitted at least once per transmitted sub-frame.
For each allocated timeslot it is signalled individually whether that timeslot carries ULSC information or not. If applied in a time slot, transmission of SS symbols is done in the data parts of the traffic burst and they are transmitted using the physical channel with the lowest physical channel sequence number (p) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7].
SS symbols may also be transmitted on more than one physical channel in a time slot. For this purpose, higher layers allocate an additional number of NSS physical channels, individually for each time slot. The SS symbols shall then be transmitted using the physical channels with the NSS+1 lowest physical channel sequence numbers (p) in that time slot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. If the rate matching function results in NRM < NSS+1 remaining physical channels in this time slot, SS symbols shall be transmitted only on the NRM remaining physical channels.
The SS symbols are spread with the same spreading factor (SF) and spreading code as the data parts of the respective physical channel.
The SS is utilised to command a timing adjustment by (k/8) Tc each M sub-frames, where Tc is the chip period. The k and M values are signalled by the network. The SS, as one of L1 signals, is to be transmitted once per 5ms sub-frame.
M (1-8) and k (1-8) can be adjusted during call setup or readjusted during the call.
Note: The smallest step for the SS signalled by the UTRAN is 1/8 Tc. For the UE capabilities regarding the SS adjustment of the UE it is suggested to set the tolerance for the executed command to be [1/9;1/7] Tc.
Figure 18H: Position of ULSC information in the traffic burst (downlink and uplink)
Note that for the uplink where there is no SS symbol used, the SS symbol space is reserved for future use. This can keep UL and DL slots the same structure.
For the number of SS symbols per time slot there are 3 possibilities, that cn be configured by higher layers individually for each time slot:
– one SS symbol
– no SS symbol
– 16/SF SS symbols
So, in case 3, when SF=1, there are 16 SS symbols which correspond to 32 bits (for QPSK) and 48 bits (for 8PSK).
Each of the SS symbols in the DL will be associated with an UL time slot depending on the allocated UL time slots and the allocated SS symbols in the DL.
Note: Even though the different time slots of the UE are controlled with independent SS commands, the UE is not in need to execute SS commands leading to a deviation of more than [3] chip with respect to the average timing advance applied by the UE.
The synchronisation shift commands for each UL time slot (all channelisation codes on that time slot have the same SS command) will be distributed to the following rules:
1. The UL time slots the SS commands are intended for will be numbered from the first to the last UL time slot occupied by the regarded UE (starting with 0) considering all CCTrCHs allocated to that UE.
2. The commanding SS symbols on all downlink CCTrCHs allocated to one UE are numbered consecutively starting with zero according to the following rules:
a) The numbers of the SS commands of a regarded DL time slot are lower than those of DL time slots being transmitted after that time slot
b) Within a DL time slot the numbers of the SS commands of a regarded channelisation code are lower than those of channelisation codes having a bigger spreading code number
The spreading code number is defined by the following table: (see TS 25.223)
|
Spreading code number |
SF (Q) |
Walsh code number (k) |
|
0 |
16 |
|
|
… |
||
|
15 |
16 |
|
|
Spreading factors 2-8 are nor used in DL |
||
|
30 |
1 |
|
c) Within a channelisation code numbers of the SS commands are lower than those of SS commands being transmitted after that time
The following equation is used to determine the UL time slot which is controlled by the regarded SS symbol:
,
where
ULpos is the number of the controlled uplink time slot.
SFN’ is the system frame number counting the sub-frames. The system frame number of the radio frames (SFN) can be derived from SFN’ by
SFN=SFN’ div 2, where div is the remainder free division operation.
NSSsymbols is the number of SS symbols in a sub-frame (excluding those associated with PLCCH).
SSpos is the number of the regarded SS symbol within the sub-frame.
NULslot is the number of UL slots in a sub-frame (excluding those slots exclusively controlled by PLCCH).
When one of the above parameters is changed due to higher layer reconfiguration, the new relationship between SS symbols and controlled UL time slots shall be valid, beginning with the radio frame, for which the new parameters are set.
The relationship between the SS Bits and the SS command for QPSK is the given in table 8D:
Table 8D: Coding of the SS for QPSK
|
SS Bits |
SS command |
Meaning |
|
00 |
‘Down’ |
Decrease synchronisation shift by k/8 Tc |
|
11 |
‘Up’ |
Increase synchronisation shift by k/8 Tc |
|
01 |
‘Do nothing’ |
No change |
The relationship between the SS Bits and the SS command for 8PSK is given in table 8E:
Table 8E: Coding of the SS for 8PSK
|
SS Bits |
SS command |
Meaning |
|
000 |
‘Down’ |
Decrease synchronisation shift by k/8 Tc |
|
110 |
‘Up’ |
Increase synchronisation shift by k/8 Tc |
|
011 |
‘Do nothing’ |
No change |
5A.2.2.4 Timeslot formats
The timeslot format depends on the spreading factor, the number of the TFCI code word bits, the number of SS and TPC symbols and the applied modulation scheme (QPSK/8PSK) as depicted in the following tables.
5A.2.2.4.1 Timeslot formats for QPSK
5A.2.2.4.1.1 Downlink timeslot formats
Table 8F : Time slot formats for the Downlink
|
Slot Format # |
SpreadingFactor |
Midamble length (chips) |
NTFCI code word (bits) |
NSS & NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field(1) (bits) |
Ndata/data field(2) (bits) |
|---|---|---|---|---|---|---|---|---|
|
0 |
16 |
144 |
0 |
0 & 0 |
88 |
88 |
44 |
44 |
|
1 |
16 |
144 |
4 |
0 & 0 |
88 |
86 |
42 |
44 |
|
2 |
16 |
144 |
8 |
0 & 0 |
88 |
84 |
42 |
42 |
|
3 |
16 |
144 |
16 |
0 & 0 |
88 |
80 |
40 |
40 |
|
4 |
16 |
144 |
32 |
0 & 0 |
88 |
72 |
36 |
36 |
|
5 |
16 |
144 |
0 |
2 & 2 |
88 |
84 |
44 |
40 |
|
6 |
16 |
144 |
4 |
2 & 2 |
88 |
82 |
42 |
40 |
|
7 |
16 |
144 |
8 |
2 & 2 |
88 |
80 |
42 |
38 |
|
8 |
16 |
144 |
16 |
2 & 2 |
88 |
76 |
40 |
36 |
|
9 |
16 |
144 |
32 |
2 & 2 |
88 |
68 |
36 |
32 |
|
10 |
1 |
144 |
0 |
0 & 0 |
1408 |
1408 |
704 |
704 |
|
11 |
1 |
144 |
4 |
0 & 0 |
1408 |
1406 |
702 |
704 |
|
12 |
1 |
144 |
8 |
0 & 0 |
1408 |
1404 |
702 |
702 |
|
13 |
1 |
144 |
16 |
0 & 0 |
1408 |
1400 |
700 |
700 |
|
14 |
1 |
144 |
32 |
0 & 0 |
1408 |
1392 |
696 |
696 |
|
15 |
1 |
144 |
0 |
2 & 2 |
1408 |
1404 |
704 |
700 |
|
16 |
1 |
144 |
4 |
2 & 2 |
1408 |
1402 |
702 |
700 |
|
17 |
1 |
144 |
8 |
2 & 2 |
1408 |
1400 |
702 |
698 |
|
18 |
1 |
144 |
16 |
2 & 2 |
1408 |
1396 |
700 |
696 |
|
19 |
1 |
144 |
32 |
2 & 2 |
1408 |
1388 |
696 |
692 |
|
20 |
1 |
144 |
0 |
32 & 32 |
1408 |
1344 |
704 |
640 |
|
21 |
1 |
144 |
4 |
32 & 32 |
1408 |
1342 |
702 |
640 |
|
22 |
1 |
144 |
8 |
32 & 32 |
1408 |
1340 |
702 |
638 |
|
23 |
1 |
144 |
16 |
32 & 32 |
1408 |
1336 |
700 |
636 |
|
24 |
1 |
144 |
32 |
32 & 32 |
1408 |
1328 |
696 |
632 |
5A.2.2.4.1.2 Uplink timeslot formats
Table 8G : Time slot formats for the Uplink
|
Slot Format # |
Spreading Factor |
Midamble length (chips) |
NTFCI code word (bits) |
NSS & NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field(1) (bits) |
Ndata/data field(2) (bits) |
|---|---|---|---|---|---|---|---|---|
|
0 |
16 |
144 |
0 |
0 & 0 |
88 |
88 |
44 |
44 |
|
1 |
16 |
144 |
4 |
0 & 0 |
88 |
86 |
42 |
44 |
|
2 |
16 |
144 |
8 |
0 & 0 |
88 |
84 |
42 |
42 |
|
3 |
16 |
144 |
16 |
0 & 0 |
88 |
80 |
40 |
40 |
|
4 |
16 |
144 |
32 |
0 & 0 |
88 |
72 |
36 |
36 |
|
5 |
16 |
144 |
0 |
2 & 2 |
88 |
84 |
44 |
40 |
|
6 |
16 |
144 |
4 |
2 & 2 |
88 |
82 |
42 |
40 |
|
7 |
16 |
144 |
8 |
2 & 2 |
88 |
80 |
42 |
38 |
|
8 |
16 |
144 |
16 |
2 & 2 |
88 |
76 |
40 |
36 |
|
9 |
16 |
144 |
32 |
2 & 2 |
88 |
68 |
36 |
32 |
|
10 |
8 |
144 |
0 |
0 & 0 |
176 |
176 |
88 |
88 |
|
11 |
8 |
144 |
4 |
0 & 0 |
176 |
174 |
86 |
88 |
|
12 |
8 |
144 |
8 |
0 & 0 |
176 |
172 |
86 |
86 |
|
13 |
8 |
144 |
16 |
0 & 0 |
176 |
168 |
84 |
84 |
|
14 |
8 |
144 |
32 |
0 & 0 |
176 |
160 |
80 |
80 |
|
15 |
8 |
144 |
0 |
2 & 2 |
176 |
172 |
88 |
84 |
|
16 |
8 |
144 |
4 |
2 & 2 |
176 |
170 |
86 |
84 |
|
17 |
8 |
144 |
8 |
2 & 2 |
176 |
168 |
86 |
82 |
|
18 |
8 |
144 |
16 |
2 & 2 |
176 |
164 |
84 |
80 |
|
19 |
8 |
144 |
32 |
2 & 2 |
176 |
156 |
80 |
76 |
|
20 |
8 |
144 |
0 |
4 & 4 |
176 |
168 |
88 |
80 |
|
21 |
8 |
144 |
4 |
4 & 4 |
176 |
166 |
86 |
80 |
|
22 |
8 |
144 |
8 |
4 & 4 |
176 |
164 |
86 |
78 |
|
23 |
8 |
144 |
16 |
4 & 4 |
176 |
160 |
84 |
76 |
|
24 |
8 |
144 |
32 |
4 & 4 |
176 |
152 |
80 |
72 |
|
25 |
4 |
144 |
0 |
0 & 0 |
352 |
352 |
176 |
176 |
|
26 |
4 |
144 |
4 |
0 & 0 |
352 |
350 |
174 |
176 |
|
27 |
4 |
144 |
8 |
0 & 0 |
352 |
348 |
174 |
174 |
|
28 |
4 |
144 |
16 |
0 & 0 |
352 |
344 |
172 |
172 |
|
29 |
4 |
144 |
32 |
0 & 0 |
352 |
336 |
168 |
168 |
|
30 |
4 |
144 |
0 |
2 & 2 |
352 |
348 |
176 |
172 |
|
31 |
4 |
144 |
4 |
2 & 2 |
352 |
346 |
174 |
172 |
|
32 |
4 |
144 |
8 |
2 & 2 |
352 |
344 |
174 |
170 |
|
33 |
4 |
144 |
16 |
2 & 2 |
352 |
340 |
172 |
168 |
|
34 |
4 |
144 |
32 |
2 & 2 |
352 |
332 |
168 |
164 |
|
35 |
4 |
144 |
0 |
8 & 8 |
352 |
336 |
176 |
160 |
|
36 |
4 |
144 |
4 |
8 & 8 |
352 |
334 |
174 |
160 |
|
37 |
4 |
144 |
8 |
8 & 8 |
352 |
332 |
174 |
158 |
|
38 |
4 |
144 |
16 |
8 & 8 |
352 |
328 |
172 |
156 |
|
39 |
4 |
144 |
32 |
8 & 8 |
352 |
320 |
168 |
152 |
|
40 |
2 |
144 |
0 |
0 & 0 |
704 |
704 |
352 |
352 |
|
41 |
2 |
144 |
4 |
0 & 0 |
704 |
702 |
350 |
352 |
|
42 |
2 |
144 |
8 |
0 & 0 |
704 |
700 |
350 |
350 |
|
43 |
2 |
144 |
16 |
0 & 0 |
704 |
696 |
348 |
348 |
|
44 |
2 |
144 |
32 |
0 & 0 |
704 |
688 |
344 |
344 |
|
45 |
2 |
144 |
0 |
2 & 2 |
704 |
700 |
352 |
348 |
|
46 |
2 |
144 |
4 |
2 & 2 |
704 |
698 |
350 |
348 |
|
47 |
2 |
144 |
8 |
2 & 2 |
704 |
696 |
350 |
346 |
|
48 |
2 |
144 |
16 |
2 & 2 |
704 |
692 |
348 |
344 |
|
49 |
2 |
144 |
32 |
2 & 2 |
704 |
684 |
344 |
340 |
|
50 |
2 |
144 |
0 |
16 & 16 |
704 |
672 |
352 |
320 |
|
51 |
2 |
144 |
4 |
16 & 16 |
704 |
670 |
350 |
320 |
|
52 |
2 |
144 |
8 |
16 & 16 |
704 |
668 |
350 |
318 |
|
53 |
2 |
144 |
16 |
16 & 16 |
704 |
664 |
348 |
316 |
|
54 |
2 |
144 |
32 |
16 & 16 |
704 |
656 |
344 |
312 |
|
55 |
1 |
144 |
0 |
0 & 0 |
1408 |
1408 |
704 |
704 |
|
56 |
1 |
144 |
4 |
0 & 0 |
1408 |
1406 |
702 |
704 |
|
57 |
1 |
144 |
8 |
0 & 0 |
1408 |
1404 |
702 |
702 |
|
58 |
1 |
144 |
16 |
0 & 0 |
1408 |
1400 |
700 |
700 |
|
59 |
1 |
144 |
32 |
0 & 0 |
1408 |
1392 |
696 |
696 |
|
60 |
1 |
144 |
0 |
2 & 2 |
1408 |
1404 |
704 |
700 |
|
61 |
1 |
144 |
4 |
2 & 2 |
1408 |
1402 |
702 |
700 |
|
62 |
1 |
144 |
8 |
2 & 2 |
1408 |
1400 |
702 |
698 |
|
63 |
1 |
144 |
16 |
2 & 2 |
1408 |
1396 |
700 |
696 |
|
64 |
1 |
144 |
32 |
2 & 2 |
1408 |
1388 |
696 |
692 |
|
65 |
1 |
144 |
0 |
32 & 32 |
1408 |
1344 |
704 |
640 |
|
66 |
1 |
144 |
4 |
32 & 32 |
1408 |
1342 |
702 |
640 |
|
67 |
1 |
144 |
8 |
32 & 32 |
1408 |
1340 |
702 |
638 |
|
68 |
1 |
144 |
16 |
32 & 32 |
1408 |
1336 |
700 |
636 |
|
69 |
1 |
144 |
32 |
32 & 32 |
1408 |
1328 |
696 |
632 |
5A.2.2.4.2 Time slot formats for 8PSK
The Downlink and the Uplink timeslot formats are described together in the following table.
Table 8H: Timeslot formats for 8PSK modulation
|
Slot Format # |
Spreading Factor |
Midamble length (chips) |
NTFCI code word (bits) |
NSS & NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field(1) (bits) |
Ndata/data field(2) (bits) |
|---|---|---|---|---|---|---|---|---|
|
0 |
1 |
144 |
0 |
0 & 0 |
2112 |
2112 |
1056 |
1056 |
|
1 |
1 |
144 |
6 |
0 & 0 |
2112 |
2109 |
1053 |
1056 |
|
2 |
1 |
144 |
12 |
0 & 0 |
2112 |
2106 |
1053 |
1053 |
|
3 |
1 |
144 |
24 |
0 & 0 |
2112 |
2100 |
1050 |
1050 |
|
4 |
1 |
144 |
48 |
0 & 0 |
2112 |
2088 |
1044 |
1044 |
|
5 |
1 |
144 |
0 |
3 & 3 |
2112 |
2106 |
1056 |
1050 |
|
6 |
1 |
144 |
6 |
3 & 3 |
2112 |
2103 |
1053 |
1050 |
|
7 |
1 |
144 |
12 |
3 & 3 |
2112 |
2100 |
1053 |
1047 |
|
8 |
1 |
144 |
24 |
3 & 3 |
2112 |
2094 |
1050 |
1044 |
|
9 |
1 |
144 |
48 |
3 & 3 |
2112 |
2082 |
1044 |
1038 |
|
10 |
1 |
144 |
0 |
48 & 48 |
2112 |
2016 |
1056 |
960 |
|
11 |
1 |
144 |
6 |
48 & 48 |
2112 |
2013 |
1053 |
960 |
|
12 |
1 |
144 |
12 |
48 & 48 |
2112 |
2010 |
1053 |
957 |
|
13 |
1 |
144 |
24 |
48 & 48 |
2112 |
2004 |
1050 |
954 |
|
14 |
1 |
144 |
48 |
48 & 48 |
2112 |
1992 |
1044 |
948 |
|
15 |
16 |
144 |
0 |
0 & 0 |
132 |
132 |
66 |
66 |
|
16 |
16 |
144 |
6 |
0 & 0 |
132 |
129 |
63 |
66 |
|
17 |
16 |
144 |
12 |
0 & 0 |
132 |
126 |
63 |
63 |
|
18 |
16 |
144 |
24 |
0 & 0 |
132 |
120 |
60 |
60 |
|
19 |
16 |
144 |
48 |
0 & 0 |
132 |
108 |
54 |
54 |
|
20 |
16 |
144 |
0 |
3 & 3 |
132 |
126 |
66 |
60 |
|
21 |
16 |
144 |
6 |
3 & 3 |
132 |
123 |
63 |
60 |
|
22 |
16 |
144 |
12 |
3 & 3 |
132 |
120 |
63 |
57 |
|
23 |
16 |
144 |
24 |
3 & 3 |
132 |
114 |
60 |
54 |
|
24 |
16 |
144 |
48 |
3 & 3 |
132 |
102 |
54 |
48 |
5A.2.2.4.3 Time slot formats for MBSFN
Downlink timeslot formats using QPSK or 16QAM modulation is dedicated for MBSFN operation and is described in the following table.
Table 8Ha : Time slot formats for MBSFN
|
Slot Format # |
SpreadingFactor |
Midamble /preamble length (chips) |
NTFCI code word (bits) |
NSS & NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field(1) (bits) |
Ndata/data field(2) (bits) |
|
|---|---|---|---|---|---|---|---|---|---|
|
0(QPSK) * |
1 |
144 |
16 |
0 & 0 |
1408 |
1404 |
702 |
702 |
|
|
1(QPSK) * |
16 |
144 |
16 |
0 & 0 |
88 |
84 |
42 |
42 |
|
|
2(16QAM) * |
1 |
144 |
32 |
0 & 0 |
2816 |
2808 |
1404 |
1404 |
|
|
3(16QAM)* |
16 |
144 |
32 |
0 & 0 |
176 |
168 |
84 |
84 |
|
|
4(QPSK)** |
1 |
96 |
16 |
0 & 0 |
1536 |
1532 |
N/A |
N/A |
|
|
5(QPSK) ** |
2 |
96 |
16 |
0 & 0 |
768 |
764 |
N/A |
N/A |
|
|
6(QPSK)** |
16 |
96 |
16 |
0 & 0 |
96 |
92 |
N/A |
N/A |
|
|
7(16QAM)** |
1 |
96 |
32 |
0 & 0 |
3072 |
3064 |
N/A |
N/A |
|
|
8(16QAM) ** |
2 |
96 |
16 |
0 & 0 |
1536 |
1528 |
N/A |
N/A |
|
|
9(16QAM)** |
16 |
96 |
32 |
0 & 0 |
192 |
184 |
N/A |
N/A |
|
|
10(QPSK)*** |
16 |
96 |
16 |
0 & 0 |
32 |
24 |
N/A |
N/A |
|
|
11(QPSK)*** |
16 |
96 |
0 |
0 & 0 |
32 |
32 |
N/A |
N/A |
|
NOTE: * denotes that these timeslot formats are used in the traffic burst for mixed carrier MBSFN. ** denotes that these timeslot formats are used in the MT burst for dedicated carrier MBSFN. *** denotes that these timeslot formats are used in the MS burst for dedicated carrier MBSFN. The burst in the dedicated carrier MBSFN has only one date field.