BR Seminar - Workshop Geneva 30/10 – 03/11/2006

BR Seminar - Workshop Geneva 30/10 – 03/11/2006
Technical Examination of the Space Plans Services Submissions under Appendices 30, 30A and 30B and the related BR Software Packages BR Seminar - Workshop Geneva 30/10 – 03/11/2006 World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Outline Technical Examinations relating to coordination of different services sharing bands subject to a Space Plan Who does what? Protection Criteria Technical Examinations of submissions under 4 of Appendices 30 and 30 Hard Limits Trigger Limits Intra-service/region Examinations Inter-service/region Examinations in the shared band Examinations at different Stages of Article 4 Networks: Publication of Part A Special Sections Publication of Part B Special Sections BR Software Package SPS (Space Plans’ System) BR Software Package GIBC (Graphical Interface for Batch Calculations) Technical Examinations of submissions under Article 2A of Appendices 30 and 30 Technical Examinations of submissions under Article 6 of Appendix 30B World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection Criteria Concept
Purpose: To identify Potential Incompatibility between proposed assignments and Radiocommuincation services of other administrations based on a set of limits on specific parameters which is calculated for potential interference assessment Limits on parameters: Such as E.I.R.P., PFD, EPM/OEPM, Orbital Position-Frequency Bands World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection Criteria Categories
Hard Limits If exceeded, Submission is not receivable or is considered as unfavorable and shall be virtually returned to notifying administration To preserve current and future use of a Radiocommunincation Service in general Coordination Trigger Limits Agreements (implicit or explicit) of affected administrations is required for successful completion of the relevant coordination procedure To protect: Existing assignments/allotments of Space Services Networks that fulfill the following conditions on their service area: Assignments in the AP30/30A Plans and List, Or Allotments and the AP30B Plan, Or assignments in the AP30B List, Or Proposed assignments of satellite network submissions whose complete AP4 information received by the BR before or on the same date of receipt of that of the incoming network, And Whose necessary bandwidth overlaps with that of an assignment of the incoming network Existing and future terrestrial services on territories of administrations World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Article 4 of Appendices 30 and 30A
Hard Limits Examinations Coordination Trigger Limits Examination Intra-service/region Examination BR Software Package: SPS (MSPACEg, BSS_Marg) To protect: Assignments of Plan/List and those of pending Article 4 submissions in the same regional AP30/30A Plan/List Inter-service/region Examinations in the shared band BR Software Package: GIBC (PFD (Space/Terrestrial services), Appendix 8) To protect: Assignments in the Plans and Lists Assignments of pending submissions under Article 4 in the other regional AP30/30A Plan/List Unplanned FSS and BSS Satellite Networks in support of Space Operation Functions submitted under Article 2A of AP30/30A Terrestrial Services World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Tech. Exam. at different Stages of Article 4 Networks
Part A Special Section: Publication under § 4.1.5/4.2.8 in BR IFIC Calculation of potential interference from the incoming Article 4 network to other services/assignments based on the relevant protection criteria using the latest SPS_ALL / SRS_ALL database Creation of Reference Situation for the incoming Article 4 network for its protection against subsequent Article 4 networks Establishment of list of potentially affected administrations Part B Special Section: Publication under § / in BR IFIC Re-calculation of potential interference would be required only if the initial network characteristics as published in Part A Special Sections have been modified SPS_ALL/SRS_ALL database Comparison of protection limits excess resulting from the modified characteristics with those produced by the Part A ones for establishment of list of administrations whose agreements are required for successful completion of Article 4 procedure World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Examination of Part B submissions
Comparison of the results with those of Part A Special Section To verify whether or not an objecting administration’s networks/territories are still identified as affected by the modified parameters, or An additional interference is imposed on an administration that has not objected or has previously agreed after an objection For the SPS Package examination the SPS_ALL database included in the BR IFIC of the network’s Part A publication is used as common existing reference situation scenario for comparison World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Article 2A of Appendices 30 and 30A
BR Software Package: GIBC (PFD (Space/Terrestrial services), Appendix 8) To protect: Assignments in the Plans and Lists Assignments of pending submissions under Article 4 in both regional AP30/30A Plans/Lists Unplanned FSS and BSS Satellite Networks in support of Space Operation Functions submitted under Article 2A of AP30/30A Terrestrial Services World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Submissions under Articles 6 of Appendix 30B
Single entry and aggregate C/I calculation: BR Software Package: SPS (MSPACEg, FSSUPD / BSS_Marg) To protect: Allotments in the Plan Assignments in the List World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Procedure: mehrdad.yousefian@itu.int Software: brsas@itu.int
Any question? About: Procedure: Software: World Radiocommunication Seminar Geneva, 30 October-3 November 2006

SPS Package - Intra-service/region Tech. Examination
Incoming Article 4 Notice {A} 1-SpaceCap Export the SPS_ALL database GIBC 2-SPS/MSPACE Identification of affected Networks / assignments Calculation of reference situation for the incoming Article 4 network GIMS Databases SPS_ALL Input Database {A, V, P} MSPACE Output database (*.out.mdb) SPS_ALL Output Database {V, P} 4- SpacePub 3-SPS/BSS_Marg Capturing of the calculated reference situation into SPS_ALL for the incoming network for the purpose protection against subsequent Article 4 submissions Changing of the type of assignment of the incoming network from A to V Capturing of the results of MSPACE examination with respect to the affected assignments for further processing of the incoming network Special Section AP30/E/, AP30A/E/ or AP30-30A/E List of affected networks/Plan beams World Radiocommunication Seminar Geneva, 30 October-3 November 2006

{Status code of Article 4 Notice}
GIBC Package – Article 4, Inter-service/region Tech. Examination GIMS Databases GIBC Identification of potentially affected services/networks of other services and AP30/30A Regional Plan/List in the shared band SPS_ALL Database {Status code of Article 4 Notice} SpacePub SRS_ALL Database Special Section AP30/E/, AP30A/E/ or AP30-30A/E - list of affected Plan beams, List or Article 4 Networks in the other regional Plan/List - list of affected unplanned BSS and FSS Networks - list of administrations whose terrestrial services are affected World Radiocommunication Seminar Geneva, 30 October-3 November 2006

GIBC Package – Article 2A, Technical Examination
GIMS Databases GIBC Identification of potentially affected services/networks of other administration in the shared band SPS_ALL Database SpacePub SRS_ALL Database Special Section AP30-30A/F/C - list of affected Plan beams, List or Article 4 Networks - list of affected unplanned BSS and FSS Networks - list of administrations whose terrestrial services are affected World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Hard Limits Appendix 30 Provision Limit Type
Examination of Compatibility of Article 4 network with Region Service  Frequency band Annex 1: Section 1, Paragraph 1 Power Flux Density 1 3 Planned Band BSS Downlink  11.7 – 12.5 GHz 11.7 – 12.2 GHz Protection of existing assignments and preservation for future assignments of satellite networks whose orbital position is separated by more than 9° from the assignment under examination Annex 7: Paragraph A1 Orbital position 2 FSS Downlink  11.7 – 12.2 GHz Paragraph A2 FSS Downlink  12.5 – 12.7 GHz FSS Downlink  12.2 – 12.7 GHz Unplanned Band BSS Downlink  12.5 – 12.7 GHz Paragraph A3 Orbital position and E.I.R.P World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30A Hard Limits Appendix 30A Provision Limit Type
Examination of Compatibility of Article 4 network with Region Service  Frequency band Annex 1: Section 4, Paragraph 1 Power Flux Density 1 and 3 Feeder-link to Planned Band BSS Downlink  14.4 – 14.8 GHz and 17.3 – 18.1 GHz Protection of existing assignments and preservation for future assignments of satellite networks whose orbital position is separated by more than 9° from the assignment under examination World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Coordination Trigger Limits – SPS Package (I)
Appendix 30 Provision Limit Type Examination of Compatibility of Article 4 network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.1.1 a) b) Section 1 PFD and EPM within ±9° arc 1 BSS Downlink Assignments of Plan, List and pending Article 4 networks  11.7 – 12.5 GHz SPS PACKAGE (MSPACEg and BSS_MARG) using GIMS and SPS databases Protected area: Service area represented by a set of maximum 20 test points 3 11.7 – 12.2 GHz 4.2.3 c) Section 2 OEPM Overall downlink and feeder-link protection criteria 2 12.2 – 12.7 GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30A Coordination Trigger Limits – SPS Package (2)
Appendix 30A Provision Limit Type Examination of Compatibility of Article 4 network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.1.1 a) b) Section 4 PFD and EPM within ±9° arc 1 and 3 BSS Feeder-link Assignments of Plan, List and pending Article 4 networks  14.5 – 14.8 GHz (outside Europe) SPS PACKAGE (MSPACEg and BSS_MARG) using GIMS and SPS databases Protected area: Feeder-link receiving space station on its Service area represented by a set of maximum 20 test points 17.3 – 18.1 GHz 4.2.2 c) Section 3 OEPM Overall downlink and feeder-link protection criteria 2 17.3 – 17.8 GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Coordination Trigger Limits – GIBC Package (I)
Appendix 30 Provision Limit Type Examination of Compatibility of Article 4 network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.1.1 c) Section 3 1st mask 2nd mask PFD Mask as a function of orbital Separation Angle 2 BSS Downlink Assignments of Plan, List and pending Article 4 networks  12.2 – 12.5 GHz GIBC-PFD (Space) using GIMS and SPS databases Output Report File Name: PXT.LST Protected area: - Service area represented by a set of maximum 20 test points 4.2.3 a) b) 1 4.2.3 f) 3 Unplanned BSS Downlink Assignments  12.2 – 12.5 GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Coordination Trigger Limits – GIBC Package (2)
Appendix 30 Provision Limit Type Examination of Compatibility of Article 4 network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.1.1 d) 4.2.3 d) Section 4 PFD Mask as a function of Arrival Angle 1 Terrestrial Services  11.7 – 12.5 GHz GIBC-PFD (Terrestrial) using GIMS and SPS databases and the latest updated PFD extract file (bss_sstn.dat) Output Report File Name: PFD.LST Protected area: Affected parts of territories of administrations that have note BSS assignments in the Plan/List whose necessary bandwidth overlaps fully that of assignment under examination 2 11.7 – 12.1 GHz 12.2 – 12.7 GHz 3 11.7 – 12.7 GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Provision Limit Type Examination of Compatibility of Article 4 network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.1.1 e) Section 6 1st mask PFD Mask as a function of orbital Separation Angle 2 FSS Downlink  11.7 – 12.2 GHz SOF Downlink  Region2 Lower Guard Band: – GHz GIBC-PFD (Space) using GIMS, SPS and SRS databases Output Report File Name: PXT.LST Protected area: Service area 1st or 2nd mask 3 FSS Downlink  12.2 – 12.5 GHz SOF Downlink  Region3 Upper Guard Band: – GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Provision Limit Type Examination of Compatibility of Article 4 network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.2.3 e) Section 6 1st mask PFD Mask as a function of orbital Separation Angle 1 FSS Downlink  12.5 – 12.7 GHz SOF Downlink Region1 Upper Guard Band: – GHz GIBC-PFD (Space) using GIMS, SPS and SRS databases Output Report File Name: PFD.LST Protected area: Service area 1st or 2nd mask 3 FSS Downlink  12.2 – 12.7 GHz SOF Downlink Region3 Upper Guard Band: – GHz Section 7 ΔT/T FSS Uplink  12.5 – 12.7 GHz GIBC-Appendix 8, Case II using GIMS, SPS and SRS databases Output Report File Name: APP8.LST Protected area: Feeder-link receiving space station on its Service area World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30A Coordination Trigger Limits – GIBC Package (5)
Appendix 30A Provision Limit Type Examination of Compatibility of Article 4 network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.1.1 c) Section 5 ΔT/T 2 BSS Feeder-link Assignments of Plan, List and pending Article 4 networks  17.3 – 17.8 GHz GIBC-Appendix 8, Case I using GIMS and SPS databases Output Report File Name: APP8.LST Protected area: Feeder-link receiving space station on its Service area represented by a set of maximum 20 test points 4.2.2 a) b) 1 and 3 World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30A Provision Limit Type Examination of Compatibility of Article 4 network with Article Annex 1 Region Service  Frequency band BR Software Article 4 4.1.1 d) Section 6 ΔT/T 2 Unplanned BSS Feeder-link Assignments  17.8 – 18.1 GHz GIBC-Appendix 8, Case I using GIMS, SPS and SRS databases Output Report File Name: APP8.LST Protected area: Feeder-link receiving space station on its Service area 4.1.1 d) and Article 2A 1 and 3 SOF Downlink  Regions 1 and 3 Lower and upper Guard Bands: GHz GHz SOF Downlink  Region 2 Lower and upper Guard Bands: : GHz GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Provision Limit Type Examination of Compatibility of Article 2A network with Article 4 Annex 1 Region Service  Frequency band BR Software 4.1.1 d) 4.2.3 d) Section 4 PFD Mask as a function of Arrival Angle 1 Terrestrial Services  Region 1 Lower and Upper Guard Bands: – GHz – GHz GIBC-PFD (Terrestrial) using GIMS and SPS databases and the latest updated PFD extract file (bss_sstn.dat) Output Report File Name: PFD.LST Protected area: Affected parts of territories of administrations that have note BSS assignments in the Plan/List whose necessary bandwidth overlaps fully that of assignment under examination 2 Region 2 Lower and Upper Guard Bands: – GHz – GHz 3 Region 3 Lower and Upper Guard Bands: – GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30 Provision Limit Type Examination of Compatibility of Article 2A network with Article Annex 4 Region Service  Frequency band BR Software Article 2A and Article & 7.2 Section 4 1st mask 3rd mask 1st or 2nd mask PFD Mask as a function of orbital Separation Angle 1 BSS Downlink Assignments of Plan, List and pending Article 4 networks  Region 1 Lower and Upper Guard Bands: – GHz – GHz GIBC-PFD (Terrestrial) using GIMS and SPS databases and the latest updated PFD extract file (bss_sstn.dat) Output Report File Name: PFD.LST Protected area: Affected parts of territories of administrations that have note BSS assignments in the Plan/List whose necessary bandwidth overlaps fully that of assignment under examination 2 Region 2 Lower and Upper Guard Bands: – GHz – GHz 3 Region 3 Lower and Upper Guard Bands: – GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30A Provision Limit Type Examination of Compatibility of Article 4 network with Article Annex 1 Region Service  Frequency band BR Software Article 4 4.1.1 d) Section 6 ΔT/T 2 Unplanned BSS Feeder-link Assignments  17.8 – 18.1 GHz GIBC-Appendix 8, Case I using GIMS, SPS and SRS databases Output Report File Name: APP8.LST Protected area: Feeder-link / Uplink receiving space station on its Service area 4.1.1 d) and Article 2A 1 and 3 SOF Downlink  Regions 1 and 3 Lower and upper Guard Bands: GHz GHz SOF Downlink  Region 2 Lower and upper Guard Bands: : GHz GHz World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Appendix 30A Provision Limit Type Examination of Compatibility of Article 2A network with Article Annex 4 Region Service  Frequency band BR Software Article 2A, Article 4 4.1.1 d) and Article 7 7.1 & 7.2 Section 2 ΔT/T 1 and 3 BSS Feeder-link Assignments of Plan, List and pending Article 4 networks  Regions 1 and 3 Lower and upper Guard Bands: GHz GHz GIBC-Appendix 8, Case I using GIMS, SPS and SRS databases Output Report File Name: APP8.LST Protected area: Feeder-link receiving space station on its Service area 2 World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Comparison Examination of Part B submissions
Network/Plan Beam identified as affected in results of examination with Inter-ference Levels Com-parison Agreement required ? Remark No. Part A parameters Part B parameters Adm. Objected on Part A Other Adm. 1 Identified with Level A Not Identified N.A. No Since the affected network/Plan Beam/Country is no more identified in the updated Part B results, agreement is not required 2 Yes 3 Identified with Level B A < B Since the level of interference of Part B is not greater than that of the published Part A, the previous implicit agreement of the affected administrant is still valid 4 Since the objecting administration is still identified as affected, its agreement is required 5 A ≥ B 6 Since the level of interference of Part B is greater than that of the published Part A, the previous implicit agreement of the affected adm. is no longer valid. An explicit agreement is therefore required 7 The agreement of the affected administration whose service/network has been newly identified as affected, is required World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Keep Findings and Reference Situation
When using “Export” command for creating a new Article 4 submission from an existing notice in the SPS database be examined by MSPACE, Reference Situation should not be kept. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Similarly when using “Clone” command for creating a new Article 4 submission from an existing notice in the SPS database to be examined by MSPACE, Reference Situation should not be kept.  No

24 When using “Clone” command for creating a new Article 4 submission from an existing notice in the SPS database to be examined by GIBC, the Notice Status should be set to 24. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Only one global Plan/List Three different Regional Plans/Lists
6/4 GHz 13/10 GHz 13/11 GHz Frequency Band Option if not all bands are involved in the examination Study Options for Regions 1 & 3 Plans/Lists Study Options for Regions 1 & 3 Plans/Lists World Radiocommunication Seminar Geneva, 30 October-3 November 2006

References and Explanatory Notes (1)
Assignment Type A: Incoming Article 4 under examination without Reference Situation V: Pending Article 4 network published in Part A – receives interference from other types of assignments but its interference to them is not taken into account P: Plan/List assignment EPM/OEPM Equivalent Protection Margin Overall Equivalent Protection Margin Generalized parameters Definition and application could be found in Annex 1/Section 1B and Annex 3A of Appendix 30B Pending Article 4 submissions Article 4 submissions whose AP4 information received by the Bureau before or on the same date of receipt of that of the incoming network Single entry and aggregate C/I Definition and application could be found in Annex 4 of Appendix 30B World Radiocommunication Seminar Geneva, 30 October-3 November 2006

References and Explanatory Notes (2)
SPS_ALL Space Plans' Systems Database Contains currently AP30/30A Plans, Lists, Article 4 and Article 2A assignments. Released each two weeks in the BR IFIC CD-ROM. It could be also downloaded from the following URL: SRS_ALL Space Radiocommunications Stations Database Contains unplanned Spaces Services Notices. Released quarterly in BR SRS on CD-ROM. Should be incrementally updated using BR IFIC CD-ROM between two subsequent release of SRS on CD-ROM. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Who does what? AP30/30A-Article 7 (SSC) Space Services
Services with coordination procedure subject to other provisions of the Radio Regulations such as those of Article 9 of RR Space Services Space Services with coordination procedure associated with to a Plan: Submissions under Article 4 of Appendices 30 and 30A AP30/30A-Article 7 (SSC) AP30/30A-Article 4 (SNP) Submissions of SOF networks under Article 2A of AP30/30A Article of RR (SNP) AP30/30A Article 7 (SNP) Terrestrial Services AP30/30A-Article 4 (SNP) AP30/30A-Article 4 (SNP) AP30/30A-Article 6 (TSD) SNP: Space Notification and Plans Division SSC: Space Systems Coordination Division TSD: Terrestrial Services Department World Radiocommunication Seminar Geneva, 30 October-3 November 2006

BR Software Package SPS (Space Plans’ System)
BR Seminar - Workshop Geneva 30/10 – 03/11/2006 World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Introduction Main Concepts GIBC SPS Package Exercises Menu
Software Programs Reporting Other Software Programs World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Introduction World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Requires GIMS to be installed GIMS data up to date! Support
SPS ? Package of software programs to determine intra-service and intra-region coordination requirements for space networks of the planned services Availability SRS CD/DVD BR IFIC CD Latest version Latest data files Requires GIMS to be installed GIMS data up to date! Support MSPACE manual Software related question: The Space Plans’ System package (SPS) is a suite of software programs that is used in the BR to identify administrations affected by new submissions under Appendices 30, 30A and 30B. SPS determines only intra-service and intra-region coordination requirements. Inter-service and inter-region coordination requirements are dealt with by another software application: GIBC. The latest version of the software programs and of its associated input data are available on the ITU web site as well as on the SRS DVD (twice a year) and on the BR IFIC CD (every two weeks). To work correctly SPS requires a complete GIMS installation. The GIMS reference database must also be maintained up to date with the incremental updates distributed on the BR IFIC CD. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

BSS Down Link R1&3 Plan Appendix 30 BSS Feeder Link R1&3 Plan
When to use SPS? BSS Down Link R1&3 Plan Appendix 30 BSS Feeder Link R1&3 Plan Appendix 30A You can use SPS whenever you intend to submit a new or modified network under one the following plan: BSS Down link plan and list of additional uses for regions 1 and 3 as described in Appendix 30 of the Radio Regulations (RR) Regions 1 and 3 14/17 GHz feeder-link plan and list of additional uses as described in Appendix 30A of the RR Combined feeder and down link plan for region 2 as described in Appendix 30 and 30A. FSS plan and list in the 6/4 GHz and 13/10-11 GHz bands as described in Appendix 30B. Region 2 Plan Appendices 30/30A FSS Plan Appendix 30B World Radiocommunication Seminar Geneva, 30 October-3 November 2006

What Is the Purpose of SPS?
Coordination Requirements Minimize Interference In the BR, SPS is primarily used as a tool to determine the coordination requirements of new or modified networks notified under AP30, AP30A and AP30B of the RR. As external users, you will probably find it useful during the coordination process or for what-if studies to determine the exact impact of modifications to your network characteristics and to minimize interference with existing systems. What If Studies World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Main Concepts World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Aggregate interfering effect from all interfering sources
Plans’ Principle Aggregate interfering effect from all interfering sources Interferers are “existing” and “virtual” networks SPS evaluates an aggregate interfering effect of all possible interfering sources. This is different from the analysis of networks in the non-planned services where interference is calculated between pairs of wanted and interfering satellites. SPS takes into account both “existing” networks (in Plan or List) with confirmed date of bringing into use, and “virtual” networks (in Plan or List) with no confirmed date of bringing into use. Pending Article 4 networks, published in Part A, are protected from interference but not taken into account as interferers; they are called “Victim” networks. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

FSS : Single-entry & aggregate C/I
BSS Appendix 30/30A The BSS region 1&3 plans are defined in terms of the Equivalent Protection Margin (EPM) for each link direction whereas the BSS region 2 plan used the Overall Equivalent Protection Margin that is calculated for a complete link. The term “equivalent” indicates that the protection margins for all interference sources from the adjacent and second adjacent channels as well as co-channel interference sources have been included. Down link assignments should also respect PFD limits. The FSS plan is based on single-entry and aggregate C/I criteria where C/I is calculated for a complete link whenever possible. A set of EPM, OEPM or C/I values is called the reference situation of a given plan. FSS : Single-entry & aggregate C/I World Radiocommunication Seminar Geneva, 30 October-3 November 2006

SPS Package World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Software
MSPACE Parameter Input, calculation BSS_Margin Update of reference situation (BSS) SPS_Reports Reporting tool The SPS package is composed of four software components: MSPACE is the main calculation program. SPS_Reports is a reporting tool that allows to visualize MSPACE’s results BSS_Margin is used to update the reference situation in the input database with newly calculated values. FSSUpd updates the reference situation in the input text files that are still use for Appendix 30B analysis. Although they are distributed in the SPS package, BSS_Margin and FSSUpd are more for BR internal use. FSSUpd Update of reference situation (FSS) World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Input
SPS GIMS Database SNS-Like Database MSPACEg MSPACE uses 4 major data sources to perform its calculations that will be described in the following slides. Only AP30B Antenna Pattern Library Text File World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Input (SPS DB)
Preferred editing tool of SPS database is SpaceCap Elliptical Beams SPS MS Access SpaceCap SNS-Like Database MS Access Format The SPS database is the main input data source that contains all alphanumerical data (as required by Appendix 4) related to planned networks. The latest data are downloadable from the ITU web site. We encourage you to use SpaceCap to modify the SPS database for your own purposes. This should ensure the internal consistency of the database. As much as possible, refrain from changing the data with MS Access unless you are very much acquainted with the SPS format. However there will be cases when you may have to use MSAccess to run specific queries that do not modify the database. For the same purpose you can also use SpaceQry. The format is similar to the SRS database format that is used to store data of networks in the non-planned services. This format is available on the ITU web site. The MSPACE manual describes the SPS-specific tables. The SPS database is used for all plans analysis except Appendix 30B. SpaceQry Schema description World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Input (Text)
Sensitive syntax Migration to DB is ongoing Only AP30B Text File Any text editor (notepad…) Appendix 30B data are still stored in text files; you can edit these files with any text editor. The format is described in the MSPACE manual and uses fixed-length fields; be cautious when modifying them because any format error will cause the program to stop. BR is currently working on the conversion of the AP30B data to the SPS database format. Format description in SPS Manual World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Input (GIMS)
New diagrams Or Modifications to REFDB diagrams Read Only DB Shaped Beams GIMS Reference Database Additional Databases GIMS installation Automatic connection SPS also uses the graphical data stored in the GIMS reference database (REFDB). This is why SPS requires GIMS to be properly installed. Once it is done SPS is able to connect to REFDB. Since REFDB is a read-only database, all your new diagrams or modifications to existing diagrams should be stored into additional GIMS databases. To allow MSPACE to use these database, you have to specify where they are located. This is achieved by clicking on the “Add GIMS Databases” button in the “Input/Output” tab of MSPACE. When MSPACE looks for a diagram, it searches first in the list of additional GIMS databases before looking into REFDB. As soon as the diagram is found, the search stops and the diagram is used. GIMS diagrams are used only for shaped beams; elliptical beams characteristics are loaded from the SPS database. SPS data must be matching diagram key elements: notice ID, notification reason, satellite name… World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Input (APL)
Users’ defined pattern The Antenna Patterns Library is a library containing all space and earth antenna patterns defined in the RR and in Recommendations. Similarly to the private GIMS database mechanism you can build your own antenna patterns libraries. Then, by clicking on the Add Antenna Library button, you select the libraries that MSPACE should use when looking for a pattern prior to searching in the standard pattern library. MSPACE could issue error messages coming from the APL library. You can find the APL messages explanation in the APL manual distributed with the SPS package. Programmatic mean of allowing SPS to use new antenna patterns. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Output
Text Files Not AP30B Output Database SPS_Reports MSPACE stores the calculation results: In a database (AP30, AP30A) In text files (AP30, AP30A, AP30B) SPS_Reports provides visual tools to analyze the results stored in the output database. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Output (DB)
Schema description in SPS manual Can hold results of multiple MSPACE runs (use vrs_no field). Not AP30B Output Database User Defined Queries Basic Queries The MSPACE output database, whose format is described in the MSPACE manual, contains calculations results: affected beams, PFD and margin values… With SPS_Reports you can produce reports showing these data. However, you may have to resort to building your own more sophisticated queries with MS Access. The output database is designed in such a way that one can store more than one set of calculation’s results. SPS_Reports World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Space Plans’ System Output (Text)
Findings File (.fnd) All plans Summary of affected beams Error and warning messages Reference Situation File (.ref) Only AP30B New reference values Detailed Report (.det) Only for one beam analysis Log intermediate values Used mainly for debugging Text Files MSPACE also outputs data to text files. The Findings file, usually with the extension fnd, lists the newly calculated margin and the current reference situation for each affected beam. Some warning and error messages are also written in this file. It is used both for BSS and FSS plans. The Reference Situation file, usually with the extension ref, is used only for FSS analysis. It lists, for each beam and for each test point, the aggregate and single-entry C/I values. Like for the input database, work is ongoing to store the FSS analysis results in the output database. The Detailed Report file, usually with the extension det, is used for storing intermediate calculation results. This file can be very big, which is why it you can create it only when performing a 1-beam analysis. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Runtime Reports in MSPACE_G
Reporting Runtime Reports in MSPACE_G SPS_Reports Output Database World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Built while MSPACEg is running Shows affected beams
Reporting in MSPACE_G Compressed Report Built while MSPACEg is running Shows affected beams Print at the end of the run Graphical Report At the end of the run Display affected test points Can copy map picture Lost when program closes Not available for AP30B While MSPACE is running, affected beams are displayed in the “Compressed Report” tab whenever they are discovered. At the end of the run, you can use the “Graphical Report” tab to visualize the position of the affected test points. These reports are lost when you close the MSPACE program. You can then use SPS_Report. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Reporting with SPS_Reports
Similar to Compressed Report in MSPACE_G PFD & EPM values Selection criteria Plot (affected) test points on map World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Exercises World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Exercise I : Reporting This exercise will show you how to use SPS_Reports and SpacePub to get the coordination requirements under a) & b) of Appendix 30. In the exercise scenario, you have just received BR IFIC 9999 that contains the Part A publication of three Article 4 networks. The database SPS_ALL_IFIC9999.mdb is the SPS database distributed on the BR IFIC CD. The three networks are: / R13DN-LINK R1&3 Down link / R13FD-LINK R1&3 Feeder link / R2-NETWORK R2 The exercise files are located into the Workshop folder whereas the Solution folder contains all input files and all output files that should have been created when you complete this workshop session. We will first use SPS_Reports to create a draft special section document. Start up SPS_Reports from the Start Menu. Open the database MSPACE Results.mdb in the folder Workshop\Part A\Results\R13 DL\. Note that SPS_Reports works with the output database that is also published on the BR IFIC CD. Click on the Compressed Report button. In the report window, select the option PFD and EPM and click on the button Create Draft of Special Section. Rename the file SS_AP_30C.rtf that was just created into DL_PartA.rtf. Have a look at that file to see the information it provides. Now we are going to run SpacePub to actually create a special section document. Start up SpacePub from the Start menu. Open the database sps_all_ific9999.mdb in the folder Workshop\Part A\Input\. SpacePub uses the SPS database where the BR stored the calculated reference situation and the list of affected administrations/networks. Select the Region 1&3 down link plan. Select the network The Special Section option is selected by default so you can just click on the Create Doc. button. Go to the last page of the document to see a table with affected administrations/networks. Note the differences between this document and the document creates with SPS_Reports. You can repeat the same exercise for the feeder link and region 2 networks. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Exercise II: SPS Package application - Part B analysis
You will now change the characteristics of your network in order to decrease the number of affected networks. Run MSPACE and check that less administrations are affected. Use GIBC to evaluate coordination requirements with terrestrial services and FSS networks. Sample MSPACEg Software Output Report Files Startup SpaceCap. Open the database SPS_ALL_IFIC9999.mdb in the folder Workshop\Part B\Input\. This is a copy of the SPS database as published on IFIC 9999. Export the notice into a new database Part B.mdb in Workshop\Part B\Input\. Uncheck the option Keep Findings and Ref. Situations. This is important to ensure that the notice is now viewed as an addition and not left as “Victim”, so that interference from it is calculated. Check the option Keep group ids of the source. Open the database Part B.mdb. Delete beams 5 and 6 and the group 384 in beam 3. Export the modified notice back into SPS_ALL_IFIC9999.mdb in the folder Workshop\Part B\Input\. Check the option Replace Notice in Target. Startup MSPACE As input database select SPS_ALL_IFIC9999.mdb in the folder Workshop\Part B\Input\. Select the R1&3 down link plan Accept the proposed output database name and findings file name. Start the analysis. Leave the analysis description empty. When the analysis is completed, go to the Compressed Report tab. Check the option PFD and EPM. Create a draft special section. Startup GIBC. Go to the tab PFD (Terrestrial serv.). Type in the network ID Select Trigger Limits as the Examination. Go to the Tools/Options tab. As the SRS Database, select SPS_ALL_IFIC9999.mdb in the folder Workshop\Part B\Input\. As Additional GIMS Database, choose gims.mdb in Workshop\Part B\Input\. Although all beams are elliptical, the PFD program does not take that information from the SPS database but from GIMS, which means that each ellipse defined in SPS must also be defined in a GIMS database. Start the analysis and check the file PFD.LST in the output folder. You may also run a PFD (Space serv.) analysis. If you do so, do not forget to add an Additional SRS DB in the Tools/Options tab; select the database srs.mdb in the folder Workshop\Part B\Input\. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

.fnd File R1&3 BSS Down link Analysis
World Radiocommunication Seminar Geneva, 30 October-3 November 2006

.fnd File FSS Appendix 30B Analysis
World Radiocommunication Seminar Geneva, 30 October-3 November 2006

.ref File FSS AP30B Analysis
Calculated Reference Situation World Radiocommunication Seminar Geneva, 30 October-3 November 2006

BR Software Package GIBC (Graphical Interface for Batch Calculations)
BR Seminar - Workshop Geneva 30/10 – 03/11/2006 World Radiocommunication Seminar Geneva, 30 October-3 November 2006

GIBC World Radiocommunication Seminar Geneva, 30 October-3 November 2006

What’s the Purpose of GIBC?
PFD Analysis Terrestrial PFD Analysis Space Inter-service, inter-regions coordination requirements GIBC performs three types of analysis in a sort of batch mode analysis: A PFD analysis where criteria to protect terrestrial services are evaluated. A PFD analysis where criteria to protect space services are evaluated. A ΔT/T (Appendix 8) analysis where criteria to protect space services are evaluated. ΔT/T World Radiocommunication Seminar Geneva, 30 October-3 November 2006

SPS SRS GIBC Input/Output Planned Data Unplanned Data Text Files
For historical reasons, GIBC applications load the elliptical data from the GIMS database. This means that all ellipses defined in the SPS database must have their counterpart in the GIMS reference database (or in an additional database). Text Files Elliptical Beams GIMS Database World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection of Terrestrial Services
SPS DB path GIMS DBs Select PFD (terrestrial) Type in ID of notice to examine Select Trigger Limits Articles d) and d) of Appendix 30 require the protection of terrestrial services. PFD limits are described in Section 4 of Annex 1 to Appendix 30. The PFD (terrestrial serv.) analysis checks the PFD of all emissions of a network against the PFD limits that applies. In the “Tools/Options” tab you have to set the path of the SPS database where data for the analyzed network should be stored. Like in MSPACE you can also define additional GIMS databases that are used in a similar manner. Also like in MSPACE the connection to the GIMS reference database is automatic provided that GIMS is installed correctly. The GIMS Appendix 30 PFD interactive analysis can perform the same PFD analysis although limited to a particular assignment of a beam. ID of notice in corresponding plan World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection of Terrestrial Services
Output Files C:\PFDRESULTS\ MSG.LST Error messages Always check ! PFD.LST Report file Affected administrations Beam Antenna Gain Class of Station Central Frequency Power Power Density Provision & Incoming Service Protected Area Test point & country At the test point: gain, PFD, PFD excess, PFD limit Countries and PFD excess Notice ID Group ID The PFD analysis results are stored in the C:\PFDRESULTS\ folder. Many files are created but two are really worth looking at. MSG.LST contains error messages. PFD.LST contains the list of affected administrations with the details of the affecting assignment and the PFD excess values. The picture in the slide describes the most important fields. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection of Space Services
SPS DB path SNS DB path GIMS DBs Select PFD (space serv.) Type in ID of notice to examine The RR also define PFD criteria for the protection of FSS networks from BSS network interference (and vice versa) and also for inter-region BSS/BSS interference. The PFD (Space serv.) analysis checks the PFD produced by all assignments of a given network against all applicable limits for each potentially affected network. Note that for this analysis, in addition to the GIMS reference database, two databases are required: SPS and SRS. The GIMS Appendix 30 PFD interactive analysis can perform the same PFD analysis although limited to a particular assignment of a beam and a given orbital separation. However the interactive tool may be useful to visualize where the PFD excess occurs. ID of notice in corresponding plan World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection of Space Services (PFD)
Output Files C:\PXTRESULTS\ MSG.LST Error messages Always check ! PXT.LST Report file Affected administrations Gain Administration Beam Sat. Pos. Central Frequency Date of Receipt ID of notice/group/assignment Sat. Name Incoming Power Power density Existing Date of protection Provision & Service Class of Station Protected Area Affected test point & country At test point: gain, PFD, PFD excess, PFD limit The PFD analysis results are stored in the C:\PXTRESULTS\ folder. Many files are created but two are really worth looking at. MSG.LST contains error messages. PXT.LST contains the list of affected networks. Summary of affected administration World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Database that contains the network to analyze
GIBC Tool/Options Database that contains the network to analyze When performing PFD (Space serv) or Appendix 8 analysis involving the protection of networks in the planned services it is required to specify the path of both an SPS and an SNS database. The field “SRS Database” should hold the path of the database where the analyzed network is stored. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection of Space Services (ΔT/T)
SPS DB path SNS DB path GIMS DBs Select Appendix 8 Activate Appendix 8 Case II Type in ID of notice to examine Protection of FSS uplink, BSS (planned and unplanned) feeder-link is ensured by ΔT/T criteria. The Appendix 8 analysis checks the ΔT/T limits for each relevant pairs of networks made of the analyzed network and all possible interfering networks. Note that for this analysis, in addition to the GIMS reference database, two databases are required: SPS and SRS. In the “Tools/Options” tab, the field “SRS Database” should hold the path of the database where the analyzed network is stored. To be complete, you should check the option App 8 Case II that is used to calculate interference between satellites sharing the same frequency bands in opposite directions of transmission. World Radiocommunication Seminar Geneva, 30 October-3 November 2006

Protection of Space Services (ΔT/T)
Output Files C:\APP8RESULTS\ MSG.LST Error messages Always check ! APP8.LST and APP8_OPT.LST Report file Affected administrations Sat. Name Administration Power Beam Gain Central Frequency Sat. Pos. Date of Receipt ΔT/T Inc. ID of notice/group/assignment Date of protection ΔT/T analysis is made in accordance with Appendix 8. The results are stored in the folder C:\APP8RESULTS. The file MSG.LST contains error messages and should always be looked at especially to verify that all required GIMS diagrams have been found. The file APP8.LST shows the affected networks if any. The file APP8_OPT.LST shows networks affected by the optional ΔT/T analysis; in some cases the “arc concept” is the coordination criteria and ΔT/T criteria is only for information purposes (see Appendix 5 of RR). Exi. Power density Class of Station Associated earth station World Radiocommunication Seminar Geneva, 30 October-3 November 2006

BR Seminar - Workshop Geneva 30/10 – 03/11/2006

Similar presentations

Presentation on theme: "BR Seminar - Workshop Geneva 30/10 – 03/11/2006"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

BR Seminar - Workshop Geneva 30/10 – 03/11/2006

Similar presentations

Presentation on theme: "BR Seminar - Workshop Geneva 30/10 – 03/11/2006"— Presentation transcript:

Similar presentations

About project

Feedback