International Telecommunication Union
GUIDELINES
Submission and
Notification of notices
relating to the GE75 and
RJ81 Agreements
Version 1.1
Released 31 March 2014
Consolidated information concerning the use of electronic file formats for the
submission and notification of frequency assignments to stations of
LF and MF terrestrial sound broadcasting service in Regions 1 and 3 governed by
the Regional Agreement Geneva 1975 (GE75) and to stations of
MF terrestrial sound broadcasting service in Region 2 governed by
the Regional Agreement Rio de Janeiro 1981 (RJ81)
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 1
Summary of changes from the original version
Version 1.1, released 31 March 2014
Page
Change description
18
ADD “Min value 0.01”
Reason
Clarify permissible values for power to, in
kW, delivered to the antenna for RJ81
notices: Numeric, with 2 decimals, 5
characters
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 2
1.
Introduction
This document supersedes the information relevant to GE75 and RJ81 submission and
notification contained in Circular Letter CR/125 dated 30 July 1999 and in Circular Letter
CR/289 dated 24 July 2008. It will be updated as required and available at
http://www.itu.int/ITU-R/go/terrestrial-notice-forms/en so that administrations may have easy
access to the most recent reference.
1.1
This document contains a general description of the relevant electronic notice types
(T03, T04, TB6, TB7, TB8 and TB9), instructions on their use and detailed rules and
guidelines concerning the preparation of these notice types (Table 5, Table 6, Table 7, Table
8, Table 9 and Table 10). Sample electronic notification files can be found on the web page
listed above.
1.2
Document “LF/MF Broadcasting, Regions 1 and 3, Geneva, 1975”, describing
procedures of submissions of the modifications to the GE75 Plan under Article 4 of the
Agreement (including the relevant flowchart) as well as notifications to the Master
International Frequency Register (MIFR) under Article 5 of the GE75 Agreement, is
available for TIES account holders at:
http://www.itu.int/md/R12-WRS12-C-0009/en
1.3
Document “Broadcasting Assignment Plan RJ81”, describing procedures of
submissions of the modifications to the RJ81 Plan under Article 4 of the Agreement
(including the relevant flowchart) as well as notifications to the Master International
Frequency Register (MIFR) under Article 5 of the RJ81 Agreement, is available for TIES
account holders at:
http://www.itu.int/md/R12-WRS12-C-0010/en
1.4
To submit files with electronic notices to the BR please use ITU-R WISAT
submission system, available at: http://www.itu.int/ITU-R/go/wisfat/en
2. General description of the types of notice forms applicable to GE75 and RJ81
The Regional Agreements GE75 and RJ81 specify procedures for the submission of
modifications to the Plan (Article 4 of the Agreement) and for the notification to the MIFR
(Article 5 of the Agreement).
In view of these indications, given the necessity of having all the necessary data elements for
performing the required examinations and keeping the relevant assignment data correctly
updated the Bureau continues to use the following notice types with necessary changes
resulting from WRC-07 decisions (Table 1).
Table 6, Table 7, Table 8, Table 9 and Table 10 provide the description of the data items for
all the types of notice forms used in the GE75 and RJ81 Agreements.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 3
Table 1
Overview of the types of notice forms applicable to LF and MF sound broadcasting
Type of
Notice
Form
Applicable for
Table
with
guidelines
T03
Application of Article 4 procedure for the addition of a new assignment to
the GE75 Plan or for modification of an existing assignment recorded in
the GE75 Plan (t_action=ADD or MODIFY).
Application of Article 5 procedure for the addition of a new assignment to
the MIFR or for modification of an existing assignment recorded in the
MIFR when the technical characteristics of the assignment being notified
are not the same as in the Plan (t_fragment= NTFD_RR). If they are the
same, notice form TB7 is to be used.
4
T04
Application of Article 4 procedure for the addition of a new assignment to
the RJ81 Plan or for modification of an existing assignment recorded in
the RJ81 Plan (t_action=ADD or MODIFY).
Application of Article 5 procedure for the addition of a new assignment to
the MIFR or for modification of an existing assignment recorded in the
MIFR when the technical characteristics of the assignment being notified
are not the same as in the Plan (t_fragment= NTFD_RR). If they are the
same, notice form TB7 is to be used.
4
TB6
Modification of administration unique identifier in the Plan or MIFR
(t_action=ADMINID).
5
TB7
Notification in the MIFR under Art. 11 of RR of an assignment with all
technical characteristics as in the Plan (t_action= CONFORM).
6
TB8
The request of the publication in Part B of a notice published in Part A
(t_action= PARTB)
7
TB9
Notice form for withdrawing a notice under treatment or suppressing a
recorded assignment in the Plan or in MIFR (t_action=WITHDRAW or
SUPPRESS).
8
2.1 Notice Form T03
2.1.1 Notice form T03 is the main notice form for the submission/notification of a
frequency assignment in LF and MF sound broadcasting in Region 1 and in MF sound
broadcasting in Region 3. Its structure is complex. In addition to standard sections HEAD,
NOTICE, TAIL and subsection COORD found also in other types of notice forms, it must
contain one or two subsection(s) OPERATION describing technical characteristics of the
day-time operation from local sunrise to local sunset (HJ) and/or technical characteristics of
the night-time operation from local sunset to local sunrise (HN) (please see Table 2)
Even if the technical characteristics for day-time and night-time operation are the same, both
complete subsections OPERATION must still be provided, one for HJ and one for HN.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 4
Table 2
The general structure of notice form T03
section
subsection
sub-subsection
sub-sub-subsection
HEAD
NOTICE
COORD
OPERATION
PATTERN
GAIN
TAIL
2.1.2 Subsection OPERATION may contain one or sub-subsections PATTERN, which
may in turn contain one or ten sub-sub-sections GAIN, which must be provided for antennae
of a complex structure (antenna type B). If the antenna structure consists of only one simple
vertical tower (antenna type A), sub-subsection PATTERN must not be provided. Instead,
only the value of the antenna height in metres of this simple vertical tower (t_ant_hgt_m)
must be provided within the relevant subsection OPERATION.
2.1.3 To identify uniquely the target assignment to be modified (in the Plan or in the MIFR)
the assigned frequency (t_trg_freq_assgn) and geographical coordinates (t_trg_long,
t_trg_lat) of the target are used. Alternatively, like in other notice forms for terrestrial
broadcasting, the unique identification code (given by the administration) of the target
assignment (t_trg_adm_ref_id) may be used. The unique identification code must remain
unique within the administration and the Plan or MIFR. However, it is recommended to use
assigned frequency and geographical coordinates for target identification in order to
minimize the potential for errors.
2.1.4 Submission or notification intended to MODIFY an existing recorded assignment
must contain a complete set of ALL MANDATORY DATA even if only one particular data
item is subject to modification. Otherwise this may lead to confusing results. For example, if
a submission or notification intended to modify only the HJ operation of an existing
assignment consisting of both HJ and HN operations does not provide also subsection
OPERATION for HN (with all data unchanged), then at the end of processing the HN
operation will be removed from the concerned assignment.
2.2 Notice Form T04
2.2.1 Notice form T04 is the main notice form for the submission/notification of a
frequency assignment in MF sound broadcasting in Region 2. Its structure is complex. In
addition to standard sections HEAD, NOTICE, TAIL and subsection COORD found also in
other types of notice forms, it must contain one or two subsection(s) OPERATION describing
technical characteristics of the day-time operation from local sunrise to local sunset (HJ)
and/or technical characteristics of the night-time operation from local sunset to local sunrise
(HN) (please see Table 3)
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 5
Even if the technical characteristics for day-time and night-time operation are the same, both
complete subsections OPERATION must still be provided, one for HJ and one for HN.
Table 3
The general structure of notice form T04
section
Subsection
sub-subsection
HEAD
NOTICE
COORD
OPERATION
TOWER
AUGMENTATION
TAIL
2.2.2 Subsection OPERATION may contain one or more numbered sub-subsections
TOWER, one per tower, which must be provided for directional or omnidirectional antennae
of a complex structure (antenna type B). If the antenna structure consists of only one simple
vertical tower (antenna type A), sub-subsection TOWER must not be provided. Instead, only
the value of electrical height of this simple vertical tower (t_hgt_elec) must be provided
within the relevant subsection OPERATION. The use of a tower structure other than 0, 1 and
2 is no longer accepted, since a combination of towers 0, 1 and 2 is sufficient to produce any
antenna diagram.
2.2.3 Subsection OPERATION may contain one or more numbered sub-subsections
AUGMENTATION, which must be provided for antenna type B with type of antenna
radiation pattern M (augmented or modified expanded). The purpose of the augmented
pattern is to put one or more “patches” on an expanded pattern. Each “patch” is referred to as
an augmentation. An augmentation may itself be augmented by a subsequent augmentation.
The numbering of augmentations has to follow the order described in point 2.8 of AN.2 to
RJ81 Agreement.
2.2.4 To identify uniquely the target assignment to be modified (in the Plan or in the MIFR)
the assigned frequency (t_trg_freq_assgn) and geographical coordinates (t_trg_long,
t_trg_lat) of the target are used. Alternatively, like in other notice forms for terrestrial
broadcasting, the unique identification code (given by the administration) of the target
assignment (t_trg_adm_ref_id) may be used. The unique identification code must remain
unique within the administration and the Plan or MIFR. However, it is recommended to use
assigned frequency and geographical coordinates for target identification in order to
minimize the potential for errors.
2.2.5 Submission or notification intended to MODIFY an existing recorded assignment
must contain a complete set of ALL MANDATORY DATA even if only one particular data
item is subject to modification. Otherwise this may lead to confusing results. For example, if
a submission or notification intended to modify only the HJ operation of an existing
assignment consisting of both HJ and HN operations does not provide also subsection
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 6
OPERATION for HN (with all data unchanged), then at the end of processing the HN
operation will be removed from the concerned assignment.
2.3 Notice Form TB6
Notice form TB6 is to be used for modification or addition of the unique identification code
(given by the administration) in the Plan or MIFR. To identify the target assignment, the
combination of its assigned frequency (t_trg_freq_assgn) and its geographical coordinates
(t_trg_long, t_trg_lat) may be used or, alternatively, its unique identification code (given by
the administration) (t_trg_adm_ref_id) if it already exists. The unique identification code
(given by the administration) must always remain unique within the administration and the
Plan or MIFR.
2.4 Notice Form TB7
2.4.1 Notice form TB7 is to be used for notification of frequency assignments in the sound
broadcasting service under Article 5 of the GE75 or RJ81 Agreements, with a view to their
recording in the Master International Frequency Register (MIFR) only when the
characteristics of the notified frequency assignments are identical to those appearing in the
assignment recorded in the Plan.
2.4.2 To uniquely identify the assignment in the GE75 or RJ81 Plan to be copied to the
MIFR the assigned frequency (t_plan_freq_assgn) and geographical coordinates
(t_plan_long, t_plan_lat) of the assignment in the Plan are used. Alternatively, like in other
terrestrial broadcasting notice forms, the unique identification code (given by the
administration) of the target assignment (t_plan_adm_ref_id) may be used.
2.4.3 If an assignment corresponding to the one in the Plan already exists in the MIFR,
Notice Form TB7 must also include its assigned frequency (t_trg_freq_assgn) and its
geographical coordinates (t_trg_long, t_trg_lat) or, alternatively, its unique identification
code (given by the administration) (t_trg_adm_ref_id), in order for the target in the MIFR to
be identified and replaced by a notified assignment having identical characteristics to those
recorded in the GE75 or RJ81 Plan.
2.4.4 It is recommended to use the assigned frequency and geographical coordinates to
uniquely identify the relevant assignments in the GE75 or RJ81 Plan and in the MIFR.
2.5 Notice Form TB8
Notice form TB8 is to be used to request the publication in Part B of a Special Section of an
assignment published in Part A.
2.5.1 Use of Notice Form TB8 with Respect to the GE75 Agreement
According to the GE75 Agreement, an assignment published in Part A to which there were no
objections within the prescribed time limit (16 weeks) after publication in Part A will not be
published automatically in Part B. An administration intending to record such an assignment
in the GE75 Plan has to submit within 12 months following (but no earlier than 16 weeks
from) the date of publication in Part A its request for publication in Part B using notice form
TB8 (see Rule of Procedure Part A3/GE75 Art 4. 3.2.12). Publication of an assignment in
Part B is equivalent to its entry into the GE75 Plan.
2.5.2 Use of Notice Form TB8 with Respect to the RJ81 Agreement
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 7
According to the RJ81 Agreement, an assignment published in Part A to which there were no
objections within the prescribed time limit (60 days) after publication in Part A will not be
published automatically in Part B. An administration intending to record such an assignment
in the RJ81 Plan has to submit within 180 days following (but not earlier than 60 days from)
the date of publication in Part A its request for publication in Part B using notice form TB8.
Publication of an assignment in Part B is equivalent to its entry into the RJ81 Plan.
2.5.3 To identify an assignment already published in Part A, the assigned frequency
(t_trg_freq_assgn) and its geographical coordinates (t_trg_long, t_trg_lat) are used or,
alternatively, its unique identification code (given by the administration) (t_trg_adm_ref_id).
2.6 Notice Form TB9
Notice form TB9 is to be used for withdrawing a notice under treatment or suppressing a
recorded assignment in the Plan or in MIFR.
To identify the target of the suppression or withdrawal, its assigned frequency
(t_trg_freq_assgn) and its geographical coordinates (t_trg_long, t_trg_lat) are used or,
alternatively, its unique identification code (given by the administration) (t_trg_adm_ref_id).
3.
Considerations regarding the file structure and other indications
3.1
The file and data structure to be used for submission and notification for LF and MF
sound broadcasting remains basically the same as described in Circular Letter CR/125 dated
30 July 1999. However, CR/125 did not require seconds to be provided when notifying
longitude and latitude. It is now required to also provide seconds (SS) for longitude and
latitude.
3.2
Tables 5 and 7 to 10 contain the description of the data items for the notice types
applicable to the sound broadcasting service under the GE75 Agreement.
3.3
Tables 6 to 10 contain the description of the data items for the notice types applicable
to the sound broadcasting service under the RJ81 Agreement.
3.4
Given the current processing arrangements within the BR, it would be preferable if
the notices T03, T04, TB6, TB7, TB8 and TB9 are submitted via ITU-R WISFAT in separate
files. Such an approach would contribute to smooth processing of all electronic notices.
3.5
If an electronic notice form is submitted containing a key-tag without providing a
value for the tag, this would be treated as an error. In such cases, the notice form will be
considered as incomplete and will be returned to the administration.
TABLE 4
Key to the symbols used in TABLES 5 to 10
X
Data item is mandatory information
+
Data item is mandatory under the specified conditions
O
Data item is optional
–
Data item which should not be provided
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 8
TABLE 5
T03 – Data Format of electronic notice for the addition or modification of an assignment in the GE75 Plan or MIFR.
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
(LF and MF sound broadcasting in Region 1 and MF sound broadcasting in Region 3)
<HEAD>
X
X
t_char_set = ISO-8859-1
O
O
ISO-8859-1
The character set used in the file.
t_d_sent = 2013-04-26
O
O
YYYY-MM-DD
The date of sending the notice.
t_adm = ALG
X
X
3 characters
The ITU symbol of the submitting or notifying administration within the GE75 Plan of Regions 1 and 3
(see the Preface to the BR IFIC).
t_email_addr =
testuser@ties.itu.int
O
O
Up to 30 characters of a
valid email address
The electronic mail address of a person submitting notices. It is used by BR to clarify the contents of
the file if needed.
</HEAD>
X
X
End of the HEAD section.
<NOTICE>
X
X
Beginning of NOTICE section containing data elements related to one notice. Use this section as many
times as there are notices in the file.
t_notice_type = T03
X
X
T03
The type of notice is T03 for the addition (t_action=ADD) or modification (t_action=MODIFY) of the
assignment in the GE75 Plan or MIFR. This notice form is used exclusively for LF and MF sound
broadcasting in Region 1 and for MF sound broadcasting in Region 3.
t_d_adm_ntc = 2013-04-24
O
O
YYYY-MM-DD
The date that the administration gives to this notice. This may be different than t_d_sent in the HEAD
section.
t_fragment = GE75
X
X
GE75 or NTFD_RR
The basis for the submission or notification.
Provide GE75 for the addition or modification of an assignment in the GE75 Plan (submission under
Article 4 of GE75 Agreement).
Provide NTFD_RR for the addition or modification of an assignment in the MIFR (notification under
Article 5 of GE75 Agreement).
t_action = MODIFY
X
X
ADD or MODIFY
The action to be taken regarding this notice
Permissible value(s)
Comments
Beginning of the HEAD section containing general data elements related to all notices. Use this section
only once in the file.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 9
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_ctry =ALG
X
X
ITU code of a
geographical area within
GE75 Plan of Regions 1
and 3
The ITU code of the geographical area in which the transmitting station is located (see the Preface to
the BR IFIC)
t_site_name = AIN EL
HADJAR
X
X
Up to 30 characters
The name of the locality by which the transmitting station is known or in which it is situated.
t_freq_assgn = 0.954
X
X
Numeric, with 3
decimals, 5 characters
For region 1:
The assigned frequency (MHz, from 0.153 to 0.279 and from 0.531 to 1.602 in 0.009 increments)
For region 3:
The assigned frequency (MHz, from 0.531 to 1.602 in 0.009 increments).
t_long = +0001512
X
X
+DDDMMSS
The longitude of the transmitting antenna site.
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees), MM (minutes) and SS (seconds) are mandatory
t_lat = +344327
X
X
+DDMMSS
The latitude of the transmitting antenna site.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees),
MM (minutes) and SS (seconds) are mandatory.
t_adm_ref_id = AIN EL
HADJAR 954
O
O
Up to 20 characters
The unique identification code given by the administration to the assignment.
t_trg_freq_assgn = 0.954
+
+
Numeric, with 3
decimals, 5 characters
For region 1:
The assigned frequency (MHz, from 0.153 to 0.279 and from 0.531 to 1.602 in 0.009 increments) of the
target assignment in the GE75 Plan or MIFR.
For region 3:
The assigned frequency (MHz, from 0.531 to 1.602 in 0.009 increments) of the target assignment in the
GE75 Plan or MIFR.
Permissible value(s)
Comments
Mandatory if t_action = MODIFY and t_trg_adm_ref_id is not provided.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 10
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_trg_long = +0001512
+
+
+DDDMMSS
The longitude of the transmitting antenna site of the target assignment to be modified in the GE75 Plan
or MIFR.
Mandatory if t_action = MODIFY and t_trg_adm_ref_id is not provided
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees), MM (minutes) and SS (seconds) are mandatory .
t_trg_lat = +344327
+
+
+DDMMSS
The latitude of the transmitting antenna site of the target assignment to be modified in the GE75 Plan or
MIFR.
Mandatory if t_action = MODIFY and t_trg_adm_ref_id is not provided.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees),
MM (minutes) and SS (seconds) are mandatory .
t_trg_adm_ref_id = AIN EL
HADJAR 954
+
+
Up to 20 characters
The unique identification code (given by the administration) to the target assignment to be modified in
the GE75 Plan or MIFR.
Mandatory if t_action = MODIFY and t_trg_freq_assgn and t_trg_long and t_trg_lat are not provided.
t_sync_net = 06001
+
+
Up to 20 characters
The identification symbols for the synchronized or single frequency network. Mandatory if the
assignmentpertains to such a network.
t_gnd_cond = 1
X
X
4000, 30, 10, 3, 1, 0.3,
0.1, 0.03, or 0.01
Ground conductivity in mS/m
t_d_inuse = 2011-01-01
-
X
YYYY-MM-DD
The date (actual or foreseen, as appropriate) of bringing the frequency assignment (new or modified)
into use .
t_op_agcy = 001
–
O
3 characters
The symbol for the operating agency from Section 3 of Chapter IV of the Preface to the BR IFIC.
t_addr_code =A
–
X
1 character
The symbol for the address of the administration responsible for the station(from Section 3 of Chapter
IV of the Preface to the BR IFIC) and to which communication should be sent on urgent matters
regarding interference, quality of emissions and questions referring to the technical operation of the
circuit (see also Article 15 of the RR).
t_call_sign =
O
O
Up to10 characters
The call sign identification used in accordance with Article 19 of the RR.
t_station_id = RADIO
ALGERIENNE
O
O
Up to 20 characters
The station identification used in accordance with Article 19 of the RR.
t_remarks = SAMPLE01 ONLY
O
O
Up to 80 characters
Any comment intended to assist the BR in processing the notice.
Permissible value(s)
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
Comments
PAGE 11
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
<OPERATION>
X
X
t_op_prd_cde =HJ
X
X
HJ or HN
The local operation period code.
Use HJ for day-time operation (between the times of local sunrise and local sunset).
Use HN for night-time operation (between the times of local sunset and local sunrise).
t_pwr_kw = 50
X
X
Between 0.01 and 2000
The power, in kW, delivered to the antenna.
t_e_max = 17
X
X
Max 40.00
Maximum effective monopole radiated power in dB(kW)
t_bdwdth =9.00
X
X
Max 20.00
The necessary bandwidth, in kHz.
t_tran_sys =ANALOG
+
+
ANALOG
DRM_A2
DRM_B2
The code corresponding to the sound broadcasting transmission system. For submission under Art.4
and notification under Art.5 of GE75 Agreement of an assignment with exclusively analogue
modulation only value (ANALOG) is allowed. This is the default value of the data item.
Submission of a Plan modification proposal or notification of an assignment with digital modulation is
possible under Rule of Procedure A3/GE75/Ann. 2 4.4 and Rule of Procedure A3/GE75/Res. 8 (or
under 8.4 of RR for notification only). In such a case t_tran_sys is mandatory with a value chosen
from: DRM_A2 or DRM_B2 (see ITU-R Rec.BS.1514 and BS.1615).
t_emi_cls = A3E--
X
X
From 3 up to 5 characters
The class of emission according to Appendix 1 to the Radio Regulations.
t_ant_type =A
O
O
one character
The symbol identifying the type of antenna: (A or B)
A – a single vertical antenna,
B – a directional or omnidirectional antenna of complex construction.
Permissible value(s)
Comments
Beginning of subsection OPERATION. It can only appear once or twice within a section
NOTICE(once for daytime operation, once for night-time operation).
The type of antenna is implicitly determined by the presence of item t_ant_hgt_m (for type A) or the
presence of the <PATTERN> section (for type B) and therefore is not required.
t_ant_hgt_m =75
+
+
Numeric, with 1 decimal,
5 characters
Transmitting antenna physical length in metres. Required for a simple antenna (type A). Must not be
provided for a directional and/or complex antenna (type B)
t_adj_ratio
X
X
0, 5, 7, or 9
Adjacent channel protection ratio in dB
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 12
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_op_hh_fr = 06:00
O
O
HH:MM
HH from 00 to 24
MM from 00 to 59
Starting time of the regular hours (UTC) of operation of the frequency assignment .
t_op_hh_to = 17:59
O
O
HH:MM
HH from 00 to 24
MM from 00 to 59
Ending time of the regular hours (UTC) of operation of the frequency assignment .
<PATTERN>
+
+
Beginning of sub-subsection PATTERN which is mandatory for a directional and/or complex antenna
(type B). Only one such sub-subsection may appear in an <OPERATION>. This sub-subsection must
not be provided for a simple antenna (type A).
<GAIN>
+
+
Beginning of the sub-sub-subsection GAIN. For day-time operation, this sub-sub-subsection must
appear once for a complex antenna, to describe the radiation pattern in the horizontal plane (t_elev = 0).
For night-time operation, this sub-sub-subsection must appear 10 times, once for each elevation in 10degree increments (t_elev = 0, 10, …, 90)
t_elev =0
+
+
0, 10, …, 90
The elevation in degrees
t_gain@azmzzz = 3.0
+
+
Numeric, with 1 decimal,
7 characters
The value of the gain in dB at 36 different azimuths in 10° intervals, measured in the horizontal plane
from True North in a clockwise direction (zzz from 000 to 350 in 10° intervals).
Permissible value(s)
Comments
Example: t_gain@azm030 = 2.0
</GAIN>
+
+
End of sub-sub-subsection GAIN.
</PATTERN>
+
+
End of sub-subsection PATTERN.
</OPERATION>
X
X
End of subsection OPERATION.
<COORD>
+
O
Beginning of subsection COORD. Subsection COORD is mandatory for submission under Art. 4 if an
agreement has been successfully effected with one or more administrations. It can appear only once
within section NOTICE.
t_adm = MRC
+
+
</COORD>
+
+
End of subsection COORD.
</NOTICE>
X
X
End of NOTICE section.
3 characters
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
The ITU symbol designating one administration within the GE75 Plan of Regions 1 and 3, with which
coordination has been successfully completed. If there are more, repeat t_adm=ADM as many times as
appropriate, one pair key=value in one line.
PAGE 13
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
<TAIL>
X
X
t_num_notices =1
X
X
</TAIL>
X
X
Permissible value(s)
Comments
Beginning of TAIL section indicating the total number of notices in the notification file.
Integer
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
The number of notices contained in the file.
End of TAIL section. End of the notification file.
PAGE 14
TABLE 6
T04 – Data Format of electronic notice for the addition or modification of an assignment in the RJ81 Plan or MIFR.
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
(MF sound broadcasting in Region 2)
<HEAD>
X
X
t_char_set = ISO-8859-1
O
O
ISO-8859-1
The character set used in the file.
t_d_sent = 2013-04-26
O
O
YYYY-MM-DD
The date of sending the notice.
t_adm = GRD
X
X
3 characters
The ITU symbol of the submitting or notifying administration within the RJ81 Plan of Region 2 (see
the Preface to the BR IFIC).
Up to 30 characters of a
valid email address
The electronic mail address of a person submitting notices. It is used by BR to clarify the contents of
the file if needed.
Permissible value(s)
Comments
Beginning of the HEAD section containing general data elements related to all notices. Use this section
only once in the file.
t_email_addr =
testuser@ties.itu.int
O
O
</HEAD>
X
X
End of the HEAD section.
<NOTICE>
X
X
Beginning of NOTICE section containing data elements related to one notice. Use this section as many
times as there are notices in the file.
t_notice_type = T04
X
X
T04
The type of notice is T04 for the addition (t_action= ADD) or modification (t_action=MODIFY) of the
assignment in the RJ81 Plan or MIFR. This notice form is used exclusively for MF sound broadcasting
in Region 2.
t_d_adm_ntc = 2013-04-24
O
O
YYYY-MM-DD
The date that the administration gives to this notice. This may be different than t_d_sent in the HEAD
section.
t_fragment = RJ81
X
X
RJ81 or NTFD_RR
The basis for the submission or notification.
Provide RJ81 for the addition or modification of an assignment in the RJ81 Plan (submission under
Article 4 of RJ81 Agreement).
Provide NTFD_RR for the addition or modification of an assignment in the MIFR (including
notification under Article 5 of RJ81 Agreement).
t_action = MODIFY
X
X
ADD or MODIFY
The action to be taken regarding this notice
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 15
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_ctry =GRD
X
X
ITU code of a
geographical area within
RJ81 Plan of Region 2
The ITU code of the geographical area in which the transmitting station is located (see the Preface to
the BR IFIC)
t_site_name = PARADISE
X
X
Up to 30 characters
t_freq_assgn = 1.29
X
X
Numeric, with 3
decimals, 5 characters
The name of the locality by which the transmitting station is known or in which it is situated.
The assigned frequency (MHz, from 0.53 to 1.70 in 0.01 increments). Values below 0.54 and above
1.60 are allowed if t_fragment= NTFD_RR (see Art.5 of RR: Table of Frequency Allocation for
Region 2).
t_long = -0614133
X
X
+DDDMMSS
The longitude of the transmitting antenna site.
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees), MM (minutes) and SS (seconds) are mandatory
t_lat = +120827
X
X
+DDMMSS
The latitude of the transmitting antenna site.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees),
MM (minutes) and SS (seconds) are mandatory.
t_adm_ref_id = PARADISE129
O
O
Up to 20 characters
The unique identification code given by the administration to the assignment.
t_trg_freq_assgn = 1.29
+
+
Numeric, with 3
decimals, 5 characters
The assigned frequency (MHz, from 0.53 to 1.70 in 0.01 increments) of the target assignment to be
modified in the RJ81 Plan or MIFR.
Mandatory if t_action = MODIFY and t_trg_adm_ref_id is not provided.
Values below 0.54 and above 1.60 are allowed if t _fragment= NTFD_RR (see Art.5 of RR: Table of
Frequency Allocation for Region 2).
t_trg_long = -0614133
+
+
+DDDMMSS
The longitude of the transmitting antenna site of the target assignment to be modified in the RJ81 Plan
or MIFR.
Mandatory if t_action = MODIFY and t_trg_adm_ref_id is not provided
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees), MM (minutes) and SS (seconds) are mandatory .
Permissible value(s)
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
Comments
PAGE 16
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_trg_lat = +120827
+
+
+DDMMSS
The latitude of the transmitting antenna site of the target assignment to be modified in the RJ81 Plan or
MIFR.
Mandatory if t_action = MODIFY and t_trg_adm_ref_id is not provided.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees),
MM (minutes) and SS (seconds) are mandatory .
t_trg_adm_ref_id =
PARADISE01
+
+
Up to 20 characters
The unique identification code (given by the administration) to the target assignment to be modified in
the RJ81 Plan or MIFR.
Mandatory if t_action = MODIFY and t_trg_freq_assgn and t_trg_long and t_trg_lat are not provided.
t_rj81_cls =C
X
X
A, B or C
RJ81 class of station (for definitions see Chapter 1 of Annex 2 of RJ81 Agreement).
t_sync_net = 06001
+
+
Up to 20 characters
The identification symbols for the synchronized or single frequency network. Mandatory if the
assignment pertains to such a network.
t_d_inuse = 2011-01-01
-
X
YYYY-MM-DD
The date (actual or foreseen, as appropriate) of bringing the frequency assignment (new or modified)
into use.
t_op_agcy = 001
–
O
3 characters
The symbol for the operating agency from Section 3 of Chapter IV of the Preface to the BR IFIC.
t_addr_code =A
–
X
1 character
The symbol for the address of the administration responsible for the station (from Section 3 of Chapter
IV of the Preface to the BR IFIC) and to which communication should be sent on urgent matters
regarding interference, quality of emissions and questions referring to the technical operation of the
circuit (see also Article 15 of the RR).
t_call_sign = WPAI
O
O
Up to10 characters
The call sign identification used in accordance with Article 19 of the RR.
t_station_id =
O
O
Up to 20 characters
The station identification used in accordance with Article 19 of the RR.
t_remarks = SAMPLE01 ONLY
O
O
Up to 80 characters
Any comment intended to assist the BR in processing the notice.
<OPERATION>
X
X
t_op_prd_cde =HJ
X
X
Permissible value(s)
Comments
Beginning of subsection OPERATION. It can only appear once or twice within a section NOTICE
(once for daytime operation, once for night-time operation).
HJ or HN
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
The local operation period code.
Use HJ for day-time operation (between the times of local sunrise and local sunset).
Use HN for night-time operation (between the times of local sunset and local sunrise).
PAGE 17
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_pwr_kw =1.25
X
X
Permissible value(s)
Comments
Numeric, with 2
decimals, 5 characters
Max values for class:
A: HJ 100 (³), HN 50 (³)
B: 50
C: HJ 1 (nz=1), 5(nz=2),
C: HN 1
The power, in kW, delivered to the antenna. The maximum permissible values depend on RJ81 class of
station (A,B,C), local operation period code (HJ, HN) and noise zone (nz=1,2).
(³) If t_action= MODIFY then the power of any class A station exceeding 100 kW by day, or 50 kW
by night shall not be increased.
Min value 0.01
t_e_rms =314.06
X
X
Numeric, with 2
decimals, 8 characters
The r.m.s. value of radiation (field strength), in mV/m at 1 km. The product of the r.m.s. characteristic
field strength in the horizontal plane and the square root of the power. The r.m.s. value of radiation
must remain within 10% of the calculated radiation based upon a one ohm loss per tower (see Annex 1
to Resolution 2 of RJ81 Agreement).
t_bdwdth =10.00
X
X
Max 20.00
The necessary bandwidth, in kHz.
t_tran_sys =ANALOG
O
+
Art.4: ANALOG
Art.5: ANALOG
IBOC_HYBRID
IBOC_ALL_DIG
DRM_A2
DRM_B2
The code corresponding to the sound broadcasting transmission system. For submission under Art.4
and notification under Art.5 of RJ81 Agreement of an assignment with exclusively analogue
modulation only value (ANALOG) is allowed. This is the default value of the data item.
At present, submission under Art.4 of RJ81 of an assignment with digital or hybrid modulation is not
allowed in Region 2. However a notification of an assignment with digital or hybrid modulation may be
possible under Art. 5.4 of RJ81 Agreement or under 8.4 of RR. In such a case t_tran_sys is mandatory
with a value chosen from: IBOC_HYBRID, IBOC_ALL_DIG, DRM_A2, DRM_B2 (see ITU-R
Rec.BS.1615).
t_emi_cls = A3E--
X
X
From 3 up to 5 characters
The class of emission according to Appendix 1 to the Radio Regulations.
t_ant_type =A
X
X
one character
The symbol identifying the type of antenna: (A or B)
A – a single vertical antenna,
B – a directional or omnidirectional antenna of complex construction.
t_hgt_elec =99.7
+
+
Numeric, with 1 decimal,
5 characters
The electrical height, in degrees, of a single vertical antenna. Mandatory if t_ant_type = A.
t_ptrn_type =E
+
+
one character
The symbol identifying the type of antenna radiation pattern T, E or M. Mandatory if t_ant_type = B.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 18
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_q_fact =10.00
O
O
Numeric, with 2
decimals, 6 characters
The special quadrature factor, in mV/m at 1 km. Optional if t_ptrn_type = E or M, and not to be
provided otherwise. The special quadrature factor may be used to replace the normal expanded
quadrature factor when special precautions are taken to ensure pattern stability.
t_op_hh_fr = 06:00
O
O
HH:MM
HH from 00 to 24
MM from 00 to 59
Starting time of the regular hours (UTC) of operation of the frequency assignment .
t_op_hh_to = 17:59
O
O
HH:MM
HH from 00 to 24
MM from 00 to 59
Ending time of the regular hours (UTC) of operation of the frequency assignment .
<TOWER>
+
+
t_twr_no =1
X
X
Integer
The serial number of the tower whose characteristics are described within this sub-subsection.
t_structure =0
X
X
Integer
The symbol corresponding to the antenna structure. Use 0 (simple vertical tower), 1 (top-loaded tower)
or 2 (sectionalized tower).
t_fld_ratio =1.000
+
+
Numeric, with 3
decimals, 6 characters
The ratio of the tower field to the field of the reference tower (relative field). Mandatory if the antenna
consists of two or more towers, and not to be provided otherwise. It is recommended to normalize it to
a maximum value of 1.
t_phase_diff =132.80
+
+
Numeric, with 2
decimals, 6 characters
The phase difference in the tower field with respect to the field of the reference tower, in degrees
(relative phase From 0.00 to 359.99). Mandatory if the antenna consists of two or more towers, and
not to be provided otherwise.
Negative values should be converted to equivalent positive (example: -120 to be converted to 240).
t_spacing =186.80
+
+
Numeric, with 2
decimals, 6 characters
The electrical spacing of the tower from the reference point, in degrees. Mandatory if the antenna
consists of two or more towers, and not to be provided otherwise.
t_orient =75.30
+
+
Numeric, with 2
decimals, 6 characters
The angular orientation of the tower from the reference point, in degrees clockwise from True North
(azimuth from 0.00 to 359.99). Mandatory if the antenna consists of two or more towers, and not to be
provided otherwise.
t_hgt_elec =99.7
+
+
Numeric, with 1 decimal,
5 characters
The electrical height, in degrees, of the tower for which t_structure=0 (simple vertical tower, neither
top-loaded nor sectionalized). Mandatory if t_structure=0, otherwise not to be provided.
Permissible value(s)
Comments
Beginning of sub-subsection TOWER which is mandatory if t_ant_type = B. Use this sub-subsection
as many times as there are towers in the structure of the type B antenna.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 19
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_tls_a =39.5
+
+
Numeric, with 1 decimal,
5 characters
The description of Parameter A of a top-loaded or sectionalized tower.
Not to be provided for t_structure = 0.
Mandatory if t_structure>0.
If t_structure=1, then t_tls_a is the electrical height of the tower (in degrees)
If t_structure=2, then t_tls_a is the electrical height of the lower section of the tower (in degrees)
t_tls_b =21.0
+
+
Numeric, with 1 decimal,
5 characters
The description of Parameter B of a top-loaded or sectionalized tower. Mandatory if t_structure=1,2.
If t_structure=1, then t_tls_b is the difference between the apparent electrical height (based on
current distribution) and actual electrical height of the tower (in degrees)
If t_structure=2, then t_tls_b is the difference between the apparent electrical height (based on
current distribution) of the lower section and actual electrical height of the lower section of the tower
(in degrees).
Not to be provided for t_structure= 0
t_tls_c =6.8
+
+
Numeric, with 1 decimal,
5 characters
The description of Parameter C of a top-loaded or sectionalized tower. Mandatory if t_structure=2.
t_tls_c is the actual total electrical height of the tower (in degrees).
Not to be provided for other values of t_structure
t_tls_d =0.3
+
+
Numeric, with 1 decimal,
5 characters
The description of Parameter D of a top-loaded or sectionalized tower. Mandatory if t_structure=2.
t_tls_d is the difference between the apparent electrical height (based on current distribution) of the
total tower and the actual total electrical height of the tower (in degrees).
Not to be provided for other values of t_structure
</TOWER>
+
+
End of sub-subsection TOWER.
<AUGMENTATION>
+
+
Beginning of the sub-subsection AUGMENTATION which is mandatory if t_ptrn_type = M. Use this
sub-subsection as many times as there are augmentations in the antenna diagram.
t_aug_no =1
X
X
Integer
The serial number of the augmentation whose characteristics are described within this sub-subsection.
t_aug_e =712.80
X
X
Numeric, with 1 decimal,
7 characters
The value of the radiation at the central azimuth of the augmentation, in mV/m at 1 km.
t_aug_azm =238.6
X
X
Numeric, with 2
decimals, 6 characters
The central azimuth of the augmentation (centre of the span) in degrees, from 0 to 359.99 deg.
Permissible value(s)
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
Comments
PAGE 20
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_aug_span =20.0
X
X
</AUGMENTATION>
+
+
End of sub-subsection AUGMENTATION.
</OPERATION>
X
X
End of subsection OPERATION.
<COORD>
+
O
Beginning of subsection COORD. Subsection COORD is mandatory for submission under Art. 4 if an
agreement has been successfully effected with one or more administrations. It can appear only once
within section NOTICE.
t_adm = VEN
+
+
</COORD>
+
+
End of subsection COORD.
</NOTICE>
X
X
End of NOTICE section.
<TAIL>
X
X
Beginning of TAIL section indicating the total number of notices in the notification file.
t_num_notices =1
X
X
</TAIL>
X
X
Permissible value(s)
Numeric, with 2
decimals, 6 characters
3 characters
Integer
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
Comments
The total span of the augmentation, in degrees.
The ITU symbol designating one administration within the RJ81 Plan of Region 2, with which
coordination has been successfully completed. If there are more, repeat t_adm=ADM as many times as
appropriate, one key=value pair per line.
The number of notices contained in the file.
End of TAIL section. End of the notification file.
PAGE 21
TABLE 7
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
TB6 – Data Format of electronic notice for modification of administration unique identifier in the Plan or MIFR
<HEAD>
X
X
t_char_set = ISO-8859-1
O
O
ISO-8859-1
The character set used in the file.
t_d_sent = 2013-04-26
O
O
YYYY-MM-DD
The date of sending the notice.
t_adm = GRD
X
X
3 characters
The ITU symbol of the submitting or notifying administration (see the Preface to the BR IFIC).
t_email_addr =
testuser@ties.itu.int
O
O
Up to 30 characters
The valid electronic mail address of a person submitting notices. It is used by BR to clarify the contents
of the file if needed.
</HEAD>
X
X
End of the HEAD section.
<NOTICE>
X
X
Beginning of NOTICE section containing data elements related to one notice. Use this section as many
times as there are notices in the file.
t_notice_type = TB6
X
X
TB6
The type of notice is TB6 for modification of the administration unique identifier in the Plan concerned
or MIFR. (This notice form may be used for other Plans).
t_d_adm_ntc = 2013-04-24
O
O
YYYY-MM-DD
The date that the administration gives to this notice. This may be different than t_d_sent in the HEAD
section.
t_fragment = RJ81
X
X
GE75, RJ81 or
NTFD_RR
The basis for the modification of the administration unique identifier in the Plan concerned or MIFR.
Provide GE75 for a modification of the administration unique identifier in the GE75 Plan.
Provide RJ81 for a modification of the administration unique identifier in the RJ81 Plan.
Provide NTFD_RR for a modification of the administration unique identifier in the MIFR.
t_action = ADMINID
X
X
ADMINID
The action to be taken regarding this notice.
Permissible value(s)
Comments
Beginning of the HEAD section containing general data elements related to all notices. Use this section
only once in the file.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 22
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_trg_freq_assgn =0.54
+
+
Permissible value(s)
Numeric, with 3
decimals, 5 characters
Comments
For region 1:
The assigned frequency (MHz, from 0.153 to 0.279 and from 0.531 to 1.602 in 0.009 increments) of the
target assignment of which the administration unique identifier is to be modified in the GE75 Plan or
MIFR.
For region 2:
The assigned frequency (MHz, from 0.53 to 1.70 in 0.01 increments) of the target assignment of which
the administration unique identifier is to be modified in the RJ81 Plan or MIFR.
Values below 0.54 and above 1.60 are allowed if t _fragment= NTFD_RR (see Art.5 of RR: Table of
Frequency Allocation for Region 2).
For region 3:
The assigned frequency (MHz, from 0.531 to 1.602 in 0.009 increments) of the target assignment of
which the administration unique identifier is to be modified in the GE75 Plan or MIFR.
Mandatory if t_trg_adm_ref_id is not provided.
t_trg_long = -0614604
+
+
+DDDMMSS
The longitude of the transmitting antenna site of the target assignment for which the administration
unique identifier is to be modified in the GE75 Plan, RJ81 Plan or MIFR. Mandatory if
t_trg_adm_ref_id is not provided
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees) MM (minutes) and SS (seconds) are mandatory .
t_trg_lat = +120120
+
+
+DDMMSS
The latitude of the transmitting antenna site of the target assignment for which the administration
unique identifier is to be modified in the GE75 Plan, RJ81 Plan or MIFR. Mandatory if
t_trg_adm_ref_id is not provided.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees)
MM (minutes) and SS (seconds) are mandatory .
t_trg_adm_ref_id
=OLDREFID0
+
+
Up to 20 characters
The unique identification code (given by the administration) of the target assignment for which the
administration unique identifier is to be modified in the GE75 Plan, RJ81 Plan or MIFR. Mandatory if
t_trg_freq_assgn and t_trg_long and t_trg_lat are not provided.
t_adm_ref_id =NEWREFID1
X
X
Up to 20 characters
The unique identification code (given by the administration) to replace that of the target assignment in
the GE75 Plan, RJ81 Plan or MIFR. It must be unique within the administration and the fragment.
t_remarks = adm_ref_id change
O
O
Up to 80 characters
Any comment intended to assist the BR in processing the notice.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 23
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
</NOTICE>
X
X
End of NOTICE section.
<TAIL>
X
X
Beginning of TAIL section indicating the total number of notices in the notification file.
t_num_notices =1
X
X
</TAIL>
X
X
Permissible value(s)
Integer
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
Comments
The number of notices contained in the file.
End of TAIL section. End of the notification file.
PAGE 24
TABLE 8
Section markers (in bold),
data items and example values
in recommended format
Art. 5
TB7 – Data Format of electronic notice for notification under Article 11 of RR of an assignment with technical characteristics identical to those appearing in the
GE75 or RJ81 Plan
<HEAD>
X
t_char_set = ISO-8859-1
O
ISO-8859-1
The character set used in the file
t_d_sent = 2013-04-26
O
YYYY-MM-DD
The date of sending the notice.
t_adm = GRD
X
3 characters
The ITU symbol of the submitting or notifying administration (see the Preface to the BR IFIC).
t_email_addr =
testuser@ties.itu.int
O
Up to 30 characters
The electronic mail address of a person submitting notices. It is used by BR to clarify the contents of
the file if needed.
</HEAD>
X
End of the HEAD section.
<NOTICE>
X
Beginning of NOTICE section containing data elements related to one notice. Use this section as many
times as there are notices in the file.
t_notice_type = TB7
X
TB7
The type of notice is TB7 for notification under Art.11 of RR of an assignment with all characteristics
as in the Plan concerned..
t_d_adm_ntc = 2013-04-24
O
YYYY-MM-DD
The date that the administration gives to this notice. This may be different than t_d_sent in the HEAD
section.
t_plan = RJ81
X
GE75 or RJ81
The name of the PLAN concerned.
t_action = CONFORM
X
CONFORM
The action to be taken regarding this notice.
Permissible value(s)
Comments
Beginning of the HEAD section containing general data elements related to all notices. Use this section
only once in the file.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 25
Section markers (in bold),
data items and example values
in recommended format
Art. 5
t_trg_freq_assgn = 0.54
+
Permissible value(s)
Numeric, with 3
decimals, 5 characters
Comments
For region 1:
The assigned frequency (MHz, from 0.153 to 0.279 and from 0.531 to 1.602 in 0.009 increments) of the
target assignment recorded in the MIFR, if any.
For region 2:
The assigned frequency (MHz, from 0.53 to 1.70 in 0.01 increments) of the target assignment recorded
in the MIFR, if any.
For region 3:
The assigned frequency (MHz, from 0.531 to 1.602 in 0.009 increments) of the target assignment
recorded in the MIFR, if any.
Mandatory if a target assignment recorded in the MIFR exists and t_trg_adm_ref_id is not provided.
t_trg_long = -0614604
+
+DDDMMSS
The longitude of the transmitting antenna site of the target assignment recorded in the MIFR, if any.
Mandatory if a target assignment recorded in the MIFR exists and t_trg_adm_ref_id is not provided.
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees) MM (minutes) and SS (seconds) are mandatory .
t_trg_lat = +120120
+
+DDMMSS
The latitude of the transmitting antenna site of the target assignment recorded in the MIFR, if any.
Mandatory if a target assignment recorded in the MIFR exists and t_trg_adm_ref_id is not provided.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees)
MM (minutes) and SS (seconds) are mandatory .
t_trg_adm_ref_id =
NEWREFID1
+
Up to 20 characters
The unique identification code (given by the administration) to the target assignment recorded in the
MIFR, if any. Mandatory if a target assignment recorded in the MIFR exists and t_trg_freq_assgn and
t_trg_long and t_trg_lat are not provided.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 26
Section markers (in bold),
data items and example values
in recommended format
Art. 5
t_plan_freq_assgn =0.54
+
Permissible value(s)
Numeric, with 3
decimals, 5 characters
Comments
For region 1:
The assigned frequency (MHz, from 0.153 to 0.279 and from 0.531 to 1.602 in 0.009 increments) of the
assignment recorded in the Plan which is to be copied to the MIFR.
For region 2:
The assigned frequency (MHz, from 0.54 to 1.60 in 0.01 increments) of the assignment recorded in the
Plan which is to be copied to the MIFR.
For region 3:
The assigned frequency (MHz, from 0.531 to 1.602 in 0.009 increments) of the assignment recorded in
the Plan which is to be copied to the MIFR.
Mandatory if t_plan_adm_ref_id is not provided.
t_plan_long = -0614604
+
+DDDMMSS
The longitude of the transmitting antenna site of the assignment recorded in the PLAN which is to be
copied to the MIFR. Mandatory if t_plan_adm_ref_id is not provided.
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees) MM (minutes) and SS (seconds) are mandatory .
t_plan_lat = +120120
+
+DDMMSS
The latitude of the transmitting antenna site of the assignment recorded in the PLAN which is to be
copied to the MIFR. Mandatory if t_plan_adm_ref_id is not provided.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees)
MM (minutes) and SS (seconds) are mandatory .
t_plan_adm_ref_id =
NEWREFID2
+
Up to 20 characters
The unique identification code (given by the administration) of the assignment recorded in the Plan
which is to be copied to the MIFR. Mandatory if t_plan_freq_assgn and t_plan_long and t_plan_lat
are not provided..
t_d_inuse = 2011-01-24
X
YYYY-MM-DD
The date (actual or foreseen, as appropriate) of bringing the frequency assignment (new or modified)
into use .
t_op_agcy =001
O
3 characters
The symbol for the operating agency from Section 3 of Chapter IV of the Preface to the BR IFIC.
t_addr_code =A
X
1 character
The symbol for the address of the administration responsible for the station(from Section 3 of Chapter
IV of the Preface to the BR IFIC) and to which communication should be sent on urgent matters
regarding interference, quality of emissions and questions referring to the technical operation of the
circuit (see also Article 15 of the RR).
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 27
Section markers (in bold),
data items and example values
in recommended format
Art. 5
<OPERATION>
+
t_op_prd_cde =HJ
+
HJ or HN
The local operation period code.
Use HJ for day-time operation (between the times of local sunrise and local sunset).
Use HN for night-time operation (between the times of local sunset and local sunrise).
t_op_hh_fr = 06:00
O
HH:MM
HH from 00 to 24
MM from 00 to 59
Starting time of the regular hours (UTC) of operation of the frequency assignment .
t_op_hh_to = 17:59
O
HH:MM
HH from 00 to 24
MM from 00 to 59
Ending time of the regular hours (UTC) of operation of the frequency assignment .
</OPERATION>
+
t_remarks = Test Only
O
</NOTICE>
X
End of NOTICE section.
<TAIL>
X
Beginning of TAIL section indicating the total number of notices in the notification file.
t_num_notices =1
X
</TAIL>
X
Permissible value(s)
Comments
Beginning of subsection OPERATION. It can only appear once or twice within a section
NOTICE(once for daytime operation, once for night-time operation), corresponding to the operation(s)
of the recorded Plan entry. This subsection is only required if operating hours are provided.
End of subsection OPERATION.
Up to 80 characters
Integer
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
Any comment intended to assist the BR in processing the notice.
The number of notices contained in the file.
End of TAIL section. End of the notification file.
PAGE 28
TABLE 9
Section markers (in bold),
data items and example values
in recommended format
Art. 4
TB8 – Data Format of electronic notice for request of the publication in Part B of the Special Section of an assignment published in Part A
<HEAD>
X
t_char_set = ISO-8859-1
O
ISO-8859-1
The character set used in the file.
t_d_sent = 2013-04-26
O
YYYY-MM-DD
The date of sending the notice.
t_adm = GRD
X
3 characters
The ITU symbol of the submitting administration (see the Preface to the BR IFIC).
t_email_addr =
testuser@ties.itu.int
O
Up to 30 characters of a
valid email address
The electronic mail address of a person submitting notices. It is used by BR to clarify the contents of
the file if needed.
</HEAD>
X
End of the HEAD section.
<NOTICE>
X
Beginning of NOTICE section containing data elements related to one notice. Use this section as many
times as there are notices in the file.
t_notice_type = TB8
X
TB8
The type of notice is TB8 for request of the publication of a modification to the RJ81 or GE75 Plan in
Part B of the Special Section.
t_d_adm_ntc = 2013-04-24
O
YYYY-MM-DD
The date that the administration gives to this notice. This may be different than t_d_sent in the HEAD
section.
t_plan = RJ81
X
GE75 or RJ81
The name of the PLAN concerned.
t_action = PARTB
X
PARTB
The action to be taken regarding this notice.
Permissible value(s)
Comments
Beginning of the HEAD section containing general data elements related to all notices. Use this section
only once in the file.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 29
Section markers (in bold),
data items and example values
in recommended format
Art. 4
t_trg_freq_assgn = 0.54
+
Permissible value(s)
Numeric, with 3
decimals, 5 characters
Comments
For region 1:
The assigned frequency (MHz, from 0.153 to 0.279 and from 0.531 to 1.602 in 0.009 increments) of the
target assignment (already published in Part A of a Special Section).
For region 2:
The assigned frequency (MHz, from 0.54 to 1.60 in 0.01 increments) of the target assignment (already
published in Part A of a Special Section).
For region 3:
The assigned frequency (MHz, from 0.531 to 1.602 in 0.009 increments) of the target assignment
(already published in Part A of a Special Section).
Mandatory if t_trg_adm_ref_id is not provided.
t_trg_long = -0614604
+
+DDDMMSS
The longitude of the transmitting antenna site of the target assignment (already published in Part A of a
Special Section). Mandatory if t_trg_adm_ref_id is not provided.
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees) MM (minutes) and SS (seconds) are mandatory .
t_trg_lat = +120120
+
+DDMMSS
The latitude of the transmitting antenna site of the target assignment (already published in Part A of a
Special Section). Mandatory if t_trg_adm_ref_id is not provided.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees)
MM (minutes) and SS (seconds) are mandatory .
t_trg_adm_ref_id =
ADMREFID1
+
Up to 20 characters
The unique identification code (given by the administration) of the assignment (already published in
Part A of a Special Section). Mandatory if t_trg_freq_assgn and t_trg_long and t_trg_lat are not
provided.
t_remarks = Test notice only
O
Up to 80 characters
Any comment intended to assist the BR in processing the notice.
<COORD>
+
t_adm = VEN
+
Beginning of subsection COORD. Subsection COORD is mandatory if an agreement has been
successfully effected with one or more administrations. It can appear only once within section
NOTICE.
3 characters
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
The ITU symbol designating one administration with which coordination has been successfully
completed. If there are more, repeat t_adm=ADM as many times as appropriate, one pair key=value in
one line.
PAGE 30
Section markers (in bold),
data items and example values
in recommended format
Art. 4
</COORD>
+
Beginning of subsection COORD. Subsection COORD is mandatory if an agreement has been
successfully effected with one or more administrations. It can appear only once within section
NOTICE.
</NOTICE>
X
End of NOTICE section.
<TAIL>
X
Beginning of TAIL section indicating the total number of notices in the notification file.
t_num_notices =1
X
</TAIL>
X
Permissible value(s)
Integer
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
Comments
The number of notices contained in the file.
End of TAIL section. End of the notification file.
PAGE 31
TABLE 10
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
TB9 – Data Format of electronic notice for withdrawing a notice under treatment or suppressing a recorded assignment in the Plan or in the MIFR
<HEAD>
X
X
t_char_set = ISO-8859-1
O
O
ISO-8859-1
The character set used in the file.
t_d_sent = 2013-04-26
O
O
YYYY-MM-DD
The date of sending the notice.
t_adm = GRD
X
X
3 characters
The ITU symbol of the submitting or notifying administration (see the Preface to the BR IFIC).
t_email_addr =
testuser@ties.itu.int
O
O
Up to 30 characters
The electronic mail address of a person submitting notices. It is used by BR to clarify the contents of
the file if needed.
</HEAD>
X
X
End of the HEAD section.
<NOTICE>
X
X
Beginning of NOTICE section containing data elements related to one notice. Use this section as many
times as there are notices in the file.
t_notice_type =TB9
X
X
TB9
The type of notice is TB9 for withdrawal or suppression of a notice or an assignment of LF or MF
sound broadcasting.
t_d_adm_ntc = 2013-04-24
O
O
YYYY-MM-DD
The date that the administration gives to this notice. This may be different than t_d_sent in the HEAD
section.
t_fragment = RJ81
X
X
GE75, RJ81 or
NTFD_RR
The basis for withdrawal or suppression.
Provide GE75 if withdrawal or suppression takes effect in the GE75 Plan, or provide RJ81 if
withdrawal or suppression takes effect in the RJ81 Plan,
Provide NTFD_RR if withdrawal or suppression takes effect in the MIFR.
t_action = SUPPRESS
X
X
SUPPRESS or
WITHDRAW
The action to be taken regarding this notice.
Permissible value(s)
Comments
Beginning of the HEAD section containing general data elements related to all notices. Use this section
only once in the file.
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
PAGE 32
Section markers (in bold),
data items and example values
in recommended format
Art. 4
Art. 5
t_trg_freq_assgn = 0.54
+
+
Permissible value(s)
Numeric, with 3
decimals, 5 characters
Comments
For region 1:
The assigned frequency (MHz, from 0.153 to 0.279 and from 0.531 to 1.602 in 0.009 increments) of the
target notice or assignment to be withdrawn or suppressed in the GE75 Plan or MIFR.
For region 2:
The assigned frequency (MHz, from 0.53 to 1.70 in 0.01 increments) of the target notice or assignment
to be withdrawn or suppressed in the RJ81 Plan or MIFR. Values below 0.54 and above 1.60ares
allowed if t_fragment= NTFD_RR (see Art.5 of RR: Table of Frequency Allocation for Region 2).
For region 3:
The assigned frequency (MHz, from 0.531 to 1.602 in 0.009 increments) of the target notice or
assignment to be withdrawn or suppressed in the GE75 Plan or MIFR.
Mandatory if t_trg_adm_ref_id is not provided.
t_trg_long = -0614604
+
+
+DDDMMSS
The longitude of the transmitting antenna site of the target notice or assignment to be withdrawn or
suppressed in the Plan or MIFR. Mandatory if t_trg_adm_ref_id is not provided.
Sign + (plus) for East Longitude, sign – (minus) for West Longitude and leading zeros in DDD
(degrees) MM (minutes) and SS (seconds) are mandatory .
t_trg_lat = +120120
+
+
+DDMMSS
The latitude of the transmitting antenna site of the target notice or assignment to be withdrawn or
suppressed in the Plan or MIFR. Mandatory if t_trg_adm_ref_id is not provided.
Sign + (plus) for North Latitude, sign – (minus) for South Latitude and leading zeros in DD (degrees)
MM (minutes) and SS (seconds) are mandatory .
t_trg_adm_ref_id =
PLANADMREFID1
+
+
Up to 20 characters
The unique identification code (given by the administration) of the target notice or assignment to be
withdrawn or suppressed in the Plan or MIFR. Mandatory if t_trg_freq_assgn and t_trg_long and
t_trg_lat are not provided.
.
t_remarks = Test notice only
O
O
Up to 80 characters
Any comment intended to assist the BR in processing the notice.
</NOTICE>
X
X
End of NOTICE section.
<TAIL>
X
X
Beginning of TAIL section indicating the total number of notices in the notification file.
t_num_notices =1
X
X
</TAIL>
X
X
Integer
GUIDELINES GE75 AND RJ81 – VERSION 1.1 RELEASED 31 MARCH 2014
The number of notices contained in the file.
End of TAIL section. End of the notification file.
PAGE 33