�ݺ�ߣ

Examination of
Coordination Requests
International Telecommunication Union
Efficient use of the spectrum / orbit resource workshop, Cyprus 2014
Hon Fai Ng
Space Services Department

A
API
C
Coordination
N
Notification
Start of regulatory
clock
Negotiate for
interference free
operation
Record in MIFR
(International
Recognition)
& BIIU
7 years
Non-planned Procedures (Articles 9 & 11)

Input: Requests for coordination
Appendix 4 Info (No. 9.30)
BR: Validate/Check/Process
Output: CR/C Publication in
BR IFIC DVD
Conformity
with Radio
Regulations
(No. 9.35)
Coordination
Requirements
(No. 9.36)
C
Coordination

BR IFIC DVD

0
200
400
600
800
1983 1988 1993 1998 2003 2008 2013
cost recovery
introduced
Source: SNL (1983– 1997), SNTrack (1998-2013)
Coordination Requests
311 per year

300+ CR/C
Publications per year
Source: Coordination Requests received in between 2008 and 2013

Unfavourable
Finding
One in three CR/Cs (No. 11.31)
No status, priority lost, cost
recovery incurred
Source: Coordination Requests received in between 2008 and 2013

Substantial
coordination
workload
60+ affected administrations
2000+ affected networks
Source: Coordination Requests received in 2013 under No. 9.7

Fee remains unchanged after 100
units, no incentive to keep filings
small
Cost
recovery
fee
Units100 units
Source: Decision 482 (modified 2012) Doc C12/95(Rev.2)
2 beams
10 frequencies
5 emissions
1 class of station
Example:

HOW TO
 Avoid unfavourable findings
 Manage coordination requirements

Conformity
with Radio
Regulations
(No. 9.35)
Coordination
Requirements
(No. 9.36)
C
Coordination

Conformity
with Radio
Regulations
(No. 9.35 of RR)

Conformity with Table of
Frequency Allocation & other
provisions (PFD/EIRP Limits
etc.)
Nos. 9.35, 11.31 of RR, RoP11.31

Conformity with RR
(No. 9.35 of RR)
Network summary
Frequency bands
Direction of transmission
Class of station/Services
Beams/Service area
Table of Frequency
Allocation
(Article 5 of Radio Regulations)
Relevant footnotes

Conformity with RR
(No. 9.35 of RR)
Frequency bands of network
Frequency allocation

Conformity with RR
(No. 9.35 of RR)
Frequency allocation
N- A- A- A- A-
N- A- N-
N-
N-
Unfavourable (N-)
if not within allocation

Conformity with RR
(No. 9.35 of RR)
N- N- N- N- N-
N- N- N-
N-
N-
Unfavourable (N-)
if wrong Service or Direction of Transmission

Conformity with RR
(No. 9.35 of RR)
Service area of network
R1R2 R3

Conformity with RR
(No. 9.35 of RR)
If allocation to Region 1 only
R1R2 R3

Conformity with RR
(No. 9.35 of RR)
Unfavourable
(N-)
Favourable
(A-)
R1 R2 R3
Service area is split

Conformity with RR
(No. 9.35 of RR)
Power-flux density
limits (PFD)
Articles 21, 22, footnotes, etc.
EIRP limits
Articles 21, footnotes, etc.
PFD = Power Density + 10log(Ref. Bandwidth) +
G(theta) – 10log(4piR^2) dB(W/m2)
Where G = Gain of transmitting space station
R = Distance from satellite to point on Earth’s surface

Conformity with RR
(No. 9.35 of RR)
Power-flux density
limits (PFD)
EIRP limits GIBC Program v7
(Graphical Interface for Batch Calculations)

Enter Network ID
Select “Hard Limits”
Click Start
Conformity with RR
(No. 9.35 of RR)
PFD (Terrestrial Services)

Conformity with RR
(No. 9.35 of RR)
PFD.LST

Conformity with RR
(No. 9.35 of RR)
PFD.LST
Unfavourable (N-)
Split from groups with Favourable assignments
Fixed beams
Steerable beams

Conformity with RR
(No. 9.35 of RR)
PFD.LST
Favourable (A-)*
Fixed beams
Steerable beams
Unfavourable (N-)
Split from groups with Favourable assignments

Conformity with RR
(No. 9.35 of RR)
*2 Conditions
Provide method to meet PFD limit
&
One location PFD limit is met
(Annex 1 of RoP No. 21.16)
Favourable (A-)*Steerable beams

Conformity with RR
(No. 9.35 of RR)
*2 Conditions
Provide method to meet PFD limit
&
One location PFD limit is met
(Annex 1 of RoP No. 21.16)
Max Excess ≤ 9.5 dB
(C, Ku, Ka-bands FSS GSO)
(Globally steerable but actual value depends on PFD limits)
Source: Rules of Procedure on No. 21.16

Conformity with RR
(No. 9.35 of RR)
Common
Unfavourable Findings
1. EIRP/PFD hard limits exceeded
Check GIBC/PFD results
2. Not in accordance with ToFA
Check frequency bands, direction of
transmission, class of station, service area
3. PFD limits exceeded for steerable
beams and no method provided
Refer to Annex 1 of RoP on No. 21.16

Conformity with RR
(No. 9.35 of RR)
Favourable
frequency
assignments
will proceed …

Coordination
requirements
(No. 9.36 of RR)

Identify any administration
with which coordination
may need to be effected
No. 9.36 of RR

Coordination requirements
(No. 9.36 of RR)
GSO Satellites
Terrestrial
Transmitting
Earth Station
Receiving
Earth Station
Non-GSO
Satellites
Interference

(No. 9.36 of RR)
GSO Satellites
Terrestrial
Transmitting
Earth Station
Receiving
Earth Station
Non-GSO
Satellites
Interference
A30#7.1,
A30A#7.1
9.14,
9.11,
9.21/C
9.12,
9.21/B
9.7
9.7
9.7
9.13,
9.21/B
9.14, 9.11,
9.21/C,
RS539
9.12A,
9.21/A
9.21/A,
9.41
9.21/A
9.21/A,
9.41
A30A#7.1
Forms of
coordination

(No. 9.36 of RR)
GSO Satellites
Terrestrial
Transmitting
Earth Station
Receiving
Earth Station
Non-GSO
Satellites
Interference
A30#7.1,
A30A#7.1
9.14,
9.11,
9.21/C
9.12,
9.21/B
9.7
9.7
9.7
9.13,
9.21/B
9.14, 9.11,
9.21/C,
RS539
9.12A,
9.21/A
9.21/A,
9.41
9.21/A,
9.41
9.21/A,
9.41
GSO vs GSO 9.7
GSO/NGSO vs NGSO 9.11A (9.13, 9.12, 9.12A)
GSO/NGSO vs Terrestrial 9.11A (9.14)
BSS (non-Plan) vs Terrestrial 9.11, RS539
GSO vs Plan A30#7.1, A30A#7.1
Agreement with administrations 9.21
Forms of
coordination

(No. 9.36 of RR)
Forms of
coordination

(No. 9.36 of RR)
Network Summary
Identify forms of coordination
Article 9 & Appendix 5 for criteria
Article 5 footnotes (9.21, 9.11A)
Rules of Procedure (9.11A)
Articles 7 of Appendices 30, 30A
Resolutions 33, 539
Forms of
coordination

(No. 9.36 of RR)
GSO
9.7
9.21/A
RS33#3
9.11
9.14
9.21/C
RS33#2.1
GSO
A30#7.1A30A#7.1
GSO
9.13
9.21/B
9.12
9.12A
9.21/A
9.21/B
NGSO GSO
9.11
9.14
9.21/C
RS33#2.1
NGSO
Identify forms of coordination
Article 9 & Appendix 5 for criteria
Article 5 footnotes (9.21, 9.11A)
Rules of Procedure (9.11A)
Articles 7 of Appendices 30, 30A
Resolutions 33, 539

(No. 9.36 of RR)
Frequency Overlap
with Space Services
Frequency Overlap
with Terrestrial
Services
PFD (Trigger) AP8 PFD (Space)
GIBC
GSO
9.7
9.21/A
RS33#3
9.11
9.14
9.21/C
RS33#2.1
GSO
A30#7.1A30A#7.1
GSO
9.13
9.21/B
9.12
9.12A
9.21/A
9.21/B
NGSO GSO
9.11
9.14
9.21/C
RS33#2.1
NGSO

(No. 9.36 of RR)
Frequency Overlap
with Space Services
Frequency Overlap
with Terrestrial
Services
GSO
9.13
9.21/B
9.12
9.12A
9.21/A
9.21/B
NGSO GSO
9.11
9.14
9.21/C
RS33#2.1
NGSO
GIBC
GSO
9.7
9.21/A
RS33#3
9.11
9.14
9.21/C
RS33#2.1
GSO
A30#7.1A30A#7.1

(No. 9.36 of RR)
(WRC-03)
Enter Network ID
Controls display of
sample DT/T cases
1 - Per administration
2 - Per group
3 - Per assignment
Click Start
Appendix 8

(No. 9.36 of RR)
9.7 Coordination Arc
WRC-12 reduced CA for C & Ku-bands to 8 & 7 degs
9.7 DT/T
9.21/A
RS33 (9.7 for API from 01.01.1999)
A30A#7.1
APP8.LST (cont.)

(No. 9.36 of RR)
A = Recorded in MIFR / Already published
T = Under examination
N = Notification / C = Coordination
C = Network causing interference
R = Network receiving interference
A = Coordination Arc
NTW.LST

(No. 9.36 of RR)
Managing coordination
requirements
Example 1: Organizing Data

(No. 9.36 of RR)
Batchresults.mdb > tr_aff_ntw
Filter or Sort

(No. 9.36 of RR)
Batchresults.mdb > queries
Example: provn

(No. 9.36 of RR)
Batchresults.mdb > queries
Example: com_el + grp + srv_cls + provn

(No. 9.36 of RR)
Managing coordination
requirements
Example 2: “What-if” studies

(No. 9.36 of RR)
Example:
Satellite X
1980 – 31000 MHz
FSS, MSS, BSS
8000+ units
Coordination under No. 9.7
published by BR:
57 affected administrations
1695 affected networks
What-if:
C, Ku-bands
FSS

(No. 9.36 of RR)
Open SRSSpaceCap
Export
Network
Click Start Page,
enter network id

(No. 9.36 of RR)
SpaceCap
Set Target Db
Create a new database
Eg. Satellite Name
Set Options
Keep Group Ids of the Source
Replace Notice in Target

(No. 9.36 of RR)
SpaceCap Open Exported Database
Delete
beams or
groups not to
be included
in “what-if
study”

(No. 9.36 of RR)
GIBC
Select Exported
Database
Tools/Options
Add SRS.mdb

(No. 9.36 of RR)
GIBC
Enter Network ID
Appendix 8
Click Start

(No. 9.36 of RR)
What-if:
C, Ku-bands
FSS
Example:
Satellite X
1980 – 31000 MHz
FSS, MSS, BSS
8000+ units
published by BR:

(No. 9.36 of RR)
GIBC
GSO
9.7
9.21/A
RS33#3
9.11
9.14
9.21/C
RS33#2.1
GSO
A30#7.1A30A#7.1

(No. 9.36 of RR)
Examination: Trigger
Enter
Network ID
Click Start

(No. 9.36 of RR)
9.11, 9.14, 9.21/C

(No. 9.36 of RR)
PFD (Space Services)
Enter
Network ID
Click Start

(No. 9.36 of RR)
A30#7.1
PFD (Space Services)

Conformity
with Radio
Regulations
(No. 9.35)
Coordination
Requirements
(No. 9.36)
C
Coordination
BR IFIC DVD

Network ID
Date of Receipt
Deadline for comments

Summary of affected administrations
for entire network (mandatory)

Summary of affected administrations for
entire network (for info)
Comment within 4 months, else
agreement

Conformity with RR
A-: Favourable
N-: Unfavourable
Forms of coordination

Detailed characteristics
of network

Gain contour & service
area diagrams Align steerable beams
with service area
(provide effective gain
contours 0, -2, -4, -6, -
10, -20 dB)
B.3.b1 of Appendix 4 (WRC-12)

Comments by BR, explanation of
findings

Coordination requirements at group level
9.7 (DT/T) 9.7 (CA)

Other forms of coordination at group level

List of affected networks
Modified by WRC-12,
effective 01.01.2013
Formal

FINAL POINTS
 Use GIBC to check PFD/EIRP
hard limits
 Check conformity with RR
 Use SpaceCap and GIBC for
coordination requirements “what-
if” studies

�ݺ�ߣ

Examination of Coordination Requests

More Related Content

Examination of Coordination Requests