Committed to connecting the world

SDG

Small Satellites Support

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​Small satellites generally follow the procedure for non-geostationary satellite networks not subject to coordination, which starts with the submission of the advance publication information (API). 

​​u Regulatory procedures for small satellites​ 

​​​u Small Satellite Handbook - Currently under development at ITU-R Working Party (WP 4A​​)

​Noting that the trend of development and utilization of small satellite technologies is a global phenomenon, and it is expected to bring benefits to the entire world, including both developed and developing economies, the ITU-R membership has expressed a strong desire and need to develop an ITU-R Small Satellite Handbook in various ITU-R conferences, assemblies and meetings. 

Small Satellite Handbook

  Currently under development at ITU-R WP 4A
Proposals from the broadest possible stakeholders (e.g. academia, operators, manufacturers, launch service providers and administrators etc.), are sought for this activity. 
Any proposals from ITU-R members should be submitted directly to WP 4A in accordance with Res ITU-R 1-8. 

Submissions from other organizations/entities which are not members of ITU-R could be addressed to SmallSatHB@itu.int​.​These submissions could be prepared as inputs to WP 4A.​ 


​​

Amateur-satellite service

In the same way as for other space services, an API must be prepared and submitted to the ITU for satellite networks operating in the amateur-satellite service . Please note that the API must be submitted to the ITU before requesting for frequency coordination with IARU.

Administrations authorizing space stations in the amateur-satellite service shall ensure that sufficient earth command stations are established before launch to ensure that any harmful interference caused by emissions from a station in the amateur-satellite service can be terminated immediately (see No. 25.11).

Amateur-satellite service is exempted from cost recovery fee. Note that, for a filing to benefit from this, there should be only one main service (EA) in the filing, and no other services (e.g. EW, EH, ET) should be present.​​​​

BR would like to remind Administrations preparing an API for the amateur satellite service that, to take into account possible change in frequency bands following the frequency coordination/consultation process with IARU, avoid submitting a very narrow frequency band at the API. If the frequency finally selected is outside of the band filed in the API, a new API will have to be submitted.

​​​  · ITU-R CR/303 letter related to Amateur-satellite service

​  · Amateur and Amateur-satellite service Handbook 

Guide to preparation of filings for small satellites

​​

For small satellites, it is common to make use of frequency bands that are not subject to coordination. In this case, the first step to registering your frequency assignments is to submit the advance publication infomation, or API in short. Please visit the following page for information about how to prepare and submit an API:

API page

Here is a guide on how to create a notification filing from the API:

​​How to prepare a notification for recording filing from the API?

BR software required for capture and validation


To view the sample mdb file as well as to make changes to it, you will require the BR software SpaceCap. To help to make sure that all mandatory information have been captured, you will need SpaceVal. Both of these software are available at the following page:

​​​BR software required for capture and validation of filings 

Filings with complete information should be submitted to the ITU via the national administration, using the online submission system: 

E-Submissions for satellite network filings ​