导航|地址|刷新
API - Advance Publication Information

Connecting the world and beyond

Advanced Search

ITU

General Secretariat

Radiocommunication
About ITU-R

Events

Databases & e-Services

Publications

Space

Terrestrial

Study Groups

Regional Presence

Join ITU-R

Standardization

Development

News

Members' Zone

Join ITU

API - Advance Publication Information

Rollup Image

You are hereITU > Homepage > ITU-R > Space Services

Share

Space Services Department

News

Space Support

BR IFIC

Preface

Cost Recovery

non-GSO satellite networks

Space Plans

Databases and Services

Space Regulatory Hub

Space Explorer

Recent

Page Content 20

  API is a mandatory procedure under Section I of Article 9 of the Radio Regulations
for all satellite networks not subject to coordination.

For non-geostationary satellite networks, this procedure is applicable to all those frequency bands/service not subject to the coordination.

For geostationary satellite networks, this procedure is applicable only to the use of inter-satellite links communicating with a non-geostationary space station which are not subject to the coordination.

The characteristics of the network required for submission is defined in Appendix 4 and are published by the ITU Bureau in an API/A special section.

To know whether a frequency band is subject to coordination, check the footnotes in the Table of Frequency Allocations in Article 5, in particular attention to requirements to coordinate under No.9.11A and the sub provisions Nos.9.12 and 9.12A, or the requirement to seek agreement under No.9.21. For coordination under No.9.11A (and Nos.9.12 and 9.12A), please note §2.3 of Rules of Procedure related to No.9.11A, and note that the procedure is applicable to all other space and terrestrial services with respect to those satellite services having allocations with equal rights and mentioned in the specific footnotes to which this provision applies (check TABLE9.11A-1).

Here is a chart on the overall regulatory procedure for non-geostationary satellite networks not subject to coordination

Guides for capture and submission of API

Page Content 9

Presentation on how to prepare and submit an API

Presentation on how to capture diagrams in GIMs format

Submission of graphical information for non-GSO

Guide to capturing diagrams and attachments for non-GSO using BR software SpaceCap and BR-SIS Validation

Guide to capturing information for operating agency

Guideline of the conversion from API to Notification

Video guides

Video on API capture with SpaceCap

Video on how to prepare diagrams for capture in GIMs

Video on how to capture diagrams for API with GIMs

Video on how to run cross validation

Sample notice databases

Page Content 10

The following are some sample databases that you can download to view, or to use as a starting point to create your notice:

Sample API database without diagrams (SNS format mdb)

Sample API databases with diagrams (SNS format mdb, GIMS format mdb)

Sample GIMS file showing various type of diagrams (GIMS format mdb)

Modifications required for API

Page Content 18

Amendments to the information for NGSO filing that requires a new API are:

• Additional frequency band

• Modification of the direction of transmission

• Modification of reference body

However, it is a good practice to submit a modification to the API any change in characteristics including orbital characteristics, service area (adding earth stations) etc.

This will allow other administrations/operators the chance to submit comments before the modifications are notified for recording in the Master Register.

Useful Links

Page Content 19

BR software required for capture and validation of filings

Non-geostationary-satellite Networks

Small Satellite Support

Small Satellite Handbook

Antenna Pattern Library (APL)

Submission of inter-satellite links

Res32 (WRC-19) Non-GSO SDM

e-Submission for satellite network filings

e-Communications for administrative correspondences
related to Space Services

Active and Passive Sensors

Page Content 6

The following specific information is required for sensors:

Active Sensors

• For transmitting beam

   - Mean peak power and mean power density

   - Pulse length and pulse repetition frequency

• For receiving beam

     - Receiver noise bandwidth

   - Noise temperature at output of signal processor

• For active sensor, please ensure that

   - the active sensor (class of station E1 or E3) must be captured for both transmitting and receiving beams with the same beam name covering the same frequency band.

Passive sensors

  - Observed bandwidth

  - Sensitivity

To capture sensor information in SpaceCap,
go toBeam tab, check the box “Beam has Sensors”

Antenna Radiation Pattern

Page Content 7

For the co-polar antenna radiation patterns submitted as images in Gims database, kindly submit the appropriate diagrams which meet the requirements as follows:

the co-polar antenna radiation pattern must be plotted as the antenna gain (dBi) as a function of the off-axis angle in degrees;

the antenna gain must be defined for all off-axis angles in the range between 0 and +/-180 degrees;

the antenna gain at 0 degrees must correspond to the respective maximum antenna gain for the same beam or associated Earth station as you have captured in the notice database;

for any off-axis angle, only one gain value shall be defined, therefore, it's not encouraged to have more than one diagrams to describe the same antenna;

the X and Y axes should be clearly and legibly labelled;

all values should be compatible with the notice database;

the image must be sufficiently good quality that can be clearly viewed in Gims by others.

Alternatively, kindly consult the Bureau's documentation on Antenna Pattern Library (APL) online, which contains the description of antennas, available at http://www.itu.int/en/ITU-R/software/Pages/ant-pattern.aspx , and capture the pattern IDs in your notice database which can represent the characteristics
of your antennas if possible.

If it's provided as equations, formulae, or a table describing all parts of the pattern as mentioned above, the Bureau will then assign the pattern ID in the said Antenna Pattern Library and capture the pattern ID in the notice database, when possible, for publication. Diagrams as images are not usable by technical examination software at the notification stage.

Once the maximum isotropic gain for a space station is less than or equal to 5 dBi, it is encouraged to use pattern IDs 609 / 610 to denote the antenna pattern for the non-directional antenna for the space station.

Please be aware that the cross-validation option of the BRSIS Validation software must be executed when validating the SNS format database against the GIMS format database, if any, for all notices in order to overcome any difficulties identified in the validation report for your notice before it is submitted to the Bureau in accordance with section § 3.4 of the Rules of Procedure concerning the Receivability of forms of notice.

Page Content 11

Page Content 12

Page Content 2

Page Content 3

Page Content 4

Page Content 5

Page Content 13

Page Content 14

Page Content 15

Page Content 16

Follow us

Twitter

Facebook

YouTube

Flickr

Linkedin

Instagram

Soundcloud

Podcasts

Spotify

Spreaker

TikTok

© ITU All Rights Reserved

Contact us

Terms of Use

Privacy notice

Accessibility

Report misconduct

Back to top

------
导航页打开网址