04-Coordination of Satellite Networks MG - TT · SIMPLIFIED COORDINATION PROCEDURE Article 9 contains ... COORDINATION (9) Appendix 5: ... API and coordination of satellite networks

Coordination ofCoordination ofSatellite NetworksSatellite Networks

Mark GriffinSpace Services Department

ITU Radiocommunication Bureau (BR)

Bangkok, Thailand28 -30 September 2010

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

TRANSMITTINGEARTH STATION

RECEIVINGEARTH STATION

INTERFERENCE

TERRESTRIAL STATION

RR 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 from Space services

- EIRP - to protect SPACE from Terr services

- EPFD - to protect GSO from Non-GSO

and…

……andand COORDINATIONCOORDINATION

Obligatory NEGOTIATIONObligatory NEGOTIATIONbetween Administrationsbetween Administrationsto arrive at interferenceto arrive at interference--free operationfree operation

Process and Procedure described in RRProcess and Procedure described in RR

PROVISIONS OF RADIO PROVISIONS OF RADIO REGULATIONSREGULATIONS

PLANNED SERVICESPLANNED SERVICESBroadcasting satellite service Broadcasting satellite service

(Appendices 30 and 30A)(Appendices 30 and 30A)FixedFixed--satellite service (Appendix 30B)satellite service (Appendix 30B)

NONNON--PLANNED SERVICESPLANNED SERVICESCoordination and Coordination and

Notification proceduresNotification procedures

ADVANCE PUBLICATION OF

INFORMATION

COORDINATION

RECORDING

IN MIFR

Central part of a

3-stage process

ADVANCE PUBLICATION OF

INFORMATION

COORDINATION

RECORDING

IN MIFR

Request, Examine, Establish Findings & Coordination Requirements, Publish, Coordinate

Submit, Publish, Inform

Notify, Examine, Check Coordination Agreements, Record

PROCEDURES APPLICABLE TO PROCEDURES APPLICABLE TO NONNON--PLANNEDPLANNED

SATELLITE NETWORKSSATELLITE NETWORKS

ARTICLE 9 ARTICLE 9

Procedure for:Procedure for:effecting Coordination with / obtaining effecting Coordination with / obtaining Agreement of other AdministrationsAgreement of other Administrations

WRC-95, -97, -2000, -03, -07

SIMPLIFIED COORDINATION PROCEDURE

Article 9 contains (almost) all cases of coordination in non-planned bands for:

- GSO and Non-GSO satellite networks - earth and terrestrial stations

(previously Articles 11, 14 and Resolutions 33, 46)

ADVANCE PUBLICATION OF ADVANCE PUBLICATION OF INFORMATIONINFORMATION

ON SATELLITE NETWORKSON SATELLITE NETWORKS(Section I of Article 9)(Section I of Article 9)

–– Aim is to inform all administrations of a Aim is to inform all administrations of a contemplated satellite network (GSO or Noncontemplated satellite network (GSO or Non--GSO) GSO)

–– Formal mechanism to initially assess Formal mechanism to initially assess interference effects of that satellite networkinterference effects of that satellite network

ADVANCE PUBLICATION (1) ADVANCE PUBLICATION (1)

1A:1A: API for satellite systems API for satellite systems NOT SUBJECT TO COORDINATIONNOT SUBJECT TO COORDINATIONprocedure under Section II of Article 9procedure under Section II of Article 9

1B:1B: API for satellite systems API for satellite systems SUBJECT TO COORDINATIONSUBJECT TO COORDINATION

procedure under Section II of Article 9procedure under Section II of Article 9

RR Article 9 Section I has two sub-sections

ADVANCE PUBLICATION (2)ADVANCE PUBLICATION (2)

Information to be communicated to the BR: Information to be communicated to the BR: →→ Appendix 4Appendix 4

To be initiated: 2 To be initiated: 2 -- 7 years before the 7 years before the planned date of bringing into use of the planned date of bringing into use of the network (or system) network (or system) –– No.9.1No.9.1

BR publishes Special Section BR publishes Special Section API/AAPI/A

Space Regulatory Workshop, Bangalore, India, 25-29 June 2007



API phase is obligatory, before API phase is obligatory, before coordination phase or notificationcoordination phase or notification

No priority in being first to start API No priority in being first to start API procedureprocedure

Starts the regulatory clock !Starts the regulatory clock !


API must be reAPI must be re--started:started:

for new frequency band(s)for new frequency band(s)

for a change of GSO orbital location by > 6 for a change of GSO orbital location by > 6 degreesdegrees

If no CR within 24 months from API receiptIf no CR within 24 months from API receipt

COORDINATION OF COORDINATION OF SATELLITE NETWORKSSATELLITE NETWORKS

Section II, Article 9Section II, Article 9““Procedure for effecting coordinationProcedure for effecting coordination””

Contains Contains (almost)(almost) all cases of all cases of coordination for noncoordination for non--planned satellite planned satellite networks (GSO and Nonnetworks (GSO and Non--GSO), earth and GSO), earth and terrestrial stations terrestrial stations

COORDINATIONCOORDINATION (2)(2)

Procedure for coordination of GSO Procedure for coordination of GSO and Nonand Non--GSO satellite networkGSO satellite network

Article 9Article 9 is to be applied for is to be applied for coordination of GSO and Noncoordination of GSO and Non--GSO GSO networks in the following cases:networks in the following cases:

• Between GSO networks - 9.7 • Between GSO and Non-GSO and between

Non-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 (in accordance with a footnote in the Table)where threshold value is exceeded - 9.14


• space station in the BSS (non-planned) with respect to terrestrial services -

- 9.11 (Res.539)• 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


COORDINATION CASES – Not in Art.9

Non-planned FSS or BSS w.r. to BSS Plan:Procedure contained in: Art. 7 of Appendix 30

Non-planned FSS of BSS w.r.to Feeder Link Plan:Procedure contained in: Art. 7 of Appendix 30A

Non-GSO BSS at 2.6 GHz w.r.to terr. services:Res.539 – resolves 2, “Furthemore”, first indent

FORMS OF COORDINATION APPLICABLE TO NONFORMS OF COORDINATION APPLICABLE TO NON--PLANNED SPACE SERVICESPLANNED SPACE SERVICES

ADVANCE PUBLICATION

Art. 9,Section I, Sub-Sections IB and IA

REQUESTAGREEMENT

Art. 9/9.21

GSO v. GSOArt. 9/9.7

(Res. 33/B)

Non-GSO v. Non-GSO,GSO, TERR

GSO v. Non-GSO,TERR9.11A (12, 12A, 13, 14)

NOTIFICATION andRECORDING IN MIFR

Art. 11

MIFR

Applicable only to certain servicesor bands(Footnotes to ToFA)

GSO only GSO & Non-GSO

Non-GSOREQUEST for COORDINATION

Data: Specified in Ap4

BSS v. TERR9.11

(Res. 33/A)

GSO & Non-GSO

Art. 7Ap30

Ap30A

GSO only

RRArt. 9

Ap30,Ap30A

Apply to all satellite networks except for those to be opeApply to all satellite networks except for those to be operated in & 30Brated in & 30B


Earliest date of receipt of the Earliest date of receipt of the coordination request: 6 months after the coordination request: 6 months after the date of receipt of API (9.1)date of receipt of API (9.1)However, request for coordination must However, request for coordination must come come within 24 months after the date of within 24 months after the date of receipt of the API,receipt of the API, otherwise restart API otherwise restart API (No.9.5D)(No.9.5D)


-- The Bureau examines coordination requests (if The Bureau examines coordination requests (if complete) for complete) for conformity withconformity with::

–– the the Table of Frequency Allocations: No. 9.35Table of Frequency Allocations: No. 9.35–– other provisionsother provisions of the RR: of the RR: No.9.35No.9.35

(e.g. compliance with PFD limits)(e.g. compliance with PFD limits)

-- The BR identifies, in accordance with Ap5 , any The BR identifies, in accordance with Ap5 , any administration with which coordination may administration with which coordination may need to be effected: No.9.36need to be effected: No.9.36

Actions of the BRActions of the BR

COORDINATION (8)“Identification of administrations with which coordination is to be effected

or agreement sought

Appendix 5Appendix 5contains criteria for identification of assignments to be taken into account in effecting coordination or seeking agreement

COORDINATION (9)Appendix 5: Space assignments to be taken into

account are those that meet all of the following:

- already started coordination or are recorded in

MIFR

- comply with RR (favourable @ No.11.31)- have frequency overlap- thresholds (if any) are exceeded

COORDINATION (10)Appendix 5: Terrestrial assignments to be taken

into account are those that meet all of the following:

- recorded in MIFR, or brought into use,or planned to be in use within 3 years;

- comply with RR (favourable @ 11.31);- have frequency overlap;- thresholds (if any) are exceeded.


Methods, Methods, threshold levelsthreshold levels and and conditions given in conditions given in Tables 5Tables 5--1 and 51 and 5--22 are are applicable to the specific cases (forms) of applicable to the specific cases (forms) of coordination coordination GSO GSO ↔↔ GSOGSOGSO GSO ↔↔ NonNon--GSO GSO NonNon--GSO GSO ↔↔ NonNon--GSO, GSO, GSO/NonGSO/Non--GSO GSO ↔↔ terrestrial services)terrestrial services)


GSO GSO ↔↔ GSOGSO

criterion criterion Delta Delta T/T>6%,T/T>6%, method of calculation in Ap8method of calculation in Ap8Coordination ArcCoordination Arc: GSO FSS, BSS, Metsat in : GSO FSS, BSS, Metsat in

certain frequency bandscertain frequency bands

List of ADMINISTRATIONS (Coord. List of ADMINISTRATIONS (Coord. requiredrequired))List of NETWORKS, List of NETWORKS, for informationfor information (No.9.36.2)(No.9.36.2)


BR publishes network data in a Special Section BR publishes network data in a Special Section of its IFIC, on CDof its IFIC, on CD--ROM, fortnightly as well as ROM, fortnightly as well as the results of its examination,the results of its examination,findings (No.9.35/11.31),findings (No.9.35/11.31),coordination requirements (list of ADMINS, coordination requirements (list of ADMINS,

No.9.36),No.9.36),list of networks (for information if only, where list of networks (for information if only, where appropriate, No. 9.36.2); and/or,appropriate, No. 9.36.2); and/or,if applicable, potentially affected Admins for if applicable, potentially affected Admins for information only (No. 9.36.1) information only (No. 9.36.1)





BR COMMENTS - Findings with respect to No.9.35/11.31

Example1. 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).

BR COMMENTS BR COMMENTS -- Findings with Findings with respect to No.9.35/11.31respect to No.9.35/11.31

1.21.2 UNFAVOURABLE for frequency UNFAVOURABLE for frequency assignment 12.5 GHz in transmitting assignment 12.5 GHz in transmitting space station beam UPC (outspace station beam UPC (out--ofof--band).band).

1.31.3 FAVOURABLE for all other frequency FAVOURABLE for all other frequency assignmentsassignments..

BR COMMENTS – Coordination Requirements (No.9.36)

CR/C• Applicable forms of COORD (page 1,2)• Summary of COORD Requirements,

per form of coord – List of Admins (p. 3,4)

(Last part of CR/C)• Detailed COORD requirements (Admins) for

each group of frequency assignments• List of networks identified (for info only)

COORDINATION (14)COORDINATION (14)

The list of:The list of:–– administrations identified by the BR administrations identified by the BR

under 9. 11 to 9.14 and 9.21under 9. 11 to 9.14 and 9.21–– networks identified by the BR under 9.7networks identified by the BR under 9.7

are only for information purposes (to help are only for information purposes (to help administrations comply with procedures) administrations comply with procedures) --9.36.1, 9.36.1, 9.36.29.36.2

COORDINATION (15)COORDINATION (15)

The list of ADMINs identified under 9.7 and The list of ADMINs identified under 9.7 and Article 7 of Appendices 30 and 30A, as a Article 7 of Appendices 30 and 30A, as a result of Coordination Arc, DeltaT/T or PFD result of Coordination Arc, DeltaT/T or PFD mask, is the formal list of administrations mask, is the formal list of administrations with which coordination is requiredwith which coordination is requiredCoordination Arc results: No. 9.41/9.42, Coordination Arc results: No. 9.41/9.42, inclusion, exclusion (4 months)inclusion, exclusion (4 months)Four months for commentsFour months for comments

COORDINATION (16) COORDINATION (16)

Action by administrationsAction by administrations……An administration having received a An administration having received a request for coordination (through request for coordination (through publication of CR/C) shall examine the publication of CR/C) shall examine the matter with respect to interference which matter with respect to interference which may be caused to, or caused by, its own may be caused to, or caused by, its own assignmentsassignments


……Action by administrationsAction by administrations……

inform the requesting administration and inform the requesting administration and the BR within four months from the date the BR within four months from the date of publication of the BR IFIC of either:of publication of the BR IFIC of either:

–– its agreement to the proposed use, orits agreement to the proposed use, or–– its disagreement, giving reasons for its disagreement, giving reasons for

the disagreement (No. 9.52)the disagreement (No. 9.52)


Action by administrationsAction by administrations……For coordination requests under Nos.For coordination requests under Nos.

9.11, 9.12 to 9.14 and 9.21:9.11, 9.12 to 9.14 and 9.21:

the absence of disagreement within the absence of disagreement within the 4the 4--month period means agreement month period means agreement (9.52C) !(9.52C) !

SpaceComSpaceCom


……Action by BureauAction by Bureau……

Checking of received commentsChecking of received comments

Verification of coordination Verification of coordination requirements and CR/D publication requirements and CR/D publication (No.9.53A)(No.9.53A)


Res.33 (Rev. WRCRes.33 (Rev. WRC--03)03)Procedure applicable to nonProcedure applicable to non--planned BSS is planned BSS is included in Article 9. However, WRCincluded in Article 9. However, WRC--97 97 decided that for satellite networks for which decided that for satellite networks for which API information was received prior to API information was received prior to 01.01.1999 01.01.1999 -- Resolution 33 applies.Resolution 33 applies.If API information was received after 01.01.99 If API information was received after 01.01.99 –– No.9.11 appliesNo.9.11 applies

Date of bringing into use of Date of bringing into use of frequency assignments to frequency assignments to

space networksspace networks

No. 9.1No. 9.1 Advance publication procedure Advance publication procedure shall be initiated not earlier than 7 years shall be initiated not earlier than 7 years before the planned date of bringing into use before the planned date of bringing into use of the network.of the network.

Date of bringing into use (2)Date of bringing into use (2)

No.11.44No.11.44 The notified date of bringing into The notified date of bringing into use of any frequency assignment to use of any frequency assignment to a space station shall be not later a space station shall be not later than than 7 years7 years following the date of following the date of receiptreceipt by the BR of the relevant by the BR of the relevant information under 9.1. information under 9.1. -- (i.e. API)(i.e. API)

Date of bringing into use (3)Date of bringing into use (3)

Res. 51 (WRCRes. 51 (WRC--2000)2000)““Transitional arrangements relating to the Transitional arrangements relating to the API and coordination of satellite networksAPI and coordination of satellite networks””

ResolvesResolves -- For satellite networks for which For satellite networks for which API had been received by the BR prior to API had been received by the BR prior to 22.11.9722.11.97, the maximum allowed time period , the maximum allowed time period to bring frequency assignment into use to bring frequency assignment into use shall be shall be 9 years9 years from the date offrom the date ofpublicationpublication of the API.of the API.

Due Diligence Due Diligence (Administrative)(Administrative)

Resolution 49Resolution 49: to address the problem of : to address the problem of reservation of orbit and spectrum capacity reservation of orbit and spectrum capacity without actual use (Res. 18 of Kyoto without actual use (Res. 18 of Kyoto Plenipotentiary)Plenipotentiary)

Applies from 22.11.1997 to any satellite Applies from 22.11.1997 to any satellite network in the FSS, MSS, BSS that is network in the FSS, MSS, BSS that is subject to coordinationsubject to coordination

Procedure: contained in `Procedure: contained in `resolvesresolves’’ & & Annex 1Annex 1

Due Diligence (2)Due Diligence (2)Information required:Information required:

Annex 2 to Resolution 49Annex 2 to Resolution 49

A.A. Identity of the satellite networkIdentity of the satellite networkB.B. Spacecraft manufacturerSpacecraft manufacturerC.C. Launch services providerLaunch services provider


A.A. Identity of the satellite networkIdentity of the satellite networka)a) Identity of the satellite networkIdentity of the satellite networkb)b) Name of the administrationName of the administrationc)c) Country symbolCountry symbold)d) Reference to the API special Reference to the API special

sectionsection


e)e) reference to the CR/C special sectionreference to the CR/C special sectionf)f) Frequency band(s)Frequency band(s)g)g) Name of the operatorName of the operatorh)h) Name of the satelliteName of the satelliteI)I) Orbital characteristicsOrbital characteristics


B.B. Spacecraft manufacturerSpacecraft manufacturera)a) Spacecraft manufacturerSpacecraft manufacturerb)b) Date of execution of the contractDate of execution of the contractc)c) Contractual Contractual ““delivery windowdelivery window””d)d) Number of satellites procuredNumber of satellites procured


C. C. Launch services providerLaunch services providera)a) Name of the launch vehicle providerName of the launch vehicle providerb)b) Date of execution of the contractDate of execution of the contractc)c) Anticipated launch delivery window or Anticipated launch delivery window or

inin--orbit deliveryorbit deliveryd)d) Name of the launch vehicleName of the launch vehiclee)e) Name and location of the launch facilityName and location of the launch facility

Due Diligence (3)Due Diligence (3)

Six months before expiry of the regulatory Six months before expiry of the regulatory limit for bringing into use, the BR sends a limit for bringing into use, the BR sends a reminderreminderIf the complete due diligence information is If the complete due diligence information is not received within the specified time limit, not received within the specified time limit, the network shall no longer be taken into the network shall no longer be taken into account and shall not be recorded in the account and shall not be recorded in the Master RegisterMaster Register

COORDINATION COORDINATION –– A SUMMARYA SUMMARY

Why?Why? …………..To avoid interference in operation..To avoid interference in operationWhat?What? ………….GSO/GSO (always).GSO/GSO (always)

BSS/Terr (always)BSS/Terr (always)NonNon--GSO/NonGSO/Non--GSO, GSO, TerrGSO, GSO, Terr(when Footnote says so)(when Footnote says so)

How?How? …………..Article 9..Article 9Criteria?Criteria? ……Appendix 5Appendix 5Data?Data? ………….Appendix 4.Appendix 4

TRANSMITTINGEARTH STATION

RECEIVINGEARTH STATION

TERRESTRIAL STATION

Thank You !Thank You !

Documents

04-Coordination of Satellite Networks MG - TT · SIMPLIFIED COORDINATION PROCEDURE Article 9 contains ... COORDINATION (9) Appendix 5: ... API and coordination of satellite networks