srs database description - tt · pdf fileannex 1 to the attachment presents an...
TRANSCRIPT
SECTION III - Chapter 1: Details relating to the contents of the SNS data items
Edition: August 2009
51/287
Section III
Chapter 1
SECTION III
CHAPTER 1
Details relating to the contents of the SNS data items published in Parts I-S, II-S, III-S
and the Special Sections of the BR IFIC CD-ROM and the database that is provided on the
SRS DVD
General explanation of the tables
This document provides a description of the database that is provided on the SRS DVD in the
form of an MS-Access database (SRS_ALL.MDB1/SPS_ALL.MDB
2). This description can also be
considered to apply to the submission of Appendix 4 information on space services that was
announced in BR Circular Letter CR/211 dated 10th
May 2004. Software is provided on this DVD
which will facilitate the electronic submission of space notices.
The data are presented in the following pages in the form of relational tables. NOTE 1
(paragraph 1.1) gives a brief description of these tables. The tables can be considered as being divided
into four categories: Appendix 4 submitted data, BR data, reference tables and BR internal data. The
attachment describes all the tables in all these categories; however, for the purposes of electronic
submission, only the first category listed (Appendix 4 submitted data) should be considered by your
Administration. Additionally, only the data-items marked with x in the columns 4/2 or 4/3 of these
tables should be provided in the submission. There are data-items that appear many times in these
tables; they should be provided only if marked x in the columns 4/2 or 4/3.
Annex 1 to the attachment presents an entity-relationship diagram used as a basis for deriving
these tables; it shows the tables and their relationships. This diagram is also shown in Annex 3 with
the tables grouped into sets. Annex 4 presents the same diagram with only the tables that are required
for submitting notices for satellite networks under Appendix 4, Annex 2. Annex 5 presents the same
diagram showing only the tables that are required for submitting notices for earth stations under
Appendix 4, Annex 2. Annex 2 provides a cross-reference between the tables and the Ap4 Notice
Forms. Annex 6 provides an entity-relationship diagram showing only the tables relating to the
submitted data; the reference tables are not shown. A description of the columns that are in this
attachment is presented below:
1. Column Table Name
This column contains the names of the tables (which are the entities in the entity-relationship
diagram) according to which the data-items in the next column are grouped together.
2. Column Data-item
In this column, the data-items contained in the tables are listed. The data-items that are to be
submitted electronically are marked by an x in columns 4/2 and 4/3 (see paragraphs 5 and 6).
Data-items that are in bold italic type form the primary key of the corresponding table (NOTE 1
provides a definition of primary key).
1 Database containing notices in unplanned space services.
2 Database containing notices in planned space services of Appendices 30 and 30A of Radio Regulation.
boswellNoteUnmarked set by boswell
boswellNoteMigrationConfirmed set by boswell
boswellNoteMigrationConfirmed set by boswell
boswellNoteAccepted set by boswell
boswellNoteAccepted set by boswell
boswellNoteCompleted set by boswell
boswellNoteCompleted set by boswell
boswellNoteMigrationConfirmed set by boswell
boswellNoteMigrationConfirmed set by boswell
SECTION III - Chapter 1: Details relating to the contents of the SNS data items
Edition: August 2009
52/287
3. Column Format
The format of the data-item is described here. It should be noted that this format is related to
the description of the field on the corresponding form of notice.
The Radiocommunication Bureau (BR) will accept these tables only as a Microsoft Access
Database file in the format described herein. BR has developed a PC-based software package
(running under MS-Windows) that permits the generation of electronic notices in MS-Access table
format as defined by this Circular Letter. This software is provided on the SRS on DVD and can be
also downloaded from the BRs web site.
The format descriptions used in the tables should be read as follows (this is not a COBOL
format but an XBASE type format):
Value Description
X used to describe alphanumeric data.
e.g. X(9) specifies a 9 character field containing alphanumeric data
XXX is equivalent to X(3).
9 used to describe digits
. shows the position of a decimal point
S implies a sign (sign leading separate)
e.g. S999.99 implies a numeric field with a range of values from -999.99 to +999.99
99 implies a numeric field with a range of values from 0 to 99
Null values for data-items (i.e. data-items that are not present in the submission) can be
provided as follows. Since the submission is provided in a Microsoft Access database file, all
data-items (alphanumeric and numeric) which are null should be specified as null (which is a valid
data value in the Microsoft Access database).
Files and file-names: all tables are contained in one physical file which can be provided with a
file-name containing a Windows compatible alphanumeric name ( typically 8 characters - up to the
choice of the Administration) followed by the extension .MDB.
4. Column 4/2 (applicable to satellite networks)
An x3 is specified in this column if the corresponding data-item is to be submitted according
to Appendix 4 (for a satellite network including submission under Article 2A of Appendices 30 and
30A). If nothing is specified in this column for a particular data-item, this implies that the data-item is
not to be provided.
3 See Annex 2 to Appendix 4 to know whether submission of a data item for a specific type of submission is optional or
mandatory.
SECTION III - Chapter 1: Details relating to the contents of the SNS data items
Edition: August 2009
53/287
5. Column 4/3 (applicable to earth stations)
An x3 is specified in this column if the corresponding data-item is to be submitted according
to Appendix 4 (for an earth station). If nothing is specified in this column for a particular data-item,
this implies that the data-item is not to be provided.
6. Column Plans (applicable to space plans Articles 4 and 5 of Appendices 30 and 30A,
Articles 6 and 8 of Appendix 30B)
An x 3
is specified in this column if the corresponding data-item is to be submitted
according to (or is applicable to) Appendix 4 (for the appropriate space plan). If nothing is specified
in this column for a particular data-item, this implies that the data-item is not to be provided. If the
column contains 30, 30A or 30B, then that data item is applicable only for that specific plan.
7. Column Description
A brief description of the corresponding data-item is provided here.
8. Column Comment
This column provides a brief remark for the corresponding data-item, if found necessary.
SECTION III - Chapter 1: Details relating to the contents of the SNS data items
Edition: August 2009
54/287
Details relating to the contents of the SNS data items published in Part I-S, II-S, III-S and the Special Sections of the BR IFIC
Table Name Data Item Items in AP4 Format 4/2 4/3 Plans Description Comment
adm_assoc Administration list on behalf of which submitted
ntc_id BR 9(9) x x unique identifier of the notice PK, FK; see NOTE 1
adm A.1.f.2 XXX x x country symbol of the notifying administration PK; see NOTE 1
assgn Assigned frequency
grp_id 9(9) x x x unique identifier of the group PK, FK; see NOTE 1
seq_no 9(4) x x x sequence number PK; see NOTE 1
f_cmp_rec BR X code indicating if two records compared are equal [E], have basic
differences [B], have non-basic differences [N] or the second record is not
found [X]
BR internal data
freq_assgn C.2.a.1.b 9(5).9(5) x x x assigned frequency
freq_mhz BR 9(6).9(6) frequency in MHz derived data
freq_sym C.2.a.1.a X x x x symbol indicating kilohertz [K], megahertz [M] or gigahertz [G]
attch Attachment information see NOTE 2
ntc_id BR 9(9) x x x unique identifier of the notice PK, FK; see NOTE 1
attch_no 999 x x x number of the attachment PK; see NOTE 1
attch_type X x x x code indicating if the attachment is on paper [P], or electronic [E] format
extension XXX x x x the file name extension in case the attachment is provided in electronic
form
file_name X(8) x x x the name of the file in case the attachment is provided in electronic form
text_info X(255) x x x textual information not mandatory
c_pfd A.17 Compliance with pfd limits
ntc_id 9(9) x unique identifier of the notice PK, FK; see NOTE 1
seq_no 9(4) x sequence number PK; see NOTE 1
bdwdth 9(8) x bandwidth (in kHz) over which pfd was calculated
freq_max S9(6).9(6) x upper frequency limit of the band [MHz]
freq_min S9(6).9(6) x lower frequency limit of the band [MHz]
pfd S999.9 x pfd value in