Title: COORDINATION OF SATELLITE NETWORKS
1COORDINATION OF SATELLITE NETWORKS
Yvon Henri yvon.henri_at_itu.intRadiocommunication
BureauITU
2INTERFERENCE
3PROVISIONS OF RADIO REGULATIONS
- PLANNED SERVICESBroadcasting satellite service
(Appendices S30 and S30A)Fixed-satellite
service(Appendix S30B) - NON-PLANNED SERVICESCoordination and
notification procedures
4REGULATORY PROCEDURES APPLICABLE TO NON-PLANNED
SPACE SERVICES
ADVANCE PUBLICATION Art. S9,Section I,
Sub-Sections IA and IB ApS4/V and VI
Applies for all satellitenetworks except for
those to be operated in accordance with a Plan
i.e. App. S30, S30A S30B
REQUEST AGREEMENT Art. S9/S9.21 ApS4/II or III
REQUEST COORDINATION
ApS4/II
GEO only
GEO Non-GEO
GEO Non-GEO
Non-GEO v. Non-GEO, GEO,
TERR GEO v. Non-GEO,TERR S9.11A (12, 12A, 13,
14)
Applies only in certain bands services
GEO v. GEO Art. S9/S9.7 Res. 33/II
BSS v. TERR S9.11 Res. 33/I
Non-GEO
NOTIFICATION Art. S11 Res. 33 ApS4/II or III
RECORDING IN MIFR
5PROCEDURES APPLICABLE TO SATELLITE SYSTEMS IN
NON-PLANNED SERVICES
- ART. S9
- Procedure for Effecting Coordination with or
Obtaining Agreement of other Administrations
6 WRC-95, 97 SIMPLIFIED COORDINATION
PROCEDURE Article S9 contains all cases of
coordination in non-planned bands for GSO and
N-GSO networks, earth and terrestrial stations
(previously Articles 11, 14, Resolutions 33, 46
and Article 7 of AP30 and AP30A)
(WRC-2000)
7ADVANCE PUBLICATION OF INFORMATION ON SATELLITE
SYSTEMS (OR NETWORKS)(Section I of Article S9)
- Aim is to inform all administrations of any
planned satellite system (GSO or N-GSO) and the
general description of the system (or network) - Formal mechanism for making initial assessment of
the effect of the planned satellite network
8ADVANCE PUBLICATION (2)
- Res. 51 (WRC-97) Res. 51 (WRC-2000)
- Resolves 1 Provisions of Sections 1, 1A and 1B
of Article S9 and some provisions of Art. S11
shall be applied on a provisional basis as from
22.11.97 - Resolves 4 The revised APS4 with respect to the
API for satellite networks which are subject to
coordination shall be applied as from 22.11.97
9ADVANCE PUBLICATION (3) 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 the
Article - 1B Advance publication of information on
satellite systems that are subject to the
coordination procedure under Section II
10ADVANCE PUBLICATION (4)
- Information to be communicated to the BR APS4
(Forms of notice APS4/V and APS4/VI BR Circular
letter CR/86 of 25.03.98) - To be initiated 2- 5 years before the planned
date of bringing into use of the network (or
system)-S9.1 - BR publishes Special Section API/A
- four months for comments
11(No Transcript)
12(No Transcript)
13COMMENTS OF RADIOCOMMUNICATION BUREAU RELATING TO
THE SPECIAL SECTION NUMBERING
- 1. The advance publication procedure of Section
I of the Annex I to Res. 46 is also required with
respect to the following frequency bands 18.9 -
19.6 GHz - 28.7 - 29.4 GHz
- 2. Paragraph 3.1 of Resolution 33 of
- WARC-79 is applicable to the following frequency
band 21.4 - 21.9 GHz -
14ADVANCE PUBLICATION (5)
- Progress report 4 months after publication (for
satellite networks not subject to further
coordination) - BR publishes AR11/B Sp. Section
- API phase is obligatory, before coordination
phase or notification - No priority in being first to start advance
publication
15ADVANCE PUBLICATION (6)
- Must be re-started
- for new frequency band(s)
- for a change of GSO orbital location
- by gt12 degrees
16 COORDINATION OF SATELLITE NETWORKS
- Section II, Article S9
- Procedure for effecting coordination
- Contains all cases of coordination in non-planned
bands of satellite systems (GSO and N-GSO), earth
and terrestrial stations (Article 11 Sections
II, III, IV, Article 14, Resolutions 33, 46 and
Article 7 of AP30, AP30A)
17COORDINATION (2)
- Procedure for coordination of GSO and Non-GSO
satellite network - (Section II of Article 11, Article 14,
Resolutions 33, 46 and Article 7 of AP30, AP30A) - Article S9 shall be applied for coordination of
GSO and N-GSO networks in the following cases
18COORDINATION (3)
- GSO networks w.r. to other GSO networks (in
non-planned bands) - S9.7 - between GSO and N-GSO and between N-GSO networks
(in accordance with a footnote in the Table) -
S9.12, S9.12A and -
S9.13 - space station of a satellite network w.r. to
stations of terrestrial services where the
threshold value is exceeded - S9.14
19COORDINATION (4)
- transmitting GSO space station in the FSS w.r. to
stations of the BSS and FL in the BSS (APS30,
APS30A) - S9.8 and S9.9 - space station in the BSS (non-planned) with
respect to terrestrial services - S9.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 - S9.21
20COORDINATION (5)
- in all these cases requests for coordination
shall be sent by the requesting administration to
the BR together with the appropriate information
listed in APS4 (S9.30) - simultaneous request for all required
coordinations (S9.23)
21COORDINATION (6)
- date of receipt of the coordination request must
be gt six months after the date of receipt of API
(S9.1) - request for coordination shall be received by the
BR within 24 months after the date of receipt of
the advance information (S9.5D)
22COORDINATION (7)Action of the BR
- The Bureau examines coordination requests (if
complete) for conformity with - the Table of Frequency Allocations
- other provisions of the RR (e.g.
- compliance with PFD limits)
- The Bureau identifies, in accordance with ApS5 ,
any administration with which coordination may
need to be effected
23COORDINATION (8)
- APS5
- Identification of administrations with which
coordination is to be effected or agreement
sought under the provisions of Article S9 - APS5 contains criteria for identification of
assignments to be taken into account in effecting
coordination or seeking agreement
24COORDINATION (9)
- Methods, threshold levels and conditions given
in Tables S5-1 and S5-2 differ according to the
specific cases of coordination (GSO/GSO,
GSO/N-GSO, GSON-GSO with respect to terrestrial
services)
25COORDINATION (10)
- GSO/GSO
- criterion DeltaT/Tgt6, method of
- calculation
in ApS8 - Coordination Arc GSO FSS in certain
- frequency
bands - List of ADMINs, and a list of
- NETWORKS for information
26COORDINATION (11)
- The BR publishes the information (network
data) in a Special Section of its Weekly Circular
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)
27(No Transcript)
28RADIOCOMMUNICATION BUREAU COMMENTS
Relating to the Administrations to which the
request for coordination has been addressed under
RR1073 J, RUS, SNG, THA, USA/IT Relating to the
examination with respect to RR1077 Coordination
is also required with the following
Administrations BLK/IK, CHN, G, INS, LAO, MLA,
PHL, UAE
29RADIOCOMMUNICATION BUREAU COMMENTS
Relating to the examination with respect to
RR1077 Coordination is also required with the
following Administrations Coordination
Arc BLK/IK, G, INS, MLA, UAE DeltaT/T CHN, G,
INS, LAO, MLA, PHL, UAE List of ADMs for each
group Network list
30Relating to the Finding with respect to RR1503
1. For frequency assignments in the 12.5-12.7
GHz band 1.1 UNFAVOURABLE for all frequency
assignments to the transmitting space station
beams ETH and ETV with maximum power density
greater than or equal to 55.8 dBW/Hz (the p.f.d.
limits of S21.16 are exceeded).
31Relating to the Finding with respect to RR1503
- 1.2 UNFAVOURABLE for frequency assignment 12.5
GHz to the transmitting space station beam UPC
(out-of-band). - 1.3 FAVOURABLE for all other frequency
assignments.
32COORDINATION (12)
- The list of
- administrations identified by the BR under S9. 11
to S9.14 and S9.21 - networks identified by the BR under S9.7/S9.27
- are only for information purposes (to help
administrations comply with procedures) -
S9.36.1, S9.36.2
33COORDINATION (13)
- The list of ADMINs identified under S9.7 to S9.9,
as a result of DeltaT/T, is the formal list of
administrations with which coordination is
required. - Coordination Arc results S9.41, inclusion,
exclusion (4 months) - Four months for comments
34COORDINATION (14)
- For coordination requests under S9.12 to S9.14
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
(S9.52D)
35COORDINATION (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 in certain cases caused by, its own assignments
36COORDINATION (16) Action by administrations
- notify 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 disagreement is based
37COORDINATION (17) Action by administrations
- For coordination requests under S9.11 (Res. 33,
w.r. to terrestrial services), S9.12-S9.14 and
S9.21, the absence of response within a four
month period means agreement (S9.52C)
38COORDINATION (18) Res. 33 (Rev. WRC-97)
- Procedure applicable to BSS in non-planned bands
is included in Art S9. However, WRC-97 decided
that for satellite networks for which advance
information or coordination requests were
received prior to 01.01.99 - Res. 33 applies. If
advance information or coordination requests are
received after 01.01.99 - Art. S9 applies.
39COORDINATION (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. (S9.53) - The agreement resulting from the coordination
involves certain legal rights and obligations.
40COORDINATION (20)
- Coordination must be effected in accordance with
RR procedures and on the basis of the criteria
established by the RR or agreement between
administrations.
41Extension of the date of bringing into use of
frequency assignments to space networks
- The previous RR
- The notified date of bringing into use of the
first assignment of a satellite network shall not
be later than six years from the date of API
publication. This date will be extended at the
request of the administration by no more than
three years. (RR1550)
42Extension (2)
- S9.1 Advance publication procedure shall be
initiated not earlier than 5 years before the
planned date of bringing into use of the network. - S11.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 S9.1.
43Extension (3)
- S11.44 The notified date of bringing into use may
be extended by not more than 2 years, only under
conditions specified under S11.44B to S11.44I. - That is, a maximum of 7 years from the date of
receipt of API.
44Extension (4)
- S11.44B The notified date of bringing into use
will be extended by the Bureau in accordance with
No. S11.44 if due diligence information required
by Res.49(WRC-97) is provided for the satellite
network if the procedure for effecting
coordination in accordance with Section II of
Article S9 as applicable has commenced and if
the notifying administration certifies that the
reason for the extension is one or more of the
following specific circumstances
45Extension (5)
- S11.44C a) launch failure
- S11.44D b) launch delays due to circumstances
outside the control of the administration or
operator - S11.44E c) delays caused by modifications of
satellite design necessary to reach coordination
agreements - S11.44F d) problems in meeting the satellite
design specifications - S11.44G e) delays in effecting coordination after
the assistance of the Bureau was requested under
No. S9.59 - S11.44H f) financial circumstances outside the
control of the administration or the operator or - S11.44I g) force majeure.
46Extension (6)
- Res. 51 (WRC-97) Res. 51 (WRC-2000)
- Provisional application of certain provisions
of the RR as modified by the WRC-97 and
transitional arrangements. - Resolves 3 For satellite networks for which API
has been received by the BR prior to 22/11/97,
the maximum allowed time period of bringing the
relevant frequency assignment into use shall be 6
years plus the extensions pursuant to RR1550 from
the date of the receipt publication of the API.
47Due Diligence (Administrative)
- Res. 49 (Rev. WRC-2000) 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 and MOD BSS
APS30/S30A plans and APS30B add. Uses from
22.11.97
48Due Diligence (2)Due Diligence information
required
- Annex 2 to Resolution 49 (Rev. WRC-2000)
- A. Identity of the satellite network
- B. Spacecraft manufacturer
- C. Launch services provider
49Annex 2 to Resolution 49(Rev. WRC-2000)
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 S30 and S30A
50Annex 2 to Resolution 49(Rev. WRC-2000)
- e) reference to the request for coordination
- f) Frequency band(s)
- g) Name of the operator
- h) Name of the satellite
- I) Orbital characteristics
51Annex 2 to Resolution 49(Rev. WRC-2000)
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
52Annex 2 to Resolution 49(Rev. WRC-2000) 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
53Due Diligence (3)
- Six months before expiry of the notified period
and if the administration has not submitted the
due diligence information 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.
54INTERFERENCE