Recommendation itu r sm. 1370-1 Design guidelines for developing advanced automated spectrum management systems

Yüklə 193 Kb.
ölçüsü193 Kb.
  1   2   3   4   5   6   7   8   9   10

Rec. ITU-R SM.1370-1


Design guidelines for developing advanced automated

spectrum management systems

(Question ITU R 68/1)


The ITU Radiocommunication Assembly,


a) that the demand for spectrum is increasing, that radio systems are becoming more complex and thus the task of frequency assignment is becoming more challenging;

b) that an advanced automated spectrum management system (AASMS) would facilitate national spectrum management and monitoring, coordination among administrations and notification to the Radiocommunication Bureau (BR);

c) that data elements used in national spectrum management have been reflected in the Preface to the International Frequency List (IFL) and Recommendation ITU R SM.1047;

d) that Recommendation ITU-R SM.1413 on a Radiocommunications Data Dictionary may replace or supplement the Preface to the IFL and modify Recommendation ITU-R SM.1047;

e) that many administrations have been successful in implementing an automated database management system (DBMS) in the development and maintenance of their national spectrum management data;

f) that various computer programs which accomplish engineering analysis and other spectrum management tasks are described in the ITU catalogue of software for radio spectrum management and will be available on a website in accordance with Resolution ITU-R 21;

g) that a Windows multi-lingual basic automated spectrum management system (WinBASMS) has been developed jointly by the Telecommunication Development Bureau (BDT) in cooperation with the ITU-R for developing countries that does frequency assignment for the fixed, mobile, broadcasting and other services and operates only as a stand alone system;

h) that AASMS also need to be developed to effectively meet the requirements of spectrum management, to handle additional radio services, to add the capability of using digital terrain data in some calculations, and to add multi user capabilities,


the following design guidelines for an AASMS:

1 that the AASMS should use as a minimum the data elements contained in Annex 1 and provide a mechanism for transferring existing data to the AASMS data structure;

2 that the AASMS should allow multiple users and have appropriate data security features;

3 that the AASMS should contain advanced engineering calculation features for radio services including, if necessary, the space services as determined by the radio service requirements of the administration;

4 that the AASMS should be capable of using a terrain database for specific engineering calculations;

5 that the AASMS should, where feasible, operate in the customer’s national language(s);

6 that output documents intended for the general population (e.g. Licences) should be easily generated in the local language and character set;

7 that the implementation of such systems should include the necessary training and support;

8 that the following specific functions and hardware capabilities should be considered when developing an AASMS.

8.1 Operational requirements

The operation of the AASMS should be designed around the same steps involved in the manual administration of licences. As a minimum, it should support the following administrative functions:

8.1.1 Application processing

This function should support the data entry of an application for wireless service. This can be an application for new service, for modification to an existing licence, or modification to a pending application. The applications should be processed sequentially through the following steps: check that all information is included and the fee paid; check specified equipment; check channel availability; check administrative compliance. If any of these checks fail, a standard letter should be produced for the applicant indicating the nature of the problem. If the proposed site is located within a region of international coordination (i.e. border area), the system should produce a request for international coordination complete with all the data required by ITU or by bilateral agreements with neighbouring administrations. In those cases where it is required, the system should also produce the appropriate ITU-R notification document (e.g. T11, T12). Once all approvals are granted and all fees are paid, the application may become a licence ready to be issued.

8.1.2 Frequency allocation plan/channel processing

This function should support the processing and analyses required to approve a requested frequency channel, or to respond to a request for international coordination from a neighbouring administration. This function may also be used to investigate the availability of open channels in the spectrum.

This function should have the following characteristics:

– provide utilities for the maintenance of national frequency allocation plan. Information to be recorded should include ITU primary and secondary services as a minimum;

– provide capability to maintain channelling plans. Utility should be included for the automated generation of channelling plan with user entered parameters;

– capability to store and retrieve frequency plan footnotes on all levels;

– retrieval of frequency channel pairs and applicable footnotes confirming with user specified parameters;

– system should be able to access the national frequency allocation plan, channelling plans, footnotes, and other system maintained databases on user supplied parameters;

– provide the allocation table in an automated display that a frequency assignment can be checked against to ensure that it is a valid frequency assignment.

  1   2   3   4   5   6   7   8   9   10

Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur © 2016
rəhbərliyinə müraciət

    Ana səhifə