How is Technical & Regulatory Examination carried out in the BR - a detailed view

TRANSMITTING EARTH STATION RECEIVING EARTH STATION INTERFERENCE TERRESTRIAL STATION GSO SATELLITES Non-GSO SATELLITES Possible Interference Scenarios

Satellite filings by administrations have two basic objectives: -Interference-free operation -international recognition by recording frequency assignments and, as appropriate, orbital positions used or intended to be used in the Master International Frequency Register (MIFR)

Two approaches for sharing orbit / spectrum resource: Coordination Approach ↔ Coordination Approach Efficiency ↔ First come, first served for actual requirements Planning Approach ↔ Planning Approach Equitable access ↔ Plan for future use

COORDINATION means Obligatory NEGOTIATION between Administrations to arrive at ” interference-free” operation by following the processes and Procedures described in Radio Regulations Radio Regulations- a binding international treaty (No. 31 of the ITU Constitution) We shall focus upon the: Coordination Approach

Article 21 & 22 Article 21 & 22 POWER LIMITS Power Flux Density - to protect Terrestrial from Space servicesEIRP Protect Space from Terrestrial services REGULATORY PROTECTION e.g. No Non-GSO to protect GSO (FSS and BSS)EPFD Protect GSO from Non-GSO Mechanisms in Radio Regulations to control interference Mechanisms in Radio Regulations to control interference Article 5 ALLOCATION Frequency separation of stations of different radio services

Radio Regulation Procedures for the `Coordination Approach Radio Regulation Procedures for the `Coordination Approach’ Article 9 Article 9 Consolidates all coordination procedures Article 11 & Resolution 33 Article 11 & Resolution 33 Provisions detailing the requirement for notification/recording of frequency assignments

Radio Regulation Procedures for the `Coordination Approach Radio Regulation Procedures for the `Coordination Approach’ Appendix 4 Appendix 4 Specifies data elements Appendix 5 Appendix 5 Criteria for identification of administrations with which coordination is to be effected or agreement sought

Coordination is central to the three stage process : Advance Publication of Information (API) Coordination Notification & Recording in the Master International Frequency Register (MIFR) Submission of advance information that is published by the BR Exam. by BR to establish Findings, coordination Requirements and to publish. Coordination is then carried out by the responsible administration. Examination of the Notification, checking of Coordordination Agreements & Recording in MIFR

Advance Publication of Information (API) Coordination Notification & Recording in the Master International Frequency Register (MIFR) Let us now focus on the process of coordination to establish Findings and coordination Requirements

Coordination Examination comprises of two parts: No (11.31) Compliance with Table of Frequency Allocation No. 9.36: Identify any administration with which coordination may need to be effected

No (11.31) Compliance with Table of Frequency Allocation refers to : Conformity with the `Table of Frequency Allocations’ (Article 5) Successful application of No.9.21 (when reqd.) Conformity with other procedures i.e. Rules of Procedure (RoP)

No (11.31) Compliance with Table of Frequency Allocation refers to : Conformity with the `Table of Frequency Allocations’ (Article 5) Successful application of No.9.21 (when reqd.) Conformity with other procedures i.e. Rules of Procedure (RoP) If Compliance exists – FINDING is `FAVOURABLE ’ If Compliance exists – FINDING is `FAVOURABLE ’ If Compliance does NOT exist – FINDING is `UNFAVOURABLE ‘ If Compliance does NOT exist – FINDING is `UNFAVOURABLE ‘

For the frequency assignments in a satellite network – how does BR check Compliance with Table of Freq. Allocations ? Let us first get….. overview of the entire process …….an overview of the entire process of checking compliance with the Table of freq. allocations (Art.5)

GIMS Data Check for applicable provisions of Article 5 SNS Online (Network Analysis) Network/Frequency Assignments/Provisions Summary No (11.31) SNS (Ingres) – BR’s Primary database SRS_ALL & GIMS PREPARATION of Network summary Network data is stored here GIMS & SRS_ALL (BR’s secondary data-base – derived from SNS) are used for coordination examination Manual check (No software tool exists) Special query & Network Analysis query on SNS online ( produce summary of network – freq. bandwidth Class of stns. Beams …………..as shown in the next slide……

Check for Compliance and applicable Provisions Extract from SNS Online ( ) Extract of Table of Frequency Allocations (Article 5) Footnote No (11.31)

Check for Compliance and applicable Provisions Applicable Provisions No (11.31)

SatelliteNetwork IDAdminLongitude2D DateSp Section No SISCOMIS B84°W CR/C/ A9.7B9.42Ap30Ap30ARes77Res84Res539Res33 3 X Freq. [MHz] Assigned Bandwidth [kHz] Freq. Band [MHz] Class o f Station EG, EJ, EU 7450 – 7750 (4 frequency assignments) EK 218BCN x X Transmit beams No.9.21 ← No *Hard PFD limits of Art.21 apply (Coordination requirements under No.9.21/C not necessary) Unfavourable N X / No See item 3 of RoP on No.1.23 Freq. [MHz] Assigned Bandwidth [kHz] Freq. Band [MHz] Class o f Station EG, EJ, EU Receive beam Remarks 220 x No.9.21 ← No Res A A /A9.21/B9.21/C XXX Remarks Applicable provisions Another Example of Network summary Checking for applicable provisions of Article 5 & conformity with Rules of Procedure (RoP)

GIMS Data Check for applicable provisions of Article 5 SNS Online (Network Analysis) Network/Frequency Assignments/Provisions Summary Checking compliance with Table of freq. allocations (Art.5) SNS (Ingres) – Primary database SRS_ALL & GIMS NGSO Manual PFD Examination GSO PFD Program exists to check Hard EIRP & PFD Limits ) PFD.LST (Text Report) (Used to manually indicate unfavourable assignments/groups of freq. assignments) Compliance with EIRP & PFD hard limits is checked (Art.21 & 22, Resolutions, Footnotes). Freq. assignments are given `unfavourable’ findings when these limits are exceeded PFD Examination No (11.31) PFD Examination

1. Enter Network ID 2. Select Exam. Type: Hard Limits 3. Start Program GIBC – PFD Program (To check with Hard EIRP/PFD Limits) PFD Examination – Cont. GIBC Graphical Interface for Batch Calculations Software-tool used for PFD Exam No (11.31) GIBC is not for N-GSO networks (PFD Calculated manually)

Frequency Assignment Worst case location where the PFD excess is maximum. PFD Excess PFD Limit –PFD.LST (Text Report) N- Finding PFD Examination (Cont.) Group Id. Transmit beam No (11.31)

Unfavourable Finding designated by N- BatchResults.mdb (Access Database) Grp Table Fdg_ref Table PFD Examination (Cont.) Provision No X/21.16 → Not in accordance with No No (11.31)

GIMS Data Check for applicable provisions of Article 5 SNS Online (Network Analysis) Network/Frequency Assignments/Provision s Summary Checking compliance with Table of freq. allocations (Art.5) SNS (Ingres) – Primary database SRS_ALL & GIMS NGSO Manual PFD Examination GSO PFD Program exists to check Hard EIRP & PFD Limits) PFD.LST (Text Report) (Used to manually indicate unfavourable assignments/groups of freq. assignments) Results.mdb (Access Database) (Groups split according to findings & contains data for entire network) Split Groups of freq. assignments For network preparation (e.g. provisions) and for unfavourable findings (N-) Groups of frequency assignments are then split according to the applicable RR provisions & `Findings’ (Favourable & Unfavourable). SPLITS No (11.31) SPLITS

9.7 AP30#7.1 Split Groups – According to the applicable Provisions for Network Preparation This group of frequencies (having 16 frequencies) is split into two groups. Provision No.9.7 is applicable to the first group and Provisions Nos.9.7 & Appendix30 # 7.1 to the second group First Group Second Group SPLITS – Cont. No (11.31)

Split Groups – According to Findings SPLITS (Cont.) No (11.31)

SNS (Ingres) – Primary database GIMS Data Check for applicable provisions of Article 5 SNS Online (Network Analysis) Network/Frequency Assignments/Provision s Summary Checking compliance with Table of freq. allocations (Art.5) SNS (Ingres) – Primary database SRS_ALL & GIMS NGSO Manual PFD Examination GSO PFD Program exists to check Hard EIRP & PFD Limits) PFD.LST (Text Report) (Used to manually indicate unfavourable assignments/groups of freq. assignments) Results.mdb (Access Database) (Groups split according to findings & contains data for entire network) Split Groups For network preparation (e.g. provisions) and for unfavourable findings (N-) Finally the data is merged with the SNS `Primary - data base’. MERGE No (11.31) MERGE

SNS (Ingres) – Primary database GIMS Data Check for applicable provisions of Article 5 SNS Online (Network Analysis) Network/Frequency Assignments/Provision s Summary SUMMARY OF STEPS - SUMMARY OF STEPS - Checking compliance with Table of freq. allocations (Art.5) SNS (Ingres) – Primary database SRS_ALL & GIMS NGSO Manual PFD Examination GSO PFD Program exists to check Hard EIRP & PFD Limits) PFD.LST (Text Report) (Used to manually indicate unfavourable assignments/groups of freq. assignments) Results.mdb (Access Database) (Groups split according to findings & contains data for entire network) Split Groups For network preparation (e.g. provisions) and for unfavourable findings (N-) PREPARATION of Network summary PFD Examination SPLITS MERGE

GIMS Data To Establish coordination requirements - the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base These data-bases are required for establishing coordination requirements These data-bases are updated every week

/A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO GIMS Data To Establish coordination requirements - the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base Provisions applicable for a satellite network Have been identified and listed in the `Network – Summary ‘ Coordination requirements under various applicable provisions are established by utilising different data-bases, as shown

GIBC PFD - TriggerAP8PXTAP8 FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO GIMS Data To Establish coordination requirements - the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base Graphical Interface for Batch calculations Software tools – GIBC, FOS, FOT - suitably selected to establish coordination requirements

GIBC PFD - TriggerAP8PXTAP8 FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO GIMS Data To Establish coordination requirements - the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base 1. Enter Network Id (e.g ) 2. Click the start button Use of GIBC tool for AP8 calculations

Examination under Appendix 8 – output files/data-bases DT/T > 6% Coordination Arc DT/T RS33#3 AP30A#7.1 * 9.21/A * Requires BSS Plans database APP8.LST → Text Report Existing network Incoming network (Network under examination) No.9.36 Coordination requirments Established under these Provisions

Examination under Appendix 8 – output files/data-bases No.9.36 Coordination requirements established under these Provisions Coordination Arc DT/T RS33#3 AP30A# /A

Examination under Appendix 8 – output files/data-bases NTW.LST → Text Report List of satellite Network for which Delta T/T > 6% or which are within Coord. Arc N = Notification C = Coordination A = Recorded in MIFR / Already published T = Under examination C = Causing Interference R = Receiving Interference A = Coordination Arc No.9.36

Examination under Appendix 8 – output files/data-bases Provn Table BatchResults.mdb → Access Database Tr_aff_ntw No.9.36 This table contains Coordination provision and the names of countries This table contains names of satellite networks

GIBC PFD - TriggerAP8PXTAP8FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO.MDB GIMS Data To Establish the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base Use of GIBC tool For PFD Trigger check Enter Network Id. Select `Triggers’ For PFD Click Start

No.9.36 Beam Group ID Frequency Assignment Names of countries over which PFD coordination trigger limits are exceeded. Excess over the limit is also shown PFD Limit PFD.LST → Text Report A- Finding Examination against PFD Trigger limits – output files/data-bases This report contains list of Countries where PFD coordination trigger limit is exceeded. With the amount of excess

No.9.36 BatchResults.mdb → Access Database Examination against PFD Trigger limits – output files/data-bases Provn Table This data-base contains List of Countries where PFD coordination trigger limit is exceeded.

GIBC PFD - TriggerAP8PXTAP8FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO.MDB GIMS Data To Establish the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base Use of GIBC Tool For PXT Exam (AP30#7.1) 1. Enter Network Id. 2. Click Start

No.9.36 PXT.LST → Text Report PFD Existing BSS network Incoming network (Network under examination) Excess PFD Limit Coordination Examination PXT – output files/data-bases AP30#7.1 Requires BSS Plans database Coordination with this administration under AP30#7.1 This report contains List of Countries with whom coordination is required under AP30#7.1

No.9.36 NTW.LST → Text Report Coordination Examination PXT – output files/data-bases This report contains List of satellite networks with whom coordination is required under AP30#7.1

No.9.36 BatchResults.mdb → Access Database Coordination Examination PXT – output files/data-bases This access data-base has the entire network plus the tables containing list countries & the satellite networks with whom coordination is required under AP30#7.1 Provn Table Tr_aff_ntw Table

GIBC PFD - TriggerAP8PXTAP8FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO.MDB GIMS Data To Establish the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base Each tool will produce a single database (access data-base) containing the entire network data as well as the coordination requirements. To find space stations or terrestrial stations with frequency overlap depending on the requirements of the provisions. Using the software tools FOS & FOT

No.9.36 FOS & FOT – both produce a text report as well as an access database with coordination requirements stored in the Provn Table. Coordination Examination Frequency Overlap – output files/data-bases Provn Table (FOS) Provn Table (FOT) Space Regulatory Workshop, Bangalore, India, June 2007 Agreement status F means detected by Frequency Overlap.

GIBC PFD - TriggerAP8PXTAP8FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO.MDB GIMS Data To Establish the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base Each tool will produce a single database (access data-base) containing the entire network data as well as the coordination requirements. Merging of all the access data-bases produced by each software tool into ONE data-base

Merge Databases (Example) 9.7 A30#7.1 A30A#7.1 ProvnTable Provision symbol & agreement status are described in Table 11 (BR Preface) No.9.36 When we merge the databases, all the Provn Tables from various tools are combined together into one single Provn Table

Merge Databases (Example) No.9.36 When we merge the databases, all the Tr_aff_ntw Table Tables from various tools are combined together into one single Tr_aff_ntw Table Table 9.7 A30A#7.1 Tr_aff_ntw Table

GIBC PFD - TriggerAP8PXTAP8FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO.MDB GIMS Data To Establish the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base Each tool will produce a single database (access data-base) containing the entire network data as well as the coordination requirements.

GIBC PFD - TriggerAP8PXTAP8FOS (Freq Overlap with Space Services) FOT (Freq Overlap with Terrestrial Services) SNS /A RS33#3 AP30A #7.1 AP30 # /C RS33#2.1 GSO A 9.21/A 9.21/B NGSO /B GSO /C RS33#2.1 GSO Merge into one.MDB.MDB GIMS Data To Establish the list of countries (& satellite networks) with whom coordination is required No.9.36 SNS (Ingres) – Primary Database SRS_ALL & GIMS BSS Plan Database Terrestrial Data-base And finally the Merged database updates the SNS

Special Section CR/C IFIC number / date of publicationSpecial Section number Name of the satellite network Network ID Responsible administration Date of receipt Last date for receipt of comments (Date of publication + 4 months) First page Satellite NetworkCR/C Indication of applicable forms of coordination to the network X 9.7 X AP30 #7.1

Special Section CR/C Second page Potentially affected administrations For information only Summary of coord. req. per provision Satellite NetworkCR/C Indication of applicable forms of coordination to the network X 9.7 X AP30 #7.1

Coord. req. at group level BR comments (e.g. N- findings) Notes by administration Gain contours Network data Summary of coord. req. per provision Satellite NetworkCR/C Indication of applicable forms of coordination to the network X 9.7 X AP30 #7.1 Special Section CR/C Coordination requirements at group level & BR Comments Subsequent pages show network parameters, gain contour diagrams, notes submitted by the administrations, comments by the BR including reasons for unfavourable findings and coordination requirements at group level.

Previous special sections Network List(s) – For info only Coord. req. at group level BR comments (e.g. N- findings) Notes by administration Gain contours Network data Summary of coord. req. per provision Satellite NetworkCR/C Indication of applicable forms of coordination to the network X 9.7 X AP30 #7.1 Special Section CR/C List of potentially affected satellite networks For information only