5 Multiplexing, channel coding and interleaving for the 3.84 Mcps MBSFN IMB option
25.2223GPPMultiplexing and channel coding (TDD)Release 17TS
5.1 General
Data streams from/to MAC and higher layers (Transport block / Transport block set) are encoded/decoded to offer transport services over the radio transmission link. The channel coding scheme is a combination of error detection, error correcting, rate matching, interleaving and the mapping of transport channels onto physical channels.
5.2 General coding/multiplexing of TrCHs
This section only applies to the transport channels BCH and FACH.
Data arrives to the coding/multiplexing unit in form of transport block sets once every transmission time interval. The transmission time interval is transport-channel specific from the set {10 ms, 20 ms, 40 ms, 80 ms}. An overview of the coding/multiplexing steps applicable to MBSFN IMB is shown in figure 2 of subclause 4.2 in [3].
5.2.1 CRC attachment
Error detection is provided on transport blocks through a Cyclic Redundancy Check (CRC). CRC attachment shall be performed in accordance with the general method described in subclause 4.2.1 of [3].
5.2.2 Transport block concatenation and code block segmentation
Transport blocks, with attached CRCs, are concatenated and segmentated into code blocks. Transport block concatenation and code block segmentation shall be performed in accordance with the general method described in subclause 4.2.2 of [3].
5.2.3 Channel coding
Code blocks are delivered to the channel coding. Channel coding shall be performed in accordance with the general method described in subclause 4.2.3 of [3]. The following restrictions apply:
– Convolutional coding shall be applied to FACH transport channel mapped on S-CCPCH frame type 1 only.
– Turbo coding shall be applied to FACH transport channels mapped on S-CCPCH frame type 2 only.
5.2.4 1st Interleaving
First interleaving shall be performed in accordance with the general methods described in subclause 4.2.5 of [3].
5.2.5 Radio frame segmentation
Radio frame segmentation shall be performed in accordance with the general method described in subclause 4.2.6 of [3].
5.2.6 Rate matching
Rate matching shall be performed in accordance with the general method described in subclause 4.2.7 of [3], in which the downlink description is only relevant. Only flexible positions of TrCHs are supported for the MBSFN IMB option.
For S-CCPCH frame type 2, the number of bits available to the CCTrCH in one radio frame using P physical channels is defined as Ndata,* = 3Ndata1+ (P-1)3 N’data1, where Ndata1 is defined in [2] and N’data1 is the data size of the corresponding slot format with zero TFCI bits.
5.2.7 TrCH multiplexing
Transport channel multiplexing shall be performed in accordance with the general method described in subclause 4.2.8 of [3].
5.2.8 Insertion of discontinuous transmission (DTX) indication bits
DTX is used to fill up the radio frame with bits. The DTX indication bits inserted in this step shall be placed at the end of the radio frame, corresponding to flexible positions of TrCHs in the radio frame [3]. Note that the DTX indication bits will be distributed over all slots after 2nd interleaving.
The bits input to the DTX insertion block are denoted by
, where S is the number of bits from TrCH multiplexing. The bits output from the DTX insertion block are denoted byand defined by the following relations:
k = 1, 2, 3, …,S
k = S+1, S+2, S+3, …,W
where DTX indication bits are denoted by . Note that bits wk are three valued and that W = Ndata,*.
5.2.9 Physical channel segmentation
For the 3.84 Mcps MBSFN IMB option, physical channel segmentation is applicable to S-CCPCH frame type 2 only.
When more than one PhCH is used, physical channel segmentation divides the bits among the different PhCHs. The bits input to the physical channel segmentation are denoted by, where W is the number of bits input to the physical channel segmentation block. The number of PhCHs is denoted by P.
The bits after physical channel segmentation are denoted
, where p is PhCH number and Up is the number of bits in one radio frame of the pth PhCH. The relation between wk and up,k is given below.
Bits on first PhCH after physical channel segmentation:
k = 1, 2 , …, U1
Bits on second PhCH after physical channel segmentation:
k = 1, 2 , …, U2
…
Bits on the Pth PhCH after physical channel segmentation:
k = 1, 2 , …, UP
The number of bits Up in one radio frame of the pth PhCH is 3Ndata1 for p=1 and 3N’data1 for p = 2,3,…, P, where Ndata1 is defined in [2] and N’data1 is the data size of the corresponding slot format with zero TFCI bits.
5.2.10 2nd Interleaving
Second interleaving is performed in accordance with the general method described in section 4.2.11 of [3]. For S-CCPCH frame type 2, 2nd interleaving is performed per physical channel of the CCTrCH.
5.2.11 Physical channel mapping
Physical channel mapping shall be performed in accordance with the general method described in subclause 4.2.12 in [3], in which the downlink description is only relevant.
5.2.12 Restrictions on different types of CCTrCHs
Restrictions on the different types of CCTrCHs are described in general terms in [16]. In this subclause those restrictions are given with layer 1 notation.
5.2.12.1 Broadcast channel (BCH)
The restrictions of subclause 4.2.13.6 of [3] apply.
5.2.12.2 Forward access channel (FACH)
– The maximum value of the number of TrCHs I in a CCTrCH and the maximum value of the number of transport blocks Mi on each transport channel are given from the UE capability class.
– Only one Secondary CCPCH frame type 1 is used per CCTrCH.
– The maximum number of Secondary CCPCHs of frame type 2 used per CCTrCH is defined in [17].
5.2.13 Multiplexing of different TrCHs into one CCTrCH, and mapping of one CCTrCH onto physical channels
Multiplexing of different transport channels into one coded composite transport channel shall be performed in accordance with the general method described in 4.2.14 of [3].
5.3 Transport format detection
For MBSFN IMB operations, the transport format combination is signalled using the TFCI field of an S-CCPCH slot and only TFCI based detection shall be used.
5.3.1 Transport format detection based on TFCI
When a TFCI is available, then TFCI based detection shall be applicable to all TrCHs within the CCTrCH. The TFCI informs the receiver about the transport format combination of the CCTrCHs. As soon as the TFCI is detected, the transport format combination, and hence the transport formats of the individual transport channels are known.
5.3.2 Coding of Transport-Format-Combination Indicator (TFCI)
The number of TFCI bits to be encoded per CCTrCH shall always be within the range 1 to 5. These bits shall be encoded according to the general method of subclause 4.3.1.2.2 to produce 16 encoded bits b0 to b15. This procedure is valid also for the case where the number of TFCI bits to be encoded is less than 3.
5.3.3 Mapping of TFCI words
5.3.3.1 Mapping of TFCI bits for Secondary CCPCH
The 16 encoded TFCI bits are directly mapped to the S-CCPCH slots of the radio frame. Within a slot the bit with lower index is transmitted before the bit with higher index. The coded bits bk, are mapped to the transmitted TFCI bits dk, according to the following formula:
dk = bk mod 16
For S-CCPCH frame type 1, k = 0, 1, 2, …, 29. For S-CCPCH frame type 2 using QPSK data modulation, k = 0, 1, 2, …, 47 whilst for S-CCPCH frame type 2 using 16-QAM data modulation, k = 0, 1, 2, …, 23.
The set of TFCI bits dk shall be modulated as defined in [9] and mapped to slots of the radio frame such that they are transmitted in ascending order of k.
Annex A (informative):
Change history
|
Change history |
|||||||
|---|---|---|---|---|---|---|---|
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
14/01/00 |
RAN_05 |
RAN_05 |
– |
Approved at TSG RAN #5 and placed under Change Control |
– |
3.0.0 |
|
|
14/01/00 |
RAN_06 |
RP-99694 |
001 |
3 |
Correction of rate matching parameters for repetition after 1st Interleaving in 25.222 |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99694 |
002 |
1 |
Clarification of bit separation and collection |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99694 |
003 |
– |
Changing the initial offset value for convolutional code rate matching |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99693 |
004 |
1 |
Editorial corrections to TS 25.222 |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99694 |
007 |
– |
Update of rate matching rule for TDD |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99694 |
009 |
1 |
Modified physical channel mapping scheme |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99694 |
013 |
– |
Introduction of TFCI for S-CCPCH in TDD mode |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99694 |
015 |
– |
TFCI coding and mapping in TDD |
3.0.0 |
3.1.0 |
|
14/01/00 |
– |
– |
– |
Change history was added by the editor |
3.1.0 |
3.1.1 |
|
|
31/03/00 |
RAN_07 |
RP-000068 |
017 |
– |
Corrections to TS 25.222 |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
018 |
– |
Refinements of Physical Channel Mapping |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
019 |
1 |
TFCI coding specification in TDD |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
021 |
– |
Modification of Turbo code internal interleaver |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
023 |
– |
Update of TS 25.222 – clarification of BTFD for TDD |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
025 |
– |
Change of TFCI basis for TDD |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
026 |
– |
Padding Function for Turbo coding of small blocks |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
027 |
– |
Editorial modification of shifting parameter calculation for turbo code puncturing |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000068 |
029 |
1 |
Editorial changes of channel coding section |
3.1.1 |
3.2.0 |
|
26/06/00 |
RAN_08 |
RP-000272 |
030 |
– |
Parity bit attachment to 0 size transport block |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000272 |
031 |
– |
Correction of the mapping formula |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000272 |
034 |
– |
Alignment of Multiplexing for TDD |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000272 |
036 |
2 |
Bit separation of the Turbo encoded data |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000272 |
038 |
2 |
Revision of code block segmentation description |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000272 |
039 |
– |
Editorial corrections in channel coding section |
3.2.0 |
3.3.0 |
|
23/09/00 |
RAN_09 |
RP-000345 |
040 |
1 |
Update of TS 25.222 |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000345 |
041 |
1 |
Editorial corrections in Turbo code internal interleaver section |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000345 |
042 |
– |
Paging Indicator Terminology |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000345 |
043 |
1 |
Bit separation and collection for rate matching |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000345 |
048 |
– |
Puncturing Limit definition in WG1 specification |
3.3.0 |
3.4.0 |
|
15/12/00 |
RAN_10 |
RP-000543 |
049 |
– |
Clarification on the Ci formula |
3.4.0 |
3.5.0 |
|
15/12/00 |
RAN_10 |
RP-000543 |
050 |
– |
Correction on TFCI & TPC Transmission |
3.4.0 |
3.5.0 |
|
15/12/00 |
RAN_10 |
RP-000543 |
053 |
1 |
Editorial corrections in TS 25.222 |
3.4.0 |
3.5.0 |
|
16/03/01 |
RAN_11 |
– |
– |
– |
Approved as Release 4 specification (v4.0.0) at TSG RAN #11 |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010063 |
051 |
1 |
Bit Scrambling for TDD |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010063 |
054 |
1 |
Corrections & Clarifications for TS25.222 |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010071 |
055 |
1 |
Inclusion of 1.28Mcps TDD in TS 25.222 |
3.5.0 |
4.0.0 |
|
21/09/01 |
RAN_13 |
RP-010523 |
057 |
– |
TFCI Terminology |
4.0.0 |
4.1.0 |
|
21/09/01 |
RAN_13 |
RP-010529 |
058 |
– |
5ms TTI for PRACH for 1.28 Mcps TDD |
4.0.0 |
4.1.0 |
|
21/09/01 |
RAN_13 |
RP-010529 |
060 |
– |
A correction on the meaning of FPACH in TS 25.222 |
4.0.0 |
4.1.0 |
|
14/12/01 |
RAN_14 |
RP-010747 |
059 |
– |
Bit Scrambling for TDD |
4.1.0 |
4.2.0 |
|
14/12/01 |
RAN_14 |
RP-010747 |
061 |
– |
Corrections in clause 4.1 and 4.2 of TS 25.222 |
4.1.0 |
4.2.0 |
|
08/03/02 |
RAN_15 |
RP-020050 |
063 |
1 |
Correction to addition of padding zeros to PICH in TDD |
4.2.0 |
4.3.0 |
|
08/03/02 |
RAN_15 |
RP-020050 |
065 |
3 |
Clarification of the requirement for the determination of the rate matching parameters and editorial corrections to 25.222 |
4.2.0 |
4.3.0 |
|
08/03/02 |
RAN_15 |
RP-020058 |
066 |
2 |
Inclusion of HSDPA in 25.222 |
4.2.0 |
5.0.0 |
|
07/06/02 |
RAN_16 |
RP-020311 |
077 |
– |
Second Stage Interleaving and Physical Channel Mapping |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020311 |
076 |
1 |
Zero padding for TFCI (3.84Mcps TDD) |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020314 |
073 |
– |
Correction to addition of padding zeros to PICH in 1.28 Mcps TDD |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020314 |
086 |
– |
Zero padding for TFCI (1.28Mcps TDD) |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020317 |
078 |
2 |
Removal of inconsistencies and ambiguities in the HARQ description |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020317 |
079 |
4 |
Corrections to HS-DSCH coding |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020317 |
082 |
1 |
Corrections to HSDPA Multiplexing and Coding |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020317 |
084 |
– |
Introduction of HS-SCCH Cyclic Sequence Counter for TDD |
5.0.0 |
5.1.0 |
|
19/09/02 |
RAN_17 |
RP-020570 |
097 |
1 |
Clarification of the definition of layer 1 transport channel numbers |
5.1.0 |
5.2.0 |
|
19/09/02 |
RAN_17 |
RP-020585 |
093 |
– |
HS-DSCH Interleaving for TDD |
5.1.0 |
5.2.0 |
|
19/09/02 |
RAN_17 |
RP-020585 |
091 |
1 |
HS-SCCH corrections for TDD |
5.1.0 |
5.2.0 |
|
19/09/02 |
RAN_17 |
RP-020585 |
089 |
1 |
Clarification of TFRI bits for 3.84Mcps HSDPA TDD |
5.1.0 |
5.2.0 |
|
15/10/02 |
– |
– |
– |
– |
Moving of misplaced sections 4.6.1.5 and 4.6.1.6 |
5.2.0 |
5.2.1 |
|
22/12/02 |
RAN_18 |
RP-020843 |
100 |
– |
Corrections to TFCI encoding of very short TFCI lengths |
5.2.1 |
5.3.0 |
|
22/12/02 |
RAN_18 |
RP-020843 |
102 |
– |
Corrections to TFCI encoding of very short TFCI lengths |
5.2.1 |
5.3.0 |
|
22/12/02 |
RAN_18 |
RP-020849 |
103 |
– |
Correction of editorial Error |
5.2.1 |
5.3.0 |
|
22/12/02 |
RAN_18 |
RP-020849 |
104 |
– |
Miscellaneous Minor HSDPA Corrections |
5.2.1 |
5.3.0 |
|
22/12/02 |
RAN_18 |
RP-020852 |
107 |
– |
Editorial modification to the section numberings |
5.2.1 |
5.3.0 |
|
25/03/03 |
RAN_19 |
RP-030139 |
108 |
1 |
HSDPA corrections |
5.3.0 |
5.4.0 |
|
25/03/03 |
RAN_19 |
RP-030139 |
109 |
3 |
Miscellaneous Corrections |
5.3.0 |
5.4.0 |
|
24/06/03 |
RAN_20 |
RP-030276 |
111 |
– |
Corrections to field coding of CQI for HS-SICH (3.84Mcps TDD) |
5.4.0 |
5.5.0 |
|
24/06/03 |
RAN_20 |
RP-030276 |
112 |
– |
Correction to definition of number of bits available to HS-DSCH in one TTI. |
5.4.0 |
5.5.0 |
|
06/01/04 |
RAN_22 |
RP-030646 |
118 |
1 |
Correction of subframe segmentation, physical channel mapping & rate matching for 1.28Mcps TDD |
5.5.0 |
5.6.0 |
|
06/01/04 |
RAN_22 |
RP-030650 |
119 |
– |
Clarification of the CRC attachment procedure for HS-SCCH (TDD) |
5.5.0 |
5.6.0 |
|
06/01/04 |
RAN_22 |
RP-030660 |
120 |
HARQ process identifier mapping |
5.5.0 |
5.6.0 |
|
|
06/01/04 |
RAN_22 |
RP-030712 |
121 |
Alignment of "Soft channel bits" terminology with 25.306 |
5.5.0 |
5.6.0 |
|
|
13/01/04 |
RAN_22 |
– |
– |
– |
Created for M.1457 update |
5.6.0 |
6.0.0 |
|
07/09/04 |
RAN_25 |
RP-040315 |
124 |
1 |
Correction of symbol Xi defined in sub-frame segmentation step |
6.0.0 |
6.1.0 |
|
13/12/04 |
RAN_26 |
RP-040451 |
125 |
– |
Introduction of MICH |
6.1.0 |
6.2.0 |
|
20/03/06 |
RAN_31 |
RP-060078 |
0126 |
– |
Introduction of the Physical Layer Common Control Channel (PLCCH) |
6.2.0 |
7.0.0 |
|
20/03/06 |
RAN_31 |
RP-060079 |
0127 |
– |
Introduction of 7.68Mcps TDD option |
6.2.0 |
7.0.0 |
|
29/09/06 |
RAN_33 |
RP-060492 |
0129 |
– |
Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD |
7.0.0 |
7.1.0 |
|
29/09/06 |
RAN_33 |
RP-060491 |
0130 |
– |
Correction to coding of PLCCH for 1.28Mcps TDD |
7.0.0 |
7.1.0 |
|
13/03/07 |
RAN_35 |
RP-070118 |
0131 |
2 |
Introduction of E-DCH for 1.28Mcps TDD |
7.1.0 |
7.2.0 |
|
30/05/07 |
RAN_36 |
RP-070385 |
0132 |
1 |
Support for MBSFN operation |
7.2.0 |
7.3.0 |
|
30/05/07 |
RAN_36 |
RP-070383 |
0133 |
1 |
Modification on HARQ process ID signalling for 1.28Mcps TDD |
7.2.0 |
7.3.0 |
|
30/05/07 |
RAN_36 |
RP-070385 |
0135 |
– |
Support for 1.28Mcps TDD MBSFN operation |
7.2.0 |
7.3.0 |
|
11/09/07 |
RAN_37 |
RP-070650 |
0136 |
– |
Introduction of multi-frequency operation for 1.28Mcps TDD |
7.3.0 |
7.4.0 |
|
11/09/07 |
RAN_37 |
RP-070647 |
0137 |
– |
TFCI mapping for S-CCPCH and 16QAM for 1.28Mcps TDD MBSFN |
7.3.0 |
7.4.0 |
|
11/09/07 |
RAN_37 |
RP-070640 |
0138 |
1 |
Improved E-HICH signature sequence allocation for LCR TDD |
7.3.0 |
7.4.0 |
|
27/11/07 |
RAN_38 |
RP-070943 |
0141 |
1 |
More improvement on dedicated carrier for 1.28Mcps TDD MBMS |
7.4.0 |
7.5.0 |
|
04/03/08 |
RAN_39 |
RP-080140 |
0144 |
1 |
Some corrections for 1.28Mcps TDD EUL |
7.5.0 |
7.6.0 |
|
04/03/08 |
RAN_39 |
RP-080141 |
0145 |
1 |
Clarification on TFCI mapping for 1.28Mcps TDD MBMS |
7.5.0 |
7.6.0 |
|
04/03/08 |
RAN_39 |
– |
– |
– |
Creation of Release 8 further to RAN_39 decision |
7.6.0 |
8.0.0 |
|
28/05/08 |
RAN_40 |
RP-080356 |
0150 |
1 |
Introduction 64QAM for 1.28Mcps TDD HSDPA |
8.0.0 |
8.1.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
151 |
1 |
Clarification on E-HICH coding for 1.28Mcps TDD |
8.1.0 |
8.2.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
153 |
1 |
Clarification of E-UCCH Number indicator on E-AGCH for 1.28Mcps TDD |
8.1.0 |
8.2.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
154 |
– |
Clarification of TRRI on E-AGCH for 1.28Mcps TDD EUL |
8.1.0 |
8.2.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
155 |
– |
Correction of E-HICH coding for 1.28 Mcps TDD EUL |
8.1.0 |
8.2.0 |
|
03/12/08 |
RAN_42 |
RP-080976 |
159 |
– |
Clarification of E-DCH RV index selection for 1.28Mcps TDD |
8.2.0 |
8.30 |
|
03/12/08 |
RAN_42 |
RP-080980 |
161 |
1 |
Correction of description about 64QAM for LCR TDD |
8.2.0 |
8.30 |
|
03/12/08 |
RAN_42 |
RP-080987 |
162 |
– |
Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD |
8.2.0 |
8.30 |
|
03/12/08 |
RAN_42 |
RP-081118 |
163 |
1 |
Support for 3.84 Mcps MBSFN IMB operation |
8.2.0 |
8.30 |
|
03/03/09 |
RAN_43 |
RP-090230 |
165 |
– |
Correction of the absolute grant (power) value mapping for 1.28Mcps TDD EUL |
8.3.0 |
8.4.0 |
|
03/03/09 |
RAN_43 |
RP-090240 |
166 |
1 |
Introducing of CPC for 1.28Mcps TDD |
8.3.0 |
8.4.0 |
|
03/03/09 |
RAN_43 |
RP-090241 |
167 |
1 |
Introducing of MIMO for 1.28Mcps TDD |
8.3.0 |
8.4.0 |
|
03/03/09 |
RAN_43 |
RP-090239 |
168 |
– |
Corrections to 25.222 for 3.84Mcps MBSFN IMB |
8.3.0 |
8.4.0 |
|
03/03/09 |
RAN_43 |
RP-090239 |
169 |
– |
TFCI for Secondary CCPCH frame type 2 with 16QAM |
8.3.0 |
8.4.0 |
|
03/03/09 |
RAN_43 |
RP-090231 |
173 |
– |
Editorial correction for 1.28Mcps TDD |
8.3.0 |
8.4.0 |
|
26/05/09 |
RAN_44 |
RP-090533 |
174 |
– |
Modification of CCS information mapping tables for LCR TDD |
8.4.0 |
8.5.0 |
|
26/05/09 |
RAN_44 |
RP-090526 |
175 |
1 |
Corrections to the coding of E-RUCCH for 1.28 Mcps TDD |
8.4.0 |
8.5.0 |
|
26/05/09 |
RAN_44 |
RP-090530 |
177 |
– |
Clarification of HS-DSCH coding for MIMO dual stream transmission for 1.28Mcps TDD |
8.4.0 |
8.5.0 |
|
15/09/09 |
RAN_45 |
RP-090893 |
178 |
2 |
Correction to the channel mapping and rate matching for HS-DSCH in CPC for 1.28Mcs TDD |
8.5.0 |
8.6.0 |
|
15/09/09 |
RAN_45 |
RP-090893 |
180 |
– |
Modification of HS-SCCH types for CPC in 1.28Mcps TDD |
8.5.0 |
8.6.0 |
|
15/09/09 |
RAN_45 |
RP-090893 |
182 |
1 |
Correction to Xptr field definition for LCR TDD |
8.5.0 |
8.6.0 |
|
15/09/09 |
RAN_45 |
RP-090893 |
183 |
1 |
Correction to HS-SCCH Type 2 definition for LCR TDD |
8.5.0 |
8.6.0 |
|
15/09/09 |
RAN_45 |
RP-090893 |
184 |
– |
Clarification of HS-SCCH Order types against HS-SCCH types |
8.5.0 |
8.6.0 |
|
01/12/09 |
RAN_46 |
RP-091166 |
185 |
1 |
Correction to the Resource repetition period of SPS operation for 1.28Mcps TDD |
8.6.0 |
8.7.0 |
|
01/12/09 |
RAN_46 |
RP-091176 |
192 |
1 |
Modification to HS-SCCH for TS0 for 1.28Mcps TDD |
8.7.0 |
9.0.0 |
|
16/03/10 |
RAN_47 |
RP-100202 |
195 |
– |
Correction to the resource repetition period index for 1.28Mcps TDD |
9.0.0 |
9.1.0 |
|
16/03/10 |
RAN_47 |
RP-100202 |
201 |
– |
Corrections to the Physical channel mapping for HS-DSCH for 1.28Mcps TDD |
9.0.0 |
9.1.0 |
|
01/06/10 |
RAN_48 |
RP-100585 |
205 |
– |
Corrections to the Physical channel mapping of 64QAM for HS-DSCH for 1.28Mcps TDD |
9.1.0 |
9.2.0 |
|
07/12/10 |
RAN_50 |
RP-101319 |
208 |
– |
Introduction of MU-MIMO for 1.28Mcps TDD |
9.2.0 |
10.0.0 |
|
15/03/11 |
RAN_51 |
RP-110253 |
209 |
1 |
Correction to TS 25.222 for MC HSUPA for 1.28Mcps TDD |
10.0.0 |
10.1.0 |
|
05/12/11 |
RAN_54 |
RP-111665 |
211 |
1 |
Physical channel mapping for HS-DSCH for secondary carrier TS0 for LCR TDD |
10.1.0 |
10.2.0 |
|
2012-09 |
SP_57 |
– |
– |
– |
Update to Rel-11 version (MCC) |
10.2.0 |
11.0.0 |
|
2013-12 |
RP_62 |
RP-131895 |
213 |
1 |
Introduction of HSPA signalling enhancements for more efficient resource usage for LCR TDD |
11.0.0 |
12.0.0 |
|
2015-12 |
SP_70 |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
RP-75 |
– |
– |
– |
– |
Promotion to Release 14 without technical change (MCC) |
14.0.0 |
|
2018-06 |
RP-80 |
– |
– |
– |
– |
Promotion to Release 15 without technical change (MCC) |
15.0.0 |
|
2020-07 |
RP-88e |
– |
– |
– |
– |
Upgrade to Rel-16 version without technical change |
16.0.0 |
|
2022-03 |
RP-95e |
– |
– |
– |
– |
Upgrade to Rel-17 version without technical change |
17.0.0 |