The DBMS engine should guarantee that every transaction that was executed Reliability/integrity: successfully will not be lost despite a system failure. Transaction based databases guarantee that an operation will be done Transaction operations: in a discrete fashion. The operation will be done completely or not at all. This capability guarantees semantic integrity in the database. Database definition languages also include the ability to impose constraints in order to assure referential integrity in the data. The DBMS engine should multiple users to be connected to the database and handle Multiuser: concurrent access to the information. A large number of users can be connected to the system. The database will handle the contentions of users trying to access the same piece of Contentions: data and appropriately lock data that are being updated. The database should implement the data content recommended by the ITU publications. The following types of data may be stored in the database: National Table of Frequency Allocations – Frequency assignments – Block assignments for concessions – Licence/concession holder – Equipment characteristics – Monitoring – Applications – Fees – Complaints – Violations/infractions – Spectrum occupancy statistics – Unidentified transmitters – Assigned frequency(ies) – Cancelled licences. – Appropriate descriptions of the transmitter, receiver and antenna characteristics are essential for optimal spectrum management. In order to facilitate data entry, the system should highlight the suitable fields and suggest defaults according to the designation of emission or type of service. For example, only for broadcasting TV (BT) should the system prompt for TV. When the antenna pattern is unknown, the system should estimate the side-lobes using an appropriate reference radiation pattern, such as given in Recommendation ITU-R F.699. All data needed to define the site should be included: coordinates, height above sea level from the digital terrain map. The specific azimuth and elevation angles are part of the station defined in the licence. The data elements in the system should be based on the latest edition of the ITU Handbook on computer-aided techniques for spectrum management. To ease data input, the operator should be allowed to choose the element from predetermined tables; the system should be capable of using defaults for most inputs. Screens should allow to add information not coded as data “remarks” elements to be recorded. Where applicable, the definitions of the fields should be in accordance with the Preface to the BR IFIC and the RDD (Recommendation ITU-R SM.1413).
Reliability/integrity: The DBMS engine should guarantee that every transaction that was executed successfully will not be lost despite a system failure. Transaction operations: Transaction based databases guarantee that an operation will be done in a discrete fashion. The operation will be done completely or not at all. This capability guarantees semantic integrity in the database. Database definition languages also include the ability to impose constraints in order to assure referential integrity in the data. Multiuser: The DBMS engine should multiple users to be connected to the database and handle concurrent access to the information. A large number of users can be connected to the system. Contentions: The database will handle the contentions of users trying to access the same piece of data and appropriately lock data that are being updated. The database should implement the data content recommended by the ITU publications. The following types of data may be stored in the database: – National Table of Frequency Allocations – Frequency assignments – Block assignments for concessions – Licence/concession holder – Equipment characteristics – Monitoring – Applications – Fees – Complaints – Violations/infractions – Spectrum occupancy statistics – Unidentified transmitters – Assigned frequency(ies) – Cancelled licences. Appropriate descriptions of the transmitter, receiver and antenna characteristics are essential for optimal spectrum management. In order to facilitate data entry, the system should highlight the suitable fields and suggest defaults according to the designation of emission or type of service. For example, only for broadcasting TV (BT) should the system prompt for TV. When the antenna pattern is unknown, the system should estimate the side-lobes using an appropriate reference radiation pattern, such as given in Recommendation ITU-R F.699. All data needed to define the site should be included: coordinates, height above sea level from the digital terrain map. The specific azimuth and elevation angles are part of the station defined in the licence. The data elements in the system should be based on the latest edition of the ITU Handbook on computer-aided techniques for spectrum management. To ease data input, the operator should be allowed to choose the element from predetermined tables; the system should be capable of using defaults for most inputs. Screens should allow “remarks” to add information not coded as data elements to be recorded. Where applicable, the definitions of the fields should be in accordance with the Preface to the BR IFIC and the RDD (Recommendation ITU-R SM.1413).
R-REC-SM.1370-2-201308-I!!MSW-E.docx