Title: COORDINATION OF SATELLITE NETWORKS Presented by Avram Sion avram'sionitu'int BRSSDSSC
1COORDINATION OF SATELLITE NETWORKSPresented by
Avram Sion(avram.sion_at_itu.int)BR/SSD/SSC
BR Radiocommunications Seminar Geneva, November
2002
2- PROPAGATION OF RADIO WAVES - laws of physics
- Radio waves do not stop at national borders
- INTERFERENCE - possible between radio stations
of different countries - This risk is high in Space Radiocommunications
- RADIO REGULATIONS One of its main purposes
- Interference-free operation of RadioComms
3INTERFERENCE
TERRESTRIAL STATION
4RR MECHANISMS TO CONTROL INTERFERENCE ALLOCATION
Frequency separation of stations of
different services REGULATORY PROTECTION
e.g. No. 22.2 Non-GSO to protect GSO (FSS
and BSS) POWER LIMITS - PFD - to protect TERR
services - EIRP - to protect SPACE
services - EPFD - to protect GSO from
Non-GSO and
5INTERFERENCE
TERRESTRIAL STATION
6INTERFERENCE
RECEIVING EARTH STATION
TRANSMITTING EARTH STATION
7and COORDINATION
- Obligatory NEGOTIATION
- between Administrations
- to arrive at interference-free operation
- Process and Procedure described in RR
8PROVISIONS OF RADIO REGULATIONS
- PLANNED SERVICES Broadcasting satellite
service (Appendices 30 and 30A)
Fixed-satellite service (Appendix 30B) - NON-PLANNED SERVICES Coordination and
Notification procedures
9ADVANCE PUBLICATION OF INFORMATION
Central part of a 3-stage process
COORDINATION
RECORDING IN MIFR
10ADVANCE PUBLICATION OF INFORMATION
Submit, Publish
Request, Examine, Establish Findings
Coordination Requirements, Publish, Coordinate
COORDINATION
RECORDING IN MIFR
Notify, Examine, Check Coordination Agreements,
Record
11PROCEDURES APPLICABLE TO NON-PLANNEDSATELLITE
NETWORKS
- ARTICLE 9
- Procedure for Effecting Coordination with or
Obtaining Agreement of other Administrations
12 WRC-95, -97, -2000 SIMPLIFIED COORDINATION
PROCEDURE Article 9 contains (almost) all cases
of coordination in non-planned bands for GSO and
N-GSO networks, earth and terrestrial stations
(previously Articles 11, 14 and
Resolutions 33, 46)
13INTERFERENCE
TERRESTRIAL STATION
14REGULATORY PROCEDURES APPLICABLE TONON-PLANNED
SPACE SERVICES
Applies for all satellitenetworks except for
those to be operated in accordance with a Plan
i.e. App. 30, 30A 30B
ADVANCE PUBLICATION Art. 9,Section I,
Sub-Sections IA and IB
REQUEST AGREEMENT Art. 9/9.21 Ap4/II or III
REQUEST COORDINATION
Ap4/II
GEO only
GEO Non-GEO
GEO Non-GEO
Applies only in certain bands services
Non-GEO v. Non-GEO, GEO,
TERR GEO v. Non-GEO,TERR 9.11A (12, 12A, 13, 14)
GEO v. GEO Art. 9/9.7 Res. 33/II
BSS v. TERR 9.11 Res. 33/I
Non-GEO
NOTIFICATION Art. 11 Res. 33
RECORDING IN MIFR
15ADVANCE PUBLICATION OF INFORMATIONON SATELLITE
NETWORKS(Section I of Article 9)
- Aim is to inform all administrations of any
planned satellite network (GSO or N-GSO) and its
general description - Formal mechanism for making initial assessment of
the interference effects of that planned
satellite network
16ADVANCE PUBLICATION (1) Section I has two
sub-sections
- 1A Advance publication of information on
satellite systems that are NOT subject to
coordination procedure under Section II of
Article 9 - 1B Advance publication of information on
satellite systems that are SUBJECT to the
coordination procedure under Section II of
Article 9
17ADVANCE PUBLICATION (2)
- Information to be communicated to the BR AP4
(Forms of notice APS4/V and APS4/VI) - To be initiated 2- 5 years before the planned
date of bringing into use of the network (or
system) - 9.1 - BR publishes Special Section API/A
18(No Transcript)
19(No Transcript)
20ADVANCE PUBLICATION (3)
- API phase is obligatory, before coordination
phase or notification - No priority in being first to start advance
publication
21ADVANCE PUBLICATION (4)
- Must be re-started
- for new frequency band(s)
- for a change of GSO orbital location by gt12
degrees
22 COORDINATION OF SATELLITE NETWORKS
- Section II, Article 9
- Procedure for effecting coordination
- Contains almost all cases of coordination for
non-planned satellite networks (GSO and N-GSO),
earth and terrestrial stations
23COORDINATION CASES Not in Art.9 Article 7 of
Appendix 30 Non-planned FSS or BSS w.r. to
BSS Plan Article 7 of Appendix 30A Non-planned
FSS of BSS w.r. to Feeder Link Plan Resolution
77 (WRC-2000) FSS w.r. to Terrestrial
Services (11.7-12.2 GHz) Resolution 84 (WRC-2000)
FSS w.r. to Terrestrial Services in R2
(37.5-40 GHz)
24COORDINATION (2)
- Procedure for coordination of GSO and Non-GSO
satellite network - Article 9 shall be applied for coordination of
GSO and N-GSO networks in the following cases
25COORDINATION (3)
- Between GSO networks - 9.7
- Between GSO and N-GSO and between N-GSO
networks (in accordance with a footnote in the
Table) - 9.12, 9.12A, 9.13 - Space station of a satellite network w.r. to
stations of terrestrial services where threshold
value is exceeded - 9.14
26COORDINATION (4)
-
- space station in the BSS (non-planned) with
respect to terrestrial services - -
9.11/Res. 33 - any station of a space service for which the
requirement to seek the agreement of other
administrations is included in a footnote to the
Table - 9.21
27COORDINATION (5)
- in all these cases, request for coordination
shall be sent by the requesting administration to
the BR together with the appropriate information
listed in Ap4 (9.30) - simultaneous request for all applicable forms of
coordination (9.23)
28COORDINATION (6)
- date of receipt of the coordination request must
be gt six months after the date of receipt of API
(9.1) - request for coordination must come within 24
months after the date of receipt of the advance
information, otherwise restart API (9.5D)
29COORDINATION (7)Action of the BR
- The Bureau examines coordination requests (if
complete) for conformity with - the Table of Frequency Allocations 9.35
- other provisions of the RR 9.35
(e.g. compliance with PFD limits) - The BR identifies, in accordance with Ap5 , any
administration with which coordination may need
to be effected 9.36
30COORDINATION (8)
- Appendix 5
- Identification of administrations with which
coordination is to be effected or agreement
sought under the provisions of Article 9 - Ap5 contains criteria for identification of
assignments to be taken into account in effecting
coordination or seeking agreement
31COORDINATION (9)
- Methods, threshold levels and conditions given
in Tables 5-1 and 5-2 differ according to the
specific cases of coordination (GSO/GSO,
GSO/N-GSO, GSON-GSO with respect to terrestrial
services)
32COORDINATION (10)
- GSO/GSO
- criterion DeltaT/Tgt6, method of
- calculation
in Ap8 - Coordination Arc GSO FSS in certain
- frequency
bands - List of ADMINISTRATIONS
- List of NETWORKS, for information
33COORDINATION (11)
- The BR publishes the information (network
data) in a Special Section of its IFIC, on
CD-ROM, fortnightly since 2000, as well as the
results of its examination, i.e. findings,
coordination requirements (list of ADMINS), list
of networks (for information, where appropriate)
34(No Transcript)
35(No Transcript)
36(No Transcript)
37(No Transcript)
38BR COMMENTS - Findings with respect to
No.9.35/11.31
1. For frequency assignments in the 12.5-12.7
GHz band 1.1 UNFAVOURABLE for all frequency
assignments in transmitting space station beams
ETH and ETV with maximum power density greater
than or equal to 55.8 dBW/Hz (p.f.d. limits of
21.16 are exceeded).
39BR COMMENTS - Findings with respect to
No.9.35/11.31
- 1.2 UNFAVOURABLE for frequency assignment 12.5
GHz in transmitting space station beam UPC
(out-of-band). - 1.3 FAVOURABLE for all other frequency
assignments.
40BR COMMENTS Coordination Requirements (No.9.36)
- Applicable forms of COORD (CR/C, page 1)
- Summary of COORD Requirements per provision
List of Admins (CR/C, p. 2) - (Last part of CR/C)
- Detailed COORD requirements (Admins) for each
group of frequency assignments - List of networks identified (for info only)
41COORDINATION (12)
- The list of
- administrations identified by the BR under 9. 11
to 9.14 and 9.21 - networks identified by the BR under 9.7/9.27
- are only for information purposes (to help
administrations comply with procedures) - 9.36.1,
9.36.2
42COORDINATION (13)
- The list of ADMINs identified under S9.7, as a
result of Coordination Arc or DeltaT/T, is the
formal list of administrations with which
coordination is required - Coordination Arc results 9.41/9.42, inclusion,
exclusion (4 months) - Four months for comments
43COORDINATION (14)
- For coordination requests under 9.11 to 9.14 and
9.21, the BR shall, 45 days prior to the expiry
of the four-month period, dispatch a circular
telegram to all administrations bringing the
matter for their attention and 30 days later a
reminder (9.52D)
44COORDINATION (15) Action by administrations
- An administration having received a request for
coordination shall examine the matter with
respect to interference which may be caused to,
or caused by, its own assignments
45COORDINATION (16) Action by administrations
- inform the requesting administration and the BR
within four months from the date of publication
of the IFIC of either - its agreement to the proposal, or
- the disagreement, giving pertinent details upon
which the disagreement is based
46COORDINATION (17) Action by administrations
- For coordination requests under 9.11 (Res. 33,
w.r. to terrestrial services), 9.12 to 9.14 and
9.21, the absence of response within the 4-month
period means agreement (9.52C)
47COORDINATION (18) Res. 33 (Rev. WRC-97)
- Procedure applicable to non-planned BSS is
included in Article 9. However, WRC-97 decided
that for satellite networks for which advance
information requests were received prior to
01.01.1999 - Resolution 33 applies. If advance
information was received after 01.01.99 9.11
applies
48COORDINATION (19)
- Coordination is a regulatory obligation
- for the administration wishing to assign a
frequency to a station - for any other administration whose services might
be affected. (9.53) - The agreement resulting from the coordination
involves certain legal rights and obligations.
49COORDINATION (20)
- Coordination is to be effected in accordance with
RR procedures and on the basis of criteria
established by the RR or agreed to between
administrations
50Extension of the date of bringing into use of
frequency assignments to space networks
- 9.1 Advance publication procedure shall be
initiated not earlier than 5 years before the
planned date of bringing into use of the network.
51Extension (2)
- 11.44 The notified date of bringing into use of
any frequency assignment to a space station shall
be not later than 5 years following the date of
receipt by the BR of the relevant information
under 9.1.
52Extension (3)
- 11.44 The notified date of bringing into use may
be extended by not more than 2 years, only under
conditions specified in Nos. 11.44B to 11.44I. - That is, a maximum of 7 years from the date of
receipt of API.
53Extension (4)
- 11.44B The notified date of bringing into use
will be extended by the Bureau in accordance with
No. 11.44 if due diligence information required
by Resolution 49 is provided for the satellite
network if the procedure for effecting
coordination in accordance with Section II of
Article 9 (if applicable) has commenced and if
the notifying administration certifies that the
reason for the extension is one or more of the
following specific circumstances
54Extension (5)
- 11.44C a) launch failure
- 11.44D b) launch delays due to circumstances
outside the control of the administration or
operator - 11.44E c) delays caused by modifications of
satellite design necessary to reach coordination
agreements - 11.44F d) problems in meeting the satellite
design specifications - 11.44G e) delays in effecting coordination after
the assistance of the Bureau was requested under
No. 9.59 - 11.44H f) financial circumstances outside the
control of the administration or the operator or - 11.44I g) force majeure.
55Extension (6)
- Res. 51 (WRC-2000)
- Transitional arrangements relating to the API
and coordination of satellite networks - Resolves - For satellite networks for which API
had been received by the BR prior to 22.11.97,
the maximum allowed time period to bring
frequency assignment into use shall be 6 years
plus the extensions pursuant to RR1550 from the
date of publication of the API.
56Due Diligence (Administrative)
- Resolution 49 to address the problem of
reservation of orbit and spectrum capacity
without actual use (Res. 18 of Kyoto
Plenipotentiary) - Application for any satellite network in the
FSS, MSS, BSS subject to coordination from
22.11.97
57Due Diligence (2)Due Diligence information
required
- Annex 2 to Resolution 49
- A. Identity of the satellite network
- B. Spacecraft manufacturer
- C. Launch services provider
58Annex 2 to Resolution 49 A. Identity of the
satellite network
- a) Identity of the satellite network
- b) Name of the administration
- c) Country symbol
- d) Reference to the advance publication
information or to the request for modification of
the Plans in Appendices 30 and 30A
59Annex 2 to Resolution 49
- e) reference to the request for coordination
- f) Frequency band(s)
- g) Name of the operator
- h) Name of the satellite
- I) Orbital characteristics
60Annex 2 to Resolution 49 B. Spacecraft
manufacturer
- a) Name of the spacecraft manufacturer
- b) Date of execution of the contract
- c) Contractual delivery window
- d) Number of satellites procured
61Annex 2 to Resolution 49 C. Launch services
provider
- a) Name of the launch vehicle provider
- b) Date of execution of the contract
- c) Anticipated launch or in-orbit delivery window
- d) Name of the launch vehicle
- e) Name and location of the launch facility
62Due Diligence (3)
- Six months before expiry of the notified period
of bringing into use, the BR sends a reminder. - If the complete due diligence information is not
received within the specified time limit, the
network shall no longer be taken into account and
shall not be recorded in the Master Register.
63COORDINATION REQUEST PROCESSING
64COORDINATION REQUEST PROCESSING
Capture network data in .MDB and .GXT format,
Validate, Submit to BR
Administration
Receivability, as-received publication,
pre-validate, 2D-date, prepare, validate
BR
SNS GIMS DataBase Ready for Examination
BR
65COORDINATION REQUEST PROCESSING
BR
Examination
Table of Frequency Allocation
Other provisions of RR (PFD)
9.35
Split Groups of Frequency Assignments
Forms of Coordination
Findings, Enter them
A, B, N
RoP 9.35
66GROUP OF FREQUENCY ASSIGNMENTS
Orbital Position Beam Assigned Bandwidth Service
(CoS) Assigned Frequency Emission/Power (Data
Elements) Assignments
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
1
1
1
2
2
1
1
1
2
2
2
16
6
1
2
3
4
4 in a group
10 50000 in one network
67GROUP SPLITTING Re-GROUPING
Orbital Position Beam Assigned Bandwidth Service
(CoS) Assigned Frequency Emission/Power Assignmen
ts
1
1
1
1
2
1
1
2
4 in a group
68GROUP SPLITTING Re-GROUPING
Orbital Position Beam Assigned Bandwidth Service
(CoS) Assigned Frequency Emission/Power Assignmen
ts
1
1
1
A
N
1
1
1
1
1
1
1
1
1
2
2
1
1
1
1
1
2
2
2
COORD
NO COORD
4 in a group
2 in a group
2 in a group
69COORDINATION REQUEST PROCESSING
BR
Examination
Table of Frequency Allocation
Other provisions of RR (PFD)
9.35
Split Groups of Freq. Assign.
Forms of Coordination
Findings, Enter them
A, B, N
RoP 9.35
70COORDINATION REQUEST PROCESSING
9.36
Examination (Cont)
BR
Forms of Coordination
9.7, 9.7A, 9.7B, 9.11, RS33, 9.11A, 9.12, 9.12A,
9.13, 9.14, 9.21/A, 9.21/B, 9.21/C, Ap30/Art.7,
Ap30A/Art.7, RS77, RS84
Software Tools for Coordination Requirements
.mdb .mdb .mdb .mdb .mdb
.MDB
SNS
71COORDINATION REQUEST PROCESSING
SNS
Publication
CR/C Special Section
72COORDINATION REQUEST PROCESSING
CR/C Special Section Final Coordination
Requirements Potentially Affected Administrations
(only for info under 9.36.1) Only Admins that,
within 4-months, inform of disagreement under
9.52, enter coordination. Others are considered
to have agreed !!!
W.R. to SPACE 9.7, RS333, 9.7A, 9.7B A307.1,
A30A7.1 9.11A 9.12, 9.12A, 9.13 9.21 9.21/A,
9.21/B CR/D
W.R. TERR RS77, RS84 9.11/RS332.1 9.11A/9.14 9.
21-9.21/C CR/D
73COORDINATION REQUEST PROCESSING
SNS
CR/D
Publication
BR
IFIC.mdb
CR/C Special Section
ADMIN
74INTERFERENCE
QUESTIONS ?
TERRESTRIAL STATION