3GPP TSG-RAN Meeting #27 Tokyo, Japan, 09 - 11 March 2005

Tdoc RP-050143
CR-Form-v7.1

CHANGE REQUEST
25.306 CR 106 rev

-

Current version:

6.3.0
symbols.

For HELP on using this form, see bottom of this page or look at the pop-up text over the

Proposed change affects:

UICC apps

ME X Radio Access Network X

Core Network

Title: Source:

Definition of Six UE categories for Enhanced Uplink Fujitsu, Motorola, NEC, Nokia, Nortel Networks, NTTDocomo, Orange, Philips, Vodafone Group EDCH-L23 B Date: Release: 08/03/2005 Rel-6

Work item code: Category:

Use one of the following categories: Use one of the following releases: F (correction) Ph2 (GSM Phase 2) A (corresponds to a correction in an earlier release) R96 (Release 1996) B (addition of feature), R97 (Release 1997) C (functional modification of feature) R98 (Release 1998) D (editorial modification) R99 (Release 1999) Rel-4 (Release 4) Detailed explanations of the above categories can Rel-5 (Release 5) be found in 3GPP TR 21.900. Rel-6 (Release 6) Rel-7 (Release 7)

Reason for change:

UE categories were discussed at RAN1#40 meeting. The proposed categories classify the UEs in terms of 1) maximum number of E-DCH codes transmitted, 2) support of the 2ms TTI and 3) maximum transport block size (i.e. maximum bit rate). It was agreed that a total of 6 categories would span a reasonable range of configurations. Among the 8 categories that were initially proposed, 5 were agreed in RAN1. Two were felt as close enough to the agreed 5 to be potentially removed. But there was no agreement wether the following category should be included or not: 2xSF2, 10ms TTI only, 20000 bits. This category allows high bit rate for 10ms TTI only configurations. Regardless of the gains a 2ms TTI may bring, undoubtedly there is a benefit in making the 10ms TTI as efficient as possible, and as such there should not be any reasons not to allow a category aiming at doing so. Going even further, the maximum transport block size for 10ms TTI could be increased to 24000 bits. Therefore it is proposed to standardize the 5 categories agreed in RAN1 with a maximum transport size of th 24000 bits for the 10ms TTI + the 6 category that maximises the performance of 10ms TTI only configurations. Table 5.1g added with 6 UE categories No UE categories defined for E-DCH

Summary of change: Consequences if not approved: Clauses affected:

5.1 Y N

CR page 1

org/specs/ For the latest version.org/specs/CR. All 3GPP specifications can be downloaded from the 3GPP server under ftp://ftp. Delete those parts of the specification which are not relevant to the change request. 2001-03 contains the specifications resulting from the March 2001 TSG meetings.htm.g. 3) With "track changes" disabled.3gpp. Below is a brief summary: 1) Fill out the above form.3gpp. look for the directory name with the latest date e. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes. The symbols above marked closest to. CR page 2 . contain pop-up help information about the field that they are 2) Obtain the latest version for the release of the specification to which the change is proposed.Other specs affected: X Other core specifications X Test specifications X O&M Specifications Other comments: How to create CRs using this form: Comprehensive information and tips about how to create CRs can be found at http://www. paste the entire CR form (use CTRL-A to select it) into the specification just in front of the clause containing the first piece of changed text.

32. 5. 6. 81920. 64. 128. 163840 640. 3840. 400. 65536. 256. 10240. 200. 4. 512. 32. 5. 1280. 10240. 10240. 5. 6400.1 Value ranges Table 5. 4096. 5120. 40960. 512 4. 1000 kBytes 3. 2560. 20480.3GPP TS 25. 8. 40960. 20480. 163840 640. 163840 4. 6400. 81920. 48. 131072 bytes 2.. 16. 5120. 16384. 163840 640. 6. 1280. 81920. 81920. 128. 8960. 2. 1024 Yes/No CR page 3 . 3. 1024 Yes/No 640. 8. 16. 8. 32. 20480. 16. 64. 50. 16. 3840. 48. 8 2. 1024 32. 7680. 7. 8. 6400. 20480. 163840 640. 1280. 48. 48. 96. 2560. 128. 128. 7680. 7680. 64. 163840 2. 16. 48. 32 1. 256. 32768. 24. 1024 32. 10240. 5120. 8 4. 4095 640. 8960. 64. 40960. 128. 8. 96. 256. 30 2047. 81920. 1. 4. 8960. 300. 7. 1024. 4. 6400.306 v6. 8. 64. 5120. 20480. 512 PDCP parameters RLC and MAC-hs parameters PHY parameters Transport channel parameters in downlink arbitrary time instant Maximum sum of number of bits of all convolutionally coded transport blocks being received at an arbitrary time instant Maximum sum of number of bits of all turbo coded transport blocks being received at an arbitrary time instant Maximum number of simultaneous transport channels Maximum number of simultaneous CCTrCH Maximum total number of transport blocks received within TTIs that end within the same 10 ms interval Maximum number of TFC Maximum number of TF Support for turbo decoding Maximum sum of number of bits of all transport blocks being transmitted at an arbitrary time instant Maximum sum of number of bits of all convolutionally coded transport blocks being transmitted at an arbitrary time instant Maximum sum of number of bits of all turbo coded transport blocks being transmitted at an arbitrary time instant Maximum number of simultaneous transport channels Maximum number of simultaneous CCTrCH of DCH type (TDD only) Maximum total number of transport blocks transmitted within TTIs that start at the same time Maximum number of TFC Maximum number of TF Support for turbo encoding Transport channel parameters in uplink 16. 7680.3. 256. 6400. 7680. 32. 1280. 3. 4. 8. 8960. 6. 40960. 16. 6400. 8960. 128. 7680. 256. 10240. 500. 64. 64. 16384 Not supported. 10240. 4. 3840. 512. 1280.0 (2004-12) CR page 3 5. 5120. 2560. 256. 100. 96. 2. 1280. 16. 12. 2560. 32 1. 512.65535 2. 2560. 3840. 3840. 40960. 5120. 81920. 150. 2048. 512. 128. 32. 2560. 96. 8192.1: UE radio access capability parameter value ranges UE radio access capability parameter Support for RFC 2507 Support for RFC 3095 Support for RFC 3095 context relocation Support for loss-less SRNS relocation Maximum header compression context space Maximum number of ROHC context sessions Support for Reverse Decompression Total RLC AM and MAC-hs buffer size Maximum number of AM entities Maximum RLC AM window size Maximum sum of number of bits of all transport blocks being received at an Value range Yes/No Yes/No Yes/No Yes/No 1024. 20480. 256. 8960. 10. 3840. 40960. 4. 750. 512.

1 Yes/No Yes/No 3.. 5. 38400.8 MHz to 245.3GPP TS 25. 4. 1200.16 1. S-CCPCH) Support for SF 512 Support of PDSCH Support of HS-PDSCH Simultaneous reception of SCCPCH and DPCH Simultaneous reception of SCCPCH.14 1.28 Mcps physical channel parameters in uplink RF parameters FDD RF parameters Tx/Rx frequency separation CR page 4 . 28800.3.0 (2004-12) CR page 4 FDD Physical channel parameters in downlink UE radio access capability parameter Maximum number of DPCH/PDSCH codes to be simultaneously received Maximum number of physical channel bits received in any 10 ms interval (DPCH.. PDSCH.. 9600. 2400. 8 600. 19200. 14400.. 67200. 2 16..84 Mcps physical channel parameters in downlink Support of dedicated pilots for channel estimation Support of dedicated pilots for channel estimation of HS-DSCH Maximum number of DPDCH bits transmitted per 10 ms Support of PCPCH Maximum number of timeslots per frame Maximum number of physical channels per frame Minimum SF Support of PDSCH Support of HS-PDSCH Maximum number of physical channels per timeslot Maximum Number of timeslots per frame Maximum number of physical channels per timeslot Minimum SF Support of PUSCH Maximum number of timeslots per subframe Maximum number of physical channels per subframe Minimum SF Support of PDSCH Support of HS-PDSCH Maximum number of physical channels per timeslot Support 8PSK Maximum number of timeslots per subframe Maximum number of physical channels per timeslot Minimum SF Support of 8PSK Support of PUSCH UE power class Yes Yes/No 600. 2 16. 1 Yes/No Yes/No 1.6 1. 6. 28800. 8.8 MHz to 205. 3600. 76800 Yes/No Yes/No Yes/No Yes/No Yes/No Yes/No 1 NOTE: Only the value 1 is part of this release of the specification FDD Physical channel parameters in uplink TDD 3. 38400. 1200.306 v6. 4.14 1. 2. 4800. DPCH and HS-PDSCH Maximum number of simultaneous SCCPCH radio links Value range 1.16 Yes/No 1. 4. 7200.28 Mcps physical channel parameters in downlink TDD 1.6 1. 2. 8. 96 16. 2.2 MHz 134. 4 NOTE: Only power classes 3 and 4 are part of this release of the specification 190 Mhz 174. 1 Yes/No 1. 1 Yes/No Yes/No 1.. 48000. 3. 19200. 3. 57600. 2.2 MHz TDD 3. 2400.. 9600. 2. 48000.224 16. 57600 Yes/No 1. 3. DPCH and PDSCH Simultaneous reception of SCCPCH.84 Mcps physical channel parameters in uplink TDD 1. 4800. …. 7.

UTRA mode and RAT) R99. b). b+c). 3 NOTE: Only power classes 2 and 3 are part of this release of the specification TDD 1. REL-5 32 kbps. b).84 Mcps Support of UTRA TDD 1. a+c). a+b). c). a+c). 3 a). b+c). 384 kbps Measurement related capabilities General capabilities DL capabilities with simultaneous HSDSCH Access Stratum release indicator DL capability with simultaneous HSDSCH configuration Table 5.3GPP TS 25. UTRA mode and RAT) Yes/No (per frequency band.84 Mcps RF parameters UE radio access capability parameter UE power class Value range 2.306 v6.1a: FDD HS-DSCH physical layer categories HS-DSCH category Maximum number of HS-DSCH codes received 5 5 5 5 5 5 10 10 15 15 5 5 Minimum inter-TTI interval Maximum number of bits of an HS-DSCH transport block received within an HS-DSCH TTI 7298 7298 7298 7298 7298 7298 14411 14411 20251 27952 3630 3630 Total number of soft channel bits Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Category 10 Category 11 Category 12 3 3 2 2 1 1 1 1 1 1 2 1 19200 28800 28800 38400 57600 67200 115200 134400 172800 172800 14400 28800 CR page 5 .0 (2004-12) CR page 5 RF parameters TDD 3. 64 kbps.28 Mcps Support of GSM Support of multi-carrier Support of UTRAN to GERAN Network Assisted Cell Change Support of ciphering algorithm UEA0 Support of ciphering algorithm UEA1 Support of integrity protection algorithm UIA1 Standalone location method(s) supported Network assisted GPS support GPS reference time capable Support for IPDL Support for OTDOA UE based method Support for Rx-Tx time difference type 2 measurement Support for UE Positioning assisted GPS measurement validity in CELL_PCH and URA_PCH RRC states Support for SFN-SFN observed time difference type 2 measurement Need for downlink compressed mode Need for uplink compressed mode a). a+b+c) Yes/No Yes/No Yes/No Yes/No (per GSM frequency band) Yes/No Yes/No Yes Yes Yes Yes/No Network based / UE based / Both/ None Yes/No Yes/No Yes/No Yes/No Yes Yes/No Yes/No (per frequency band. a+b+c) 2.28 Mcps RF parameters Multi-mode related parameters Multi-RAT related parameters Security parameters UE positioning related parameters Radio frequency bands UE power class Radio frequency bands Support of UTRA FDD Support of UTRA TDD 3. 128 kbps. REL-4.3. c). a+b).

3.28 Mcps TDD HS-DSCH physical layer categories HS-DSCH category Maximum number of AM RLC entities Minimum total RLC AM and MAC-hs buffer size [kBytes] 50 50 50 50 50 50 50 50 50 50 50 Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Category 10 Category 11 6 6 6 6 6 6 6 6 6 6 6 CR page 6 . Table 5.1d: RLC and MAC-hs parameters for 1.1b: RLC and MAC-hs parameters for FDD HS-DSCH physical layer categories HS-DSCH category Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Category 10 Category 11 Category 12 Maximum number of AM RLC entities 6 6 6 6 6 6 8 8 8 8 6 6 Minimum total RLC AM and MAC-hs buffer size [kBytes] 50 50 50 50 50 50 100 100 150 150 50 50 Table 5.1c: 1.306 v6.28 Mcps TDD HS-DSCH physical layer categories HS-DSCH category Maximum number of HSDSCH codes per timeslot Maximum number of HSDSCH timeslots per TTI Maximum number of HSDSCH transport channel bits that can be received within an HSDSCH TTI 7016 7016 7016 7016 7016 7016 10204 10204 10204 10204 10204 10204 14056 14056 14056 Total number of soft channel bits Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Category 10 Category 11 Category 12 Category 13 Category 14 Category 15 12 12 12 16 16 16 12 12 12 16 16 16 16 16 16 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 28160 56320 84480 28160 56320 84480 40912 81824 122736 40912 81824 122736 56320 112640 168960 Table 5.0 (2004-12) CR page 6 UEs of Categories 11 and 12 support QPSK only.3GPP TS 25.

1f: RLC and MAC-hs parameters for 3.306 v6.84 Mcps TDD HS-DSCH physical layer categories HS-DSCH category Maximum number of HSDSCH codes per timeslot Maximum number of HSDSCH timeslots per TTI Maximum number of HS-DSCH transport channel bits that can be received within an HS-DSCH TTI 12000 12000 24000 24000 36000 36000 53000 73000 102000 Total number of soft channel bits Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 16 16 16 16 16 16 16 16 16 2 12 4 12 6 12 12 12 12 52992 52992 105984 105984 158976 158976 211968 264960 317952 Table 5.84 Mcps TDD HS-DSCH physical layer categories HS-DSCH category Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Maximum number of AM RLC entities 6 6 6 6 6 6 6 8 8 Minimum total RLC AM and MAC-hs buffer size [kBytes] 50 50 50 50 100 100 150 150 200 Table 5.0 (2004-12) CR page 7 HS-DSCH category Maximum number of AM RLC entities Category 12 Category 13 Category 14 Category 15 6 6 6 6 Minimum total RLC AM and MAC-hs buffer size [kBytes] 50 100 100 100 Table 5.1g: FDD E-DCH physical layer categories E-DCH category Maximum number of E-DCH codes transmitted 1 2 Minimum spreading factor Support for 10 and 2 ms TTI EDCH Maximum number of bits of an E-DCH transport block transmitted within a 10 ms E-DCH TTI Maximum number of bits of an E-DCH transport block transmitted within a 2 ms E-DCH TTI Category 1 Category 2 10 ms TTI only 7296 10 ms and 14592 2919 2 ms TTI Category 3 2 SF4 10 ms TTI only 14592 Category 4 2 SF2 10 ms and 24000 5837 2 ms TTI Category 5 2 SF2 10 ms TTI only 24000 Category 6 4 SF2 10 ms and 24000 11520 2 ms TTI NOTE: When 4 codes are transmitted in parallel. two codes shall be transmitted with SF2 and two with SF4 SF4 SF4 CR page 7 .3.1e: 3.3GPP TS 25.

306 v6.0 (2004-12) CR page 8 CR page 8 .3.3GPP TS 25.

Sign up to vote on this title
UsefulNot useful