DraftCRonLTETDDPRACHtime-frequencymapping.doc

1、Comment H1: Page: 1Document numbers are allocated by the Working Group Secretary. Use the format of document number specified by the 3GPP Working Procedures.Comment H2: Page: 1Enter the specification number in this box. For example, 04.08 or 31.102. Do not prefix the number with anything . i.e. do n

2、ot use “TS“, “GSM“ or “3GPP“ etc.Comment H3: Page: 1Enter the CR number here. This number is allocated by the 3GPP support team. It consists of at least four digits, padded with leading zeros if necessary.Comment H4: Page: 1Enter the revision number of the CR here. If it is the first version, use a

3、“-“.Comment H5: Page: 1Enter the version of the specification here. This number is the version of the specification to which the CR was written and (normally) to which it will be applied if it is approved. Make sure that the latest version of the specification (of the relevant release) is used when

4、creating the CR. If unsure what the latest version is, go to http:/www.3gpp.org/specs/specs.htm.Comment H6: Page: 1For help on how to fill out a field, place the mouse pointer over the special symbol closest to the field in question.Comment H7: Page: 1Mark one or more of the boxes with an X.Comment

5、H8: Page: 1SIM / USIM / ISIM applications.Comment H9: Page: 1Enter a concise description of the subject matter of the CR. It should be no longer than one line, but if this is not possible, do not enter hard new-line characters. Do not use redundant information such as “Change Request number xxx to 3

6、GPP TS xx.xxx“.Comment H10: One or more organizations (3GPP Individual Members) which drafted the CR and are presenting it to the Working Group.Comment H11: For CRs agreed at Working Group level, the identity of the WG. Use the format “xn“ where x = “C“ for TSG CT, “R“ for TSG RAN, “S“ for TSG SA, “

7、G“ for TSG GERAN; Page: 1n = digit identifying the Working Group; for CRs drafted during the TSG meeting itself, use “P“. Examples: “C4“, “R5“, “G3new“, “SP“.Comment H12: Page: 1Enter the acronym for the work item which is applicable to the change. This field is mandatory for category F, A, B & C CR

8、sfor Release 4 and later. A list of work item acronyms can be foundin the 3GPP work plan. See http:/www.3gpp.org/ftp/Specs/html-info/WI-List.htm .Comment H13: Page: 1Enter the date on which the CR was last revised. Format to be interpretable by English version of MS Windows applications, e.g. 19/02/

9、2006.Comment H14: Page: 1Enter a single letter corresponding to the most appropriate category listed. For more detailed help on interpreting these categories, see Technical Report 21.900 “TSG working methods“.Comment H15: Page: 1Enter a single release code from the list below.Comment H16: Page: 1Ent

10、er text which explains why the change is necessary.Comment H17: Page: 1Enter text which describes the most important components of the change. i.e. How the change is made.Comment H18: Page: 1Enter here the consequences if this CR were to be rejected. It is mandatory to complete this section only if

11、the CR is of category “F“ (i.e. correction), though it may well be useful for other categories.Comment H19: Page: 1Enter the number of each clause which contains changes. Be as specific as possible (ie list each subclause, not just the umbrella clause).Comment H20: Page: 1Tick “yes“ box if any other

12、 specifications are affected by this change. Else tick “no“. You MUST fill in one or the other.Comment H21: Page: 1List here the specifications which are affected or the CRs which are linked.Comment H22: Page: 1Enter any other information which may be needed by the group being requested to approve t

13、he CR. This could include special conditions for its approval which are not listed anywhere else above.3GPP TSG-RAN1 Meeting #53 R1-08xxxxKansas City, USA, 5-9 May 2008CR-Form-v9.4DRAFT CHANGE REQUEST 36.211CRCRNumrev - Current version:8.2.0For HELP on using this form look at the pop-up text over th

14、e symbols. Comprehensive instructions on how to use this form can be found at http:/www.3gpp.org/specs/CR.htm.Proposed change affects:UICC apps ME X Radio Access NetworkX Core NetworkTitle: TDD PRACH time/frequency mappingSource to WG: EricssonSource to TSG:Work item code: LTE-Phys Date: 28/04/2008C

15、ategory: F Release: Rel-8Use one of the following categories:F (correction)A (corresponds to a correction in an earlier release)B (addition of feature), C (functional modification of feature)D (editorial modification)Detailed explanations of the above categories canbe found in 3GPP TR 21.900.Use one

16、 of the following releases:R99 (Release 1999)Rel-4 (Release 4)Rel-5 (Release 5)Rel-6 (Release 6)Rel-7 (Release 7)Rel-8 (Release 8)Rel-9 (Release 9)Reason for change: PRACH time/frequency resource mapping has not been specified for TDDSummary of change: Added the TDD PRACH configuration table (Table

17、5.7.1-3) and corresponding text in accordance with previously agreed CR0011 (R1-081691) Added TDD PRACH time/frequency resource mapping table (Table 5.7.1-4), and corresponding text explaining the construction of the table. Added new symbols to the Symbols subclauseConsequences if not approved: The

18、PRACH time/frequency resource mapping will not be well defined for TDDClauses affected: 3.1, 5.7.1Y NOther specs X Other core specifications affected: X Test specificationsX O&M SpecificationsOther comments: 3GPPError! No text of specified style in document.2Error! No text of specified style in docu

19、ment.3.1 SymbolsFor the purposes of the present document, the following symbols apply:Resource element with frequency-domain index and time-domain index ),(lk klValue of resource element for antenna port ,pa ),(lkpMatrix for supporting cyclic delay diversityDDensity of random access opportunities pe

20、r frameRACarrier frequency0fPRACH resource frequency indexScheduled bandwidth for uplink transmission, expressed as a number of subcarriers PUSCHscMScheduled bandwidth for uplink transmission, expressed as a number of resource blocksRBNumber of coded bits to transmit on a physical channel for code w

21、ord (q)bit qNumber of modulation symbols to transmit on a physical channel for code word symNumber of modulation symbols to transmit per layer for a physical channellaerNumber of modulation symbols to transmit per antenna port for a physical channelpsybMA constant equal to 2048 for and 4096 for N kH

22、z15f kHz5.7fDownlink cyclic prefix length for OFDM symbol in a slotl,CP lNumber of cyclic shifts used for PUCCH formats 1/1a/1b in a resource block with a mix of (1)csformats 1/1a/1b and 2/2a/2bBandwidth reserved for PUCCH formats 2/2a/2b, expressed in multiples of (2)RB RBscNNumber of resource bloc

23、ks in a slot used for PUCCH transmission (set by higher layers)PUCHNPhysical layer cell identitycelIDMBSFN area identityMSFDownlink bandwidth configuration, expressed in multiples of LRB RBscSmallest downlink bandwidth configuration, expressed in multiples of min, scNLargest downlink bandwidth confi

24、guration, expressed in multiples of DaxNUplink bandwidth configuration, expressed in multiples of ULRB RBscSmallest uplink bandwidth configuration, expressed in multiples of in, scLargest uplink bandwidth configuration, expressed in multiples of maxNumber of OFDM symbols in a downlink slot DLsybNumb

25、er of SC-FDMA symbols in an uplink slot UNResource block size in the frequency domain, expressed as a number of subcarriersRBscNumber of downlink to uplink switch points within the radio frameSPNumber of reference symbols per slot for PUCCHUCHTiming offset between uplink and downlink radio frames at

26、 the UE, expressed in units of TA sTResource index for PUCCH formats 1/1a/1b)1(PnResource index for PUCCH formats 2/2a/2b2UCHNumber of PDCCHs present in a subframeDPhysical resource block numberPRBFirst physical resource block occupied by PRACH resource consideredAnFirst physical resource block avai

27、lable for PRACHofset Virtual resource block numberVRB3GPPError! No text of specified style in document.3Error! No text of specified style in document.Radio network temporary identifierRNTInSystem frame numberfSlot number within a radio framesNumber of cell-specific antenna portsPAntenna port numberp

28、Code word numberqIndex for PRACH versions with common preamble format and PRACH densityRArTime-continuous baseband signal for antenna port and OFDM symbol in a slottspl)( plFrame index of PRACH opportunity0Half frame index of PRACH opportunity1RAtUL subframe number for start of PRACH opportunity2Rad

29、io frame durationfTBasic time unitsSlot durationlotPrecoding matrix for downlink spatial multiplexingWAmplitude scaling for PRACHPRACHAmplitude scaling for PUCCHUAmplitude scaling for PUSCHSAmplitude scaling for sounding reference symbolsSubcarrier spacingfSubcarrier spacing for the random access pr

30、eambleRANumber of transmission layers3GPPError! No text of specified style in document.4Error! No text of specified style in document.5.7.1 Time and frequency structureThe physical layer random access preamble, illustrated in Figure 5.7.1-1, consists of a cyclic prefix of length and a CPTsequence pa

31、rt of length . The parameter values are listed in Table 5.7.1-1 and depend on the frame structure and the SEQTrandom access configuration. Higher layers control the preamble format.S e q u e n c eC PTEQTFigure 5.7.1-1: Random access preamble format.Table 5.7.1-1: Random access preamble parameters.Pr

32、eamble format CPTSEQT0 s3168 s245761 2042 s s3 TT4(frame structure type 2 only) s8 s4096The transmission of a random access preamble, if triggered by the MAC layer, is restricted to certain time and frequency resources. These resources are enumerated in increasing order of the subframe number within

33、 the radio frame and the physical resource blocks in the frequency domain such that index 0 correspond to the lowest numbered physical resource block and subframe within the radio frame. For frame structure type 1 with preamble format 0-3, there is at most one random access resource per subframe for

34、 FDD. Table 5.7.1-2 lists the subframes in which random access preamble transmission is allowed for a given configuration in frame structure type 1. The start of the random access preamble shall be aligned with the start of the corresponding uplink subframe at the UE assuming a timing advance of zer

35、o. For PRACH configuration 0, 1, 2, 15, the UE may for handover purposes assume an absolute value of the relative time difference between radio frame in the icurrent cell and the target cell of less than . s15360T3GPPError! No text of specified style in document.5Error! No text of specified style in

36、 document.Table 5.7.1-2: Frame structure type 1 Random access preamble timing for preamble format 0-3.PRACH configuration System frame number Subframe number0 Even 11 Even 42 Even 73 Any 14 Any 45 Any 76 Any 1, 67 Any 2 ,78 Any 3, 89 Any 1, 4, 710 Any 2, 5, 811 Any 3, 6, 912 Any 0, 2, 4, 6, 813 Any

37、1, 3, 5, 7, 914 Any 0, 1, 2, 3, 4, 5, 6, 7, 8, 915 Even 9For frame structure type 2 with preamble format 0-4, there might be multiple random access resources in an UL subframe (or UpPTS for preamble format 4) depending on the UL/DL configuration see table 4.2-2. Table 5.7.1-3 lists PRACH configurati

38、ons allowed for frame structure type 2 where the configuration index corresponds to a certain combination of preamble format, PRACH density value, , and version index, RAD.RAr3GPPError! No text of specified style in document.6Error! No text of specified style in document.Table 5.7.1-3: Frame structu

39、re type 2 Random access configurations for preamble format 0-4PRACH conf.IndexPreambleFormatDensityPer 10 msRADVersionRArPRACH conf.IndexPreambleFormatDensityPer 10 msRADVersionRAr0 0 0.5 0 32 2 0.5 21 0 0.5 1 33 2 1 02 0 0.5 2 34 2 1 13 0 1 0 35 2 2 04 0 1 1 36 2 3 05 0 1 2 37 2 4 06 0 2 0 38 2 5 0

40、7 0 2 1 39 2 6 08 0 2 2 40 3 0.5 09 0 3 0 41 3 0.5 110 0 3 1 42 3 0.5 211 0 3 2 43 3 1 012 0 4 0 44 3 1 113 0 4 1 45 3 2 014 0 4 2 46 3 3 015 0 5 0 47 3 4 016 0 5 1 48 4 0.5 017 0 5 2 49 4 0.5 118 0 6 0 50 4 0.5 219 0 6 1 51 4 1 020 1 0.5 0 52 4 1 121 1 0.5 1 53 4 2 022 1 0.5 2 54 4 3 023 1 1 0 55 4

41、 4 024 1 1 1 56 4 5 025 1 2 0 57 4 6 026 1 3 027 1 4 028 1 5 029 1 6 030 2 0.5 031 2 0.5 1Table 5.7.1-4 lists the mapping to physical resources for the different random access opportunities needed for the PRACH densities, . Each quadruple of the format indicates the location of a specific random RAD

42、),(210RARAttfaccess resource, where is a frequency resource index, indicates whether the resource is reoccurring in f every even frame, in every odd frame, or in both odd and even frames, respectively, indicates whether the random 1RAtaccess resource is located in half frame 0 (first half frame) or

43、in half frame 1 (second half frame), and is the UL 2RAtsubframe number where the preamble starts (counting from 0 at the first UL subframe in each half frame), with the exception of preamble format 4 which is always transmitted in UpPTS. For preamble formats 0 to 3, the start of the random access pr

44、eamble shall be aligned with the start of the corresponding uplink subframe at the UE assuming a timing advance of zero. For preamble format 4, the preamble shall start before the end of the UpPTS at the s4832TUE.For some PRACH configurations there are several entries in Table 5.7.1-4 for a single c

45、onfiguration in order to reach the specified density of PRACH opportunities. The PRACH opportunities within a configuration are allocated in time first and then in frequency if and only if time multiplexing is not sufficient to hold all opportunities of a configuration without overlap in time. For p

46、reamble format 0-3, the frequency multiplexing shall be done according to3GPPError! No text of specified style in document.7Error! No text of specified style in document.otherwis,26602md, RARAofsetPBULRBAofsetPfnNfnwhere is the first resource block allocated to the PRACH opportunity considered and w

47、here indicates RAPBn RAofsetPBn the first resource block available for PRACH. For preamble format 4, the frequency multiplexing shall be done according to otherwis,266 02md)2()md( f, 1 RARAofsetPBULRB RASPfAofsetPfnN tNnnwhere is the system frame number and where is the number of DL to UL switch poi

48、nts within the radio frame.f SPNEach random access preamble occupies a bandwidth corresponding to 6 consecutive resource blocks for both frame structures.3GPPError! No text of specified style in document.8Error! No text of specified style in document.Table 5.7.1-4: Frame structure type 2 Random acce

49、ss preamble mapping in time and frequency.UL/DL configuration (See Table 4.2-2)PRACH conf. IndexPreambleformat 0 1 2 3 4 5 60 0 (0,0,0,2) (0,0,0,1) (0,0,0,0) (0,0,0,2) (0,0,0,1) (0,0,0,0) (0,0,0,2)1 0 (0,1,0,2) (0,1,0,1) (0,1,0,0) (0,1,0,2) (0,1,0,1) (0,1,0,0) (0,1,0,2)2 0 (0,0,1,2) (0,0,1,1) (0,0,1,0) (0,0,0,1) (0,0,0,0) (0,0,0,0) (0,0,1,1)3 0 (0,2,0,2) (0,2,0,2) (0,2,0,0) (0,2,0,2) (0,2,0,1) (0,2,0,0) (0,2,0