Committed to connecting the world

Search
Girls in ICT

Non-geostationary-satellite networks (Non-GSO)

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ITU Regulatory Procedure​s

​There are two main regulatory procedures for non-GSO​ satellite networks, ​​either subject or not subject to coordination​​:

Establishment of whether to start from API or Coordination Request

To know whether a particular service in a frequency band is subject to coordination, kindly consult the Table of Frequency Allocations in Article 5 of the Radio Regulations. The most common coordination procedures for non-GSO satellite networks are No.9.11A and No.9.21. For a list of frequency bands/services that are subject to No.9.11A, the table "TABLE 9.11A-1" of the Rules of Procedure can be helpful.

For those not subject to coordination, the first step is to submit an advance publication information (API) to the Bureau (No.9.1), followed by a notification for recording within 7 years from the date of receipt of the API.

For those subject to coordination, the first step is to submit a request for coordination to the Bureau (No.9.30), followed by a notification for recording within 7 years from the date of receipt of the request for coordination.

Data required 

As compared to GSO satellite networks, it should be noted that non-GSO ​satellite networks have additional data requirements as specified in Appendix 4 of the Radio Regulations.​

For all non-GSO satellite networks, it is first necessary to specify whether the reference body is the Earth or other objects (e.g. Moon), and provide the the number of orbital planes.

For those where the reference body is the Earth, the basic list of orbital parameters required to describe the non-GSO satellite networks include for each orbital plane, the inclination, the number of satellites per plane and the period.

However, for non-GSO satellite networks that are considered as "constellation", additional orbital parameters are required, this include the initial phase angles, Longitude of ascending nodes etc..​

For those non-GSO satellite networks that are subject to coordination under Nos. 9.11A, 9.12 or 9.12A, the RAAN value must additionally be provided.  Other additional parameters required include the orientation angles alpha and beta of each beam, satellite antenna gain as a function of elevation angle, maximum and average beam peak eirp etc. 

Next, for those non-GSO satellite networks that are subject to Nos. 22.5C, 22.5D. 22.5F or 22.5L, even more orbital parameters are required, including whether the space station uses station-keeping to maintain a repeating ground track, and if the space station uses station-keeping to maintain a repeating ground track, the time in seconds that it takes for the constellation to return to its starting position, i.e. such that all satellites are in the same location with respect to the​​​ Earth and each other, specific precession rate etc.. In addition, many additional parameters required for the evaluation of EPFD such as the PFD/EIRP masks, information on the exclusion zone etc. are required.
 

Submission of information for the ITU filing 

  • ​​Submission format​

A satellite network filing normally contains two mdb files, one in the SNS format and the other in the GIMS graphical format, except for some information to be provided in attachment as well as those concerning the PFD, EIRP masks. 
The one in the SNS format should be captured using the BR software SpaceCap, and the one in the graphical format should be captured using the BR software GIMS. All BR space software are available for free download from our webpage: BR space software​

  • ​​​​​​Submission portal​​

The complete files should be submitted through the e-Submission system​ by the administration. 
See our ​webpage on e-Subm​ission​​ for more information​. 


RR Article 22 EPFD examination

​Resolution 85 (WRC-03) requires the Bureau to verify compliance of frequency assignments of non-GSO fixed satellite service  systems with the single-entry equivalent-power flux density (EPFD) limits in Tables 22-1A, 22-1B, 22-1C, 22-1D, 22-1E, 22 2 and 22-3 of Article 22 of the Radio Regulations and to determine the coordination requirements under Nos. 9.7A and 9.7B.

EPFD validation results as well as description and status of EPFD validation can be found below:

Supplementary interference analysis

​Since coordination requirements are established based on frequency overlap only, in the absence of appropriate criteria or calculation methods to verify that there is no increase of interference or protection, to certify that Rules of procedure on No. 9.27 are met administrations may submit justifications based on static and dynamic interference assessments. For the later one, calculation may be e.g. in the form of a cumulative​distribution function of the interference level, expressed as an interference-to-noise (I/N) ratio for varying percentages of time and locations into the subsequently filed non-GSO FSS systems.

Information submitted by administrations and studied by the Bureau can be found below.​


Resolution - 35 (WRC-19)

​The Resolution 35 (WRC-19) defines a milestone-based approach for the implementation of frequency assignments to space stations in a non-GSO satellite system in specific frequency bands and servic​es.

The notifying administration should submit deployment information at four stages using the e-submission system with the Res 35 online capture tool or by uploading a XML file in the relevant format.

​

Resolution - 770 (WRC-19)

​Resolution 770 (WRC-19) concerns non-GSO fixed-satellite service systems in the frequency bands 37.5-39.5 GHz, 39.5-42.5 GHz, 47.2-50.2 GHz and 50.4-51.4 GHz.

Since the Radiocommunication Bureau is currently unable to examine non-GSO FSS systems subject to the single-entry provision given in No. 22.5L due to a lack of available software, the notifying administration shall send BR a commitment that the non-GSO FSS system complies with the limits given in No. 22.5L, and provide all the required input parameters needed.

Useful links

Guides for submissions

Videos for capture

Guidlines for capture

© ITU All Rights Reserved

Back to top