1、 Rec. ITU-R S.1656 1 RECOMMENDATION ITU-R S.1656 Outline of a software specification for automating the examination of satellite network filings for compliance with Article 5 of the Radio Regulations (Question ITU-R 230/4) (2003) The ITU Radiocommunication Assembly, considering a) that the problem o
2、f the backlog in the Radiocommunication Bureaus (Bureau) processing of satellite network filings was first discussed at the Plenipotentiary Conference (Kyoto, 1994), resulting first in the adoption of Resolution 18 (Kyoto, 1994) and then in decisions at WRC-97 that provided a partial solution to thi
3、s problem; b) that Council-98 provided additional resources to the Bureau to address this problem, but the unused funds remaining at the end of the 1998-1999 budget period could not be carried over to the 2000-2001 budget period, and this problem remains unresolved; c) that in January 2000 a corresp
4、ondence group was established by the Director of the Bureau to identify approaches for addressing this problem which could be considered at WRC-2000, but that Conference adopted only a few of the approaches identified; d) that, at Council-2000, the Director established a Software Experts Group to id
5、entify approaches for improving the software used in processing satellite network filings, but the work of that group has not yet resolved any significant portion of this problem; e) that the backlog in the Bureaus processing of satellite network filings continues to be a very significant factor aff
6、ecting administrations and operators ability to comply with the time-frames specified in various provisions of the Radio Regulations (RR); f) that the backlog in the Bureaus processing of satellite network filings is having an adverse impact on the Bureaus ability to continue providing other service
7、s to administrations, including those services provided to developing countries; g) that the annual reports to the Council submitted by the Director of the Bureau described the continually increasing growth of the backlog in the Bureaus processing of satellite network filings; h) that the reports to
8、 the Council submitted by the Director of the Bureau, which specifically respond to Resolution 74 (Minneapolis, 1998) describe possible approaches for resolving this problem; j) that the report from the Working Group on Reform concludes that the backlog in the Bureaus processing of satellite network
9、 filings has been a critical problem for the Union, and that the elimination of this problem will require the systematic development and implementation of an action plan for addressing numerous contributing factors; 2 Rec. ITU-R S.1656 k) that at the 13-14 November 2000 meeting of the Informal Softw
10、are Expert Group, it was identified that in the processing of satellite network filings many manual functions and manual interfaces were required for the regulatory examinations and some of these manual tasks were done at the validation stage as well; l) that examination for compliance with the Tabl
11、e of Frequency Allocations is a manual process; m) that automation of these manual checks could reduce the time required by the Bureau in processing satellite network filings, and may assist administrations to check the compliance of their own satellite network filings with the provisions of RR Arti
12、cle 5 before submitting them to the Bureau, recommends 1 that Annex 1 to this Recommendation, comprising a software requirements outline, should be used in the development of software to automate the examination of satellite network filings for compliance with the Table of Frequency Allocations (RR
13、Article 5) and associated footnotes, invites 1 the Bureau to assure that software developed on the basis of this Recommendation and offered for use by the Bureau accurately reflects the provisions of RR Article 5 and is efficiently integrated into the satellite network filing processing procedures,
14、2 the Bureau to identify what additional manual checks may still be necessary and which of those can be automated to assure that satellite network filings are completely checked for compliance with RR Article 5 and the Rules of Procedure. NOTE 1 For the purpose of commercial development of software,
15、 a more detailed specification, based on the outline in Annex 1, needs to be prepared. NOTE 2 The software to be developed on the basis of this Recommendation should be designed to ensure easy integration with existing Bureau software and software tools used by administrations. Annex 1 General softw
16、are requirements to examine the compliance of satellite network filings with RR Article 5 1 Reasons for developing a software requirement This requirements Recommendation outlines a procedure and the parameters used for the automated checking against the provisions of RR Article 5 of radio-frequency
17、 notices drawn up in accordance with RR Appendix 4, in the interests of enhancing the efficiency with which notices are examined by the Bureau and reducing the number of errors made by administrations when completing them. This involves the development of an RR Article 5 database and software for th
18、e automated examination of notices. Rec. ITU-R S.1656 3 2 Anticipated users and significance of the checking software It is anticipated that the software may be used by the Bureau in checking satellite network filings for compliance with the provisions of RR Article 5. In addition, such software may
19、 be used by administrations in checking their satellite network filings before submission to the Bureau. Furthermore, the RR Article 5 relational database could be used as a reference system for the rapid retrieval of information on frequency band allocations. 3 Input file The input for the examinat
20、ion of a satellite network filing shall be in the electronic format defined by the Bureau for the electronic space notification described in the Circular Letter CR/58 and subsequent amendments published on the Space Radiocommunications Stations on CD-ROM (SRS-on-CD-ROM) (see also Resolution 55 (WRC-
21、2000). The input database may contain one or more networks distinguished by the notice identification number (“ntc_id” as currently defining the field name within a table). The current implementation of the satellite network filing maintains, to some extent, a hierarchical structure, some informatio
22、n relates to the complete network, some to a specific beam and some to a particular group of frequency assignments. In addition, data might have been provided in graphical format and stored in the Graphical Interference Management System (GIMS) database, outside the alphanumerical database. In most
23、cases, the process of automated examination must begin with the identification of the service areas, since this is usually provided in the form of graphical data for each beam. If the service area table associated with a filing is not populated, then it may be possible to use the GIMS software tool
24、to extract a list of territories within a given service area. The data submitted are all listed in RR Appendix 4: The date of bringing into use (A2). The assigned frequency (or frequencies) and bandwidth (C2, C3, C7). The class(es) of station (C4). The direction of the signal (B2). Whether GSO or no
25、n-GSO (indicator for B3 or B4). The service area or areas (C11). The power characteristics of the transmission (C8) might also be required for further examinations due to e.i.r.p. or pfd limitations given in footnotes. (Additional data might be required for some services, for example for services th
26、at can be either active or passive services, deep space, etc. or for particular cases where the date of receipt by the Bureau might be of importance.) NOTE 1 When this Recommendation is revised, further parameters may be added. 4 Rec. ITU-R S.1656 4 RR Article 5 reference database The software will
27、use a database of RR Article 5 that represents the allocations and constraints contained in the RR. This database contains a number of interrelated tables describing the allocations in terms of radiocommunication services, frequency bands, regions (or subregions), date of entry-into-force and associ
28、ated footnotes. The format of the database is shown in Appendix 1. Also included in the database is a set of tables representing the footnotes to the RR Article 5 Table of Frequency Allocations, broken down into their individual components. These components include, for example, additional allocatio
29、ns, constraints and regional variations. The format of this Table of the database is shown in Appendix 2. 5 Examination for compliance with the Table of Frequency Allocations and footnotes The conformity software will check a particular notice through a sequence of steps that will depend on the stru
30、cture of the notice itself and the complexity of the allocation as given in the Table of Frequency Allocations of RR Article 5 and the applicable footnotes within this or these allocation(s). This sequence might require a number of iterations: Frequency band identified under C2a: This will be checke
31、d against the frequency range given for each allocation in the Table of Frequency Allocations, until the proper range is identified. In some cases, (e.g. radio astronomy service) it might be necessary to use other related parameters, C2b and C3. If the allocation is worldwide (i.e. global), the iden
32、tification of the radiocommunication service will take place. Allocated service: The correlation between the classes of station identified under C4, for each group and each beam of the notice and the radiocommunication service(s) of the Table of Frequency Allocations will be checked using a referenc
33、e table that provides this correlation. Direction of transmission: The direction of the signal (identified by item B2) will have to correspond to the direction that might restrict the use of the allocation. Regional allocation: If it is a regional allocation, it will be necessary first to identify t
34、he territories intended to be served by the space network, in other words, the service area identified under C11. Since a service area could be defined in various ways, it might require accessing the graphical data and in this case perform a surfaces overlap between the graphical service area and th
35、e close contour that defined the radiocommunication Region examined. A simple case is a list of territories defining the service area that will have to be inside the close contour of the Region. Footnotes usually identify a list of territories. The correlation between classes of station and services
36、 will take place again, followed by other service-related checks (direction, GSO, etc.). Once the allowed radiocommunication service is identified, the protection status is identified: either the service is primary, secondary, or “undefined” (no harmful interference; no protection). Rec. ITU-R S.165
37、6 5 Date of bringing into use: This will be checked against the period of applicability of the Table of Frequency Allocations of RR Article 5. This date is actually defined for each group, regardless of its location in RR Appendix 4. The same date is checked when a footnote specifies dates (until, a
38、fter) or a period of validity. Of course, optimization will need to be implemented while doing the navigation within and between the two databases (RR Article 5 and satellite network filing(s). If an allocation has a service footnote attached, it is necessary to perform checks against the footnote b
39、efore the examination is completed. An allocation to a particular radiocommunication service may extend over a number of adjacent sub-bands of the Table of Frequency Allocations. In such a case, the allocation should be treated as a contiguous allocation for this service. An example of an algorithm
40、to check compliance is shown in Appendix 3. Note that the filing contains a “class of station” for each assignment, and this must be mapped to the appropriate radiocommunication service(s) for comparison with the entry in the Table of Frequency Allocations these Tables are part of the RR Article 5 d
41、atabase, and are shown in Appendix 4. The software will examine the input file for compliance with applicable footnotes for each assignment. These may be advisory footnotes, or other footnotes that do not require an examination to be carried out by the Bureau. In most cases, however, the footnotes m
42、odify an allocation shown in the Table, or add additional constraints to its use. A list of the main examinations to check compliance with the footnotes is shown in Appendix 5. 6 Output information The software will generate a data table that contains the results of each examination. The table will
43、contain the following fields for each frequency range in the assignment: the network identity (ntc_id); group identity (grp_id); assigned frequency; compliance with service check (positive/negative); indication of allocation status (secondary/primary); compliance with permitted direction of transmis
44、sion (positive/negative); compliance with permitted service area (positive/negative); compliance with permitted date of application (positive/negative); a list of applicable footnotes; indication of any applicable footnote that could not be automatically examined. An example of the format of the out
45、put report is shown in Appendix 6. This data table may be used by other processes (such as other automated examinations), or may be displayed directly to the user. For clarity, however, a user report should contain only those entries from the notice for which inconsistencies with RR Article 5 (the T
46、able or footnotes thereto) were detected, or for which it was not possible, in automatic mode, to determine conformity with RR Article 5. Consideration should be given to providing user-interfaces in multiple languages. 6 Rec. ITU-R S.1656Appendix 1 to Annex 1 Format of RR Article 5 reference databa
47、se Frequency band Region Footnote Radiocommunication service Service footnote WRC Decision FREQ_L FREQ_U FootNoteID (GENERAL) SERVICE FootNoteID (SERVICE) 1930 - 1970 MHz XR1 FIXED 2000 MOD MOBILE 5.388A 2000 MOD 5.388 2000 MOD 1930 - 1970 MHz XR2 FIXED 2000 MOD MOBILE 5.388A 2000 MOD Mobile-satelli
48、te (Earth-to-space) 2000 MOD 5.388 2000 MOD 1930 - 1970 MHz XR3 FIXED 2000 MOD MOBILE 5.388A 2000 MOD 5.388 2000 MOD Rec. ITU-R S.1656 7 Appendix 2 to Annex 1 Format of RR Article 5 footnote table 1656-01Normalized frequency band- Division ID- Footnote ID- Band frequency- Unit frequency- Lowest freq
49、uency- Highest frequencyGeographical area- Division ID- Footnote ID- Geographical area code- Exclusion areaCategory- Division ID- Footnote ID- Alloc categoryReference RR- Division ID- Footnote ID- Application reference- Type reference- RR referenceRestriction- Footnote ID- Division ID- Type restriction- Clause restriction- Text restrictionAllocation- Division ID- Footnote ID- Radio service allocation- Basis allocation- Domain allocationFootnotes (subdivided)- Footnote ID- Division ID- Sort ID- Criterion- Division text8 R
