THE PLANNING PROCEDURE FOR HF BROADCASTING - ARTICLE 12 OF THE RADIO REGULATIONS

Transcription

1 THE PLANNING PROCEDURE FOR HF BROADCASTING - ARTICLE 12 OF THE RADIO REGULATIONS Nedialko Miltchev Radiocommunication Bureau 1 Introduction The current procedures for the use of the HF bands allocated exclusively to the broadcasting service, as decided by the World Radiocommunication Conference 1997 (WRC-97), are contained in Article 17 of the revised and simplified Radio Regulations. It replaces, from 1 January 1999, the one contained in the former Article 17 of the Radio Regulations, that has been in place since 1959, with some modifications by WARC-HFBC-87. Article 12, entitled "Seasonal Planning of the HF Bands Allocated to the Broadcasting Service Between khz and khz" is a planning procedure for HF broadcasting based on coordination. The implementation of the procedure has been carried out in close consultation with Administrations, broadcasting organizations (referred to as broadcasters in Article 12), frequency management organizations and particularly the regional HF coordination groups ASBU, ABU-HFC and HFCC. This paper discusses the planning and coordination procedures. 2 Frequency bands khz ** khz khz khz ** khz * khz khz ** khz ** khz ** khz ** khz khz khz ** khz ** khz khz khz ** khz khz ** * Regions 1 and 3 only ** The bands are allocated, until 1 April 2007, to the fixed or mobile service. The use of these additional bands by the broadcasting service as from 1 April 2007 will be subject to the application of the procedure of Article 12. Administrations are encouraged to use these bands to facilitate the introduction of digitally modulated emissions in accordance with the provisions of Resolution 517 (Rev.WRC-03). REGIONAL RADIOCOMMUNICATION SEMINAR ARPIL 2007 ABU DHABI, UAE

2 - 2-3 Principles The Procedure is based on the principle of equal rights of all countries, large or small, to equitable access to the concerned bands (RR 12.2). All broadcasting requirements, national and international, are treated on an equal basis, without consideration of the difference between these two kinds of broadcasting requirements (RR12.5). The Procedure attempts to ensure an efficient use of the spectrum and to provide a satisfactory quality of reception (RR 12.6). Whenever is possible, only one frequency should be used. 4 Main features Administrations are encouraged to coordinate their schedules with other Administrations as far as possible prior to submission. Administration and broadcasters are urged to participate in the relevant regional coordination groups, and to achieve the coordination through bilateral or multilateral meetings (RR 12.10). An Administration may, on behalf of a group of Administrations, submit their coordinated schedules, or authorise broadcasters or other organisations to coordinate on its behalf (RR12.30). 5 Notification 5.1 Who can notify? Requirements must be notified by Administrations or organizations, such as broadcasters and frequency managers, who are authorized by the Administrations concerned to do so. In the latter case, Administrations must advise the Bureau in writing in advance stating the names of the authorized organizations, their three-letter code and the scope of the authorizations (RR 12.1). 5.2 How to notify? Notification of requirements will be in electronic format only. The notification file shall be in the commonly used text file format. The Bureau makes available computer software that can be used by Administrations to create files of HF requirements in the appropriate electronic format. Administrations can submit their requirements to the Bureau by electronic mail to: brmail@itu.int with the requirement file attached to the message, not in the body of the message. Alternatively, Administrations can send the requirement file saved on a 3.5-inch floppy diskette (Resolution 535 of WRC-97) to the address below: International Telecommunication Union Radiocommunication Bureau Place des Nations 1211 Geneva 20 Switzerland When an Administration ceases its broadcasting service in the HF bands, it shall notify the Bureau of such a decision in writing (RR 12.28).

3 What to notify? The data fields to be submitted for each requirement are discussed in Annex 1 of Circular Letter CR/257 ( The format of the electronic file of requirements is described in Annex 2 of Circular Letter CR/257 ( CIR-0257/e). In order to avoid possible confusion on the data elements such as transmitter site codes, antenna codes and organization codes, the Bureau maintains a number of reference tables that are updated and published with each CD-ROM and are also available for viewing and downloading from ITU's website. For all amendments to the reference tables, Administrations concerned should advise the Bureau in writing ( , fax or letter) including all the necessary information. For example when an Administration wishes to include a new antenna code, it should write to the Bureau and include the full description of the antenna system. The Bureau then assigns an appropriate code, advises the Administration concerned and publishes updated reference tables on CD-ROM and its website: The proposed common electronic format is similar to the format of requirement files that are currently used by existing coordination groups so that Administrations can continue, with some modifications, to utilize their developed software for internal purposes. The text file format was chosen in order to facilitate the preparation of requirement files using commonly available software such as Notepad, MSWord, etc. In all cases, Administrations shall submit the whole schedule, not just the amended requirements. This follows the current practice used in the HFCC and ABU coordination groups. By submitting the whole schedule, this minimizes the potential for errors, for example, modifying incorrect requirements because the targets are incorrectly identified. In the case where requirements for a given season period are exactly those of the previous corresponding season, Administrations can advise the Bureau in writing of the fact without submitting the new schedule. This is to facilitate Administrations having regular broadcast requirements. 5.4 When to notify? For each broadcasting season, the Bureau establishes and publishes, via circular letter and its website, the closing dates for receipt of the schedules relating to that season. The closing dates are generally set at about two (2) weeks before the publication dates of HFBC CD-ROMs to allow inclusion of up-to-date data, while providing the Bureau with sufficient time to process and arrange publication of the schedules. Generally Administrations should send their schedules to the Bureau ten (10) weeks before the start date of a given schedule period. For example, for the schedule period B06, starting on 29 October 2006 (last Sunday of October), the closing date for submitting a schedule is 13 August Two weeks before the start date of a given schedule period Administrations can, if necessary, send amended full schedules. For example, for the schedule period B06, starting on 29 October 2006, the date for submitting amendments to schedules is 15 October 2006.

4 - 4 - During a given schedule period, Administrations should send any changes to their schedules to the Bureau as soon as possible. HFBC Schedule on CD-ROM - Season B06 (29 October March 2007) List of editions and closing dates for submissions as set in Circular Letter CR/257 of 1 May 2006: Schedule Title Date of edition Date limit for submissions B06 Tentative 1 (B06T1) End of August August 2006 B06 Tentative 2 (B06T2) End of September September 2006 B06 Schedule 1 (B06S1) End of October October 2006 B06 Schedule 2 (B06S2) End of December December 2006 B06 Final (B06F) End of April April 2007 It is important to note that, in order to allow for the time required by the Bureau to prepare for the publication of updates of the schedule and its corresponding compatibility analysis, any requirements or amendments received less than two (2) weeks before the publication date will not be included in the publication. The above timing is consistent with Resolution 535 of WRC What if no schedule is submitted? If an Administration does not submit its requirements for a new seasonal schedule, the Bureau shall use the requirements from the previous corresponding seasonal schedule for this Administration for the new schedule period. The Bureau will advise the Administration concerned of the action. These requirements will be identified accordingly in the published schedule (RR 12.26). If the same Administration does not indicate its requirements for the next corresponding seasonal period, the Bureau shall notify the Administration concerned that the schedule will not include its requirements unless the Administration advises otherwise (RR 12.27). 6 Publication of the schedule and compatibility analysis 6.1 How is the data published? The schedule and corresponding compatibility analysis are published on CD-ROM and sent by mail to regional coordination groups and registered subscribers. 6.2 What does the CD-ROM contain? The CD-ROM contains the following: Up-to-date broadcasting schedule of the current seasonal schedule together with detailed signal propagation and compatibility analysis; Propagation data to 911 test points for all requirements; Up-to-date reference tables;

5 - 5 - Latest version of ITU HFBC software that can be used to: Prepare amendments to requirements and create file in appropriate electronic format for submitting to the Bureau; Assess performance of requirements (basic and overall service reliability); Select a suitable frequency band for a requirement; and Carry out what-if studies to search for solutions to minimize interference between services. 6.3 When is the data published? Two Tentative Schedules are published two months and one month before the start of each of the two schedule periods (WRC-03). At the start of each broadcasting season, the Bureau publishes the first schedule. During the season updated versions of the schedule are published (two versions for season A and one version for season B). One month after the end of the season the Bureau publishes the final schedule (RR 12.43). 7 Coordination Coordination shall be achieved through bilateral and multilateral meetings of Administrations or broadcasters or other means such as telephone, facsimile, , etc., acceptable to the parties concerned (RR 12.36). Regional coordination groups shall identify themselves to the Bureau (RR 12.11). Details on the coordination groups already identified by the Bureau are given in Annex 3 and also available from the ITU website. Administrations, broadcasters and authorized organizations are encouraged to participate in the relevant coordination groups. The Bureau should convene, as appropriate, joint meetings of the representatives of all the regional coordination groups to develop strategies for further reduction of incompatibilities and to discuss related matters. 8 Assistance to Administrations 8.1 Selection of frequencies Any requirement submitted without a frequency or with a number of (up to three) alternative frequencies or with a preferred operating frequency band will be considered as a request for assistance from the Bureau in selecting a suitable frequency. The Bureau will carry out studies to look for suitable frequencies and will advise the Administration concerned accordingly (RR 12.33). 8.2 Application of the procedure Upon request and subject to its resources, the Bureau shall endeavour to assist Administrations, particularly the Administrations of developing countries, in the application of the procedure. In particular circumstances, where an Administration can demonstrate that it does not have adequate resources to carry out an effective coordination with other Administrations, the Bureau shall consider appropriate measures including coordinating the Administration's broadcast requirements on their behalf.

6 - 6-9 HF Broadcasting software 9.1 General principles The development of the HFBC software was guided by the following general principles: Consistent with the general principles set out in Article 12 and the specifications in Resolutions 535 of WRC-97. Developed in close consideration with Administrations, broadcasters, and existing HFBC coordination groups. Making use of the currently available HFBC software developed by ITU and Administrations. Taking into account the availability of suitable computer hardware by Administrations to run the software. 9.2 Assistance from Administrations The Bureau has received assistance and support throughout the development of the software. Assistance was in many cases volunteered. Special mention is due to Mr. Greg Hand (United States) for his contribution and advice in developing the software for the propagation calculation in accordance with ITU-R 533. The same also goes to many members of the regional coordination groups ABU-HFC, HFCC and ASBU for their helpful comment and advice on the development of the overall software package. 9.3 Key features of the software modules Data capture A separate software module (HFBC REC) has been developed to enable Administrations, broadcasters or authorized organisations easily to capture and prepare their requirement files for submitting to the Bureau. Requirement files are created as text files in a simple format witch is similar to that currently used by most Administrations and within the coordination groups. It is possible to import data from text format to the MS Access database, to modify requirements and to prepare requirement files for the following seasons Propagation prediction The main module of the software (ITUHFBC) calculates field strength, power received and basic circuit reliability (BCR) for a transmission circuit. The basic service reliability (BSR) is also calculated for a percentage of locations of test points, determined by the users. The module calculates propagation data for all bands and results are presented in tabular form or shown on maps Compatibly analysis The software calculates interference from other requirements on the same and adjacent channels. Interference sources are identified and their contribution to the overall degradation of compatibly is provided. This should assist coordination between Administrations. The results are shown on maps with overlaid CIRAF zones boundaries using different colours to highlight the severity of interference. Users can select suitable values of required S/N and protection ratios between cochannel and adjacent channel.

7 Versions released Currently available versions: ITUHFBC 5.2 Main software program. Include the methodology and data required for the propagation calculations and compatibility analysis relating to digital emissions, according to Resolution 535 (Rev. WRC-03). HFBCREC Data capture module. For creating the requirement files. HFBCANT 1.0 Software module witch calculates the HF antenna patterns. HFBCVAL 1.1 Program witch enables Administrations to quickly validate their requirements. The software is designed to run under the Windows operating system. All software modules are available in English, French and Spanish. The package is included in the CD-ROM HFBC Schedule and it is available for downloading from the ITU HF web site: