COORDINATION OF SATELLITE NETWORKS Presented by Avram SION avram'sionitu'int BRSSDSSC

1
COORDINATION OF SATELLITE NETWORKSPresented by
Avram SION(avram.sion_at_itu.int)BR/SSD/SSC
BR Radiocommunications Seminar Geneva, Oct-Nov
2006
2

• PROPAGATION OF RADIO WAVES ? Laws of Physics
• Radio waves do not stop at national borders !
• INTERFERENCE ? possible between radio stations
  of different countries
• This risk is high in Space Radiocommunications
  !
• RADIO REGULATIONS ? One of its main purposes
• Interference-free operation of RadioComms

3
INTERFERENCE
TERRESTRIAL STATION
4
RR MECHANISMS TO CONTROL INTERFERENCE ALLOCATION
Frequency separation of stations of
different services REGULATORY PROTECTION
e.g. No. 22.2 Non-GSO to protect GSO (FSS
and BSS) POWER LIMITS - PFD - to protect TERR
from Space services - EIRP - to protect
SPACE from Terr services - EPFD - to
protect GSO from Non-GSO and
5
INTERFERENCE
TERRESTRIAL STATION
6
INTERFERENCE
RECEIVING EARTH STATION
TRANSMITTING EARTH STATION
7
and ? COORDINATION

• Obligatory NEGOTIATION
• between Administrations
• to arrive at interference-free operation
• Process and Procedure described in RR

8
PROVISIONS OF RADIO REGULATIONS

• PLANNED SERVICES (in some bands)
• Broadcasting satellite service
  (Appendix 30/30A)
• Fixed-satellite service (Appendix 30B)
• NON-PLANNED SERVICES
• Coordination and Notification procedure

9
ADVANCE PUBLICATION OF INFORMATION
1-2 years
Central part of a 3-stage process
COORDINATION
3-6 years
RECORDING IN MIFR
10
ADVANCE PUBLICATION OF INFORMATION
Submit, Publish
Request, Examine, Establish Findings
Coordination Requirements, Publish, Coordinate
1-2 years
COORDINATION
3-6 years
Notify, Examine, Check Coordination Agreements,
Record
RECORDING IN MIFR
11
PROCEDURES APPLICABLE TO NON-PLANNEDSATELLITE
NETWORKS

• ARTICLE 9
• Procedure for
• Effecting Coordination with
• or Obtaining Agreement of other Administrations

12
WRC-95, -97, -2000, -03 SIMPLIFIED COORDINATION
PROCEDURE Article 9 contains (almost) all cases
(forms) of coordination for GSO and Non-GSO
satellite networks, earth and terrestrial
stations (previously Articles 11, 14 and
Resolutions 33, 46)
13
COORDINATION ALWAYS BETWEEN ADMINISTRATIONS Always
initiated by the Admin of a station -some
by Coordination Request submitted to
and published by the BR -others by sending
Coordination Request directly to
other Admins
14
INTERFERENCE
TERRESTRIAL STATION
15
REGULATORY PROCEDURES APPLICABLE TONON-PLANNED
SPACE SERVICES
Applies for all satellitenetworks except for
those to be operated in accordance with a Plan
i.e. App. 30, 30A 30B
ADVANCE PUBLICATION Art. 9,Section I,
Sub-Sections IA and IB
REQUEST AGREEMENT Art. 9/9.21 Ap4/II or III
REQUEST COORDINATION
Ap4/II
GEO only
GEO Non-GEO
GEO Non-GEO
Applies only in certain bands services
Non-GEO v. Non-GEO, GEO,
TERR GEO v. Non-GEO,TERR 9.11A (12, 12A, 13, 14)
GEO v. GEO Art. 9/9.7 Res. 33/II
BSS v. TERR 9.11 Res. 33/I
Non-GEO
NOTIFICATION Art. 11 Res. 33
RECORDING IN MIFR
16
ADVANCE PUBLICATION OF INFORMATION (API)ON
SATELLITE NETWORKS(Section I of Article 9)

• Aim is to inform all administrations of a
  contemplated satellite network (GSO or Non-GSO)
• Formal mechanism to initially assess interference
  effects of that satellite network

17
ADVANCE PUBLICATION (1) Section I has two
sub-sections

• 1A API for satellite systems
• NOT SUBJECT TO COORDINATION
• under Section II of Article 9
• 1B API for satellite systems
• SUBJECT TO COORDINATION
• under Section II of Article 9

18
ADVANCE PUBLICATION (2)

• Information to be communicated to the BR for
  publication ? Appendix 4
• To be initiated 2- 5 7 years before the planned
  date of bringing into use of the network (or
  system) No. 9.1
• BR publishes Special Section API/A

19
(No Transcript)
20
(No Transcript)
21
ADVANCE PUBLICATION (3)

• API phase is obligatory, before coordination
  phase or notification
• No priority in being first to start advance
  publication
• ?? Starts the regulatory clock !!!

22
ADVANCE PUBLICATION (4)

• Must be (re)started
• for new frequency band(s)
• for a change of GSO orbital location by gt12 6
  degrees

23
COORDINATION OF SATELLITE NETWORKS

• Section II, Article 9
• Procedure for effecting coordination
• Contains (almost) all cases (forms) of
  coordination for satellite networks (GSO and
  Non-GSO), earth and terrestrial stations

24
COORDINATION CASES Not in Art.9 Article 7 of
Appendix 30 FSS or BSS (Non-Plan) _at_ BSS
Plan Article 7 of Appendix 30A FSS or BSS (Non
Plan) _at_ Feeder Link Plan Resolution 77 (WRC-2000)
FSS with Terrestrial Services (11.7-12.2
GHz) Resolution 84 (WRC-2000) FSS with
Terrestrial Services in R2 (37.5-40
GHz) Resolution 539 resolves 2, Furthemore,
first indent Non-GSO BSS 2.6 GHz
_at_ Terrestrial services
25
COORDINATION (2)

• Procedure for coordination of GSO and Non-GSO
  satellite network
• Article 9 is to be applied for coordination of
  GSO and N-GSO networks in the following cases

26
COORDINATION (3)

• Between GSO networks No. 9.7
• Between GSO and Non-GSO and between Non-GSO
  networks (if a footnote to ToFA says so) Nos.
  9.12, 9.12A, 9.13
• Space station in respect of terrestrial stations
  (if a FN to ToFA says so) where threshold value
  is exceeded No. 9.14

27
COORDINATION (4)

• space station in the BSS (non-Plan) with respect
  to terrestrial stations - No.
  9.11/Res.33, Res.539
• any station of a space service for which a FN to
  ToFA imposes a requirement to seek agreement of
  other administrations
• - No. 9.21

28
COORDINATION (5)

• in all of these cases, request for coordination
  is to be sent by the requesting administration to
  the BR together with the required data as
  specified Ap4 (No. 9.30)
• simultaneous request for all applicable forms of
  coordination (No. 9.23)

29
COORDINATION (6)

• date of receipt of the coordination request must
  be ? six months after the date of receipt of API
  (No. 9.1)
• request for coordination must come within 24
  months after the date of receipt of the API,
  otherwise restart
• API (No. 9.5D)

30
COORDINATION (7)Actions of the BR

• The BR examines coordination requests
• (if complete) for conformity with
• the ToFA No. 9.35
• other provisions of the RR No. 9.35
  (e.g. compliance with PFD limits)
• The BR identifies, in accordance with Ap5 ,
  administrations with which coordination may need
  to be effected No. 9.36

31
COORDINATION (8)

• Appendix 5
• Identification of administrations with which
  coordination is to be effected or agreement
  sought under the provisions of Article 9
• Ap5 contains criteria for identification of
  assignments to be taken into account in effecting
  coordination or seeking agreement

32
COORDINATION (8)
Appendix 5 Assignments to be taken into
account - those that started coordination or
were recorded in MIFR before - comply with
RR (favourable _at_ 11.31) - have frequency
overlap - thresholds (if any) are exceeded
33
COORDINATION (9)

• Methods, thresholds and conditions given in
  Tables 5-1 and 5-2 differ according to the
  specific cases (forms) of coordination
• (GSO?GSO, GSO ? Non-GSO,
• Non-GSO ? Non-GSO,
• GSONon-GSO ?? terrestrial stations)

34
COORDINATION (10)

• e.g. GSO ? GSO
• Criterion
• DeltaT/Tgt6, method of calculation in Ap8
• Coordination Arc between and among
• GSO FSS or BSS in some frequency bands
• List of ADMINISTRATIONS (required Coord)
• List of NETWORKS, for information (9.36.2)

35
COORDINATION (11)

• BR publishes network data in a CR/C Special
  Section of its IFIC, on CD-ROM, fortnightly since
  2000, together with the results of its
  examination, i.e. findings (No. 9.35/11.31),
  coordination requirements (list of ADMINS, No.
  9.36), list of networks, if applicable (for
  information only, No. 9.36.2) and/or, if
  applicable, potentially affected Admins for
  information only (list of ADMINS, No. 9.36.1)

36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
BR COMMENTS - Findings with respect to No.
9.35/11.31
1. For frequency assignments in the 12.5-12.7
GHz band 1.1 UNFAVOURABLE for all frequency
assignments in transmitting space station beams
ETH and ETV with maximum power density greater
than or equal to 55.8 dBW/Hz (p.f.d. limits of
No. 21.16 are exceeded).
41
BR COMMENTS - Findings with respect to No.
9.35/11.31

• 1.2 UNFAVOURABLE for frequency assignment 12.5
  GHz in transmitting space station beam UPC
  (out-of-band).
• 1.3 FAVOURABLE for all other frequency
  assignments.
• Read CR/C, it says a lot

42
BR COMMENTS Coordination Requirements (No. 9.36)

• CR/C
• Applicable forms of COORD (page 1/2)
• Summary of COORD Requirements,
• per form of coord List of Admins (p. 3/4)
• (Last part of CR/C)
• Detailed COORD requirements (Admins) for each
  group of frequency assignments
• List of networks identified (for info only)

43
COORDINATION (12)

• The list of
• administrations identified by the BR under Nos.
  9.11 to 9.14 and 9.21
• networks identified by the BR under 9.7
• are only for information purposes to help
  administrations comply with procedures (Nos.
  9.36.1, 9.36.2)

44
COORDINATION (13)

• List of ADMINs identified under No.9.7, as a
  result of Coordination Arc or DeltaT/T, is the
  formal list
• of ADMINs with which coordination is required
• Coordination Arc results 9.41/9.42, inclusion,
  exclusion (4 months)
• Four months for comments

45
COORDINATION (15) Action by administrations

• An administration having received a request for
  coordination (through publication of CR/C) is to
  examine the matter with respect to interference
  which may be caused to or by its own assignments

46
COORDINATION (16) Action by administrations

• inform the requesting administration and the BR
  within four months from the date of publication
  of the CR/C of either
• its agreement to the proposed use, or
• its disagreement, giving reasons for the
  disagreement

47
COORDINATION (17) Action by administrations

• For coordination requests under Nos. 9.11 (Res.33
  _at_ terrestrial services), 9.12 to 9.14 and 9.21,
  the absence of disagreement within the 4-month
  period means agreement (No. 9.52C) !

48
COORDINATION (18) Res.33 (Rev. WRC-03)

• Procedure applicable to non-planned BSS is
  included in Article 9. However, Resolution 33
  still applies to satellite networks with API
  received prior to 01.01.1999.
• If API information was received after 01.01.1999
  No. 9.11 applies

49
COORDINATION (19)

• Coordination is an obligation
• for the administration wishing to assign a
  frequency to a station
• for any other administration whose services might
  be affected (No. 9.53)
• The agreement resulting from coordination
  involves certain rights and obligations

50
COORDINATION (20)

• Coordination is to be effected in accordance with
  RR procedures and on the basis of criteria
  established by the RR or agreed to between
  administrations

51
Extension of the Date of bringing into use of
frequency assignments to space networks

• No. 9.1 Advance publication procedure shall be
  initiated not earlier than 5 7 years before the
  planned date of bringing into use of the network.

52
Date of bringing into use (2)

• 11.44 The notified date of bringing into use of
  any frequency assignment to a space station shall
  be not later than 5 7 years following the date of
  receipt by the BR of the relevant information
  under No. 9.1.

53
Extension (3)

• 11.44 The notified date of bringing into use may
  be extended by not more than 2 years, only under
  conditions specified in Nos. 11.44B to 11.44I.
• That is, a maximum of 7 years from the date of
  receipt of API.

54
Extension (4)

• 11.44B, 11.44C, 11.44D, 11.44E, 11.44F, 11.44G,
  11.44H, 11.44I

55
Date of bringing into use (3)

• Resolution 51
• Transitional arrangements relating to the API
  and coordination of satellite networks
• Resolves - For satellite networks with API
  received by the BR before 22.11.1997, the maximum
  allowed time period to bring assignment into use
  shall be 6 years plus the extensions pursuant to
  RR1550 (639 Years) from the date of publication
  of the API.

56
Due Diligence (Administrative)

• Resolution 49 address the problem of
  reservation of orbit and spectrum capacity
  without actual use (Res. 18 of Kyoto
  Plenipotentiary)
• Applies from 22.11.1997 to any satellite network
  in the FSS, MSS, BSS that is subject to
  coordination
• Procedure resolves and Annex 1

57
Due Diligence (2)Information required

• Annex 2 to Resolution 49
• A. Identity of the satellite network
• B. Spacecraft manufacturer
• C. Launch services provider

58
Annex 2 to Resolution 49 A. Identity of the
satellite network

• a) Identity of the satellite network
• b) Name of the administration
• c) Country symbol
• d) Reference to the API special section

59
Annex 2 to Resolution 49

• e) reference to the CR/C special section
• f) Frequency band(s)
• g) Name of the operator
• h) Name of the satellite
• I) Orbital characteristics

60
Annex 2 to Resolution 49 B. Spacecraft
manufacturer

• a) Spacecraft manufacturer
• b) Date of execution of the contract
• c) Contractual delivery window
• d) Number of satellites procured

61
Annex 2 to Resolution 49 C. Launch services
provider

• a) Name of the launch vehicle provider
• b) Date of execution of the contract
• c) Anticipated launch delivery window or in-orbit
  delivery
• d) Name of the launch vehicle
• e) Name and location of the launch facility

62
Due Diligence (3)

• Six months before expiry of the notified period
  of bringing into use 7-year regulatory
  lifetime, the BR sends a reminder
• If the due diligence information is not received
  in time, the network shall no longer be taken
  into account and shall not be recorded in the
  Master Register

63
COORDINATION REQUEST PROCESSING
64
COORDINATION REQUEST PROCESSING
Capture network data in .MDB and .GXT format,
Validate, Provide to BR
Administration
Receivability, as-received publication,
pre-validate, 2D-date, prepare, validate
BR
SNS GIMS DataBase Ready for Examination
BR
65
COORDINATION REQUEST PROCESSING
BR
Examination
Table of Frequency Allocation
Other provisions of RR (PFD)
9.35
Split Groups of Frequency Assignments
Forms of Coordination
Findings, Enter them
A, B, N
RoP 9.35
66
GROUP OF FREQUENCY ASSIGNMENTS

Orbital Position Beam Assigned Bandwidth Service
(CoS) Assigned Frequency Emission/Power (Data
Elements) Assignments
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
1
1
1
2
2
1
1
1
2
2
2
16
6
1
2
3
4
4 in a group
10 50000 in one network
67
GROUP SPLITTING Re-GROUPING

Orbital Position Beam Assigned Bandwidth Service
(CoS) Assigned Frequency Emission/Power Assignmen
ts
1
1
1
1
2
1
1
2
4 in a group
68
GROUP SPLITTING Re-GROUPING

Orbital Position Beam Assigned Bandwidth Service
(CoS) Assigned Frequency Emission/Power Assignmen
ts
1
1
1
A
N
1
1
1
1
1
1
1
1
1
2
2
1
1
1
1
1
2
2
2
COORD
NO COORD
4 in a group
2 in a group
2 in a group
69
COORDINATION REQUEST PROCESSING
BR
Examination
Table of Frequency Allocation
Other provisions of RR (PFD)
9.35
Split Groups of Freq. Assign.
Forms of Coordination
Findings, Enter them
A, N
70
COORDINATION REQUEST PROCESSING
9.36
Examination (Cont)
BR
Forms of Coordination
9.7, 9.7A, 9.7B, 9.11, RS33, 9.11A, 9.12, 9.12A,
9.13, 9.14, 9.21/A, 9.21/B, 9.21/C, Ap30/Art.7,
Ap30A/Art.7, RS539
Software Tools for Coordination Requirements
.mdb .mdb .mdb .mdb .mdb
.MDB
SNS
71
COORDINATION REQUEST PROCESSING
SNS
Publication
CR/C Special Section
72
COORDINATION REQUEST PROCESSING
CR/C Special Section Final Coordination
Requirements Potentially Affected Administrations
(only for info under No. 9.36.1) Only Admins
that, within 4-months, inform of disagreement
under 9.52, enter coordination. Others are
considered to have agreed !!!
W.R. to SPACE 9.7, RS333, 9.7A, 9.7B A307.1,
A30A7.1 9.11A 9.12, 9.12A, 9.13 9.21 9.21/A,
9.21/B CR/D
W.R. TERR RS539 9.11/RS332.1 9.11A/9.14 9.21-9.
21/C CR/D
73
COORDINATION REQUEST PROCESSING
9.11, 9.12, 9.12A, 9.13, 9.14, 9.21A/B/C
SNS
CR/D
Publication
BR
9.7, 9.7A, 9.7B, Ap30/30A7.1
IFIC.mdb
CR/C Special Section
ADMIN
74
INTERFERENCE
QUESTIONS ?
TERRESTRIAL STATION