Title: RECEIVABILITY OF THE SPACE NOTICES Istvn BOZSKI BR SSDSPR
1 RECEIVABILITY OF THE SPACE NOTICESIstván
BOZSÓKI BR SSD/SPR
- Biennial Seminar of the Radiocommunication
BureauGeneva 30 October-3 November 2006
2Basic Rules of Procedure (ROP) related to the
Receipt of notices - BR registry date
RECEIVABILITY OF THE NOTICES
- ROP 2 - It is incumbent on all ADM to meet
deadlines established in the RR and, accordingly,
to take account of possible mail delays, holidays
or periods during which ITU may be closed. - Having regard to the various means available for
transmission and delivery of notices and other
related correspondence - Mail received through the postal service shall be
recorded as received on the first working day on
which it is delivered to the ITU/BRs offices in
Geneva. Where the mail is subject to a regulatory
time limit that occurs on a date on which ITU is
closed, the mail should be accepted if it has
been recorded as received on the first working
day following the period of closure - E-mail or telefax documents shall be recorded as
received on the actual date of receipt,
irrespective of whether or not that is a working
day at the ITU/BRs offices in Geneva - In the case of E-mails, an administration is
required to send, within 7 days of the date of
the E-mail, a confirmation by either telefax or
mail which shall be regarded as being received on
the same date as the original E-mail.
3Processing of Satellite Network Filings -
RECEIVABILITY
CORRESPONDENCE WITH ADMINISTRATIONS
GIMS DB
BR CENTRAL REG I STRY
ISSUE COST RECOVERY INVOICES
Electronic Notices
SSD REG I STRY
GRAPHICAL DATA CAPTURE
REGULATORY DATE OF RECEIPT
COORDINATION RES 49
VALIDATION COMPLETENESS FOR COORDINATION AND
NOTIFICATION
FIRST VALIDATION AND RECEIVABILITY CHECK
EXAMinSSC
DATA MANAGEMENT
NOTIFICATION
PUBLISH IN BR IFIC
AS RECEIVED
API
PART I-S
PUBLISH IN BR IFIC
BR IFIC
API/A
BR WEB
SNS
ISSUE COST RECOVERY INVOICES
SNTRACK
SNL
BR WEB
BR DOCUMENTUM DATABASE
4Processing of Satellite Network Filings
PUBLICATION
COORDINATION
UPDATE LIST OF AFFECTED ADMs AND NETWORKs
ISSUE COST RECOVERY INVOICES
BR WEB
COORDINATION
PUBLISH IN BR IFIC
CAPTURE OF FINDINGS, SPLIT GROUPS
SPECIAL SECTIONS
EXAM inSSC
PART II-S, III-S
PART III-S RETURN NOTIFICATION NOTICES WITH
UNFAVOURABLE FINDINGS EXPLANATIONS TO
ADMINISTRATIONS
PART II-S UPDATE MASTER REGISTER
CAPTURE OF FINDINGS, SPLIT GROUPS
NOTIFICATION
NOTIFICATION
SNS
SPACE NETWORK LIST
5RECEIVABILITY OF THE NOTICES
Establishment of Date of Receipt (1)
- Entry examination of the notice received by the
Bureau - submission of information in electronic format
(RES 55) - in application of the Radio Regulations
- in application of the Rules of Procedures
approved by the RRB concerning the Receivability
of forms of notice - paragraphs 3.2 and 3.3 of the ROP vis à vis
mandatory information its completeness (Annex 2
of AP 4) and correctness - use of the validation
SW by the ADM - Result of the entry examination
- Confirmation of the BR registry date -
establishment of the formal regulatory date of
receipt
6Establishment of Date of Receipt (2)
RECEIVABILITY OF THE NOTICES
- Formal date of receipt is established when the
Bureau confirms that the information submitted is
complete and checks the correctness (using
validation soft) - Accordingly, where a notice does not contain all
of the mandatory information as defined in the AP
4 of the RR, or for example - the email from ADM
is without attached data or a letter with an
empty CD-ROM etc, further processing of the
notice will remain in abeyance and a date of
receipt will not be established until the missing
information is received - If all mandatory data have been submitted and
further clarification is required concerning the
correctness of the mandatory data, the Bureau
shall request the ADMto provide the
clarification within 30 days.
7RECEIVABILITY OF THE NOTICES
Establishment of Date of Receipt (3)
- If the information is received within the 30 days
period, the original date of receipt is retained,
otherwise, a new date of receipt will be
established - Nevertheless, for replies received within the
above period of 30 days, a new formal date of
receipt is established in those cases (or for the
concerned part of the network) where the
information submitted subsequently is outside the
scope and beyond the objective of the Bureaus
enquiry, if the new or modified data has impact
on the regulatory and technical examination,
irrespective of whether the newly provided
information adds new affected administrations or
not - The Bureau is keeping any pending submission
containing incomplete information for one year.
8RECEIVABILITY OF THE NOTICES
Establishment of Date of Receipt (4)
- When a Coordination request or Notification is
communicated to the Bureau at the same time as
the API, the formal date of receipt of this
information (No. 9.1) is established as follows - For the Assignments that require coordination
under Sect II of Article 9 - 6 months after the date of receipt of API
- For the Assignments that do not require
coordination under Sect II of Article 9 - 6 months after the date of publication of API
9List of as received
RECEIVABILITY OF THE NOTICES
- Coordination Requests or Notifications as
received are made available by the BR within 30
days (RES 55) - International Frequency Information Circular BR
IFIC (Space services) CD-ROM - This information can also be monitored through
the ITU website ITU ? Radiocommunication ? Space
Services ? BR IFIC ? List of information as
received at http//www.itu.int/ITU-R/space/brif
ic/asreceived/ - This advance version of the information received
from the ADM with a date of receipt in the
registry of the Bureau is not to be confused
with the official publication of the relevant
PART or Special section with a formal date of
receipt which is yet to occur
10ADVANCE PUBLICATION INFORMATION (API) ART 9
Sect. I
If incomplete
9.1 9.2
9.2B
AP4/V 1)
Send to the BR not earlier than 7 years, and not
later than 2 years before the dBiU
Publication of API within 3 months
RR Provisions applicable
ADM
AP4 DATA
Formal (regulatory) date of receipt
AP4/VI 2)
1) SECTION IA. Non GSO not subject to
Coordination under Section II of Article 9, 2)
SECTION IB. GSO or non GSO subject to
Coordination under Section II of Article 9.
2c date extentions 11.44
If the information under 9.30 (CR - 9.7, 9.14
and 9.21) AP4 data is not received within 24
months after the date of receipt of the relevant
information under 9.1
Coordination or notification can be send at the
same time with API
9.5D RES51
If the coordination is required by Section II of
Article 9, It shall be considered that
Coordination request as having been received not
earlier than 6 months after the date of receipt
of API
If the coordination is not required by Section II
of Article 9, notification date of receipt shall
be 6 months after the date of publication of API
Information published under 9.2B shall be
cancelled
11API (1)
RECEIVABILITY OF THE NOTICES
- API phase is obligatory, before coordination
phase or notification - No priority in being first to start advance
publication - Starts the regulatory clock
12RECEIVABILITY OF THE NOTICES
API (2)
- Relevant Rules of Procedure on Receivability
- 1 electronic filing (resolves 5 of RES55)
- 3.2 completeness (Annex 2 of AP 4) and
correctness of the information - 3.5 No validation software yet if Bureau finds
information incomplete or incorrect, shall
request the ADM to provide the clarification
within 30 days - 4.1 API not earlier then 7 years before dBiU
- Select the proper notice form
- AP4/V coordination not required (non-GSO, GEO
--gtnon-GSO) - AP4/VI coordination required (GEO, non-GSO)
- mixed
13API (3)
RECEIVABILITY OF THE NOTICES
- Submission of MOD is required and the API have to
be recorded with a new date of receipt (No. 9.2)
- for new frequency band(s)
- for a change of GSO orbital location by more
than /- 6 degrees - if no CR within 24 months from API receipt(No.
9.5D apply)
14COORDINATION PROCEDURE (CR) - ART 9 Section IIA
Checking with API Checking with RES51
Modification of orbital positions within /- 6
deg.
RULES OF PROCEDURES
Within 4 months
PUBLICATION
9.38
AP4 DATA Electronic Notices 9.30
Data management graphical information
CR/C
First validation Receivability check
REG TECH EXAMINATION FINDINGS
Coordination requirement under 9.7 - 9.14 9.21
Regulatory Date of Receipt
Validation Completeness
ADM
Publication in BR IFIC as received With BR
Registry Date
Coordination request can be send at the same time
with API
BR Enter unfavourable findings
UnfavourableFINDINGS
It shall be considered that Coordination request
as having been received 6 months after the date
of receipt of API
15Coordination Request (1)
RECEIVABILITY OF THE NOTICES
- No. 9.1 - CR shall be considered as having been
received not earlier than 6 months after date of
reception of the API - No. 9.2 Check modification of the orbital
position whether not more than /-6 degrees
vis-à-vis the API - No. 9.5D - CR is received within 2 years after
the date of reception of the API (frequency
bands!) - Check date of bringing into use (dBiU) with
respect to No. 11.44 - - max 7 years after date of receipt of the API
- - or max. 9 years after the date of publication
of the API if it was received prior to
22.11.1997
16Coordination Request (2)
RECEIVABILITY OF THE NOTICES
- Validation of graphical data
- ART 5 (Regional service area restrictions)
- AP4 and CR 58 and IFRB Circular Letter 769
- Steerable beams (No. 1.191, AP4 B.3.b)
- The maximum co-polar isotropic gain, in dBi is
required where a steerable beam (see No. 1.191)
is used if the effective boresight area (see No.
1.175) is identical with the global service area,
the maximum antenna gain, in dBi, is applicable
to all points on the Earths visible surface
17Coordination Request (3)
RECEIVABILITY OF THE NOTICES
- Validation of graphical data
- GSO diagrams (AP4 B.3.e)
- if the space station is operating in a band
allocated in the Earth-to-space direction and in
the space-to-Earth direction, the gain of the
antenna in the direction of those parts of the
geostationary-satellite orbit which are not
obstructed by the Earth - Check with respect to ROP
- No. 21.16 PFD limits for steerable beams
- No. 23.13 - Disagreement by and ADM on the
inclusion of its territory in the service area of
a BSS (except sound broadcasting) network
18Coordination Request (4)
RECEIVABILITY OF THE NOTICES
- Validation of graphical data
- Antenna Gain contours AP4 B.3.b.1 requirements
- The co-polar antenna gain contours plotted on a
map of the Earths surface, preferably in a
radial projection from the satellite onto a plane
perpendicular to the axis from the centre of the
Earth to the satellite - The space station antenna gain contours shall be
drawn as isolines of the isotropic gain, at least
for -2,-4,-6,-10 and -20 dB and at 10 dB
intervals thereafter relative to the maximum
antenna gain - Where a steerable beam (see No. 1.191) is used,
if the effective boresight area (see No. 1.175)
is less than the global service area, the
contours are the result of moving the boresight
of the steerable beam around the limit defined by
the effective boresight area and are to be
provided as described above but shall also
include the 0 dB relative gain isoline - The antenna gain contours shall include the
effects of the planned inclination excursion,
longitudinal tolerance and the planned pointing
accuracy of the antenna
19NOTIFICATION - ART 11 Notification and Recording
Section I Section II
11.25
11.44.1
11.44
Not earlier than 3 years before brought into use
AP4 DATA Electronic Notices
- Assignments brought into use prior to completion
of coordination - If RES49 data submitted
- to be taken into consideration for 7 years from
date of receipt of API - if API has been received prior to 22 November
1997, corresponding period will be 9 years from
the API publication.
Notified date of bringing into use shall be not
later than 7 years following the date of receipt
under 9.1
No Coordination Under Section II Art 9
Publication in BR IFIC AS RECEIVED With BR
Registry Date
Notification date shall be 6 months after the
date of publication of API
11.27
Completeness check characteristics specified in
AP4
SPACE STATIONS
Needs Coordination Under Section II Art 9
11.15
11.28
Regulatory Date of Receipt
ADM
11.46
Coordination request is not yet received
11.30
Examination of Notices
RESUBMISSION If resubmitted notice is received
more than 6 months after the date on which the
original notice was returned Considered as a NEW
NOTICE
UNFAVOURABLE
FAVOURABLE
Is supported by a space API
11.36
EARTH STATIONS
Conformity with table of frequency allocations
11.31
Return
NO
4.4
11.37
Incomplete
The coordination with other administrations 11.32
11.48
If the Coordination is not required, Notification
can be send at the same time with API
When the information is incorrect or
incomplete BR will request the ADM to provide
the information within 30 days
If after expiry of the period of 7 years
frequency assignments has not brought into use
information published under 9.2B and 9.38 shall
be cancelled
11.38
Probability of harmful interference 11.32A,
11.33
NO
Maintain the initial date of receipt
Publication in Part IS of the BR IFIC
If the information is received within 30 days
ADM
MIFR
YES
20Notification (1)
RECEIVABILITY OF THE NOTICES
- Notification not earlier than 3 years before dBiU
(No. 11.25) - Nos. 11.44, 11.44.1 and 11.48
- maximum regulatory period for bringing an
assignment into use and submission of the first
notification request (7 / 9 years ) - 11.44.1 assignment brought into use prior
completion of the coordination process and RES 49
have been submitted first notification by the
end of 7 / 9 years following No. 9.1 or 9.2 - 11.48 expiry of bringing into use of a network
- ROP 4.3 multiple procedures (API (C) N)
- previously applicable procedures have to be
effected - for earth station associated space station
supported by an API - resolves 6 of RES49 (Rev. WRC-03)
- SUP if no administrative due diligence
information until the deadline (deadlines in
resolves 2 and 2bis) - BR reminders (3 or 6 months before the expiry
date)
21Notification (2) - Non-Receivable Notices
RECEIVABILITY OF THE NOTICES
- Mandatory data has not been provided or in
incorrect format (paper) - A notification received by the Bureau earlier
than the prescribed date limit in No. 11.25 - A notice for a particular procedure is receivable
only if the previously applicable procedures have
been effected. If not, the notice will be deemed
not receivable. - Examples
- A notification relating to a satellite network,
or an earth station whose associated space
station, is not supported by an API - A notification relating to a satellite network
which is not supported by a publication of
coordination request - The regulatory time limit specified in No. 11.44
has expired or the due diligence information as
prescribed by Resolution 49 has not been provided
22Notification (3) - Useful Reminders
RECEIVABILITY OF THE NOTICES
- Ensure forms are filled up accurately and
correctly use SpaceCap, GIMS and SpaceVal
software for preparation of submissions in
electronic format - Submit forms in electronic format Access files
with .mdb extension, and not the Acrobat (.PDF)
or Word (.doc) files, should be submitted to the
Bureau - Ensure most up-to-date coordination information
has been provided - Ensure the relevant API and Coordination Special
Sections exist for the assignments being notified
- Take note of the time constraints of Nos. 11.44,
11.44.1 (RES49), No.11.43A and 11.25
23Notification (4) -Time Constraints
RECEIVABILITY OF THE NOTICES
- No. 11.25
- Notice shall reach the Bureau not earlier than 3
years before date of bringing into use of the
assignment - No. 11.43A
- Any change to the characteristics of an
assignment that has been notified and confirmed
as having been brought into use shall be brought
into use within five years from the date of the
notification of the modification. - No. 11.44
- Notified date of bringing into use shall be not
later than 7 or 9 years from the date of the
relevant API - No. 11.44.1 (notification prior completion of the
coord and RES49 is OK) - The first notice for recording of the assignments
must be within 7 or 9 years from the date of
the relevant API - Note
- max 7 years after date of receipt of the API
- max. 9 years after the date of publication if the
API was received prior to 22.11.1997
24RECEIVABILITY OF THE NOTICES
Notification (5) - Earth station
- General conditions for receivability apply
- Additional condition for receivability of an
earth station is that the corresponding space
station have to be supported by the related API
25Notification (6) Publication of Complete
Notification
RECEIVABILITY OF THE NOTICES
- Complete notices are published in PART I-S of the
BR IFIC (Space services) with the date of
receipt. This publication shall constitute the
acknowledgement to the notifying ADM of receipt
of its notice. - Complete notices will be used for further
technical and regulatory examination by the
Bureau and may differ from those published as
received
26How to submit filing to the Bureau? (1)
RECEIVABILITY OF THE NOTICES
- When Administrations submit electronic filings to
the Bureau ( on diskette, CD-ROM or as email
attachment) for several satellite networks or
earth stations, each network or station should be
filed in a separate Directory or Folder. - Each Directory/Folder should then contain the
following files, as appropriate, for that
particular network or station - One Network_Name/Station_Name.mdb file in the SNS
file format (this file should contain only ONE
network !!) - Several Beam_Name.gxt files (if diagrams are
being provided in the GIMS file format) - One or several files for the submission of
graphical data, not in the GIMS file format - One Network_Name/Station_Name.doc file (for any
comments pertaining to the network or station)
27How to submit filing to the Bureau? (2)
RECEIVABILITY OF THE NOTICES
28How to submit filing to the Bureau? (3)
RECEIVABILITY OF THE NOTICES
- When zipped files are submitted, each satellite
network or earth station should be zipped
separately. This is especially important when
notices are submitted by e-mail, which should
only be sent to the official BR e-mail address
brmail_at_itu.int
29Basic ROP related to submission of the notices
RECEIVABILITY OF THE NOTICES
- All mail must be sent to the following address
- Radiocommunication Bureau
- International Telecommunication Union
- Place des Nations
- CH-1211 Geneva 20
- Switzerland
- All telefaxes must be sent to41 22 730 5785
(several lines) - All E-mail must be sent to brmail_at_itu.int
- Information received in the ITU/BR by E-mail
shall be acknowledged by E-mail - Confirmation by telefax or letter is required
from the Administration within 7 days of the date
of the e-mail.
30Relevant Circular Letters related to the Receipt
of notices
RECEIVABILITY OF THE NOTICES
- CR/144
- Application of RES 55 (WRC-2000) for the
submission of information to the Bureau for
publication of information relating to Space
Services - CR/158
- Required AP4 data elements for the submission of
information to the Radiocommunication Bureau
under Appendices 30, 30A and 30B - CR/165
- Rules of Procedure on the receivability of
notices and related correspondence in respect of
space and terrestrial services - CR/166
- Modification to the Rules of Procedure
- CR/169 and 252
- Electronic submission of notices establishing a
formal date of receipt validation reminders and
confirmations - CR/ 211 and CR/222
- BRsoft 5.0 and SNS V5.0 since 01 July 2004
changes after 01 January 2005
31RECEIVABILITY - Recapitulation
RECEIVABILITY OF THE NOTICES
- ROP 1 electronic filing (resolves 5 of RES55)
- ROP 3.2 completeness (Annex 2 of AP4, validation
SW) - ROP 4.1 API not more than 7 years before dBiU
(No. 9.1) - ROP 4.2 Notification not more than 3 years
before dBiU (No. 11.25) - ROP 4.3 1 API 1 CR (No. 1.112)
- ROP 4.4 multiple procedures (API (C) N)
- previously applicable procedures have to be
effected - for earth station associated space station
supported by an API - ROP 4.5 Notification (ART 11) also not
receivable - regulatory time limit (7 or 9 years) has expired
- ROP 5 BR returns the notice to the ADM with a
justification - RES49 information has to be provided latest by
bringing into use - Paragraph 12 of Annex 1 to Resolution 49
32Recapitulation (2) -Time Constraints
RECEIVABILITY OF THE NOTICES
- One of the most critical problems for the ADM is
to have under control and query/view the
critical regulatory dates for a selected
satellite network - Date of receipt of the API - regulatory clock
- Frequency bands published in the API(s)
- CR due date (9.5D)
- Notified date of bringing into use - final
regulatory date (11.44, 11.44.1) - BR reminder to ADM at least 3 /6 months before
a relevant expiry date
33Recapitulation (3) -Time Constraints
RECEIVABILITY OF THE NOTICES
- BR SNS Online HELP - API regulatory dates
summary - http//www.itu.int/sns/advpub.html
34 RECEIVABILITY OF THE NOTICES István BOZSÓKI
BR SSD/SPR
35http//www.itu.int/ITU-R/space/support/seminar2006
/index.html