B.2 TxAA weights
25.2243GPPPhysical layer procedures (TDD)TS
In a generic sense, the weight vector to be applied at the transmitter is the w that maximises:
P=wHHHHw (1)
where
H=h1 h2 and w = [ w1, w2 ]T
and where the column vector hi represents the estimated uplink channel impulse response for the i’th transmission antenna, of length equal to the length of the channel impulse response.
Annex C (informative):
Cell search procedure for 3.84Mcps TDD
During the cell search, the UE searches for a cell and determines the downlink scrambling code, basic midamble code and frame synchronisation of that cell. The cell search is typically carried out in three steps:
Step 1: Primary synchronisation code acquisition
During the first step of the cell search procedure, the UE uses the SCH’s primary synchronisation code to find a cell. This is typically done with a single matched filter (or any similar device) matched to the primary synchronisation code which is common to all cells. A cell can be found by detecting peaks in the matched filter output.
Note that for a cell of SCH slot configuration case 1, the SCH can be received periodically every 15 slots. In case of a cell of SCH slot configuration case 2, the following SCH slot can be received at offsets of either 7 or 8 slots from the previous SCH slot.
Step 2: Code group identification and slot synchronisation
During the second step of the cell search procedure, the UE uses the SCH’s secondary synchronisation codes to identify 1 out of 32 code groups for the cell found in the first step. This is typically done by correlating the received signal with the secondary synchronisation codes at the detected peak positions of the first step. The primary synchronisation code provides the phase reference for coherent detection of the secondary synchronisation codes. The code group can then uniquely be identified by detection of the maximum correlation values.
Each code group indicates a different toffset parameter and 4 specific cell parameters. Each of the cell parameters is associated with one particular downlink scrambling code and one particular long and short basic midamble code. When the UE has determined the code group, it can unambiguously derive the slot timing of the found cell from the detected peak position in the first step and the toffset parameter of the found code group in the second step.
Note that the modulation of the secondary synchronisation codes also indicates the position of the SCH slot within a 2 frames period, e.g. a frame with even or odd SFN. Additionally, in the case of SCH slot configuration following case 2, the SCH slot position within one frame, e.g. first or last SCH slot, can be derived from the modulation of the secondary synchronisation codes.
Step 3: Downlink scrambling code, basic midamble code identification and frame synchronisation
During the third and last step of the cell search procedure, the UE determines the exact downlink scrambling code, basic midamble code and frame timing used by the found cell. The long basic midamble code can be identified by correlation over the P-CCPCH (or any other beacon channel) with the 4 possible long basic midamble codes of the code group found in the second step. A P-CCPCH (or any other beacon channel) always uses the midamble m(1) (and in case of SCTD also midamble m(2)) derived from the long basic midamble code and always uses a fixed and pre-assigned channelisation code.
When the long basic midamble code has been identified, downlink scrambling code and cell parameter are also known. The UE can read system and cell specific BCH information and acquire frame synchronisation.
Note that even for an initial cell parameter assignment, a cell cycles through a set composed of 2 different cell parameters according to the SFN of a frame, e.g. the downlink scrambling code and the basic midamble code of a cell alternate for frames with even and odd SFN. Cell parameter cycling leaves the code group of a cell unchanged.
If the UE has received information about which cell parameters or SCH configurations to search for, cell search can be simplified.
Annex CA (informative):
Cell search procedure for 1.28Mcps TDD
During the initial cell search, the UE searches for a cell. It then determines the DwPTS synchronization, scrambling and basic midamble code identification, control multi-frame synchronisation and then reads the contents in BCH. This initial cell search is carried out in 4 steps:
Step 1: Search for DwPTS
During the first step of the initial cell search procedure, the UE uses the SYNC-DL (in DwPTS) to acquire DwPTS synchronization to a cell. This is typically done with one or more matched filters (or any similar device) matched to the received SYNC-DL which is chosen from PN sequences set. A single or more matched filter (or any similar device) is used for this purpose. During this procedure, the UE needs to identify which of the 32 possible SYNC-DL sequences is used.
Step 2: Scrambling and basic midamble code identification
During the second step of the initial cell search procedure, the UE receives the midamble of the P-CCPCH.The P-CCPCH is followed by the DwPTS. In the 1.28 Mcps TDD each DwPTS code corresponds to a group of 4 different basic midamble code. Therefore there are total 128 midamble codes and these codes are not overlapping with each other. Basic midamble code number divided by 4 gives the SYNC-DL code number. Since the SYNC-DL and the group of basic midamble codes of the P-CCPCH are related one by one (i.e, once the SYNC-DL is detected, the 4 midamble codes can be determined), the UE knows which 4 basic midamble codes are used. Then the UE can determine the used basic midamble code using a try and error technique. The same basic midamble code will be used throughout the frame. As each basic midamble code is associated with a scrambling code, the scrambling code is also known by that time. According to the result of the search for the right midamble code, UE may go to next step or go back to step 1.
Step 3: Control multi-frame synchronisation
During the third step of the initial cell search procedure, the UE searches for the MIB( Master Indication Block) of multi-frame of the BCH in the P-CCPCH indicated by QPSK phase modulation of the DwPTS with respect to the P-CCPCH midamble. The control multi-frame is positioned by a sequence of QPSK symbols modulated on the DwPTS. [n] consecutive DwPTS are sufficient for detecting the current position in the control multi-frame. According to the result of the control multi-frame synchronisation for the right midamble code, UE may go to next step or go back to step 2.
Step 4: Read the BCH
The (complete) broadcast information of the found cell in one or several BCHs is read. According to the result the UE may move back to previous steps or the initial cell search is finished.
For Dedicated Carrier MBSFN
For the MS burst, the preamble codes (see the Table AA.1a in TS25.221) are segmented into even code group and odd code group, PP,even group and PP,odd group (see the clause 8.3Aa in TS25.223). When the preamble of the MS burst is PP,odd, it indicates that the next sub-frame is the beginning of the multi-frame of PCCPCH; otherwise, the preamble of MS burst uses the PP,even (PP,even and PP,odd belong to the same subgroup). The preamble of MT burst is decided by the upper-layer signaling. This initial SFN cell search is carried out in 4 steps:
Step 1: Search for PP,even
During the first step of the initial SFN cell search procedure, the UE uses the PP,even (in MS burst) to acquire synchronization to a SFN cell.
Step 2: Multi-frame synchronization
During the second step of the initial SFN cell search procedure, the UE searches for the PP,odd (in MS burst) to get the beginning position of the multi-frame of PCCPCH. According to the result of multi-frame synchronization, UE may go to next step or go back to step 1.
Step 3: Read the BCCH
The UE reads the MIB (Master Indication Block) of multi-frame P-CCPCHs in the BCH and gets the system information of the found SFN cell. According to the result of reading the BCCH, UE may go to next step or go back to step 2.
Step 4: Read the MCCH
The UE reads the MCCH indicated by the BCCH information. According to the result the UE may move back to previous steps or the initial cell search is finished.
Annex CB (informative):
Examples random access procedure for 1.28Mcps TDD
Table CB.1: One PRACH, TTI=5ms, WT=4, L =1, SF4 PRACH
|
Sub-frame Number |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
|
Users sending on UpPCH |
1 2 |
3 4 |
5 6 |
7 8 |
|||||||
|
Acknowledged user on FPACH |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||||
|
User sending on PRACH 0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
User 8 is not granted because more than 5 sub-frames would have passed since the UpPCH.
Table CB.2: Two PRACHs, TTI=10ms, WT=4, L =2, SF8 PRACH
|
Sub-frame Number |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
|
Users sending on UpPCH |
1 2 |
3 4 |
5 6 |
7 8 |
||||||||
|
Acknowledged user on FPACH |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||||
|
User sending on PRACH 0 |
2 |
2 |
4 |
4 |
6 |
6 |
||||||
|
User sending on PRACH 1 |
1 |
1 |
3 |
3 |
5 |
5 |
7 |
7 |
User 8 is not granted because more than 5 sub-frames would have passed since the UpPCH.
Table CB.3: Four PRACHs, TTI=20ms, WT=4, L =4, SF16 PRACH
|
Sub-frame Number |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
|
Users sending on UpPCH |
1 2 |
3 4 |
5 6 |
7 8 |
||||||||||
|
Acknowledged user on FPACH |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|||||||
|
User sending on PRACH 0 |
4 |
4 |
4 |
4 |
||||||||||
|
User sending on PRACH 1 |
1 |
1 |
1 |
1 |
5 |
5 |
5 |
5 |
||||||
|
User sending on PRACH 2 |
2 |
2 |
2 |
2 |
6 |
6 |
6 |
6 |
||||||
|
User sending on PRACH 3 |
3 |
3 |
3 |
3 |
7 |
7 |
7 |
7 |
User 8 is not granted because more than 5 sub-frames would have passed since the UpPCH.
Table CB.4: Two PRACHs, TTI=20ms, WT=4, L =4, SF16 PRACH
|
Sub-frame Number |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
|
Users sending on UpPCH |
1 2 |
3 4 |
5 6 |
7 8 |
|||||||||
|
Acknowledged user on FPACH |
X |
1 |
2 |
3 |
X |
X |
|||||||
|
User sending on PRACH 0 |
2 |
2 |
2 |
2 |
|||||||||
|
User sending on PRACH 1 |
1 |
1 |
1 |
1 |
3 |
3 |
3 |
3 |
The FPACH is used ONLY in sub-frames 0, 1, 4, 5, 8, 9,… because they correspond to the used RACH resources.
The FPACH in sub-frame 0 is not used because no UpPCH is preceding.
The FPACH in sub-frames 8,9 is not used because no UpPCH is preceding in the last 4 sub-frames.
In contrast to the previous examples users 4,5,6,7 are not granted because they would not lead to a RACH anyway. In this example their grant would come too late.
User 8 is not granted because more than 4 sub-frames would have passed since the UpPCH.
Annex D (informative):
Change history
|
Change history |
|||||||
|---|---|---|---|---|---|---|---|
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
14/01/00 |
RAN_05 |
RP-99594 |
– |
Approved at TSG RAN #5 and placed under Change Control |
– |
3.0.0 |
|
|
14/01/00 |
RAN_06 |
RP-99698 |
001 |
01 |
Primary and Secondary CCPCH in TDD |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99698 |
002 |
– |
Measurement procedure of received reference power for OL-TPC in TDD |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99699 |
004 |
1 |
STTD capability for P-CCPCH, TDD component |
3.0.0 |
3.1.0 |
|
14/01/00 |
RAN_06 |
RP-99697 |
005 |
1 |
Alignment of Terminology Regarding Spreading for TDD Mode |
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-000070 |
003 |
2 |
Cycling of cell parameters |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
007 |
2 |
Clarifications on the UL synchronisation and Timing advance |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
008 |
– |
Modification of SIR threshold on setting TPC |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
009 |
1 |
New section describing the random access procedure |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
011 |
– |
Removal of Synchronisation Case 3 in TDD |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
012 |
1 |
Clarifications on power control procedures |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
013 |
– |
Signal Point Constellation |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
014 |
2 |
Out-of-sync handling for UTRA TDD |
3.1.1 |
3.2.0 |
|
31/03/00 |
RAN_07 |
RP-000070 |
015 |
– |
Removal of ODMA from the TDD specifications |
3.1.1 |
3.2.0 |
|
26/06/00 |
RAN_08 |
RP-000274 |
016 |
– |
Editorial correction for the power control section in 25.224 |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000274 |
017 |
– |
Power control for TDD during DTX |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000274 |
018 |
1 |
Power Control for PDSCH |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000274 |
020 |
1 |
Editorial modification of 25.224 |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000274 |
021 |
– |
Clarifications on TxDiversity for UTRA TDD |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000274 |
022 |
1 |
Introduction of the TDD DSCH detection procedure in TS 25.224 |
3.2.0 |
3.3.0 |
|
26/06/00 |
RAN_08 |
RP-000274 |
023 |
– |
Downlink power control on timeslot basis |
3.2.0 |
3.3.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
019 |
1 |
Gain Factors for TDD Mode |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
025 |
– |
Terminology regarding the beacon function |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
026 |
1 |
Synchronisation of timing advance adjustment and timing deviation measurement |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
027 |
1 |
CCTrCH UL/DL pairing for DL inner loop power control |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
028 |
1 |
RACH timing in TDD mode |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
030 |
1 |
TDD Access Bursts for HOV |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
032 |
– |
Removal of ODMA related abbreviations and correction of references |
3.3.0 |
3.4.0 |
|
23/09/00 |
RAN_09 |
RP-000347 |
033 |
– |
Clarifications on the Out-of-sync handling for UTRA TDD |
3.3.0 |
3.4.0 |
|
15/12/00 |
RAN_10 |
RP-000544 |
035 |
1 |
Radio Link establishment and sync status reporting |
3.4.0 |
3.5.0 |
|
15/12/00 |
RAN_10 |
RP-000544 |
040 |
– |
Clarification on PICH power setting |
3.4.0 |
3.5.0 |
|
15/12/00 |
RAN_10 |
RP-000544 |
042 |
– |
Correction to TDD timing advance description |
3.4.0 |
3.5.0 |
|
15/12/00 |
RAN_10 |
RP-000544 |
043 |
– |
Limit on maximum value of alpha used for open loop power control |
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-010065 |
036 |
– |
DTX and Special Burst Scheduling |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010065 |
037 |
1 |
RACH random access procedure |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010065 |
045 |
– |
Introduction of closed-loop Tx diversity for the PDSCH and DTX for the PUSCH/PDSCH |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010065 |
046 |
2 |
Corrections of TDD power control sections |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010065 |
050 |
– |
Use of a special burst in reconfiguration |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010065 |
053 |
– |
Known TFCI for the TDD special burst |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010073 |
044 |
2 |
Layer 1 procedure for Node B synchronisation |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010071 |
047 |
1 |
Inclusion of 1,28 Mcps TDD in TS 25.224 |
3.5.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010072 |
048 |
1 |
Idle periods for IPDL location method |
3.5.0 |
4.0.0 |
|
15/06/01 |
RAN_12 |
RP-010338 |
057 |
– |
Correction of Timing Advance section for 3.84 Mcps TDD |
4.0.0 |
4.1.0 |
|
15/06/01 |
RAN_12 |
RP-010338 |
059 |
– |
Addition to the abbreviation list |
4.0.0 |
4.1.0 |
|
15/06/01 |
RAN_12 |
RP-010343 |
049 |
– |
Clarification of IP_Frame(x) definition |
4.0.0 |
4.1.0 |
|
15/06/01 |
RAN_12 |
RP-010343 |
055 |
1 |
Correction of IPDL burst parameters |
4.0.0 |
4.1.0 |
|
21/09/01 |
RAN_13 |
RP-010525 |
064 |
1 |
Correction of criteria for OOS indication |
4.1.0 |
4.2.0 |
|
21/09/01 |
RAN_13 |
RP-010531 |
060 |
– |
Corrections for TS 25.224 |
4.1.0 |
4.2.0 |
|
21/09/01 |
RAN_13 |
RP-010531 |
062 |
1 |
Corrections of Annex E in 25.224 |
4.1.0 |
4.2.0 |
|
21/09/01 |
RAN_13 |
RP-010531 |
061 |
– |
Corrections and Clarifications for calculation of idle period position in subclause 4.10.3 in 25.224 |
4.1.0 |
4.2.0 |
|
14/12/01 |
RAN_14 |
RP-010742 |
066 |
– |
Removal of the remark on power control |
4.2.0 |
4.3.0 |
|
14/12/01 |
RAN_14 |
RP-010742 |
068 |
1 |
Transmit Diversity for P-CCPCH and PICH |
4.2.0 |
4.3.0 |
|
14/12/01 |
RAN_14 |
RP-010742 |
070 |
1 |
Correction to random access procedure (Primitive from MAC) |
4.2.0 |
4.3.0 |
|
14/12/01 |
RAN_14 |
RP-010749 |
073 |
1 |
Random access procedure for 1.28Mcps TDD |
4.2.0 |
4.3.0 |
|
14/12/01 |
RAN_14 |
RP-010749 |
074 |
– |
Transmit diversity for P-CCPCH and PICH |
4.2.0 |
4.3.0 |
|
14/12/01 |
RAN_14 |
RP-010749 |
075 |
– |
Correction of Annex A.3 in 25.224 |
4.2.0 |
4.3.0 |
|
14/12/01 |
RAN_14 |
RP-010749 |
076 |
– |
Removal of the remark on power control |
4.2.0 |
4.3.0 |
|
14/12/01 |
RAN_14 |
RP-010749 |
077 |
– |
Corrections to DL-PC sections for 1.28 Mcps TDD |
4.2.0 |
4.3.0 |
|
08/03/02 |
RAN_15 |
RP-020052 |
079 |
1 |
Removal of quantisation of bj gain factor when calculated from a reference TFC |
4.3.0 |
4.4.0 |
|
08/03/02 |
RAN_15 |
RP-020052 |
084 |
1 |
TDD MAC layer subchannel assignment |
4.3.0 |
4.4.0 |
|
08/03/02 |
RAN_15 |
RP-020052 |
086 |
– |
Transmit diversity on PICH |
4.3.0 |
4.4.0 |
|
08/03/02 |
RAN_15 |
RP-020057 |
080 |
– |
Introduction of "UE Positioning Enhancements for 1.28 Mcps TDD" |
4.3.0 |
5.0.0 |
|
08/03/02 |
RAN_15 |
RP-020055 |
082 |
1 |
Introduction of "Node B synchronization for 1.28 Mcps TDD" |
4.3.0 |
5.0.0 |
|
08/03/02 |
RAN_15 |
RP-020058 |
081 |
1 |
Power Control and Procedures for HSDPA |
4.3.0 |
5.0.0 |
|
07/06/02 |
RAN_16 |
RP-020315 |
088 |
– |
Clarification on power control and TxDiversity procedure for 1.28 Mcps TDD |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020317 |
089 |
– |
TxDiversity for HSDPA in TDD |
5.0.0 |
5.1.0 |
|
07/06/02 |
RAN_16 |
RP-020317 |
090 |
– |
Correction to HS-SCCH Power Control (TDD) |
5.0.0 |
5.1.0 |
|
20/09/02 |
RAN_17 |
RP-020586 |
091 |
1 |
Corrections to 25.224 for HSDPA |
5.1.0 |
5.2.0 |
|
20/09/02 |
RAN_17 |
RP-020572 |
094 |
2 |
Corrections to transmit diversity mode for TDD beacon-function physical channels |
5.1.0 |
5.2.0 |
|
20/09/02 |
RAN_17 |
RP-020577 |
097 |
1 |
Corrections to uplink synchronisation procedure |
5.1.0 |
5.2.0 |
|
20/09/02 |
RAN_17 |
RP-020577 |
099 |
– |
Correction to the PRACH open loop power control procedure for 1.28 Mcps TDD |
5.1.0 |
5.2.0 |
|
20/09/02 |
RAN_17 |
RP-020579 |
101 |
1 |
Corrections to transmit diversity mode for TDD beacon-function physical channels |
5.1.0 |
5.2.0 |
|
15/10/02 |
– |
– |
– |
– |
Separate subclause 5.1.1.3, which was by accident merged into the header of subclause 5.1.1.4 |
5.2.0 |
5.2.1 |
|
22/12/02 |
RAN_18 |
RP-020854 |
102 |
1 |
Corrections and clarifications to TDD CQI description |
5.2.1 |
5.3.0 |
|
22/12/02 |
RAN_18 |
RP-020852 |
105 |
– |
Editorial modification to the section numberings |
5.2.1 |
5.3.0 |
|
24/03/03 |
RAN_19 |
RP-030141 |
109 |
1 |
Corrections to TPC Procedures During a DL Transmission Pause |
5.3.0 |
5.4.0 |
|
24/03/03 |
RAN_19 |
RP-030141 |
114 |
1 |
Corrections to link adaptation procedure for UTRA TDD (3.84 Mcps Option) |
5.3.0 |
5.4.0 |
|
24/03/03 |
RAN_19 |
RP-030141 |
115 |
2 |
Minimum timing requirement for CQI transmission on HS-SICH in UTRA TDD |
5.3.0 |
5.4.0 |
|
24/03/03 |
RAN_19 |
RP-030141 |
117 |
2 |
Clarification of downlink closed loop power control procedures for 3.84 Mcps TDD |
5.3.0 |
5.4.0 |
|
24/03/03 |
RAN_19 |
RP-030133 |
119 |
2 |
Corrections to the LCR power control procedure |
5.3.0 |
5.4.0 |
|
24/06/03 |
RAN_20 |
RP-030277 |
120 |
– |
Clarifications for the 1.28Mcps TDD power control procedure |
5.4.0 |
5.5.0 |
|
22/09/03 |
RAN_21 |
RP-030460 |
121 |
3 |
Clarification on PDSCH Downlink Power Control Procedures |
5.5.0 |
5.6.0 |
|
22/09/03 |
RAN_21 |
RP-030476 |
125 |
1 |
DTX and Special Bursts in case of no data on S-CCPCH and Beacon Channels |
5.5.0 |
5.6.0 |
|
06/01/04 |
RAN_22 |
RP-030698 |
128 |
1 |
Correction to computed gain factors with signalled reference gain factor values |
5.6.0 |
5.7.0 |
|
13/01/04 |
RAN_22 |
– |
– |
– |
Created for M.1457 update |
5.7.0 |
6.0.0 |
|
09/06/04 |
RAN_24 |
RP-040235 |
131 |
2 |
Addition of TSTD for S-CCPCH in 3.84Mcps TDD |
6.0.0 |
6.1.0 |
|
07/09/04 |
RAN_25 |
RP-040316 |
134 |
– |
Transmit diversity usage for beacon channels in LCR TDD |
6.1.0 |
6.2.0 |
|
07/09/04 |
RAN_25 |
RP-040319 |
137 |
1 |
Corrections of radio access procedure for 1.28Mcps TDD |
6.1.0 |
6.2.0 |
|
13/12/04 |
RAN_26 |
RP-040451 |
138 |
– |
Introduction of MICH |
6.2.0 |
6.3.0 |
|
13/12/04 |
RAN_26 |
RP-040452 |
139 |
– |
Introduction of MBMS soft combining for TDD |
6.2.0 |
6.3.0 |
|
14/03/05 |
RAN_27 |
RP-050097 |
140 |
2 |
Improvements to uplink closed-loop power control for 1.28Mcps TDD |
6.3.0 |
6.4.0 |
|
14/03/05 |
RAN_27 |
RP-050089 |
141 |
– |
Release 6 HS-DSCH operation without a DL DPCH for 3.84Mcps TDD |
6.3.0 |
6.4.0 |
|
16/06/05 |
RAN_28 |
RP-050255 |
144 |
2 |
Clarification of UpPCH Sub-channel for 1.28 Mcps TDD |
6.4.0 |
6.5.0 |
|
12/12/05 |
RAN_30 |
RP-050724 |
0146 |
1 |
Clarify the power control procedure of HS-SCCH for TDD |
6.5.0 |
6.6.0 |
|
20/03/06 |
RAN_31 |
RP-060078 |
0149 |
– |
Introduction of the Physical Layer Common Control Channel (PLCCH) |
6.6.0 |
7.0.0 |
|
20/03/06 |
RAN_31 |
RP-060079 |
0150 |
– |
Introduction of 7.68Mcps TDD option |
6.6.0 |
7.0.0 |
|
29/09/06 |
RAN_33 |
RP-060497 |
0152 |
– |
Release 7 Timing Advance (3.84 Mpcs and 7.68 Mcps TDD) |
7.0.0 |
7.1.0 |
|
29/09/06 |
RAN_33 |
RP-060492 |
0153 |
– |
Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD |
7.0.0 |
7.1.0 |
|
29/09/06 |
RAN_33 |
– |
– |
– |
Editorial correction for Tdoc number of CR0140R2 from RP-050096 to RP-050097 on table of history change |
7.0.0 |
7.1.0 |
|
13/03/07 |
RAN_35 |
RP-070118 |
0159 |
2 |
Introduction of E-DCH for 1.28Mcps TDD |
7.1.0 |
7.2.0 |
|
13/03/07 |
RAN_35 |
RP-070113 |
0155 |
1 |
Modification on the power control function of HS-SICH for LCR TDD |
7.1.0 |
7.2.0 |
|
13/03/07 |
RAN_35 |
RP-070113 |
0158 |
2 |
Clarification of closed Loop Uplink HS-SICH Power Control for 1.28Mcps TDD |
7.1.0 |
7.2.0 |
|
30/05/07 |
RAN_36 |
RP-070385 |
0160 |
1 |
Support for MBSFN operation |
7.2.0 |
7.3.0 |
|
30/05/07 |
RAN_36 |
RP-070386 |
0162 |
1 |
Support for 1.28Mcps TDD MBSFN operation |
7.2.0 |
7.3.0 |
|
11/09/07 |
RAN_37 |
RP-070640 |
0164 |
1 |
Improvement on the power control of E-PUCH in 1.28Mcps TDD |
7.3.0 |
7.4.0 |
|
11/09/07 |
RAN_37 |
RP-070650 |
0163 |
1 |
Introduction of multi-frequency operation for 1.28Mcps TDD |
7.3.0 |
7.4.0 |
|
14/09/07 |
RAN_37 |
RP-070726 |
0166 |
1 |
Correction to the calculating formula of SIR |
7.3.0 |
7.4.0 |
|
27/11/07 |
RAN_38 |
RP-070942 |
0172 |
– |
Clarification of gain factor |
7.4.0 |
7.5.0 |
|
27/11/07 |
RAN_38 |
RP-070943 |
0171 |
1 |
More improvement on dedicated carrier for 1.28Mcps TDD MBMS |
7.4.0 |
7.5.0 |
|
04/03/08 |
RAN_39 |
RP-080140 |
0170 |
2 |
EUL power control improvements for 1.28Mcps TDD |
7.5.0 |
7.6.0 |
|
04/03/08 |
RAN_39 |
RP-080140 |
0176 |
– |
Improvement of the UL synchronisation of E-PUCH for 1.28Mcps TDD EUL |
7.5.0 |
7.6.0 |
|
04/03/08 |
RAN_39 |
RP-080140 |
0177 |
1 |
Clarification and Correction of E-PUCH power control for LCR TDD |
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 |
|
09/09/08 |
RAN_41 |
RP-080661 |
186 |
4 |
HS-SCCH and HS-SICH power control clarification for 1.28Mcps TDD |
8.0.0 |
8.1.0 |
|
09/09/08 |
RAN_41 |
RP-080664 |
187 |
– |
Use of Special Bursts for DTX on MBSFN FACH in 1.28 Mcps TDD |
8.0.0 |
8.1.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
188 |
– |
Correction of E-PUCH power control for 1.28 Mcps TDD EUL |
8.0.0 |
8.1.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
190 |
1 |
Clarification of the E-AGCH monitoring for 1.28Mcps TDD EUL |
8.0.0 |
8.1.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
192 |
– |
Correction of UpPCHPOS bit number in subclause 5.2.7 |
8.0.0 |
8.1.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
193 |
– |
EUL power control clarification for 1.28Mcps TDD |
8.0.0 |
8.1.0 |
|
09/09/08 |
RAN_41 |
RP-080661 |
194 |
1 |
EUL power control improvement for 1.28Mcps TDD |
8.0.0 |
8.1.0 |
|
03/12/08 |
RAN_42 |
RP-080976 |
199 |
1 |
Modification of HS-SICH sync description for 1.28Mcps TDD |
8.1.0 |
8.2.0 |
|
03/12/08 |
RAN_42 |
RP-080976 |
201 |
1 |
Clarification of precision and quantization mode for coderate and beta of E-PUCH for 1.28Mcps TDD EUL |
8.1.0 |
8.2.0 |
|
03/12/08 |
RAN_42 |
RP-080987 |
202 |
1 |
Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD |
8.1.0 |
8.2.0 |
|
03/12/08 |
RAN_42 |
RP-081118 |
203 |
1 |
Support for 3.84 Mcps MBSFN IMB operation |
8.1.0 |
8.2.0 |
|
03/03/09 |
RAN_43 |
RP-090230 |
205 |
– |
Clarification of the beta value for smallest E-TFC of E-PUCH for 1.28Mcps TDD EUL |
8.2.0 |
8.3.0 |
|
03/03/09 |
RAN_43 |
RP-090240 |
206 |
1 |
Introducing of CPC for 1.28Mcps TDD |
8.2.0 |
8.3.0 |
|
03/03/09 |
RAN_43 |
RP-090241 |
207 |
1 |
Introducing of MIMO for 1.28Mcps TDD |
8.2.0 |
8.3.0 |
|
03/03/09 |
RAN_43 |
RP-090230 |
209 |
2 |
E-DCH power control clarification for 1.28Mcps TDD |
8.2.0 |
8.3.0 |
|
26/05/09 |
RAN_44 |
RP-090533 |
210 |
1 |
Clarification of HS-SICH and E-PUCH power control in semi-persistent transmission for LCR TDD |
8.3.0 |
8.4.0 |
|
26/05/09 |
RAN_44 |
RP-090533 |
211 |
1 |
Clarification of E-PUCH synchronization in semi-persistent transmission for LCR TDD |
8.3.0 |
8.4.0 |
|
26/05/09 |
RAN_44 |
RP-090533 |
212 |
2 |
Clarification of DRX operation in CPC for LCR TDD |
8.3.0 |
8.4.0 |
|
26/05/09 |
RAN_44 |
RP-090526 |
216 |
– |
Clarification of the transmit power for E-RUCCH for 1.28Mcps TDD |
8.3.0 |
8.4.0 |
|
26/05/09 |
RAN_44 |
RP-090531 |
218 |
2 |
Pilot power behaviour for MBSFN IMB |
8.3.0 |
8.4.0 |
|
15/09/09 |
RAN_45 |
RP-090892 |
219 |
4 |
Clarification on HS-DSCH procedure when using BCCH specific H-RNTI in CELL_PCH or URA_PCH state for 1.28Mcps TDD |
8.4.0 |
8.5.0 |
|
15/09/09 |
RAN_45 |
RP-090892 |
224 |
1 |
Change the timing definition in CELL-PCH for 1.28Mcps TDD |
8.4.0 |
8.5.0 |
|
15/09/09 |
RAN_45 |
RP-090887 |
226 |
2 |
Clarification of SNPL calculation and reporting for 1.28 Mcps TDD |
8.4.0 |
8.5.0 |
|
01/12/09 |
RAN_46 |
RP-091258 |
217 |
5 |
Correction of Out of synchronisation handling for 1.28Mcps TDD CPC usage |
8.5.0 |
8.6.0 |
|
01/12/09 |
RAN_46 |
RP-091166 |
230 |
3 |
Correction on Control Channel DRX description for 1.28Mcps TDD |
8.5.0 |
8.6.0 |
|
01/12/09 |
RAN_46 |
RP-091166 |
232 |
1 |
Clarification of the Control Channel DRX operation for 1.28Mcps TDD |
8.5.0 |
8.6.0 |
|
01/12/09 |
RAN_46 |
RP-091167 |
234 |
1 |
Terminology correction for 1.28Mcps TDD standalone midamble channel |
8.5.0 |
8.6.0 |
|
01/12/09 |
RAN_46 |
RP-091169 |
236 |
– |
Clarification of HS-DSCH channel quality indication procedure in CELL_FACH state for 1.28Mcps TDD |
8.5.0 |
8.6.0 |
|
01/12/09 |
RAN_46 |
– |
– |
– |
Creation of Release 9 (v9.0.0) at RAN#46 |
8.6.0 |
9.0.0 |
|
16/03/10 |
RAN_47 |
RP-100201 |
244 |
– |
Clarification of the TPC and SS on HS-SCCH uplink synchronization establishement command for 1.28Mcps TDD |
9.0.0 |
9.1.0 |
|
16/03/10 |
RAN_47 |
RP-100202 |
246 |
1 |
Clarification of HS-DSCH Channel Quality Indication Procedure for 1.28Mcps TDD |
9.0.0 |
9.1.0 |
|
16/03/10 |
RAN_47 |
RP-100201 |
248 |
– |
Clarification of ePCH modulation scheme |
9.0.0 |
9.1.0 |
|
14/09/10 |
RAN_49 |
RP-100896 |
254 |
2 |
Clarification on HS-DSCH transmission in CELL_PCH or URA_PCH state for 1.28Mcps TDD |
9.1.0 |
9.2.0 |
|
07/12/10 |
RAN_50 |
RP-101314 |
261 |
– |
Correction of MC-HSDPA DRX for 1.28Mcps TDD |
9.2.0 |
9.3.0 |
|
07/12/10 |
RAN_50 |
RP-101316 |
263 |
2 |
Clarification for special burst power calculation for 1.28Mcps TDD |
9.2.0 |
9.3.0 |
|
07/12/10 |
RAN_50 |
RP-101317 |
257 |
3 |
Introduction of MC-HSUPA for LCR TDD |
9.3.0 |
10.0.0 |
|
07/12/10 |
RAN_50 |
RP-101319 |
259 |
1 |
Introduction of MU-MIMO for LCR TDD |
9.3.0 |
10.0.0 |
|
15/03/11 |
RAN_51 |
RP-110252 |
265 |
1 |
Correction of the special burst transmission power calculation for 1.28Mcps TDD |
10.0.0 |
10.1.0 |
|
01/06/11 |
RAN_52 |
RP-110817 |
266 |
– |
Clarification on SCCPCH selection for LCR TDD |
10.1.0 |
10.2.0 |
|
15/09/11 |
RAN_53 |
RP-111227 |
270 |
2 |
Clarifications on SYNC-UL signatures for E-RUCCH procedure for LCR TDD |
10.2.0 |
10.3.0 |
|
2012-09 |
SP_57 |
– |
– |
– |
Update to Rel-11 version (MCC) |
10.3.0 |
11.0.0 |
|
04/12/12 |
RAN_58 |
RP-121847 |
272 |
2 |
Clarification about the frequency on which UE initiates uplink synchronization in enhanced CELL_PCH state for 1.28Mcps TDD |
11.0.0 |
11.1.0 |
|
04/12/13 |
RAN_62 |
RP-131895 |
273 |
1 |
Introduction of HSPA signalling enhancements for more efficient resource usage for LCR TDD |
11.1.0 |
12.0.0 |
|
07/12/15 |
SP_70 |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
and Pe-base in LCR TDD EUL|
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 |