1 / 53

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

How is Technical & Regulatory Examination carried out in the BR - a detailed view. Possible Interference Scenarios. INTERFERENCE. GSO SATELLITES. Non-GSO SATELLITES. RECEIVING EARTH STATION. TRANSMITTING EARTH STATION. TERRESTRIAL STATION. Satellite filings by administrations have

jaguar
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

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

  4. Two approaches for sharing orbit / spectrum resource: Coordination ApproachEfficiency↔ First come, first served for actual requirements Planning ApproachEquitable access↔ Plan for future use

  5. We shall focus upon the:Coordination Approach 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)

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

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

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

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

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

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

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

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

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

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

  16. No. 9.35 (11.31) Check for Compliance and applicable Provisions Extract of Table of Frequency Allocations (Article 5) Extract from SNS Online (http://www.itu.int/sns/ntwktab.html) Footnote

  17. No. 9.35 (11.31) Check for Compliance and applicable Provisions Applicable Provisions

  18. Applicable provisions Another Example of Network summary Transmit beams Remarks No.9.21 ← No.5.461 *Hard PFD limits of Art.21 apply (Coordination requirements under No.9.21/C not necessary) Unfavourable N X / No.11.31 See item 3 of RoP on No.1.23 Receive beam Checking for applicable provisions of Article 5 & conformity with Rules of Procedure (RoP) Remarks No.9.21 ← No.5.461

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

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

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

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

  23. No. 9.35 (11.31) Checking compliance with Table of freq. allocations (Art.5) GIMS Data SPLITS SNS (Ingres) – Primary database SRS_ALL & GIMS SNS Online (Network Analysis) Check for applicable provisions of Article 5 GSO PFD Program exists to check Hard EIRP & PFD Limits) NGSO Manual PFD Examination Network/Frequency Assignments/Provisions Summary 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-) SPLITS Groups of frequency assignments are then split according to the applicable RR provisions & `Findings’ (Favourable & Unfavourable).

  24. No. 9.35 (11.31) SPLITS – Cont. 9.7 AP30#7.1 9.7 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 Second Group First Group

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

  26. No. 9.35 (11.31) GIMS Data SNS (Ingres) – Primary database Checking compliance with Table of freq. allocations (Art.5) MERGE SNS (Ingres) – Primary database SRS_ALL & GIMS SNS Online (Network Analysis) Check for applicable provisions of Article 5 GSO PFD Program exists to check Hard EIRP & PFD Limits) NGSO Manual PFD Examination Network/Frequency Assignments/Provisions Summary 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

  27. SUMMARY OF STEPS - Checking compliance with Table of freq. allocations (Art.5) GIMS Data SNS (Ingres) – Primary database PREPARATION of Network summary SNS (Ingres) – Primary database SRS_ALL & GIMS SNS Online (Network Analysis) PFD Examination Check for applicable provisions of Article 5 GSO PFD Program exists to check Hard EIRP & PFD Limits) NGSO Manual PFD Examination Network/Frequency Assignments/Provisions Summary PFD.LST (Text Report) (Used to manually indicate unfavourable assignments/groups of freq. assignments) SPLITS 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-) MERGE

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

  29. GIMS Data GSO GSO GSO NGSO GSO 9.7 9.21/A RS33#3 9.11 9.14 9.21/C RS33#2.1 AP30A #7.1 AP30 #7.1 9.13 9.21/B 9.12 9.12A 9.21/A 9.21/B 9.11 9.14 9.21/C RS33#2.1 No.9.36 To Establish coordination requirements - the list of countries (& satellite networks) with whom coordination is required SNS (Ingres) – Primary Database SRS_ALL & GIMS Terrestrial Data-base BSS Plan Database 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

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

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

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

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

  34. A = Recorded in MIFR / Already published T = Under examination N = Notification C = Coordination C = Causing Interference R = Receiving Interference A = Coordination Arc No.9.36 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

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

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

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

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

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

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

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

  42. No.9.36 Coordination Examination PXT – output files/data-bases • BatchResults.mdb→ Access Database 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

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

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

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

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

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

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

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

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

More Related