4G TDD Planning

Mobile Access
Content
• Uplink / Downlink Subframe Configuration
• Special Subframe Configuration
• PHICH
• PDCCH
• PRACH
• PUCCH
• Paging
• Bit Rates
• Link Budget
• VoLTE

2
Uplink / Downlink Subframe
Configuration

Mobile Access
Frame Structure
• 3GPP specifies 2 radio frame structures • Subframes are categorised as:
• Type 1: applicable to FDD • Uplink
• Type 2: applicable to TDD • Downlink
• Special
1 Radio Frame = 10 ms • Half Frame of 5ms is most relevant to countries
1 Half Frame = 5 ms 1 Half Frame = 5 ms with legacy TDD systems using 5 ms radio frame

Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9

1 subframe =
1 TTI = 1 ms
DwPTS GP UpPTS

4
Uplink/Downlink Subframe Configurations
• 3GPP has specified 7 uplink/downlink subframe configurations
• provides flexibility in terms of:
• coexistence with existing radio technologies
• balance between uplink and downlink resource allocations
• subframes 0 and 5 are always downlink
• subframe 1 is always a Special Subframe, whereas subframe 2 is always uplink

5
UK 2.3 GHz Spectrum
• The UK regulator, OFCOM is planning to auction spectrum between 2350 and 2390 MHz
• Corrresponds to a subset of operating band 40 (2300 to 2400 MHz)
• OFCOM has specified that users of this spectrum must follow the transmission pattern
defined by uplink/downlink subframe configuration 2 (3DL:1UL)
• 5 ms switching pattern with 2 Special Subframes per radio frame

• OFCOM has also specified that the Special Subframes must follow the transmission pattern
defined by Special Subframe Configuration 6 (9DwPTS:3GP:2UpPTS)
• Small cells are excluded from these requirements

6
UK 3.4 GHz Spectrum
• The UK regulator, OFCOM is planning to auction spectrum between 3410 and 3600 MHz
• Corrresponds to a subset of operating band 42 (3400 to 3600 MHz)
• OFCOM has specified a ‘preferred’ frame structure but also states that any other
‘compatible’ frame structure can be used if operators co‐ordinate with one another

Preferred Frame Structure Compatible Frame Structure

• OFCOM has specified that the Special Subframes must follow the transmission pattern
defined by Special Subframe Configuration 6 (9DwPTS:3GP:2UpPTS)
• Small cells are excluded from these requirements

7
Special Subframe Configuration

Mobile Access
Special Subframes (I)
• Special Subframe is required to provide Guard Period (GP) to accommodate delays
associated with RF propagation and transceiver switching between UL and DL
• Special Subframe includes DwPTS, Guard Period and UpPTS
• Utilisation of the DwPTS and UpPTS depends upon their duration
• Subframe duration remaining after DwPTS and UpPTS forms the Guard Period (GP)

DwPTS = Downlink Pilot

Time Slot

UpPTS = Uplink Pilot

Time Slot

9
Special Subframes (II)
• The table below translates the 3GPP durations for DwPTS and UpPTS into symbol durations

10
 Guard Period Requirement
• The timing diagram below illustrates the reason for requiring a guard period at the DL‐>UL
switching point, but not at the UL‐>DL switching point

Propagation Delay Propagation Delay BTS Rx‐Tx

Switching
delay
BTS
Downlink Uplink Uplink Downlink
View

UE Downlink Uplink Uplink Downlink

View
UE Rx‐Tx
Switching Timing Advance brings
delay forward UE transmissions

Guard Period required at DL to UL Guard Period not required here as

switching to avoid overlap of DL gap is inherently generated by
and UL at the UE timing advance

11
Cell Range from Guard Period
Special DwPTS UpPTS Guard Guard Cell
• Each Special Subframe Guard Period Subframe (Ts) (Ts) Period Period Range
defines a maximum cell range Configuration (Ts) (μsec) (km)

• Guard period defines the maximum 0 6592 2192 21936 714 101
round trip delay 1 19760 8768 285 37

• Calculations assume: 2 21952 6576 214 26

3 24144 4384 143 15
• 40 μsec switching delay
4 26336 2192 71 5
• normal cyclic prefix for both
5 6592 4384 19744 643 90
uplink and downlink
6 19760 6576 214 26
• Calculations apply:
7 21952 4384 143 15
• 30720 Ts = 1 ms 8 24144 2192 71 5
9 13168 13168 429 58

Special Subframe selected

by OFCOM for UK 12
Uplink Frame timing
• The uplink frame timing for TDD includes an additional 624 Ts
• 624 Ts = 20 μsec
• allows time for the eNode B to switch from receiver to transmit
• The maximum NTA value of 20512 allows for the 100 km cell range

FDD TDD

10 ms Downlink Radio Frame Timing 10 ms Downlink Radio Frame Timing

NTA x Ts seconds (NTA + 624) x Ts seconds

10 ms Uplink Radio Frame Timing 10 ms Uplink Radio Frame Timing

0 < =NTA <= 20512 0 < =NTA <= 20512

13 30720 Ts = 1 ms
Synchronization Requirements
• Both FDD and TDD networks are frequency synchronized
• ensures that center frequencies are aligned in neighboring eNode B
• FDD networks may also have phase synchronization to support specific features
• e.g. MBMS and eICIC
• TDD networks must always have phase synchronization to time align the uplink/downlink
subframe configurations
• applicable both within a single network and to networks operating on adjacent
carriers

14
PHICH

Mobile Access
Uplink Resource Allocation Timings (I)
• In the case of FDD, uplink resource allocations are always applicable to the 4th subframe
following the subframe where the resource allocation was signalled on the PDCCH
• This pattern is not always possible for TDD because the 4th subframe may be a downlink
subframe
• Example for UL/DL Subframe Configuration 2 is shown below
• possible to maintain the 4th subframe pattern

Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9

DL UL DL DL DL UL DL DL

Resource
Allocation Resource
Allocation

16
Uplink Resource Allocation Timings (II)
• Example for UL/DL Subframe Configuration 1 is shown below
• 2 of the 4 resource allocations have a delay of 6 subframes rather than 4 subframes

Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9

DL UL UL DL DL UL UL DL

Resource Resource
Allocation Resource Allocation
Resource Allocation
Allocation

• UL/DL Subframe Configuration 0 is a special case because there are more UL subframes than
DL subframes
• means that some DL subframes include resource allocations for multiple UL subframes
• flag within PDCCH indicates which subframe the resource allocation targets

17
PHICH (I) means that PDCCH capacity can
vary between subframes

• The PHICH is not included in every downlink subframe

• it is only included when there is a requirement to send HARQ acknowledgements
• when there is a corresponding uplink subframe to send acknowledgements
• The example for UL‐DL subframe configuration 2 is shown below
• only 2 UL subframes so only 2 DL subframes which include the PHICH

Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9

DL UL DL DL DL UL DL DL

PHICH

PHICH

18
PHICH (II)
• In the case of UL/DL Subframe Configuration 0, there is a requirement for a DL subframe to
include the HARQ acknowledgements for multiple UL subframes
• due to there being more UL subframes than (DL subframes + Special Subframes)
• This doubles the number of PHICH Groups in subframes 0 and 5

Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9

DL UL UL UL DL UL UL UL

PHICH PHICH PHICH PHICH

19
PHICH (III)
• When dimensioning the PHICH it is necessary to account for the number of HARQ ACK which
need to be sent during each downlink subframe
• varies according to the uplink/downlink subframe configuration

UL‐DL Subframe UL DL HARQ ACK ACK to send

Configuration Subframes Subframes to send in DL per Subframe
0 6 4 6 1 or 2
1 4 6 4 1 or 0
2 2 8 2 1 or 0
3 3 7 3 1 or 0
4 2 8 2 1 or 0
5 1 9 1 1 or 0
6 5 5 5 1

20
PDCCH

Mobile Access
PDCCH
• The number of symbols available to the PDCCH depends upon the subframe number
• impacts CCE capacity
Subframes 1 and 6 (even when subframe 6 is a DL subframe)
• allocated symbols signalled by PCFICH 1.4 MHz channel: 2 symbols
Other channels: 1 to 2 symbols

Other DL subframes
1.4 MHz channel: 2 to 4 symbols
Other channels: 1 to 3 symbols
22
PDCCH – Capacity Example
• Assume:
• 20 MHz channel bandwidth
• Uplink/Downlink subframe configuration 2
• Special Subframe configuration 6
• Maximum symbols allocated to PDCCH
• 3 PHICH Groups
• Cell Specific Reference Signal for 2 antenna ports

23
PDCCH – Capacity Example
• Analysis must be done for each subframe
• PDCCH is fully available for downlink Resource Allocations in many subframes

Subframe 0 1 2 3 4 5 6 7 8 9

Total RE 3600 2400 UL 3600 3600 3600 2400 UL 3600 3600

PCFICH RE 16 16 UL 16 16 16 16 UL 16 16

PHICH RE 0 0 UL 36 0 0 0 UL 36 0

CS‐RS RE 400 400 UL 400 400 400 400 UL 400 400

PDCCH RE 3184 1984 UL 3148 3184 3184 1984 UL 3148 3184

CCE 88 55 UL 87 88 88 55 UL 87 88

CCE Required for UL No No UL Yes No No No UL Yes No

24
PRACH

Mobile Access
PRACH (I)
• 3GPP has specified 5 PRACH preamble formats for TDD
• Preamble Format 4 is specified for TDD only
• has a short duration of 4544 Ts and is designed to
be accommodated by the Special Subframe UpPTS
• When using the normal cyclic prefix in the uplink,
• duration of the PRACH preamble exceeds the
duration of the UpPTS

Smaller than 4544 Ts

26 Total of 4544 Ts
PRACH (II)
• 3GPP specifies the timing shown below for Preamble Format 4
• creates a Guard Period of 288 Ts = 9.375 μsec
• equivalent to a cell range of 1.4 km
• Allowing the PRACH preamble Cyclic Prefix to be transmitted within the Special Subframe
Guard Period is acceptable because only small cell ranges are permitted

upPTS Symbol 1 upPTS Symbol 2

Cyclic Guard
Prefix Sequence Period
4096 Ts Next subframe
448 Ts 288 Ts

upPTS Symbol 1 upPTS Symbol 2

27
PRACH (III) These columns replace the subframe and radio frame columns in the FDD table

• In the case of FDD, only a single

PRACH opportunity can be
configured during each
subframe, i.e. single set of 6
PRB
• TDD allows multiple PRACH
opportunities per subframe, i.e.
multiple sets of 6 PRB can be
allocated
• Increases the complexity of the
PRACH Configuration Index
table
• Density indicates the number
of PRACH opportunities per
radio frame
28
PRACH (IV)
• In the case of TDD, 3GPP specifies a second
PRACH Configuration Index table
• Each quadruplet within the table
corresponds to:

Frequency
Resource Index

Starting
All, even, odd uplink
1st or 2nd subframe
radio frames
half frame
Example of multiple PRACH
29 opportunities with equal timing
but different frequency offsets
PRACH (V)
• When multiple PRACH are frequency multiplexed within a single subframe then the frequency
domain position of each PRACH is fixed by a single input parameter (prachFreqOffset in case of
Nokia) and by the 3GPP equations shown below
• Take example of fRA values = 0,1,2,3 with
20 MHz channel, prachFreqOffset = 5 and Preamble formats 0 to 3
preamble formats 0 to 3
• Then PRACH is positioned at:
• 5
• 100 – 6 – 5 = 89
Preamble formats 0 to 4
• 5 + 6 = 11
• 100 – 6 – 5 – 6 = 83

30
PRACH (VI)
• The maximum cell range is limited by the Guard Time belonging to each preamble format
• Maximum Cell Range = Minimum of
uplink/downlink subframe
• Cell Range limited by PRACH Preamble Format configuration 2 supports a
maximum cell range of 14.5 km
• Cell Range limited by Special Subframe Configuration
because there is a maximum of
• Cell Range limited by PRACH Zero Correlation Zone 1 ms uplink transmission

Preamble Format Cyclic Prefix Sequence Guard Time Total Length Max. Cell Range
Duration Duration
0 103.13 μs 800 μs 96.88 μs 1 ms 14.5 km
1 684.38 μs 800 μs 515.63 μs 2 ms 77.3 km
2 203.13 μs 1600 μs 196.88 μs 2 ms 29.5 km
3 684.38 μs 1600 μs 715.63 μs 3 ms 100.2 km
4 14.58 μs 133 μs 9.38 μs 0.16 ms 1.4 km

31
PUCCH

Mobile Access
PUCCH (I)
• The PUCCH is not transmitted within the UpPTS field of the Special Subframes
• PUCCH capacity is limited by the number of uplink Subframes
• selecting an uplink/downlink subframe configuration which favours the downlink can
limit the number of connections per cell because PUCCH capacity becomes limited
• Similar to FDD, the PUCCH for TDD uses formats 1,1a,1b,2,2a,2b,3
• In the case of PUCCH Format 1b:
• FDD uses Format 1b with Channel Selection for Carrier Aggregation with 2 CC
• TDD can use Format 1b with Channel Selection without Carrier Aggregation
• can be used when necessary to transfer more than 2 HARQ ACK per subframe
• necessary when there are more downlink subframes than uplink subframes

33
PUCCH (II)
• In the case of PUCCH Format 3:
• FDD can transfer up to 10 HARQ ACK for 5 Component Carrier CA
• TDD can transfer up to 20 HARQ ACK, but only by applying an ‘AND’ function to
pairs of ACKs
• 20 HARQ ACK are reduced to 10 HARQ ACK before transmission
• means that a single block error results in re‐transmission of 2 blocks

34
PUCCH Dimensioning – Format 1 Nokia
parameters
• PUCCH Format 1 is used to transfer Scheduling Requests used for
• Assume Uplink/Downlink Subframe Configuration 2 example
• Step 1: Identify Scheduling Request period from cellSrPeriod
• assume a value of 20 ms for this example
• Step 2: Identify the maximum number of RRC Connected UE within a cell
• max{maxNumRrc + max(addAUeRrHo, addAUeTcHo), maxNumRrcEmergency}
• assume a value of 360 for this example
• Step 3: Determine the multiplexing capability of PUCCH format 1
• 3 orthogonal codes are available
• cyclic shifts are also available
• the number of cyclic shifts is given by: 12 / deltaPucchShift
• assuming deltaPucchShift = 1, there are 12 cyclic shifts available
35
PUCCH Dimensioning – Format 1
• Step 4: Final Calculation

Resource Block Requirement = ROUNDUP max number connections

(SR Period / 5) x Mux Capacity
Factor of 5 is new for TDD
Value is specific to UL/DL subframe configuration 2
Accounts for only 1/5th of subframes containing PUCCH

Resource Block Requirement = ROUNDUP 360 =3

(20 / 5) x 36

n1PucchAn = Resource Block Requirement x Mux Capacity = 108

36
PUCCH Dimensioning – Format 2
• PUCCH Formats 2, 2a and 2b are used to report Channel State Information (CSI)
• Step 1: Identify rate of periodic CQI reporting from cqiPerNp
• assume a value of 40 ms for this example
• Step 2: Identify the maximum number of RRC Connected UE within a cell
• max{maxNumRrc + max(addAUeRrHo, addAUeTcHo), maxNumRrcEmergency}
• assume a value of 360 for this example
• Step 3: Determine the multiplexing capability of PUCCH formats 2, 2a and 2b
• Nokia implementation uses a fixed set of 6 cyclic shifts
• 6 UE can be multiplexed per Resource Block

37
PUCCH Dimensioning – Format 2
• Step 4: Identify DRX configuration

CQI CQI CQI

DRX Enabled
RI RI RI

CQI
DRX Disabled

RI RI

• When DRX is enabled with Rank Indicator reporting, there is a requirement for twice the
number of PUCCH Resources for CSI reporting

38
PUCCH Dimensioning – Format 2
• Step 5: Final Calculation

DRX enabled
Resource Block Requirement = ROUNDUP 2 x max number connections
(Reporting Period / 5) x Mux Capacity

Resource Block Requirement = ROUNDUP 2 x 360 = 15 PRB

(40 / 5) x 6

• Thus, nCqiRb should be set equal to 15

39
PUCCH Dimensioning – Formats 1a, 1b
• PUCCH Formats 1a and 1b are used to signal HARQ acknowledgements and Scheduling
Requests
• Step 1: Calculate the maximum number of PDCCH CCE
• in the case of TDD this must be done ‘per subframe’
• required because the PUCCH resource index is calculated from PDCCH CCE index used to
make the associated PDSCH resource allocation
• requirement to account for overheads generated by Cell Specific Reference Signal, PCFICH
and PHICH
• Example taken from earlier slide (20 MHz channel, UL/DL subframe config 2)

Subframe 0 1 2 3 4 5 6 7 8 9

CCE 88 55 UL 87 88 88 55 UL 87 88

40
PUCCH Dimensioning – Formats 1a, 1b
• Step 2: Sum total number of CCE Associated with each Uplink Subframe
• the PUCCH within subframe 2 signals the ACKs for n‐8, n‐7, n‐4, n‐6
• Subframes 4, 5, 8, 6 having 88, 88, 87, 55 CCE
• Total of 318 CCE
• the PUCCH within subframe 7 signals
the ACKs for n‐8, n‐7, n‐4, n‐6
• Subframes 9, 0, 3, 1 having
88, 88, 87, 55 CCE
• Total of 318 CCE

Subframe 0 1 2 3 4 5 6 7 8 9

CCE 88 55 UL 87 88 88 55 UL 87 88

41
PUCCH Dimensioning – Formats 1a, 1b
• Step 3: Determine the multiplexing capability of PUCCH formats 1a, 1b
• Same as PUCCH format 1
• 3 x 12 / deltaPucchShift = 36 (for this example)

• Step 4: Final Calculation

Resource Block Requirement = ROUNDUP max number CCE

Mux Capacity

Resource Block Requirement = ROUNDUP 318 =9

36

42
Paging

Mobile Access
Paging
• In the case of FDD, paging is broadcast during subframes 0, 4 or 9
• In the case of TDD, paging is broadcast during subframes 0, 1, 5 or 6
• Subframes 0 and 5 are always downlink subframes
• Subframe 1 is always a special subframe
• Subframe 6 can be either a downlink subframe or a special subframe

UE specific based upon UE identity

i_s = 0 i_s = 1 i_s = 2 i_s = 3

Cell level Ns = 1 Subframe 0 ‐ ‐ ‐
configuration
according to Ns = 2 Subframe 0 Subframe 5 ‐ ‐
capacity
requirement Ns = 3 Subframe 0 Subframe 1 Subframe 5 Subframe 6

44
Bit Rates

Mobile Access
Downlink Bit Rates (I)
• The analysis of bit rates for TDD is complicated by the large number of combinations of
uplink‐downlink subframe configurations and special subframe configurations
• The example here is based upon the UK OFCOM scenario:
• uplink‐downlink subframe configuration 2
• special subframe configuration 6
• A 20 MHz channel with a normal cyclic prefix is assumed in both the uplink and downlink
directions

6 downlink subframes

2 uplink subframes
2 special subframes
46
Downlink Bit Rates (II)
Normal DL subframes
• Step 1: Calculate Total Downlink Resource Elements
• 100 PRB x 12 subcarriers x 14 symbols x 6 subframes Special subframes
+ 100 PRB x 12 subcarriers x 9 symbols x 2 subframes
= 122 400 Resource Elements per 10 ms Radio Frame

• Step 2: Remove overheads generated by PCFICH, PHICH, PDCCH, PBCH, Primary

Synchronisation Signal, Secondary Synchronisation Signal & Cell Specific Reference Signal
• Assume maximum PDCCH allocation as worst case
• 100 PRB x 12 subcarriers x 3 symbols x 6 subframes Includes PCFICH, PHICH,
+ 100 PRB x 12 subcarriers x 2 symbols x 2 subframes PDCCH and some Cell
Specific Reference Signal
= 26 400 Resource Elements per 10 ms Radio Frame

47
Downlink Bit Rates (III)
• Step 2 continued: Remove overheads generated by PCFICH, PHICH, PDCCH, PBCH,
Primary Synchronisation Signal, Secondary Synchronisation Signal & Cell Specific
Reference Signal
• PBCH occupies 228 RE
• Primary Synchronisation Signal = 144 RE
• Secondary Synchronisation Signal = 144 RE
• Cell Specific Reference Signal (outside PDCCH region)
• 100 PRB x 12 RE per PRB pair x 6 DL subframes
+ 100 PRB x 8 RE per PRB pair x 2 DL subframes
= 8800 RE
NET Resource Elements available to the PDSCH = 86 624

48
Downlink Bit Rates (III)
• Step 3: Translate Resource Elements to Throughput
• NET Resource Elements available to the PDSCH = 86 624
• QPSK => 17.3 Mbps
• 16QAM => 34.6 Mbps
• 64QAM => 52.0 Mbps
• 64QAM with 2x2 MIMO = > 103.9 Mbps
• Step 4: Remove other overheads
• coding rate assumption, e.g. 0.9
• Re‐transmission overhead
• SIB, Paging, SRB overheads in the order of 10 to 15 %
• TCP/IP overheads

49
Uplink Bit Rates (I)
• In the case of the uplink, the analysis is not dependent upon the special subframe
configuration because the PUSCH cannot be transmitted during the UpPTS
• The following example is based upon the UK OFCOM scenario:
• uplink‐downlink subframe configuration 2
• A 20 MHz channel with a normal cyclic prefix is assumed in both the uplink and downlink
directions

6 downlink subframes

2 uplink subframes
2 special subframes

50
Uplink Bit Rates (II)
Normal UL subframes
• Step 1: Calculate Total Uplink Resource Elements
• 100 PRB x 12 subcarriers x 14 symbols x 2 subframes
= 33 600 Resource Elements per 10 ms Radio Frame

• Step 2: Remove overheads generated by the PUCCH and Demodulation Reference Signal
• Assume PUCCH occupies 6 PRB
• 6 PRB x 12 subcarriers x 14 symbols x 2 subframes
= 2 016 Resource Elements per 10 ms Radio Frame
• Demodulation Reference Signal occupies 1 column of Resource Elements per PRB
• 94 PRB x 12 subcarriers x 2 symbol x 2 subframes
= 4 512 Resource Elements per 10 ms Radio Frame

51
Uplink Bit Rates (III)
• Step 2 continued: Removing the PUCCH and Demodulation Reference Signal Overheads
leads to:
33 600 ‐ 2 016 ‐ 4 512 = 27 072 Resource Elements per 10 ms Radio Frame

• The overheads generated by the PRACH and Sounding Reference Signal (SRS) can also be
removed
• overhead generated by the PRACH depends upon the PRACH format and PRACH
Configuration Index
• PRACH may be transmitted during the Special Subframe and have no impact
• Overhead generated by the SRS depends upon the transmission period

52
Uplink Bit Rates (IV) Maximum of 1 ms available when using
uplink‐downlink subframe configuration 2

• Step 2 continued:
• assuming PRACH Preamble Format 0 and Configuration Index 3 the PRACH
occupies: 12 rather than 14 symbols because
• 6 x 2 = 12 PRB every 10 ms radio frame DMRS already taken into account

• overhead of 6 PRB x 12 subcarriers x 1 subframes x 12 symbols

= 864 Resource Elements per 10 ms Radio Frame

• assuming the SRS is scheduled once every 10 ms then it occupies:

• 94 PRB x 12 subcarriers x 1 symbol
= 1 128 Resource Elements per 10 ms Radio Frame

53
Uplink Bit Rates (VI)
• Step 2 continued:
• Accounting for these overheads leads to:
27 072 – 864 – 1 128 = 25 080 Resource Elements per 10 ms Radio Frame

54
Uplink Bit Rates (VII)
• Step 3: Translate Resource Elements to Throughput
• NET Resource Elements available to the PUSCH = 25 080
• QPSK => 5.0 Mbps
• 16QAM => 10.0 Mbps
• 64QAM => 15.0 Mbps
• Step 4: Remove other overheads
• coding rate assumption, e.g. 0.9
• Re‐transmission overhead
• SRB overheads in the order of 10 to 15 %
• TCP/IP overheads

55
Link Budget

Mobile Access
Link Budget
• Differences between FDD and TDD link budgets include:
• Operating Band impacts:
• Antenna Gain
• Building Penetration Loss
• Propagation Loss
• Subframes per Radio Frame
• the reduced number of subframes per radio frame means that ‘throughputs
per subframe’ must be higher to achieve the same average throughput
• or example, to achieve an uplink average throughput of 1 Mbps with TDD
uplink/downlink subframe configuration 2 requires uplink subframes to
achieve 5 Mbps
• leads to an increased SINR requirement

57
Link Budget
• Differences between FDD and TDD link budgets include:
• Antenna Technology
• TDD may benefit from Beamforming from an antenna array
• Beamforming increases antenna gain
• 2 column antenna provides potential 3 dB increase
• 4 column antenna provides potential 6 dB increase
• Increased number of Power Amplifiers
• TDD may benefit from an increased number of Power Amplifiers providing
greater total downlink transmit power
• applicable when digital beamforming is used
• could also be applicable if 4x2 MIMO or 4x4 MIMO is used

58
VoLTE

Mobile Access
VoLTE Coverage
• Lack of TTI Bundling for some uplink/downlink subframe configurations likely to impact
coverage for a specific voice quality
• VoLTE link budget for TDD should not be impacted in the same way as data
• data requires a higher instantaneous throughput during downlink subframes to
compensate for uplink subframes, and vice versa
• VoLTE buffer can typically be emptied using a single subframe so no requirement to
compensate
Higher SINR required to
equal average throughput achieve higher instantaneous
throughput
Data

VoLTE
FDD TDD
60
VoLTE – PDCCH Capacity (I)
• Live network statistics indicate typical average PDCCH aggregation levels of 4 to 5

61
VoLTE – PDCCH Capacity (II)
• Live network statistics indicate typical average PDCCH aggregation levels of 4 to 5

Speech packets transferred

across the air every 40 ms

Uplink speech speech speech speech

(UE 1)
40 ms period

Uplink SID SID

(UE 2)

160 ms period

PDCCH transmissions per 160 ms = 4 +1 = 5 so average PDCCH use per 20 ms = 5 / 8 = 0.625

62
VoLTE – PDCCH Capacity (III)
• From earlier slide, the number of CCE available for a 20 MHz channel bandwidth
assuming uplink/downlink subframe configuration 2 and special subframe configuration 6
• Assume that scheduler targets 80% CCE utilisation

Subframe 0 1 2 3 4 5 6 7 8 9

CCE 88 55 UL 87 88 88 55 UL 87 88

80% of CCE 70 44 UL 69 70 70 44 UL 69 70

PDCCH Transmissions 17 11 UL 17 17 17 11 UL 17 17
assuming aggregation 4
CCE Required for UL No No UL Yes No No No UL Yes No

63
VoLTE – PDCCH Capacity (IV)
Subframe 0 1 2 3 4 5 6 7 8 9

PDCCH Transmissions 17 11 UL 17 17 17 11 UL 17 17
assuming aggregation 4
CCE Required for UL No No UL Yes No No No UL Yes No

• 34 PDCCH transmissions per 20 ms for Uplink assuming 50/50 split between uplink and
downlink resource allocations during subframes 3 and 8
• Thus VoLTE Capacity = 34 / 0.625 = 54 connections
• Removing overheads generated by 10 % re‐transmission rate and 5 % segmentation:
• 54 x 0.9 x 0.95 = 46 VoLTE users per cell

equivalent figure for 10 MHz FDD channel is 219 users

64
VoLTE – PDCCH Capacity (V)
• Simulation results confirm significantly lower VoLTE capacity on TDD network
• Example simulations for 10 MHz channel with uplink/downlink subframe configuration 1

63 390

65
TTI Bundling
• In the case of TDD, TTI Bundling is only supported for Uplink/Downlink Subframe
configurations 0, 1 and 6
• TTI Bundling is not supported by the UK OFCOM selection of Uplink/Downlink Subframe
configuration 2

• Bundles of 4 subframes are not contiguous subframes in the case of TDD

66
Semi Persistent Scheduling
• Limited PDCCH capacity increases the
argument to have Semi Persistent Scheduling
(SPS) for the uplink of VoLTE connections
• SPS provides a trade‐off between:
• PDCCH load
• dynamic scheduling gain
• Requires UE support (FGI 29)
• The following are fixed with SPS:
• number of allocated PRB
• position of allocated PRB
• MCS

67