1 / 28

Improving the Radio Regulations, Prospective WRC (WRC-15) Agenda Items

Improving the Radio Regulations, Prospective WRC (WRC-15) Agenda Items. Per Hovstad, Principal Spectrum Engineer Asia Satellite Telecommunications Co. Ltd. E-mail: phovstad@asiasat.com. ITU Workshop, Limassol April 2014. Four steps in the righ direction. Improved due diligence procedures

georgia-dodson
Download Presentation

Improving the Radio Regulations, Prospective WRC (WRC-15) Agenda Items

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Improving the Radio Regulations,Prospective WRC (WRC-15) Agenda Items Per Hovstad, Principal Spectrum EngineerAsia Satellite Telecommunications Co. Ltd.E-mail: phovstad@asiasat.com ITU Workshop, Limassol April 2014

  2. Four steps in the righ direction • Improved due diligence procedures • Elimination of API for satellite networks subject to coordination • Reduction of "unecessary coordination" • Balancing up- and downlink spectrum ITU Workshop, Limassol April 2014

  3. Four steps in the right direction Does not solve all problems associated with; • Equitable access • Efficient spectrum usage • Congestion of real operational satellites in the arc • Commercial value of controlling access to orbit spectrum resources • "Paper satellites" • "Virtual satellites" However, they are steps in the right direction

  4. Improved due diligence procedures

  5. Improved due diligence procedures • Purpose; to remove “virtual satellites” • Resolution 49 • (Planned) date of launch • No obligation to renew information when satellites are relocated or deorbited • Improved due diligence procedures • Information submitted after launch (exact date) • Requirement to renew information whenever changes occur • Specific ID of satellite, based upon submissions by administrations, to allow tracking of location of satellite in time and avoid same satellite recorded as operational in several locations simultaneously • Resolution 552 • Attempt to improve procedures for BSS networks in 21.4-22 GHz band by WRC-12

  6. Elimination of API for satellite networks subject to cordination

  7. Geostationary satellite networks subject to coordination • Advance Public Information was originally used as a “pre-coordination” to assess potential orbit location and other parameters of later coordination requests • Over time, the API information has been reduced to a bare minimum enabling no pre-coordination • The API process is not suitable for an environment of commercial and competitive satellite operators • No advantages • Disadvantages

  8. API process API period of validity = 2 years Coordination request not receivable = 6 months Coordination request receivable = 1.5 years RR 9.1 Administration A Publication of plans Earliest possible date of filing priority API gives no ITU filing priority Coordination request receiveable within +/- 6° of the location of the API APIs every 12° enables coordination requests to be submitted anywhere in GSO arc Administration B can submit a coordination request for a network which is incompatible with Administration A and receive higher priority than Administration A APIs are not subject to filing fees Administration B

  9. Reduce "uneccessary" coordination

  10. Congestion in the arc • "Paper satellites" • "Virtual satellites" • Real operational satellites (every 2°-3° around the GSO arc) • In particular in unplanned C- and Ku-band • Well established and mature technology and applications • Relatively homogeneous technical parameters have evolved

  11. Large number of administrations and networks identifed as affected • E.g. ASIASAT-105.3T • 1802 networks identified • 49 administrations • All orbital separations (up to 157.8°) • Coordination needs to be completed within 7 years of API, i.e. within ≤ 6.5 years of coordination request • Force administrations to notify without completing coordination (RR 11.41) • Need to avoid unneccessary coordination

  12. In reality, first adjacent satellite networks on either side will completely dominate adjacent satellite interference • Further away networks will have little impact • Need to be able to live with first adjacent satellite network will limit operation • Causing interference to others • Receiving interference from others • This will also allow compatibility with further away networks

  13. Current types of coordination triggers/protection criteria

  14. What interfering level should trigger coordination? Actual ΔT/T as a function of orbital separation for different antenna sizes Practical adjacent satellite interference in real operation 4 GHz 12 GHz Practical adjacent satellite interference in real operation ITU coordination trigger/protection criteria (ΔT/T = 6%) (D1, D2 and D3 denote antenna sizes of 1.8, 2.4 and 3.5 m at 4 GHz and 0.45, 0.6 and 0.9 m at 12 GHz) In practical operation, satellite networks operate with adjacent satellite interference corresponding to: C-band: ΔT/T > ~ 28% Ku-band: ΔT/T > ~ 55% • Significant overprotection in ITU criteria: • Unneccessary coordination • Complicating coordination • Complicating access to spectrum orbit resources • Leading to inefficient usage of spectrum orbit resources

  15. WRC-12 reduced the size of the coordination arc by 2° for unplanned C- and Ku-band. However: • Inclusion under RR 9.41 increases • 1854 networks requested included between 01.01.2013 and February 2014 • 33 networks requested included on average per coordination request (20 before 01.01.2013) • Criteria under RR 9.41 and RR 11.32A are based upon filed parameters • Filings can be designed with parameters that are artificially sensitive to interference, triggering coordination and unduly blocking access for other networks

  16. Give adequate protection to satellites with a reasonable range of technical parameters inside and outside the coordination arc • No additional protection for networks with parameters outside this range • Avoid overprotection stemming from unrealistic parameters contained in filings • Protection criteria not based upon parameters contained in individual filings • Has already been implemented in Appendix 30 and for BSS in 21.4-22 GHz band (pfd masks) • Requires fairly stable technology and relatively homogeneous parameters

  17. Required representative parameters and their possible values to determine pfd masks/values

  18. Example of downlink pfd masks to obtain ΔT/T = 20% 12 GHz 4 GHz Maximum uplink pfd at GSO (dBW/m2 ∙ Hz):6 GHz -198.8 (-204 for ΔT/T = 6%) 14 GHz -202.8 (-208 for ΔT/T = 6%)

  19. Pfd downlink masks and uplink values: • Defined protection inside and outside coordination arc • Independent of filed parameters • Artificial parameters will not unduly block coordination of other networks • No need to define allowable range for parameters to be contained in a filing • Could be introduced at RR 9.7, 9.41 and/or 11.32A • Proposed introduced only at RR 11.32A

  20. WRC-15, Agenda Item 9.1, Issue 9.1.2 • The issue of types of coordination trigger / protection criteria was considered by WRC-12 together with proposals to reduce the size of the coordination ard (Agenda Item 7, Issue 2A) • WRC-12 reduced the size of the coordination arc for C- and Ku-band, but • decided to further study this issue under WRC-15 Agenda Item 9.1, Issue 9.1.2 (Resolution 756 (WRC-12), resolves 1)

  21. Resolution 756 • resolves to invite ITU‑R • 1 to carry out studies to examine the effectiveness and appropriateness of the current criterion (ΔT/T > 6%) used in the application of No. 9.41 and consider any other possible alternatives (including the alternatives outlined in Annexes 1 and 2 to this Resolution), as appropriate, for the bands referred to in recognizing e); • 2 to study whether additional reductions in the coordination arcs in RR Appendix 5(Rev.WRC‑12) are appropriate for the 6/4 GHz and 14/10/11/12 GHz frequency bands, and whether it is appropriate to reduce the coordination arc in the 30/20 GHz band,

  22. Resolution 756 Two separate issues: • Size of coordination arc (resolves 2) • Types of protection criteria/coordination trigger (resolves 1)

  23. Balancing up- and downlink spectrum

  24. Commercial communication satellites normally use "bent-pipe" technology: frequency change Uplink Downlink • BWdown = BWup • Amount of spectrum for up- and downlink should match • Due to satellite antenna design, waveguide and OMTs etc., it is normally most efficient to have up- and downlink in frequency bands in the vicinity of each other

  25. Example 1: Current ITU-R Region 3 table of allocations, Ku-band 13.75 14.0 14.8 17.3 18.1 12.75 13.0 13.25 14.5 17.7 Uplink Downlink 12.2 10.7 10.95 11.2 11.45 11.7 12.75 12.5 300 MHz of downlink capacity cannot be efficiently used due to lack of uplink capacity FSS (unplanned/planned) BSS (unplanned/planned) and uplinks limited to only feederlinks for BSS 350 (600) MHz of uplink capacity cannot be efficiently used due to lack of downlink capacity

  26. Example 2: Current ITU-R Region 1 table of allocations, Ka-band 31 25.25 24.65 27.5 Uplink Downlink 21.2 21.4 22 17.3 FSS (unplanned) 400 MHz of downlink capacity cannot be efficiently used due to lack of uplink capacity BSS (unplanned) and uplinks limited to only feederlinks for BSS Up until corrected by WRC-12, no uplink assignments existed 26

  27. To facilitate efficient spectrum usage, up- and downlink spectrum should be balanced • WRC-15 Agenda Item 1.6.2 is addressing spectrum imbalance in Ku-band for unplanned FSS in Regions 2 and 3.

  28. Thank you! Per Hovstad, Asia Satellite Telecommunications Co. Ltd. e-mail: phovstad@asiasat.com ITU Seminar, Almaty September 2011

More Related