RPC Training Session: Topic III Overview of Coexistence Planning for Narrowband, Wideband,

1
National Public Safety Telecommunications Council
RPC Training Session Topic IIIOverview of
Coexistence Planning for Narrowband, Wideband,
BroadbandOperations Islip, New York, November
14, 2006
Sean OHara NPSTC Technical Support Regions 8,
19, 28, 30 and 55 SRC - State of New York -
SWN 315-452-8152 (office) ohara_at_syrres.com
David Eierman Motorola Principal Staff
Engineer [phone] (office)
David.Eierman_at_motorola.com
2
Introduction

• Purpose
• Introduce RPCs to techniques and requirements for
  handling coordination and coexistence of diverse
  700 MHz technologies
• This will only provide an overview
• Relevancy
• Immediate need to manage these issues, since 700
  MHz spectrum is likely to become flexible use to
  a much larger degree than it was yesterday
• Audience
• Technical
• System Operators, RPC Technical Committee
  Members, Frequency Coordinators, Spectrum and
  System Planners, etc
• Collaboration
• These guidelines were developed through
  collaboration with Industry as well as public
  safety
• DataRadio, Lucent Technologies, M/A-COM,
  Motorola, NPSTC, Qualcomm
• Next Steps
• NPSTC and Industry will generate and make
  available a detailed set of coexistence
  guidelines early on in 2007

3
Reminder

• It is up to us (the RPCs) to manage this spectrum
  effectively
• If we do not
• Interference will result
• Regional capacity will drop
• Flexibility will go out the window
• The FCC gives us basic rules we can impose
  whatever additional Regional restrictions/rules
  are necessary to manage the spectrum
• The spectrum management responsibility has been
  given to us

4
Final BB/WB/NB Guidelines

• The final Guidelines will be written such that it
  could be adapted by the RPCs without having to
  develop their own.
• The Guidelines will contain
• Coordination procedures
• Deployment recommendations (power flux limits,
  minimum desired level targets, etc)
• Interference mitigation procedures

5
Overview and Schedule
6
Key Concepts

• Recall some concepts from earlier session they
  are important here as well
• Reliability
• Channel Performance Criterion (CPC) for Voice and
  Data Services
• Near/Far Effects
• Adjacent Channel Coupled Power Ratio (ACCPR)
• We do not have time to review these in full here,
  but please ask Qs if appropriate as we go along

7
700 Technologies

• Narrowband Technologies
• Use Voice and Data up to 100 kbps (raw)
• Channel Size 6.25 kHz, 12.5 kHz, 25 kHz
• Modulation Methods C4FM, F4FM, GFSK, QAM
• Access Methodologies FDD, FDMA/TDMA
• Products Project 25, OpenSky, HPD, others
• Wideband Technologies
• Use Data up to 800 kbps (raw)
• Channel Size 50 kHz, 100 kHz, 150 kHz
• Modulation Methods QPSK through 64-QAM,
  FM/N-ary FSK
• Access Methodologies FDD, and TDD
• Products SAM, IOTA, others
• Broadband Technologies
• Use Voice High Speed Data (beyond 1 Mbps)
• Channel Size 1.25 MHz to 5 MHz
• Modulation Methods OFDM with QAM, CDMA with
  N-PSK
• Access Methodologies FDD, and TDD
• Products 802.16/e, 802.20, cdma2000 EVDO, UMTS

8
National Public Safety Telecommunications Council
Co-ChannelCoordination
9
Co-Channel Planning

• Co-channel planning for most situations is a
  matter of bandwidth and power coupling ratios
• NB to NB, WB to WB
• NB to WB, NB to BB
• WB to BB
• BB to BB involves technology aspects as well

NB to BB is a special case for border areas or
by waiver
10
Power Coupling

• Recall the ACCPR calculations covered in the
  earlier session.
• The same calculations need to be done for the
  co-channel cases, except the signals now overlap.
• This can actually be easier, since the
  interfering power density is either (1) more
  uniform over the capture filter shape or (2) is
  completely captured by the victim receiver.

11
Power Coupling
DWE
6.25-kHz
12.5-kHz
Unless both signals are BB For planning, you
can simply look at the total power of the
interfering signal, de-rated by the power coupled
into the other signal
25.0-kHz
50-kHz
100-kHz
150-kHz
1.25 MHz
12
Power Coupling
DWE
De-rate co-channel interferers ERP by the table
at left, then perform normal co-channel
analyses Note that as the victim bandwidth gets
wider it captures more interference Also note
that as the interferer gets wider, it offers less
interference into narrower victim, bandwidths
13
Implications
DWE

• With -23 dB power coupling, a single NB/WB to
  co-channel BB coordination can be treated much
  like an adjacent channel coordination was
  performed at NPSPAC
• NB and BB can get much closer to each other than
  NB to NB or NB to WB
• However, a BB signal may capture many NB/WB
  co-channel interferers at each field point
• All the NB/WB power must be captured and combined
  like in the multiple NB interferer cases shown
  earlier today.
• BB may be the one to get interfered with first.

NB to BB is a special case for border areas or
by waiver
14
Implications
SYS-2 BB 1 Channels
SYS-2 (BB) gets interfering power from both SYS-1
(NB), and SYS-3 (NB/WB) Therefore it suffers
reliability degradation as much as 6-10 dB
earlier, with reduced throughput at cell edges
SYS-1 NB/WB 4 Channels
SYS-3 NB/WB 3 Channels
NB to BB is a special case for border areas or by
waiver
15
Technology Dependent Considerations

• OFDM/A to OFDM/A
• Still collecting information on this, will cover
  in more detail in the final guidelines
• Must use FDD in this allocation, right now WiMAX
  (802.16) is focused on TDD
• CDMA to CDMA
• Intra-system co-channel operations are handled
  through the technology and hand-offs
• Inter-system co-channel coordination is possible,
  even between adjacent counties
• However, systems should be coordinated (PN-offset
  codes) and synchronized
• RPCs should encourage and/or require this
  coordination
• CDMA to OFDM/A
• Use power coupling method
• All Technologies
• Right now there is a real need for consistent
  CPCf specifications across the technologies
• These will need to be a CPC function, one that
  related required S/(?IN) to data
  throughput/goodput, message success rate or some
  other data metric

16
National Public Safety Telecommunications Council
Adjacent and Off ChannelCoordination
17
Adjacent and Off ChannelCoordination

• In this area we look at coexistence of both
  direct adjacent channel technologies as well as
  off-channel technologies
• Adjacent are within one NB/WB channel block width
  (NB up to 25-kHz, WB up to 150-kHz)
• Off-Channels can be as far away as 10-MHz
• The main factor involved is the determination of
  near/far Hole sizes and impacts (Swiss
  Cheese)
• Caused by ACCPR effects
• Caused by Out of Band Emissions (OOBE)
• Undesired emissions from other deployments
  leaking into the band where the desired signal
  operates
• Caused by receiver effects (IM and Overload)
• High levels of out of band power that cause the
  victim receiver to operate in a non-linear manner
  and degrade the ability to receive and
  understand the desired signal

18
Swiss Cheese, Reliability Loss
19
C/(?IN), Swiss Cheese Effects
Note the mobile edge of cell effects from TDD
or OOBE
20
C/(?IN), Swiss Cheese Effects
S/(?NI)
S/N
21
Adjacent Channel Coordination

• Recall earlier session on TSB-88-based
  coordination
• Process
• Compute technology to technology ACCPR
• De-rate interferer and follow co-channel approach
• Avoid allowing the adjacent channel interferers
  site inside victims service area
• Manage near/far in overlap areas
• If adjacent channel is BB, use off-channel
  approach

22
Off-Channel Near/Far Holes
DWE

• Need to look at path isolation, IM, and link
  analyses for scenarios of interest
• Necessary to understand the problem
• We will review the magnitude of the noise floor
  degradations with respect to current rules, and
  consistent broadband rules set for the 700 MHz
  public safety allocations
• Current Rules Part 27, Commercial use of the
  upper 700 MHz
• Examine what attenuation a guard band or guard
  distance must provide to narrowband and broadband
  operations
• Assess impacts to public safety
• Frequency coordination and utilization issues
• Size and impact of interference holes

23
DWE
Near/Far Holes from BB OOBE Existing Part 27
Rules
PS and Commercial BB
NB PS LMR
-36 dBm
10 dB Main Beam Gain (and line losses)
-46 dBm
76 10logP into 6.25 kHz Additional filtering
and guard band of about 1MHz can reduce this
further
Desired Mobile Signal
Path Isolation Coupling loss between the output
of the dipole transmit antenna and a victim
dipole Free space loss between dipoles
Antenna pattern discrimination below
main beam
Reliability Losses
97 Reliability at CPC (Z1.88, ? 8)
- 92 dBm
?Z 15 dB
50 Reliability at CPC
-107 dBm
18 dB CPCf
-125 dBm
NB Noise Floor kTB NF
24
Typical Antenna Pattern (824-896 MHz) -DB872G60A
Panel Antenna-
Horizontal/Azimuth Pattern
Vertical/Elevation Pattern
25
Path Isolation Parameters
R2 d2 h2 Distance for Free Space Loss
? atan(h/d) The depression angle and downtilt
angle are used to determine antenna pattern
discrimination below main beam.
h
R
?
d
Field Location
26
Vertical Pattern Attenuation for Several Transmit
Heights (Using 3-degrees Downtilt) 30, 50, 70,
and 100 meter transmit heights
Antenna discrimination has little effect after
75 to 175-m
27
Free Space Path Loss Between Dipoles 30, 50, 70,
and 100 meter transmit heights
Antenna height little effect after 25 to 100-m
28
Path Isolation 30, 50, 70, and 100 meter transmit
heights, with 3-deg downtilt
Antenna and TX height dominate at 100 to 350-m
Free space loss dominates after
29
The Table Lamp Path Isolation 30 m transmitter
height, with 3-deg downtilt
Free Space
Free Space
Antenna Nulls
30
Path Isolation (Free Space Loss, and Vertical
Pattern Attenuation) 30, 50, 70, and 100 meter
transmit heights, with 3-deg downtilt
80 dB Typical for PS LMR
70 dB Typical for Cellular
31
OOBE Reliability Degradation vs. Hole
Size Standard Mobile Noise Limited Design (97)
Long distance reliability degradation effects
Probability of Achieving DAQ of 3.5 for P25
Large reliability losses in Hole for lower sites
32
OOBE Reliability Degradation vs. Hole Size Mobile
Noise 5 dB Margin Design (97)
No long distance reliability degradation effects
Probability of Achieving DAQ of 3.5 for P25
Manageable reliability losses in Hole for all
sites
33
OOBE Reliability Degradation vs. Hole
Size Standard Portable Noise Limited Design (97)
No long distance reliability degradation effects
Probability of Achieving DAQ of 3.5 for P25
Manageable reliability losses in Hole for all
sites
10 dB Antenna losses
34
DWE
Power Flux Density (PFD)
Desired
Undesired
Individual PFD Total power of individual
undesired signals Cumulative PFD Total power of
all undesired signals
35
Near/Far Holes from NB/WB/BB IM
PS Commercial NB/WB/BB
Power Flux Density at the Input to NB Victim
Dipole
- 45 dBm
NB PS LMR
Portable radio antenna losses relative to dipole
(if applicable)
Desired Mobile Signal
IMR IM Rejection relative to static sensitivity
of PS receiver IMR(NB) lt IMR(WN) lt
IMR(BB) IMR(NB) 75 dB (Mobile)
Reliability Losses
97 Reliability at CPC (Z1.88, ? 8)
- 92 dBm
?Z 15 dB
50 Reliability at CPC
-107 dBm
18 dB CPCf
Static Sensitivity kTB NF Cs/N
-125 dBm
NB Noise Floor kTB NF
36
DWE
Progression of Off Channel Interference (NB, WB,
and BB)
As signal levels on the ground rise, the impacts
shift from OOBE to IM to Overload
NB/WB to WB/NB IM and BB to NB/WB OOBE
Overload Range (OL)
BB to NB/WB IM
-20 dBm
-30 dBm
-40 dBm
37
Currently Proposed PFD Limits
DWE
Still Looking at final PFD recommendations, and
at what site distance it should be measured
38
Best Practices
DWE

• Pay attention to planning around and resolving
  these issues at the Regional Planning and
  Frequency Coordination level
• Should not create issues that need to be resolved
  later by adding cost to systems
• Bring system design team into Regional Planning
  and Frequency Coordination
• Frequency coordination and channel selection must
  happen early in the system design process
• Best practices to mitigate near/far effects
• Use additional filtering and guard band to reduce
  OOBE
• Limit undesired power at the ground (PFD
  Restrictions) to reduce IM and OL
• Raise desired power at the ground in appropriate
  areas to combat OOBE and IM
• Other sources of guidance
• Motorola Technical Appendix to the Nextel Best
  Practices Guide
• TIA TSB-88
• FINAL NPSTC COEXISTANCE GUIDELINES 1Q07

39
National Public Safety Telecommunications Council
Example (1)Deployment of NB/BB/WBwithin a
County
40
County BB and NB Coexistence

• Suppose in a given County, there is a desire to
  deploy 700 MHz BB data.
• Area 950 mi2
• Population 120,000
• BB Data Sites 30, each 100 foot high, with 6-km
  cell radius
• In the County there is already a 700 MHz NB
  system deployed
• NB Voice Sites 6, each 150 to 350 feet high
• How can this be done?
• What impacts need to be examined?
• How will the co-deployments affect each others
  performance?

41
First Where do we put the BB

• Need to decide where in the frequency band the BB
  can be deployed.
• There either needs to be a guard band or guard
  distance
• Since the guard distance is zero, a guard band
  must be employed
• How big should the Guard band be
• As big as it needs to be to meet the OOBE
  limitations
• External filters may be used here to control OOBE

42
Guard Band, OOBE and Filtering

• A combination of filtering and guard band will be
  required to meet the OOBE limitations into the
  nearest NB incumbent
• 76 10logP
• -46 dBm / 6.25 kHz

BB/WB
NB
For reasonable filtering, about a 1-MHz Guard
band would be required This can be reduced
through tighter filtering
43
Second How Do We Coordinate?

• Assume the OOBE level as the main transmitter
  power into the antenna.
• Run area reliability degradation study as we
  would for narrowband.
• We will see that this passes

44
Macro Example County Deployment
Example County Area 950 mi2 Population
120,000 NB Voice Sites 6 BB Data Sites 30
Propagation Model Longley Rice 1.2.2. Median
Mode No LULC
Broadband Sites 30-m Transmitter Height -38 dBm
ERP OOBE 6-km Site Radius
Received Power (dBm)
45
Macro Example County Deployment
Desired Signal (NB Site Coverage)
Undesired Signal (BB Site Coverage)
Received Power (dBm)
Received Power (dBm)
46
Macro Example County Deployment
S/I (dB)
Signal to Interference
47
Macro Example County Deployment
Results Broadband Effects No significant
interference effects 0.01 Reduction in Area
Reliability S/N, S/(?IN) Distributions
Identical Impacts would be greater for less
reliable designs
48
Impacts Near Sites

• Incumbent should look at the areas around the
  sites
• Look at the average desired power near the sites.
• In this case, it is all greater than -79 dBm into
  a dipole receive antenna (mobile coverage)
• Compute the average impact around the sites
• With the applicant meeting OOBE and PFD limits
• Decide whether or not to increase desired power
  near the sites
• Are the areas critical?
• Is the coverage degradation unacceptable?

49
Impacts Near Sites

• OOBE Impacts
• OOBE Level at ground at a D 150-m
• -36 dBm 70 dB -106 dBm
• Reliability at a distance D
• Assume undesired ? has no effect
• R 1 Qerf((-79 18 (-106))/8) 0.87 or 87
• IM Impacts
• Require applicant to show that (1) PFD limits are
  met, or (2), get agreement that degradation near
  the sites is acceptable to the incumbent
• If PFD is met, then it is up to the incumbent to
  increase desired power if coverage degradation
  near the BB sites is unacceptable

50
National Public Safety Telecommunications Council
Example (2)Deployment of BB/WBwithin/between
Regions
51
Co-Channel WB/BB Requests
Lets look at Several folks wishing to deploy BB
(1.25 MHz) and WB (50-kHz) systems County A
Wideband (8-Chan) County B Wideband
(8-Chan) County C Broadband (1-Chan) County D
Wideband (8-Chan) County E Broadband
(1-Chan) Note that these systems span three
Regions
A
D
C
B
E
52
What to Look For

• First Can the systems operate non co-channel?
• See below, there are three broadband channels
  available.
• We only need two BB channels
• The WB could use spectrum in the third, on
  between the BB channels

6-MHz
E
C
Flexible Use
Flexible Use
A,B,D
53
How About Worst Case?

• Lets assume worst case
• All systems operate co-channel
• Reasonable, since there are also other systems
  out there that need to use the spectrum as well

C and E
Flexible Use
Flexible Use
A,B,D
54
Co-Channel Coupling

• System A, WB, 8-50 kHz Channels
• 0-dB (100) Coupling from Sys-B and Sys-D
• 14-dB Coupling from Sys-C and Sys-E
• 10log(50 / 1250) -14dB
• System B, WB, 8-50 kHz Channels
• 0-dB (100) Coupling from Sys-A and Sys-D
• 14-dB Coupling from Sys-C and Sys-E
• 10log(50 / 1250) -14dB
• System C 1.25 MHz BB
• 0-dB (100) Coupling from Sys-B and Sys-D
• 0-dB (100) Coupling from Sys-A and Sys-B, and
  Sys-D
• System D, WB, 8-50 kHz Channels
• 0-dB (100) Coupling from Sys-A and Sys-B
• 14-dB Coupling from Sys-C and Sys-E
• 10log(50 / 1250) -14dB
• System E 1.25 MHz BB
• 0-dB (100) Coupling from Sys-B and Sys-D
• 0-dB (100) Coupling from Sys-A and Sys-B, and
  Sys-D

55
Analysis

• Analysis will follow the model set out
  earlierExcept
• We do not have a mature CPC model for data
  reliability and or goodput degradation
• For the high speed data systems (or any data
  systems), this is a need that needs to be worked
  on.
• Ongoing work in several areas to fill this need
• NPSTC (BB Task Force and Ad Hoc Joint TWG), RPCs,
  TIA/TR-8.18, etc

56
National Public Safety Telecommunications Council
QA and Feedback
57
QA and Feedback

• This is a lot to pack into 90-minutes
• I will be happy to go these concepts this again
  at area RPC meetings
• Usually attend Region 8, 30, 55 meetings
• Often attend Region 19 and 28 meetings as well
• Any Questions?
• Any Feedback?

58
Contact for Further Information
Sean OHara Business Area Manager Analysis,
Communications, and Collection Systems Syracuse
Research Corporation ohara_at_syrres.com 315.452.81
52 office, 315.559.5632 mobile
David Eierman Principle Staff Engineer Motorola d
avid.eierman_at_motorola.com 410.712.6242 office