------------------------------------------------ ----------------------------------------------------
  **World Radiocommunication Conference (WRC‑07)\  ![](media/image1.png){width="1.9270833333333333in"
  Geneva, 22 October - 16 November 2007**          height="0.8125in"}

                                                   

                                                   

  **PLENARY MEETING**                              **Addendum 2 to Document 14-E**

                                                   **28 September 2007**

                                                   **Original: English**

  CITEL Administrations                            

  inter-american proposals for the work of the     
  conference                                       

                                                   
  ------------------------------------------------ ----------------------------------------------------

TABLE OF CONTENTS

Page

[Agenda item 1.2 2](#agenda-item-1.2)

[Agenda item 1.4 6](#agenda-item-1.4)

[Agenda item 1.5 16](#agenda-item-1.5)

[Agenda item 1.6 25](#agenda-item-1.6)

[Agenda item 1.8 37](#agenda-item-1.8)

[Agenda item 1.9 47](#agenda-item-1.9)

[Agenda item 1.10 51](#agenda-item-1.10)

[Agenda item 1.12 88](#__RefHeading___Toc177410985)

[Agenda item 1.13 114](#agenda-item-1.13)

[Agenda item 1.14 120](#agenda-item-1.14)

[Agenda item 1.16 174](#agenda-item-1.16)

[Agenda item 1.18 178](#agenda-item-1.18)

[Agenda item 2 181](#agenda-item-2)

[Agenda item 4 192](#agenda-item-4)

[Agenda item 7.1 193](#agenda-item-7.1)

[Agenda item 7.2 197](#agenda-item-7.2)

#### Agenda item 1.2

1.2 to consider allocations and regulatory issues related to the Earth
exploration-satellite (passive) service, space research (passive)
service and the meteorological satellite service in accordance with
Resolutions **746** **(WRC‑03)** and **742** **(WRC‑03)**

Proposals for Agenda item 1.2

Resolution 746: Use of the frequency band 18-18.4 GHz

Background information

"resolves

1 to invite ITU‑R to conduct sharing analyses between geostationary
meteorological satellites operating in the space-to-Earth direction and
the fixed, fixed-satellite and mobile services in the band 18-18.4 GHz
to define appropriate sharing criteria with a view to extending the
current 18.1-18.3 GHz geostationary meteorological satellites allocation
in the space-to-Earth direction to 300 MHz of contiguous spectrum;"

This proposal addresses resolves 1 of Resolution 746 (WRC‑03), "to
invite ITU‑R to conduct sharing analyses between geostationary
meteorological satellites operating in the space-to-Earth direction and
the fixed, fixed-satellite and mobile services in the band 18.0-18.4 GHz
to define appropriate sharing criteria with a view to extending the
current 18.1-18.3 GHz geostationary meteorological satellite allocation
in the space-to-Earth direction to 300 MHz of contiguous spectrum;".
Presently the meteorological-satellite (MetSat) service
(space-to-Earth), limited to the geostationary-satellite orbit (GSO), is
allocated by footnote 5.519 in the band 18.1-18.3 GHz. The band is
allocated on a primary basis to the fixed-satellite service (FSS), the
fixed service and the mobile service in all three Regions and these
allocations also exist for these same services in the band 17.8-18.1 GHz
in all Regions. In both bands, the FSS is allocated in both the
space-to-Earth and Earth-to-space directions. Additionally, in the
18.1-18.4 GHz band, the FSS (space-to-Earth) allocation has associated
with it Nos. 5.484A and 5.516B. The first provision applies to
non-geostationary FSS satellite systems. The latter provision states
that the band 18.3-19.3 GHz has been identified for use by high-density
applications in the FSS in Region 2.

The design of the next generation GSO meteorological satellites has been
optimized to maximize the level of homogeneity between FSS and MetSat
systems. It is envisioned that this would maximize compatibility and
facilitate coordination under No. 9.7 for operation of both types of
systems in the space-to-Earth direction.

Sharing between fixed service point-to-point systems and MetSat earth
stations under line-of-sight conditions is feasible with an angular
off-pointing of typically around 2-2.5° and a separation distance of
typically 4-9 km. For point-to-multipoint systems (outstations), sharing
is possible with no or very little angular off-pointing. Values may
range between 0° and 0.9° and a separation distance of typically 4 to
7 km is required. Point-to-multipoint central stations do not require
off-pointing. Given the small number of geostationary MetSat systems and
their corresponding earth stations (approximately five per Region)
careful selection of the location of meteorological earth stations
should facilitate coordination with fixed service stations. To
facilitate coordination with the fixed service, Table 8d of Appendix 7
would have to be amended in order to provide the required parameters for
the determination of coordination distance for a receiving MetSat earth
station in the 18.0-18.3 GHz band.

In accordance with No. 5.516 the band 18.0-18.1 GHz in the
Earth-to-space direction is used for feeder links for the
broadcasting-satellite service. Compatibility studies have been
performed to estimate the typical required separation distances in
reverse band sharing situations between receiving MetSat earth stations
and transmitting BSS feeder uplink stations. In the worst case, it has
been determined that around 40 km separation is required. Therefore it
is expected that with some care in situating the limited number of
MetSat receive stations international coordination would rarely be
required under No. 9.17A.

While the expected design of the GSO MetSat satellite networks
envisioned for operation in the 300 MHz wide band appears to be
generally compatible with FSS systems being implemented, it would appear
that, for Region 2, operating MetSat systems below 18.3 GHz would avoid
several potential difficulties. Given the desire to have a common MetSat
allocation in all three Regions, it is proposed to expand the additional
allocation in No. 5.519 from 18.1-18.3 GHz to 18.0-18.3 GHz, including
the limitation to geostationary satellites and the requirement to meet
the current applicable power flux-density limits as given in RR Table
21-4 for the MetSat service in the band 18.1-18.3 GHz in the new 100 MHz
extension.

In addition, ITU‑R studies have shown that, in conjunction with
extending the MetSat allocation, extending the existing FSS coordination
arc principle in this band to the case of MetSat systems coordinating
with FSS networks has the potential to reduce the workload of the Bureau
in identifying affected administrations and fulfils the purposes
envisioned by Resolution 901 (WRC‑03). As such, a consequential
modification to Table 5-1 of Appendix 5 to include this change is also
proposed. It is noted that as with the current No. 9.7, an
administration may request, pursuant to No. 9.41, to be included in
requests for coor­dination involving the MetSat or FSS service in this
band, indicating the networks for which the value of *T*/*T* calculated
by the method in § 2.2.1.2 and 3.2 of Appendix 8 exceeds 6%.

ARTICLE 9

Procedure for effecting coordination with or\
            obtaining agreement of other
administrations**^1,\ 2,\ 3,\ 4,\ 5,\ 6,\ 7,\ 8^**     (WRC-03)

**MOD** IAP/14A2/1

**9.41** Following receipt of the BR IFIC referring to requests for
coordination under Nos. **9.7** to **9.7B**, an administration believing
that it should have been included in the request or the initiating
administration believing that an administration identified under No.
**9.36** in accor­dance with the provisions of No. **9.7** (GSO/GSO)
(items 1), 2), 3), 4), 5) and 6) of the frequency band column),
No. **9.7A** (GSO earth station/non‑GSO system) or No. **9.7B** (non-GSO
system/GSO earth station) of Table 5-1 of Appendix **5** should not have
been included in the request, shall, within four months of the date of
publication of the relevant BR IFIC, inform the initiating
administration or the identified administration, as appropriate, and the
Bureau, giving its technical reasons for doing so, and shall request
that its name be included or that the name of the identified
administration be excluded, as appropriate.     (WRC‑07)

**Reasons:** Consequential modification to Table 5-1 of Appendix 5.

APPENDIX 7 (Rev.WRC-03)

Methods for the determination of the coordination area around an earth
station in frequency bands between 100 MHz and 105 GHz

ANNEX 7

System parameters and predetermined coordination distances for\
determination of the coordination area around an earth station

**MOD** IAP/14A2/2

TABLE 8d

Parameters required for the determination of coordination distance for a
receiving earth station

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 1%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 6%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><strong>Receiving space<br />
radiocommunication<br />
service designation</strong></td>
<td><strong>Meteoro­logical- satellite</strong></td>
<td><strong>Fixed-satellite<br />
</strong></td>
<td><strong>Fixed-satellite 3</strong></td>
<td><strong>Broad­casting-<br />
satellite</strong></td>
<td><strong>Earth exploration-<br />
satellite 4</strong></td>
<td><strong>Earth exploration-<br />
satellite 5</strong></td>
<td><strong>Space research<br />
(deep space)</strong></td>
<td colspan="2"><strong>Space research</strong></td>
<td><strong>Fixed-<br />
satellite 6</strong></td>
<td><strong>Fixed-<br />
satellite 5</strong></td>
<td><strong>Mobile-satellite</strong></td>
<td><strong>Broadcasting-satellite,<br />
fixed-satellite</strong></td>
<td><strong>Mobile-satellite</strong></td>
<td><strong>Radio-navigation</strong></td>
<td><strong>Broadcasting-satellite<br />
</strong></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>Unman­ned</td>
<td>Manned</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3"><blockquote>
<p>Frequency bands (GHz)</p>
</blockquote></td>
<td>18.0-18.3</td>
<td><blockquote>
<p>18.8-19.3</p>
</blockquote></td>
<td><blockquote>
<p>19.3-19.7</p>
</blockquote></td>
<td><blockquote>
<p>21.4-22.0</p>
</blockquote></td>
<td><blockquote>
<p>25.5-27.0</p>
</blockquote></td>
<td><blockquote>
<p>25.5-27.0</p>
</blockquote></td>
<td><blockquote>
<p>31.8-32.3</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>37.0-38.0</p>
</blockquote></td>
<td><blockquote>
<p>37.5-40.5</p>
</blockquote></td>
<td><blockquote>
<p>37.5-40.5</p>
</blockquote></td>
<td><blockquote>
<p>39.5-40.5</p>
</blockquote></td>
<td><blockquote>
<p>40.5-42.5</p>
</blockquote></td>
<td>43.5-47.0</td>
<td><blockquote>
<p>43.5-47.0</p>
</blockquote></td>
<td><blockquote>
<p>84-86</p>
</blockquote></td>
</tr>
<tr class="even">
<td colspan="3"><blockquote>
<p>Transmitting terrestrial<br />
service designations</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed,<br />
radio-<br />
navigation</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile</p>
</blockquote></td>
<td><blockquote>
<p>Broadcasting,<br />
fixed</p>
</blockquote></td>
<td><blockquote>
<p>Mobile</p>
</blockquote></td>
<td><blockquote>
<p>Mobile</p>
</blockquote></td>
<td><blockquote>
<p>Fixed, mobile,<br />
broadcasting</p>
</blockquote></td>
</tr>
<tr class="odd">
<td colspan="3"><blockquote>
<p>Method to be used</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.1</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.1, § 2.2</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.2</p>
</blockquote></td>
<td><blockquote>
<p>§ 1.4.5</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.2</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.1</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.1, § 2.2</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>§ 2.1, § 2.2</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.2</p>
</blockquote></td>
<td><blockquote>
<p>§ 2.1</p>
</blockquote></td>
<td><blockquote>
<p>§ 1.4.6</p>
</blockquote></td>
<td><blockquote>
<p>§ 1.4.5, § 2.1</p>
</blockquote></td>
<td><blockquote>
<p>§ 1.4.6</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>§ 1.4.5</p>
</blockquote></td>
</tr>
<tr class="even">
<td colspan="3"><blockquote>
<p>Modulation at earth station 1</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>N</p>
</blockquote></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td rowspan="6"><blockquote>
<p>Earth station<br />
interference<br />
parameters<br />
and criteria</p>
</blockquote></td>
<td><blockquote>
<p><em>p</em>0 (%)</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>(0.05)</p>
</blockquote></td>
<td><blockquote>
<p>0.003</p>
</blockquote></td>
<td><blockquote>
<p>0.01</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0.25</p>
</blockquote></td>
<td><blockquote>
<p>0.25</p>
</blockquote></td>
<td><blockquote>
<p>0.001</p>
</blockquote></td>
<td><blockquote>
<p>0.1</p>
</blockquote></td>
<td><blockquote>
<p>0.001</p>
</blockquote></td>
<td><blockquote>
<p>0.02</p>
</blockquote></td>
<td><blockquote>
<p>0.003</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p><em>n</em></p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>2</p>
</blockquote></td>
<td><blockquote>
<p>2</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>2</p>
</blockquote></td>
<td><blockquote>
<p>2</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>2</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><blockquote>
<p><em>p</em> (%)</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0.025</p>
</blockquote></td>
<td><blockquote>
<p>0.0015</p>
</blockquote></td>
<td><blockquote>
<p>0.01</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0.125</p>
</blockquote></td>
<td><blockquote>
<p>0.125</p>
</blockquote></td>
<td><blockquote>
<p>0.001</p>
</blockquote></td>
<td><blockquote>
<p>0.1</p>
</blockquote></td>
<td><blockquote>
<p>0.001</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0.0015</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p><em>NL</em> (dB)</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><blockquote>
<p><em>Ms</em> (dB)</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>18.8</p>
</blockquote></td>
<td><blockquote>
<p>5</p>
</blockquote></td>
<td><blockquote>
<p>5</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>11.4</p>
</blockquote></td>
<td><blockquote>
<p>14</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>1</p>
</blockquote></td>
<td><blockquote>
<p>6.8</p>
</blockquote></td>
<td><blockquote>
<p>6</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p><em>W</em> (dB)</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td><blockquote>
<p>0</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td rowspan="5"><blockquote>
<p>Terrestrial station parameters</p>
</blockquote></td>
<td rowspan="2"><blockquote>
<p><em>E</em> (dBW)<br />
in <em>B</em> 2</p>
</blockquote></td>
<td><blockquote>
<p>A</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>40</p>
</blockquote></td>
<td><blockquote>
<p>40</p>
</blockquote></td>
<td><blockquote>
<p>40</p>
</blockquote></td>
<td><blockquote>
<p>40</p>
</blockquote></td>
<td><blockquote>
<p>42</p>
</blockquote></td>
<td><blockquote>
<p>42</p>
</blockquote></td>
<td><blockquote>
<p>–28</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>–28</p>
</blockquote></td>
<td><blockquote>
<p>35</p>
</blockquote></td>
<td><blockquote>
<p>35</p>
</blockquote></td>
<td><blockquote>
<p>35</p>
</blockquote></td>
<td><blockquote>
<p>44</p>
</blockquote></td>
<td><blockquote>
<p>40</p>
</blockquote></td>
<td><blockquote>
<p>40</p>
</blockquote></td>
<td></td>
</tr>
<tr class="odd">
<td rowspan="2"><blockquote>
<p><em>Pt</em> (dBW) in <em>B</em></p>
</blockquote></td>
<td><blockquote>
<p>A</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td><blockquote>
<p>–</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p>N</p>
</blockquote></td>
<td><blockquote>
<p>–7</p>
</blockquote></td>
<td><blockquote>
<p>–7</p>
</blockquote></td>
<td><blockquote>
<p>–7</p>
</blockquote></td>
<td><blockquote>
<p>–7</p>
</blockquote></td>
<td><blockquote>
<p>–3</p>
</blockquote></td>
<td><blockquote>
<p>–3</p>
</blockquote></td>
<td><blockquote>
<p>–81</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>–73</p>
</blockquote></td>
<td><blockquote>
<p>–10</p>
</blockquote></td>
<td><blockquote>
<p>–10</p>
</blockquote></td>
<td><blockquote>
<p>–10</p>
</blockquote></td>
<td><blockquote>
<p>–1</p>
</blockquote></td>
<td><blockquote>
<p>–7</p>
</blockquote></td>
<td><blockquote>
<p>–7</p>
</blockquote></td>
<td></td>
</tr>
<tr class="odd">
<td><blockquote>
<p><em>Gx</em> (dBi)</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>47</p>
</blockquote></td>
<td><blockquote>
<p>47</p>
</blockquote></td>
<td><blockquote>
<p>47</p>
</blockquote></td>
<td><blockquote>
<p>47</p>
</blockquote></td>
<td><blockquote>
<p>45</p>
</blockquote></td>
<td><blockquote>
<p>45</p>
</blockquote></td>
<td><blockquote>
<p>53</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>45</p>
</blockquote></td>
<td><blockquote>
<p>45</p>
</blockquote></td>
<td><blockquote>
<p>45</p>
</blockquote></td>
<td><blockquote>
<p>45</p>
</blockquote></td>
<td><blockquote>
<p>45</p>
</blockquote></td>
<td><blockquote>
<p>47</p>
</blockquote></td>
<td><blockquote>
<p>47</p>
</blockquote></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p>Reference band-<br />
width 6</p>
</blockquote></td>
<td><blockquote>
<p><em>B</em> (Hz)</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>107</p>
</blockquote></td>
<td><blockquote>
<p>106</p>
</blockquote></td>
<td><blockquote>
<p>106</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>107</p>
</blockquote></td>
<td><blockquote>
<p>107</p>
</blockquote></td>
<td><blockquote>
<p>1</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>1</p>
</blockquote></td>
<td><blockquote>
<p>106</p>
</blockquote></td>
<td><blockquote>
<p>106</p>
</blockquote></td>
<td><blockquote>
<p>106</p>
</blockquote></td>
<td><blockquote>
<p>106</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><blockquote>
<p>Permissible interference power</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p><em>Pr</em>( <em>p</em>) (dBW)<br />
in <em>B</em></p>
</blockquote></td>
<td><blockquote>
<p>−115</p>
</blockquote></td>
<td><blockquote>
<p>–140</p>
</blockquote></td>
<td><blockquote>
<p>–137</p>
</blockquote></td>
<td></td>
<td><blockquote>
<p>–120</p>
</blockquote></td>
<td><blockquote>
<p>–116</p>
</blockquote></td>
<td><blockquote>
<p>–216</p>
</blockquote></td>
<td colspan="2"><blockquote>
<p>–217</p>
</blockquote></td>
<td><blockquote>
<p>–140</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="19"><p>1 A: analogue modulation; N: digital modulation.</p>
<p>2 <em>E</em> is defined as the equivalent isotropically radiated
power of the interfering terrestrial station in the reference
bandwidth.</p>
<p>3 Non-geostationary mobile-satellite service feeder links.</p>
<p>4 Non-geostationary-satellite systems.</p>
<p>5 Geostationary-satellite systems.</p>
<p>6 Non-geostationary fixed-satellite service systems.</p></td>
</tr>
</tbody>
</table>

**Reasons:** Parameters are required for coordination between
terrestrial and the meteorological-satellite services near 18 GHz. Since
this band is not allocated to the non-geostationary
meteorological-satellite service, reference to § 2.2 (dealing with
non-GSO systems) is not required.

#### Agenda item 1.4 

1.4 to consider frequency-related matters for the future development of
IMT‑2000 and systems beyond IMT‑2000 taking into account the results of
ITU‑R studies in accordance with Resolution **228 (Rev.WRC‑03)**

Proposals for Agenda item 1.4

Background information

WARC-92 identified the 1 885-2 025 MHz and 2 110-2 200 MHz bands
(230 megahertz of spectrum) allocated to the mobile service for possible
use on a worldwide basis by administrations wishing to implement
IMT-2000 systems in footnote 5.388. Additionally, WRC‑2000 identified
the 806-960 MHz band in footnote 5.317A and the 1 710-1 885 MHz and
2 500-2 690 MHz bands in footnote 5.384A for possible IMT-2000 use. Each
administration would decide which portions of the identified bands to
use for IMT-2000.

In Resolution 228 (WRC‑2000), WRC‑2000 invited the ITU-R to continue
studies on the overall objectives, applications and technical and
operational implementation of IMT systems. At WRC‑03, Resolution 228
(Rev.WRC‑03) was modified to ask the ITU‑R to report, in time for
WRC‑07, on the results of studies on the spectrum requirements and
potential frequency ranges suitable for IMT systems, taking into
account:

-- the evolving user needs, including the growth in demand for IMT-2000
services;

-- the evolution of IMT-2000 and pre IMT-2000 systems through advances
in technology;

-- the bands currently identified for IMT-2000;

-- the time-frame in which spectrum would be needed;

-- the period for migration from existing to future systems;

-- the extensive use of frequencies below those identified for IMT-2000
in No. 5.317A;

And to conduct studies that consider:

-- the regulatory and technical issues associated with the use of
frequencies below those currently identified, including an assessment of
their advantages and disadvantages;

-- the needs of developing countries, including the use of the satellite
component of IMT-2000, for suitable coverage in these countries;

-- the results of sharing and compatibility studies with services to
which the potential bands are already allocated.

The need for the studies was driven by the perception that there may be
a need for new spectrum to accommodate:

-- the increasing demand for mobile services,

-- the development of higher bandwidth technologies, and

-- the potential to use mobile services to meet universal service
requirements

ITU‑R WP 8F completed a report on service types and their spectrum
requirements, and a report that evaluates suitable frequency ranges
including in what time-frame such spectrum would be needed. WP 8F
finalized the spectrum calculation methodology for IMT systems and used
this to calculate spectrum estimates for IMT. The results of studies are
documented in the CPM Report, while other Reports and Recommendations
will be ready before WRC‑07.

WP 8F decided on a new name for Systems Beyond IMT-2000, IMT-Advanced,
at their October 2005 meeting. It was also agreed that "IMT" would be
the root name and would encompass both IMT-2000 and IMT-Advanced
systems. The term IMT is recognized outside of the ITU, is simple, and
represents the services provided to users.

When considering the naming of IMT systems, one must also consider the
Radio Regulations and regulatory clarity. Generally, the Radio
Regulations (RR) allocate frequencies to services (e.g. mobile, fixed,
etc.) and these are, in some cases, further identified for certain
applications. Systems that meet the regulatory criteria in the frequency
band should not be limited in their evolution and there is no precedence
for limiting an allocation in the RR to a specific technology or
generation of technology. IMT-2000 is a set of technologies (as
described in Recommendation ITU‑R M.1457), a specific generation of IMT,
which represents a unique situation in the RR.

The CPM text for Agenda item 1.4 was completed at the 20th meeting of WP
8F and includes three methods to satisfy the agenda item. These are
concepts that may be applied to all or some of the candidate frequency
bands or a part of these bands. The Methods describe how footnotes would
reflect which IMT system(s) a specific frequency range is being
identified for.

Deploying cellular infrastructure is costly and time-consuming therefore
being able to reuse existing infrastructure to expand the services
offered to users is essential. Advances in radio technology are allowing
operators to increase their capacity without increasing their spectrum
usage. As IMT-Advanced systems are being deployed it is important to
allow operators to expand or evolve their existing systems to offer
IMT-Advanced services within the bands that they are using for IMT-2000
wherever it is feasible.

The 2 700-2 900 MHz band is a major band for radiodetermination
services, either radionavigation or radiolocation (see No. 5.423) and is
currently heavily used for civil aviation and meteorological purposes,
all relating to safety of life and property.

Airport surveillance radars that operate in this band are crucial to the
safe and efficient operation of air travel worldwide. For many
administrations that currently may not use the band or use the band
lightly, loss of spectrum will also limit implementation of additional
airport surveillance radars and meteorological radars as the
requirements for deployment of additional systems continue to grow.

The 2 700-2 900 MHz band is also used by civil aviation radars for
medium range detection. Furthermore, in some administrations primary
radars, which were previously using the 1 215-1 300 MHz band, are now
progressively migrating into the 2 700-2 900 MHz band.

For some administrations, this band is used for civil aviation systems
(aeronautical radionavigation) integrating radiolocation and
radionavigation in the same infrastructure. Operating experience shows
that any non-radar emissions in this band would significantly interfere
with existing systems and would seriously jeopardize the safety of life,
operations of civil aviation and radiolocation services. Moreover, the
high power necessary for civil aviation radionavigation radar systems,
makes the sharing of the band with IMT very difficult. ITU‑R WP 8B
studies prior to WRC‑03, and more recently in preparation for WRC‑07,
have concluded that sharing of IMT with radionavigation and
radiolocation in the band 2 700-2 900 MHz is clearly not feasible.

In all three ITU‑R Regions, the 2 700-2 900 MHz band is allocated to
aeronautical radionavigation. The radionavigation service is designated
as a safety service under RR No. 4.10 and harmful interference to it
cannot be accepted. By RR No. 5.423, ground-based meteorological radars
are authorized to operate on an equal primary basis. Previous detailed
analysis and sharing studies undertaken by various ITU administrations
and ongoing within the ITU‑R working parties have shown that the
utilization of the 2 700-2 900 MHz band by IMT systems is not feasible.

It is expected that within the next decade most countries will
transition to digital broadcasting. As a result of this transition,
additional spectrum will become available for implementation of advanced
wireless applications e.g. IMT. When analogue transmissions are
terminated at the end of the transition period, it will be possible for
all of the existing TV stations to operate in much smaller blocks of
spectrum, thereby allowing a portion of spectrum to be recovered for
other uses. If identified adequately in advance, it is possible to
define contiguous blocks of spectrum.

Accordingly, CITEL plans to take advantage of the conversion of analogue
to digital television by proposing part of the broadcast band as a
candidate band for IMT, particularly 698-806/862 MHz. This proposed
identification would indicate that this band is intended for use, on a
worldwide basis, by administrations wishing to implement IMT, but that
this does not preclude the use by any application of services to which
the band is also allocated.

In the consideration of potential candidate bands, it was noted that the
470-806/862 MHz band is currently used by the broadcast service
(television) and some parts of it are shared with the fixed service and
mobile service on a secondary basis, and on a primary basis in the
countries in footnote 5.293. As well, Resolution 646 (WRC‑03) encourages
administrations to consider the band 746 to 806 MHz for public
protection and disaster relief (PPDR). Canada, the United States and
Mexico recently reached agreements to share the bands 764 to 776 MHz and
794 to 806 MHz for the use of PPDR along the common borders.

It is important for spectrum identifications for advanced communications
applications, like IMT, to be flexible enough to accommodate new
technologies in a timely manner. In this regard, it is important to note
that many CITEL countries continue to fully support the ongoing efforts
at the ITU‑R to include OFDMA TDD WMAN in the IMT-2000 family
(Recommendation ITU‑R M.1457), and are optimistic that these efforts
will be completed prior to WRC‑07. If, however, these efforts are not
complete before the WRC, it will be necessary for some administrations
to revisit this proposal in order to ensure that broadband wireless
access systems are explicitly included in the IMT identifications.

The objective of identifying spectrum for use by IMT is to encourage
global harmonization and to provide guidance to manufacturers so that
they may develop equipment for global roaming at a minimum cost. In
order to maximize the benefit of this newly available spectrum it is
important to establish an international regulatory framework that would
allow adequate time for national regulators, manufacturers and operators
to prepare for the introduction of new services. In light of that, the
timing of WRC‑07 is highly advantageous, as it provides an opportunity
to identify the spectrum in the broadcasting bands that would facilitate
eventual transition to other applications such as advanced wireless
technologies.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/3

410-460 MHz

**MOD** IAP/14A2/3A

**460-890 MHz**

+----------------------+----------------------+-----------------------+
| **Allocation to      |                      |                       |
| services**           |                      |                       |
+----------------------+----------------------+-----------------------+
| **Region 1**         | **Region 2**         | **Region 3**          |
+----------------------+----------------------+-----------------------+
| > **460-470** FIXED  |                      |                       |
| >                    |                      |                       |
| > MOBILE             |                      |                       |
| >                    |                      |                       |
| > Mete               |                      |                       |
| orological-Satellite |                      |                       |
| > (space-to-Earth)   |                      |                       |
|                      |                      |                       |
| 5.287 5.288 5.289    |                      |                       |
| 5.290 ADD 5.XXX      |                      |                       |
+----------------------+----------------------+-----------------------+

**ADD** IAP/14A2/4

**5.XXX** The 450-470 MHz band has been identified for use by
administrations wishing to implement International Mobile
Telecommunications (IMT) that ITU‑R has approved. This identification
does not preclude the use of these bands by any application of the
services to which they are allocated and does not establish priority in
the Radio Regulations.

**Reasons:** To identify the 450-470 MHz band for use by administrations
wishing to implement IMT systems and to provide a guideline for the use
of the said band.

**[NOC]{.underline}** IAP/14A2/5

2 700-4 800 MHz

+----------------------+----------------------+-----------------------+
| > Allocation to      |                      |                       |
| > services           |                      |                       |
+----------------------+----------------------+-----------------------+
| > Region 1           | > Region 2           | > Region 3            |
+----------------------+----------------------+-----------------------+
| **4 400-4 500**      |                      |                       |
| FIXED                |                      |                       |
|                      |                      |                       |
| MOBILE               |                      |                       |
+----------------------+----------------------+-----------------------+
| **4 500-4 800**      |                      |                       |
| FIXED                |                      |                       |
|                      |                      |                       |
| FIXED-SATELLITE      |                      |                       |
| (space-to-Earth)     |                      |                       |
| 5.441                |                      |                       |
|                      |                      |                       |
| MOBILE               |                      |                       |
+----------------------+----------------------+-----------------------+

**[NOC]{.underline}** IAP/14A2/5A

4 800-5 570 MHz

**Reasons:** Studies have not shown the compatibility of IMT with the
radio relay and troposcatter networks operating within the fixed and
mobile services in the 4 400-4 940 MHz band. Further, the
4 940-4 990 MHz band is used for critical public protection and disaster
relief applications. This [NOC]{.underline} proposal applies to Agenda
item 1.4 and the identification of spectrum for IMT. The 4 400-4 940 MHz
band is being considered for aeronautical mobile telemetry for flight
test (air-to-ground) under Agenda item 1.5. In addition, this band is
heavily used for fixed point-to-point systems to establish long-distance
links; also, portions of this band are planned to be used for government
public protection and disaster relief applications.

**MOD** IAP/14A2/6

460-890 MHz

+----------------------+----------------------+-----------------------+
| Allocation to        |                      |                       |
| services             |                      |                       |
+----------------------+----------------------+-----------------------+
| Region 1             | Region 2             | Region 3              |
+----------------------+----------------------+-----------------------+
| > **470-698**        | > **470-512**        | > **470-585**         |
| >                    | >                    | >                     |
| > BROADCASTING       | > BROADCASTING       | > FIXED               |
| >                    | >                    | >                     |
| > 5.149 5.291A 5.294 | > Fixed              | > MOBILE              |
| > 5.296\             | >                    | >                     |
| > 5.300 5.302 5.304  | > Mobile             | > BROADCASTING        |
| > 5.306\             | >                    | >                     |
| > 5.311 5.312        | > 5.292 5.293        | > 5.291 5.298         |
|                      | >                    | >                     |
|                      | > **512-608**        | > **585-610**         |
|                      | >                    | >                     |
|                      | > BROADCASTING       | > FIXED               |
|                      | >                    | >                     |
|                      | > 5.297              | > MOBILE              |
|                      | >                    | >                     |
|                      | > **608-614**        | > BROADCASTING        |
|                      | >                    | >                     |
|                      | > RADIO ASTRONOMY    | > RADIONAVIGATION     |
|                      | >                    | >                     |
|                      | > Mobile-satellite   | > 5.149 5.305 5.306   |
|                      | > except\            | > 5.307               |
|                      | > aeronautical       | >                     |
|                      | > mobile-satellite\  | > **610-698**         |
|                      | > (Earth-to-space)   | >                     |
|                      | >                    | > FIXED               |
|                      | > **614-698**        | >                     |
|                      | >                    | > MOBILE              |
|                      | > BROADCASTING       | >                     |
|                      | >                    | > BROADCASTING        |
|                      | > Fixed              | >                     |
|                      | >                    | > 5.149 5.305 5.306   |
|                      | > Mobile             | > 5.307\              |
|                      | >                    | > 5.311               |
|                      | > 5.293 5.309 5.311  |                       |
+----------------------+----------------------+-----------------------+
| > **698-790**        | > **698-806**        | > **698-806**         |
| >                    | >                    | >                     |
| > BROADCASTING       | > BROADCASTING       | > FIXED               |
| >                    | >                    | >                     |
| > MOBILE MOD 5.317A  | > Fixed              | > MOBILE MOD 5.317A   |
| >                    | >                    | >                     |
| > 5.296 5.300 5.311  | > MOBILE MOD 5.317A  | > BROADCASTING        |
| > 5.312              | >                    | >                     |
|                      | > 5.293 5.309 5.311  | > 5.311 5.320         |
+----------------------+----------------------+-----------------------+
| > **790-806**        |                      |                       |
| >                    |                      |                       |
| > FIXED              |                      |                       |
| >                    |                      |                       |
| > BROADCASTING       |                      |                       |
| >                    |                      |                       |
| > MOBILE MOD 5.317A  |                      |                       |
| >                    |                      |                       |
| > 5.312 5.314 5.315  |                      |                       |
| > 5.316              |                      |                       |
+----------------------+----------------------+-----------------------+
| > **806-862**        | > **806-890**        | > **806-890**         |
| >                    | >                    | >                     |
| > FIXED              | > FIXED              | > FIXED               |
| >                    | >                    | >                     |
| > BROADCASTING       | > MOBILE MOD 5.317A  | > MOBILE MOD 5.317A   |
| >                    | >                    | >                     |
| > 5.312 5.314 5.315  | > BROADCASTING       | > BROADCASTING        |
| > 5.316 5.319 5.321  |                      |                       |
+----------------------+----------------------+-----------------------+
| > **862-890**        |                      |                       |
| >                    |                      |                       |
| > FIXED              |                      |                       |
| >                    |                      |                       |
| > MOBILE except      |                      |                       |
| > aeronautical\      |                      |                       |
| > mobile MOD 5.317A  |                      |                       |
| >                    |                      |                       |
| > BROADCASTING 5.322 |                      |                       |
+----------------------+----------------------+-----------------------+
| > 5.319 5.323        | > 5.317 5.318        | > 5.320               |
+----------------------+----------------------+-----------------------+

**Reasons:** The frequency band 698-806/862 MHz should be considered
identified for use by IMT systems, recognizing national flexibility as
to which parts of the band in particular could be identified for IMT
given the importance of incumbent services in the band. This band is
adjacent to the bands already identified for IMT-2000 and this frequency
range has good propagation characteristics which allow for building of
larger cells.

**MOD** IAP/14A2/7

**5.317A** Administrations wishing to implement International Mobile
Telecommunications (IMT) may use those parts of the band 698-960 MHz
which are allocated to the mobile service on a primary basis and are
used or planned to be used for mobile systems (see Resolution **224
(Rev.WRC‑07)**). This identification does not preclude the use of these
bands by any application of the services to which they are allocated and
does not establish priority in the Radio Regulations.     (WRC‑2000)

**Reasons:** The proposed modification to the footnote is to identify
the frequency band 698-806/862 MHz for IMT systems.

**MOD** IAP/14A2/8

RESOLUTION 224 (Rev.WRC-07)

Frequency bands for the terrestrial component of IMT-2000 below 1 GHz

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that parts of the band 806-960 MHz are extensively used in the
three Regions by first- and second-generation mobile systems;

*b)* that, as a result of the transition from analogue to digital
terrestrial television broadcasting, some countries are making the band
698-806 MHz available for applications in the mobile service;

*c)* that some administrations are planning to use part of the band
698-806 MHz for International Mobile Telecommunications (IMT);

*d)* that IMT includes IMT-2000, its future development, and
IMT-Advanced;

*e)* that IMT systems are intended to provide telecommunication services
on a worldwide scale, regardless of location, network or terminal used;

*f)* that there is an urgency in fulfilling fundamental universal access
objectives, and the urgent need for socio-economic progress, especially
in developing countries;

*g)* that many communities are particularly under-served as compared to
urban centres;

*h)* that there is a need, in many developing countries and countries
with large areas of low-population density, for cost-effective
implementation of advanced wireless systems;

*i)* that administrations should take into account the need to protect
the existing and future broadcasting service stations, both analogue and
digital, in the 698-806 MHz band;

*j)* that first- and second-generation mobile systems in the three
Regions operate using various frequency arrangements;

*k)* that where cost considerations warrant the installation of fewer
base stations, such as in sparsely populated areas, bands below 1 GHz
are generally suitable for implementing mobile systems including IMT;

*l)* Recommendation ITU-R M.819 which describes the objectives to be met
by IMT‑2000 to meet the needs of developing countries,

recognizing

*a)* that the evolution of first- and second-generation cellular-based
mobile systems to IMT‑2000 can be facilitated if they are permitted to
use their current frequency bands;

*b)* that the field of mobile wireless telecommunications is
experiencing many rapid improvements in capability, due to technology
advances, and that administrations should be encouraged to facilitate
the deployment of these rapid improvements;

*c)* that the 698-806 MHz band is extensively used in many countries for
broadcasting systems;

*d)* that parts of the bands 746-806 MHz and 806-860 MHz are widely used
by some administrations for point-to-point, point-to-multipoint, trunked
and conventional dispatch systems that include critical applications
such as public protection and disaster relief radiocommunications
(PPDR);

*e)* that Resolution **646 (WRC‑03)** recommends administrations to
consider the use of regionally harmonized frequency bands for PPDR and
encourages administrations to consider the use of the band 746-806 MHz,
among others, in Region 2, and states that some countries in Region 3
have identified the 746-806 MHz band for PPDR applications;

*f)* that although the 698-806 MHz band is used for television
broadcasting in some areas, there are other areas in great need of
communications coverage where this band may be underutilized, in
particular, remote rural communities;

*g)* that spectrum planning is done at the national level, taking into
account the need for interoperability and the benefits of neighbouring
administrations using harmonized frequency bands;

*h)* that there are benefits to spectrum harmonization, including
economies of scale, expanded equipment availability, and enhanced
cross-border coordination;

*i)* that countries, particularly developing countries, have an urgent
need for low-cost communications equipment;

*j)* that the band 698-806 MHz will be heavily used in many
administrations during transition from analogue to digital TV,

emphasizing

*a)* that flexibility must be afforded to administrations:

-- to determine, at a national level, how much spectrum to make
available for IMT from within the identified bands, taking into account
current usages of the spectrum and the need for other applications;

-- to develop their own transition plans, if necessary, tailored to meet
their specific deployment of existing systems;

-- to have the ability for the identified bands to be used by all
services having allocations in those bands;

-- to determine the timing of availability and use of the bands
identified for IMT, in order to meet particular market demand and other
national considerations;

*b)* that the particular needs of developing countries must be met,

resolves

to request administrations which are implementing, or planning to
implement IMT, to consider the use of bands below 1 GHz and the
possibility of evolution of first- and second-generation mobile systems
to IMT, in the frequency band identified in No. **5.317A**, based on
market demand and other national and technical considerations,

invites ITU-R

to study compatibility between mobile systems with different technical
characteristics and provide guidance on any impact on spectrum
arrangements.

**Reasons:** The modification of this Resolution is required because it
is referred by the modified footnote 5.317A. Globally identified
frequency bands will encourage the adoption of IMT by facilitating
global roaming and reducing equipment cost through economies of scale.
There is enough spectrum in this range to support the wide area mobility
capability of IMT while being close to the bands already identified for
IMT-2000, thus facilitating the production of equipment. Given the
favourable propagation characteristics of this band and the associated
coverage advantages, this spectrum is of interest to developing
countries and those with areas of low population density.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**[NOC]{.underline}** IAP/14A2/9

2 700-4 800 MHz

+----------------------+----------------------+-----------------------+
| > Allocation to      |                      |                       |
| > services           |                      |                       |
+----------------------+----------------------+-----------------------+
| > Region 1           | > Region 2           | > Region 3            |
+----------------------+----------------------+-----------------------+
| > **3 400-3 600**    | > **3 400-3 500**    |                       |
| >                    | >                    |                       |
| > FIXED              | > FIXED              |                       |
| >                    | >                    |                       |
| > FIXED-SATELLITE\   | > FIXED-SATELLITE    |                       |
| > (space-to-Earth)   | > (space-to-Earth)   |                       |
| >                    | >                    |                       |
| > Mobile             | > Amateur            |                       |
| >                    | >                    |                       |
| > Radiolocation      | > Mobile             |                       |
| >                    | >                    |                       |
| > 5.431              | > Radiolocation      |                       |
| >                    | > 5.433              |                       |
| > **3 600-4 200**    | >                    |                       |
| >                    | > 5.282 5.432        |                       |
| > FIXED              | >                    |                       |
| >                    | > **3 500-3 700**    |                       |
| > FIXED-SATELLITE\   | >                    |                       |
| > (space-to-Earth)   | > FIXED              |                       |
| >                    | >                    |                       |
| > Mobile             | > FIXED-SATELLITE    |                       |
|                      | > (space-to-Earth)   |                       |
|                      | >                    |                       |
|                      | > MOBILE except      |                       |
|                      | > aeronautical       |                       |
|                      | > mobile             |                       |
|                      | >                    |                       |
|                      | > Radiolocation      |                       |
|                      | > 5.433              |                       |
|                      | >                    |                       |
|                      | > 5.435              |                       |
|                      | >                    |                       |
|                      | > **3 700-4 200**    |                       |
|                      | >                    |                       |
|                      | > FIXED              |                       |
|                      | >                    |                       |
|                      | > FIXED-SATELLITE    |                       |
|                      | > (space-to-Earth)   |                       |
|                      | >                    |                       |
|                      | > MOBILE except      |                       |
|                      | > aeronautical       |                       |
|                      | > mobile             |                       |
+----------------------+----------------------+-----------------------+

**Reasons:** This proposal recommends no change to 3 400-3 600 MHz and
is complementary to the CITEL IAP/14A1/11 which recommends no change for
3 600-4 200 MHz.

#### Agenda item 1.5

1.5 to consider spectrum requirements and possible additional spectrum
allocations for aeronautical telecommand and high bit-rate aeronautical
telemetry, in accordance with Resolution **230 (WRC‑03)**

Proposals for Agenda item 1.5

Background information

This agenda item addresses a growing demand for spectrum allocated for
aeronautical telemetry and associated telecommand. There is a
significant and growing shortfall in spectrum that is necessary to
conduct aeronautical telemetry. The shortfall is exacerbated by the loss
of telemetry spectrum diverted to other than telemetry applications. As
indicated in the responses to Question ITU‑R 231/8, additional spectrum
is necessary due to rapidly increasing data rates associated with the
testing of new and emerging technologies. For example, newer
technologies rely increasingly on high-resolution video for monitoring
aircraft functions or increased use of computer-based aircraft systems.
Without access to additional spectrum, aeronautical development would be
subject to escalating delays and costs, and the growth of the aerospace
industry would be impaired (including equipment manufacturers, civilian
programs and test ranges, and airlines). New worldwide telemetry
spectrum will aid numerous countries and the international aeronautical
community as administrations continue to support their national airlines
and some administrations initiate their own test programs. Existing
international allocations used for aeronautical telemetry will need to
remain available.

Aeronautical mobile telemetry "AMT" is an application within the mobile
service. Depending on the extent to which new AMT spectrum requirements
can be fulfilled using primary mobile service allocations, it is
important that the viability of additional spectrum for AMT be studied.
International recognition of bands suitable for AMT will not only
encourage international harmonization of test equipment, but also
provide assurance to administrations that, based on technical studies
conducted in the ITU‑R, implementation of telemetry systems can be
accomplished by those administrations wishing to do so without
disrupting other services using the bands. This will also enable
manufacturers to offer prospective customers aircraft with common test
equipment packages, and thus help airlines achieve additional economies
in the aircraft life-cycle cost. Moreover, by establishing conditions
under which AMT use of a band would be suitable, incumbent users of the
spectrum can be assured that they will not experience unacceptable
interference, while manufacturers and test ranges will have a measure of
additional certainty for the substantial investment in range
infrastructure that will be incurred in equipping to use new bands
deemed suitable for AMT.

The need for additional spectrum has been studied by several
administrations who indicate that the amount of additional spectrum for
aeronautical flight test telemetry is between 100 MHz and 650 MHz. The
requirement may differ depending on national and regional needs. It is
not necessary to fulfill all AMT requirements in only one band. The new
requirements for aeronautical telemetry are only in the air-to-ground
direction inasmuch as telecommand functions (i.e. ground-to-air
transmissions) can be accommodated in existing bands. In addition, this
new AMT spectrum will not be used for the protection of life and
property. The latter AMT applications will continue to be accommodated
in existing bands (see Nos. 5.342, 5.343, and 5.394 in the Radio
Regulations).

Hence, aeronautical mobile telemetry applications in new spectrum will
not require the level of protection associated with operations in
existing telemetry bands. However, the AMT application may be utilizing
bands, such as the 6 GHz band, that are used for critical applications
such as public

safety communications (including police and fire vehicle dispatch),
coordinating the movement of railroad trains, controlling natural gas
and oil pipelines, regulating the electric grid, and backhauling
wireless telephone traffic.

ITU‑R WP 8B conducted a number of studies of bands that could be used to
satisfy the requirements of aeronautical telemetry applications.
Available technologies, signal fading/propagation considerations, and
the scope of Agenda item 1.5 dictate that the new wideband AMT spectrum
requirements be fulfilled in the 3 GHz to 7 GHz frequency range.
Conversely, technological challenges necessitate at this juncture a
focus on bands below 16 GHz. With the cooperation of other responsible
WPs, several bands were studied for suitability to implement AMT, given
the other co-primary services in the band. Portions of these bands, such
as the 5 925-6 700 MHz band, are used for public safety communications
and other applications that require a high degree of protection. It is
expected that the implementation of telemetry may require avoiding
co-frequency operations with local services in some of the bands. This
will likely mean that the spectrum requirement for AMT would be
satisfied using portions of each of the bands studied and deemed
suitable for AMT implementation. In this context, suitable means that
AMT can be implemented compatibly with other co-primary services
utilizing the band, assuming the implementation is in accordance with
the established sharing criteria.

ITU‑R studies have determined conditions under which aeronautical mobile
telemetry for flight test purposes can be implemented in these bands
without adversely affecting the operation of existing systems and
allocated services. The ability to implement AMT in some areas and in
some portions of the bands may be restricted based on deployment density
of other co-primary service stations, such as the fixed service (FS)
stations, in the same vicinity. In cases where AMT operations could
impact radio astronomy observatories, it may be possible to arrange AMT
time-sharing with those observatories to enable AMT use of the
4 825-4 835 MHz band.

In the past, terms such as "designated" or "identified" have been used
in the Radio Regulations with respect to certain technologies and bands
to encourage technology implementation on a worldwide basis without
making the use by administrations mandatory, and without establishing
any priority of use. Since the spectrum requirements and the conditions
under which AMT will be implemented can vary by administration, an
approach is proposed to simply indicate the suitability of certain bands
for the implementation of AMT based on compatibility studies. This
approach provides valuable information while maximizing the flexibility
of implementing AMT. A finding that spectrum is suitable for AMT
implementation inherently would not establish any priority of use or
preclude use of the bands by other co‑primary services.

Any authorization of AMT operations within these bands would be decided
by individual administrations, and would be specifically limited to
testing of aircraft at designated flight test areas in the air-to-ground
direction within those individual countries. According to No. 5.444 of
the Radio Regulations, the 5 091-5 150 MHz band is to be used by the MLS
(microwave landing system) with precedence given to this international
standard system. However, to date there has been no deployment of MLS in
the band 5 091-5 150 MHz.

The 5 091-5 150 MHz band is already allocated to the aeronautical
radionavigation service (ARNS) on a primary basis in all Regions and is
also allocated to the fixed-satellite service (FSS) (Earth-to-space) on
a primary basis. This FSS allocation is limited to feeder links of
non‑geostationary mobile-satellite systems in the mobile-satellite
service and is subject to coordination under No. 9.11A. Test aircraft
are not intended to use ground-to-air transmissions in this ARNS band.
Administrations are also considering the band 5 091-5 150 MHz under
Agenda item 1.6 for allocation to the aeronautical mobile (R) service
(AM(R)S). Studies have shown that AMT can share with both the FSS and
the proposed AM(R)S system in the band 5 091-5 150 MHz.

In the event the Conference determines that use of the 4 400-4 940 MHz,
5 925-6 700 MHz, and 5 091‑5 150 MHz bands would be suitable for
aeronautical telemetry, coordination with FSS earth stations in
accordance with Article 9 of the ITU Radio Regulations would be
required.

ITU‑R studies have not adequately demonstrated that aeronautical
telemetry or telecommand applications could share spectrum with other
uses in the band 5 150 MHz-5 250 MHz.

Changes to Article 1 definitions of aeronautical telemetry and
aeronautical telecommand are unnecessary. This is not only the least
restrictive of the options for implementing aeronautical mobile
telemetry, but has a long and successful history in the ITU. The effort
to secure Article 1 definitions would impose substantial burdens on the
Special Committee for Regulatory and Procedural Matters and ITU staff,
as well as complicate the work of the WRC. There are also less formal
approaches to exploring the meaning of these terms as an alternative to
adopting formal definitions under Article 1 of the Radio Regulations. To
the extent any administration should be of the view that further
clarification regarding the scope of the agenda item would be in order,
such clarification can be provided via text in the WP 8B preliminary
draft new Report.

Remotely piloted aircraft, also referred to as unmanned aerial vehicles
"UAVs", are envisioned by many as fulfilling a variety of civil
applications, and flying in the national airspace of numerous
administrations within the next decade. Vehicles such as these must be
carefully tested before any such operation commences given, the obvious
safety implications associated with these flights. Additional spectrum
designated for aeronautical mobile telemetry pursuant to Agenda item 1.5
may be utilized for the flight testing of such aircraft. Such testing is
expected to occur at designated test centres on a coordinated basis with
incumbent services. Such use does not include command and control of
UAVs in national airspace. Consideration of the spectrum needs of UAVs
operating in national airspace should not be considered under Agenda
item 1.5.

It is noted that, to date, with reference to Resolution 230 (WRC‑03)
*resolves* 2, no current secondary allocations of the mobile service
have been identified for upgrade to primary.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**ADD** IAP/14A2/10

**5.\[444C\]** *Additional allocation:*  The band 5 091-5 150 MHz is
also allocated to the aeronautical mobile service, limited to flight
test telemetry transmissions by aircraft stations. The provisions of
No. **1.83** apply. Any such use does not preclude the use of this band
by other services to which this band is allocated on a co-primary basis
and does not establish priority in the Radio Regulations.
Resolution **\[IAP/14A2/24\] (WRC‑07)** shall apply.

**Reasons:** This allocation is necessary for implementation of AMT in
the band 5 091-5 150 MHz. The footnote will ensure that the allocation
to AMS is limited to air-to-ground flight test telemetry only, while not
precluding the use of the bands by other co‑primary services. Resolution
\[IAP/14A2/11\] (WRC‑07) specifies the sharing conditions in the band.

**ADD** IAP/14A2/11

RESOLUTION \[IAP/14A2/11\] (WRC‑07)

Use of the band 5 091-5 150 MHz by the aeronautical mobile service for
the implementation of aeronautical mobile telemetry applications

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* the allocation of the frequency band 5 030-5 150 MHz to the
aeronautical radionavigation service;

*b)* that the allocation of the 5 091-5 150 MHz band to the
fixed-satellite service (FSS) (Earth-to-space) is limited to feeder
links of non-geostationary satellite (non-GSO) systems in the
mobile-satellite service (MSS);

*c)* that the band 5 000-5 150 MHz is also allocated to the aeronautical
mobile-satellite (R) service on a primary basis, subject to agreement
obtained under No. **9.21**;

*d)* that this Conference has allocated the 5 091-5 150 MHz band to the
aeronautical mobile service (AMS), limited to air-to-ground flight test
telemetry applications,

recognizing

*a)* that spectrum efficiency is enhanced in situations where new
applications can be implemented compatibly in heavily occupied bands;

*b)* that studies have been conducted within the ITU‑R concerning the
sharing and compatibility of aeronautical mobile telemetry (AMT) for
flight testing with other services in the band 5 091-5 150 MHz;

*c)* that precedence is to be given to the microwave landing system
(MLS) in accordance with No. **5.444** in the frequency band
5 030-5 150 MHz,

noting

*a)* that ITU‑R studies describe methods in Report ITU‑R M.\[AMS-FSS\]
for ensuring compatibility and sharing between the AMS and FSS operating
in the band 5 091-5 150 MHz that result in interference from AMT
aircraft stations transmissions to the fixed-satellite service
spacecraft receivers of no more than 1% Δ*T~satellite~*/*T~satellite~*;

*b)* that methods to facilitate sharing between MLS and AMS are
contained in Recommendation ITU‑R \[MLS-AMS\] (Doc. 8/220R1),

resolves

1 that administrations take account that the band 5 091-5 150 MHz has
been allocated to AMS, limited to implementation of aeronautical mobile
telemetry applications for flight test purposes, based on the ITU
studies referred to in *notings a)* and *b)* above;

2 that administrations choosing to implement aeronautical mobile
telemetry for flight test purposes in the band 5 091-5 150 MHz shall
utilize the criteria set forth below:

-- limit transmissions to those from aircraft stations only, see
No. **1.83**;

-- transmissions limited to designated flight test areas, where flight
test areas are airspace designated by administrations for flight test
within their territories;

-- limit the aggregate of any interference from all AMS including AMT
aircraft stations transmissions to the fixed-satellite service
spacecraft receivers to no more than 3% Δ*T~satellite~*/*T~satellite~*;

-- bilaterally coordinate with administrations operating microwave
landing systems and whose territory is located with the distance *D* of
the AMT flight area, where *D* is determined by the following equation:

*D* = 43 + 10^\[127.55\ −\ 20\ log(*f*)\ +\ *E*\]/20^

where:

*D*: distance separation (km) triggering the coordination

*f*: minimum frequency (MHz) used by the AMT system

*E*: peak equivalent isotropically radiated power density (dBW in
150 kHz) of the aircraft transmitter.

**Reasons:** Resolution \[IAP/14A2/11\] (WRC‑07) provides the sharing
conditions to ensure compatibility between the new allocation to the
aeronautical mobile service, limited to flight test telemetry
transmissions by aircraft stations, and the incumbent services in
accordance with footnote 5.444C (proposal 2).

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**NOC** IAP/14A2/12

4 800-5 570 MHz

**Reasons:** The aeronautical telecommand and high bit-rate aeronautical
telemetry is not compatible with the existing services allocated in band
5 150-5 250 MHz.

**ADD** IAP/14A2/13

**5.\[441A\]** Use of the bands 4 400-4 940 MHz and 5 925-6 700 MHz by
aeronautical mobile telemetry (AMT) for flight testing by aircraft
stations (see No. **1.83**) shall be in accordance with
Resolution **\[IAP/14A2/16\] (WRC‑07)**, and such use shall not unduly
constrain the fixed-satellite and fixed services. Any such use does not
preclude the use of these bands by other mobile service applications or
by other services to which these bands are allocated on a co-primary
basis and does not establish priority in the Radio Regulations.

**Reasons:** Except as noted in the proposal below, these bands already
have a primary mobile allocation with no restriction on aeronautical
mobile applications such as telemetry. The footnote accomplishes two
goals: firstly, it refers to a Resolution which sets out criteria for
the deployment of AMT in order not to adversely affect other primary
services and systems in these bands. Secondly the footnote addresses the
spectrum requirements for AMT in bands already allocated to the mobile
service and for which ITU‑R studies have demonstrated compatibility,
i.e. bands which are suitable for this particular application.

**MOD** IAP/14A2/14

**5.442** In the band 4 950-4 990 MHz, the allocation to the mobile
service is restricted to the mobile, except aeronautical mobile,
service. In the band 4 825-4 835 MHz, applications in the aeronautical
mobile service are limited to aeronautical mobile telemetry for flight
testing by aircraft stations. Resolution **\[IAP/14A2/16\] (WRC‑07)**
shall apply.

**Reasons:** This modification to No. 5.442 exempts AMT from the
aeronautical mobile exclusion.

**MOD** IAP/14A2/15

2 700-4 800 MHz

+----------------------+----------------------+-----------------------+
| > Allocation to      |                      |                       |
| > services           |                      |                       |
+----------------------+----------------------+-----------------------+
| > Region 1           | > Region 2           | > Region 3            |
+----------------------+----------------------+-----------------------+
| **4 400-4 500**      |                      |                       |
| FIXED                |                      |                       |
|                      |                      |                       |
| MOBILE ADD           |                      |                       |
| 5.\[441A\]           |                      |                       |
+----------------------+----------------------+-----------------------+
| **4 500-4 800**      |                      |                       |
| FIXED                |                      |                       |
|                      |                      |                       |
| FIXED-SATELLITE      |                      |                       |
| (space-to-Earth)     |                      |                       |
| 5.441                |                      |                       |
|                      |                      |                       |
| MOBILE ADD           |                      |                       |
| 5.\[441A\]           |                      |                       |
+----------------------+----------------------+-----------------------+

**MOD** IAP/14A2/15A

4 800-5 570 MHz

**MOD** IAP/14A2/15B

5 570-7 250 MHz

+----------------------+----------------------+-----------------------+
| Allocation to        |                      |                       |
| services             |                      |                       |
+----------------------+----------------------+-----------------------+
| Region 1             | Region 2             | Region 3              |
+----------------------+----------------------+-----------------------+
| **5 925-6 700**      |                      |                       |
| FIXED                |                      |                       |
|                      |                      |                       |
| FIXED-SATELLITE      |                      |                       |
| (Earth-to-space)     |                      |                       |
| 5.457A 5.457B        |                      |                       |
|                      |                      |                       |
| MOBILE ADD           |                      |                       |
| 5.\[441A\]           |                      |                       |
|                      |                      |                       |
| 5.149 5.440 5.458    |                      |                       |
+----------------------+----------------------+-----------------------+

**Reasons:** The appropriate modifications to the Table of Frequency
Allocations have been made to reflect proposals made.

**ADD** IAP/14A2/16

RESOLUTION \[iap/14A2/16\] (WRC‑07)

Use of the bands 4 400-4 940 MHz and 5 925-6 700 MHz by an aeronautical
mobile telemetry application in the mobile service

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that there is a need to provide global spectrum to the mobile
service for wideband aeronautical telemetry systems;

*b)* that studies have been conducted within ITU‑R concerning the
sharing and compatibility of aeronautical mobile telemetry for flight
testing with other services in the bands 4 400-4 940 and
5 925-6 700 MHz;

*c)* that based on the results of these studies, in the bands
4 400-4 940 MHz and 5 925-6 700 MHz, technical and operational measures
applied to aeronautical mobile telemetry for flight test purposes
facilitate sharing with other services and applications in these bands;

*d)* that spectrum efficiency is enhanced in situations where new
applications can be implemented compatibly in bands that are heavily
occupied;

*e)* that there is extensive deployment of fixed-satellite service earth
stations in the band 5 925-6 425 MHz;

*f)* that there is extensive deployment of fixed service stations in the
bands 4 400-4 940 MHz and 5 925-6 700 MHz;

*g)* that in certain locations, availability of spectrum will be limited
due to its extensive use by the various services while in other
locations, this may not be the case;

*h)* that there are various techniques which can enhance sharing between
co-primary services such as frequency, or geographic separation,

recognizing

*a)* that the bands 4 400-4 500 MHz and 4 800-4 940 MHz are allocated to
the fixed and mobile services on a primary basis;

*b)* that the band 4 500-4 800 MHz is allocated to the fixed,
fixed-satellite (space-to-Earth), and mobile services on a co-primary
basis;

*c)* that the band 4 800-4 990 MHz is allocated to the radio astronomy
service on a secondary basis worldwide and that No. **5.149** applies;

*d)* that the band 4 825-4 835 MHz referred to in *recognizing c)* is
allocated on a primary basis to radio astronomy in Argentina, Australia
and Canada (see No. **5.443**);

*e)* that No. **5.442** applies to aeronautical mobile telemetry for
flight testing operations in the band 4 825-4 835 MHz; \[*Editor's
note:* *it is assumed that proposed mod to 5.442 is accepted.*\]

*f)* that the band 5 925-6 700 MHz is allocated to the fixed,
fixed-satellite (Earth-to-space), and mobile services on a co-primary
basis;

*g)* that the use of the bands 4 500-4 800 MHz (space-to-Earth) by the
fixed-satellite service shall be in accordance with the provisions of
Appendix **30B** (see No. **5.441**);

*h)* that provisions for the coordination of terrestrial and space
services exist in the Radio Regulations,

noting

*a)* that the criteria used and assumptions made in sharing studies
between aeronautical mobile telemetry flight test applications and other
services are only applicable to this specific case,

resolves

1 that, in the bands 4 400-4 940 MHz and 5 925-6 700 MHz,
administrations authorizing aeronautical mobile telemetry for flight
test purposes shall utilize the criteria set forth below:

-- emissions limited to transmission from aircraft stations only, see
No. **1.83**;

-- in these bands, aeronautical mobile telemetry is not considered an
application of a safety service as per No. **1.59**;

-- the peak e.i.r.p. density shall not exceed −2.2 dB(W/MHz);

-- transmissions limited to designated flight test areas, where flight
test areas are airspace designated by administrations for flight testing
within their territories;

-- if operation of AMT aircraft stations are planned within 500 km of
the territory of an administration in which the band 4 825-4 835 MHz is
allocated to radio astronomy on a primary basis (see No. **5.443**),
consult with that administration to determine whether any special
measures are needed to prevent interference to their radio astronomy
observations;

-- in the bands 4 400-4 940 MHz and 5 925-6 700 MHz, bilateral
coordination for transmitting AMT aircraft station with respect to
receiving fixed or mobile stations must be effected if the AMT aircraft
station will operate within 450 km of the receiving fixed or mobile
stations of another administration. The following procedure should be
used to establish whether fixed or mobile service receiver within 450 km
of the flight test area will receive an acceptable level of
interference:

-- determine if the receiving fixed or mobile station's antenna
main-beam axis, out to a distance of 450 km from the fixed service
receiver, passes within 12 km of the designated area used by
transmitting AMT aircraft stations, where this distance is measured
orthogonally from the main-beam axis projection on the Earth's surface
to the nearest boundary of the projection of the flight test area on the
Earth's surface;

-- if the main-beam axis does not intersect the flight test area or any
point within the 12 km offset, the interference could be accepted.
Otherwise further bilateral coordination discussions would be needed;

2 that administrations authorizing aeronautical mobile telemetry in the
bands 4 400-4 940 MHz and 5 925-6 700 MHz require the use of technical
and/or operational measures on AMT where appropriate to facilitate
sharing with other services and applications in these bands.

**Reasons:** Resolution \[IAP/14A2/16\] (WRC‑07) provides the sharing
conditions for aeronautical mobile telemetry for flight testing in order
to ensure compatibility between AMT and the other co‑primary services in
the bands 4 400-4 940 MHz and 5 925-6 700 MHz, as referenced in footnote
5.441A.

#### Agenda item 1.6

1.6 to consider additional allocations for the aeronautical mobile (R)
service in parts of the bands between 108 MHz and 6 GHz, in accordance
with Resolution **414** **(WRC‑03)** and, to study current satellite
frequency allocations, that will support the modernization of civil
aviation telecommunication systems, taking into account Resolution
**415** **(WRC‑03)**

Proposals for Agenda item 1.6

Background information

Resolution 414 (WRC‑03)

Existing AM(R)S bands are nearing saturation in high traffic areas. In
addition, new applications and concepts in air traffic management put
further pressure on existing AM(R)S bands. Resolution 414 (WRC‑03)
states that new technologies to support air navigation may not conform
to the definition of aeronautical radionavigation in the Radio
Regulations. WRC‑03 provided a mechanism to implement these new aviation
technologies by adding AM(R)S use in the band 108-117.975 MHz by
footnote 5.197A in accordance with Resolution 413 (WRC‑03)[^1]. One
emerging application driving requirements for new AM(R)S spectrum is the
integration of command and control for unmanned aircraft (UA) into air
traffic services (ATS) airspace. Conversely, AM(R)S spectrum is not
appropriate for UA payload data use, such as downlinking information and
operational data from the UA.

ITU‑R Working Party 8B (WP 8B) and the International Civil Aviation
Organization (ICAO) developed a draft operational concept, and
technology selection criteria and procedures for new aviation
technology. WP 8B and ICAO determined that the new aviation systems
require two distinct categories of AM(R)S spectrum.

The first category for surface applications at airports could support
high data throughput over moderate (i.e. up to several kilometres)
transmission distances. There is a high degree of reuse of this
spectrum. This proposal addresses the 5 000-5 010, 5 010-5 030, and
5 091-5 150 MHz bands for that airport surface application. The AM(R)S
systems are planned to have characteristics based on IEEE 802.16e
standards.

The bands 5 000-5 010 MHz and 5 010-5 030 MHz should be allocated to
AM(R)S limited to surface applications at airports on the basis that
AM(R)S stations operating in these bands cannot cause harmful
interference to, nor claim protection from radionavigation satellite
service (RNSS) systems. Analysis shows that compatibility between AM(R)S
transmitters and RNSS feeder uplink satellite receivers in the 5 000-5
010 MHz band is practicable under worst-case conditions. The analysis
has also shown that compatibility with RNSS feeder downlinks in the
5 010-5 030 MHz band can be achieved with geographic separation between
operating AM(R)S transmitters and RNSS receivers. Since it may not be
practical to implement sufficient geographic separation between AM(R)S
transmitters and RNSS service link receivers in the vicinity of
AM(R)S-equipped airports there may be a possibility of some
incompatibility between the two operations. In these cases, spectrum
management measures such as site-specific analysis, consistent with the
allocation to AM(R)S in the 5 010-5 030 MHz band, will need to be taken
by the responsible administration.

Geographic separation will ensure AM(R)S systems are compatible with
radio astronomy stations operating in the adjacent 4 990-5 000 MHz band.
In the few instances where radio astronomy observatories are in relative
proximity to airports, local coordination can be employed to resolve any
remaining issues.

The 5 091-5 150 MHz band is used by the fixed-satellite service to
provide feeder uplinks for non-geostationary mobile-satellite service
systems. Studies within WP 8B have shown that those feeder links would
be protected from interference from new AM(R)S applications proposed for
this band. ITU‑R has also studied this band under Agenda item 1.5 for
the purpose of aeronautical mobile telemetry applications. These studies
have shown that AM(R)S can share with both the existing fixed satellite
service and possible aeronautical telemetry (AMT) systems in the band 5
091-5 150 MHz. No priority over other uses in this band is established
for the AM(R)S uses.

The second category for bidirectional air to ground applications could
support a moderate data throughput over longer propagation distances out
to radio line-of-sight. These applications require a number of distinct
channels to allow for sector-to-sector assignments. For radio
line-of-sight applications, ICAO and WP 8B recommended 960-1 024 MHz as
a suitable band. The provisions of the new footnote No. 5.XXX and
Resolution \[IAP/14A2/21\] (WRC‑07), contained in this proposal should
enter into force on \[10\] November 2007. The provisional application of
this footnote and associated Resolution should be contained in a WRC
Resolution similar to Resolution 96 (WRC‑03) on the provisional
application of certain provisions of the Radio Regulations as revised by
WRC‑03 and abrogation of certain resolutions and recommendations.

Consistent with development of CPM text, WP 8B discussed that there is a
need to account for systems in the aeronautical radionavigation service
operating in 960-1164 MHz band for which no standards and recommended
practices (SARPs) have been developed by the International Civil
Aviation Organization (ICAO). The countries operating these systems are
identified in No. 5.312.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/17

890-1 300 MHz

**Reasons:** To provide allocations to support evolving AM(R)S
applications.

**ADD** IAP/14A2/18

**5.XXX** The band 960-1 024 MHz is also allocated to the aeronautical
mobile (R) service on a primary basis, limited to systems operating in
accordance with recognized international aeronautical standards. Such
use also shall be in accordance with Resolution** \[IAP/14A2/21\]
(WRC‑07)**.

**Reasons:** To provide allocations to support evolving AM(R)S
applications. Compatibility with regard to existing aeronautical
radionavigation service (ARNS) systems will be addressed as a part of
standards development for the new AM(R)S system.

**ADD** IAP/14A2/19

**5.AMR** The bands 5 000-5 010 MHz and 5 010-5 030 MHz are also
allocated to the aeronautical mobile (R) service on a primary basis,
limited to systems operating in accordance with recognized international
aeronautical standards. Such use shall be in accordance with Resolution
**\[IAP/14A2/23\] (WRC‑07)**.

**Reasons:** To provide allocations to support evolving AM(R)S surface
applications at airports.

**ADD** IAP/14A2/20

**5.ZZZ** The band 5 091-5 150 MHz is also allocated to the aeronautical
mobile (R) service on a primary basis, limited to surface applications
at airports by systems operating in accordance with recognized
international aeronautical standards. Such use shall be in accordance
with Resolution **\[IAP/14A2/24\] (WRC‑07)**.

**Reasons:** To provide allocations to support evolving AM(R)S
applications. Compatibility with regard to existing aeronautical
radionavigation service (ARNS) systems will be addressed as a part of
standards development for the new AM(R)S system. The 5 091-5 150 MHz
band is used by the fixed-satellite service to provide feeder uplinks
for non-geostationary mobile-satellite systems (5.444A). ITU‑R studies
show that these feeder links would be protected for interference from
new AM(R)S applications proposed for this band. No priority over the FSS
in this band is established for the AM(R)S uses.

**ADD** IAP/14A2/21

RESOLUTION \[IAP/14A2/21\] (WRC‑07)

Use of the band 960-1 024 MHz by aeronautical services

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* the current allocation of the frequency band 960-1 164 MHz to the
aeronautical radionavigation service (ARNS);

*b)* the use of the band 960-1 215 MHz by the aeronautical
radionavigation service is reserved on a worldwide basis for the
operation and development of airborne electronic aids to air navigation
and any directly associated ground-based facilities per No. **5.328**;

*c)* that new technologies are being developed to support communications
and air navigation, including airborne and ground surveillance
applications;

*d)* that new applications and concepts in air traffic management which
are data intensive are being developed,

recognizing

*a)* that precedence must be given to the ARNS operating in the
frequency band 960-1 164 MHz;

*b)* that Annex 10 of the Convention of the International Civil Aviation
Organization (ICAO) contains standards and recommended practices (SARPs)
for aeronautical radionavigation and radiocommunication systems used by
international civil aviation;

*c)* that all compatibility issues between the ICAO standard Universal
Access Transceiver (UAT) and other systems which operate in the band
960-1 024 MHz have been addressed within ICAO,

noting

that excluding the system identified in *recognizing c)*, no
compatibility criteria currently exist between AM(R)S systems proposed
for operations in the frequency band 960-1 024 MHz and the existing ARNS
aeronautical systems in the band,

resolves

1 that prior to operating in the frequency band 960-1 024 MHz any AM(R)S
systems shall have standards and recommended practices requirements
published in Annex 10 of the ICAO Convention on International Civil
Aviation, and that those requirements will ensure compatibility with and
not constrain the future development of ARNS systems operating in
accordance with international (ICAO) standards;

2 that any AM(R)S systems operating in the band 960-1 024 MHz shall not
cause harmful interference to, nor claim protection from, and shall not
impose constraints on the operation and planned development of
aeronautical radionavigation systems operating in accordance with
international (ICAO) standards in the same band,

instructs the Secretary-General

to bring this Resolution to the attention of ICAO.

**Reasons:** A Resolution is needed to indicate the systems allowed
under the AM(R)S allocation in the 960-1 024 MHz band and to explain the
role of ICAO in developing standards for compatibility between ARNS and
AMRS in this band.

**ADD** IAP/14A2/22

Insert in the *resolves* of Resolution \[IAP/14A2/22\] (WRC‑07).
Provisional application of certain provisions of the Radio Regulations
as revised by WRC‑07 and abrogation of certain Resolutions and
Recommendations (see example below):

Radio Regulations **5.XXX** and Resolution **\[IAP/14A2/21\] (WRC‑07)**
shall provisionally apply as of \[10\] November 2007.

RESOLUTION \[IAP/14A2/22\] (WRC‑07)

Provisional application of certain provisions of the Radio Regulations\
as revised by WRC‑07 and abrogation of certain\
Resolutions and Recommendations

The World Radiocommunication Conference (Geneva, 2007),

...

resolves

1 that, as of \[10\] November 2007, the following provisions of the RR,
as revised or established by this Conference, shall provisionally apply:
... Nos. ... **5.XXX**, ...

...

further resolves

1 that, as of \[10\] November 2007, the following Resolutions, as
revised or established by this Conference, shall provisionally apply:

...

Resolution** \[IAP/14A2/21\] (WRC‑07)**

...

**Reasons:** Because the Resolution and Radio Regulations 5.XXX address
compatibility issues that need to be implemented prior to adding AM(R)S
uses to the band, the provisions of the new footnote should enter into
force on \[10\] November 2007. The provisional application of this
footnote should be inserted in the WRC‑07 resolution similar to
Resolution 96 (WRC‑03) on the provisional application of certain
provisions of the Radio Regulations as revised by WRC‑03 and abrogation
of certain resolutions and recommendations.

**ADD** IAP/14A2/23

RESOLUTION \[IAP/14A2/23\] (WRC‑07)

Use of the 5 000-5 030 MHz band by the aeronautical mobile (R) service
and\
protection of the radionavigation-satellite and the radio astronomy
services

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* the current allocation of the frequency band 5 000-5 010 MHz to the
aeronautical mobile satellite (R) service (AMS(R)S) subject to agreement
obtained under No. **9.21**, the aeronautical radionavigation service
(ARNS) and the radionavigation-satellite service (RNSS)
(Earth-to-space);

*b)* the current allocation of the frequency band 5 010-5 030 MHz to the
AMS(R)S, subject to agreement obtained under No. **9.21**, the ARNS and
the RNSS (space-to-Earth and space-to-space);

*c)* that this Conference has made allocations to the aeronautical
mobile (R) service (AM(R)S) in the bands 5 000-5 010 MHz and
5 010-5 030 MHz limited to systems operating in accordance with
recognized international aeronautical standards;

*d)* that the International Civil Aviation Organization (ICAO) is in the
process of identifying the technical and operating characteristics of
new systems operating in the AM(R)S in the bands 5 000-5 010 MHz and
5 010-5 030 MHz;

*e)* that compatibility between AM(R)S systems and aeronautical
radionavigation systems operating in accordance with international
aeronautical standards will be ensured by ICAO,

recognizing

*a)* that ICAO publishes recognized international aeronautical standards
for AM(R)S;

*b)* that preliminary studies have been conducted within ITU‑R
concerning the sharing and compatibility of surface-based AM(R)S systems
with planned RNSS systems in the bands 5 000-5 010 MHz and
5 010-5 030 MHz, and compatibility with the radio astronomy service
operating in the band 4 990-5 000 MHz;

*c)* that system characteristics for RNSS and AM(R)S systems planned for
the bands 5 000-5 010 MHz and 5 010-5 030 MHz are still evolving;

*d)* that technical characteristics and operational parameters for the
RNSS and AM(R)S have not been fully established within ITU‑R and ICAO
respectively;

*e)* that the RNSS will need access to the bands 5 000-5 010 MHz and
5 010-5 030 MHz for service and feeder links in the longer term;

*f)* that spectrum efficiency is enhanced in situations where new
applications can be implemented compatibly in bands to be used by
multiple services,

noting

*a)* that currently only preliminary guidelines are available for the
AM(R)S to ensure protection of the RNSS;

*b)* that ITU‑R is actively developing new Recommendations regarding the
technical characteristics and operational parameters for the RNSS;

*c)* that appropriate regulatory provisions would ensure protection of
the RNSS,

resolves

1 that the operation of stations in the AM(R)S in the 5 000-5 010 MHz
and 5 010-5 030 MHz bands shall not cause harmful interference to, nor
claim protection from, RNSS systems;

2 that in the frequency bands 5 000-5 010 MHz and 5 010-5 030 MHz any
AM(R)S systems shall operate in accordance with Standards and
Recommended Practices (SARPs) requirements published in Annex 10 of the
ICAO Convention on International Civil Aviation;

3 that AM(R)S use in the bands 5 000-5 010 MHz and 5 010-5 030 MHz shall
be limited to surface applications at airports,

requests ITU‑R

1 to study, in the bands 5 000-5 010 MHz and 5 010-5 030 MHz, the
technical and operational issues relating to the protection of the RNSS
by the AM(R)S;

2 to study the technical and operational issues relating to the
compatibility between the radio astronomy service operating in the
4 990-5 000 MHz band and the AM(R)S operating in the bands
5 000-5 010 MHz and 5 010-5 030 MHz;

3 to incorporate in ITU‑R Recommendations and/or Reports the results
from the studies in *requests ITU‑R* 1 and 2,

invites

1 administrations and ICAO to supply technical and operational
characteristics for the AM(R)S necessary for compatibility studies, and
to participate actively in the studies;

2 administrations to supply technical and operational characteristics
and protection criteria for the RNSS necessary for compatibility
studies, and to participate actively in the studies,

instructs the Secretary-General

to bring this Resolution to the attention of ICAO.

**Reasons:** A resolution is needed to outline the conditions of the
proposed use of the bands 5 000-5 010 MHz and 5 010-5 030 MHz by the
AM(R)S and to explain the role of administrations, ITU‑R, and ICAO in
developing technical and operational parameters, and compatibility
studies, in order to ensure protection of the RNSS from emissions of the
AMRS in these bands.

**ADD** IAP/14A2/24

RESOLUTION \[IAP/14A2/24\] (WRC‑07)

Compatibility between the aeronautical mobile (R) service and
fixed-satellite\
service (Earth-to-space) in the band 5 091 -5 150 MHz

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that the current allocation of the 5 091-5 150 MHz band to the
fixed-satellite service (FSS) (Earth-to-space), is limited to feeder
links of non-geostationary satellite (non-GSO) systems in the
mobile-satellite service (MSS));

*b)* the current allocation of the frequency band 5 000-5 150 MHz to the
aeronautical mobile-satellite (R) service is subject to agreement
obtained under No. **9.21**. This band is also allocated to the
aeronautical radionavigation service (ARNS);

*c)* that this Conference has allocated the 5 091-5 150 MHz band for the
aeronautical mobile (R) service limited to systems operating in
accordance with recognized international aeronautical standards;

*d)* that this Conference has allocated the 5 091-5 150 MHz band to the
aeronautical mobile service (AMS) limited to secure and confidential
communications between aircraft and ground, principally during unlawful
interference to aircraft;

*e)* that ICAO is in the process of identifying the technical and
operating characteristics of new systems operating in the AM(R)S in the
band 5 091-5 150 MHz;

*f)* that one AM(R)S system, to be used by aircraft operating on the
airport surface, has demonstrated compatibility with the FSS in the
5 091-5 150 MHz band;

*g)* that ITU‑R studies have examined potential sharing among AMS
applications and have shown that the aggregate interference from
aeronautical security, aeronautical telemetry and AM(R)S should total no
more than 3% Δ*T*/*T*,

recognizing

*a)* that precedence is to be given to the microwave landing system
(MLS) in accordance with No. **5.444** in the frequency band
5 030-5 150 MHz;

*b)* that Resolution **114 (WRC‑03)** applies to the sharing conditions
between the fixed-satellite and aeronautical radionavigation service in
the 5 091-5 150 MHz band;

*c)* that the International Civil Aviation Organization publishes
standards for aeronautical mobile (R) systems,

noting

*a)* that ITU‑R studies describe methods for ensuring compatibility
between the AM(R)S and FSS operating in the band 5 091-5 150 MHz,

*b)* that the use of the band 5 091-5 150 MHz by the AM(R)S needs to
ensure protection of the current or planned use of this band by the FSS
(Earth-to-space),

resolves

1 that administrations, in making assignments to stations in the
aeronautical mobile (R) service shall take into account the
International Civil Aviation (ICAO) Standards and Recommended Practices
(SARPs);

2 that in part to meet the provisions of Article **4**, No. **4.10**,
the coordination distance with respect to stations in the fixed
satellite service (FSS) operating in the band 5 091-5 150 MHz shall be
based on ensuring that the received signal at the AM(R)S station from
the FSS transmission does not exceed −143 dB(W/MHz), where the required
basic transmission loss shall be determined using the methods described
in Recommendations ITU‑R P.525-2 and ITU‑R P.526-9;

3 that the Δ*T*/*T* aggregate interference into FSS space station
receivers from AM(R)S stations shall be limited to xx%[^2],

invites

administrations and ICAO to supply technical and operational criteria
necessary for sharing studies for the aeronautical mobile (R) service,
and to participate actively in such studies,

instructs the Secretary-General

to bring this Resolution to the attention of ICAO.

**Reasons:** A resolution is needed to outline the conditions of the
proposed use of the band 5 091-5 150 MHz by the AM(R)S and to explain
the role of administrations, ITU‑R, and ICAO in developing technical and
operational parameters, and compatibility studies, in order to ensure
protection of the fixed-satellite service from emissions of the AMRS in
this band.

**NOC** IAP/14A2/25

RESOLUTION 413 (WRC‑03)

Use of the band 108-117.975 MHz by aeronautical services

**Reasons:** No additional allocations are being proposed that require
Resolution 413 (WRC‑03) to be modified to ensure compatibility with
existing services in lower adjacent band. If such proposals are made by
the WRC it would be appropriate to review Resolution 413 (WRC‑03).

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**NOC** IAP/14A2/26

75.2-137.175 MHz

+----------------------+----------------------+-----------------------+
| Allocation to        |                      |                       |
| services             |                      |                       |
+----------------------+----------------------+-----------------------+
| Region 1             | Region 2             | Region 3              |
+----------------------+----------------------+-----------------------+
| **108-117.975**      |                      |                       |
| AERONAUTICAL         |                      |                       |
| RADIONAVIGATION      |                      |                       |
|                      |                      |                       |
| 5.197 5.197A         |                      |                       |
+----------------------+----------------------+-----------------------+

**Reasons:** No additional allocations are being proposed. AM(R)S
allocations in the band 108-117.975 MHz are only being considered by the
United States for new aviation navigation surveillance technology
consistent with No. 5.197A. ITU‑R studies determining the feasibility of
extending AM(R)S use in this band have not been completed. Additionally,
ITU‑R studies determining compatibility issues between AM(R)S in this
band and the broadcasting service in the adjacent band (87-108 MHz) have
not been completed.

**MOD** IAP/14A2/27

4 800-5 570 MHz

**Reasons:** To provide allocations to support evolving AM(R)S
applications.

Resolution 415 (WRC‑03) -- Study of current satellite frequency
allocations that will support the modernization of civil aviation
telecommunications systems

Existing aeronautical mobile (R) service bands are nearing saturation in
high traffic areas. In addition, new applications and concepts in air
traffic management put further pressure on existing aeronautical mobile
bands. In particular, the 117.975-136 MHz band is extremely congested
due to increased aeronautical mobile use in the band. For the
aforementioned reasons, and since there are no operational or planned
AMS(R)S systems in this band, the secondary allocation to AMS(R)S in
Radio Regulation No. 5.198 should be suppressed.

With ever-increasing speed, existing and new communications systems are
being based on Internet-related protocols and services. Access to these
services with sufficient bandwidth is becoming essential for all forms
of telecommunications. Communications with aircraft are not exempt from
this growing dependence on Internet applications. Aircraft owners and
operators are realizing that without this access aeronautical operations
will be hindered from gaining the efficiencies and benefits that these
types of service offer. Internet usage is fast becoming dependent on
broadband connectivity. A demonstrated viable means of providing this
connectivity for mobile platforms on an intercontinental basis is
through satellite channels.

The ITU‑R recognized that the use of the 14.0-14.5 GHz band for the
aeronautical mobile-satellite service (AMSS) on a secondary basis was
compatible with current fixed-satellite service (FSS) systems and was
supported by studies leading up to WRC‑03. Additional studies in ITU‑R
also confirmed compatibility with other services in the 14.0-14.5 GHz
range. At WRC‑03, the decision was made to expand the secondary MSS
allocation in the 14-14.5 GHz band to include AMSS (Earth-to-space). In
addition, although there were no changes made to the Radio Regulations
for a corresponding downlink, there were some discussions at the 14th
Plenary Meeting of WRC‑03 confirming use of the associated 10/11/12 GHz
downlink (space-to-Earth) bands to facilitate this service. This
decision has enabled the use of Internet applications by aircrews and
passengers.

The 14.0-14.5 GHz AMSS (Earth-to-space) secondary allocation is
currently being used operationally by aircraft earth stations globally.
At the same time and due to the FSS spectrum pairing arrangement the
10/11/12 GHz (space-to-Earth) frequency bands are currently being used
operationally for transmissions to these aircraft earth stations. It
should be noted that the AMSS systems operate within the envelope of FSS
technical requirements and coordination agreements reached for specific
FSS satellite networks. The downlink (space-to-Earth) transmissions to
AMSS earth stations are not treated any differently from those to FSS
earth stations in the primary FSS services.

It should also be noted that the intended AMSS services operating within
the FSS range of frequencies, are not to be used for provision of
safety-of-life services or the AMS(R)S services, as defined in
accordance with categories 1 to 6 of Article 44 of the Radio
Regulations.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/28

75.2-137.175 MHz

+----------------------+----------------------+-----------------------+
| Allocation to        |                      |                       |
| services             |                      |                       |
+----------------------+----------------------+-----------------------+
| Region 1             | Region 2             | Region 3              |
+----------------------+----------------------+-----------------------+
| **117.975-137**      |                      |                       |
| AERONAUTICAL MOBILE  |                      |                       |
| (R)                  |                      |                       |
|                      |                      |                       |
| 5.111 5.199 5.200    |                      |                       |
| 5.201 5.202 5.203    |                      |                       |
| 5.203A 5.203B        |                      |                       |
+----------------------+----------------------+-----------------------+

**Reasons:** The modification of the table is due to the suppression of
No. 5.198.

**SUP** IAP/14A2/29

**5.198**

**Reasons:** The secondary allocation by footnote to AMS(R)S is no
longer needed.

**[NOC]{.underline}** IAP/14A2/30

No change in the band 10.7-12.75 GHz of Article 5 of the Radio
Regulations.

**Reasons:** The current FSS allocations can support expansion of
broadband satellite services on‑board aircraft, consistent with their
current allocations and regulations; as a result neither additional
spectrum, nor any changes to the RR are necessary.

**[NOC]{.underline}** IAP/14A2/31

**5.504A** In the band 14-14.5 GHz, aircraft earth stations in the
secondary aeronautical mobile-satellite service may also communicate
with space stations in the fixed-satellite service. The provisions of
Nos. **5.29**, **5.30** and **5.31** apply.    (WRC‑03)

**Reasons:** Current FSS allocations can support expansion of broadband
satellite services on-board aircraft, consistent with their current
allocations and regulations; as a result, neither additional spectrum,
nor any changes to the Radio Regulations are necessary.

#### Agenda item 1.8

1.8 to consider the results of ITU-R studies on technical sharing and
regulatory provisions for the application of high altitude platform
stations operating in the bands 27.5-28.35 GHz and 31‑31.3 GHz in
response to Resolution **145** **(WRC‑03),** and for high altitude
platform stations operating in the bands 47.2-47.5 GHz and 47.9-48.2 GHz
in response to Resolution **122 (Rev.WRC‑03)**

Proposals for Agenda item 1.8

Proposals for modifications to two footnotes and Resolution 145 (WRC‑03)

Background information

Resolution 145 (WRC‑03): WRC‑2000 decided to adopt provisions for the
operation of HAPS on a non-interfering/non-protected basis in the bands
27.5-28.35 and 31-31.3 GHz in Region 3, but did not allow operation in
the entire bands until studies could be completed to determine how best
to protect existing services in these and nearby frequency bands. WRC‑03
further refined these provisions by deciding to limit HAPS operation to
300 MHz in a specified direction in each of these two bands, retaining
the requirement for HAPS to operate on a non-interfering/non-protected
basis in these two 300 MHz segments, and adopting Resolution 145
(WRC‑03), which created the possibility of allowing Region 2
administrations to advise the Radiocommunication Bureau of their intent
to implement HAPS systems within the bands 27.5-28.35 and 31-31.3 GHz.
Administrations intending to implement HAPS in these bands are to seek
the explicit agreement of concerned administrations in accordance with
*resolves* 4 of this Resolution.

Under Resolution 145 (WRC‑03), the use of HAPS within the fixed-service
allocations within the 27.5-28.35 GHz and 31-31.3 GHz bands must be
limited to 300 MHz in each band, and is subject to the condition that
such use must not cause harmful interference to, nor claim protection
from, other stations of services operating in accordance with the Table
of Frequency Allocations of Article 5. Furthermore, the
Resolution specifies that the development of these other services shall
proceed without constraints by HAPS operating pursuant to the
Resolution. This Resolution also calls for the identification of a
common 300 MHz within the 27.5-28.35 GHz band for use by HAPS. With
respect to the band 31-31.3 GHz, Resolution 145 (WRC‑03) specifies that
systems using HAPS in Region 2 in the band 31-31.3 GHz must not cause
harmful interference to the radio astronomy service having a primary
allocation in the band 31.3-31.8 GHz, taking into account the protection
criterion given in Recommendation ITU‑R RA.769. The Resolution contains
limits on the level of unwanted power density into the HAPS ground
station antenna in the band 31.3-31.8 GHz in order to ensure the
protection of satellite passive services.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/32

**5.537A** In Bhutan, Korea (Rep. of), the Russian Federation,
Indonesia, Iran (Islamic Republic of), Japan, Kazakhstan, Lesotho,
Malaysia, Maldives, Mongolia, Myanmar, Uzbekistan, Pakistan, the
Philippines, Kyrgyzstan, the Dem. People's Rep. of Korea, Sri Lanka,
Thailand and Viet Nam, the allocation to the fixed service in the
band 27.5-27.8 GHz may also be used by high altitude platform stations
(HAPS) within the territory of these countries. Such use of 300 MHz of
the fixed-service allocation by HAPS in the above countries is further
limited to operation in the HAPS-to-ground direction and shall not cause
harmful interference to, nor claim protection from, other types of
fixed-service systems or other co‑primary services. Furthermore, the
development of these other services shall not be constrained by HAPS.
See Resolution **145 (Rev.WRC‑07)**.     (WRC-07)

**Reasons:** WRC‑03 called for the identification of a common 300 MHz
band, within the 27.5-28.35 GHz band, for use by HAPS in those countries
wishing to implement such service. Such identification will help to ease
the implementation and harmonization of HAPS in those countries.
Identifying the lowest 300 MHz segment for potential use by HAPS
maximizes the amount of contiguous FSS spectrum in the 27.5-30.0 GHz
band that would not be impaired domestically in any way as a consequence
of any potential use of the band by HAPS.

**MOD** IAP/14A2/33

**5.543A** In Bhutan, Korea (Rep. of), the Russian Federation,
Indonesia, Iran (Islamic Republic of), Japan, Kazakhstan, Lesotho,
Malaysia, Maldives, Mongolia, Myanmar, Uzbekistan, Pakistan, the
Philippines, Kyrgyzstan, the Dem. People's Rep. of Korea, Sri Lanka,
Thailand and Viet Nam, the allocation to the fixed service in the
band 31-31.3 GHz may also be used by systems using high altitude
platform stations (HAPS) in the ground-to-HAPS direction. The use of the
band 31-31.3 GHz by systems using HAPS is limited to the territory of
the countries listed above and shall not cause harmful interference to,
nor claim protection from, other types of fixed-service systems, systems
in the mobile service and systems operated under No. **5.545**.
Furthermore, the development of these services shall not be constrained
by HAPS. Systems using HAPS in the band 31-31.3 GHz shall not cause
harmful interference to the radio astronomy service having a primary
allocation in the band 31.3-31.8 GHz, taking into account the protection
criterion as given in Recommendation ITU‑R RA.769. In order to ensure
the protection of satellite passive services, the level of unwanted
power density into a HAPS ground station antenna in the band
31.3-31.8  GHz shall be limited to 106 dB(W/MHz) under clear-sky
conditions, and may be increased up to ‑100 dB(W/MHz) under rainy
conditions to mitigate against fading due to rain, provided the
effective impact on the  passive satellite does not exceed the impact
under clear-sky conditions. See Resolution **145
(Rev.WRC‑07)**.     (WRC-07)

**Reasons:** Revisions to text add clarity. Consequential to the changes
to Resolution 145 (WRC‑03) in IAP/14A2/34.

**MOD** IAP/14A2/34

RESOLUTION 145 (Rev.WRC-03)

Potential use of the bands 27.5-27.8 GHz and 31-31.3 GHz\
by high altitude platform stations (HAPS)\
in the fixed service

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that WRC‑97 made provision for the operation of HAPS, also known as
stratospheric repeaters, within a 2  300 MHz portion of the
fixed-service allocation in the bands 47.2-47.5 GHz and 47.9-48.2 GHz;

*b)* that WRC‑97 adopted No. **4.15A** specifying that transmissions to
or from HAPS shall be limited to the bands specifically identified in
Article **5**;

*c)* that at WRC‑2000, several countries in Region 3 and one country in
Region 1 expressed a need for a lower frequency band for HAPS due to the
excessive rain attenuation that occurs at 47 GHz in these countries;

*d)* that some countries in Region 2 have also expressed an interest in
using a frequency range lower than those referred to in
*considering a)*;

*e)* that, in order to accommodate the need expressed by the countries
referred to in *considering c)*, WRC‑2000 adopted Nos. **5.537A** and
**5.543A**, which were modified at WRC‑03 and then again at WRC‑07 to
permit the use of HAPS in the fixed service in the band 27.5-27.8 GHz
and in the band 31-31.3 GHz in certain Region 1 and 3 countries on a
non-harmful interference, non-protection basis;

*f)* that the bands 27.5-27.8 GHz and 31-31.3 GHz are already heavily
used or planned to be used by a number of different services and a
number of other types of applications in the fixed service;

*g)* that while the decision to deploy HAPS can be taken on a national
basis, such deployment may affect neighbouring administrations,
particularly in small countries;

*h)* that the 31.3-31.8 GHz band is allocated to the radio astronomy,
Earth exploration-satellite (passive) and space research (passive)
services, and that WRC‑03 amended No.** 5.543A** to specify signal
levels that would protect satellite passive services and radio astronomy
stations;

*i)* that ITU‑R has conducted studies dealing with sharing between
systems using HAPS in the fixed service and other types of systems in
the fixed service in the bands 27.5-27.8 GHz and 31-31.3 GHz leading to
Recommendation ITU‑R F.1609;

*j)* that results of some ITU‑R studies indicate that, in the bands
27.5-27.8 GHz and 31-31.3 GHz, sharing between fixed-service systems
using HAPS and other conventional fixed-service systems in the same area
will require appropriate interference mitigation techniques to be
developed and implemented;

*k)* that ITU‑R has conducted studies dealing with compatibility between
systems using HAPS and the passive services in the 31.3-31.8 GHz band
leading to Recommendations ITU‑R F.1570 and ITU‑R F.1612;

*l)* that ITU‑R has produced Recommendation ITU‑R SF.1601 containing
methodologies for evaluating interference from the fixed-service system
using HAPS into GSO FSS systems in the band 27.5-27.8 GHz;

*m)* that HAPS technical issues should continue to be studied in order
to determine appropriate measures for protecting the fixed service and
other co-primary services in the band 27.5-27.8 GHz,

resolves

1 that, notwithstanding No. **4.15A**, in Region 2 the use of HAPS
within the fixed-service allocations in the 27.5-27.8 GHz and 31-31.3
GHz bands shall not cause harmful interference to, nor claim protection
from, other stations of services operating in accordance with the Table
of Frequency Allocations of Article **5**, and, further, that the
development of these other services shall proceed without constraints by
HAPS operating pursuant to this Resolution;

2 that any use by HAPS of the fixed-service allocation at 27.5-27.8 GHz
pursuant to *resolves* 1 shall be limited to operation in the
HAPS-to-ground direction, and that any use by HAPS of the fixed-service
allocation at 31-31.3 GHz shall be limited to operation in the
ground-to-HAPS direction;

3 that systems using HAPS in the band 31-31.3 GHz, in accordance with
*resolves* 1 above, shall not cause harmful interference to the radio
astronomy service having a primary allocation in the band 31.3-31.8 GHz,
taking into account the protection criterion given in the relevant ITU‑R
Recommendation in the RA series. In order to ensure the protection of
satellite passive services, the level of unwanted power density into the
HAPS ground station antenna in the band 31.3-31.8 GHz shall be limited
to −106 dB(W/MHz) under clear-sky conditions and may be increased up to
−100 dB(W/MHz) under rainy conditions to take account of rain
attenuation, provided that effective impact on the passive satellite
does not exceed the impact under clear-sky conditions as given above;

4 that the administrations listed in Nos. **5.537A** and **5.543A**
which intend to implement systems using HAPS in the fixed service in the
bands 27.5-27.8 GHz and 31-31.3 GHz shall seek explicit agreement of
concerned administrations with regard to their stations of primary
services to ensure that the conditions in Nos. **5.537A** and **5.543A**
are met, and those administrations in Region 2 which intend to implement
systems using HAPS in the fixed service in these bands shall seek
explicit agreement of concerned administrations with regard to their
stations of services operating in accordance with the Table of Frequency
Allocations of Article **5** to ensure that the conditions in
*resolves* 1 and *resolves* 3 are met;

5 that administrations planning to implement a HAPS system pursuant to
*resolves* 1 above shall notify the frequency assignment(s) by
submitting all mandatory elements of Appendix **4** to the
Radiocommunication Bureau for the examination of compliance with
*resolves* 3 and 4 above,

instructs the Director of the Radiocommunication Bureau

to publish in the International Frequency Information Circular (BR IFIC)
a list of administrations who have so advised, and to publish the
information on HAPS implementation received from administrations which
intend to implement systems using HAPS in the fixed service in the bands
27.5-27.8 GHz and 31-31.3 GHz.

**Reasons:** Changes to frequency ranges throughout, deletion of
*invites* 1, and other minor changes are consequential to proposal
IAP/14A2/32. Deletion of *noting* is made recognizing that this is a
simple statement of fact. Deletion of *invites* 4 is made recognizing
the retention of old *resolves* 4, now *resolves* 3. Changes to *invites
administrations* are proposed to clarify that administrations are to
supply technical details of their systems along with an indication of
their intention to implement HAPS in these frequency bands. The changes
also bring the Resolution up to date.

Proposals for modifications related to Resolution 122 (WRC‑03)

Background information

ITU has been considering the implications of HAPS in the fixed service
in the 47.2-47.5 GHz and 47.9-48.2 GHz band since 1997, when WRC‑97
first made provision for the operation of HAPS within the fixed service.
Studies have been ongoing under versions of Resolution 122 since WRC‑97.

Resolution 122 (Rev.WRC‑2000) indicated that sharing studies remain to
be completed between the fixed-satellite service (FSS) and HAPS
operations in the FS. Pending the completion of studies, Resolution 122
(Rev. WRC‑2000) instructed the Radiocommunication Bureau "that from
22 November 1997, and pending review of the sharing studies in
*considering j)* and review of the notification process by WRC‑03, the
Bureau shall accept notices in the bands 47.2-47.5 GHz and 47.9-48.2 GHz
only for HAPS in the fixed service and for feeder links for the
broadcasting-satellite service, shall continue to process notices for
FSS networks (except for feeder links for the broadcasting-satellite
service) for which complete information for advance publication has been
received prior to 27 October 1997, and shall inform the notifying
administrations accordingly." In other words, notices received after 22
November, 1997 from non-BSS feeder link FSS networks in the
47.2-47.5 GHz and 47.9-48.2 GHz bands have not been accepted.

Resolution 122 (Rev.WRC‑03) extended the restriction on processing of
notices for FSS networks other than those providing service exclusively
within Region 2. It also instructed the Bureau to maintain, until a date
to be decided by a future WRC, notices concerning HAPS that were
received by the Bureau prior to 22 November 1997 and provisionally
recorded in the Master International Frequency Register. This is a
substantial exception to No. 11.26, which provides that "\[n\]otices
relating to assignments for high altitude platform stations in the fixed
service in the bands 47.2-47.5 GHz and 47.9-48.2 GHz shall reach the
Bureau not earlier than five years before the assignments are brought
into use."

The studies regarding HAPS in the 47.2-47.5 GHz and 47.9-48.2 GHz bands
have been completed and the results are contained in Recommendation
ITU‑R SF.1481. This recommendation makes clear that co-frequency
operations between HAPS in the fixed service and FSS networks and
systems are feasible in the 47.2-47.5 GHz and 47.9-48.2 GHz bands, even
while noting that "there may be a need to develop the maximum allowable
power flux-density at satellites on the GSO due to aggregate
interference caused by ground user terminals of high altitude platform
networks." The revision to Resolution 122 (Rev.WRC‑03) that was approved
at WRC‑03 confirms that coexistence between HAPS in the FS and the FSS
at 47.2-47.5 GHz and 47.9-48.2 GHz is feasible, as administrations were
encouraged to facilitate interservice coordination.

In the WRC‑03 revision of Resolution 122 (Rev.WRC‑03), the ITU‑R was
invited to study power limitations on HAPS ground stations to facilitate
sharing with space station receivers, regulatory provisions to address
deployment of HAPS in the FS near country borders, and technical sharing
criteria between HAPS in the FS and both radio astronomy and FSS systems
(taking into account the operational environments and the requirements
of FSS systems). With the exception of interference to and from FSS
spacecraft, and border area coordination matters in the FS, the
deployment of HAPS is a national issue. The issue of interference
between the FSS satellite and HAPS networks can be addressed through
coordination using Articles 9 and 11 of the Radio Regulations. As a
result, Resolution 122 (Rev.WRC‑03) can be suppressed, provided that
reference to the use of Article 9 for HAPS is included in a new
resolution that is referenced in No. 5.552A of the Radio Regulations.
The Bureau should be instructed to retain all notices concerning HAPS
that are maintained in the MIFR only by virtue of *instructs the
Director of the Radiocommunication Bureau* 1 of Resolution 122 (Rev.
WRC‑03) only until 1 January 2010, unless the notifying administration
earlier informs the Bureau that the notified assignments have been
brought into use.

**SUP** IAP/14A2/35

RESOLUTION 122 (Rev.WRC‑03)

Use of the bands 47.2-47.5 GHz and 47.9-48.2 GHz by high altitude
platform stations (HAPS) in the fixed service and by other services

**Reasons:** Studies called for in relation to HAPS at 47 GHz have been
completed. The Resolution 122 (Rev.WRC‑03) application of the provisions
of Article 9 is proposed for incorporation into the Radio Regulations
(see IAP below).

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/36

**5.552A** The allocation to the fixed service in the bands 47.2-47.5
GHz and 47.9-48.2 GHz is designated for use by high altitude platform
stations. The use of the bands 47.2-47.5 GHz and 47.9-48.2 GHz by high
altitude platforms in the fixed service is subject to the provisions of
Resolution **\[IAP/14A2/37\] (WRC‑07)**. All notices for high altitude
platform stations in these bands that were filed with the Bureau prior
to 22 November 1997 shall be cancelled as of 1 January 2010 unless the
notifying administration informs the Bureau before this date that the
notified assignments have been brought into use.     (WRC-97)

**Reasons:** Consequential to the suppression of Resolution 122
(Rev.WRC‑03). While studies have been completed, HAPS systems still need
to be subject to the provisions of Article 9 to ensure coordination with
the FSS at 47 GHz. Nos. 9.17 and 9.18, which apply for the coordination
of terrestrial stations, including HAPS, with earth stations, are
currently applicable without having to be called out in a footnote to
Article 5 of the Radio Regulations. Resolution \[IAP/14A2/37\] (WRC‑07)
is a new resolution (see IAP below) that is intended to address the
previously unaddressed coordination case of transmitting HAPS
ground-based stations with receiving space station of the FSS, when the
HAPS ground station appears in the coverage area of a satellite network.
The final sentence of the provision is needed because Resolution 122
(Rev.WRC‑03) instructs the BR to maintain HAPS notices received prior to
22 November 1997 "until a date to be decided by a future WRC".

**ADD** IAP/14A2/37

RESOLUTION \[IAP/14A2/37\] (WRC‑07)

Additional coordination mechanism resulting from high altitude platform\
stations (HAPS) in the fixed service in the bands 47.2-47.5 GHz and\
47.9-48.2 GHz by and by other services

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that the band 47.2-50.2 GHz is allocated to the fixed, mobile and
fixed-satellite services on a co-primary basis;

*b)* that WRC‑97 made provision for operation of HAPS, also known as
stratospheric repeaters, within the fixed service in the bands
47.2-47.5 GHz and 47.9-48.2 GHz;

*c)* that Recommendation ITU‑R F.1500 contains the characteristics of
systems in the fixed service using HAPS;

*d)* that Recommendation ITU‑R SF.1481‑1 contains information on
frequency sharing between systems in the fixed service using high
altitude platform stations and satellite systems in the geostationary
orbit in the fixed-satellite service in the bands 47.2-47.5 GHz and
47.9-48.2 GHz;

*e)* that while the decision to deploy HAPS can be taken on a national
basis, such deployment may affect neighbouring administrations;

*f)* that ITU‑R has completed studies dealing with sharing between
systems using HAPS in the fixed service and other types of systems in
the fixed service in the bands 47.2-47.5 GHz and 47.9-48.2 GHz,

recognizing

*a)* that the procedures of Article **9** have been applied on a
provisional basis from the end of WRC‑97 through the end of WRC‑07 for
coordination between satellite systems and systems using HAPS in the
bands 47.2-47.5 GHz and 47.9-48.2 GHz;

*b)* that with the suppression of Resolution **122 (Rev.WRC‑03)** as of
the end of WRC‑07, there is a need to provide coordination provisions
between satellite systems and systems using HAPS in the bands
47.2-47.5 GHz and 47.9-48.2 GHz in cases not presently covered under the
procedures of Article **9**;

*c)* that Nos. **9.17** and **9.18** apply for the coordination of
terrestrial stations, including HAPS, with earth stations, and vice
versa;

*d)* that the coordination scenario involving a transmitting station in
the fixed service which is part of a high altitude platform network as
defined by No. **1.66A**, and other administrations with frequency
assignments for existing or planned space stations in any frequency band
in which the high altitude platform station network is to operate, is
not presently addressed in Section** II** of Article **9**,

resolves

1 to encourage administrations to facilitate coordination between
systems in the fixed service using HAPS operating in the bands
47.2-47.5 GHz and 47.9-48.2 GHz and systems of the co‑primary satellite
services in the same bands;

2 that, before an administration notifies to the Bureau or brings into
use a frequency assignment in the bands 47.2-47.5 GHz and/or
47.9-48.2 GHz for a transmitting station in the fixed service which is
part of a high altitude platform network as defined by No. **1.66A**, it
shall request and effect coordination with other administrations with
frequency assignments for existing or planned space stations in any
frequency band in which the high altitude platform station network is to
operate;

3 that any administration requesting coordination pursuant to
*resolves* 2 above shall send its request to the Bureau, together with
the appropriate information listed in Appendix **4**;

4 that any administration having received a request for coordination
made under *resolves* 2 above shall promptly examine the matter with
regard to interference which may be caused to its own assignments, using
relevant ITU‑R Recommendations for guidance on interference calculation
methods and criteria;

5 that if, following its action under *resolves* 4 above, the
administration with which coordination was sought under *resolves* 2
does not agree to the request for coordination, it shall, within four
months of the date of publication of the BR IFIC under No. **9.38**,
inform the requesting administration of its disagreement, and shall
provide information concerning its own assignments upon which that
disagreement is based, including suggestions as it is able to offer with
a view to satisfactory resolution of the matter, to the requesting
administration with a copy to the Bureau;

6 that Nos. **9.53** through **9.55** and Nos. **9.58** and **9.59**
shall apply or be applied, as appropriate, to coordination activities
initiated pursuant to this Resolution;

7 that an administration having received a request for coordination made
under *resolves* 2 above, but having not responded in the manner
provided in *resolves* 5 above, shall be regarded as unaffected,

instructs the Director of the Radiocommunication Bureau

1 to treat complete coordination information provided to it under
*resolves* 3 above in the manner in which No. **9.34** directs the
Bureau to treat complete information sent under No. **9.30** or
No. **9.32**;

2 to apply No. **9.40A** if the information provided to it under
*resolves* 3 above is found to be incomplete.

**Reasons:** Incorporates into a new resolution the coordination
provisions in Article 9 that are not already applicable by operation of
regulation to HAPS stations in the fixed service in the 47.2-47.5 GHz
and 47.9-48.2 GHz bands.

#### Agenda item 1.9

1.9 to review the technical, operational and regulatory provisions
applicable to the use of the band 2 500-2 690 MHz by space services in
order to facilitate sharing with current and future terrestrial services
without placing undue constraint on the services to which the band is
allocated

Proposals for Agenda item 1.9

Background information

The band 2 500-2 690 MHz is allocated to terrestrial and satellite
services. The terrestrial services allocations include mobile and fixed
services (including IMT-2000). Both services have been rapidly evolving
to encompass high speed mobile Internet access requiring sensitive
receiving equipment some of which are highly susceptible to
interference.

WRC‑03 recognized that there may be a need to revise technical,
operational and regulatory provisions applicable to the space services
in the band to accommodate the implementation of new innovative
technologies in the fixed and mobile services. To that end, WRC‑03
developed and included this issue for consideration by WRC‑07 (see
Agenda item 1.9). Technical, operational and regulatory provisions
applicable to the use of the band 2500-2690 MHz by the following space
services are to be reviewed:

-- The fixed-satellite service which is subject to footnote 5.415 for
the use of the bands 2 500-2 690 MHz in Region 2 and 2 500-2 535 MHz and
2 655-2 690 MHz in Region 3, with the following condition of interest to
Region 2:

1\) The use is limited to national and regional systems, subject to
agreement obtained under No. 9.21, giving particular attention to the
broadcasting-satellite service in Region 1. In the direction
space-to-Earth, the power flux-density at the Earth's surface shall not
exceed the values given in Table 21-4.

-- The mobile-satellite service which is subject to footnotes 5.351A,
5.403, 5.407, 5.414, 5.419 and 5.420, with the following conditions of
interest to Region 2:

1\) The use of the bands 2 500-2 520 MHz and 2 670-2 690 MHz refers to
Resolutions 212 (Rev.WRC‑97) and 225 (WRC‑2000).

2\) The band 2 520-2 535 MHz (until 1 January 2005, the use of the band
2 500-2 535 MHz) may also be used for Earth-to-space (except
aeronautical mobile-satellite) and is limited to within national
boundaries. The use is subject to agreement obtained under No. 9.21. The
provisions of No. 9.11A apply.

3\) The band 2 655-2 670 MHz (until 1 January 2005, the band 2 655-2
690 MHz) may also be used for Earth-to-space (except aeronautical
mobile-satellite) and is limited to within national boundaries. This use
is subject to agreement obtained under No. 9.21 and the provisions of
No. 9.11A apply.

4\) After 1 January 2005, the allocation of the band 2 500-2 520 MHz
shall be effective for space-to-Earth and is subject to coordination
under No. 9.11A

5\) After 1 January 2005, the allocation of the band 2 670-2 690 MHz
shall be effective. When introducing systems in this band,
Administrations shall take all necessary steps to protect the satellite
systems operating in this band prior to 3 March 1992. The coordination
shall be in accordance with No. 9.11A.

6\) In the band 2 500-2 520 MHz, the power flux-density at the surface
of the Earth from space stations operating from space-to-earth shall not
exceed −152 dB(W/(m^2^ ∙ 4 kHz)) in Argentina, unless otherwise agreed
by the administrations concerned.

-- The aeronautical mobile-satellite service which is subject to
footnotes 5.415A and 5.420A.

-- The broadcasting-satellite service which is subject to footnotes
5.416, 5.418, 5.417A, 5.417B, 5.417C, 5.417D, 5.418A, 5.418B, and 5.418C
with the following condition of interest to Region 2:

1\) The use of the band 2 520-2 670 MHz by the broadcasting-satellite
service is limited to national and regional systems for community
reception, subject to agreement obtained under No. 9.21.

-- The radiodetermination-satellite service which is subject to footnote
5.404.

Within the terrestrial mobile service, the use of the band by IMT-2000
is subject to footnote 5.384A. This band is identified for use by
administrations wishing to implement IMT-2000 in accordance with
Resolution 223 (WRC‑2000).

There are concerns that terrestrial service may suffer constraints, such
as reduction of cell coverage, a consequential increase in the number of
base stations and the cost of infrastructure that may have a large
economic impact.

Regarding CITEL activities, PCC.II/Recommendation 8 (IV-04) was approved
in the IV meeting of PCC II, in December 2004. This Recommendation
establishes the following frequency arrangement for IMT-2000 in the band
2 500-2 690 MHz, among others, noting that there is no intention to
implement MSS in this band:

Administrations in Region 2 are planning for implementation of
terrestrial services in the 2 500-2 690 MHz band. There are no known
plans to provide MSS in Region 2.

**ADD** IAP/14A2/38

RESOLUTION \[IAP/14A2/38\] (WRC‑07)

Transitional measures for application of Article 21 provisions\
in the band 2 500-2 690 MHz

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that WRC‑07 revised the limits of power flux-density from space
stations in Article **21**, Table **21-4** for the band 2 500-2 690 MHz;

*b)* that use of the bands 2 500-2 690 MHz in Region 2 and
2 500-2 535 MHz and 2 655-2 690 MHz in Region 3 by the fixed
satellite-service is limited to national and regional systems, subject
to agreement obtained under No. **9.21** (see No. **5.415** and
No. **5.2.1**);

*c)* that in the band 2 520-2 670 MHz, the broadcasting-satellite
service is limited to national and regional systems, subject to
agreement obtained under No. **9.21** (see No. **5.416** and
No. **5.2.1**);

*d)* that in the band 2 520-2 535 MHz, the mobile-satellite service
(space-to-Earth) is limited to within national boundaries, subject to
agreement obtained under No. **9.21** and application of the provisions
of No. **9.11A** (see No. **5.403**);

*e)* that, in No. **5.384A**, the 2 500-2 690 MHz band is identified for
use by administrations wishing to implement International Mobile
Telecommunications-2000 (IMT-2000) in accordance with Resolution **223
(WRC‑2000)**;

*f)* that due to the unique national and regional limitations applied to
certain space services and the identification for use by administrations
wishing to implement IMT‑2000, it is advantageous to apply the revised
Article **21**, Table **21-4** limits in the band 2 500-2 690 MHz at an
early date,

recognizing

1 that in the 2 500-2 690 MHz band, several administrations in all three
Regions implemented or plan to implement advanced wireless terrestrial
services exclusively;

2 that in the 2 500-2 690 MHz band, some administrations deployed or
plan to deploy satellite networks;

3 that in the cases of national or regional satellite systems described
in *considerings b)*, *c)*, and *d)*, the service area can include the
territories of administrations only with the explicit agreement from
those administrations;

4 that in frequency bands below 3 GHz, the satellite networks inherently
have a wide geographic coverage that may extend beyond the intended
service area;

5 that in the band 2 500-2 690 MHz, ITU‑R concluded, on the basis of
certain assumptions, that it is not technically feasible to operate
mobile-satellite service systems and terrestrial services systems on
co-frequency basis in the same geographical area;

6 that applying power flux-density limits to the band 2 500-2 690 MHz
alleviates the uncertainty of the coordination process;

7 that expedited transition to the revised power flux-density limits in
the band 2 500-2 690 MHz adopted by WRC‑07 would facilitate deployment
of commercially viable advanced wireless networks and is necessary due
to the unique national and regional limitations applied to certain space
services,

resolves

1 that the power flux-density at the Earth's surface produced by
emissions from space stations in the 2 500-2 690 MHz band by the
fixed-satellite service, the 2 520-2 670 MHz band by the
broadcasting-satellite service, and the 2 500-2 516.5 MHz band by the
radiodetermination-satellite service for which complete notification
information has been received by the Radiocommunication Bureau before
17 November 2007, and whose frequency assignments in the 2 500-2 690 MHz
band were brought into use by 31 December 2008 shall not exceed the
following values:

--152 dB(W/m^2^) for \< 5°

--152 + 0.75(δ -- 5) dB(W/m^2^) for 5° ≤ δ ≤ 25°

--137 dB(W/m^2^) for δ \> 25°

in any 4 kHz band, where δ is the angle of arrival above the horizontal
plane and the limits in Table **21‑4** do not apply;

2 that the coordination thresholds in Table 5-2 of Annex 1 to
Appendix **5** of the Radio Regulations (Edition of 2004), in
conjunction with the applicable provisions of Articles **9** and **11**
of the Radio Regulations associated with No. **9.11A**, shall apply to
mobile-satellite service systems and networks in the band
2 500-2 535 MHz for which complete notification information has been
received by the Radiocommunication Bureau before 17 November 2007, and
whose frequency assignments in the 2 500-2 690 MHz band were brought
into use by 31 December 2008 and the limits in Table **21-4** do not
apply,

instructs the Radiocommunication Bureau

as of the end of WRC‑07, to observe the above *resolves* when examining
frequency assignment notices received from administrations.

**Reasons:** To establish regulatory provisions specifying transition to
the revised power flux-density limits in Article 21 for the
2 500-2 690 MHz band.

#### Agenda item 1.10

1.10 to review the regulatory procedures and associated technical
criteria of Appendix **30B** without any action on the allotments, the
existing systems or the assignments in the List of Appendix **30B**

Proposals for Agenda item 1.10

Background information

As stated in § 1.1 of Appendix 30B the objective of the Plan "is to
guarantee in practice, for all countries, equitable access to the
geostationary-satellite orbit in the frequency bands of the
fixed-satellite service covered by this Appendix". While the plan has
been in force for some 18 years, little use has been made of the
precious spectrum (1 600 MHz) regulated by this appendix, particularly
as compared to the other bands allocated globally to the FSS. Moreover,
numerous administrations have complained that the technical parameters
are outdated and the procedures are difficult to apply and are
exceedingly time-consuming to apply. For these reasons, administrations
agreed to include consideration of this matter on the agenda for WRC‑07.
Several ITU‑R preparatory meetings (including WP 4A and the Special
Committee) as well as regional bodies have been studying the related
issues for several years.

Taking the foregoing into consideration, it is considered that the
conditions for the use the Appendix 30B frequencies can be improved and
optimized for ITU Member States that want to implement their allotments.
Simplified procedures for additional systems have been addressed as
well. The proposed modifications to the regulatory procedures in
Articles 6, 7 and 8 are premised upon the adoption of a "non-sequential"
process in which the PDA concept is not retained. A proposed new
category called "Additional Systems" that incorporates both former
"Additional Uses" and "Sub-regional Systems" serves to greatly simplify
regulatory procedures of Article 6 thereby allowing the multiple
regulatory procedures to be combined into a single procedure based upon
the old Section II of Article 6.

\* *Editorial Note:* For the convenience of the reader, the proposal
presented here includes in most cases text proposed for no change (NOC)
as well as text proposed for suppression (SUP).

APPENDIX 30B (Rev. WRC-2000)

Provisions and associated Plan for the fixed-satellite service\
in the frequency bands 4 500-4 800 MHz, 6 725-7 025 MHz,\
10.70-10.95 GHz, 11.20-11.45 GHz and 12.75-13.25 GHz

ARTICLE 1

Objective of the provisions and associated Plan

**NOC** IAP/14A2/39

1.1 The objective of the procedures prescribed in this Appendix is to
guarantee in practice, for all countries, equitable access to the
geostationary-satellite orbit in the frequency bands of the
fixed-satellite service covered by this Appendix.

**MOD** IAP/14A2/40

1.2 The procedures prescribed in this Appendix shall in no way prevent
the implementa­tion of assignments in conformity with the allotments of
the Plan.

**Reasons:** Consequential to elimination of Part B from the Plan.

ARTICLE 2

Definitions

**NOC** IAP/14A2/41

2.1 *Conference:* World Administrative Radio Conference on the Use of
the Geostationary-Satellite Orbit and the Planning of Space Services
Utilizing It, First Session, Geneva, 1985; Second Session, Geneva, 1988.

**MOD** IAP/14A2/42

2.2 *Plan:* The Plan for the fixed-satellite service in the frequency
bands contained in this Appendix, consisting of national allotments.

**Reasons:** Existing systems are associated with FSS satellite networks
that had already been submitted to the ITU BR when the Plan was
developed. By now, the frequency assignments in these networks have
either been brought into use and have become assignments in the List of
Appendix 30B or have been cancelled. Therefore there is no need for
keeping the concept of Part B of the Plan.

**MOD** IAP/14A2/43

2.3 *Allotment:* For the purpose of this Appendix, an allotment
comprises:

-- a nominal orbital position;

-- a bandwidth of 800 MHz (up-link and down-link) in the frequency bands
listed in Article 3 of this Appendix;

-- a service area for national coverage.

**Reasons:** The generalized parameters are not considered to be
necessary since examination of the compatibility of any proposed
assignment with allotments in the Plan or assignments in the List can be
conducted without calculating such parameters. As discussed and
justified in connection with Article 6, a non-sequential processing of
submissions is being proposed here and such approach is not compatible
with retention of the PDA concept.

**MOD** IAP/14A2/44

2.4 *Existing systems:* Those satellite systems in the frequency bands
covered by this Appendix , which are identified in
Resolution **\[IAP/14A2/154\] (WRC‑07)**.

**Reasons:** Existing systems are now either assignments in the List or
they have been cancelled.

**SUP** IAP/14A2/45

2.5

**Reasons:** Subregional systems are now considered as "additional
systems" together with conversions of allotments into assignments and
modifications of assignments in the List under a single consolidated
procedure in Article 6 of Appendix 30B.

**MOD** IAP/14A2/46

2.6 *Additional* *system:* For the application of the provisions of this
Appendix, additional systems shall be understood to be systems for which
the assignments, notified by an administration, are not the result of
conversion of an allotment into assignments. An additional system may
also be submitted on behalf of a group of named administrations with one
designated administration to act as the notifying administration in
respect of ITU.

**Reasons:** Definition of the new category of "additional systems"
covers both former "additional uses" and former "subregional systems".
The concepts of subregional systems and additional uses have been
introduced in the Appendix 30B Plan with different motivations. In
particular, subregional systems intended to allow neighbouring countries
to combine their allotments into a system with regional coverage. For
that reason, the possibility of suspending allotments was associated
with subregional systems. However, up to now the submissions for
subregional systems have seldom if ever included requests for suspension
or partial suspension of allotments and such submissions have been
implemented in a way that does not affect allotments in the Plan or
assignments in the List. Therefore, subregional systems have actually
been implemented as "additional uses" in the sense that they will
coexist with allotments and assignments as additional

uses have. In view of the above, it is proposed to eliminate the
category of subregional systems and to have a new and more simplified
definition for "additional system", capable of accommodating
requirements currently being met by the two existing categories.

**ADD** IAP/14A2/47

2.7 Whenever, under § 2.6, an administration acts on behalf of a group
of named administrations, all members of that group retain the right to
respond in respect of their own networks or systems.

**Reasons:** Gives administrations participating in an "additional
system" providing multi-national services, equal rights with respect to
their own networks.

**ADD** IAP/14A2/48

2.8 *List of assignments (hereafter called, in short, the "List"):* The
List associated with the Plan contains assignments resulting from the
successful application of the provisions of Article 6 of
Appendix **30B** or the application of Resolution** \[IAP/14A2/154\]
(WRC‑07)**.

**Reasons:** Consequential to the revision of the provisions of
Article 6 and the treatment of former Part B "existing systems" under
Resolution \[IAP/14A2/154\] (WRC‑07).

**NOC** IAP/14A2/49

ARTICLE 3

Frequency bands

**Reasons:** Article 3 does not need to be changed because the frequency
bands subject to Appendix 30B will remain the same.

**NOC** IAP/14A2/50

ARTICLE 4

Execution of the provisions and associated Plan

**Reasons:** Article 4 should be retained as it is because it conveys
the general idea of operation with the characteristics of the Plan
(§ 4.1 of Article 4) and at the same time refers to the possible
exceptions contemplated in Appendix 30B itself or elsewhere in the Radio
Regulations.

**SUP** IAP/14A2/51

ARTICLE 5     (WRC-03)

The Plan and the associated List of assignments

**Reasons:** The predetermined arc (PDA) concept is not pertinent under
the example offered for consideration in this document. Additionally,
material relating to List of Assignments has been transferred to
Article 2 containing definitions.

**MOD** IAP/14A2/52

{*Editorial Note:* Given the simplifications introduced in the previous
Articles, namely elimination of Part B and merger of the categories
"subregional systems" and "additional uses", Article 6 can be
significantly shortened. Accordingly, sections I, IA, IB and III are
suppressed and a new, consolidated, single procedure is shown as a
revision to section II. For simplicity, wherever entire sections of text
have been deleted, they are shown as suppressed but without showing the
entire text stricken.}

ARTICLE 6     (Rev.WRC-03)

**SUP** IAP/14A2/53

Procedures for implementation of the Plan and regulation of\
the fixed-satellite service in the planned bands**^1^**     (WRC-03)

**Reasons:** The new single procedure needs only a single heading. The
new heading for a revised Section II of Article 6 can be applied to all
of Article 6.

**SUP** IAP/14A2/54

Section I -- Procedure for conversion of an allotment into an assignment

**Reasons:** Consequential to suppression of all sections of Article 6
except for Section II which is used as the basis for a new single
consolidated regulatory procedure.

**SUP** IAP/14A2/55

Section IA -- Procedure for conversion of an allotment into an
assignment that is not in conformity with Part A of the Plan or that
does not comply with Annex 3B

**Reasons:** Consequential to suppression of all sections of Article 6
except for Section II, which is used as the basis for a new single
consolidated regulatory procedure.

**SUP** IAP/14A2/56

Section IB -- Procedure for recording in the List of the existing
systems\
contained in Part B of the Plan

**Reasons:** This section is now irrelevant. Satellite systems in Part B
of the Plan have either been brought into use and have become
assignments in the List of Appendix 30B or have been cancelled and thus
Part B of the Plan is empty. "Existing systems" in § 2.4 of Article 2
are now covered by Resolution \[IAP/14A2/154\] (WRC‑07).

**MOD** IAP/14A2/57

Procedure for the conversion of an allotment into an assignment, for the
introduction of an additional system or for the modification\
to an assignment in the List^1,^ [^3]

**Reasons:** The new title of the new consolidated regulatory procedure
is the title of a revised Article 6.

**MOD** IAP/14A2/58

6.1 When an administration intends to convert an allotment into an
assignment (with or without modifications to the allotment in the Plan)
or when an administration, or one acting on behalf of a group of
administrations, intends to introduce an additional subregional system
or modify characteristics of assignments in the List for a system that
has been brought into use, it shall, not earlier than eight years and
not later than two years before the planned date of bringing into use,
send to the Bureau the information specified in Appendix **4**.

**Reasons:** The text clearly identifies the three scenarios under which
it applies: a) conversion of an allotment with or without modifications
to the allotment in the Plan; b) additional system; and c) modification
of assignments in the List for systems that were brought into use. The
qualification imbedded in the latter case c) "\...that has been brought
into use\..." is considered very important in that it ensures that the
eight year system implementation time limit is observed. Note that
modifications to the initial Appendix 4 information as the result of
coordination consultations, not to be confused with case c) above, is
dealt elsewhere under this Article (please see ADD 6.17 and subsequent
provisions on this issue.)

**ADD** IAP/14A2/59

6.2 If the information received by the Bureau under § 6.1 is found to be
incomplete, the Bureau shall immediately seek from the administration
concerned any clarification required and information not provided.

**Reasons:** To provide the Bureau with the ability to request
administrations to provide information missing from incomplete notices.
This process serves the same purpose in ensuring an efficient process of
examination of notices by the Bureau as that of § 11.27 of Article 11.

**SUP** IAP/14A2/60

§ **6.39** through **6.42**

**MOD** IAP/14A2/61

6.3 Upon receipt of a complete (Appendix **4**) notice relating to the
proposed assignment, the Bureau shall examine the notice as to its
conformity with the Table of Frequency Allocations and any other
provisions^ADD\ 6.1^ of these Regulations, except those provisions
relating to conformity with the fixed-satellite service Plan.

**ADD** IAP/14A2/61A

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^ADD\ 6.1^ The "other provisions" shall be identified and included in
the Rules of Procedure.

**ADD** IAP/14A2/62

6.4 BR will then identify those administrations whose territory has been
included in the service area of the system submitted under § 6.1. The
notifying administration shall seek the agreement of any administration
whose territory is partially or wholly included in the intended service
area of the system.

**Reasons:** The intentional inclusion in the service area of a system
of territories other than those of the notifying administration is
understood to clearly signify the intent of the notifying administration
to establish services in such territories. Consequently it is reasonable
that the notifying administration seeks the agreement of the
administration whose territory is partially or wholly included in the
system's intended service area. To facilitate consultations and to
facilitate efficient processing by the Bureau, this agreement need only
be submitted to the Bureau at the time the notifying administration
submits its request to the Bureau for inclusion of its assignments in
the List.

**ADD** IAP/14A2/63

6.5 When the examination with respect to § 6.3 leads to an unfavourable
finding, the notice shall be returned to the notifying administration
with an indication of the appropriate action.

**Reasons:** Follows directly from the application of § 6.3. It is
proposed that the consequence of an unfavourable finding be similar to
that of Article 11.

**ADD** IAP/14A2/64

6.6 When the examination with respect to § 6.3 leads to a favourable
finding, the Bureau shall use the method of Annex 4 to determine
administrations whose:

-- allotments in the Plan; *or*

-- assignments which appear in the List; *or*

-- assignments for which the Bureau has previously received complete
information in accordance with this Article,

are considered as being affected.

**Reasons:** Follows directly from the application of MOD IAP/14A2/61.
Simplified as a result of equal treatment of allotments, assignments in
the List and those systems for which the Bureau has previously received
complete information.

**ADD** IAP/14A2/65

6.7 The Bureau shall publish, in a Special Section of its International
Frequency Information Circular (BR IFIC), the complete information
received under § 6.1, together with the names of the administrations
identified under § 6.4 and § 6.6 and the corresponding allotments in the
Plan, assignments in the List, assignments for which the Bureau has
previously received complete information in accordance with this
Article.

**Reasons:** The Bureau maintains transparency in the process of its
examinations by publishing the results of its examination for all ITU
Members to view and to verify. This is a necessary provision of
information that would be normally expected by any affected
administration.

**ADD** IAP/14A2/66

6.8 The Bureau shall immediately send the results of its examination to
the administration proposing the assignment, drawing attention to the
requirement to seek and obtain the agreement of those administrations
whose national territory is included in the service area of the system,
or whose allotments are considered affected.

**Reasons:** There is a requirement to highlight two cases of identified
administrations. Firstly, the case of administrations whose territories
have been included in the service area of a system and secondly those
whose allotments in the Plan or assignments resulting from the
conversion of allotments are considered affected, on the basis of
Annex 4 of Appendix 30B criteria. Clearly, in these two cases it is
incumbent upon the notifying administration to initiate and conclude the
bilateral consultations in seeking the agreement of the affected
administration(s) and not the responsibility of the affected
administration(s) to react within set time frames in order to claim
protection. Consequently, a provision such as ADD IAP/14A2/66 greatly
clarifies for the notifying administration the requirements to obtain
these agreements by the time it submits to the Bureau its request for
inclusion of its assignments in the List.

**ADD** IAP/14A2/67

6.9 The Bureau shall also send a telegram/fax to the administrations
listed in the Special Section of the BR IFIC drawing their attention to
the information it contains and shall send them the results of its
examination.

**Reasons:** Follows directly from ADD IAP/14A2/65. This communication
is a necessary provision of information that would be normally expected
by any affected administration.

**ADD** IAP/14A2/68

6.10 Comments from affected administrations on the information published
pursuant to § 6.7 shall be sent to the administration proposing the
assignment with a copy to the Bureau within a period of four (4) months
following the date of its publication in the BR IFIC.

**Reasons:** The identified (affected) administration fulfils its
obligation to reply to the administration proposing the assignment
within a four (4) month regulatory time-frame while Bureau is kept
apprised of consultations in the event that their assistance is
requested by one of the parties.

**ADD** IAP/14A2/69

6.11 Thirty days prior to the expiry of the same four-month period, the
Bureau shall dispatch a reminder telegram or fax to an administration
which has not made its comments under § 6.10, bringing the matter to its
attention.

**Reasons:** Courtesy to administration and a fail-safe in the event
that the administration was not aware that they were affected for
whatever reason.

**ADD** IAP/14A2/70

6.12 An administration which considers that it should have been
identified in the publication referred to under § 6.7 above shall,
within four (4) months of the date of publication of its relevant
BR IFIC, and identifying the affected allotment, assignment or proposed
assignment, request the Bureau to include its name in the publication.
The Bureau shall study this information on the basis of Annex 4 and
shall inform both administrations of its conclusions. Should the Bureau
agree to the administration's request, it shall publish an addendum to
the publication under § 6.7.

**Reasons:** Provides administrations with recourse to demonstrate that
it should have been included in the Bureau's original list of affected
administrations and the opportunity to enter into a coordination
exercise.

**ADD** IAP/14A2/71

6.13 An administration, other than an administration identified under
§ 6.4 or whose allotment in the Plan or assignment resulting from the
conversion of an allotment has been considered to be affected under
§ 6.6, that has not submitted its comments either to the administration
seeking agreement or to the Bureau within a period of four months
following the date of its BR IFIC referred to in § 6.7 shall be deemed
to have agreed to the proposed assignment.

**Reasons:** The onus is on the affected administration to act within
the 4-month regulatory time-frame to ensure inclusion in the
coordination process, except for the specific situations described in
this provision.

**ADD** IAP/14A2/72

6.14 After expiry of the deadline for comments in respect of the
proposed assignment, the Bureau shall, according to its records, publish
a Special Section indicating the list of administrations whose
agreements are required for completion of the Article 6 procedure.

**Reasons:** Finalizes the determination of the list of affected
administrations in the four (4) month regulatory time-frame.

**ADD** IAP/14A2/73

6.15 If agreements have been reached with administrations identified in
accordance with § 6.14, the administration proposing the new or modified
assignment may request the Bureau to have the assignment entered into
the List, indicating the final characteristics of the frequency
assignment together with the names of the administrations with which
agreement has been reached. For this purpose, it shall send to the
Bureau the information specified in Appendix **4**. In submitting the
notice, the administration may request the Bureau to examine the notice
simultaneously under § 6.18, 6.20, 6.21 and 6.22 (entry into the List)
and § 8.7 and 8.8 (notification).

**Reasons:** Corollary to § 6.14 stating the procedure to be followed by
administrations for new or modified assignments where agreements with
administrations have been reached. It is more efficient for the Bureau
to examine notices simultaneously under all the subsequent provisions
listed if the requirements for those provisions have also been
fulfilled.

**ADD** IAP/14A2/74

6.16 If the information received by the Bureau under § 6.15 is found to
be incomplete, the Bureau shall immediately seek from the administration
concerned any clarification required and information not provided.

**Reasons:** Provides the Bureau with the ability to request
administrations to provide, information missing from incomplete notices.
This process serves the same purpose in ensuring an efficient process of
examination of notices by the Bureau as that of § 11.27 of Article 11.

**ADD** IAP/14A2/75

6.17 If, in seeking agreement, an administration modifies its initial
notice, it shall again apply the provisions of § 6.1 and the consequent
procedure with respect to any other administration whose services might
be affected as a result of modifications to the initial notice.
Examination under § 6.6 shall include consideration of allotments in the
Plan, assignments in the List and assignments for which the Bureau has
previously received complete information in accordance with this
Article. For submissions for which the Bureau has received the complete
information in the intervening period between the dates of receipt of
the initial and modified notices, examination shall be made so as to
ensure that the corresponding assignments do not suffer more
interference from the modified notice.

**Reasons:** Specifies the procedure to be followed by an administration
and the regulatory treatment to be applied by the Bureau when an
administration modifies its initial notice. Also ensures that
submissions received after prior submissions are not adversely affected
if those prior submissions are subsequently modified.

**ADD** IAP/14A2/76

6.18 Upon receipt of a complete (Appendix **4**) notice relating to the
proposed assignment, the Bureau shall examine any modification to the
initial notice as to its conformity with respect to the Table of
Frequency Allocations and the other provisions[^4]^DD\ 6.22^ of these
Regulations, except those provisions relating to conformity with the
fixed-satellite service Plan.

**Reasons:** The Bureau ensures that only the basic requirements of a
complete notice are met in the case of modifications to an initial
notice. Deferring examination of a notice with respect to conformity to
the Plan allows notices to be processed in parallel instead of waiting
for the Bureau to complete its examination of all notices received in a
serial manner.

**ADD** IAP/14A2/77

6.19 When the examination with respect to § 6.18 leads to an
unfavourable finding, the notice shall be returned to the notifying
administration with an indication of the appropriate action.

**Reasons:** Follows directly from the application of § 6.18. It is
proposed that the consequence of an unfavourable finding be similar to
that of Article 11.

**ADD** IAP/14A2/78

6.20 When the examination of all or parts of the modifications with
respect to § 6.18 leads to a favourable finding, the Bureau shall use
the method of Annex 4 with respect to the relevant part of the notice to
examine if the affected administrations and the corresponding:

-- allotments in the Plan;

-- assignments which appear in the List;

-- assignments for which the Bureau has previously received complete
information in accordance with this Article,

indicated in the Special Section published under § 6.14 and whose
agreement has not been reached under § 6.15 are still considered as
being affected by the modifications to the notice.

**Reasons:** Follows directly from the application of MOD IAP/14A2/76.
Simplified as a result of equal treatment of allotments, assignments in
the List and those systems for which the Bureau has previously received
complete information.

**ADD** IAP/14A2/79

6.21 The Bureau shall further examine each notice, or parts of a notice
with a favourable finding in accordance with § 6.18 with respect to
§ 6.17 to identify administrations whose allotments in the Plan,
assignments in the List and/or submissions for which the Bureau has
previously received complete information in accordance with this
Article are identified as affected as a result of the modifications to
the initial notice.

**Reasons:** This provision ensures that the Bureau will make a
determination based on its examination as to whether modifications to
initial notices affect other allotments, assignments in the List and/or
submissions for which the Bureau has previously received complete
information.

**ADD** IAP/14A2/80

6.22 The Bureau shall further examine each notice, or parts of a notice
with a favourable finding with respect to the requirement for the
notifying administration to seek the agreement of those administrations
whose territories are partially or wholly included in the intended
service area of the system.

**Reasons:** This provision specifies that the Bureau defer its
determination of a favourable or unfavourable finding until a later time
(just prior to notification under Article 8 and within the regulatory
time limit) thus allowing the notifying administration to obtain the
necessary agreements from affected administrations. This provision also
guarantees that the sovereign rights of administrations with respect to
their own territories. Furthermore, this provision allows notices to be
processed in parallel instead of waiting for the Bureau to complete its
examination of all notices received in a serial manner.

**SUP** IAP/14A2/81

6.43*bis*

**Reasons:** Under the set of proposals for simultaneous treatment of
notices received in the "non-sequential" processing of notices,
§ 6.43*bis*, detailing the conditions under which networks may be
processed simultaneously, is irrelevant and may therefore be suppressed.

**MOD** IAP/14A2/82

6.23 In the event of a favourable finding with regard to compatibility
under § 6.20, 6.21 and 6.22, the Bureau shall enter the proposed
assignment in the List and publish in a Special Section to its BR IFIC,
the characteristics of the assignment received under § 6.15 together
with the names of administrations with which the provisions of this
Article have been successfully applied. The administration may then
notify the assignment in accordance with Article 8.

**Reasons:** Specifies the consequences in terms of Bureau action and
the rights of administrations in the case of a favourable finding.

**ADD** IAP/14A2/83

6.24 When the examination under § 6.21 and 6.22 leads to an unfavourable
finding, the Bureau shall publish in a Special Section of its BR IFIC
the information received under § 6.15 together with the names of any
administrations with which the provisions of this Article have been
successfully applied as well as the administrations with which they have
not. Upon completion of the remaining coordination requirements, the
notifying administration may again apply the procedures starting with
§ 6.15.

**Reasons:** Specifies the consequences in terms of Bureau action and
the rights of administrations in the case of an unfavourable finding.

**ADD** IAP/14A2/84

6.25 After a notice is published under § 6.24, should the notifying
administration resubmit the notice and insist upon its reconsideration,
the Bureau, on condition that all the required agreements with
administrations identified under § 6.4 or whose allotment in the Plan or
assignment resulting from the conversion of an allotment has been
considered to be affected under § 6.6 have been obtained, shall enter
the assignments provisionally in the List with an indication of those
administrations whose assignment(s) were the basis of the unfavourable
finding[^5]^DD\ 6.29^. The entry shall be changed from provisional to
definitive recording in the List only if the Bureau is informed that the
new assignment has been in use, together with the assignment(s) which
was the basis for the unfavourable finding, for at least four (4) months
without any complaint of harmful interference.

**Reasons:** Allows administrations, having received unfavourable
findings, to have such networks, upon reconsideration, to be
provisionally recorded as an assignment. If after four (4) months in
use, the assignment has received no complaint of harmful interference,
the entry in the List can be changed to definitive. In the case of the
footnote (ADD 6.29), a finding can be definitive if the network only
receives interference in excess of the limits as specified in the Plan
since no other administration is affected by interference caused by the
network.

**SUP** IAP/14A2/85

**6.45**-**6.53**

**Reasons:** These regulatory procedures (§ 6.45 to § 6.53) are no
longer relevant given the proposed new Article 6 regulatory procedures
and thus they can be suppressed.

**MOD** IAP/14A2/86

6.26 When a frequency assignment included in the List is no longer
required, the notifying administration shall immediately inform the
Bureau.

**Reasons:** Consequential to the proposed new single regulatory
procedure in Article 6. Eliminates the need to specifically identify
subregional systems.

**ADD** IAP/14A2/87

6.27 The date of bringing into use may be extended by the notifying
administration up to no more than eight years from the date of receipt
by the Bureau of the complete Appendix **4** under § 6.1.

**Reasons:** Makes it clear that under the proposed single regulatory
procedure, all submissions have up to eight years (including any
requested extension of the bringing into use date) to be brought into
use.

**ADD** IAP/14A2/88

6.28 When:

-- an assignment is no longer required; *or*

-- a frequency assignment recorded in the List and brought into use has
been suspended for a period of two years; *or*

-- a frequency assignment recorded in the List has not been brought into
use within the eight year period following the receipt by the Bureau of
the relevant complete information under § 6.1, with the exception of
national systems submitted by new Member States where § 6.30 applies;
*or*

-- a proposed new or modified frequency assignment has not fulfilled all
the requirements for entering the List, in accordance with § 6.23 or
§ 6.25, by the expiry date specified in § 6.27 the Bureau shall:

*a)* publish in a Special Section of its BR IFIC the cancellation of the
related Special Sections and/or circular telegrams, as appropriate, and
of the assignments recorded in the Appendix **30B** List;

*b)* reinstate the allotment in the Appendix **30B** Plan, if
appropriate;

*c)* update the reference situation for the allotments of the Plan and
the assignments of the List;

*d)* if the cancelled assignment is the result of the conversion of an
allotment with modifications, reinstate the allotment with the same
orbital location and technical parameters of the cancelled assignment
except for its service area that shall be the national territory of the
administration whose allotment is being reinstated.

**Reasons:** Specifies the consequential actions to be taken by the
Bureau under the specified set of circumstances under which the
frequency assignment: 1) is no longer required, 2) has not been brought
into use, 3) nor will it be brought into use. The exception for national
systems submitted by new Member States is clearly stated.

**ADD** IAP/14A2/89

6.29 The procedure of this Article may be applied by the administration
of a new ITU Member State in order to include new assignments in the
List. Upon completion of the procedure, the next World
Radiocommunication Conference may be requested to consider, among the
assignments included in the List after the successful completion of this
procedure, the inclusion in the Plan of a new allotment over the
national territory of the new Member State.

**Reasons:** Specifies that the proposed new single regulatory procedure
in Article 6 is applicable to new ITU Member States seeking to establish
new assignments in the List. Also specifies that new allotments for new
Member States will be subject to consideration at a subsequent World
Radiocommunication Conference.

**ADD** IAP/14A2/90

6.30 Should the assignments mentioned in § 6.29 over the national
territory of the administration not be brought into use within the eight
years following the receipt by the Bureau of the relevant complete
information under § 6.1, they would be retained in the List until the
end of the World Radiocommunication Conference immediately following the
successful completion of the procedure referred to in § 6.29, and
thereafter shall be converted to a national allotment specified by its
generalized parameters for inclusion in the Plan and deletion of the
associated assignments recorded in the List.

**Reasons:** The Plan, being a Plan of national allotments, needs to be
updated to account for and reflect geopolitical changes that take place
over time. New Member States should be afforded entry(ies) in the Plan
according to the provisions of this Appendix. It is therefore reasonable
that following the successful completion of these procedures, even if
the new Member State is unable to meet the eight year implementation
time-frame, the results of the successful application of the procedures
of this Appendix are captured and recorded in the Plan. This approach
would allow for the equitable treatment of new and existing ITU Member
States.

**SUP** IAP/14A2/91

Section III -- Supplementary provisions applicable to additional uses\
in the planned bands

ARTICLE 7

Procedure for the addition of a new allotment to the Plan\
for a new Member State of the Union

**MOD** IAP/14A2/92

7.1 The administration of a country which has joined the Union as a new
Member State shall obtain a national allotment in the Plan by applying
the procedure of this Article.

**Reasons:** Consequential to elimination of Part B and renaming Part A
the "national allotments".

**NOC** IAP/14A2/93

7.2 The administration shall submit its request for an allotment to the
Bureau, with the following information:

*a)* the geographical coordinates of not more than 10 test points for
determining the minimal ellipse to cover its national territory;

*b)* the height above sea level of each of its test points and the rain
zone or zones;

*c)* any special requirement, other than a fixed orbital position, which
is to be taken into account to the extent practicable.

**MOD** IAP/14A2/94

7.3 Upon receipt of the complete information (mentioned in § 7.2 above),
the Bureau shall find an appropriate orbital position and shall enter
the national allotment of the new Member State of the Union in the Plan.

7.4 For this purpose the Bureau shall consult, and if necessary seek the
agreement of, any administrations that may be affected.

**Reasons:** Consequential to the adoption of a non-sequential
processing of submissions and the elimination of the PDA concept.

**NOC** IAP/14A2/95

ARTICLE 8     (WRC-03)

Procedure for notification and recording in the Master Register of\
assignments in the planned bands for the fixed-satellite service

**Reasons:** No change is proposed to the title of this Article.

**MOD** IAP/14A2/96

8.1 Any assignment for which the relevant procedure of Article 6 has
been successfully applied shall be notified to the Bureau using the
relevant characteristics listed in Appendix** 4**.     (WRC-03)

**Reasons:** Consequential to the proposal to defer findings with
respect to conformity to the Plan until just prior to notification. (See
reasons for § 6.22)

**MOD** IAP/14A2/97

8.2 If the first notice referred to in § 8.1 has not been received by
the Bureau within the eight-year period mentioned in § 6.1 of Article 6,
the assignments in the List shall no longer be taken into account by the
Bureau and administrations. The Bureau shall then act as if the
assignment in the List has not been brought into use in conformity with
§ 6.1 of Article 6. The Bureau shall inform the notifying
administration, three months in advance of the end of the eight-year
period, of the actions it intends to take.     (WRC-03)

**Reasons:** Changes are consequential of those introduced in Article 6.

**NOC** IAP/14A2/98

8.3 Notices not containing those characteristics specified in
Appendix **4** as mandatory or required shall be returned with comments
to help the notifying administration to complete and resubmit them,
unless the information not provided is immediately forthcoming in
response to an inquiry by the Bureau.     (WRC-03)

**Reasons:** § 8.3 reaffirms the need for Appendix 4 information to be
complete.

**SUP** IAP/14A2/99

8.4

**Reasons:** Suppression is consequential of the elimination of the PDA
concept.

**NOC** IAP/14A2/100

8.4 Complete notices shall be marked by the Bureau with their date of
receipt and shall be examined in the date order of their receipt.
Following receipt of a complete notice the Bureau shall, within not more
than two months, publish its contents, with any diagrams and maps and
the date of receipt, in the BR IFIC, which shall constitute the
acknowledgement to the notifying administration of receipt of its
notice. When the Bureau is not in a position to comply with the
time-limit referred to above, it shall periodically so inform the
administrations, giving the reasons therefor.     (WRC-03)

**Reasons:** No change is required. Formal acknowledgement of receipt of
notices by the Bureau is still needed regardless of the specific
procedures in Article 6.

**NOC** IAP/14A2/101

8.5 The Bureau shall not postpone the formulation of a finding on a
complete notice unless it lacks sufficient data to reach a conclusion
thereon.     (WRC-03)

**Reasons:** No change is being proposed. Consequential to renumbering
of Article 8 provisions.

**NOC** IAP/14A2/102

8.6 Each notice shall be examined:     (WRC-03)

**Reasons:** No change is being proposed. Consequential to renumbering
of Article 8 provisions.

**NOC** IAP/14A2/103

8.7 *a)* with respect to its conformity with the Table of Frequency
Allocations and the other provisions[^6] of these Regulations, except
those provisions relating to conformity with the fixed-satellite service
Plan which are the subject of the following subpara­graph;     (WRC‑03)

**Reasons:** Consequential to renumbering of Article 8 provisions.

**MOD** IAP/14A2/104

8.8 *b)* with respect to its conformity with the fixed-satellite service
Plan and the associated provisions^ADD\ 8.8^.     (WRC-03)

**ADD** IAP/14A2/104A

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^ADD\ 8.8^ When an administration notifies any assignment with
characteristics different from those entered in the List through
successful application of Article 6 of Appendix **30B**, the Bureau will
undertake calculation to determine if the proposed new characteristics
increase the interference level caused to other allotments and
assignments in the Plan and List. The increase of the interference will
be checked by comparing the *C*/*I* ratio (power density) of these other
allotments and assignments, which result from the use of the proposed
new characteristics of the subject assignment on the one hand, and those
obtained with the characteristics of the subject assignment in the List,
on the other hand. This *C*/*I* calculation is performed under the same
technical assumptions and conditions.

**Reasons:** Reference is made to ADD 8.8 which specifies the procedure
through which the Bureau will ensure that a notified assignment, should
its characteristics differ from those in the List, will not cause more
interference to other allotments and assignments in the Plan and List.
This ensures that, given the possibility that a submission may be
modified from that of its initial submission, that the notification
process does not disrupt the integrity of the Plan.

**MOD** IAP/14A2/105

8.9 When the examination with respect to § 8.7 leads to a favourable
finding, the assignment shall be examined further with respect to § 8.8;
otherwise the notice shall be returned with an indication of the
appropriate action.     (WRC-03)

**Reasons:** Consequential to renumbering of Article 8 provisions.

**MOD** IAP/14A2/106

8.10 When the examination with respect to § 8.8 leads to a favourable
finding, the assignment shall be recorded in the Master Register. When
the finding is unfavourable, the notice shall be returned to the
notifying administration, with an indication of the appropriate
action.     (WRC‑03)

**Reasons:** Consequential to renumbering of Article 8 provisions.

**NOC** IAP/14A2/107

8.11 In every case when a new assignment is recorded in the Master
Register it shall, in accordance with the provisions of Article** 8**,
include an indication of the finding reflecting the status of the
assignment. This information shall also be published in the
BR IFIC.     (WRC-03)

**Reasons:** § 8.4 through § 8.11 contain the treatment that the BR
should give to complete notices, specifying how examination should be
conducted and the actions to be taken in case of favorable or
unfavorable findings. The text in its current form is consistent with
changes being proposed to other portions of Appendix 30B and should
therefore be maintained.

**MOD** IAP/14A2/108

8.12 A notice of a change in the characteristics of an assignment
already recorded, as specified in Appendix **4**, shall be examined by
the Bureau under § 8.8, and 8.9 as appropriate. Any changes to the
characteristics of an assignment, that has been notified and confirmed
as having been brought into use, shall be brought into use within eight
years from the date of the notification of the modification. Any changes
to the characteristics of an assignment that has been notified but not
yet brought into use shall be brought into use within the period
provided for in § 6.1 and § 6.27 of Article 6.     (WRC-03)

**Reasons:** Changes are consequential of those introduced in Article 6.

**MOD** IAP/14A2/109

8.13 In the case of a change in the characteristics of an assignment
which is in conformity with § 8.7, should the Bureau reach a favourable
finding with respect to § 8.8, the amended assignment shall retain the
original date of entry in the Master Register. The date of receipt by
the Bureau of the notice relating to the change shall be entered in the
Master Register.     (WRC-03)

**Reasons:** Consequential to renumbering of Article 8 provisions.

**NOC** IAP/14A2/110

8.14 In applying the provisions of this Article, any resubmitted notice
which is received by the Bureau more than six months after the date on
which the original notice was returned by the Bureau shall be considered
to be a new notice.     (WRC-03)

**Reasons:** § 8.13 and 8.14 address the treatment to be given to
modifications to frequency assignments that received an unfavorable
finding with respect to Appendix 30B provisions but were in conformance
with the Table of Frequency Allocations and other provisions of the
Radio Regulations. In particular the 6-month limit set in § 8.14 in
order for the notice not to be considered a new notice is appropriate.

**NOC** IAP/14A2/111

8.15 All frequency assignments notified in advance of their being
brought into use shall be entered provisionally in the Master Register.
Any frequency assignment provisionally recorded under this provision
shall be brought into use by the date specified in the notice. Within
thirty days of such an assignment being brought into use, the notifying
administration shall so inform the Bureau. If the Bureau does not
receive that confirmation within the above period, after sending a
reminder, it shall cancel the entry. The Bureau shall, however, inform
the administration concerned before taking such action.     (WRC-03)

**Reasons:** § 8.15 addresses frequency assignments notified in advance
of their date of bringing into use and mirrors No. 11.47.

**NOC** IAP/14A2/112

8.16 Where the use of a recorded assignment to a space station is
suspended for a period not exceeding eighteen months, the notifying
administration shall, as soon as possible, inform the Bureau of the date
on which such use was suspended and the date on which the assignment is
to be brought back into regular use. This latter date shall not exceed
two years from the date of suspension.     (WRC-03)

**Reasons:** § 8.15 addresses frequency assignments notified in advance
of their date of bringing into use and mirrors No. 11.47. § 8.16
addresses the suspension of frequency assignments and mirrors No. 11.49.
Proposals for modifying both 11.47 and 11.49 have been discussed in the
Working Party of the Special Committee in connection with WRC‑07 Agenda
item 1.12. The provisions § 8.15 and § 8.16 should remain unchanged,
however, they may have to be revised in the case 11.47 and/or 11.49 are
actually modified.

**NOC** IAP/14A2/113

8.17 No provision of this Appendix shall be considered as modifying the
requirements of Article **9** relating to coordination between earth
stations in the fixed-satellite service and stations of terrestrial
services sharing the planned bands on an equal primary
basis.     (WRC-03)

**Reasons:** The coordination of FSS earth stations and stations of
terrestrial services in the Appendix 30B bands should follow the
provisions of Article 9 and therefore § 8.17 should be retained without
any change.

**NOC** IAP/14A2/114

8.18 Notification of assignments to a specific earth station using
assignments included in the List shall be effected applying the
provisions of Article **11**.     (WRC-03)

**Reasons:** The notification of a specific earth station using a
frequency assignment included in the Appendix 30B List should be
conducted in accordance with the provisions of Article 11. Therefore,
§ 8.18 should be retained without any changes.

ARTICLE 9

Procedure for effecting coordination with or\
            obtaining agreement of other administrations**^1^**,
**^2,^** **^3^**, **^4^**, **^5^**, **^6^**, **^7^**,
**^8^**     (WRC-03)

Section II -- Procedure for effecting coordination**^12^**, **^13^**

Sub-Section IIA -- Requirement and request for coordination

**[NOC]{.underline}** IAP/14A2/115

Article 9 (only with respect to coordination of FSS earth stations and
terrestrial stations in Appendix 30B bands).

**Reasons:** The current coordination provisions of Article 9,
particularly Nos. 9.17, 9.18, and 9.19, apply in the sharing of FSS
earth stations using Appendix 30B bands and terrestrial stations. These
provisions provide a balanced coordination process that needs to be
maintained.

APPENDIX 30B (Rev. WRC-2000)

Provisions and associated Plan for the fixed-satellite service\
in the frequency bands 4 500-4 800 MHz, 6 725-7 025 MHz,\
10.70-10.95 GHz, 11.20-11.45 GHz and 12.75-13.25 GHz

ARTICLE 9

General provisions

**MOD** IAP/14A2/116

9.1 The Plan is limited to national systems providing a domestic
service. Administrations may, however, in accordance with the provisions
of Article 6, modify their allotments or propose additional uses to
provide multinational services.

**Reasons:** Changes are consequential of the consolidated regulatory
procedures introduced in Article 6.

**SUP** IAP/14A2/117

9.2

**Reasons:** Existing systems are associated with FSS satellite networks
that had already been submitted to the ITU BR when the Plan was
developed. By now, the frequency assignments in these networks have
either been brought into use and become assignments in the List or have
been cancelled.

§ 9.2 strictly applied would require all these frequency assignments to
cease operation (or operate under No. 4.4 of the Radio Regulations)
after 16 March 2010. Operation under No. 4.4 is not a realistic option,
at least as Appendix 30B frequencies are more widely used. Moreover,
requiring that operational satellite networks with large number of users
abruptly cease their operation is unreasonable.

By suppressing § 9.2, frequency assignments of existing systems that
have been brought into use just remain in the List similarly to the way
in which frequency assignments associated with subregional systems are
currently treated. Resolution \[IAP/14A2/154\] (WRC‑07) is intended to
cover "existing systems" as defined in § 2.4 of Article 2.

ARTICLE 10

Plan for the fixed-satellite service in the frequency bands\
4 500-4 800 MHz, 6 725-7 025 MHz, 10.70-10.95 GHz,\
11.20-11.45 GHz and 12.75-13.25 GHz 

**MOD** IAP/14A2/118

A.1 COLUMN HEADINGS OF THE PLAN

**Reasons:** Change is consequential to the changes proposed in the
elimination of Part B.

{*Editorial note:* Although Column 4 includes the western and eastern
limits of the pre-determined arc, deletion of this column is not being
proposed at this time pending the decision of the conference on the
regulatory treatment of national allotments for which the process of
conversion into assignments has been commenced but not yet concluded.}

**NOC** IAP/14A2/119

A.2 TEXT FOR SYMBOLS IN REMARKS COLUMN OF THE PLAN

Tables with Allotments.

**Reasons:** No need to change section A2 or the tables containing the
allotments because, consistent with the scope of the agenda item, no
changes to the Plan are being proposed.

**SUP** IAP/14A2/120

B COLUMN HEADINGS OF PART B OF THE PLAN

**Reasons:** Consequential to the elimination of Part B and the proposed
treatment for "existing systems" (see Resolution \[IAP/14A2/154\]
(WRC‑07)).

ARTICLE 11

Period of validity of the provisions and associated Plan

**NOC** IAP/14A2/121

11.1 These provisions and associated Plan have been prepared in order to
guarantee in practice for all countries equitable access to the GSO and
the frequency bands contained in Article 3, to meet the requirements of
the fixed-satellite service for a period of at least 20 years from the
date of entry into force of this Appendix.

**Reasons:** § 11.1 re-emphasizes the objectives of the Plan, as stated
in Article 1, and should be retained.

**MOD** IAP/14A2/122

11.2 These provisions and associated Plan shall, in any event, remain in
force until their revision by a competent world radiocommunication
conference, convened in accordance with the relevant provisions of the
Convention in force.

**Reasons:** Editorial change to take account of the fact that world
administrative radiocommunication conferences are now referred to as
world radiocommunication conferences.

ANNEX 1     

Parameters used in characterizing the fixed-satellite service Plan

Section A -- Technical data used in establishing the Allotment Plan\
and the associated provisions

**NOC** IAP/14A2/123

# 1 Basic technical characteristics

The allotments in the Plan are based on a reference satellite network
with the following assumptions:

**MOD** IAP/14A2/124

## 1.1 Type of modulation

The Plan is based upon supporting a maximum modulation index that
results in a carrier-to-noise (*C*/*N*) threshold of 12 dB.

**Reasons:** Modern satellite systems predominantly use digital
modulation and thus have lower *C*/*N* thresholds. A 12 dB threshold
should be adequate for most current and anticipated satellite
applications.

**MOD** IAP/14A2/125

## 1.2 Carrier-to-noise ratio

The carrier-to-noise ratio (*C */* N*) is as follows:

*a)* the total link (*C*/*N*) under rain faded conditions should exceed
a threshold of 12 dB;

*b)* for the 6/4 GHz bands, the threshold is exceeded for 99.9% of the
year;

*c)* for the 13/10-11 GHz bands, the threshold is exceeded for 99.8% of
the year;

*d)* the gaseous atmospheric attenuation and rain attenuation models
used are those described in Recommendations ITU‑R P.676-6 and ITU‑R
P.618-8.

**Reasons:** a) Commercial satellite systems predominantly use
"bent-pipe" (transparent) transponders and thus have a threshold *C*/*N*
at the receiver earth station only; b) A total link availability of
99.9% is consistent with separate uplink and downlink availabilities of
99.95% and 99.95%, respectively; c) A total link availability of 99.8%
is consistent with separate uplink and downlink availabilities of 99.9%
and 99.9%, respectively; d) The pertinent Recommendations that are in
force are listed.

**MOD** IAP/14A2/126

## 1.3 Earth station antenna elevation angle

The minimum elevation angle for each test point defining the service
area is based on the following values of rain rate *R*~0.01~ (exceeded
for the worst 0.01% of the time)[^7]:

10 for *R*~0.01~ 30 mm/h;

20 for 30 \< *R*~0.01~ 60 mm/h;

30 for 60 \< *R*~0.01~ 95 mm/h;

40 for *R*~0.01~ \> 95 mm/h.

Administrations may select lower elevation angles for their service
areas. For countries at high latitudes or with dispersed territories, in
the absence of such a request, if the above values for minimum elevation
angle are unobtainable, then the highest elevation angle leading to a
non-zero service arc applies. In mountainous areas, the elevation angles
are specified by the administrations concerned.

**Reasons:** The latest in-force version of Recommendation ITU‑R
P.837(-4) uses rain rate, expressed in (mm/hr) exceeded for the worst
0.01% of the time as the basis for the determination of rain fade using
Recommendation P.618-8. The rain rate ranges corresponding to the "old"
climatic zones in version 1 of Recommendation ITU‑R P.837 have been used
in place of the climatic zones listed.

**MOD** IAP/14A2/127

## 1.4 Interference criteria

The Plan has been prepared with a view to assuring for each allotment an
aggregate carrier-to-interference ratio under free-space conditions of
22 dB or higher for the 13/10-11 GHz bands and 20 dB or higher for the
6/4 GHz bands.

**Reasons:** A reduced (relaxed) *C*/*I* criteria is required in
combination with a reduced (relaxed) total link *C*/*N* ratio to ensure
that the lower *C*/*I* that will result with some allotments due to the
use of smaller earth station antennas, will still be within acceptable
limits.

**NOC** IAP/14A2/128

## 1.5 Polarization

Polarization isolation between satellite networks was not used in the
development of the Allotment Plan.

**Reasons:** Statement of fact about the WARC-88 Plan. There is no
proposal to change this provision.

**MOD** IAP/14A2/129

## 1.6 Earth station characteristics

1.6.1 The diameters of the earth station antennas are:

4.5 m for the 6/4 GHz band;

2.4 m for the 13/10-11 GHz band.

**Reasons:** Technical studies have indicated that these are the minimum
antenna sizes that when used in association with: the revised *C*/*N*
threshold (MOD 1.2), interference criteria (MOD 1.4), earth station
receiving systems noise temperatures (MOD 1.6.2) and space station
receiving system noise temperatures (MOD 1.7.3); that national
allotments and assignments in the List are adequately protected (i.e. in
accordance with the provisions of Appendix 30B (WRC‑07)).

**MOD** IAP/14A2/130

1.6.2 The earth station receiving system noise temperature referred to
the output of the receiving antenna is:

95 K for the 4 GHz band;

125 K for the 10-11 GHz band.

**Reasons:** These earth station noise temperatures are typical of those
that can be achieved with modern technology.

**NOC** IAP/14A2/131

1.6.3 The earth station antenna efficiency is 70%.

**Reasons:** No proposal to change the earth station antenna efficiency
from that of the WARC-88 Plan.

**MOD** IAP/14A2/132

1.6.4 The applicable earth station antenna reference pattern is shown in
Table 1 below. If so desired by an administration, the improved
side-lobe pattern shown in Table 2 below may be used.     (WRC-03)

**Reasons:** Reference to Part A is no longer necessary, consequential
to elimination of Part B from the Plan.

**NOC** IAP/14A2/133

TABLE 1     (WRC-03)

![](media/image2.wmf){width="0.4722222222222222in"
height="0.4583333333333333in"}![](media/image3.wmf){width="0.18055555555555555in"
height="0.4305555555555556in"}![](media/image4.wmf){width="0.9305555555555556in"
height="0.3888888888888889in"}![](media/image5.wmf){width="2.2916666666666665in"
height="0.3611111111111111in"}

**Reasons:** No changes are required in the table. The reference
radiation pattern for earth stations in the Table is already consistent
with the design objective for "newer" earth stations (installed after
1995) having a diameter-to-wavelength ratio of 50 and 150 in
Recommendation ITU‑R S.580-6.

**MOD** IAP/14A2/134

1.6.5 In cases where the required aggregate *C */* I* ratio specified in
1.4 of this Annex cannot be obtained, it would be appropriate for the
countries concerned to agree on the use of antennas with an improved
sidelobe pattern or on other suitable means so as to obtain the above
ratio (see Table 2 below).     (WRC-03)

**Reasons:** Consequential to change in Appendix 30B interference
criteria in 1.4.

**NOC** IAP/14A2/135

TABLE 2     (WRC-03)

![](media/image2.wmf){width="0.4722222222222222in"
height="0.4583333333333333in"}![](media/image6.wmf){width="0.18055555555555555in"
height="0.4305555555555556in"}![](media/image4.wmf){width="0.9305555555555556in"
height="0.3888888888888889in"}![](media/image7.wmf){width="2.2916666666666665in"
height="0.3611111111111111in"}![](media/image8.wmf){width="2.0in"
height="0.4583333333333333in"}

**Reasons:** Consistent with § 1.6.5, countries are free to make use of
improved antenna reference antenna patterns for earth stations such as
that depicted in Table 2. The reference pattern referred to in § 1.6.5
is included for completeness. No change in the improved sidelobe pattern
in Table 2 is proposed.

## 1.7 Space station characteristics

**NOC** IAP/14A2/136

1.7.1 The allotment Plan is based on the use of space station antennas
with beams of elliptical or circular cross-section.

**Reasons:** Statement of fact about basis of the WARC-88 Plan with
respect to the shape of space station antennas. There is no proposal to
change this provision.

**NOC** IAP/14A2/137

1.7.2 The antenna radiation characteristics are as shown in Fig. 1. The
fast roll-off characteristics shown in Fig. 2 may be used when so
specified by administrations.

![](media/image9.wmf){width="5.274305555555555in"
height="3.647222222222222in"}

*Gmax* 44.45 -- 10 log (01 · 02)               dBi

*Curve A:* dB relative to main beam gain

-- 12 (/0)2  for 0 (0) 1.45

--  (22 20 log (/0))  for (0) 1.45

after intersection with Curve B: Curve B

*Curve B:* Minus the on-axis gain (Curves B in this Figure illustrates
the particular case of an antenna with an on-axis gain of 46 dBi)

01, 02: Major and minor axis half-power beamwidth, respectively, of
elliptical beam (degrees)

0: Cross-sectional half-power beamwidth in the direction of interest
(degrees)

![](media/image10.wmf){width="4.817361111111111in"
height="3.370138888888889in"}

*Curve A*: dB relative to main beam gain

--12 (/~0~)^2^ for 0 (/~0~) 0.5

--![](media/image11.wmf){width="0.9583333333333334in" height="0.5in"}
for 0.5 (/~0~) ![](media/image12.wmf){width="0.9027777777777778in"
height="0.4583333333333333in"}

--25.23 for ![](media/image13.wmf){width="1.7916666666666667in"
height="0.4583333333333333in"}

--(22 20 log (/~0~)) for (~0~) 1.45

after intersection with Curve B: Curve B.

*Curve B*: Minus the on-axis gain (Curve B represents examples of four
antennas having different values of ~0~ as labelled in Fig. 2. The
on-axis gains of these antennas are approximately 28.3, 34.3, 40.4 and
46.4 dBi, respectively)

where:

>  : off-axis angle (degrees)
>
> ~0~ : cross-sectional half-power beamwidth in the direction of
> interest (degrees)
>
> ![](media/image14.wmf){width="1.0277777777777777in"
> height="0.4583333333333333in"}

where:

> ![](media/image15.wmf){width="1.8055555555555556in"
> height="0.6631944444444444in"}

[^8]

**Reasons:** Countries are free to make use of fast roll-off antenna
reference antenna patterns for space stations such as that depicted in
Figure 2. The reference antenna pattern is included for completeness. No
change in the fast roll-off antenna pattern in Figure 2 is proposed.

**MOD** IAP/14A2/138

1.7.3 The space station receiving system noise temperature referred to
the output of the receiving antenna is:

500 K for the 6 GHz band;

550 K for the 13 GHz band.

**Reasons:** These space station noise temperatures are typical of those
that can be achieved with modern technology.

**NOC** IAP/14A2/139

1.7.4 The minimum beamwidth size, in terms of the half-power beamwidth,
is 1.6 for the 6/4 GHz band and 0.8 for the 13/10-11 GHz band.

**Reasons:** Statement of fact about the WARC-88 Plan with respect to
the minimum half-power beamwidth of space station antennas. There is no
proposal to change this provision.

**NOC** IAP/14A2/140

1.7.5 The space station antenna efficiency is 55%.

**Reasons:** Statement of fact about the WARC-88 Plan with respect to
the space station antenna efficiency. There is no proposal to change
this provision.

**NOC** IAP/14A2/141

1.7.6 The deviation of the space station antenna beam from its nominal
pointing direction is limited to 0.1 in any direction. The rotation
accuracy of elliptical beams is 1.0.

**Reasons:** Statement of fact about the WARC-88 Plan with respect to
the nominal pointing direction of space station antennas and rotational
accuracy of elliptical beams. There is no proposal to change this
provision.

**ADD** IAP/14A2/142

1.7.7 The maximum East/West deviation of the space station is 0.05° from
its nominal orbital location.

**Reasons:** This level of East/West deviation is typical of the
station-keeping accuracy of modern geostationary satellites. The
deviation is non-zero and thus should be properly identified and taken
into account when developing limits for determining whether an allotment
or an assignment made in accordance with the provisions of Appendix 30B
is considered to be affected.

**NOC** IAP/14A2/143

## 1.8 Bandwidth

The allotment Plan is based on the carrier power averaged over the
necessary bandwidth of the modulated carrier and referred to a 1 MHz
bandwidth.

**Reasons:** Statement of fact about the WARC-88 Plan on the basis of
the Plan with respect to the necessary bandwidth of a modulated carrier
and the reference bandwidth. There is no proposal to change this
provision.

**SUP** IAP/14A2/144

Section B -- Generalized parameters used for determining when the
assignments of a\
proposed satellite network are in conformity with the Plan

**Reasons:** This proposal is consequential of the proposed elimination
of the generalized parameters (see Article 2.3).

**MOD** IAP/14A2/145

ANNEX 2     (WRC-03)

Basic data to be furnished in notices relating to stations\
in the fixed-satellite service using frequency bands of the Plan

These data are listed in Appendix **4**.

**Reasons:** The change in the title is required as a consequence of the
proposal to eliminate the concept of "design stage" through the
suppression of Article 5.

**NOC** IAP/14A2/146

ANNEX 3A

Criteria for determining when proposed assignments\
are considered as being in conformity with the Plan

**Reasons:** This proposal is consequential to the elimination of the
generalized parameters.

**SUP** IAP/14A2/147

ANNEX 3B

Macrosegmentation concept

**Reasons:** Satellite networks being deployed are using digital
modulation and hence there is no need to order traffic in each allotment
band according to high and low density carriers when the traffic tends
to be uniform.

**SUP** IAP/14A2/148

ANNEX 4     (WRC-03)

Limits for determining whether an allotment or an assignment\
made in accordance with the provisions of Appendix 30B is\
considered to be affected

**ADD** IAP/14A2/149

ANNEX 4     (WRC‑07)

Limits for determining whether an allotment or an assignment\
made in accordance with the provisions of Appendix 30B is\
considered to be affected

An allotment or assignment shall be considered as being affected by
another administration if, at its nominal orbital position within the
coordination arc, the calculated single-entry power flux-density or the
calculated value, based on the Plan, due to that other administration
(whichever is the lower), at any test point within the service area of
the interfered-with satellite network[^9] exceeds any of the following
values in the applicable frequency bands.

For the purpose of assessing interference levels from satellite networks
into interfered‑with satellite networks, a "coordination arc" is defined
as that within 9° of the nominal orbital position in the 13/10-11 GHz
band and within 10° of the nominal orbital position in the 6/4 GHz band,
under free-space propagation conditions, the power flux-density at any
test point within the service area associated with any of its frequency
assignments in the Plan does not exceed the following
values dB(W/(m^2^  Hz)):

Evaluated at 13 GHz, the pfd masks, in dB(W/(m^2^  MHz)), are as
follows:

Using an antenna with a 2.4 m diameter or larger:

−145.9 for θ \< 0.1°

−145.39 + 51.19 θ^2^ − 10.238 θ for  0.1° \< θ 0.43°

−143.47 + 32.76 θ^2^ − 6.552 θ for 0.43° \< θ 0.77°

−95.22 -- min (29.26, 27.97 -- 25 log (θ − 0.1)) for 0.77° \< θ 18.24°

−95.22 − max (min (−3.5, 30.97 − 25 log(θ − 0.1), −10) for θ \> 18.24°

Evaluated at 6.875 GHz, the pfd masks, in dB(W/(m^2^  MHz)), are as
follows:

Using an antenna with a 4.5 m diameter or larger:

−145.3 for θ 0.1°

−144.52 + 77.95 θ^2^ − 15.59 θ for 0.1° \< θ 0.31°

−142.88 + 32.22 θ^2^ − 6.444 θ for 0.31° \< θ 0.78°

−94.53 − min (29.2, 27.97 − 25 log (θ − 0.1)) for 0.78° \< θ 18.24°

−94.53 − max (min (−3.5, 30.97 − 25 log (θ − 0.1)), −10) for θ \> 18.24°

Evaluated at 11.2 GHz, the pfd masks, in dB(W/(m^2^  MHz)), are as
follows:

Using an antenna with a 2.4 m diameter or larger:

−166.4 for θ 0.1°

−166.02 + 38 θ^2^ − 7.6 θ for 0.1° \< θ 0.64°

−162.16 + 24.32 θ^2^ − 4.864 θ for 0.64° \< θ 0.9°

−117.02 − min (29.74, 27.97 − 25 log (θ − 0.1)) for 0.9° \< θ 18.24°

−117.02 − max (min (−3.5, 30.97 − 25 log (θ − 0.1)), −10) for θ \>
18.24°

Evaluated at 4.65 GHz, the pfd masks, in dB(W/(m^2^  MHz)), are as
follows:

Using an antenna with a 4.5 m diameter:

−177.6 for θ 0.1°

−176.24 + 35.66 θ^2^ − 7.132 θ for 0.1° \< θ 0.64°

−171.75 + 14.74 θ^2^ − 2.948 θ for 0.64° \< θ 1.12°

−128.49 − min (29.54, 27.97 − 25 log (θ − 0.1)) for 0.74° \< θ 18.24°

−128.49 − max (min (−3.5, 30.97 − 25 log (θ − 0.1)), −10) for θ \> 18.24

Note that the angle is the angular separation between the wanted and the
interfering satellite networks measured on the geostationary orbital
arc. All pfd masks have taken worst-case relative orbital separation
into account by assuming that each of the wanted and the interfering
satellite networks can be 0.05° from their nominal orbital locations
(and thus 0.1° closer together) in accordance with the East/West
station-keeping tolerances in § 1.77 of Section A of Annex 1.

The power flux-density limits are based upon an overall single-entry
carrier-to-interference ratio of 26 dB for the 13/10-11 GHz bands and
24 dB for the 6/4 GHz bands assuming that the aggregate
carrier-to-interference ratios are 4 dB lower.

All submissions for modifications to allotments or additional systems,
including those already received by the Bureau but not yet processed on
or after the closing date of the WRC‑07 shall be examined for their
potential interference to:

-- allotments in the Plan,

-- assignments in the List,

-- assignments for which the Bureau has previously received complete
information in accordance with this Article as follows:

*a)* for systems which are separated from the nominal orbital position
of the interfered-with satellite network by an amount less than the
coordination arc and do not exceed the applicable limits will be
considered to be in accordance with the provisions of Appendix **30B**;

*b)* for systems which are separated from the nominal orbital position
of the interfered-with satellite network by an amount less than the
coordination arc exceed the applicable limits will be examined further
to ensure that a minimum single-entry carrier-to-interference ratio of
26 dB for the 13/10-11 GHz bands or 24 dB for the 6/4 GHz bands is
achieved at all test points of the interfered-with satellite network;

*c)* for systems which are outside the coordination arc with respect to
the interfered-with satellite network and do not exceed the applicable
limits will be considered to be in accordance with the provisions of
Appendix **30B**;

*d)* for systems which are outside the coordination arc with respect to
the interfered-with satellite network and exceed the applicable limits
will only be examined further if the affected administration can
demonstrate that a minimum single-entry carrier-to-interference ratio of
26 dB for the 13/10-11 GHz bands or 24 dB for the 6/4 GHz bands is not
achieved at all test points of the interfered-with satellite network.

**Reasons:** Coordination arcs that can be used with in association with
pfd masks and the methods for examining submissions for their potential
for interference (as stipulated in *a)*, *b)*, *c)* and *d)*) allow the
coordination arc concept to be applied. Provision for inclusion in the
coordination process for systems inside and outside the coordination arc
are given in *b)* and *d)* respectively by using *C*/*I* calculations
even when calculated interfering pfd levels are within the pfd mask
limits.

**SUP** IAP/14A2/150

APPENDIX 1 TO ANNEX 4 

Method for determination of the single-entry and aggregate\
carrier-to-interference ratio averaged over the necessary\
bandwidth of the modulated carrier

**Reasons:** The method contained in this section should be retained in
an ITU‑R Recommendation.

**ADD** IAP/14A2/151

APPENDIX 1 TO ANNEX 4     (WRC‑07)

Method for determination of the single-entry power flux density\
averaged over a 1 MHz reference bandwidth

When calculating the pfd either from a satellite or from an earth
station, the actual path length from the space station or earth station
under evaluation toward the potentially affected earth station or space
station should be used. The calculated pfd can then be compared with the
pfd limit masks in Annex 4 to determine whether the satellite network
under evaluation should be included or excluded from further
consideration in coordination with the potentially affected network. As
the pfd limit masks, which are derived from single-entry *C*/*I*
criteria, are intended as a convenient tool for the facilitation of
further coordination between satellite networks, the single-entry and
aggregate *C*/*I* between such networks should be calculated using
Recommendation ITU‑R S.740. The derivation of single-entry pfd limits is
described below.

Uplink pfd limits to protect adjacent satellite systems and downlink pfd
limits to protect earth stations in Annex 4 were derived based on the
following expression:

$\text{pfd}_{i} = \text{pfd}_{w} - \left( \frac{C}{I} \right)_{\text{SE}} + \left( G_{\text{Max}} - G(\phi_{\text{topo}}) \right)$
(1)

where *pfd~w~* is:

1\) in the case of the uplink is 0 dB(W/MHz) at the input to the
transmitting earth station, and

2\) in the case of the satellite downlink is the representative level
for the minimum wanted power flux-density. In the case of the 10-11 GHz
and the 4 GHz frequency bands, −134 dB(W/m^2^/MHz) and
−146 dB(W/m^2^/MHz) respectively.

When calculating the wanted pfd, a spreading loss equivalent to the loss
at an elevation angle of 25° of was used. The gain of the receiving and
transmitting earth station antennas is calculated using the earth
station antenna reference pattern in Table 1 to Annex 1 of
Appendix **30B**. *G*(φ*~topo~*) is the gain of the receiving or
transmitting antenna where topocentric angle is the angle between the
wanted and interfering satellite, measured at the earth station (or test
point), in degrees. In calculating the uplink and downlink pfd masks, a
multiplication factor of 1.1 was used where φ*~topo~ *= 1.1 , where is
the minimum geocentric angular separation. This simplification was made
for the purpose of deriving the pfd masks since the multiplication
factor actually changes depending upon the relative location of two test
points. The single-entry (*C*/*I*)*~SE~* values derived from
expressions (4) through (7) below were used in the derivation of the pfd
limits in equation (1).

The division between the amount of interference on the total link due to
contributions of interference on the uplink and the downlink assumes
that the same topocentric angular separation between the wanted and the
interfering signal on both the uplink and the downlink is maintained.
Thus, the following expressions (2) and (3) are true.

$\left( \frac{c}{i} \right) = \left\lbrack \left( \frac{c}{i} \right)_{\frac{U}{L}}^{- 1} + \left( \frac{c}{i} \right)_{\frac{D}{L}}^{- 1} \right\rbrack^{- 1}$
(2)

$\left( \frac{C}{I} \right)_{\frac{U}{L}} - \left( \frac{C}{I} \right)_{\frac{D}{L}} = \text{20}\ \text{log}\left( \frac{f_{\frac{U}{L}}}{f_{\frac{D}{L}}} \right)$
(3)

where:

$\left( \frac{c}{i} \right)_{\frac{U}{L}},\left( \frac{C}{I} \right)_{\frac{U}{L}}$
= Carrier to interference ratio of the uplink (as a ratio, dB)

$\left( \frac{c}{i} \right)_{\frac{D}{L}},\left( \frac{C}{I} \right)_{\frac{D}{L}}$
= Carrier to interference ratio of the downlink (as a ratio, dB)

*f~U~*~/*L*~ = uplink frequency in GHz

*f~D~*~/*L*~ = downlink frequency in GHz.

6/4 GHz band

$\left( \frac{C}{I} \right)_{\frac{U}{L}} = \left( \frac{C}{I} \right)_{\text{Link}} + 5\text{.}\text{03}$
(4)

$\left( \frac{C}{I} \right)_{\frac{D}{L}} = \left( \frac{C}{I} \right)_{\text{Link}} + 1\text{.}\text{64}$
(5)

13/10-11 GHz band

$\left( \frac{C}{I} \right)_{\frac{U}{L}} = \left( \frac{C}{I} \right)_{\text{Link}} + 3\text{.}\text{71}$
(6)

$\left( \frac{C}{I} \right)_{\frac{D}{L}} = \left( \frac{C}{I} \right)_{\text{Link}} + 2\text{.}\text{41}$
(7)

where $\left( \frac{C}{I} \right)_{\text{Link}}$is the single-entry
*C*/*I* criteria of 26 dB and 24 dB for the 13/10-11 GHz and the 6/4 GHz
bands respectively. It is assumed that a difference of 4 dB is
maintained such that the aggregate criteria (*C*/*I*)*~aggregate~* is
4 dB less than the single-entry criteria (*C*/*I*)*~SE~*.

**Reasons:** Inclusion of this method on calculating the interfering
levels of pfd toward the space stations and earth stations of
potentially affected satellite networks allows interfering pfd levels to
be calculated in an unambiguous way. Additionally, the derivation of pfd
masks from single-entry *C*/*I* criteria are provided. A reference to
Recommendation ITU‑R S.740 (where the old Appendix 1 to Annex 4 is
proposed to reside) is essential in that calculation of the single-entry
and aggregate *C*/*I* values is maintained as the definitive measure by
which examinations are conducted to determine compliance with the
provisions of Appendix 30B.

**SUP** IAP/14A2/152

ANNEX 5     (WRC-03)

Application of the PDA (predetermined arc) concept

**Reasons:** The suppression of this Annex is consequential of the
proposed elimination of the PDA concept.

**MOD** IAP/14A2/153

ANNEX 6     (WRC-03)

Technical means which may be used to avoid incompatibilities between\
systems in the fixed-satellite service at their implementation stage

1 Improved frequency modulated TV carrier dispersal techniques with up
to 4-5 MHz peak-to-peak deviation.

2 Frequency separation between signals with high peak spectral density
and narrow-band signals (bandwidth segmentation).

3 The use of transmitting and receiving antennas with special beams
providing minimum gain in the direction to neighbouring satellites.

4 Shaped beams for transmitting satellite antennas.

**Reasons:** The pertinence of this four methods to improve technical
compatibility between satellite systems needs to be considered in light
of the revised technical parameters in the Plan. The ratios in § 5 are
obsolete given proposals for revised technical parameters in the Plan.

**ADD** IAP/14A2/154

RESOLUTION \[IAP/14a2/154\] (WRC‑07)

Satellite systems in Part B of Appendix 30B

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that WARC-Orb-88 adopted a Plan for the fixed-satellite service in
the frequency bands 4 500-4 800 MHz, 6 725-7 025 MHz, 10.70-10.95 GHz,
11.20-11.45 GHz and 12.75-13.25 GHz as contained in Appendix **30B**;

*b)* that, when the Plan was adopted, some satellite systems in the same
frequency bands were under coordination or had been recorded in the
Master International Frequency Register (MIFR) or had information
relating to advance publication that was received by the
Radiocommunication Bureau before 8 August 1985;

*c)* that in the original provisions of Appendix **30B (WARC-Orb 88)**,
the satellite systems referred to in *considering b)* above were
designated as existing systems and were contained in Part B of the Plan;

*d)* that satellite systems identified in *considering b)* and in Part B
of the Plan have either been included into the List of Appendix **30B**
or cancelled, and thus Part B of the Plan is empty,

recognizing

*a)* that the period of operation of satellite systems in Part B of the
Plan expires after 16 March 2010;

*b)* that but some administrations expressed their wish to continue
operation of these systems after the above-mentioned deadline mentioned
in *recognizing a)*;

*c)* that satellite systems referred to in *considering b)* are
compatible with satellite networks in Appendix **30B**,

resolves

1 that Part B of the Plan in Appendix **30B** should be cancelled;

2 that use of frequency assignments to satellite systems identified in
*considering b)* which are included into the List of assignments of
Appendix **30B** and recorded in the Master Register should continue in
accordance with the notified period of validity, *or have their period
of operation extended by 42 months from the closing of the Conference
(WRC‑07) whichever date comes later*;

3 that if a notifying administration which wishes to extend the period
of operation *beyond that determined under 2 above*, to a satellite
system identified in *considering b)* informs the Bureau accordingly
more than three years before the expiry of the period in question and if
all other basic characteristics of that assignment remain unchanged, the
Bureau shall amend as requested the period of operation originally
recorded in the Master Register and publish that information in a
special section of the Bureau's International Frequency Information
Circular (BR IFIC),

instructs the Radiocommunication Bureau

1 to take the appropriate actions in accordance with *resolves* 1, 2
and 3 above.

**Reasons:** The new Resolution is necessary to provide regulatory
treatment to satellite systems still in operation after the expiration
of the period of operation of satellite systems in Part B of the Plan
given that some administrations have systems which entered the Plan
under Part B and that some of these systems may continue to be
operational beyond the original expiration of
operation.[]{#__RefHeading___Toc177410985 .anchor}

#### Agenda item 1.12 

1.12 to consider possible changes in response to Resolution 86 (Rev.
Marrakesh, 2002) of the Plenipotentiary Conference: "Advance
publication, coordination, notification and recording procedures for
frequency assignments pertaining to satellite networks" in accordance
with Resolution **86** **(WRC‑03)**

Proposal for Agenda item 1.12: Power flux-density limits for the
27.5 GHz band

Background information

The last sentence of Radio Regulation No. 5.538 makes reference to the
application of pfd limits contained in Table 21-4 of Radio Regulation
Article 21 in the band 27.500-27.501 GHz whereas Table 21-4 does not
contain this frequency band.

It is proposed to modify Table 21-4 and No. 5.538 as shown in Section
6/1.12/1.4 of the CPM Report.

ARTICLE 21

Terrestrial and space services sharing frequency bands above 1 GHz

**MOD** IAP/14A2/155

TABLE **21-4***  *(*continued*)     (WRC-07)

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/156

**5.538** *Additional allocation:  *the bands 27.500-27.501 GHz and
29.999-30.000 GHz are also allocated to the fixed-satellite service
(space‑to‑Earth) on a primary basis for the beacon transmissions
intended for up-link power control. Such space-to-Earth transmissions
shall not exceed an equivalent isotropically radiated power (e.i.r.p.)
of 10 dBW in the direction of adjacent satellites on the
geostationary-satellite orbit.

**Reasons:** To incorporate the power flux-density limits in the band
27.500-27.501 GHz in Table 21-4 of Article 21 and delete the
corresponding reference in Radio Regulation No. 5.538.

Proposal for Agenda item 1.12: Appendix 5 Coordination arc in the band
17.3-17.8 GHz and other closely related proposals

Background information

Resolution 901 (WRC‑03) invites ITU‑R "to conduct studies on the
applicability of the coordination arc concept for space
radiocommunication services not yet covered by these Regulations" as
well as "to recommend, as appropriate, the orbital separation required
for triggering inter-service and intra-service coordination concerning
the satellite services in frequency bands above 3.4 GHz for
geostationary-satellite (GSO) networks not subject to a Plan and not
already covered by the coordination arc concept specified in No. **9.7**
(GSO/GSO) of Table 5-1 (Appendix **5**), under items 1), 2) and 3) of
the frequency band column, and subject to Section II of Article **9**".
This Resolution further resolves to recommend that a future competent
conference review the results of ITU‑R studies on the application of the
coordination arc and consider including the results of these studies in
Appendix 5. Review of such study results are considered under
Resolution 86 of Agenda item 1.12.

Pursuant to Resolution 901 (WRC‑03), ITU‑R studied the appropriate
coordination arc value to trigger coordination between
broadcasting-satellite service (BSS) networks serving Region 2 in the
band 17.3-17.8 GHz and fixed-satellite service (FSS) (space-to-Earth)
networks serving Region 1 in the band 17.3-17.7 GHz and FSS
(space-to-Earth) networks serving Regions 1, 2 and 3 in the band
17.7-17.8 GHz.

The ITU‑R studies concluded that a coordination arc value of ±8° is
appropriate to trigger coordination between GSO BSS networks serving
Region 2 and GSO FSS (space-to-Earth) networks whose service areas are
limited to Region 1 in the band 17.3-17.7 GHz and between GSO BSS
networks serving Region 2 and GSO FSS (space-to-Earth) networks whose
service areas are limited to Regions 1 and/or 3 in the band
17.7-17.8 GHz. As a result, specific changes are proposed to Table 5-1
of Appendix 5 to incorporate these conclusions. For the case of Region 2
FSS (space-to-Earth) with respect to Region 2 BSS in the 17.7-17.8 GHz
band footnote No. 5.517 applies.

"**5.517** In Region 2, the allocation to the broadcasting-satellite
service in the band 17.3-17.8 GHz shall come into effect on 1 April
2007. After that date, use of the fixed-satellite (space-to-Earth)
service in the band 17.7-17.8 GHz shall not claim protection from and
shall not cause harmful interference to operating systems in the
broadcasting-satellite service."

Changes to the wording of this provision, as well as consequential
changes to the Table of Allocations are proposed recognizing that the 1
April 2007 date has passed.

Finally, also for Region 2, No. 5.518 applies for the mobile service.

"**5.518** *Different category of service:* in Region 2, the allocation
of the band 17.7-17.8 GHz to the mobile service is on a primary basis
until 31 March 2007."

Suppression of this provision is proposed, recognizing that the 31 March
2007 date has passed.

APPENDIX 5 (Rev.WRC‑03)

Identification of administrations with which coordination is to be
effected or\
agreement sought under the provisions of Article 9

**MOD** IAP/14A2/157

TABLE 5-1     (Rev.WRC‑07)

Technical conditions for coordination\
(see Article 9)

+----+-----------+-----------+-----------------+--------+-----------+
| Re | Case      | Frequency | Thre            | Calcul | Remarks   |
| fe |           | bands\    | shold/condition | ation\ |           |
| re |           | (and      |                 | method |           |
| nc |           | Region)   |                 |        |           |
| e\ |           | of the    |                 |        |           |
| o  |           | service\  |                 |        |           |
| f\ |           | for which |                 |        |           |
| A  |           | coor      |                 |        |           |
| rt |           | dination\ |                 |        |           |
| ic |           | is sought |                 |        |           |
| le |           |           |                 |        |           |
| 9  |           |           |                 |        |           |
+----+-----------+-----------+-----------------+--------+-----------+
| N  | A station | 1\)       | i\) Bandwidth   |        | With      |
| o. | in a      | 3         | overlap, and    |        | respect   |
| ** | satellite | 400-4 200 |                 |        | to the    |
| 9. | network   | MHz\      | ii\) any        |        | space     |
| 7\ | using the | 5         | network in the  |        | services  |
| *  | geost     | 725-5 850 | fixed-satellite |        | listed in |
| *G | ationary- | MHz       | service (FSS)   |        | the       |
| SO | satellite | (         | and any         |        | t         |
| /G | orbit     | Region 1) | associated      |        | hreshold/ |
| SO | (GSO), in | and\      | space operation |        | condition |
|    | any space | 5         | functions (see  |        | column in |
|    | radiocomm | 850-6 725 | No. **1.23**)   |        | the bands |
|    | unication | MHz\      | with a space    |        | in 1),    |
|    | service,  | 7         | station within  |        | 2), 3),   |
|    | in a      | 025-7 075 | an orbital arc  |        | 4) 5), 6) |
|    | frequency | MHz       | of  10° of the  |        | and 7) an |
|    | band and  |           | nominal orbital |        | admin     |
|    | in a      |           | position of a   |        | istration |
|    | Region    |           | proposed        |        | may       |
|    | where     |           | network in the  |        | request,  |
|    | this      |           | FSS             |        | pursuant  |
|    | service   |           |                 |        | to        |
|    | is not    |           |                 |        | No.       |
|    | subject   |           |                 |        | **9.41**, |
|    | to a      |           |                 |        | to be     |
|    | Plan, in  |           |                 |        | included  |
|    | respect   |           |                 |        | in        |
|    | of any    |           |                 |        | requests  |
|    | other     |           |                 |        | for       |
|    | satellite |           |                 |        | coor      |
|    | network   |           |                 |        | ­dination, |
|    | using     |           |                 |        | i         |
|    | that      |           |                 |        | ndicating |
|    | orbit, in |           |                 |        | the       |
|    | any space |           |                 |        | networks  |
|    | radio­comm |           |                 |        | for which |
|    | unication |           |                 |        | the value |
|    | service   |           |                 |        | of        |
|    | in a      |           |                 |        | *T*/*T*   |
|    | frequency |           |                 |        | c         |
|    | band and  |           |                 |        | alculated |
|    | in a      |           |                 |        | by the    |
|    | Region    |           |                 |        | method in |
|    | where     |           |                 |        | § 2.2.1.2 |
|    | this      |           |                 |        | and 3.2   |
|    | service   |           |                 |        | of        |
|    | is not    |           |                 |        |  Appendix |
|    | subject   |           |                 |        | **8**     |
|    | to a      |           |                 |        | exceeds   |
|    | Plan,     |           |                 |        | 6%. When  |
|    | with the  |           |                 |        | the       |
|    | exception |           |                 |        | Bureau,   |
|    | of the    |           |                 |        | on        |
|    | coo       |           |                 |        | request   |
|    | rdination |           |                 |        | by an     |
|    | between   |           |                 |        | affected  |
|    | earth     |           |                 |        | admini    |
|    | stations  |           |                 |        | stration, |
|    | operating |           |                 |        | studies   |
|    | in the    |           |                 |        | this      |
|    | opposite  |           |                 |        | in        |
|    | direction |           |                 |        | formation |
|    | of        |           |                 |        | pursuant  |
|    | tra       |           |                 |        | to        |
|    | nsmission |           |                 |        | No.       |
|    |           |           |                 |        | **9.42**, |
|    |           |           |                 |        | the       |
|    |           |           |                 |        | ca        |
|    |           |           |                 |        | lculation |
|    |           |           |                 |        | method    |
|    |           |           |                 |        | given in  |
|    |           |           |                 |        | § 2.2.1.2 |
|    |           |           |                 |        | and 3.2   |
|    |           |           |                 |        | of        |
|    |           |           |                 |        | Appen     |
|    |           |           |                 |        | dix **8** |
|    |           |           |                 |        | shall be  |
|    |           |           |                 |        | used      |
+----+-----------+-----------+-----------------+--------+-----------+
|    |           | 2\)       | i\) Bandwidth   |        |           |
|    |           | 1         | overlap, and    |        |           |
|    |           | 0.95-11.2 |                 |        |           |
|    |           | GHz\      | ii\) any        |        |           |
|    |           | 1         | network in the  |        |           |
|    |           | 1.45‑11.7 | FSS or          |        |           |
|    |           | GHz\      | broadca         |        |           |
|    |           | 11.7-12.2 | sting-satellite |        |           |
|    |           | GHz\      | service (BSS),  |        |           |
|    |           | (R        | not subject to  |        |           |
|    |           | egion 2)\ | a Plan, and any |        |           |
|    |           | 12.2-12.5 | associated      |        |           |
|    |           | GHz\      | space operation |        |           |
|    |           | (R        | functions (see  |        |           |
|    |           | egion 3)\ | No. **1.23**)   |        |           |
|    |           | 1         | with a space    |        |           |
|    |           | 2.5‑12.75 | station within  |        |           |
|    |           | GHz       | an orbital arc  |        |           |
|    |           | (         | of  9° of the   |        |           |
|    |           | Regions 1 | nominal orbital |        |           |
|    |           | and 3)    | position of a   |        |           |
|    |           | 1         | proposed        |        |           |
|    |           | 2.7‑12.75 | network in the  |        |           |
|    |           | GHz       | FSS or BSS, not |        |           |
|    |           | (         | subject to a    |        |           |
|    |           | Region 2) | Plan            |        |           |
|    |           | and\      |                 |        |           |
|    |           | 1         |                 |        |           |
|    |           | 3.75‑14.5 |                 |        |           |
|    |           | GHz       |                 |        |           |
+----+-----------+-----------+-----------------+--------+-----------+

TABLE 5-1 (*continued*)     (Rev.WRC‑07)

+----+-----------+-----------+-----------------+--------+-----------+
| ** | **Case**  | **        | **Thresh        | **     | **        |
| Re |           | Frequency | old/condition** | Calcul | Remarks** |
| fe |           | bands\    |                 | ation\ |           |
| re |           | (and      |                 | me     |           |
| nc |           | Region)   |                 | thod** |           |
| e\ |           | of the    |                 |        |           |
| o  |           | service\  |                 |        |           |
| f\ |           | for which |                 |        |           |
| A  |           | coor      |                 |        |           |
| rt |           | dination\ |                 |        |           |
| ic |           | is        |                 |        |           |
| le |           | sought**  |                 |        |           |
| 9  |           |           |                 |        |           |
| ** |           |           |                 |        |           |
+----+-----------+-----------+-----------------+--------+-----------+
| N  |           | 3\)       | i\) Bandwidth   |        |           |
| o. |           | 17.7‑20.2 | overlap, and    |        |           |
| ** |           | GHz,\     |                 |        |           |
| 9. |           | (Regions  | ii\) any        |        |           |
| 7\ |           | 2 and     | network in the  |        |           |
| ** |           | 3),\      | FSS and any     |        |           |
| GS |           | 17.3-20.2 | associated      |        |           |
| O/ |           | GHz\      | space operation |        |           |
| GS |           | (         | functions (see  |        |           |
| O\ |           | Region 1) | No. **1.23**)   |        |           |
| (  |           | and\      | with a space    |        |           |
| *c |           | 27.5‑30   | station within  |        |           |
| on |           | GHz       | an orbital arc  |        |           |
| t. |           |           | of  8° of the   |        |           |
| *) |           |           | nominal orbital |        |           |
|    |           |           | position of a   |        |           |
|    |           |           | proposed        |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | FSS             |        |           |
+----+-----------+-----------+-----------------+--------+-----------+
|    |           | 4\)       | i\) Bandwidth   |        |           |
|    |           | 17.3-     | overlap, and    |        |           |
|    |           | 17.7 GHz\ |                 |        |           |
|    |           | (         | ii\) a) any     |        |           |
|    |           | Regions 1 | network in the  |        |           |
|    |           | and 2)    | FSS and any     |        |           |
|    |           |           | associated      |        |           |
|    |           |           | space operation |        |           |
|    |           |           | functions (see  |        |           |
|    |           |           | No. **1.23**)   |        |           |
|    |           |           | with a space    |        |           |
|    |           |           | station within  |        |           |
|    |           |           | an orbital arc  |        |           |
|    |           |           | of 8° of the    |        |           |
|    |           |           | nominal orbital |        |           |
|    |           |           | position of a   |        |           |
|    |           |           | proposed        |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | BSS             |        |           |
|    |           |           |                 |        |           |
|    |           |           | *or*            |        |           |
|    |           |           |                 |        |           |
|    |           |           | b\) any network |        |           |
|    |           |           | in the BSS and  |        |           |
|    |           |           | any associated  |        |           |
|    |           |           | space operation |        |           |
|    |           |           | functions (see  |        |           |
|    |           |           | No. **1.23**)   |        |           |
|    |           |           | with a space    |        |           |
|    |           |           | station within  |        |           |
|    |           |           | an orbital arc  |        |           |
|    |           |           | of 8° of the    |        |           |
|    |           |           | nominal orbital |        |           |
|    |           |           | position of a   |        |           |
|    |           |           | proposed        |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | FSS             |        |           |
+----+-----------+-----------+-----------------+--------+-----------+

TABLE 5-1 (*continued*)     (Rev.WRC‑07)

+----+-----------+-----------+-----------------+--------+-----------+
| ** | **Case**  | **        | **Thresh        | **     | **        |
| Re |           | Frequency | old/condition** | Calcul | Remarks** |
| fe |           | bands\    |                 | ation\ |           |
| re |           | (and      |                 | me     |           |
| nc |           | Region)   |                 | thod** |           |
| e\ |           | of the    |                 |        |           |
| o  |           | service\  |                 |        |           |
| f\ |           | for which |                 |        |           |
| A  |           | coor      |                 |        |           |
| rt |           | dination\ |                 |        |           |
| ic |           | is        |                 |        |           |
| le |           | sought**  |                 |        |           |
| 9  |           |           |                 |        |           |
| ** |           |           |                 |        |           |
+----+-----------+-----------+-----------------+--------+-----------+
| N  |           | 5\)       | i\) Bandwidth   |        |           |
| o. |           | 17.7      | overlap, and    |        |           |
| ** |           | -17.8 GHz |                 |        |           |
| 9. |           |           | ii\) a) any     |        |           |
| 7\ |           |           | network in the  |        |           |
| ** |           |           | FSS and any     |        |           |
| GS |           |           | associated      |        |           |
| O/ |           |           | space operation |        |           |
| GS |           |           | functions (see  |        |           |
| O\ |           |           | No. **1.23**)   |        |           |
| (  |           |           | with a space    |        |           |
| *c |           |           | station within  |        |           |
| on |           |           | an orbital arc  |        |           |
| t. |           |           | of 8° of the    |        |           |
| *) |           |           | nominal orbital |        |           |
|    |           |           | position of a   |        |           |
|    |           |           | proposed        |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | BSS             |        |           |
|    |           |           |                 |        |           |
|    |           |           | *or*            |        |           |
|    |           |           |                 |        |           |
|    |           |           | b\) any network |        |           |
|    |           |           | in the BSS and  |        |           |
|    |           |           | any associated  |        |           |
|    |           |           | space operation |        |           |
|    |           |           | functions (see  |        |           |
|    |           |           | No. **1.23**)   |        |           |
|    |           |           | with a space    |        |           |
|    |           |           | station within  |        |           |
|    |           |           | an orbital arc  |        |           |
|    |           |           | of 8° of the    |        |           |
|    |           |           | nominal orbital |        |           |
|    |           |           | position of a   |        |           |
|    |           |           | proposed        |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | FSS             |        |           |
|    |           |           |                 |        |           |
|    |           |           | > (See also     |        |           |
|    |           |           | >               |        |           |
|    |           |           |  No. **5.517**) |        |           |
+----+-----------+-----------+-----------------+--------+-----------+
|    |           | 6\) Bands | i\) Bandwidth   |        |           |
|    |           | above     | overlap, and    |        |           |
|    |           | 17.3 GHz, |                 |        |           |
|    |           | except    | ii\) any        |        |           |
|    |           | those     | network in the  |        |           |
|    |           | defined   | FSS and any     |        |           |
|    |           | in § 3)   | associated      |        |           |
|    |           |           | space operation |        |           |
|    |           |           | functions (see  |        |           |
|    |           |           | No. **1.23**)   |        |           |
|    |           |           | with a space    |        |           |
|    |           |           | station within  |        |           |
|    |           |           | an orbital arc  |        |           |
|    |           |           | of 8° of the    |        |           |
|    |           |           | nominal orbital |        |           |
|    |           |           | position of a   |        |           |
|    |           |           | proposed        |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | FSS (see also   |        |           |
|    |           |           | Resolution      |        |           |
|    |           |           | **901           |        |           |
|    |           |           | (WRC‑03)**)     |        |           |
+----+-----------+-----------+-----------------+--------+-----------+

TABLE 5-1 (*continued*)     (Rev.WRC‑07)

+----+-----------+-----------+-----------------+--------+-----------+
| ** | **Case**  | **        | **Thresh        | **     | **        |
| Re |           | Frequency | old/condition** | Calcul | Remarks** |
| fe |           | bands\    |                 | ation\ |           |
| re |           | (and      |                 | me     |           |
| nc |           | Region)   |                 | thod** |           |
| e\ |           | of the    |                 |        |           |
| o  |           | service\  |                 |        |           |
| f\ |           | for which |                 |        |           |
| A  |           | coor      |                 |        |           |
| rt |           | dination\ |                 |        |           |
| ic |           | is        |                 |        |           |
| le |           | sought**  |                 |        |           |
| 9  |           |           |                 |        |           |
| ** |           |           |                 |        |           |
+----+-----------+-----------+-----------------+--------+-----------+
| N  |           | 7\) Bands | i\) Bandwidth   |        |           |
| o. |           | above     | overlap, and    |        |           |
| ** |           | 17.3 GHz, |                 |        |           |
| 9. |           | except    | ii\) any        |        |           |
| 7\ |           | those     | network in the  |        |           |
| ** |           | defined   | FSS or BSS, not |        |           |
| GS |           | in § 4)   | subject to a    |        |           |
| O/ |           | and 5)    | Plan, and any   |        |           |
| GS |           |           | associated      |        |           |
| O\ |           |           | space operation |        |           |
| (  |           |           | functions (see  |        |           |
| *c |           |           | No. **1.23**)   |        |           |
| on |           |           | with a space    |        |           |
| t. |           |           | station within  |        |           |
| *) |           |           | an orbital arc  |        |           |
|    |           |           | of 16° of the   |        |           |
|    |           |           | nominal orbital |        |           |
|    |           |           | position of a   |        |           |
|    |           |           | proposed        |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | FSS or BSS, not |        |           |
|    |           |           | subject to a    |        |           |
|    |           |           | Plan, except in |        |           |
|    |           |           | the case of a   |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | FSS with        |        |           |
|    |           |           | respect to a    |        |           |
|    |           |           | network in the  |        |           |
|    |           |           | FSS (see also   |        |           |
|    |           |           | R               |        |           |
|    |           |           | esolution **901 |        |           |
|    |           |           | (WRC‑03)**)     |        |           |
+----+-----------+-----------+-----------------+--------+-----------+
|    |           | 8\) All   | i\) Bandwidth   | Ap     | In        |
|    |           | frequency | overlap, and    | pendix | ap        |
|    |           | bands,    |                 | **8**  | plication |
|    |           | other     | ii\) Value of   |        | of        |
|    |           | than      | *T*/*T* exceeds |        | Article   |
|    |           | those in  | 6%              |        | 2A of     |
|    |           | 1), 2),   |                 |        | Appendix  |
|    |           | 3), 4),   |                 |        | **30**    |
|    |           | 5), 6)    |                 |        | for the   |
|    |           | and 7),   |                 |        | space     |
|    |           | allocated |                 |        | operation |
|    |           | to a      |                 |        | functions |
|    |           | space     |                 |        | using the |
|    |           | service,  |                 |        | g         |
|    |           | and the   |                 |        | uardbands |
|    |           | bands in  |                 |        | defined   |
|    |           | 1), 2),   |                 |        | in § 3.9  |
|    |           | 3), 4),   |                 |        | of Annex  |
|    |           | 5), 6)    |                 |        | 5 of      |
|    |           | and 7)    |                 |        | Appendi   |
|    |           | where the |                 |        | x **30**, |
|    |           | radio     |                 |        | the       |
|    |           | service   |                 |        | t         |
|    |           | of the    |                 |        | hreshold/ |
|    |           | proposed  |                 |        | condition |
|    |           | network   |                 |        | specified |
|    |           | or        |                 |        | for the   |
|    |           | affected  |                 |        | FSS in    |
|    |           | networks  |                 |        | the bands |
|    |           | is other  |                 |        | in 2)     |
|    |           | than the  |                 |        | applies.  |
|    |           | space     |                 |        |           |
|    |           | services  |                 |        | In        |
|    |           | listed in |                 |        | ap        |
|    |           | the       |                 |        | plication |
|    |           | t         |                 |        | of        |
|    |           | hreshold/ |                 |        | Article   |
|    |           | condition |                 |        | 2A of     |
|    |           | column,   |                 |        | Appendi   |
|    |           | or in the |                 |        | x **30A** |
|    |           | case of   |                 |        | for the   |
|    |           | coo       |                 |        | space     |
|    |           | rdination |                 |        | operation |
|    |           | of space  |                 |        | functions |
|    |           | stations  |                 |        | using the |
|    |           | operating |                 |        | g         |
|    |           | in the    |                 |        | uardbands |
|    |           | opposite  |                 |        | defined   |
|    |           | direction |                 |        | in § 3.1  |
|    |           | of        |                 |        | and 4.1   |
|    |           | tra       |                 |        | of Annex  |
|    |           | nsmission |                 |        | 3 of      |
|    |           |           |                 |        | Appendix  |
|    |           |           |                 |        |  **30A**, |
|    |           |           |                 |        | the       |
|    |           |           |                 |        | t         |
|    |           |           |                 |        | hreshold/ |
|    |           |           |                 |        | condition |
|    |           |           |                 |        | specified |
|    |           |           |                 |        | for the   |
|    |           |           |                 |        | FSS in    |
|    |           |           |                 |        | the bands |
|    |           |           |                 |        | in 4)     |
|    |           |           |                 |        | applies   |
+----+-----------+-----------+-----------------+--------+-----------+
| \. |           |           |                 |        |           |
| .. |           |           |                 |        |           |
+----+-----------+-----------+-----------------+--------+-----------+

**Reasons:** These modifications to Table 5-1 of Appendix 5 incorporate
the results of ITU‑R studies that conclude that a coordination arc of
±8º between Region 2 BSS and Regions 1 and 3 FSS in the bands
17.3-17.8 GHz is sufficient for triggering coordination between these
services. These modifications also note that No. 5.517 applies in the
band 17.7-17.8 GHz.

**NOC** IAP/14A2/158

RESOLUTION 901 (WRC-03)

Determination of the orbital arc separation for which coordination would
be required between two satellite networks operating in a space\
service not subject to a Plan

**Reasons:** The study called for in this Resolution is still valid for
other cases not yet addressed by the ITU‑R.

Other closely related proposals for modifying the Table of Frequency
Allocations

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/159

**5.517** In Region 2 use of the fixed-satellite (space-to-Earth)
service in the band 17.7-17.8 GHz shall not claim protection from and
shall not cause harmful interference to operating systems in the
broadcasting-satellite service.

**Reasons:** Modifications to this footnote are consequential to the 1
April 2007 date having passed.

**SUP** IAP/14A2/160

**5.518**

**Reasons:** Suppression of this Radio Regulation provision is
consequential to the 31 March 2007 date having passed.

**MOD** IAP/14A2/161

15.4-18.4 GHz

+-----------------------+-----------------------+-----------------------+
| Allocation to         |                       |                       |
| services              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| Region 1              | Region 2              | Region 3              |
+-----------------------+-----------------------+-----------------------+
| **17.3-17.7**         | **17.3-17.7**         | **17.3-17.7**         |
|                       |                       |                       |
| FIXED-SATELLITE\      | FIXED-SATELLITE\      | FIXED-SATELLITE\      |
| (Earth-to-space)      | (Earth-to-space)      | (Earth-to-space)      |
| 5.516\                | 5.516                 | 5.516                 |
| (space-to-Earth)      |                       |                       |
| 5.516A 5.516B         | B                     | Radiolocation         |
|                       | ROADCASTING-SATELLITE |                       |
| Radiolocation         |                       |                       |
|                       | Radiolocation         |                       |
+-----------------------+-----------------------+-----------------------+
| 5.514                 | 5.514 5.515           | 5.514                 |
+-----------------------+-----------------------+-----------------------+
| **17.7-18.1**         | **17.7-17.8**         | **17.7-18.1**         |
|                       |                       |                       |
| FIXED                 | FIXED                 | FIXED                 |
|                       |                       |                       |
| FIXED-SATELLITE\      | FIXED-SATELLITE\      | FIXED-SATELLITE\      |
| (space-to-Earth)      | (space-to-Earth)\     | (space-to-Earth)      |
| 5.484A\               | (Earth-to-space)      | 5.484A\               |
| (Earth-to-space)      | 5.516                 | (Earth-to-space)      |
| 5.516                 |                       | 5.516                 |
|                       | B                     |                       |
| MOBILE                | ROADCASTING-SATELLITE | MOBILE                |
|                       |                       |                       |
|                       | Mobile                |                       |
|                       |                       |                       |
|                       | 5.515 MOD 5.517       |                       |
+-----------------------+-----------------------+-----------------------+
|                       | \...                  |                       |
+-----------------------+-----------------------+-----------------------+

**Reasons:** Modifications to the table are consequential to the
modifications made to the wording of No. 5.517 and the suppression of
No. 5.518.

Proposal for Agenda item 1.12: Provisions of Radio Regulation No. 11.47

Background information

WRC‑03 identified in Resolution 86 (WRC‑03) the scope and the criteria
to be used for the implementation of Resolution 86 (Rev. Marrakesh,
2002). *Resolves* 1 of Resolution 86 (WRC‑03) specifically states that
WRC‑07 should "\... consider any proposals which deal with deficiencies
in the advance publication, coordination and notification procedures of
the Radio Regulations for space services which have either been
identified by the Board and included in the Rules of Procedure or which
have been identified by administrations or by the Radiocommunication
Bureau as appropriate;". WRC‑03 also resolved that future WRCs consider
any proposals that are intended to transform the content of the Rules of
Procedure into regulatory text.

WRC‑03 modified No. 11.44 by suppressing the possibility of extension of
the date of bringing into use. However, WRC‑did not modify the
provisions of No. 11.47 which still refers to an "extension granted
under No. **11.44**". In light of this decision, ITU‑R has concluded
that these provisions should be amended in order to be consistent with
the decision taken by WRC‑03 on No. 11.44.

In addition, No. 11.47 states that "\... Any frequency assignment
provisionally recorded under this provision shall be brought into use by
the date specified in the notice ..." It has been noted that the date of
bringing into use specified in the notice is an anticipated date,
subject to change. The Rule of Procedure (RoP) on No. 11.47 addresses
the procedures to be followed by the Radiocommunication Bureau (BR) when
the responsible administration fails to notify the bringing into use of
provisionally recorded assignments by the date recorded in the Master
Register. This RoP provides the notifying administration with the
possibility to modify this expected date of bringing into use without
any justification, as long as the new date falls within the limits
prescribed in No. 11.44. It should, therefore, be recognized that the
assignment should not be cancelled if it is not brought into use by the
expected date of bringing into use, but only the non-respect of the
7-year period should lead to cancellation.

No. 11.47 also refers to the provisional recording of assignments to
terrestrial stations, as it mentions the extension provided under
No. 11.45. ITU‑R has concluded that no change should be made in this
area.

This proposal modifies the provisions of No. 11.47 to suppress the
reference to any extension granted under No. 11.44, consistent with the
decisions of WRC‑03 to modify No. 11.44. It is also proposed to remove
the requirement to bring into use assignments to space stations
provisionally recorded in the Master Register by the date specified in
the notice, as this date is considered as an expected date of bringing
into use and the only regulatory deadline is the latest date provided by
No. 11.44. Under this approach, it is proposed that the Bureau send a
reminder only when the administration fails to advise the Bureau that
the provisionally recorded assignment has been brought into use in
accordance with No. 11.44. It is further proposed that, with these
modifications, the RoP associated with No. 11.47 can be suppressed.

Finally, it is proposed not to amend the provisions of No. 11.47 in
respect of terrestrial services. It is proposed to modify No. 11.47 as
shown in Section 6/1.12/4 of the CPM Report.

ARTICLE 11

Notification and recording of frequency\
            assignments**^1^**, **^2^**, **^3^**, **^3^**, **^3^**,
**^6^**     (WRC-03)

**MOD** IAP/14A2/162

**11.47** All frequency assignments notified in advance of their being
brought into use shall be entered provisionally in the Master Register.
Any frequency to a space station assignment provisionally recorded under
this provision shall be brought into use no later than the end of the
period provided under No. **11.44**. Any other frequency assignment
provisionally recorded under this provision shall be brought into use by
the date specified in the notice, or by the extension granted under
No. **11.45**, as the case may be. Unless the Bureau has been informed
by the notifying administration of the bringing into use of the
assignment, it shall, no later than fifteen days before the notified
date of bringing into use, in the case of an earth station, or the end
of the regulatory period established under No. **11.44** or
No. **11.45**, as appropriate, send a reminder requesting confirmation
that the assignment has been brought into use within the regulatory
period. If the Bureau does not receive that confirmation within thirty
days following the notified date of bringing into use, in the case of an
earth station, or the period provided under No. **11.44** or
No. **11.45**, as the case may be, it shall cancel the entry in the
Master Register. The Bureau shall inform the administration concerned
before taking such action.

**Reasons:**

1\) To address the inconsistency created with the modification of
No. 11.44 at WRC‑03.

2\) To remove the regulatory nature associated with the notified date of
bringing into use assignments provisionally recorded in the Master
Register.

3\) To incorporate the associated rules of procedure outlining the
actions to be taken by the Bureau and the filing administration should
the Bureau not be advised that assignments provisionally recorded in the
Master Register have been brought into use by the latest date prescribed
by Nos. 11.44 or 11.45 as applicable.

4\) To reduce the administrative burdens on the BR in managing this
process.

Proposal for Agenda item 1.12: Appendix 7 Table 10 for ground-based
earth stations and aircraft terrestrial stations

Background information

Resolution 86 (Rev. Marrakesh, 2002) requested that WRC‑03 and
subsequent Conferences review the regulatory procedures associated with
the advance publication, coordination, notification and recording of
frequency assignments pertaining to satellite network. WRC‑03 identified
in Resolution 86 (WRC‑03) the scope and the criteria to be used for the
implementation of Resolution 86 (Rev. Marrakesh, 2002). *Resolves* 1 of
Resolution 86 (WRC‑03) specifically states that WRC‑07 should "\...
consider any proposals which deal with deficiencies in the advance
publication, coordination and notification procedures of the Radio
Regulations for space services which have either been identified by the
Board and included in the Rules of Procedure or which have been
identified by administrations or by the Radiocommunication Bureau as
appropriate;".

A review of Appendix 7, Table 10 (Predetermined coordination distance)
indicates that the case of ground-based earth stations and aircraft
terrestrial stations, except for those specifically identified cases in
the table, is missing. In the past the Radiocommunication Bureau has
used the predetermined distance of 500 km for this case, e.g. see
Document RRB98/134(Rev.1) dated 8 December 1998. This coordination
distance was derived assuming line-of-sight propagation between the
aircraft and ground-based stations with a 4/3 Earth radius and the
aircraft altitude of 12 km. The 500 km is consistent with the distance
currently applicable to the similar cases of coordination between
aircraft and ground-based stations such as i) ground-based earth
stations in the bands below 1 GHz to which No. 9.11A
applies/ground-based mobile in the bands within the range 1‑3 GHz to
which No. 9.11A applies and aircraft (mobile) terrestrial stations; ii)
aircraft (mobile) earth stations and ground-based terrestrial stations;
and iii) non-GSO MSS feeder-link earth stations and aircraft (mobile)
terrestrial stations. To cover the case of ground-based earth stations
and aircraft terrestrial stations, Table 10 needs to be modified to
include this case with a coordination distance of 500 km. The proposal
does not apply to frequency bands already covered in Table 10.

APPENDIX 7 (Rev.WRC-03)

**Methods for the determination of the coordination area around an
earth\
station in frequency bands between 100 MHz and 105 GHz**

ANNEX 7

System parameters and predetermined coordination distances for\
determination of the coordination area around an earth station

**MOD** IAP/14A2/163

TABLE 10     (WRC-03)

Predetermined coordination distances

  ---------------------- ----------------- -------------------------------
  Frequency sharing                        Coordination distance (in
  situation                                sharing\
                                           situations involving services\
                                           allocated with equal rights)\
                                           (km)

  Type of earth station  Type of           
                         terrestrial       
                         station           

  \...                                     

  Ground-based           Mobile (aircraft) 500
                         (all bands not    
                         included          
                         elsewhere in      
                         Table 10)         
  ---------------------- ----------------- -------------------------------

**Reasons:** For No. 9.17, this modification is needed to cover the case
of ground-based earth stations and aircraft terrestrial stations.

Proposal for Agenda item 1.12: Appendix 4 data element (C.8.d.2)
contiguous satellite bandwidth

Background information

WRC‑03 reviewed Annex 2 of Radio Regulations Appendix 4. Among the
modifications, WRC‑03 added an item C.8.d.2 "Contiguous satellite
bandwidth". This item was introduced in Radio Regulations Appendix 4 in
order to cover the specific cases where a transmitting satellite
transponder would operate in a multi-carrier mode, where the aggregate
bandwidth of the transmitted carriers would be different and lower than
the transponder bandwidth.

This item was introduced in Radio Regulations Appendix 4 in order to
help administrations to conduct coordination in these cases of
multi-carrier transmissions. The relationship between this item and item
C.3.a "Bandwidth of the assigned frequency band" is considered here. It
is proposed to modify Appendix 4 as shown in Section 6/1.12/7 of the CPM
Report.

**MOD** IAP/14A2/164

APPENDIX 4 (Rev.WRC‑07)

Consolidated list and tables of characteristics for use in the\
application of the procedures of Chapter III

**Reasons:** Consequential to the modification of item C.8.d.2 of
Annex 2 of Appendix 4 of the Radio Regulations.

MOD IAP/14A2/165

ANNEX 2

**Characteristics of satellite networks, earth stations\
or radio astronomy stations2**     (WRC-07)

**Reasons:** Consequential to the modification of item C.8.d.2 of
Annex 2 of Appendix 4 of the Radio Regulations.

**MOD** IAP/14A2/166

Table of characteristics to be submitted for space and radio astronomy
services (WRC-03)

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 29%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 3%" />
</colgroup>
<thead>
<tr class="header">
<th><strong>Items in Appendix</strong></th>
<th><em><strong>C <sup>_</sup> CHARACTERISTICS TO BE PROVIDED FOR EACH
GROUP OF FREQUENCY ASSIGNMENTS FOR A SATELLITE ANTENNA BEAM OR AN EARTH
STATION OR RADIO ASTRONOMY ANTENNA</strong></em></th>
<th><strong>Advance publication of a geostationary-satellite
network</strong></th>
<th><strong>Advance publication of a non-geostationary-satellite network
subject to coordination under Section II of Article 9</strong></th>
<th><strong>Advance publication of a non-geostationary-satellite network
not subject to coordination under Section II of Article 9</strong></th>
<th><strong>Notification or coordination of a geostationary-satellite
network (including space operation functions under Article 2A of
Appendices 30 or 30A)</strong></th>
<th><strong>Notification or coordination of a
non-geostationary-satellite network</strong></th>
<th><strong>Notification or coordination of an earth station (including
notification under Appendices 30A or 30B)</strong></th>
<th><strong>Notice for a satellite network in the broadcasting-satellite
service under Appendix 30 (Articles 4 and 5)</strong></th>
<th><strong>Notice for a satellite network (feeder-link) under
Appendix 30A (Articles 4 and 5)</strong></th>
<th><strong>Notice for a satellite network in the fixed-satellite
service under Appendix 30B (Articles 6 and 8)</strong></th>
<th><strong>Items in Appendix</strong></th>
<th><strong>Radio astronomy</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>...</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td rowspan="3">C.8.d.2</td>
<td><blockquote>
<p>each contiguous satellite bandwidth</p>
</blockquote></td>
<td rowspan="3"></td>
<td rowspan="3"></td>
<td rowspan="3"></td>
<td rowspan="3"><strong>+</strong></td>
<td rowspan="3"><strong>+</strong></td>
<td rowspan="3"></td>
<td rowspan="3"></td>
<td rowspan="3"></td>
<td rowspan="3"></td>
<td rowspan="3">C.8.d.2</td>
<td rowspan="3"><strong> </strong></td>
</tr>
<tr class="odd">
<td><blockquote>
<p>For the maximum saturated peak envelope power of the satellite
transponder, this corresponds to the bandwidth of each transponder</p>
</blockquote></td>
</tr>
<tr class="even">
<td><blockquote>
<p>Required only for a space-to-Earth or space-to-space link, and only
if different from item C.3.a</p>
</blockquote></td>
</tr>
<tr class="odd">
<td>...</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

**Reasons:** To modify Annex 2 to Radio Regulations Appendix 4, in order
to request the submission of item C.8.d.2 only if it is different from
the item C.3.a.

Proposal for Agenda item 1.12: Resolution 88 (WRC‑03)

Background information

Resolution 88 (WRC‑03) resolves that WRC‑07 review the results of
studies to be undertaken by the ITU‑R on the rationalization of Radio
Regulations Articles 9 and 11, taking due account of RR No. 0.3, and
take appropriate action. It is proposed to suppress Resolution 88
(WRC‑03) as shown in Section 6/1.12/8 of the CPM Report.

**SUP** IAP/14A2/167

RESOLUTION 88 (WRC‑03)

Rationalization of Articles 9 and 11 of the Radio Regulations

**Reasons:** Suppression of Resolution 88 (WRC‑03) is appropriate
because of the potential disadvantages from rationalization of
Articles 9 and 11 of the Radio Regulations.

Proposal for Agenda item 1.12: Coordination of the
radionavigation-satellite service (space-to-space) in the bands
1 215-1 300 MHz and 1 559-1 610 MHz

Background information

The scope and criteria to be used for the implementation of
Resolution 86 (Rev. Marrakesh, 2002) of the Plenipotentiary Conference
by future world radiocommunication conferences (WRCs) is established in
Resolution 86 (WRC‑03). *Resolves* 1 of Resolution 86 (WRC‑03) relates
to the consideration of proposals dealing with deficiencies in the
advance publication, coordination and notification procedures of the
Radio Regulations for space services, and *resolves* 2 relates to
consideration of proposals intended to transform the content of the
Rules of Procedure into regulatory text.

WRC‑2000 added the space-to-space direction to the existing
radionavigation-satellite service (RNSS) (space-to-Earth) allocations in
the bands 1 215-1 300 MHz and 1 559-1 610 MHz, along with footnote
5.329A. WRC‑03 added footnote 5.328B, which applied coordination between
two non-GSO RNSS systems and between non-GSO and GSO RNSS systems in the
bands 1 164-1 300 MHz, 1 559-1 610 MHz and 5 010-5 030 MHz under Nos.
9.12, 9.12A and 9.13 after 1 January 2005, without specifying direction
(i.e. space-to-Earth or space-to-space). Coordination between GSO RNSS
systems in the same bands (space-to-Earth and space-to-space) is covered
by No. 9.7, again without specifying direction (i.e. space-to-Earth or
space-to-space).

No. 9.11A applies the coordination provisions of Nos. 9.12 to 9.16 where
the requirement to coordinate is included in a footnote to the Table of
Frequency Allocations referring to No. 9.11A. Since WRC‑2000, the Rules
of Procedure (RoP), issued by the Radio Regulations Board (RRB), rather
than the Radio Regulations have defined the services and frequency bands
for which the coordination procedure under No. 9.11A is required. The
RRB considered the application of No. 9.11A to the bands given in
No. 5.329A (i.e. 1 215-1 300 and 1 559-1 610 MHz) and interpreted the
Regulations as excluding RNSS (space-to-space) assignments in the bands
given in No. 5.329A from any obligation to coordinate with other
services and with RNSS (space-to-Earth), but as obliging these RNSS
(space-to-space) assignments to coordinate with each other.

In addition, many RNSS (space-to-space) network assignments are
receive-only in the bands 1 215-1 300 MHz and 1 559-1 610 MHz.
Resolution 610 (WRC‑03), as referenced in No. 5.328B, requires
administrations to provide evidence of binding agreements for the
manufacture, procurement, and launch of RNSS systems and networks. This
resolution was intended to aid bilateral coordination between
transmitting RNSS systems and networks by ensuring such systems are
either in operation or in the process of being implemented. Requiring
Resolution 610 (WRC‑03) data for receiving space stations is
unnecessary.

Therefore, modifications to No. 5.329A and No. 5.328B are needed to
reflect the RRB decision that requires RNSS (space-to-space) to
coordinate only with other RNSS (space-to-space) but not with other
services or with RNSS (space-to-Earth), and to remove Resolution 610
(WRC‑03) obligations from RNSS receiving space stations. Additionally,
to ensure that the obligation on RNSS (space-to-space) networks under
No. 5.329A is also adequately reflected for geostationary RNSS
(space-to-space) networks with respect to GSO RNSS (space-to-Earth)
networks in the 1 215-1 300 MHz and 1 559-1 610 MHz bands (a
coordination scenario not encompassed by Nos. 9.12, 9.12A, and 9.13),
the modification to No. 5.328B refers as well to No. 9.7.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/168

**5.328B** The use of the bands 1 164-1 300 MHz, 1 559-1 610 MHz and
5 010-5 030 MHz by systems and networks in the radionavigation-satellite
service for which complete coordination or notification information, as
appropriate, is received by the Radiocommunication Bureau after
1 January 2005 is subject to the application of the provisions of
Nos. **9.12**, **9.12A** and **9.13**. Resolution **610** **(WRC‑03)**
shall also apply; however, in the case of the radionavigation-satellite
service (space-to-space) networks and systems, Resolution **610
(WRC‑03)** shall only apply to transmitting space stations. In
accordance with No. **5.329A**, for systems and networks in the
radionavigation-satellite service (space-to-space) in the bands
1 215‑1 300 MHz and 1 559-1 610 MHz the provisions of Nos. **9.7**,
**9.12**, **9.12A** and **9.13** shall only apply with respect to other
systems and networks in the radionavigation-satellite service
(space-to-space).     (WRC-07)

**Reasons:** To make it clear that the application of the coordination
procedure in Nos. 9.7, 9.12, 9.12A and 9.13 to RNSS (space-to-space)
systems and networks is only with respect to other
radionavigation-satellite service (space-to-space) systems and networks
in the bands 1 215-1 300 MHz and 1 559-1 610 MHz and to limit the
application of Resolution 610 (WRC‑03) to transmitting space stations.

**MOD** IAP/14A2/169

**5.329A** Use of systems in the radionavigation-satellite service
(space-to-space) operating in the bands 1 215-1 300 MHz and 1 559-1 610
MHz is not intended to provide safety service applications, and shall
not impose any additional constraints on radionavigation-satellite
service (space-to-Earth) systems or on other services operating in
accordance with the Table of Frequency Allocations.     (WRC‑07)

**Reasons:** To clarify that "other systems" in No. 5.329A refers to the
radionavigation-satellite service (space-to-Earth) and that "services"
refers to services other than the radionavigation-satellite service.

Proposal for Agenda item 1.12: Provisions of Radio Regulations No. 11.49

Background information

The provisions of Radio Regulations No. 11.49 are mainly applied by
administrations in the case of malfunction of a satellite and allow the
continuation of the rights of the assignment to be protected. ITU‑R has
concluded that two years, as provided in RR No. 11.49, is the
appropriate period for the malfunctioning spacecraft to be replaced to
allow for actual situations.

ARTICLE 11

Notification and recording of frequency\
            assignments**^1^**, **^2^**, **^3^**, **^4^**, **^5^**,
**^6^**     (WRC-03)

**NOC** IAP/14A2/170

**11.49** Where the use of a recorded assignment to a space station is
suspended for a period not exceeding eighteen months, the notifying
administration shall, as soon as possible, inform the Bureau of the date
on which such use was suspended and the date on which the assignment is
to be brought back into regular use. This latter date shall not exceed
two years from the date of suspension.

**Reasons:** ITU‑R has concluded that two years, as provided in Radio
Regulations No. 11.49, is the appropriate period for the malfunctioning
spacecraft to be replaced to allow for actual situations and that there
should be no changes in the provisions of RR No. 11.49.

Proposal for Agenda item 1.12: Provisions of Radio Regulations No. 9.1

Background information

There has been a longstanding requirement in Article 9 of the Radio
Regulations, under No. 9.1, for the Radiocommunications Bureau to wait a
requisite six months after receiving the advanced publication
information for satellite networks requiring coordination under Section
II of Article 9 before receiving the accompanying coordination request
information, even if both sets of information are submitted to the
Bureau at the same time. While this six-month delay may have served a
purpose in years past when there was a substantial amount of technical
data included in the API for administrations to consider and potentially
comment upon, this is no longer the case. As a consequence of the
simplification of the Radio Regulations at WRC‑95, the API for satellite
networks requiring coordination under Section II of Article 9 includes
very limited information, e.g. orbital position and frequency bands, and
as such, there is little for administrations to review and comment upon.
In addition, this six month delay has the effect of adding uncertainty
into the possible availability of orbital slots, as conflicting
coordination requests associated with other, earlier filed APIs, may be
received by the BR during the six month period thereby making a
previously available orbital slot no longer available. This required six
month delay therefore serves no purpose other than to delay the overall
coordination process for satellite networks and add uncertainty as to
the possible availability of orbital slots.

ARTICLE 9

Procedure for effecting coordination with or\
            obtaining agreement of other administrations**^1^**,
**^2^**, **^3^**, **^4^**, **^5^**, **^6^**, **^7^**,
**^8^**     (WRC-03)

Section I -- Advance publication of information on satellite\
networks or satellite systems

General

**MOD** IAP/14A2/171

**9.1** Before initiating any action under this Article or under
Article **11** in respect of frequency assignments for a satellite
network or a satellite system, an administration, or one^9^ acting on
behalf of a group of named administrations, shall, prior to the
coordination procedure described in Section II of Article **9** below,
where applicable, send to the Bureau a general description of the
network or system for advance publication in the International Frequency
Information Circular (BR IFIC) not earlier than seven years and
preferably not later than two years before the planned date of bringing
into use of the network or system (see also No. **11.44**). The
characteristics to be provided for this purpose are listed in Appendix
**4**. The coordination or notification information may also be
communicated to the Bureau at the same time. When coordination is
required by Section II of Article **9**, the coordination information
shall be considered as having been received by the Bureau upon the date
of receipt of the complete information. Where coordination is not
required by Section II, notification shall be considered as having been
received by the Bureau not earlier than six months after the date of
publication of the advance publication information.     (WRC-07)

**Reasons:** To address the unnecessary requirement for the
Radiocommunications Bureau to wait six months after receipt of the
advanced publication information before receiving the coordination
request information for satellite networks requiring coordination under
Section II of Article 9.

Proposal for Agenda item 1.12: Resolution 86 (WRC‑03)

Background information

Resolution 86 (Rev. Marrakesh, 2002) deals with the review and update of
the various procedures (advance publication, coordination, notification
and recording in the MIFR) for frequency assignments pertaining to
satellite networks. This Resolution was initially adopted by PP-98 after
an in-depth review of these procedures was conducted by the VGE
(Voluntary Group of Experts) and induced profound modifications in the
Radio Regulations. The main purpose of this Resolution is to invite the
WRCs to review and update the various steps in the regulatory procedures
for space networks/systems.

PP-02 modified this Resolution by settling the global framework of the
review of the space procedures, including aspects related to equitable
access to the orbit/spectrum resource and to cost savings in BR and the
administrations. PP-02 also invited WRC‑03 to determine the scope and
criteria to be used for the implementation of this Resolution.

In response to this invitation, WRC‑03 adopted Resolution 86 (WRC‑03)
which contains the various criteria to be used in the context of the
corresponding WRC agenda item. The 2006 Plenipotentiary Conference
considered modifying Resolution 86 (Rev. Marrakesh, 2002) and concluded
not to change that Resolution due to the disagreement on the scope of
modification. However, PP-06 decided to invite WRC‑07 to consider the
matter further and report to PP-10.

**NOC** IAP/14A2/172

RESOLUTION 86 (WRC‑03)

Scope and criteria to be used for the implementation of\
Resolution 86 (Rev. Marrakesh, 2002) of the\
Plenipotentiary Conference

**Reasons:** As stated in view B in Section 6/1.12/14.2 of the CPM
Report, the framework provided by Resolution 86 (WRC‑03) is satisfactory
and it should be retained.

Proposal for Agenda item 1.12: Application of the provisions of Radio
Regulations No. 9.14

Background information

The Rule of Procedure on Radio Regulation No. 9.11A specifies in
§ 2.4 *a)* that "No. **9.14** applies to space-to-Earth frequency
allocations only, i.e. coordination of a transmitting space station in
respect of receiving terrestrial stations when the threshold value is
exceeded. In the absence of threshold value, the provisions of
No. **9.50.1** could apply (see also Appendix **5**) \...".

Considering that this Rule has not raised difficulties and can be
translated in RR text, it is proposed to amend the wording of RR
No. 9.14 to reflect the Rule of Procedure. Consequently, the Rules of
Procedure on RR No. 9.14 related to this aspect should be suppressed.

ARTICLE 9

Procedure for effecting coordination with or\
            obtaining agreement of other administrations**^1^**,
**^2^**, **^3^**, **^4^**, **^5^**, **^6^**, **^7^**,
**^8^**     (WRC-03)

Section II -- Procedure for effecting coordination**^12^**, **^13^**

Sub-Section IIA -- Requirement and request for coordination

**MOD** IAP/14A2/173

**9.14** *i)* for a space station of a transmitting satellite network
for which the requirement to coordinate is included in a footnote to the
Table of Frequency Allocations referring to this provision or to
No. **9.11A** in respect of receiving stations of terrestrial services
where the threshold value is exceeded;     (WRC-07)

**Reasons:** To reflect the Rule of Procedure on No. 9.14, as shown in
Section 6/1.12/15 of the CPM Report.

Proposal for Agenda item 1.12: Nos. 9.15 to 9.18

Background information

Since WRC‑95, with the consideration and adoption of the report of the
Voluntary Group of Experts (VGE), at various WRCs several attempts have
been made to merge Radio Regulation No. 9.15 into RR No. 9.17 and RR
No. 9.16 into RR No. 9.18 due to the apparent similarity of these two
pairs of provisions. In fact RR No. 9.15 and RR No. 9.16 stem from
former Resolution 46 (WARC-92) and RR No. 9.17 and RR No. 9.18 stem from
former provisions RR1107 and RR1148 (Edition of 1990). However, after
lengthy discussion, these different WRCs have recognized that the
objectives and purposes of the two pairs mentioned above were entirely
different.

The merging of these two pairs would thus cause unforeseeable
difficulties. Incorporation/merging of provisions of RR No. 9.15 with RR
No. 9.17 and provisions of RR No. 9.16 with RR No. 9.18 is not
consistent with the letter and the spirit of the Radio Regulations. Such
incorporation/merging does not simplify the application of these
provisions and may create confusion for administrations in applying
these provisions.

ITU‑R has concluded that no change be made to these provisions.

ARTICLE 9

Procedure for effecting coordination with or\
            obtaining agreement of other administrations**^1^**,
**^2^**, **^3^**, **^4^**, **^5^**, **^6^**, **^7^**,
**^8^**     (WRC-03)

**NOC** IAP/14A2/174

**9.15** to **9.18**

**Reasons:** Nos. 9.15 to 9.18 of the Radio Regulations address
different coordination procedures and should remain without change as
stated in Section 6/1.12/16 of the CPM Report.

Proposal for Agenda item 1.12: Non-payment of satellite network cost
recovery for notification

Background information

WRC‑2000, as a result of including the consequences of non-payment of
cost recovery fees, modified footnotes in Article 9, Appendices 30, 30A,
and 30B. These footnotes provided that if payments were not received in
accordance with the provisions as set forth in Decision 482, as
modified, the Bureau would cancel the publication, after informing the
administration concerned. Council 05 approved a further modified
Decision 482, which extended satellite network cost recovery
requirements to notifications of satellite network filings. As a result
of this action, similar modifications are required for Article 11,
Appendices 30, 30A and 30B.

**MOD** IAP/14A2/175

ARTICLE 11

Notification and recording of frequency\
            assignments**^1^**, **^2^**, **^3^**, **^4^**, **^5^**,
**^6^**     (WRC-03)

**Reasons:** Consequential editorial change.

Section II -- Examination of notices and recording of frequency
assignments\
in the Master Register

**MOD** IAP/14A2/176

**11.28** Complete notices shall be marked by the Bureau with their date
of receipt and shall be examined in the date order of their receipt. On
receipt of a complete notice the Bureau shall, within no more than two
months, publish^10A^ its contents, with any diagrams and maps and the
date of receipt, in the BR IFIC which shall constitute the
acknowledgement to the notifying administration of receipt of its
notice. When the Bureau is not in a position to comply with the time
limit referred to above, it shall periodically so inform the
administrations, giving the reasons therefore.

**Reasons:** Add a footnote to point to new footnote 11.28.1 which takes
into account satellite network cost recovery requirements for
notification.

**ADD** IAP/14A2/177

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^10A^ **11.28.1** If the payments are not received in accordance with
the provisions of Council Decision 482, as amended, on the
implementation of cost recovery for notification of satellite network
filings, the Bureau shall cancel the publication, after informing the
administration concerned. The Bureau shall inform all administrations of
such action, and that the network specified in the publication in
question no longer has to be taken into consideration by the Bureau and
other administrations. The Bureau shall send a reminder to the notifying
administration not later than two months prior to the deadline for the
payment in accordance with Council Decision 482 unless the payment has
already been received. See also Resolution **87 (WRC‑03)**.

**Reasons:** : New footnote that takes into account Council 05 decision
to include notification in satellite network cost recovery requirements.

APPENDIX 30 (Rev.WRC-07)^\*^

Provisions for all services and associated Plans and List**^1^** for\
the broadcasting-satellite service in the frequency bands\
11.7-12.2 GHz (in Region 3), 11.7-12.5 GHz (in Region 1)\
             and 12.2-12.7 GHz (in Region 2)     (WRC-03)

              (See Articles **9** and **11**)     (WRC‑03)

**MOD** IAP/14A2/178

            ARTICLE 5     (Rev.WRC-07)

**Notification, examination and recording in the Master International\
Frequency Register of frequency assignments to space stations\
in the broadcasting-satellite service**

**Reasons:** Consequential editorial change.

**MOD** IAP/14A2/179

5.1.6 Upon receipt of a complete notice, the Bureau shall include^19A^
its particulars, with the date of receipt, in its BR IFIC, which shall
contain the particulars of all such notices received since the
publication of the previous Circular.     (WRC‑2000)

**Reasons:** Add a footnote to point to new footnote 19A which takes
into account satellite network cost recovery for notification.

**ADD** IAP/14A2/180

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^19A^ If the payments are not received in accordance with the provisions
of Council Decision 482, as amended, on the implementation of cost
recovery for notification of satellite network filings, the Bureau shall
cancel the publication, after informing the administration concerned.
The Bureau shall inform all administrations of such action, and that the
network specified in the publication in question no longer has to be
taken into consideration by the Bureau and other administrations. The
Bureau shall send a reminder to the notifying administration not later
than two months prior to the deadline for the payment in accordance with
Council Decision 482 unless the payment has already been received. See
also Resolution **87 (WRC‑03)**.

**Reasons:** New footnote that takes into account Council 05 decision to
include notification in satellite network cost recovery requirements.

APPENDIX 30A  (Rev.WRC‑03)\*

**Provisions and associated Plans and List1 for feeder links for the\
broadcasting-satellite service (11.7-12.5 GHz in Region 1, 12.2-12.7
GHz\
in Region 2 and 11.7-12.2 GHz in Region 3) in the frequency bands\
14.5-14.8 GHz2 and 17.3-18.1 GHz in Regions 1 and 3,\
and 17.3-17.8 GHz in Region 2**     (WRC‑03)

(See Articles **9** and **11**)     (WRC‑03)

**MOD** IAP/14A2/181

              ARTICLE 5     (Rev.WRC‑07)

Coordination, notification, examination and recording in the Master\
International Frequency Register of frequency assignments to\
feeder-link transmitting earth stations and receiving\
space stations in the fixed-satellite service**^21^**

**Reasons:** Consequential editorial change.

**MOD** IAP/14A2/182

5.1.10 Upon receipt of a complete notice, the Bureau shall include^23A^
its particulars, with the date of receipt, in its BR IFIC which shall
contain the particulars of all such notices received since the
publication of the previous Circular.

**Reasons:** Add a footnote to point to new footnote 23A which takes
into account satellite network cost recovery for notification.

**ADD** IAP/14A2/183

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^23A^ If the payments are not received in accordance with the provisions
of Council Decision 482, as amended, on the implementation of cost
recovery for notification of satellite network filings, the Bureau shall
cancel the publication, after informing the administration concerned.
The Bureau shall inform all administrations of such action, and that the
network specified in the publication in question no longer has to be
taken into consideration by the Bureau and other administrations. The
Bureau shall send a reminder to the notifying administration not later
than two months prior to the deadline for the payment in accordance with
Council Decision 482 unless the payment has already been received. See
also Resolution **87 (WRC‑03)**. 

**Reasons:** A new footnote that takes into account Council 05 decision
to include notification in satellite network cost recovery requirements.

APPENDIX 30B (Rev. WRC-2000)

**Provisions and associated Plan for the fixed-satellite service\
in the frequency bands 4 500-4 800 MHz, 6 725-7 025 MHz,\
10.70-10.95 GHz, 11.20-11.45 GHz and 12.75-13.25 GHz**

**MOD** IAP/14A2/184

ARTICLE 8     (WRC-07)

Procedure for notification and recording in the Master Register of\
assignments in the planned bands for the fixed-satellite service

**Reasons:** Consequential editorial change.

**MOD** IAP/14A2/185

8.5 Complete notices shall be marked by the Bureau with their date of
receipt and shall be examined in the date order of their receipt.
Following receipt of a complete notice the Bureau shall, within not more
than two months, publish^3A^ its contents, with any diagrams and maps
and the date of receipt, in the BR IFIC, which shall constitute the
acknowledgement to the notifying administration of receipt of its
notice. When the Bureau is not in a position to comply with the
time-limit referred to above, it shall periodically so inform the
administrations, giving the reasons therefor.     (WRC-03)

**Reasons:** Add a footnote to point to new footnote 3A which takes into
account satellite network cost recovery requirements for notification.

**ADD** IAP/14A2/186

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^3A^ If the payments are not received in accordance with the provisions
of Council Decision 482, as amended, on the implementation of cost
recovery for notification of satellite network filings, the Bureau shall
cancel the publication, after informing the administration concerned.
The Bureau shall inform all administrations of such action, and that the
network specified in the publication in question no longer has to be
taken into consideration by the Bureau and other administrations. The
Bureau shall send a reminder to the notifying administration not later
than two months prior to the deadline for the payment in accordance with
Council Decision 482 unless the payment has already been received. See
also Resolution **87 (WRC‑03)**. 

**Reasons:** New footnote that takes into account Council 05 decision to
include notification in satellite network cost recovery requirements.

It is noted that the date of entry into force of the modifications to
the Radio Regulations addressing the consequences of non-payment of
satellite network cost recovery fees for notification along with
appropriate modifications to Resolution 87 (WRC‑03) will also be needed.

**MOD** IAP/14A2/187

RESOLUTION 87 (Rev.WRC-03)

Date of entry into force of certain provisions of the Radio Regulations\
relating to the non-payment of cost‑recovery fees\
for the notification of satellite networks

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that WRC‑2000 adopted certain provisions in Article **9**,
Appendix **30**, Appendix **30A** and Appendix **30B** relating to the
consequences of non‑payment of cost-recovery fees as adopted by the
Council in Decision 482 and established a date of entry into force of 1
August 2003;

*b)* that Council 2005 modified Decision 482 to apply satellite network
cost recovery to all satellite network filings concerning notification
for recording of frequency assignments in the Master International
Frequency Register (Article **11** of the RR, Article 5 of
Appendices **30/30A** to the RR and Article 8 of Appendix **30B** to the
RR) received by the Radiocommunication Bureau on or after 1 January 2006
if they refer to advance publication or modification of the space
service plans or lists (Part A) or requests for the implementation of
the fixed-satellite service plan, as appropriate, received on or after
19 October 2002;

*c)* that WRC‑07 adopted certain provisions in Article **11**,
Appendix **30**, Appendix **30A** and Appendix **30B** relating to the
consequences of non‑payment of cost-recovery fees for notification of
satellite networks as adopted by the Council in Decision 482 (as
modified),

recognizing

that Resolution 88 (Rev. Marrakesh, 2002) of the Plenipotentiary
Conference recognizes that the provisions adopted by WRC‑2000
established a linkage between the rights acquired by Member States in
applying the relevant procedures of the Radio Regulations after
7 November 1998 and the payment of the fees for cost recovery for
satellite network filings,

noting

that the Director of the Radiocommunication Bureau has issued invoices
for cost recovery fees for notifications since 1 January 2006, as
indicated in *considering b)*,

resolves

1 that the date of entry into force of Nos. **11.28** and **11.28.1** in
Article **11**, § 5.16 of Appendix **30**, § 5.1.10 of Appendix **30A**
and § 8.5 of Appendix **30B** shall be\[17 November 2007\];

2 that satellite network filings subject to satellite network cost
recovery for notification in accordance with Decision 482 (modified
2005) as summarized in *considering b)* and for which complete
notification information was received by the Radiocommunication Bureau
before \[17 November 2007\], shall be cancelled if payment has not been
received by \[17 May 2008\],

instructs the Director of the Radiocommunication Bureau

to send, to the notifying administrations responsible for satellite
networks to which *resolves* 2 applies, a reminder concerning the
deadline for the payment in Council Decision 482 (modified 2005) and of
the consequences of non-payment according to *resolves* 2, not later
than two months prior to \[17 May 2008\], unless the payment has already
been received.

**Reasons:** To modify Resolution 87 (WRC‑03) provide a date of entry
into force for cost recovery for notifications of satellite networks.

#### Agenda item 1.13

1.13 taking into account Resolutions **729 (WRC‑97)**, **351**
**(WRC‑03)** and **544** **(WRC‑03)**, to review the allocations to all
services in the HF bands between 4 MHz and 10 MHz, excluding those
allocations to services in the frequency range 7 000-7 200 kHz and those
bands whose allotment plans are in Appendices **25**, **26** and **27**
and whose channelling arrangements are in Appendix **17**, taking
account of the impact of new modulation techniques, adaptive control
techniques and the spectrum requirements for HF broadcasting

Proposals for Agenda item 1.13

Background information

There are multiple services allocated to the HF bands between 4 MHz and
10 MHz, including aeronautical mobile (OR), aeronautical mobile (R),
amateur, broadcasting, fixed, maritime mobile and mobile services.
ITU‑R studies on this Agenda item have been divided into five issues as
discussed below.

-- Issue A -- Resolution 729 (WRC‑97)

-- Issue B -- Resolution 729 (WRC‑97)

-- Issue C -- Resolution 351 (WRC‑03)

-- Issue D -- Resolution 544 (WRC‑03)

-- Issue E -- General review of 4-10 MHz not covered by the Resolutions
above.

Issue (A) and (B): Resolution 729 (WRC‑97) *resolves* 2 and 3

Use of frequency adaptive systems in the MF and HF bands.

-- *resolves* 2 -- that frequency adaptive systems shall automatically
limit simultaneous use of frequencies to the minimum necessary for
communication requirements;

-- *resolves* 3 -- that with a view to avoiding harmful interference,
the system should evaluate the channel occupancy prior to and during
operation.

This Resolution outlines the use of frequency adaptive systems in the MF
and HF bands and *invites ITU‑R* to pursue studies on the subject to
achieve optimum operational performance and compatibility and to report
on the results of these studies to a future world radiocommunication
conference.

Adaptive HF systems have been in use for over 20 years and no special
consideration in the ITU Radio Regulations is required to fully
implement adaptive HF systems. By their nature these systems already
automatically limit simultaneous use of frequencies to the minimum
necessary for communication requirements. These systems also
automatically avoid harmful interference by evaluating the channel
occupancy prior to and during operations. ITU‑R has also developed new
Recommendations and Reports as well as revisions to existing
Recommendations describing these systems and providing technical
characteristics of representative systems.

**ADD** IAP/14A2/188

RESOLUTION \[IAP/14A2/188\] (WRC‑07)

Bandwidth requirements for advanced fixed and mobile\
HF technologies in the 3-30 MHz band

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that in both the planned and unplanned portions of the 3-30 MHz
band fixed and mobile HF systems commonly use channel bandwidths up to
3 kHz, and many channel bandwidths are below 500 Hz;

*b)* that trials of advanced fixed and mobile HF frequency systems have
demonstrated their feasibility and their associated spectrum efficiency;

*c)* that advanced fixed and mobile HF frequency systems require larger
channel bandwidth assignments greater than the 3 kHz assignments that
are currently common,

noting

*a)* that some advanced fixed and mobile HF frequency adaptive systems
utilize bandwidths of up to 12 kHz to support HF electronic messaging,
HF Internet, and HF file transfer;

*b)* that aeronautical mobile (OR) and (R) services use the 3-30 MHz
range on a worldwide basis as defined in Appendices **26** and **27**
respectively,

resolves to invite ITU‑R

1 to determine the feasibility of changing the Radio Regulations related
to the fixed and mobile services to provide for the use of wider
bandwidths to support advanced adaptive fixed and mobile HF systems in
the 3-30 MHz band, excluding provisions related to the aeronautical
mobile (R) service found in Appendix **27**;

2 to study the impact of these advanced fixed and mobile systems on the
aeronautical mobile (OR) and (R) service channels in this range to
ensure that they shall not cause harmful interference to existing
aeronautical mobile (OR) and (R) systems;

3 not to consider changes to the allotment plan contained in
Appendix **26** unless other options to change the Radio Regulations are
inadequate to meet the requirement for wider bandwidths;

4 to bring the results of these studies to the attention of WRC‑\[11\].

**Reasons:** Urgent studies are required to determine the suitability of
changing the Radio Regulations to allow for wider bandwidths to the
fixed and mobile services to accommodate advanced HF adaptive systems.

Issue (C): Resolution 351 (WRC‑03)

**NOC** IAP/14A2/189

APPENDIX 17 (Rev.WRC-03)

Frequencies and channelling arrangements in the\
high-frequency bands for the maritime mobile service

**Reasons:** There are still several studies underway that need to be
completed prior to resolving this issue. IMO is still in the process of
developing HF data system performance requirements. These studies should
be completed prior to the next conference, where the appropriate changes
to the RR can be considered.

**MOD** IAP/14A2/190

RESOLUTION 351 (Rev.WRC-07)

Review of the frequency and channel arrangements in the MF and\
HF bands allocated to the maritime mobile service with a view to\
improving efficiency by considering the use of new digital\
technology by the maritime mobile service

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that the agenda of this Conference included consideration of the
use of new digital technology in the maritime mobile service (MMS) in
the MF and HF bands;

*b)* that the introduction of new digital technology in the MMS shall
not disrupt the distress and safety communications in the MF and HF
bands including those established by the International Convention for
the Safety of Life at Sea (SOLAS), 1974, as amended;

*c)* that changes made in Appendix **17** should not prejudice the
future use of these frequencies or the capabilities of systems or new
applications required for use by the MMS;

*d)* that the need to use new digital technologies in the MMS is growing
rapidly;

*e)* that the use of new digital technology on HF and MF frequencies
allocated to the MMS will make it possible to better respond to the
emerging demand for new services;

*f)* that the HF bands allocated to the MMS for A1A Morse telegraphy are
not used for this purpose and narrow-band direct-printing (NBDP)
allocations are utilized only by a small number of low-volume residual
services at present;

*g)* that there are new HF data exchange technologies capable of
delivering Maritime Safety Information (MSI);

*h)* that the IMO supports the frequencies of Appendix **15**,
concerning NBDP, be retained for the foreseeable future;

*i)* that the ITU Radiocommunication Sector is conducting ongoing
studies to improve the efficient use of these bands,

noting

*a)* that different digital technologies have already been developed and
are in use in the MF and HF bands in several radiocommunication
services;

*b)* that new maritime HF data transfer protocols have already been
developed to replace general narrow-band direct-printing communications
using Appendix **17** frequencies and mobile frequencies outside
Appendix **17**,

noting also

that various channels or bands used by the MMS have been identified in
the MF and HF bands for the introduction of new digital technology,

resolves

1 that, in order to provide full worldwide interoperability of equipment
on ships, there should be one technology, or more than one interoperable
worldwide technology to serve the MMS;

2 that, if the ITU‑R studies are completed, \[WRC‑11\] should consider
necessary changes to Appendix **17** to facilitate the use of new
technology by the MMS,

invites ITU-R

to finalize studies currently ongoing:

-- to identify future requirements of the MMS;

-- to identify the technical characteristics necessary to facilitate use
of digital systems in the MF and HF bands allocated to the MMS, taking
into account any relevant ITU‑R Recommendations;

-- to identify the digital system(s) to be used in the MF/HF bands by
the MMS;

-- to identify any necessary modifications to the frequency table
contained within Appendix **17**;

-- to propose a timetable for the introduction of new digital
technologies and any consequential changes to Appendix **17**;

-- to recommend how digital technologies can be introduced while
ensuring compliance with distress and safety requirements,

instructs the Secretary-General

to bring this Resolution to the attention of the International Maritime
Organization, the International Civil Aviation Organization, the
International Association of Marine Aids to Navigation and Lighthouse
Authorities and the Comité International Radio-Maritime.

**Reasons:** There are still several studies underway that need to be
completed prior to resolving this issue. IMO is still in the process of
developing HF data system performance requirements. These studies should
be completed prior to the next conference, where the appropriate changes
to the RR can be considered.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/191

3 230-5 003 kHz

+-----------------------+-----------------------+-----------------------+
| Allocation to         |                       |                       |
| services              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| Region 1              | Region 2              | Region 3              |
+-----------------------+-----------------------+-----------------------+
| **4 063-4 438**       |                       |                       |
| MARITIME MOBILE 5.79A |                       |                       |
| 5.109 5.110 5.130     |                       |                       |
| 5.131 5.132           |                       |                       |
|                       |                       |                       |
| 5.128 5.129 ADD 5.XYZ |                       |                       |
+-----------------------+-----------------------+-----------------------+

**MOD** IAP/14A2/191A

5 003-7 450 kHz

**MOD** IAP/14A2/191B

7 450-13 360 kHz

+-----------------------+-----------------------+-----------------------+
| Allocation to         |                       |                       |
| services              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| Region 1              | Region 2              | Region 3              |
+-----------------------+-----------------------+-----------------------+
| **8 195-8 815**       |                       |                       |
| MARITIME MOBILE 5.109 |                       |                       |
| 5.110 5.132 5.145     |                       |                       |
|                       |                       |                       |
| 5.111 ADD 5.XYZ       |                       |                       |
+-----------------------+-----------------------+-----------------------+
| \...                  |                       |                       |
+-----------------------+-----------------------+-----------------------+
| **12 230-13 200**     |                       |                       |
| MARITIME MOBILE 5.109 |                       |                       |
| 5.110 5.132 5.145 ADD |                       |                       |
| 5.XYZ                 |                       |                       |
+-----------------------+-----------------------+-----------------------+

**MOD** IAP/14A2/191C

13 360-18 030 kHz

  ----------------------- ----------------------- -----------------------
  Allocation to services                          

  Region 1                Region 2                Region 3

  **16 360-17 410**                               
  MARITIME MOBILE 5.109                           
  5.110 5.132 5.145 ADD                           
  5.XYZ                                           
  ----------------------- ----------------------- -----------------------

**MOD** IAP/14A2/191D

18 030-23 350 kHz

+-----------------------+-----------------------+-----------------------+
| Allocation to         |                       |                       |
| services              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| Region 1              | Region 2              | Region 3              |
+-----------------------+-----------------------+-----------------------+
| **18 780-18 900**     |                       |                       |
| MARITIME MOBILE ADD   |                       |                       |
| 5.XYZ                 |                       |                       |
+-----------------------+-----------------------+-----------------------+
| \...                  |                       |                       |
+-----------------------+-----------------------+-----------------------+
| **19 680-19 800**     |                       |                       |
| MARITIME MOBILE 5.132 |                       |                       |
| ADD 5.XYZ             |                       |                       |
+-----------------------+-----------------------+-----------------------+
| \...                  |                       |                       |
+-----------------------+-----------------------+-----------------------+
| **22 000-22 855**     |                       |                       |
| MARITIME MOBILE 5.132 |                       |                       |
|                       |                       |                       |
| 5.156 ADD 5.XYZ       |                       |                       |
+-----------------------+-----------------------+-----------------------+

**MOD** IAP/14A2/191E

23 350-27 500 kHz

  ----------------------- ----------------------- -----------------------
  Allocation to services                          

  Region 1                Region 2                Region 3

  **25 070-25 210**                               
  MARITIME MOBILE ADD                             
  5.XYZ                                           

  \...                                            

  **26 100-26 175**                               
  MARITIME MOBILE 5.132                           
  ADD 5.XYZ                                       
  ----------------------- ----------------------- -----------------------

**Reasons:** Allow limited use of HF data services in radiotelephony
channels addressed by Article 52.

**ADD** IAP/14A2/192

**5.XYZ** The bands 4 063-4 438 kHz, 6 200-6 525 kHz, 8 195-8 815 kHz,
12 230-13 200 kHz, 16 360-17 410 kHz, 18 780-18 900 kHz,
19 680-19 800 kHz, 22 000-22 855 kHz, 25 070-25 210 kHz and
26 100-26 175 kHz allocated exclusively to the maritime mobile service
are used in accordance with Article **52**. The use of HF data
transmissions in the duplex telephony channels may be used for the
introduction of new HF digital technologies within the maritime mobile
service. Stations using these sub-bands for this purpose shall not cause
harmful interference to, and shall not claim protection from, other
stations operating in accordance with Article **52**.

**Reasons:** Allow limited use of HF data services in radiotelephony
channels addressed by Article 52.

#### Agenda item 1.14

1.14 to review the operational procedures and requirements of the Global
Maritime Distress and Safety System (GMDSS) and other related provisions
of the Radio Regulations, taking into account Resolutions **331
(Rev.WRC‑03)** and **342 (Rev.WRC‑2000)** and the continued transition
to the GMDSS, the experience since its introduction, and the needs of
all classes of ships

Proposals for Agenda item 1.14

Background information

Issue A -- Transition to GMDSS

The 1991-1999 implementation of the Global Maritime Distress and Safety
System (GMDSS) was expected to lead to the deletion of Appendix 13 and
other regulatory text concerning systems which preceded GMDSS, but
experience of Administrations has shown the need to continue parts of
those systems, particularly those related to the MF and VHF
radiotelephony distress, safety and calling frequencies 2 182 kHz and
156.8 MHz. In this context, the CPM text for WRC‑07 Agenda item 1.14
reflects the integration of Appendix 13 VHF radiotelephone procedures
into Chapter VII of the Radio Regulations, the transfer of
radiotelephone procedures for 2 182 kHz from Appendix 13 into a new
Resolution, and the suppression of Appendix 13.

Experience with GMDSS since its introduction has also demonstrated the
need for modifications to certain operational procedures and
requirements prescribed by the Radio Regulations. An example of this
relates to excessive DSC alerts produced in the announcement of safety
messages due to the existing regulatory requirements.

With the loss of radio officers and other personnel on ship familiar
with radiocommunication procedures, further consideration was given to
the modifications of the Radio Regulations, such as the simplification
of the document carriage requirements in Appendix 16. Additionally, with
the advent of radiocommunications equipment equipped with
microprocessors and software, a need became apparent to migrate as much
of the GMDSS procedures specified in the Radio Regulations from the
responsibility of shipboard personnel to the specifications of the GMDSS
radio equipment as possible. That migration is still incomplete.
Regardless, the text proposed here is intended to be consistent with
that prepared by the Conference Preparatory Meeting of 19 February to
2 March 2007.

Issue B -- New technologies for maritime VHF

Resolution 342 (Rev.WRC-2000), titled "New technologies to provide
improved efficiency in the use of the band 156-174 MHz in the maritime
mobile service", considers the need for new maritime technologies which
use the bands described by Appendix 18 of the Radio Regulations.
*Considering k)* of this Resolution in particular addresses the new
Automatic Identification System (AIS) developed by ITU‑R and the need to
provide full worldwide interoperability of equipment on ships.

AIS is an international standard for ship-to-ship, ship-to-shore and
shore-to-ship communication of information, including vessel position,
speed, course, destination and other data defined by Recommendation
ITU‑R M.1371-1. AIS transmits on 161.975 MHz and 162.025 MHz, as
specified by Appendix 18 of the Radio Regulations and by Recommendation
ITU‑R M.1371-1. AIS was originally designed to enhance navigation
safety, but its potential as a prime contributor to security quickly
became apparent. AIS provides an effective means to monitor the total
global marine environment that could affect the security, safety,
economy, or environment of an administration.

On 6 December 2000, the International Maritime Organization (IMO)
amended Chapter V of the Safety of Life at Sea (SOLAS) Convention to
include an implementation schedule for shipboard AIS carriage
requirements. In 2002, in response to the needs of administrations to
improve their security, the IMO accelerated the AIS carriage
requirements schedule from a phased approach ending in 2008 to require
all vessels over 300 gross tons on international voyages to carry AIS
equipment by 31 December 2004.

AIS receivers on aircraft and on low earth orbit mobile satellite
platforms permits the location and identification of vessels for
security purposes beyond VHF range of shore. Recommendation ITU‑R M.1371
is being amended to accommodate AIS transmissions from aircraft and aids
to navigation stations. Satellite use is not currently allocated in
Article 5; however, based on studies to date, a secondary allocation for
satellite detection of AIS is identified as a possible method to address
this issue in the CPM Report for WRC‑07 Agenda item 1.14.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**MOD** IAP/14A2/193

**5.79A** When establishing coast stations in the NAVTEX service on the
frequencies 490 kHz, 518 kHz and 4 209.5 kHz, administrations are
strongly recommended to coordinate the operating characteristics in
accordance with the procedures of the International Maritime
Organization (IMO) (see Resolution **339 (Rev.WRC-03)**). (WRC‑07)

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/194

**5.82** In the maritime mobile service, the frequency 490 kHz is to be
used exclusively for the transmission by coast stations of navigational
and meteorological warnings and urgent information to ships, by means of
narrow-band direct-printing telegraphy. The conditions for use of the
frequency 490 kHz are prescribed in Articles **31** and **52**. In using
the band  415-495 kHz for the aeronautical radionavigation service,
administrations are requested to ensure that no harmful interference is
caused to the frequency 490 kHz.     (WRC-07)

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/195

**5.83** The frequency 500 kHz is an international distress and calling
frequency for Morse radiotelegraphy. The conditions for its use are
prescribed in Articles **31** and **52**.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/196

**5.84** The conditions for the use of the frequency 518 kHz by the
maritime mobile service are prescribed in Articles **31**
and **52**.     (WRC-07)

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/197

**5.108** The carrier frequency 2 182 kHz is an international distress
and calling frequency for radiotelephony. The conditions for the use of
the band 2 173.5-2 190.5 kHz are prescribed in Articles **31**
and **52**.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/198

**5.111** The carrier frequencies 2 182 kHz, 3 023 kHz, 5 680 kHz, 8 364
kHz and the frequencies 121.5 MHz, 156.525 MHz, 156.8 MHz and 243 MHz
may also be used, in accordance with the procedures in force for
terrestrial radiocom­munication services, for search and rescue
operations concerning manned space vehicles. The conditions for the use
of the frequencies are prescribed in Article **31**.

The same applies to the frequencies 10 003 kHz, 14 993 kHz and 19 993
kHz, but in each of these cases emissions must be confined in a band of
 3 kHz about the frequency.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/199

**5.115** The carrier (reference) frequencies 3 023 kHz and 5 680 kHz
may also be used, in accordance with Article **31** by stations of the
maritime mobile service engaged in coordinated search and rescue
operations.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/200

**5.130** The conditions for the use of the carrier frequencies 4 125
kHz and 6 215 kHz are prescribed in Articles **31** and **52**.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/201

**5.145** The conditions for the use of the carrier frequencies
8 291 kHz, 12 290 kHz and 16 420 kHz are prescribed in Articles **31**
and **52**.

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/202

**5.199**

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/203

75.2-137.175 MHz

+----------------------+----------------------+-----------------------+
| Allocation to        |                      |                       |
| services             |                      |                       |
+----------------------+----------------------+-----------------------+
| Region 1             | Region 2             | Region 3              |
+----------------------+----------------------+-----------------------+
| **117.975-137**      |                      |                       |
| AERONAUTICAL MOBILE  |                      |                       |
| (R)                  |                      |                       |
|                      |                      |                       |
| 5.111 5.198 5.199    |                      |                       |
| MOD 5.200 5.201      |                      |                       |
| 5.202 5.203 5.203A   |                      |                       |
| 5.203B               |                      |                       |
+----------------------+----------------------+-----------------------+

**Reasons:** Consequential to GMDSS implementation; editorial.

**MOD** IAP/14A2/204

**5.200** In the band 117.975-137 MHz, the frequency 121.5 MHz is the
aeronautical emergency frequency and, where required, the frequency
123.1 MHz is the aeronautical frequency auxiliary to 121.5 MHz. Mobile
stations of the maritime mobile service may communicate on these
frequencies under the conditions laid down in Article **31** for
distress and safety purposes with stations of the aeronautical mobile
service.

**Reasons:** Consequential to GMDSS implementation; editorial.

**MOD** IAP/14A2/205

148-223 MHz

+----------------------+----------------------+-----------------------+
| Allocation to        |                      |                       |
| services             |                      |                       |
+----------------------+----------------------+-----------------------+
| Region 1             | Region 2             | Region 3              |
+----------------------+----------------------+-----------------------+
| **150.05-153**       | **150.05-156.5125**  |                       |
|                      |                      |                       |
| FIXED                | FIXED                |                       |
|                      |                      |                       |
| MOBILE except        | MOBILE               |                       |
| aeronautical\        |                      |                       |
| mobile               |                      |                       |
|                      |                      |                       |
| RADIO ASTRONOMY      |                      |                       |
|                      |                      |                       |
| 5.149                |                      |                       |
+----------------------+----------------------+-----------------------+
| **153-154**          |                      |                       |
|                      |                      |                       |
| FIXED                |                      |                       |
|                      |                      |                       |
| MOBILE except        |                      |                       |
| aeronautical\        |                      |                       |
| mobile (R)           |                      |                       |
|                      |                      |                       |
| Meteorological Aids  |                      |                       |
+----------------------+----------------------+-----------------------+
| **154-156.5125**     |                      |                       |
|                      |                      |                       |
| FIXED                |                      |                       |
|                      |                      |                       |
| MOBILE except        |                      |                       |
| aeronautical\        |                      |                       |
| mobile (R)           |                      |                       |
+----------------------+----------------------+-----------------------+
| 5.226                | 5.225 5.226          |                       |
+----------------------+----------------------+-----------------------+
| *                    |                      |                       |
| *156.5125-156.5375** |                      |                       |
| MARITIME MOBILE      |                      |                       |
| (distress and        |                      |                       |
| calling)             |                      |                       |
|                      |                      |                       |
| 5.111 5.226          |                      |                       |
+----------------------+----------------------+-----------------------+
| *                    | *                    |                       |
| *156.5375-156.7625** | *156.5375-156.7625** |                       |
|                      |                      |                       |
| FIXED                | FIXED                |                       |
|                      |                      |                       |
| MOBILE except        | MOBILE               |                       |
| aeronautical\        |                      |                       |
| mobile               | 5.225 5.226          |                       |
|                      |                      |                       |
| 5.226                |                      |                       |
+----------------------+----------------------+-----------------------+
| *                    |                      |                       |
| *156.7625-156.8375** |                      |                       |
| MARITIME MOBILE      |                      |                       |
| (distress and        |                      |                       |
| calling)             |                      |                       |
|                      |                      |                       |
| 5.111 5.226          |                      |                       |
+----------------------+----------------------+-----------------------+
| **156.8375-174**     | **156.8375-174**     |                       |
|                      |                      |                       |
| FIXED                | FIXED                |                       |
|                      |                      |                       |
| MOBILE except        | MOBILE               |                       |
| aeronautical\        |                      |                       |
| mobile               |                      |                       |
+----------------------+----------------------+-----------------------+
| 5.226 5.229 ADD      | 5.226 5.230 5.231    |                       |
| 5.AAA                | 5.232 ADD 5.AAA      |                       |
+----------------------+----------------------+-----------------------+

**Reasons: Consequential to GMDSS implementation. Reallocation of DSC
distress frequency 156.525 MHz does not include guardband. Therefore, it
is not necessary.**

**MOD** IAP/14A2/206

**5.226** The frequency 156.8 MHz is the international distress, safety
and calling frequency for the maritime mobile VHF radiotelephone
service. The conditions for the use of this frequency are contained in
Article **31** and Appendix **18**.

The frequency 156.525 MHz is the international distress, safety and
calling frequency for the maritime mobile VHF radiotelephone service
using digital selective calling (DSC). The conditions for the use of
this frequency are contained in Articles **31** and **52**, and
Appendix **18**.

In the bands 156-156.5125 MHz, 156.5375-156.7625 MHz, 156.8375-157.45
MHz, 160.6-160.975 MHz and 161.475-162.05 MHz, each administration shall
give priority to the maritime mobile service on only such frequencies as
are assigned to stations of the maritime mobile service by the
administration (see Articles **31** and **52**, and Appendix **18**).

Any use of frequencies in these bands by stations of other services to
which they are allocated should be avoided in areas where such use might
cause harmful interference to the maritime mobile VHF radio­communication
service.

However, the frequencies 156.8 MHz and 156.525 MHz and the frequency
bands in which priority is given to the maritime mobile service may be
used for radiocommunications on inland waterways subject to agreement
between interested and affected administrations and taking into account
current frequency usage and existing agreements.

**Reasons:** Consequential to GMDSS implementation. Reallocation of DSC
distress frequency 156.525 MHz does not include guardband, not believed
to be necessary.

**SUP** IAP/14A2/207

**5.227**

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/208

**5.AAA** The bands 161.9625-161.9875 MHz and 162.0125-162.0375 MHz are
also allocated to the mobile-satellite service (Earth-to-space) on a
secondary basis for the reception of the automatic identification system
(AIS) emissions.

**Reasons:** Consequential to GMDSS implementation. Allows for satellite
detection of AIS to allow administrations help ensure the safety and
security of ships and ports.

**MOD** IAP/14A2/209

**5.256** The frequency 243 MHz is the frequency in this band for use by
survival craft stations and equipment used for survival purposes.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/210

**5.266** The use of the band 406-406.1 MHz by the mobile-satellite
service is limited to low power satellite emergency position-indicating
radiobeacons (see also Article **31**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/211

**5.287** In the maritime mobile service, the frequencies 457.525 MHz,
457.550 MHz, 457.575 MHz, 467.525 MHz, 467.550 MHz and 467.575 MHz may
be used by on-board communication stations. Where needed, equipment
designed for 12.5 kHz channel spacing using also the additional
frequencies 457.5375 MHz, 457.5625 MHz, 467.5375 MHz and 467.5625 MHz
may be introduced for on-board communications. The use of these
frequencies in territorial waters may be subject to the national
regulations of the administration concerned. The characteristics of the
equipment used shall conform to those specified in
Recommendation ITU‑R M.1174‑2.     (WRC-07)

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 15

Interferences

Section I -- Interference from Radio Stations

**MOD** IAP/14A2/212

**15.8** § 4 Special consideration shall be given to avoiding
interference on distress and safety frequencies, those related to
distress and safety identified in Article **31**, and those related to
safety and regularity of flight identified in Appendix
**27**.     (WRC‑07)

**Reasons:** Consequential to GMDSS implementation.

Section VI -- Procedure in a case of harmful interference

**MOD** IAP/14A2/213

**15.28** § 20 Recognizing that transmissions on distress and safety
frequencies and frequencies used for the safety and regularity of flight
(see Article **31** and Appendix **27**) require absolute international
protection and that the elimination of harmful interference to such
transmissions is imperative, administrations undertake to act
immediately when their attention is drawn to any such harmful
interference.     (WRC‑07)

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 19

Identification of stations

Section III -- Formation of call signs

**MOD** IAP/14A2/214

**19.55** § 24 1)

-- two characters and two letters, *or*

-- two characters, two letters and one digit (other than the digits 0
or 1), *or*

-- two characters (provided that the second is a letter) followed by
four digits (other than the digits 0 or 1 in cases where they
immediately follow a letter), *or*

-- two characters and one letter followed by four digits (other than the
digits 0 or 1 in cases where they immediately follow a letter).

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/215

**19.56**

**Reasons:** Consequential to GMDSS implementation.

Section IV -- Identification of stations using radiotelephony

**MOD** IAP/14A2/216

**19.76** 4) *Emergency position‑indicating radiobeacon stations*

When speech transmission is used:

-- the name and/or the call sign of the parent ship to which the
radiobeacon belongs.

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 30

General provisions

Section I -- Introduction

**MOD** IAP/14A2/217

**30.1** § 1 This Chapter contains the provisions for the operational
use of the global maritime distress and safety system (GMDSS). GMDSS
functional requirements, system elements and equipment carriage
requirements are set forth in the International Convention for the
Safety of Life at Sea (SOLAS), 1974, as amended. This Chapter also
contains provisions for initiating distress, urgency and safety
communications by means of radiotelephony on the frequency 156.8 MHz
(VHF channel 16).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/218

**30.3** § 3 No provision of these Regulations prevents the use by
stations on board aircraft, ships engaged in search and rescue
operations, land stations, or earth stations, in exceptional
circumstances, of any means at their disposal to assist a mobile station
or a mobile earth station in distress (see also Nos. **4.9** and
**4.16**).

**Reasons:** Consequential to GMDSS implementation.

Section II -- Maritime provisions

**MOD** IAP/14A2/219

**30.4** § 4 The provisions specified in this Chapter are obligatory in
the maritime mobile service and the maritime mobile‑satellite service
for all stations using the frequencies and techniques prescribed for the
functions set out herein (see also No. **30.5**).

**Reasons:** Consequential to GMDSS implementation.

Section III -- Aeronautical provisions

**ADD** IAP/14A2/220

**30.11*bis*** Aircraft, when conducting search and rescue operations
are also permitted to operate DSC equipment on the VHF DSC frequency
156.525 MHz, and AIS equipment on the AIS frequencies 161.975 MHz and
162.025 MHz.

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 31

Frequencies for the global maritime distress and safety system (GMDSS)

Section I -- General

**MOD** IAP/14A2/221

**31.1** § 1 The frequencies to be used for the transmission of distress
and safety infor­mation under the GMDSS are contained in Appendix **15**.
In addition to the frequencies listed in Appendix **15**, ship stations
and coast stations should use other appropriate frequencies for the
transmission of safety messages and general radiocommunications to and
from shore-based radio systems or networks.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/222

**31.2** § 2 Any emission causing harmful interference to distress and
safety communi­cations on any of the discrete frequencies identified in
Appendix **15** is prohibited.

**Reasons:** Consequential to GMDSS implementation.

Section III -- Watchkeeping

**MOD** IAP/14A2/223

**31.17** § 8 1) Ship stations, where so equipped, shall, while at sea,
maintain an auto­matic digital selective calling watch on the appropriate
distress and safety calling frequencies in the frequency bands in which
they are operating. Ship stations, where so equipped, shall also
maintain watch on the appropriate frequencies for the automatic
reception of transmissions of meteorological and navigational warnings
and other urgent information to ships.

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 32

Operational procedures for distress and safety communications in the
global\
maritime distress and safety system (GMDSS)

Section I -- General

**MOD** IAP/14A2/224

**32.1** § 1 Distress communications rely on the use of terrestrial MF,
HF and VHF radiocommunications and communications using satellite
techniques. Distress communications shall have absolute priority over
all other transmissions.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/225

**32.2** § 2 1) The distress alert (see No. **32.9**) shall be sent
through a satellite either with absolute priority in general
communication channels, on exclusive distress and safety frequencies
reserved for satellite EPIRBs in the Earth-to-space direction or on the
distress and safety frequencies designated in the MF, HF and VHF bands
(see Appendix **15**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/226

**32.3** 2) The distress alert (see No. **32.9**) or radiotelephone
distress call and message (see Nos. **32.13C** and **32.13D**) shall be
sent only on the authority of the person responsible for the ship,
aircraft or other vehicle carrying the mobile station or the mobile
earth station.

**Reasons:** Proposed modification extends provision to radiotelephony
distress procedures which are proposed to be incorporated into Chapter
VII.

**MOD** IAP/14A2/227

**32.4** § 3 All stations which receive a distress alert or
radiotelephone distress call transmitted on the distress and safety
frequencies in the MF, HF and VHF bands shall immediately cease any
transmission capable of interfering with distress traffic and prepare
for subsequent distress traffic.

**Reasons:** Consequential to GMDSS implementation. Proposed
modification extends provision to radiotelephony distress procedures
which are proposed to be incorporated into Chapter VII.

**MOD** IAP/14A2/228

**32.5** § 4 Calls using digital selective calling shall use the
technical structure and content set forth in Recommendations
ITU‑R M.493-11 and ITU‑R M.541-9.

**Reasons:** Consequential to GMDSS implementation. Mandatory reference
is made to Recommendations ITU‑R M.493-11 and ITU‑R.541.9.

Section II -- Distress alerting

**ADD** IAP/14A2/229

**32.10B** Administrations shall take practicable and necessary steps to
ensure the avoidance of false distress alerts, including those
transmitted inadvertently.

**Reasons:** Consequential to GMDSS implementation. False distress
alerts, particularly those generated by automated equipment such as the
GMDSS, are a burden for rescue coordination centers and those having
search and rescue responsibility.

**ADD** IAP/14A2/230

**32.10C** § 7B 1) The radiotelephone distress signal consists of the
word MAYDAY pronounced as the French expression "m\'aider".

**Reasons:** Proposed addition is consistent with incorporating
radiotelephony distress procedures into Chapter VII and is appropriately
introduced prior to the description of the distress call and message in
provisions 32.13C and 32.13D of the CPM Report.

**ADD** IAP/14A2/231

**32.10D** 2) The distress signal indicates that a ship, aircraft,
person or other vehicle is threatened by grave and imminent danger and
requests immediate assistance.

**Reasons:** Proposed addition is consistent with incorporating
radiotelephony distress procedures into Chapter VII.

**MOD** IAP/14A2/232

**32.13** § 9 1) Ship-to-ship distress alerts are used to alert other
ships in the vicinity of the ship in distress and are based on the use
of digital selective calling in the VHF and MF bands. Additionally, the
HF band may be used.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/233

**32.13A** 2) In order to attract attention from as many ship stations
as possible, ship stations equipped for making use of digital selective
calling procedures may transmit a radiotelephony distress call and
message on the frequency 156.8 MHz (VHF channel 16) immediately
following the distress alert sent by digital selective calling on the
frequency 156.525 MHz (VHF channel 70).

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/234

**32.13B** 3) Ship stations not equipped for making use of the digital
selective calling procedures may initiate the distress communications by
transmitting a radiotelephony distress call and message on the frequency
156.8 MHz (VHF channel 16). The radiotelephone distress procedure
consists of the distress call and the distress message^6^.

**ADD** IAP/14A2/234A

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^6^ **32.13B.1** It should be noted that there is a higher probability
of successful reception of a distress message if the distress message is
preceded by a DSC alert.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/235

**32.13C** § 9A 1) The distress call sent on the frequency 156.8 MHz
(VHF channel 16) shall be given in the following form:

-- the distress signal MAYDAY, spoken three times;

-- the words THIS IS;

-- the name of the vessel in distress, spoken three times;

-- the call sign or other identification;

-- the MMSI (if the initial alert has been sent by DSC).

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/236

**32.13D** 2) The distress message which follows the distress call,
shall be given in the following form:

-- the distress signal MAYDAY;

-- the words THIS IS;

-- the name of the vessel in distress;

-- the call sign or other identification;

-- the MMSI (if the initial alert has been sent by DSC);

-- the position given as the latitude and longitude, or if latitude and
longitude is not known, with respect to a known geographical location;

-- the nature of the distress;

-- the kind of assistance required;

-- any other useful information.

**Reasons:** Consequential to GMDSS implementation. In reference to the
CPM text, the second bullet was added as it provides the correct format
for the call and maintains consistency with the associated provisions
which were intended to be transferred from Appendix 13 and with other
provisions proposed to be incorporated into Chapter VII. The sixth
bullet was revised from the CPM text to emphasize the importance of
latitude and longitude by search and rescue authorities.

**ADD** IAP/14A2/237

**32.13E** § 9B Digital selective calling procedures use a combination
of automated functions and manual intervention to generate the
appropriate distress call format in the most recent version of
Recommendation ITU‑R M.541. The distress alert sent by digital selective
calling consists of one or more distress alert attempts in which a
message format is transmitted identifying the station in distress,
giving its last recorded position and, if entered, the nature of the
distress. At MF and HF, distress alert attempts may be sent as a single
frequency attempt or a multi-frequency attempt on up to six frequencies
within one minute. At VHF, only single frequency call attempts are used.
The distress alert will repeat automatically at random intervals, a few
minutes apart, until an acknowledgement sent by digital selective
calling is received.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/238

**32.15** 2) The distress alert relay shall contain the identification
of the mobile unit in distress, its position and all other information
which might facilitate rescue.

B3 -- Transmission of a distress alert relay by a station not itself in
distress

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/239

**32.16** § 11 A station in the mobile or mobile-satellite service which
learns that a mobile unit is in distress (for example, by a radio call
or by observation) shall initiate and transmit a distress alert relay on
behalf of the mobile unit in distress once it has ascertained that any
of the following circumstances apply:

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/240

**32.17** *a)* on receiving a distress call sent by radiotelephony on
the frequency 156.8 MHz (VHF channel 16), which is not acknowledged by a
coast station or another vessel within 5 minutes (see also
No. **32.29A**);

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/241

**32.17A** *b)* on receiving a distress alert on an HF channel, which is
not acknowledged by a coast station within 5 minutes (see also
No. **32.31**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/242

**32.18** *c)* on knowing that the mobile unit in distress is otherwise
unable or incapable of participating in distress communications and the
master or other person responsible for the mobile unit not in distress
considers that further help is necessary.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/243

**32.19** § 12 1) The distress relay on behalf of a mobile unit in
distress shall be sent in a form appropriate to the circumstances using
either a MAYDAY relay by radiotelephony (see No. **32.19E**), an
individually addressed distress relay call by digital selective calling
(see No. **32.19B**) or a distress priority message through a ship earth
station.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/244

**32.19A** 2) A station transmitting a distress alert relay in
accordance with Nos. **32.16** to **32.18** shall indicate that it is
not itself in distress.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/245

**32.19B** 3) A distress alert relay sent by digital selective calling
should use the call format, as found in the most recent version of
Recommendations ITU‑R M.493 and ITU‑R M.541 and preferably be addressed
to an individual coast station or rescue coordination centre^new1^.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/246

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^new1^ **32.19B.1** Vessels making a distress relay call should ensure
that a suitable coast station or rescue coordination centre is informed
of any original distress communications.

**ADD** IAP/14A2/247

**32.19C** 4) However, a ship shall not transmit a distress alert relay
to all ships by digital selective calling on the VHF or MF distress
frequencies following receipt of a distress alert sent by digital
selective calling by the ship in distress.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/248

**32.19D** 5) When an aural watch is being maintained on shore and
reliable ship-to-shore communications can be established by
radiotelephony, a distress relay call shall be sent by radiotelephony
and addressed to the relevant coast station or rescue coordination
centre^new2^ on the appropriate frequency.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/249

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^new2^ **32.19D.1** Vessels making a distress relay call should ensure
that a suitable coast station or rescue coordination centre is informed
of any original distress communications.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/250

**32.19E** 6) The distress relay call sent by radiotelephony shall be
given in the following form:

-- the distress signal MAYDAY RELAY, spoken three times;

-- ALL STATIONS or coast station name, as appropriate, spoken three
times;

-- the words THIS IS;

-- the name of the relaying station, spoken three times;

-- the call sign or other identification of the relaying station;

-- the MMSI (if the initial alert has been sent by DSC) of the relaying
station (the vessel not in distress).

**Reasons:** Consequential to GMDSS implementation. In reference to the
CPM text, the 2nd bullet was modified to allow formatting of the call
according to the circumstances (e.g. the use of coast station name per
No. 32.19D, or the use of ALL STATIONS per No. 32.19H, or the option to
use neither in the case of a distress relay by a coast station).

**ADD** IAP/14A2/251

**32.19F** 7) This call shall be followed by a distress message which
shall, as far as possible, repeat the information^new3^ contained in the
original distress alert.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/252

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^new3^ **32.19F.1** If the station in distress cannot be identified,
then it will be necessary to originate the distress message as well,
using, for example, terms such as "Unidentified trawler" or
"Unidentified helicopter" refer to the mobile unit in distress.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/253

**32.19G** 8) When no aural watch is being maintained on shore, or there
are other difficulties in establishing reliable ship-to-shore
communications by radiotelephony, an appropriate coast station or rescue
coordination centre may be contacted by sending an individual distress
relay call by digital selective calling addressed solely to that station
and using the appropriate call formats.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/254

**32.19H** 9) In the event of continued failure to contact a coast
station or rescue coordination centre directly then it may be
appropriate to send a MAYDAY relay by radiotelephony addressed to all
ships or to all ships in a certain geographical area. See also
No. **32.19C**.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/255

**32.21** § 13 1) Acknowledgement of receipt of a distress alert,
including a distress alert relay, shall be made in the manner
appropriate to the method of transmission of the alert and within the
time-scale appropriate to the role of the station in receipt of the
alert. Acknowledgement by satellite shall be sent immediately.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/256

**32.21A** 2) When acknowledging receipt of a distress alert sent by
digital selective calling^new4^, the acknowledgement in the terrestrial
services shall be made by digital selective calling, radiotelephony or
narrow-band direct-printing telegraphy as appropriate to the
circumstances, on the associated distress and safety frequency in the
same band in which the distress alert was received, taking due account
of the directions given in the most recent versions of Recommendations
ITU‑R M.493 and ITU‑R M.541.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/257

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^new4^ **32.21A.1** In order to ensure that no unnecessary delay occurs
before the shore based authorities become aware of a distress incident,
the acknowledgement by digital selective calling to a distress alert
sent by digital selective calling shall normally only be made by a coast
station or a rescue coordination centre, as an acknowledgement by
digital selective calling will cancel any further automated repetition
of the distress alert using digital selective calling.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/258

**32.21B** Acknowledgement by digital selective calling in receipt of a
distress alert sent by digital selective calling addressed to stations
in the maritime mobile services shall be addressed to the same station
as the distress alert^new5^.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/259

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^new5^ **32.21B.1** In order to ensure that no unnecessary delay occurs
before the shore based authorities become aware of a distress incident,
the acknowledgement by digital selective calling to a distress alert
sent by digital selective calling shall normally only be made by a coast
station or rescue coordination centre, as an acknowledgement by digital
selective calling will cancel any further automated repetition of the
distress alert using digital selective calling.

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/260

**32.22**

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/261

**32.23** § 15 1) When acknowledging by radiotelephony the receipt of a
distress alert from a ship station or a ship earth station, the
acknowledgement shall be given in the following form:

-- the distress signal MAYDAY;

-- the name followed by the call sign or the MMSI or other
identification of the station sending the distress message;

-- the words THIS IS;

-- the name and call sign or other identification of the station
acknowledging receipt;

-- the word RECEIVED;

-- the distress signal MAYDAY.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/262

**32.24** 2) When acknowledging by narrow-band direct-printing
telegraphy the receipt of a distress alert from a ship station, the
acknowledgement shall be given in the following form:

-- the distress signal MAYDAY;

-- the call sign or other identification of the station sending the
distress alert;

-- the word DE;

-- the call sign or other identification of the station acknowledging
receipt of the distress alert;

-- the signal RRR;

-- the distress signal MAYDAY.

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/263

**32.25**

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/264

**32.26** § 17 Coast stations and the appropriate coast earth stations
in receipt of distress alerts shall ensure that they are routed as soon
as possible to a rescue coordination centre. In addition receipt of a
distress alert is to be acknowledged as soon as possible by a coast
station, or by a rescue coordination centre via a coast station or an
appropriate coast earth station. A shore-to-ship distress alert relay
(see Nos. **32.14** and **32.15**) shall also be made when the method of
receipt warrants a broadcast alert to shipping or when the circumstances
of the distress incident indicate that further help is necessary.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/265

**32.27** § 18 A coast station using digital selective calling to
acknowledge a distress alert shall transmit the acknowledgement on the
distress calling frequency on which the alert was received and should
address it to all ships. The acknowledgement shall include the
identification of the ship whose distress alert is being acknowledged.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/266

**32.29** 2) In areas where reliable communications with one or more
coast stations are practicable, ship stations in receipt of a distress
alert from another vessel should defer acknowledgement for a short
interval so that a coast station may acknowledge receipt in the first
instance.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/267

**32.29A** 3) Ship stations in receipt of a distress call sent by
radiotelephony on the frequency 156.8 MHz (VHF channel 16) shall, if the
call is not acknowledged by a coast station or another vessel within 5
minutes, acknowledge receipt to the vessel in distress and use any means
available to relay the distress alert to an appropriate coast station or
coast earth station (see also Nos. **32.16** to **32.19F**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/268

**32.30** § 20 1) Ship stations operating in areas where reliable
communications with a coast station are not practicable which receive a
distress alert from a ship station which is, beyond doubt, in their
vicinity, shall, as soon as possible and if appropriately equipped,
acknowledge receipt to the vessel in distress and inform a rescue
coordination centre through a coast station or coast earth station (see
also Nos. **32.16** to **32.19H**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/269

**32.31** 2) However, in order to avoid making unnecessary or confusing
transmissions in response a ship station receiving an HF distress alert,
which may be at a considerable distance from the incident, shall not
acknowledge it but shall observe the provisions of Nos. **32.36** to
**32.38**, and shall, if the alert is not acknowledged by a coast
station within 5 minutes, relay the distress alert, but only to an
appropriate coast station or coast earth station (see also Nos.
**32.16** to **32.19H**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/270

**32.32** § 21 A ship station acknowledging receipt of a distress alert
sent by digital selective calling should, in accordance with
No. **32.29** or No. **32.30**:

**32.33** *a)* in the first instance, acknowledge receipt of the alert
by using radiotelephony on the distress and safety traffic frequency in
the band used for the alert, taking into account any potential
instructions issued by a responding coast station;

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/271

**32.34A** § 21A However, unless instructed to do so by a coast station
or a rescue coordination centre, a ship station may only send an
acknowledgement by digital selective calling in the event that:

*a)* no acknowledgement by digital selective calling from a coast
station has been observed; and

*b)* no other communication by radiotelephony or narrow-band
direct-printing telegraphy to or from the vessel in distress has been
observed; and

*c)* at least 5 minutes have elapsed and the distress alert by digital
selective calling has been repeated (see No. **32.21A.1**).

**Reasons:** Consequential to GMDSS implementation.

Section III -- Distress traffic

**SUP** IAP/14A2/272

**32.41**

**Reasons:** Provision is no longer required as the same provision is
proposed to be incorporated at a more appropriate location, in an
earlier section (Section II) of Article 32 (see ADD 32.10C).

**MOD** IAP/14A2/273

**32.45** § 28 1) The rescue coordination centre responsible for
controlling a search and rescue operation shall also coordinate the
distress traffic relating to the incident or may appoint another station
to do so.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/274

**32.51** § 31 When distress traffic has ceased on frequencies which
have been used for distress traffic, the station controlling the search
and rescue operation shall initiate a message for transmission on these
frequencies indicating that distress traffic has finished.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/275

**32.52** § 32 1) In radiotelephony, the message referred to in
No. **32.51** consists of:

-- the distress signal MAYDAY;

-- the call "ALL STATIONS", spoken three times;

-- the words THIS IS;

-- the name of the station sending the message, spoken once;

-- the call sign or other identification of the station sending the
message;

-- the time of handing in of the message;

-- the MMSI (if the initial alert has been sent by DSC), the name and
the call sign of the mobile station which was in distress; and

-- the words SEELONCE FEENEE pronounced as the French words "silence
fini".

**Reasons:** Consequential to GMDSS implementation. In reference to the
CPM text, the 4th bullet was further modified to provide the correct
format for the call and maintain consistency with the associated
provisions which are intended to be transferred from Appendix 13.

**ADD** IAP/14A2/276

**32.53A** Cancellation of an inadvertent distress alert

A station transmitting an inadvertent distress alert shall cancel the
distress alert.

Immediately cancel the distress alert orally on the associated distress
and safety frequency in the same band on which the "distress alert" was
transmitted using the following procedure:

-- All Stations All Stations All Stations;

-- the words THIS IS;

-- the name of the vessel, spoken three times;

-- the call sign or other identification;

-- the MMSI (if the initial alert has been sent by DSC);

-- PLEASE CANCEL MY FALSE DISTRESS ALERT of time in UTC.

Monitor the same band on which the "distress alert" was transmitted and
respond to any communications concerning that distress alert as
appropriate.

If the initial alert has been sent by DSC, if the DSC equipment is
capable, initiate a SELF CANCELLATION.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/277

**32.63** 3) Locating signals may be transmitted in the following
frequency bands:

117.975-137 MHz;

156-174 MHz;

406-406.1 MHz; and

9 200-9 500 MHz.

**Reasons:** Consequential to GMDSS implementation; editorial.

**SUP** IAP/14A2/278

**32.64**

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 33

Operational procedures for urgency and safety communications in\
the global maritime distress and safety system (GMDSS)

Section I -- General

**MOD** IAP/14A2/279

**33.1** § 1 1) Urgency and safety communications include:

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/280

**33.7A** 2) Urgency communications shall have priority over all other
communications, except distress.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/281

**33.7B** 3) Safety communications shall have priority over all other
communications, except distress and urgency.

**Reasons:** Consequential to GMDSS implementation.

Section II -- Urgency communications

**MOD** IAP/14A2/282

**33.8** § 2 1) In a terrestrial system, urgency communications consist
of an announcement, transmitted using digital selective calling or
radiotelephony, followed by the urgency message transmitted using
radiotelephony, narrow-band direct-printing, or data. The announcement
of the urgency message shall be made on one or more of the distress and
safety calling frequencies specified in Section I of Article **31**
using either digital selective calling techniques and the urgency call
format or, when appropriate, radiotelephony procedures and the urgency
signal. Calls using digital selective calling shall use the technical
structure and content set forth in Recommendations ITU‑R M.493-11 and
ITU‑R M.541-9.

**Reasons:** Consequential to GMDSS implementation. "Data" is added to
avoid restricting technology and recognize the decline in use of
narrow-band direct-printing by many administrations. Mandatory reference
is made to Recommendations ITU‑R M.493-11 and ITU‑R M.541‑9.

**ADD** IAP/14A2/283

**33.8A** 2) Ship stations not equipped for making use of digital
selective calling procedures may announce an urgency message by
transmitting the urgency signal by radiotelephony on the frequency
156.8 MHz (channel 16)^32.8A.1^, while taking into account that other
stations outside VHF range may not receive the announcement.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/284

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**33.8A.1** It should be noted that there is a higher probability of
successful reception of an urgency message if it is announced by DSC.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/285

**33.8B** 3) In the maritime mobile service, urgency communications may
be addressed either to all stations or to a particular station. When
using digital selective calling techniques, the urgency announcement
shall indicate which frequency is to be used to send the subsequent
message and, in the case of a message to all stations, shall use the
"All Ships" format setting.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/286

**33.8C** 4) Urgency communications from a coast station may also be
directed to a group of vessels or to vessels in a defined geographical
area.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/287

**33.9** § 3 1) The urgency message shall be transmitted on one or more
of the distress and safety traffic frequencies specified in Section I of
Article **31**.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/288

**33.9A** 2) However, in the maritime mobile service, the message shall
be transmitted on a working frequency:

*a)* in the case of a long message or a medical call; *or*

*b)* in areas of heavy traffic when the message is being repeated.

An indication to this effect shall be included in the announcement.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/289

**33.9B** 3) In the maritime mobile-satellite service, a separate
announcement does not need to be made before sending the urgency
message. However, if available, the appropriate network priority access
settings should be used for sending the message.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/290

**33.11** § 5 1) The urgency call format and the urgency signal indicate
that the calling station has a very urgent message to transmit
concerning the safety of a mobile unit or a person.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/291

**33.11A** 2) Communications concerning medical advice may be preceded
by the urgency signal. Mobile stations requiring medical advice may
obtain it through any of the land stations shown in the List of
Radiodetermination and Special Service Stations.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/292

**33.11B** 3) Urgency communications to support search and rescue
operations need not be preceded by the urgency signal.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/293

**33.12** § 6 1) The urgency call consists of:

-- the urgency signal PAN PAN, spoken three times;

-- the name of the called station or "all stations", spoken three times;

-- the words THIS IS;

-- the name of the station transmitting the urgency message, spoken
three times;

-- the call sign or any other identification;

-- the MMSI (if the initial announcement has been sent by DSC),

followed by the message or followed by the details of the channel to be
used for the message in the case where a working channel is to be used.

In radiotelephony, on the selected working frequency, the urgency call
and message consists of:

-- the urgency signal PAN PAN, spoken three times;

-- the name of the called station or "all stations", spoken three times;

-- the words THIS IS;

-- the name of the station transmitting the urgency message, spoken
three times;

-- the call sign or any other identification;

-- the MMSI (if the initial announcement has been sent by DSC);

-- the text of the urgency message.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/294

**33.14** § 7 1) The urgency call format or urgency signal shall be sent
only on the authority of the person responsible for the ship, aircraft
or other vehicle carrying the mobile station or the mobile earth
station.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/295

**33.15A** § 7A 1) Ship stations in receipt of an urgency announcement
or call addressed to all stations shall not acknowledge.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/296

**33.15B** 2) Ship stations in receipt of an urgency announcement or
call of an urgency message shall monitor the frequency or channel
indicated for the message for at least five minutes. If, at the end of
the five minute monitoring period, no urgency message has been received,
a coast station should, if possible, be notified of the missing message.
Thereafter, normal working may be resumed.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/297

**33.15C** 3) Coast and ship stations which are in communication on
frequencies other than those used for the transmission of the urgency
signal or the subsequent message may continue their normal work without
interruption, provided that the urgency message is not addressed to them
nor broadcast to all stations.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/298

**33.16** § 8 The urgency cancellation consists of:

-- the urgency signal PAN PAN, spoken once;

-- "all stations", spoken three times;

-- the words THIS IS;

-- the name of the station transmitting the urgency message, spoken
once;

-- the call sign or any other identification;

-- the MMSI (if the initial announcement has been sent by DSC);

-- URGENCY CANCELLED of time in UTC.

**Reasons:** Consequential to GMDSS implementation. Further
modifications in bullets 1, 4, and 7 as compared to those in the CPM
text simplify the call format for the urgency cancellation.

Section III -- Medical transports

**MOD** IAP/14A2/299

**33.20** § 11 1) For the purpose of announcing and identifying medical
transports which are protected under the above-mentioned Conventions,
the procedure of Section II of Article **31** is used. The urgency
signal shall be followed by the addition of the single word MEDICAL in
narrow-band direct-printing and by the addition of the single word
MAY-DEE-CAL pronounced as in French "médical", in radiotelephony.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/300

**33.20A** 2) When using digital selective calling techniques, the
announcement on the appropriate digital selective calling distress and
safety frequencies shall always use the following call format, if so
equipped:

-- Format specified: "ALL SHIPS" on VHF, and geographical area on HF and
MF;

-- Category: "URGENCY";

-- Telecommand: "MEDICAL TRANSPORT".

**Reasons:** Certain DSC radios may not be able to provide the "MEDICAL
TRANSPORT" telecommand (i.e. according to Recommendation ITU‑R M.493-11,
Table 4.5, a class 'D' station does not seem capable of generating a
"MEDICAL TRANSPORT" call). Consequential to GMDSS implementation.

**ADD** IAP/14A2/301

**33.20B** 3) Medical transports may use one or more of the distress and
safety traffic frequencies specified in Section I of Article** 31** for
the purpose of self-identification and to establish communications. As
soon as practicable, communications shall be transferred to an
appropriate working frequency.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/302

**33.21** § 12 The use of the signals described in Nos. **33.20** and
**33.20A** indicates that the message which follows concerns a protected
medical transport. The message shall convey the following data:

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/303

**33.28** to **33.29**

**Reasons:** Consequential to GMDSS implementation.

Section IV -- Safety communications

**MOD** IAP/14A2/304

**33.31** § 15 1) In a terrestrial system, safety communications consist
of an announcement, transmitted using digital selective calling or
radiotelephony, followed by the safety message transmitted using
radiotelephony, narrow-band direct-printing, or data. The announcement
of the safety message shall be made on one or more of the distress and
safety calling frequencies specified in Section I of Article** 31**
using either digital selective calling techniques and the safety call
format or radiotelephony procedures and the safety signal.

**Reasons:** Consequential to GMDSS implementation. "Data" is added to
avoid restricting technology and recognize the decline in use of
narrow-band direct-printing by many administrations.

**MOD** IAP/14A2/305

33.31A 2) However, in order to avoid unnecessary loading of the distress
and safety calling frequencies specified for use with digital selective
calling techniques:

*a)* safety messages transmitted by coast stations in accordance with a
predefined timetable should not be announced by digital selective
calling techniques;

*b)* safety messages which only concern vessels sailing in the immediate
area should only be announced using radiotelephony
procedures.     (WRC‑07)

**Reasons:** Consequential to GMDSS implementation. In reference to the
CPM text, further modification was introduced in *b)* to provide a more
accurate and clearer text for the provision.

**ADD** IAP/14A2/306

**33.31B** 3) In addition, ship stations not equipped for making use of
digital selective calling procedures may announce a safety message by
transmitting the safety signal by radiotelephony. In such cases, the
announcement shall be made using the frequency 156.8 MHz (VHF channel
16), while taking into account that other stations outside VHF range may
not receive the announcement.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/307

**33.31C** 4) In the maritime mobile service, safety messages shall
generally be addressed to all stations. In some cases, however, they may
be addressed to a particular station. When using digital selective
calling techniques, the safety announcement shall indicate which
frequency is to be used to send the subsequent message and, in the case
of a message to all stations, shall use the "All Ships" format setting.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/308

**33.32** § 16 1) In the maritime mobile service, the safety message
shall, where practicable, be transmitted on a working frequency in the
same band(s) as used for the announcement. A suitable indication to this
effect shall be made at the end of the announcement. In the case that no
other option is practicable, the safety message may be sent by
radiotelephony on the frequency 156.8 MHz (VHF channel 16).

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/309

**33.32A** 2) In the maritime mobile-satellite service, a separate
announcement does not need to be made before sending the safety message.
However, if available, the appropriate network priority access settings
should be used for sending the message.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/310

**33.34** § 18 1) The safety call format or the safety signal indicates
that the calling station has an important navigational or meteorological
warning to transmit.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/311

**33.34A** 2) Messages from ship stations containing information
concerning the presence of cyclones shall be transmitted, with the least
possible delay, to other mobile stations in the vicinity and to the
appropriate authorities through a coast station, or through a rescue
coordination centre via a coast station or an appropriate coast earth
station. These transmissions shall be preceded by the safety signal.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/312

**33.34B** 3) Messages from ship stations containing information on the
presence of dangerous ice, dangerous wrecks, or any other imminent
danger to marine navigation, shall be transmitted as soon as possible to
other ships in the vicinity, and to the appropriate authorities through
a coast station, or through a rescue coordination centre via a coast
station or an appropriate coast earth station. These transmissions shall
be preceded by the safety signal.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/313

**33.35** § 19 1) The complete safety call consists of:

-- the safety signal SÉCURITÉ, spoken three times;

-- the name of the called station or "all stations", spoken three times;

-- the words THIS IS;

-- the name of the station transmitting the safety message, spoken three
times;

-- the call sign or any other identification;

-- the MMSI (if the initial announcement has been sent by DSC);

followed by the safety message or followed by the details of the channel
to be used for the message in the case where a working channel is to be
used.

In radiotelephony, on the selected working frequency, the safety call
and message consists of:

-- the safety signal SÉCURITÉ, spoken three times;

-- the name of the called station or "all stations", spoken three times;

-- the words THIS IS;

-- the name of the station transmitting the safety message, spoken three
times;

-- the call sign or any other identification;

-- the MMSI (if the initial alert has been sent by DSC);

-- the text of the safety message.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/314

**33.38A** § 20*bis* 1) Ship stations in receipt of a safety
announcement using digital selective calling techniques and the "All
Ships" format setting, or otherwise addressed to all stations shall not
acknowledge.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/315

**33.38B** 2) Ship stations in receipt of an announcement of a safety
message shall monitor the frequency or channel indicated for the message
and shall listen until they are satisfied that the message is of no
concern to them. They shall not make any transmission likely to
interfere with the message.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/316

Section V -- Transmission of maritime safety information^MOD 1^

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/317

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^1^ **33.V.1** Maritime safety information includes navigation and
meteorological warnings, meteorological forecasts and other urgent
messages pertaining to safety transmitted from coast stations or coast
earth stations.

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/318

**33.39A** to **33.40**

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/319

Section VII -- Use of other frequencies for safety

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/320

**33.53** § 28 Radiocommunications for safety purposes concerning ship
reporting communications, communications relating to the navigation,
movements and needs of ships and weather observation messages may be
conducted on any appropriate communications frequency, including those
used for public correspondence. In terrestrial systems, the bands
between 415 kHz and 535 kHz (see Article **52**), 1 606.5 kHz and
4 000 kHz (see Article **52**), 4 000 kHz and 27 500 kHz (see
Appendix **17**) and 156 MHz and 174 MHz (see Appendix **18**) are used
for this function. In the maritime mobile-satellite service, frequencies
in the bands 1 530-1 544 MHz and 1 626.5-1 645.5 MHz are used for this
function as well as for distress alerting purposes (see No. **32.2**).

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/321

**33.54** to **33.55**

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 34

Alerting signals in the global maritime distress and safety system
(GMDSS)

Section I -- Emergency position-indicating radiobeacon (EPIRB) and\
satellite EPIRB signals

**MOD** IAP/14A2/322

**34.1** § 1 The emergency position-indicating radiobeacon signal
transmitted on 156.525 MHz and satellite EPIRB signals in the band
406-406.1 MHz shall be in accordance with relevant ITU-R
Recommendations, to include but not limited to Recommendation **604
(Rev.Mob-87)**.

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 41

Communications with stations in the maritime services

**MOD** IAP/14A2/323

**41.1** Stations on board aircraft may communicate, for purposes of
distress, and for public correspondence^1^, with stations of the
maritime mobile or maritime mobile-satellite services. For these
purposes, they shall conform to the relevant provisions of
Chapter **VII** and Chapter **IX**, Articles **51** (Section III), **53,
54, 55, 57** and **58** (see also Nos. **4.19, 4.20** and** 43.4**).

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 47

Operator's certificates

Section I -- General provisions

**MOD** IAP/14A2/324

**47.18** § 5 Each administration may determine the conditions under
which personnel holding certificates may be granted certificates
specified in Nos. **47.20** to **47.23**.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/325

Section IV -- Qualifying service     (WRC‑03)

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/326

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^1^ **47.IV.1**

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 51

Conditions to be observed in the maritime services

Section I -- Maritime mobile service

**SUP** IAP/14A2/327

**51.8** to **51.23**

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/328

**51.8** Section B (SUP - WRC‑07)

**51.9** -- **51.23** *(SUP - WRC‑07)*

**Reasons:** Consequential to the suppression of the record notes 51.8
through 51.23.

**MOD** IAP/14A2/329

**51.53** *a)* send class J3E emissions on a carrier frequency of
2 182 kHz and receive class J3E emissions on a carrier frequency of
2 182 kHz, except for such apparatus as is referred to in No. **51.56**;

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/330

**51.58** § 23 All ship stations equipped with radiotelephony to work in
the authorized bands between 4 000 kHz and 27 500 kHz and which do not
comply with the provisions of Chapter** VII** should be able to send and
receive on the carrier frequencies 4 125 kHz and 6 215 kHz. However, all
ship stations which comply with the provisions of Chapter** VII** shall
be able to send and receive on the carrier frequencies designated in
Article** 31** for distress and safety traffic by radiotelephony for the
frequency bands in which they are operating.

**Reasons:** Consequential to GMDSS implementation.

Section III -- Stations on board aircraft communicating with stations
of\
the maritime mobile service and the maritime mobile-satellite service

**MOD** IAP/14A2/331

**51.79** 2) The frequency 156.3 MHz may be used by stations on board
aircraft for safety purposes. It may also be used for communication
between ship stations and stations on board aircraft engaged in
coordinated search and rescue operations (see Appendix **15**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/332

**51.80** 3) The frequency 156.8 MHz may be used by stations on board
aircraft for safety purposes only (see Appendix **15**).

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 52

Special rules relating to the use of frequencies

**SUP** IAP/14A2/333

Section II -- Use of frequencies for Morse radiotelegraphy

**Reasons:** Consequential to GMDSS implementation, remove current
Section II, record notes 52.16 through 52.93.

**SUP** IAP/14A2/334

**52.16** to **52.93**

**Reasons:** Consequential to GMDSS implementation

**MOD** IAP/14A2/335

Section II -- Use of frequencies for narrow-band direct-printing
telegraphy

**Reasons:** Consequential change due to the suppression of the current
Section II -- Use of frequencies for Morse radiotelegraphy.

**MOD** IAP/14A2/336

**52.101** 2) Narrow-band direct-printing telegraphy is forbidden in the
band 2 170-2 194 kHz except as provided for in Appendix **15.**

**Reasons:** Consequential to the changes proposed for Appendix 15.

Section VI -- Use of frequencies for radiotelephony

**MOD** IAP/14A2/337

**52.183** § 86 1) Unless otherwise specified in the present Regulations
(see Nos. **51.53**, **52.188**, **52.189** and **52.199**), the class
of emission to be used in the bands between 1 606.5 kHz and 4 000 kHz
shall be J3E.     (WRC‑07)

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/338

**52.189** § 87 1) The frequency 2 182 kHz^2^ is an international
distress frequency for radiotelephony.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/339

**52.209** 2) The carrier frequencies 2 045 kHz and 2 048 kHz shall not
be used for working between stations of the same nationality^\*^.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/340

**52.221** § 97 1) Ship stations may use the following carrier
frequencies for calling in radiotelephony:

4 125 kHz^3^, MOD ^4^, ^5^

6 215 kHzMOD ^4,\ 5^

8 255 kHz

12 290 kHz^5^ (see also No. **52.221A**)

16 420 kHz^5^ (see also No. **52.221A**)

18 795 kHz

22 060 kHz

25 097 kHz (WRC‑2000)

**MOD** IAP/14A2/340A

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^4^ **52.221.2** The carrier frequencies 4 125 kHz and 6 215 kHz are
also authorized for common use by coast and ship stations for
single-sideband radiotelephony on a simplex basis for call and reply
purposes, provided that the peak envelope power of such stations does
not exceed 1 kW. The use of these frequencies for working purposes is
not permitted (see also No. **52.221.1**).

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/341

**52.231** § 101 1) The frequency 156.8 MHz is the international
frequency for distress traffic and for calling by radiotelephony when
using frequencies in the authorized bands between 156 MHz and 174 MHz.
The class of emission to be used for radiotelephony on the frequency
156.8 MHz shall be G3E (as specified in Recommendation
ITU‑R M.489‑2).     (WRC‑07)

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/342

**52.241A** 10) The frequency 156.525 MHz is the international distress,
safety and calling frequency for the maritime mobile VHF radiotelephone
service using digital selective calling (DSC) when using frequencies in
the authorized bands between 156 MHz and 174 MHz.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/343

**52.241B** 11) All emissions in the band 156.4875-156.5625 MHz capable
of causing harmful interference to the authorized transmissions of
stations of the maritime mobile service on 156.525 MHz are forbidden.

**Reasons:** Consequential to GMDSS implementation.

**ADD** IAP/14A2/344

**52. 241C** 12) To facilitate the reception of distress calls and
distress traffic, all transmissions on 156.525 MHz shall be kept to a
minimum.

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/345

**52.242** § 102 1) A coast station open to the international public
correspondence service should, during its hours of service, maintain
watch on its receiving frequency or frequencies indicated in the List of
Coast Stations.

**Reasons:** Consequential to GMDSS implementation.

ARTICLE 57

Radiotelephony

**MOD** IAP/14A2/346

**57.1** § 1 The procedure detailed in Recommendation ITU‑R M.1171 shall
be applicable to radiotelephone stations, except in cases of distress,
urgency or safety.     (WRC‑07)

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/347

**57.8** § 4 Calling, and signals preparatory to traffic, shall not
exceed one minute when made on the carrier frequency 2 182 kHz or on
156.8 MHz, except in cases of distress, urgency or safety.

**Reasons:** Consequential to GMDSS implementation.

**SUP** IAP/14A2/348

APPENDIX 13 (Rev.WRC‑03)^\*^

Distress and safety communications (non-GMDSS)

(See Article **30**)

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/349

APPENDIX 15 (Rev.WRC-07)

Frequencies for distress and safety communications for the Global\
Maritime Distress and Safety System (GMDSS)

(See Article **31**)

The frequencies for distress and safety communications for the GMDSS are
given in Tables 15‑1 and 15-2 for frequencies below and above 30 MHz,
respectively.

TABLE 15-1

Frequencies below 30 MHz

TABLE 15-1 (*end *)

TABLE 15-2

Frequencies above 30 MHz (VHF/UHF)

TABLE 15-2 (*end *)

**Reasons:** Consequential to GMDSS implementation. Automatic
Identification System (AIS) is also added due to its safety use and to
the International Maritime Organization Subcommittee on Communications
and Search and Rescue's decision to use AIS for locating purposes under
the GMDSS (AIS-SART). Asterisks added consequential to ship-to-ship
safety of navigation communications (Article 33, No. 33.3), support
communications for search and rescue operations (Article 33, No. 33.5),
and communications relating to the navigation, movements and needs of
ships (Article 33, No. 33.7) inclusion as urgency and safety
communications (Article 33, No. 33.1).

APPENDIX 16

Documents with which stations on board ships\
and aircraft shall be provided

(See Articles **42** and **51**)

**MOD** IAP/14A2/350

Section I -- Ship stations for which a Global Maritime Distress and
Safety System (GMDSS) installation is required by international
agreement

These stations shall be provided with:

1 the licence prescribed by Article **18**;

2 certificates of the operator or operators;

3 a log in which the following are recorded as they occur, together with
the time of the occurrence, unless administrations have adopted other
arrangements for recording all information which the log should contain:

*a)* a summary of communications relating to distress, urgency and
safety traffic;

*b)* a reference to important service incidents;

*c)* if the ship's rules permit, the position of the ship at least once
a day;

4 ITU Service Publications, in either printed or electronic format,
containing a list of MMSI stations and other operational information in
the Maritime Mobile Service (see Article **20**);

5 ITU Service Publications, in either printed or electronic format,
showing the details of coast stations and coast earth stations with
which communications are likely to be conducted and a list of coast
stations and coast earth stations providing navigational and
meteorological warnings and other urgent information for ships (see
Article **20**);

6 the relevant rules and procedures of radiocommunications, e.g. Manual
for Use by the Maritime Mobile and Maritime Mobile-Satellite Services
(paper or electronic format) (see Article **20**).

NOTE -- Administrations may, under appropriate circumstances, exempt
ships from the carriage of the documents mentioned in items 4 to 6
above, or where equivalent publications with the same and similarly
updated content exist, notify the changed carrier requirement to the
Bureau which will make this publicly available.

**Reasons:** Consequential to GMDSS implementation. Provisions allowing
recreational vessels and other small vessels licensed by regulation to
travel between neighbouring administrations by mutual agreement is also
included.

**MOD** IAP/14A2/351

Section II -- Other ship stations for which a radio installation is
required

These stations shall be provided with:

1 the licence prescribed by Article **18**;

2 certificates of the operator or operators;

3 a log or other arrangements which the administration may have adopted
for that purpose, in which a summary of communications related to
distress, urgency and safety traffic shall be recorded together with the
time of their occurrence;

4 ITU Service Publications, in either printed or electronic format,
showing the details of coast stations with which communications are
likely to be conducted and a list of coast stations and coast earth
stations providing navigational and meteorological warnings and other
urgent information for ships (see Article **20**);

5 the relevant rules and procedures of radiocommunications, e.g. Manual
for Use by the Maritime Mobile and Maritime Mobile-Satellite Services
(paper or electronic format) (see Article **20**).

NOTE -- Administrations may, under appropriate circumstances, exempt
ships from the carriage of the documents mentioned in items 4 and 5
above, or where equivalent publications with the same and similarly
updated content exist, notify the changed carrier requirement to the
Bureau which will make this publicly available.

Section III -- Other ship stations

These stations shall be provided with:

1 the documents mentioned in items 1 and 2 of Section II;

2 the documents mentioned in items 4 and 5 of Section II, in accordance
with the requirements of the administrations concerned.

NOTE -- Administrations may, under appropriate circumstances, exempt
ships from the carriage of the documents mentioned in item 2, or where
equivalent publications with the same and similarly updated content
exist, notify the changed carrier requirement to the Bureau which will
make this publicly available. Administrations may also, under
appropriate circumstances and mutual agreement, exempt ships travelling
only between their national jurisdictions from the licensing prescribed
by Article **18** and the carriage of the documents mentioned in item 1
immediately above, provided those vessels are otherwise licensed or
authorized by regulation.

**Reasons:** Consequential to GMDSS implementation. Provides provisions
which would permit the establishment of agreements, among neighbouring
administrations to allow recreational vessels and other small vessels
licensed by regulation to travel between those neighbouring
administrations by mutual agreement.

**SUP** IAP/14A2/352

Section V -- Ship stations equipped with multiple installations

**SUP** IAP/14A2/352A

Section VA -- Stations on board ships for which a GMDSS installation is\
required by international agreement

**Reasons:** Consequential to GMDSS implementation.

**MOD** IAP/14A2/353

Section IV -- Stations on board aircraft

These stations shall be provided with:

1 the documents mentioned in items 1 and 2 of Section I;

2 a log, unless administrations have adopted other arrangements for
recording all information which the log should contain;

3 those published documents, in either printed or electronic formats,
containing official information relating to stations which the aircraft
station may use for the execution of its service.

**Reasons:** Consequential to GMDSS implementation. Provisions allowing
recreational vessels and other small vessels licensed by regulation to
travel between neighbouring administrations by mutual agreement is also
included.

**SUP** IAP/14A2/354

APPENDIX 19

Technical characteristics of emergency position-indicating radiobeacons\
operating on the carrier frequency 2 182 kHz

(See Appendix **13**, Part A5)

**Reasons:** Consequential to GMDSS implementation.

Proposals for Issue B:

**MOD** IAP/14A2/355

APPENDIX 18 (Rev.WRC-07)

Table of transmitting frequencies in the VHF\
maritime mobile band

(See Article **52**)

**Reasons:** Consequential date change.

**MOD** IAP/14A2/356

NOTE A -- For assistance in understanding the Table, see Notes *a)* to
*p)* below.     (WRC‑07)

NOTE B -- The Table below defines the channel numbering for conventional
maritime VHF based on 25 kHz channel spacing and use of several duplex
channels but allows also the use of 12.5 kHz channel spacing. The
channel numbering for 12.5 kHz channels and the conversion of
two-frequency channels for single-frequency operation shall be in
accordance with Recommendation ITU‑R M.1084-4 Annex 4, Tables 1 and 3.

**Reasons:** Clarification.

**MOD** IAP/14A2/357

**Reasons:** Clarification; consequential to note changes

**Notes referring to the Table**

*General notes*

**MOD** IAP/14A2/358

*e)* Administrations may apply 12.5 kHz channel interleaving on a
non-interference basis to 25 kHz channels, in accordance with the most
recent version of Recommendation ITU‑R M.1084, provided:

-- it shall not affect the 25 kHz channels of the present Appendix
maritime mobile distress and safety frequencies, especially the channels
06, 13, 15, 16, 17, and 70, nor the technical characteristics set forth
in Recommendation ITU-R M.489-2 for those channels;

-- implementation of 12.5 kHz channel interleaving and consequential
national requirements shall be subject to prior agreement between the
implementing administrations and administrations whose ship stations or
services may be affected.

**Reasons:** Clarification and consequential updates.

*Specific notes*

**MOD** IAP/14A2/359

*f)* The frequencies 156.300 MHz (channel 06) , 156.525 MHz
(channel 70), 156.800 MHz (channel 16), 161.975 MHz (AIS 1) and
162.025 MHz (AIS 2) may also be used by aircraft for the purpose of
search and rescue operations and other safety-related communications.

**Reasons:** Clarification and updates consequential to GMDSS and AIS.

**MOD** IAP/14A2/360

*l)* These channels (AIS 1 and AIS 2) are used for an automatic
identification system capable of providing worldwide operation in
accordance with ITU‑R Recommendations, unless other frequencies are
designated on a regional basis for this purpose.

**Reasons:** Clarification and consequential updates.

**MOD** IAP/14A2/361

*m)* These channels may be operated as single frequency channels,
subject to prior agreement between interested and affected
administrations.     (WRC‑07)

**MOD** IAP/14A2/361A

*o)* These channels may be used to provide bands for new technologies,
subject to prior agreement between interested and affected
administrations. Stations using these channels or bands for new
technologies shall not cause harmful interference to, and shall not
claim protection from, other stations operating in accordance with this
Appendix or Article **5**. The design of such systems shall be such as
to preclude the possibility of interference to the detection of AIS
signals on 161.975 or 162.025 MHz. (WRC‑07)

**Reasons:** To enable new wideband data systems in these bands, while
ensuring they do not interfere with the reception of AIS.

**ADD** IAP/14A2/362

*p)* Additionally, AIS 1 and AIS 2 may be used by the maritime
mobile-satellite service (Earth-to-space) for the reception of AIS
transmissions from ships.

**Reasons:** To recognize long range detection of AIS for security
reasons.

**ADD** IAP/14A2/363

*q)* When using these channels (10 and 11), all precautions should be
taken to avoid harmful interference to channel 70.

**Reasons:** Consequential to GMDSS implementation.

**[NOC]{.underline}** IAP/14A2/364

APPENDIX 17 (Rev.WRC-03)

Frequencies and channelling arrangements in the\
high-frequency bands for the maritime mobile service

(See Article **52**)

**Reasons:** This appendix should not be opened until evolving
requirements from the International Maritime Organization regarding HF
data in the GMDSS and electronic navigation (E-Nav) spectrum
requirements are identified, so that they can be accommodated.

**MOD** IAP/14A2/365

RESOLUTION 18 (Rev.WRC‑07)

Relating to the procedure for identifying and announcing the position
of\
ships and aircraft of States not parties to an armed conflict[^10]

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that ships and aircraft encounter considerable risk in the vicinity
of an area of armed conflict;

*b)* that for the safety of life and property it is desirable for ships
and aircraft of States not parties to an armed conflict to be able to
identify themselves and announce their position in such circumstances;

*c)* that radiocommunication offers such ships and aircraft a rapid
means of self-identification and providing location information prior to
their entering areas of armed conflict and during their passage through
the areas;

*d)* that it is considered desirable to provide a supplementary signal
and procedure for use, in accordance with customary practice, in the
area of armed conflict by ships and aircraft of States representing
themselves as not parties to an armed conflict;

resolves

1 that the frequencies for urgency signal and messages specified in the
Radio Regulations may be used by ships and aircraft of States not
parties to an armed conflict for self-identification and establishing
communications. The transmission will consist of the urgency or safety
signals, as appropriate, described in Article **33** followed by the
addition of the single group \"NNN\" in radiotelegraphy and by the
addition of the single word "NEUTRAL" pronounced as in French "neutral"
in radiotelephony. As soon as practicable, communications shall be
transferred to an appropriate working frequency;

2 that the use of the signal as described in the preceding paragraph
indicates that the message which follows concerns a ship or aircraft of
a State not party to an armed conflict. The message shall convey at
least the following data:

*a)* call sign or other recognized means of identification of such ship
or aircraft;

*b)* position of such ship or aircraft;

*c)* number and type of such ships or aircraft;

*d)* intended route;

*e)* estimated time en route and of departure and arrival, as
appropriate;

*f)* any other information, such as flight altitude, radio frequencies
guarded, languages and secondary surveillance radar modes and codes;

3 that the provisions of Article **33** relating to urgency and safety
transmissions, and medical transports shall apply as appropriate to the
use of the urgency and safety signals, respectively, by such ship or
aircraft;

4 that the identification and location of ships of a State not party to
an armed conflict may be effected by means of appropriate standard
maritime radar transponders. The identification and location of aircraft
of a State not party to an armed conflict may be effected by the use of
the secondary surveillance radar (SSR) system in accordance with
procedures to be recommended by the International Civil Aviation
Organization (ICAO);

5 that the use of the signals described above would not confer or imply
recognition of any rights or duties of a State not party to an armed
conflict or a party to the conflict, except as may be recognized by
common agreement between the parties to the conflict and a non-party;

6 to encourage parties to a conflict to enter into such agreements,

requests the Secretary-General

to communicate the contents of this Resolution to the International
Maritime Organization (IMO) and ICAO for such action as they may
consider appropriate,

requests ITU‑R

to recommend an appropriate signal in the digital selective calling
system for use in the maritime mobile service and other appropriate
information as necessary.

**ADD** IAP/14A2/366

Resolution  \[IAP/14A2/366\] (WRC‑07)

Distress and safety radiotelephony procedures for 2 182 kHz

The World Radiocommunication Conference (Geneva, 2007),

noting

*a)* that all ships subject to the International Convention for the
Safety of Life at Sea (SOLAS), 1974, as amended, are required to be
fitted for the Global Maritime Distress and Safety System (GMDSS);

*b)* that some vessels not subject to SOLAS, 1974, as amended, may not
be making use of the techniques and frequencies of the GMDSS prescribed
in Chapter **VII** and may wish to continue using radiotelephony
procedures for distress and safety communications on 2 182 kHz until
such time as they are able to participate in the GMDSS;

*c)* that some administrations may have a need to maintain shore-based
radiotelephony distress and safety services on 2 182 kHz so that vessels
not subject to SOLAS, 1974, as amended, and not yet using the techniques
and frequencies of the GMDSS, will be able to obtain assistance from
these services until such time as they are able to participate in the
GMDSS,

considering

*a)* that there needs to be some recognized guidance, for the use of
radiotelephony on 2 182 kHz for distress and safety communications,

resolves

1 that ships, when in distress or when engaged in urgency or
safety-related communications on 2 182 kHz, use the radiotelephony
procedures contained in the Annex to this Resolution;

2 that coast stations, in order to maintain communication with non-GMDSS
ships in distress or engaged in urgency or safety-related communications
on 2 182 kHz, use the radiotelephony procedures contained in the
Annex to this Resolution.

ANNEX TO RESOLUTION \[IAP/14A2/366\] (WRC‑07)

Distress and safety radiotelephony procedures for 2 182 kHz[^11]

PART A1 -- GENERAL

§ 1 The frequencies and techniques specified in this Resolution may be
used in the maritime mobile service for stations[^12] not required by
national or international regulation to fit GMDSS equipment and for
communications between those stations and aircraft. However, stations of
the maritime mobile service, when additionally fitted with any of the
equipment used by stations operating in conformity with the provisions
specified in Chapter **VII**, should, when using that equipment, comply
with the appropriate provisions of that Chapter.

§ 2 1) No provision of these Regulations prevents the use by a mobile
station or mobile earth station in distress of any means at its disposal
to attract attention, make known its position, and obtain help.

2\) No provision of these Regulations prevents the use by stations on
board aircraft or ships engaged in search and rescue operations, in
exceptional circumstances, of any means at their disposal to assist a
mobile station or mobile earth station in distress.

3\) No provision of these Regulations prevents the use by a land station
or coast earth station, in exceptional circumstances, of any means at
its disposal to assist a mobile station or mobile earth station in
distress (see also No. **4.16**).

§ 3 In cases of distress, urgency or safety, transmissions by
radiotelephony should be made slowly and distinctly, each word being
clearly pronounced to facilitate transcription.

§ 4 The abbreviations and signals of Recommendation ITU‑R M.1172 and the
Phonetic Alphabet and Figure Code in Appendix **14** should be used
where applicable[^13].

§ 5 Distress, urgency and safety transmissions may also be made using
digital selective calling and satellite techniques and/or
direct-printing telegraphy, in accordance with the provisions specified
in Chapter **VII** and relevant ITU‑R Recommendations.

§ 6 Mobile stations[^14] of the maritime mobile service may communicate,
for safety purposes, with stations of the aeronautical mobile service.
Such communications shall normally be made on the frequencies
authorized, and under the conditions specified, in Section I of Part A2
(see also § 2 1)).

§ 6A Mobile stations of the aeronautical mobile service may communicate,
for distress and safety purposes, with stations of the maritime mobile
service in conformity with the provisions of this Resolution.

§ 7 Any aircraft required by national or international regulations to
communicate for distress, urgency or safety purposes with stations of
the maritime mobile service shall be capable of transmitting and
receiving class J3E emissions when using the carrier frequency 2 182 kHz
or the carrier frequency 4 125.

PART A2 -- FREQUENCIES FOR DISTRESS AND SAFETY

Section I -- Availability of frequencies

A -- 2 182 kHz

§ 1 1) The carrier frequency 2 182 kHz is an international distress
frequency for radiotelephony; it may be used by ship, aircraft and
survival craft stations when requesting assistance from the maritime
services. It is used for distress calls and distress traffic, for the
urgency signal and urgency messages and for the safety signal. Safety
messages should be transmitted, when practicable, on a working frequency
after a preliminary announcement on 2 182 kHz. The class of emission to
be used for radiotelephony on the frequency 2 182 kHz shall be J3E.
Distress traffic on 2 182 kHz following the reception of a distress call
using digital selective calling should take into account that some
shipping in the vicinity may not be able to receive this traffic.

2\) If a distress message on the carrier frequency 2 182 kHz has not
been acknowledged, the distress call and message may be transmitted
again on a carrier frequency of 4 125 kHz or 6 215 kHz, as appropriate.

3\) However, ship stations and aircraft which can transmit neither on
the carrier frequency 2 182 kHz nor on the carrier frequencies 4 125 kHz
or 6 215 kHz, may use any other available frequency on which attention
might be attracted.

4\) Coast stations using the carrier frequency 2 182 kHz for distress
purposes and to send navigational warnings may transmit an audible alarm
signal[^15] of a short duration for the purpose of attracting attention
to the message which follows.

B -- 4 125 kHz

§ 2 1) The carrier frequency 4 125 kHz is used to supplement the carrier
frequency 2 182 kHz for distress and safety purposes and for call and
reply. This frequency is also used for distress and safety traffic by
radiotelephony.

2\) The carrier frequency 4 125 kHz may be used by aircraft to
communicate with stations of the maritime mobile service for distress
and safety purposes, including search and rescue.

C -- 6 215 kHz

§ 3 The carrier frequency 6 215 kHz is used to supplement the carrier
frequency 2 182 kHz for distress and safety purposes and for call and
reply. This frequency is also used for distress and safety traffic by
radiotelephony.

Section II -- Protection of distress and safety frequencies

A -- General

§ 4 1) Test transmissions on any of the distress and safety frequencies
described above shall be kept to a minimum and, wherever practicable, be
carried out on artificial antennas or with reduced power.

§ 5 Before transmitting on any of the frequencies identified for
distress and safety communications, a station shall listen on the
frequency concerned to make sure that no distress transmission is being
sent (see Recommendation ITU‑R M.1171). This does not apply to stations
in distress.

B -- 2 182 kHz

§ 6 1) Except for transmissions authorized on the carrier frequency
2 182 kHz and on the frequencies 2 174.5 kHz, 2 177 kHz, 2 187.5 kHz and
2 189.5 kHz, all transmissions on the frequencies between 2 173.5 kHz
and 2 190.5 kHz are forbidden (see also Appendix **15**).

2\) To facilitate the reception of distress calls, all transmissions on
2 182 kHz should be kept to a minimum.

Section III -- Watch on distress frequencies

A -- 2 182 kHz

§ 7 1) Coast stations may maintain a watch on the carrier frequency
2 182 kHz if so directed by the Administration. Such watch should be
indicated in the List of Coast Stations.

2\) Ship stations not fitted with equipment compatible with the GMDSS
are encouraged to keep the maximum watch practicable on the carrier
frequency 2 182 kHz.

B -- 4 125 kHz, 6 215 kHz

§ 8 1) Coast stations may maintain additional watch, as permitted, on
the carrier frequencies 4 125 kHz and 6 215 kHz. Such watch, if
maintained, should be indicated in the List of Coast Stations.

Part A3 -- Distress communications

Section I -- General

§ 1 The general provisions for distress communications are found in
Section I of Article **32** (see Nos. **32.1**, **32.3**, and **32.4**).

Section II -- Distress signal, call and message

§ 2 The radiotelephone distress signal, call and message are described
in Section II of Article **32** (see Nos. **32.10C**, **32.10D**,
**32.13B**, **32.13C**, and **32.13D**).

Section III -- Procedures

§ 3 After the transmission by radiotelephony of its distress message,
the mobile station may be requested to transmit suitable signals
followed by its call sign or other identification, to permit
direction-finding stations to determine its position. This request may
be repeated at frequent intervals if necessary.

§ 4 1) The distress message, preceded by the distress call, shall be
repeated at intervals until an answer is received.

2\) The intervals shall be sufficiently long to allow time for replying
stations preparing to start their sending apparatus.

§ 5 When the mobile station in distress, receives no answer to a
distress message sent on the distress frequency, the message may be
repeated on any other available frequency on which attention might be
attracted.

Section IV -- Transmission of a distress relay message by a station not
itself in distress

§ 7 The radiotelephone procedures for the transmission of a distress
relay message by a station not itself in distress are found in Section
II of Article **32** (see Nos. **32.16** to **32.19A** and **32.19D** to
**32.19F**).

Section V -- Receipt and Acknowledgement of a distress message

§ 8 The procedures relating to the receipt and acknowledgement of a
distress message are found in Section II of Article 32 (see Nos.
**32.21**, **32.23** and **32.26** to **32.30**).

§ 9 1) Every mobile station acknowledging receipt of a distress message
shall, on the order of person responsible for the ship, aircraft or
other vehicle, transmit, the following information in the order shown as
soon as possible:

-- its name;

-- its position;

-- the speed at which it is proceeding towards, and the approximate time
it will take to reach, the mobile station in distress;

-- additionally, if the position of the ship in distress appears
doubtful, ship stations should also transmit, when available, the true
bearing of the ship in distress.

2\) Before transmitting the message specified in § 9 1), the station
shall ensure that it will not interfere with the emissions of other
stations better situated to render immediate assistance to the station
in distress.

Section VI -- Distress traffic

§ 15 The radiotelephone procedures relating to the distress traffic are
found in Section III of Article **32** (see Nos. **32.39** to
**32.63**).

Part A4 -- URGENCY and safety COMMUNICATIONS

Section I -- Urgency communications

§ 1 The radiotelephone procedures for urgency communications are found
in Sections I and II of Article **33** (see Nos. **33.1** to **33.18**).

Section II -- Safety communications

§ 2 The radiotelephone procedures for safety communications are found in
Sections I and IV of Article **33** (see Nos. **33.1** to **33.7B** and
**33.31** to **33.38B**).

**Reasons:** The addition of Resolution \[IAP/14A2/366\] (WRC‑07) as
shown in section 5/1.14/5.1 of the CPM report is supported, taking into
account some modifications to Parts A1, A3 and A4.

#### Agenda item 1.16

1.16 to consider the regulatory and operational provisions for Maritime
Mobile Service Identities (MMSIs) for equipment other than shipborne
mobile equipment, taking into account Resolutions** 344 (Rev.WRC‑03)**
and **353 (WRC‑03)**

Proposals for Agenda item 1.16

Background information

WRC‑03 identified a need to assign Maritime Mobile Service Identities
(MMSIs) to Search and Rescue (SAR) aircraft stations and aids to
navigation. The assignment of MMSIs to Search and Rescue (SAR) aircraft
stations, Aids to Navigation (AtoN) and other stations is proposed to
improve maritime safety and enhance maritime navigation systems.

SAR aircraft require MMSIs for use with digital selective calling (DSC)
to enable effective communications with GMDSS equipped ships during
emergency communications. Further, MMSIs are used with Automatic
Identification System (AIS) equipment on-board SAR aircraft for
applications relating to safety and security in the maritime mobile
service. In respect to AtoN, the assignment of MMSIs will permit the
introduction of AIS technologies for these systems to increase maritime
navigation safety. In the course of ITU‑R Working Party 8B studies, an
additional need was identified for unique MMSI assignments to crafts
associated with another vessel.

Currently, Article 19 of the Radio Regulations contains regulatory
provisions for the assignment of MMSIs only to ship and coast stations
and Recommendation ITU‑R M.585-3 provides additional guidance relating
to the assignment and use of these identities only for ships. Revisions
to Article 19 and Recommendation ITU‑R M.585-3 are required to introduce
provisions for MMSI assignments to SAR aircraft, aids to navigation, and
crafts associated with a parent vessel. An updated Recommendation ITU‑R
M.585-4 should be published and available before the convening of
WRC‑07.

Efficiencies would be gained by placing the procedural provisions for
MMSI assignments only within Recommendation ITU‑R M.585 and
incorporating this recommendation by reference into Article 19 in
accordance with Resolutions 27 (Rev.WRC‑03) and 28 (Rev.WRC‑03). This
method avoids the need to maintain two separate and differing MMSI
procedures, one in Article 19 and another in Recommendation ITU‑R M.585,
as advances in maritime technology inevitably requires updates to MMSI
procedures. It also avoids the need to repeatedly place this matter on
the agenda of future WRCs. Finally, it will help ensure an adequate
number of maritime identification digits (MIDS) are available to all
administrations needs in the future.

**NOC** IAP/14A2/367

RESOLUTION 344 (Rev.WRC-03)

Management of the maritime mobile service identity\
numbering resource

**Reasons:** The Director of the Radiocommunication Bureau needs to
continue to manage the allotment and distribution of the MID resources
within the MMSI numbering format, taking into account Article 19 and
Recommendation ITU‑R M.585.

**SUP** IAP/14A2/368

RESOLUTION 353 (WRC-03)

Maritime mobile service identities for equipment\
other than shipborne mobile equipment

**Reasons:** Recommendation ITU‑R M.585-4, the relevant recommendation,
has been revised by ITU‑R SG 8 to address the expanded use of MMSI for
equipment other than shipborne mobile equipment (i.e. SAR aircraft).

ARTICLE 19

Identification of stations

Section II -- Allocation of international series and assignment of call
signs

**MOD** IAP/14A2/369

**19.30** 2) As the need arises, ship stations and ship earth stations
to which the provisions of Chapter **IX** apply, and coast stations,
coast earth stations, or other stations capable of commu­nicating with
such ship stations, shall have assigned to them maritime mobile service
identities in accordance with Section VI of this Article.

**Reasons:** Extends provisions for MMSI assignments to other
non-shipborne stations (e.g. search and rescue aircraft, aids to
navigation, and crafts associated with a parent vessel). The types of
non-shipborne stations are not specified in order to allow for future
additional MMSI requirements without the need for revisions to
Article 19.

**MOD** IAP/14A2/370

Section VI -- Maritime mobile service identities

**Reasons:** Disassociates the assignment of MMSIs to only those
stations specified in the definitions for the maritime mobile service
and the maritime mobile-satellite service.

**MOD** IAP/14A2/371

**19.99** § 39 When a station^5^ operating in the maritime mobile
service or the maritime mobile‑satellite service is required to use
maritime mobile service identities, the responsible admin­istration shall
assign the identity to the station in accordance with the provisions
described in Recommendation ITU‑R M.585-4; in so doing, it should take
into account any other relevant ITU‑R and ITU‑T Recommendations. In
accordance with No. **20.16,** administrations shall notify the Bureau
immediately when assigning maritime mobile service identities

**Reasons:** Extends the requirement to use MMSIs to stations other than
only those specified in the definitions for the maritime mobile service
and the maritime mobile satellite service (e.g. search and rescue
aircraft, aids to navigation, and crafts associated with a parent
vessel) and incorporates by reference the provisions describing the
assignment of MMSIs in an approved revision of Recommendation ITU‑R
M.585.

**MOD** IAP/14A2/372

**19.100** § 40 1) Maritime mobile service identities are formed of a
series of nine digits which are transmitted over the radio path in order
to uniquely identify ship stations, ship earth stations, coast stations,
coast earth stations, group calls, and other non-shipborne stations
operating in the maritime mobile service or the maritime
mobile-satellite service.

**Reasons:** Expands the description of MMSIs to include other
non-shipborne stations (e.g. search and rescue aircraft, aids to
navigation, and crafts associated with a parent vessel). The types of
non-shipborne stations are not specified in order to allow for future
additional MMSI requirements without the need for revisions to
Article 19.

**MOD** IAP/14A2/373

**19.102** 3) The types of maritime mobile service identities shall be
as described in Recommendation ITU‑R M.585-4.

**Reasons:** Amendment removes the specific MMSI types from Article 19
and incorporates by reference the provisions describing the types of
MMSIs in an approved revision of Recommendation ITU‑R M.585.

**SUP** IAP/14A2/374

**19.103** to **19.107**

**Reasons:** Removes the specific types of MMSIs from Article 19 since
these are described in an approved revision of Recommendation ITU‑R
M.585 which is proposed to be incorporated by reference.

**MOD** IAP/14A2/375

**19.108A** § 41 The maritime identification digits M~1~I~2~D~3~ are an
integral part of the maritime mobile service identity and denote the
geographical area of the administration responsible for the station so
identified.     (WRC-03)

**Reasons:** Consequential change resulting from the modification of
provision 19.102 and the suppression of provisions 19.103 to 19.106.

**MOD** IAP/14A2/376

**19.110** *C --* *Maritime Mobile Service* *Identities* *(MMSIs)*

**Reasons:** Consequential change resulting from the modification of
provisions 19.111 to 19.114 and the suppression of provisions 19.117 to
19.126. Section is modified to address MMSI regulatory provisions in
general since the procedural provisions for specific MMSI assignments
(e.g. ship station identities, group ship station call identities, coast
station identities, and group coast station call identities) are
proposed to be transferred into and incorporated by reference in an
approved revision of Recommendation ITU‑R M.585.

**MOD** IAP/14A2/377

**19.111** § 43 1) Administrations shall follow the provisions contained
in Recommendation ITU‑R M.585-4 concerning the assignment and use of
maritime mobile service identities.

**Reasons:** Incorporates by reference the provisions prescribing the
assignment of MMSIs in an approved revision of Recommendation ITU‑R
M.585.

**MOD** IAP/14A2/378

**19.112** 2) Administrations should:

**19.113** *a)* make optimum use of the possibilities of forming
identities from the single MID allocated to them;

**19.114** *b)* take particular care in assigning ship station
identities with six significant digits (i.e. having three-trailing-zero
identities), which should be assigned only to ship stations which can
reasonably be expected to require such an identity for automatic access
on a worldwide basis to public switched networks, in particular
for mobile-satellite systems accepted for use in the GMDSS on or before
1 February 2002, as long as those systems maintain the MMSI as part of
their numbering scheme.     (WRC-03)

**Reasons:** Amendments are consequential changes resulting from the
modification of provision 19.111.

**SUP** IAP/14A2/379

**19.117** to **19.126**

**Reasons:** Removes provisions specifying formats for ship station,
group ship station call, coast station, group coast station call
identities which are no longer required since these provisions are
proposed to be incorporated by reference through revisions to provisions
19.99, 19.102, and 19.111.

#### Agenda item 1.18

1.18 to review pfd limits in the band 17.7-19.7 GHz for satellite
systems using highly inclined orbits, in accordance with Resolution
**141 (WRC‑03)**

Proposals for Agenda item 1.18

Background information

ITU‑R has been considering the sharing aspects for non-GSO
fixed-satellite service systems using highly-inclined orbits (HIOs),
including highly elliptical orbit (HEO) satellite systems, in a number
of contexts and under a number of different names in recent years.
Several categories of non-GSOs are encompassed within the term
"highly-inclined," but all HIO systems are non-geostationary satellite
orbit (non-GSO) systems, and hence are subject to all limitations that
apply to non-GSO systems in the Radio Regulations. Specifically, all HIO
systems are treated as non-GSO systems by the ITU when they are examined
for regulatory compliance. WRC‑95 adopted provisional limits on the pfd
produced at the surface of the Earth by non-GSO satellites operating in
the FSS (space-to-Earth) in the band 17.7-19.7 GHz in order to protect
terrestrial services. WRC‑97 and WRC‑2000 modified the Article 21 power
flux-density (pfd) limits that apply to non-GSO FSS system satellites,
including HIO satellites, to adequately protect terrestrial systems in
the 17.7-19.7 GHz frequency band.

In Resolution 141 (WRC‑03), ITU‑R was invited to determine whether the
current pfd limits for non-GSO FSS satellite systems in Article 21 are
adequate to protect the fixed service in the 17.7 to 19.7 GHz band from
non-GSO systems using highly inclined orbits, without unduly
constraining the use of these non-GSO systems. Resolution 141 (WRC‑03)
also calls for a determination to be made as to whether there are
technical and operational measures that could be implemented by the
fixed service to mitigate interference from FSS space stations.

Studies performed in ITU‑R, using conservative but feasible assumptions
for satellite operations, show conclusively that systems of HIO
satellites operating at the pfd limits from Article 21, Table 21-4,
applicable to non-GSO FSS satellites in the 17.7-19.7 GHz band
adequately protect the fixed service. It is noteworthy that at least one
HEO system has been operating in the 17.7-19.7 GHz band for years at the
power levels in the applicable portion of Article 21, and that to date,
there have been no reports of interference from the non-GSO FSS into the
fixed service.

The following proposals under Agenda item 1.18 are intended to resolve
the question of the appropriate pfd limits to apply to non-GSO FSS
systems using highly-inclined orbits having an apogee altitude greater
than 18 000 km and an orbital inclination between 35 and 145 --
especially, but not exclusively, those operating in highly-elliptical
orbits.

Issues

1 Whether the current pfd limits in Article 21 for non-geostationary
(non-GSO) systems in the FSS are adequate to protect the fixed service
in the 17.7-19.7 GHz band from non-GSO systems using highly inclined
orbits (HIO) having an apogee altitude greater than 18 000 km and an
orbital inclination between 35° and 145°, without unduly constraining
the use of these non-GSO FSS systems.

2 Whether there are technical and operational measures in the band
17.7-19.7 GHz that could be implemented in the fixed service to mitigate
interference from FSS space stations in HIO.

**NOC** IAP/14A2/380

ARTICLE 1

Terms and definitions

We propose NOC in relation to HIO-type or HEO-type non-GSO operations
referred to in Article 1.

**Reasons:** Satellite networks using highly-inclined orbits, including
HEOs, should continue to be considered as non-GSOs so there is no need
to modify the terms and definitions in the Radio Regulations to
accommodate HIO-type or HEO-type non-GSO operations.

ARTICLE 21

Terrestrial and space services sharing frequency bands above 1 GHz

Section V -- Limits of power flux-density from space stations

**NOC** IAP/14A2/381

TABLE **21-4***  *(*continued*)     (WRC-03)

**Reasons:** The current pfd limits and associated provisions in Section
V of Article 21 that were finalized at WRC‑2000 for all non-GSO FSS
systems in the 17.7-19.3 GHz frequency band, and the limits that apply
to all FSS satellites in the 19.3-19.7 GHz band, are adequate to protect
the fixed service in the 17.7-19.7 GHz band from non-GSO FSS systems
using highly-inclined orbits having an apogee altitude greater than
18 000 km and an orbital inclination between 35 and 145°. Satellite
networks using HIOs, including non-GSO systems using HEO, should
continue to be considered as non-GSOs and have the same regulatory
standing as other types of non-GSOs. No additional regulatory provisions
are needed for such systems.

**SUP** IAP/14A2/382

RESOLUTION 141 (WRC‑03)

Sharing between certain types of non-geostationary-satellite systems\
in the fixed-satellite service and stations in the fixed service\
in the 17.7-19.7 GHz band

**Reasons:** All of the actions required under this Resolution have been
completed and it may be suppressed. The technical studies confirmed that
the current pfd limits for non‑GSO FSS systems in Article 21 are
adequate to protect the fixed service in the 17.7-19.7 GHz band from
non-GSO systems having an apogee altitude greater than 18 000 km and an
orbital inclination between 35 and 145°, without unduly constraining the
non-GSO FSS systems. With the suppression of this Resolution, there is
no need for the Radiocommunication Bureau to review or revise any
findings made on the compliance with the limits contained in Article 21
of a highly-inclined orbit non‑GSO FSS system for which complete advance
publication information has not been received prior to 5 July 2003.

#### Agenda item 2

2 to examine the revised ITU-R Recommendations incorporated by reference
in the Radio Regulations communicated by the Radiocommunication
Assembly, in accordance with Resolution **28 (Rev.WRC‑03)**, and to
decide whether or not to update the corresponding references in the
Radio Regulations, in accordance with principles contained in the Annex
to Resolution **27** **(Rev.WRC‑03)**

Background information

Resolution 28 (Rev.WRC‑03) *urges administrations* to examine any
indicated revisions of ITU‑R Recommendations containing text
incorporated by reference and to prepare proposals on possible updating
of relevant references in the Radio Regulations.

Annex 1 to Resolution 27 (Rev.WRC‑03) lists the principles for
incorporation by reference. Principle 5 states:

"If, between WRCs, a text incorporated by reference (e.g. an
ITU‑Recommendation) is updated, the reference in the Radio Regulations
shall continue to apply to the earlier version incorporated by reference
until such time as a competent WRC agrees to incorporate the new
version. The mechanism of considering such as step is given in
Resolution **28 (Rev.WRC‑03)**."

Accordingly, proposals are included below to update the references in
the Radio Regulations to ITU‑R Recommendations incorporated by reference
to reflect the latest version, where it is deemed appropriate.

Resolution 27 (Rev.WRC‑03) *invites administrations* to submit proposals
to future conferences, taking into account the CPM Report, in order to
clarify the status of references, where ambiguities remain regarding the
mandatory or non-mandatory status of the references in question, with a
view to amending those references:

i\) that appear to be of a mandatory nature, identifying such references
as being incorporated by reference by using clear linking language in
accordance to Annex 2;

ii\) that are of a non-mandatory character, so as to refer to "the most
recent version" of the Recommendations.

Accordingly, proposals are included below to clarify the status of
existing references to ITU‑R Recommendations and to correct, among other
things, any remaining ambiguities.

The CPM Report addresses the two types of proposals described above
(i.e. 1) updating references in the Radio Regulations to reflect new
versions of ITU‑R Recommendations, and 2) clarifying the status of
references) and was used as the basis for some of the proposals included
below. The CPM Report also describes a third situation where a WRC
Resolution includes a *resolves* referring to an ITU‑R Recommendation
using mandatory language (i.e. shall). In this situation, the ITU‑R
Recommendation or parts thereof, as may be specified, are considered to
be incorporated by reference. Therefore, in order to clarify the scope
of incorporation by reference and confirm the treatment of those ITU‑R
Recommendations, Resolution 27 (Rev.WRC‑03) should be modified
accordingly.

Regarding the incorporation by reference of Recommendation ITU‑R
M.1642-1 into the Radio Regulations, both this latter situation of
incorporation by reference via a WRC Resolution and the need to update
the reference in the Radio Regulations apply. It is noted that
consequential changes to the Radio Regulations in relation to this
proposal may be addressed under Agenda item 3.

VOLUME 4

ITU‑R Recommendations incorporated by reference

**MOD** IAP/14A2/383

RECOMMENDATION ITU‑R M.541-9\*

Operational procedures for the use of digital selective-calling\
equipment in the maritime mobile service

(1978-1982-1986-1990-1992-1994-1995-1996-1997-2004)

**Reasons:** This Recommendation was updated to Rev.9 on 5/2004. The
updated revision was examined as requested by Resolution 28
(Rev.WRC‑03). It is appropriate to update the corresponding reference in
the Radio Regulations, in accordance with the principles contained in
the Annex to Resolution 27 (Rev.WRC‑03).

**MOD** IAP/14A2/384

RECOMMENDATION ITU‑R P.838-3

Specific attenuation model for rain for use in prediction methods

(Question ITU‑R 201/3)

(1992-1999-2003-2005)

**Reasons:** This Recommendation was updated to Rev. 3 on 5/2004. The
updated revision was examined as requested by Resolution 28
(Rev.WRC‑03). It is appropriate to update the corresponding reference in
the Radio Regulations, in accordance with the principles contained in
the Annex to Resolution 27 (Rev.WRC‑03).

**MOD** IAP/14A2/385

RECOMMENDATION ITU‑R M.1174-2\*

Technical characteristics of equipment used for on-board\
vessel communications in the bands between 450 and 470 MHz

(1995-1998-2004)

**Reasons:** This Recommendation was updated to Rev.2 on 5/2004. The
updated revision was examined as requested by Resolution 28
(Rev.WRC‑03). It is appropriate to update the corresponding reference in
the Radio Regulations, in accordance with the principles contained in
the Annex to Resolution 27 (Rev.WRC‑03).

**ADD** IAP/14A2/386

RECOMMENDATION ITU‑R M.1642-1

Methodology for assessing the maximum aggregate equivalent power
flux-density at an aeronautical radionavigation service station\
from all radionavigation-satellite service systems\
operating in the 1 164‑1 215 MHz band

(2003-2005)

**Reasons:** Footnote 5.328A (WRC‑03) states that RNSS systems operating
in the band 1 164-1 215 MHz shall operate in accordance with the
provisions of Resolution 609 (WRC‑03). *Resolves* 10 of this
Resolution states that Recommendation ITU‑R M.1642 shall be used to
perform the requisite calculations related to this resolution.
Therefore, the revised referenced Recommendation fulfils the criteria to
be incorporated into the Radio Regulations.

The previous Agenda item 2 proposals may require consequential changes
to the Radio Regulations, in accordance with Agenda item 3.

ARTICLE 47

Operator's certificates

Section IV -- Qualifying service**^1^**     (WRC‑03)

**MOD** IAP/14A2/387

**47.26** § 8 1) The holder of a radiocommunication general operator's
certificate or a first- or second-class radiotelegraph operator's
certificate shall be authorized to embark as chief operator of a ship
station of the fourth category (which is described in the most recent
version of Recommendation ITU‑R M.1169).     (WRC‑07)

**Reasons:** To clarify that this ITU‑R Recommendation is not
incorporated by reference and its use is considered non-mandatory by
modifying the linking language to conform to Resolution 27 (Rev.WRC‑03)
(Annex 2, No. 5).

**MOD** IAP/14A2/388

**47.27** 2) However, before becoming chief or sole operator of a ship
station of the fourth category (in accordance with the most recent
version of Recommendation ITU‑R M.1169) which is required by
international agreements to carry a radiotelegraph operator, the holder
of a radiocommunication general operator's certificate or a first- or
second-class radiotelegraph operator's certificate shall have had
adequate experience as operator on board ship at sea.     (WRC‑07)

**Reasons:** To clarify that this ITU‑R Recommendation is not
incorporated by reference and its use is considered non-mandatory by
modifying the linking language to conform to Resolution 27 (Rev.WRC‑03)
(Annex 2, No. 5).

**MOD** IAP/14A2/389

**47.28** 3) Before becoming chief operator of a ship station of the
second or third category (in accordance with the most recent version of
Recommendation ITU‑R M.1169), the holder of a radiocom­munication general
operator's certificate or a first- or second-class radiotelegraph
operator's certificate shall have had, as operator on board ship or in a
coast station, at least six months' experience of which at least three
months shall have been on board ship.     (WRC‑07)

**Reasons:** To clarify that this ITU‑R Recommendation is not
incorporated by reference and its use is considered non-mandatory by
modifying the linking language to conform to Resolution 27 (Rev.WRC‑03)
(Annex 2, No. 5)

**MOD** IAP/14A2/390

**47.29** 4) Before becoming chief operator of a ship station of the
first category (in accordance with the most recent version of
Recommendation ITU‑R M.1169), the holder of a radiocommunication general
operator's certificate or a first-class radiotelegraph operator's
certificate shall have had, as operator on board ship or in a coast
station, at least one year's experience of which at least six months
shall have been on board ship.     (WRC‑07)

**Reasons:** To clarify that this ITU‑R Recommendation is not
incorporated by reference and its use is considered non-mandatory by
modifying the linking language to conform to Resolution 27 (Rev.WRC‑03)
(Annex 2, No. 5).

Proposals for Agenda item 2: ITU‑R Recommendations incorporated by
reference in the Radio Regulations which have been revised and approved
since WRC‑03

Section 7/2/3 of the CPM Report identifies ITU‑R Recommendations which
have been revised and approved during the elapsed study period since
WRC‑03. The following provisions require the corresponding references be
updated to reflect the revised and approved version of the concerned
ITU‑R Recommendation.

ARTICLE 5

Frequency allocations

Section IV -- Table of Frequency Allocations\
(See No. 2.1)

**(MOD)** IAP/14A2/391

**5.279A** The use of this band by sensors in the Earth
exploration-satellite service (active) shall be in accordance with
Recommendation ITU-R RS.1260-1. Additionally, the Earth
exploration-satellite service (active) in the band 432-438 MHz shall not
cause harmful interference to the aeronautical radionavigation service
in China. The provisions of this footnote in no way diminish the
obligation of the Earth exploration-satellite service (active) to
operate as a secondary service in accordance with Nos. **5.29**
and **5.30**.     (WRC-07)

**Reasons:** Recommendation ITU‑R SA.1260-1 was renamed to the RS
series.

**MOD** IAP/14A2/392

**5.287** In the maritime mobile service, the frequencies 457.525 MHz,
457.550 MHz, 457.575 MHz, 467.525 MHz, 467.550 MHz and 467.575 MHz may
be used by on-board communication stations. Where needed, equipment
designed for 12.5 kHz channel spacing using also the additional
frequencies 457.5375 MHz, 457.5625 MHz, 467.5375 MHz and 467.5625 MHz
may be introduced for on-board communications. The use of these
frequencies in territorial waters may be subject to the national
regulations of the administration concerned. The characteristics of the
equipment used shall conform to those specified in
Recommendation ITU‑R M.1174‑2.     (WRC-07)

**Reasons:** To update the reference to Recommendation ITU‑R M.1174 to
the latest version approved during the elapsed study period since WRC‑03
and delete the reference to Resolution 341 (WRC‑97), which was abrogated
by WRC‑03.

**MOD** IAP/14A2/393

**5.288** In the territorial waters of the United States and the
Philippines, the preferred frequencies for use by on‑board communication
stations shall be 457.525 MHz, 457.550 MHz, 457.575 MHz and 457.600 MHz
paired, respectively, with 467.750 MHz, 467.775 MHz, 467.800 MHz and
467.825 MHz. The characteristics of the equipment used shall conform to
those specified in Recommendation ITU‑R M.1174-2.     (WRC-07)

**Reasons:** To update the reference to Recommendation ITU‑R M.1174 to
the latest version approved during the elapsed study period since
WRC‑03.

**MOD** IAP/14A2/394

**5.447F** In the band 5 250-5 350 MHz, stations in the mobile service
shall not claim protection from the radiolocation service, the Earth
exploration-satellite service (active) and the space research service
(active). These services shall not impose on the mobile service more
stringent protection criteria, based on system characteristics and
interference criteria, than those stated in Recommendations ITU‑R M.1638
and ITU‑R RS.1632.     (WRC-07)

**Reasons:** Recommendation ITU‑R SA.1632 was renamed to the RS series.

ARTICLE 22

Space services**^1^**

Section II -- Control of interference to geostationary-satellite systems

**MOD** IAP/14A2/395

TABLE **22-1D**     (WRC-07)

**Limits to the epfd radiated by non-geostationary-satellite systems in
the fixed-satellite\
service in certain frequency bands into 30 cm, 45 cm, 60 cm, 90 cm, 120
cm,\
180 cm, 240 cm and 300 cm broadcasting-satellite service antennas**6, 9,
10, 11

**MOD** IAP/14A2/395A

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

^12^ **22.5C.11** For this Table, reference patterns of Annex 1 to
Recommendation ITU‑R BO.1443‑2 shall be used only for the calculation of
interference from non‑geostationary-satellite systems in the
fixed-satellite service into geostationary-satellite systems in the
broadcasting-satellite service.     (WRC-07)

TABLE **22-1D** (*end*)     (WRC-07)

**Reasons:** To update the references to Recommendation ITU‑R BO.1443 to
the latest version approved during the elapsed study period since
WRC‑03.

ARTICLE 51

Conditions to be observed in the maritime services

Section I -- Maritime mobile service

**MOD** IAP/14A2/396

**51.35** *b)* send and receive class F1B or J2B emissions on an
international calling channel (identified in Recommendation
ITU‑R M.541‑9) in each of the HF maritime mobile bands necessary for
their service;     (WRC‑07)

**Reasons:** To update the reference to Recommendation ITU‑R M.541 to
the latest version approved during the elapsed study period since
WRC‑03.

ARTICLE 52

Special rules relating to the use of frequencies

Section IV -- Use of frequencies for digital selective-calling

D2 -- Call and acknowledgement

**MOD** IAP/14A2/397

**52.148** *b)* subject to the provisions of No. **52.149**, one of the
international digital selective-calling frequencies indicated in
Recommendation ITU-R M.541-9.     (WRC‑07)

**Reasons:** To update the reference to Recommendation ITU‑R M.541 to
the latest version approved during the elapsed study period since
WRC‑03.

**MOD** IAP/14A2/398

**52.149** 2) The international digital selective-calling frequencies
indicated in Recommendation ITU-R M.541-9 may be used by any ship
station. In order to reduce inter­ference on these frequencies, they
shall only be used when calling cannot be made on nationally assigned
frequencies.     (WRC‑07)

**Reasons:** To update the reference to Recommendation ITU‑R M.541 to
the latest version approved during the elapsed study period since
WRC‑03.

**MOD** IAP/14A2/399

**52.152** *b)* subject to the provisions of No. **52.153**, one of the
international digital selective-calling frequencies indicated in
Recommendation ITU-R M.541-9.     (WRC‑07)

**Reasons:** To update the reference to Recommendation ITU‑R M.541 to
the latest version approved during the elapsed study period since
WRC‑03.

**MOD** IAP/14A2/400

**52.153** 2) The international digital selective-calling frequencies
indicated in Recommendation ITU-R M.541-9 may be assigned to any coast
station. In order to reduce interference on these frequencies, they may
be used as a general rule by coast stations to call ships of another
nationality, or in cases where it is not known on which digital
selective-calling frequencies within the bands concerned the ship
station is maintaining watch.     (WRC‑07)

**Reasons:** To update the reference to Recommendation ITU‑R M.541 to
the latest version approved during the elapsed study period since
WRC‑03.

E2 -- Call and acknowledgement

**MOD** IAP/14A2/401

**52.159** § 71 1) The frequency 156.525 MHz is an international
frequency in the maritime mobile service used for distress, urgency,
safety and calling by digital selective-calling techniques (see
Nos. **33.8** and **33.31**, Appendix **15** and Recommendation ITU-R
M.541-9).     (WRC‑07)

**Reasons:** To update the reference to Recommendation ITU‑R M.541 to
the latest version approved during the elapsed study period since
WRC‑03.

ARTICLE 54

Selective calling

**MOD** IAP/14A2/402

**54.2** 2) Selective calling may be carried out using a sequential
single-frequency code system which shall be in accordance with
Recommendation ITU-R M.257‑3 or a digital selective-calling system which
shall be in accordance with Recommendations ITU‑R M.493-11, ITU‑R
M.541-9, ITU‑R M.821-1 and ITU‑R M.825-3 in the shore-to-ship,
ship-to-shore and ship-to-ship directions.     (WRC‑07)

**Reasons:** To update the references to ITU‑R Recommendations in this
provision to the latest version approved during the elapsed study period
since WRC‑03 and use clear linking language appropriate for mandatory
references.

APPENDIX 4 (Rev.WRC‑03)

**Consolidated list and tables of characteristics for use in the\
application of the procedures of Chapter III**

ANNEX 2

Characteristics of satellite networks, earth stations\
or radio astronomy stations^2^     (WRC-03)

**MOD** IAP/14A2/403

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 29%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 3%" />
</colgroup>
<thead>
<tr class="header">
<th><strong>Items in Appendix</strong></th>
<th><em><strong>C <sup>_</sup> CHARACTERISTICS TO BE PROVIDED FOR EACH
GROUP OF FREQUENCY ASSIGNMENTS FOR A SATELLITE ANTENNA BEAM OR AN EARTH
STATION OR RADIO ASTRONOMY ANTENNA</strong></em></th>
<th><strong>Advance publication of a geostationary-satellite
network</strong></th>
<th><strong>Advance publication of a non-geostationary-satellite network
subject to coordination under Section II of Article 9</strong></th>
<th><strong>Advance publication of a non-geostationary-satellite network
not subject to coordination under Section II of Article 9</strong></th>
<th><strong>Notification or coordination of a geostationary-satellite
network (including space operation functions under Article 2A of
Appendices 30 or 30A)</strong></th>
<th><strong>Notification or coordination of a
non-geostationary-satellite network</strong></th>
<th><strong>Notification or coordination of an earth station (including
notification under Appendices 30A or 30B)</strong></th>
<th><strong>Notice for a satellite network in the broadcasting-satellite
service under Appendix 30 (Articles 4 and 5)</strong></th>
<th><strong>Notice for a satellite network (feeder-link) under
Appendix 30A (Articles 4 and 5)</strong></th>
<th><strong>Notice for a satellite network in the fixed-satellite
service under Appendix 30B (Articles 6 and 8)</strong></th>
<th><strong>Items in Appendix</strong></th>
<th><strong>Radio astronomy</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>...</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>C.10.d.6</td>
<td><blockquote>
<p>if the associated station is a receiving earth station, the lowest
total receiving system noise temperature, in kelvins, referred to the
output of the receiving antenna of the earth station under clear-sky
conditions</p>
</blockquote></td>
<td></td>
<td></td>
<td><strong>+</strong></td>
<td><strong>+</strong></td>
<td><strong>+</strong></td>
<td></td>
<td></td>
<td></td>
<td><strong>+</strong></td>
<td>C.10.d.6</td>
<td><strong> </strong></td>
</tr>
<tr class="odd">
<td rowspan="2">C.10.d.7</td>
<td><blockquote>
<p>the antenna diameter, in metres</p>
</blockquote></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"><strong>+</strong></td>
<td rowspan="2"><strong>+</strong></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"><strong>X</strong></td>
<td rowspan="2"></td>
<td rowspan="2">C.10.d.7</td>
<td rowspan="2"><strong> </strong></td>
</tr>
<tr class="even">
<td><blockquote>
<p>In cases other than Appendix <strong>30A</strong>, to be provided
only for fixed-satellite service networks operating in the frequency
band 13.75-14 GHz</p>
</blockquote></td>
</tr>
<tr class="odd">
<td>C.10.d.8</td>
<td><blockquote>
<p>the equivalent antenna diameter (i.e. the diameter, in metres, of a
parabolic antenna with the same off-axis performance as the receiving
associated earth station antenna)</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>X</strong></td>
<td></td>
<td></td>
<td>C.10.d.8</td>
<td><strong> </strong></td>
</tr>
<tr class="even">
<td><strong>C.11</strong></td>
<td><strong>SERVICE AREA(S)</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>C.11</strong></td>
<td><strong> </strong></td>
</tr>
<tr class="odd">
<td rowspan="3">C.11.a</td>
<td><blockquote>
<p>the service area or areas of the satellite beam on the Earth, when
the associated transmitting or receiving stations are earth stations</p>
</blockquote></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3"></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3"><strong>X</strong></td>
<td rowspan="3">C.11.a</td>
<td rowspan="3"><strong> </strong></td>
</tr>
<tr class="even">
<td><blockquote>
<p>For a space station submitted in accordance with Appendix
<strong>30</strong>, <strong>30A</strong> or <strong>30B</strong>, the
service area identified by a set of a maximum of twenty test points and
by a service area contour on the surface of the Earth or defined by a
minimum elevation angle</p>
</blockquote></td>
</tr>
<tr class="odd">
<td><blockquote>
<p>For advance publication of satellite networks subject to
coordination, only a list of countries and geographical areas, using the
symbols from the Preface, or a narrative description of the service area
shall be supplied</p>
</blockquote></td>
</tr>
<tr class="even">
<td rowspan="2">C.11.b</td>
<td><blockquote>
<p>the appropriate information required to calculate the affected region
(as defined in Recommendation ITU‑R M.1187‑1)</p>
</blockquote></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"><strong>+</strong></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2"></td>
<td rowspan="2">C.11.b</td>
<td rowspan="2"><strong> </strong></td>
</tr>
<tr class="odd">
<td><blockquote>
<p>Required only for a non-geostationary space station in the
mobile-satellite service submitted in accordance with
No. <strong>9.11A</strong></p>
</blockquote></td>
</tr>
<tr class="even">
<td>...</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

**Reasons:** To update the reference to Recommendation ITU‑R M.1187 to
the latest version approved during the elapsed study period since
WRC‑03.

#### Agenda item 4

4 in accordance with Resolution **95 (Rev.WRC‑03)**, to review the
Resolutions and Recommendations of previous conferences with a view to
their possible revision, replacement or abrogation

Background information

Resolution 33 (Rev.WRC‑03) contains procedures to be applied for the
coordination and notification of BSS satellite networks for which the
API has been received by the Radiocommunications Bureau prior to 1
January 1999.

The BR Director's review of Resolutions and Recommendations of WARC/WRC,
submitted to the last meeting of the CPM, proposed that WRC‑07 suppress
Resolution 33 (Rev.WRC‑03) under the justification "Processing of
filings under this Resolution completed".

However, some countries still have BSS filings in the process of
coordination and notification in accordance with the terms of
Resolution 33 (Rev.WRC‑03). These filings have been submitted under
11.43A and are covered by an API submitted prior to 1 January 1999.
Moreover, their validity extends well beyond 2007.

**NOC** IAP/14A2/404

RESOLUTION 33 (Rev.WRC‑03)

Bringing into use of space stations in the broadcasting-satellite
service,\
prior to the entry into force of agreements and associated plans for\
the broadcasting-satellite service

**Reasons:** Suppression of Resolution 33 (Rev.WRC‑03) by WRC‑07 is not
appropriate because it will modify in mid-course the coordination and
notification procedures applicable to certain filings still in process
within the ITU.

#### Agenda item 7.1

7.1 to consider and approve the Report of the Director of the
Radiocommunication Bureau:

-- on the activities of the Radiocommunication Sector since WRC‑03;

-- on any difficulties or inconsistencies encountered in the application
of the Radio Regulations; and

-- on action in response to Resolution **80 (Rev.WRC‑2000)**

Proposal for Agenda item 7.1: Modifications to Article 2A of each of
AP30 and AP30A to reflect guardband usage

Background information

The WRC‑07 Conference Preparatory Meeting held in Geneva 19 February --
2 March 2007 considered the issue of inconsistencies in Article 2A of
each of AP30 and AP30A of the Radio Regulations. Article 2A addresses
the use of guardbands to provide space operation functions in accordance
with RR No. 1.23 in support of the operations of geostationary-satellite
networks in the broadcasting-satellite service (BSS) and the BSS feeder
link.

The regulatory deadline for bringing into use an assignment for space
operation functions in the guardband supporting the BSS network is
defined in Article 2A of each of AP30 and AP30A, wherein direction is
given to notify such assignments in accordance with RR Article 11.
However, the regulatory deadline for notification of the assignment is
not clear because RR No. 11.44.1 refers to a maximum period of seven
years from the date of receipt of the relevant advance publication
information (API), but an API is not submitted for such BSS or BSS
feeder-link assignments.

In addition, there currently exits no regulatory procedure to
accommodate a new entry or modification to an assignment for the space
operations functions in the guardband when the assignments of the
associated geostationary-satellite network in the BSS have been already
brought into use. This situation can occur when there is a replacement
BSS satellite that has the same characteristics as the notified network,
with the exception of the assignments for space operation functions.
Accordingly, a new regulatory procedure with associated deadline is
required to accommodate this situation.

Apart from the inconsistencies noted above, the CPM considered that the
overall flow of the provisions in Article 2A is confusing. Thus Section
6/7.1/1.4 of the CPM Report states that a complete and comprehensive
review of the entire text in Article 2A of each of AP30 and AP30A would
be appropriate, to ensure that the situation is fully clarified.
Specifically, it is stated that modification could occur with a view to
reorganizing the sequencing of the provisions to improve the logical
flow; clarifying the deadline for notification and bringing into use of
assignments for space operations functions in the guardband supporting
the BSS network; accommodating a new entry or modification to an
assignment for the space operations functions in the guardband when the
assignments of the supporting geostationary-satellite network in the BSS
have been already brought into use; and preserving the original intent
of the coordination and notification procedures that are the subject of
Article 2A.

In view of the above, it is proposed that Article 2A of each of AP30 and
AP30A be modified as reflected below, which shows modifications in the
form of track changes to excerpts of the existing Article 2A text in
each of AP30 and AP30A of the Radio Regulations.

APPENDIX 30 (Rev.WRC-03)^\*^

Provisions for all services and associated Plans and List**^1^** for\
the broadcasting-satellite service in the frequency bands\
11.7-12.2 GHz (in Region 3), 11.7-12.5 GHz (in Region 1)\
             and 12.2-12.7 GHz (in Region 2)     (WRC-03)

              (See Articles **9** and **11**)     (WRC‑03)

**MOD** IAP/14A2/405

            ARTICLE 2A     (WRC-03)

Use of the guardbands

2A.1 The use of the guardbands defined in § 3.9 of Annex 5 to provide
space operation functions in accordance with No. **1.23** is in support
of the operation of geostationary-satellite networks in the
broadcasting-satellite service (BSS). Advance publication information is
not required. Coordination information shall be in accordance with
Appendix **4**.

2A.1.1 Coordination between assignments intended to provide the space
operation functions and assignments of the BSS subject to a Plan shall
be effected using the provisions of Article 7.

2A.1.2 Coordination among assignments intended to provide the space
operation functions and services not subject to a Plan shall be effected
using the provisions of Nos. **9.7**, **9.17**, **9.18** and the
associated provisions of Section II of Article **9**, or § 4.1.1 *d)* or
4.2.3 *d)* of Article 4, as appropriate.

2A.1.3 Coordination of modifications to the Region 2 Plan or assignments
to be included in the Regions 1 and 3 List with assignments intended to
provide these functions shall be effected using § 4.1.1 *e)* or
4.2.3 *e)*, as appropriate, of Article 4.

2A.2 Any assignment intended to provide these functions in support of a
geostationary-satellite network in the BSS shall be notified under
Article **11** and brought into use in accordance with the time-limits
set forth in the provisions below:

2A.2.1 for the case where the associated BSS assignments are in one of
the initial Plans (Region 2 Plans incorporated in the Radio Regulations
at WARC Orb‑85 and the Regions 1 and 3 Plan adopted at WRC‑2000), within
the regulatory time-limit referred to in § 4.1.3 or § 4.2.6 of Article 4
from the date of receipt by the Bureau of the complete Appendix **4**
data for those assignments intended to provide the space operation
functions;

2A.2.2 for the case where the associated BSS assignments have been
submitted under § 4.1.3 or § 4.2.6 of Article 4 for entry to the
Regions 1 and 3 List or a modification to the Region 2 Plan, within the
regulatory time-limit referred to in § 4.1.3 or § 4.2.6 of Article 4 for
those associated BSS assignments;

2A.2.3 for the case where the associated BSS assignments have already
been brought into use in accordance with the Radio Regulations, within
the regulatory time-limit referred to in § 4.1.3 and § 4.2.6 of
Article 4 from the date of receipt by the Bureau of the complete
Appendix **4** data for those assignments intended to provide the space
operation functions.

2A.3 Section II of Article **23** does not apply to assignments in the
guardbands intended to provide the above-mentioned functions.

**Reasons:** To improve the flow of Article 2A of Appendix 30, clarify
the deadline for notification and bringing into use of assignments for
space operations functions in the guardband supporting the BSS network,
and accommodate a new entry or modification to an assignment for the
space operations functions in the guardband.

APPENDIX 30A  (Rev.WRC‑03)\*

**Provisions and associated Plans and List1 for feeder links for the\
broadcasting-satellite service (11.7-12.5 GHz in Region 1, 12.2-12.7
GHz\
in Region 2 and 11.7-12.2 GHz in Region 3) in the frequency bands\
14.5-14.8 GHz2 and 17.3-18.1 GHz in Regions 1 and 3,\
and 17.3-17.8 GHz in Region 2**     (WRC‑03)

(See Articles **9** and **11**)     (WRC‑03)

**MOD** IAP/14A2/406

            ARTICLE 2A     (WRC-03)

Use of the guardbands

2A.1 The use of the guardbands defined in § 3.1 and 4.1 of Annex 3 to
provide space operation functions in accordance with No. **1.23** is in
support of the operation of geostationary-satellite networks for the
broadcasting-satellite service (BSS) feeder link. Advance publication
information is not required. Coordination information shall be in
accordance with Appendix **4**.

2A.1.1 Coordination between assignments intended to provide the space
operation functions and assignments of the BSS feeder link subject to a
Plan shall be effected using the provisions of Article 7.

2A.1.2 Coordination among assignments intended to provide the space
operation functions and services not subject to a Plan shall be effected
using the provisions of Nos. **9.7, 9.17, 9.17A, 9.18,** and the
associated provisions of Section II of Article **9**, as appropriate.

2A.1.3 Coordination of modifications to the Region 2 feeder‑link Plan or
assignments to be included in the Regions 1 and 3 feeder-link List, with
assignments intended to provide these functions shall be effected using
§ 4.1.1 *d)* of Article 4.

2A.2 Any assignment intended to provide these functions in support of a
geostationary-satellite network for the BSS feeder link shall be
notified under Article **11** and brought into use in accordance with
the time-limits set forth in the provisions below:

2A.2.1 for the case where the associated feeder-link assignments are in
one of the initial Plans (Region 2 Plans incorporated in the Radio
Regulations at WARC Orb-85 and Regions 1 and 3 Plan adopted at
WRC‑2000), within the regulatory time-limit referred to in § 4.1.3 or
4.2.6 of Article 4 from the date of receipt by the Bureau of the
complete Appendix **4** data for those assignments intended to provide
these space operation functions;

2A.2.2 for the case where the associated feeder-link assignments have
been submitted under § 4.1.3 or § 4.2.6 of Article 4 for entry to the
Regions 1 and 3 List or a modification to the Region 2 Plan, within the
regulatory time-limit referred to in § 4.1.3 or § 4.2.6 of Article 4 for
the associated feeder-link assignments;

2A.2.3 for the case where the associated feeder-link assignments have
already been brought into use in accordance with the Radio Regulations,
within the regulatory time-limit referred to in § 4.1.3 and § 4.2.6 of
Article 4 from the date of receipt by the Bureau of the complete
Appendix **4** data for those assignments intended to provide these
space operation functions.

**Reasons:** To improve the flow of Article 2A of Appendix 30A, clarify
the deadline for notification and bringing into use of assignments for
space operations functions in the guardband supporting the BSS network,
and accommodate a new entry or modification to an assignment for the
space operations functions in the guardband.

#### Agenda item 7.2

7.2 to recommend to the Council items for inclusion in the agenda for
the next WRC, and to give its views on the preliminary agenda for the
subsequent conference and on possible agenda items for future
conferences, taking into account Resolution **803** **(WRC‑03)**

Proposal for Agenda item 7.2: additional agenda item providing a primary
allocation of up to 500 MHz for the space research service in the
22.55-23.15 GHz

Background information

At WRC‑03, a primary space research service (space-to-Earth) allocation
in the band 25.5-27.0 GHz was added to the Table of Allocations to
support a wide range of space research missions.

To support the SRS missions in near Earth orbit, including missions in
transit to the moon and at or near the moon, downlink (space-to-Earth)
transmissions will operate in the 25.5-27.0 GHz SRS allocation. This
1.5 GHz wide downlink band will be used for both scientific data
retrieval and voice/video communication with the Earth.

However, there is a need for a companion uplink (Earth-to-space) band to
provide the mission data, command and control links for these missions.
Due to the potential for many concurrent exploration related systems and
the large bandwidth requirements of these systems, especially those
supporting manned missions, it is envisioned that a total uplink
bandwidth of up to 500 MHz will be needed.

The 22.55-23.55 GHz band is used for Tracking and Data Relay Satellite
System (TDRSS) to communicate with user satellites (forward links) via
an existing primary inter-satellite service allocation. These forward
links are paired with inter-satellite return links in the 25.25-27.5 GHz
band. In addition, the 22.55-23.55 GHz band is both far enough from the
25.5-27.0 GHz band to provide adequate frequency separation and wide
enough to accommodate a 500 MHz sub-band, while allowing adequate
bandwidth to protect existing systems. Thus the 22.55-23.55 GHz band is
the logical companion band to provide the necessary uplink bandwidth and
by using the same band as the TDRSS for communication in the
Earth-to-space direction, it provides a degree of redundancy and
coverage that may prove vital for future missions.

The inter-satellite service links of a non-GSO MSS satellite system
operate in the ISS allocation in the band 23.183-23.377 GHz. They have
been in operation for several years and are increasingly being used as a
source of last communications in situations of emergencies and natural
disasters.

Proposal

CITEL Administrations propose to submit a new agenda item on use of the
band 22.55-23.15 GHz by the space research service to be considered at
WRC‑11, as follows:

**ADD** IAP/14A2/407

PROPOSAL FOR AN ADDITIONAL AGENDA ITEM PROVIDING A PRIMARY ALLOCATION OF
UP TO 500 MHz FOR THE SPACE RESEARCH SERVICE\
IN THE 22.55-23.15 GHz BAND

***Subject:*** Proposed future WRC agenda item for WRC‑11 providing a
primary allocation of up to 500 MHz for the space research service in
the 22.55-23.15 GHz band

***Origin:*** CITEL Administrations

***Proposal:*** to consider the addition of up to a 500 MHz primary
space research service (Earth-to-space) allocation in the
22.55-23.15 GHz band, taking into account the results of ITU‑R studies
and recognizing the need to protect existing systems in the band, taking
into account Resolution \[IAP/14A2/410\] (WRC‑07)

***Background/reason:*** To support the SRS missions in near Earth
orbit, including missions in transit to the moon and at or near the
moon, downlink (space-to-Earth) transmissions will operate in the
25.5-27.0 GHz SRS allocation. This 1.5 GHz wide downlink band will be
used for both scientific data retrieval and voice/video communication
with the Earth. However, there is a need for a companion uplink
(Earth-to-space) band to provide the mission data, command and control
links for these missions. Due to the potential for many concurrent
exploration related systems and the large bandwidth requirements of
these systems, especially those supporting manned missions, it is
envisioned that a total uplink bandwidth of up to 500 MHz will be
needed. Allocating sufficient primary space research service frequency
spectrum in the 22.55-23.15 GHz band will provide the space exploration
initiatives adequate uplink (Earth-to-space) bandwidth capacity in a
band that is paired with the inter-satellite service and thus is a
reasonable companion to the primary space research service 25.5-27.0 GHz
space-to-Earth band.

***Radiocommunication services concerned:*** SRS, FSS, FS and MS

***Indication of possible difficulties:*** None foreseen

***Previous/ongoing studies on the issue:*** None to date

+-----------------------------+----------------------------------------+
| ***Studies to be carried    | > ***with the participation of:*** SG  |
| out by:*** SG 7             | > 4, SG 8 and SG 9                     |
+-----------------------------+----------------------------------------+

***ITU‑R Study Groups concerned:*** SG 7, SG 4, SG 8 and SG 9

***ITU resource implications, including financial implications (refer to
CV126):*** Minimal

***Common regional proposal:*** Yes/No ***Multicountry proposal:***
Yes/No

Number of countries:

***Remarks***

**MOD** IAP/14A2/408

RESOLUTION 803 (Rev.WRC‑07)

Agenda for the 2011 World\
Radiocommunication Conference

The World Radiocommunication Conference (Geneva, 2007),

**ADD** IAP/14A2/409

2.XB to consider the addition of up to a 500 MHz primary space research
service (Earth-to-space) allocation in the 22.55-23.15 GHz band, taking
into account the results of ITU‑R studies and recognizing the need to
protect existing systems in the band, taking into account Resolution
**\[IAP/14A2/410\] (WRC‑07)**;

**ADD** IAP/14A2/410

RESOLUTION \[IAP/14A2/410\] (WRC‑07)

Use of the band 22.55-23.15 GHz by the space research service

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that there is growing interest by space agencies around the world
in the comprehensive exploration of the moon;

*b)* that the lunar exploration missions, examining the terrain,
environment and potential landing sites, will be robotic for the
foreseeable future and manned in the long term;

*c)* that a primary space research service (space-to-Earth) allocation
in the band 25.5-27.0 GHz was added to the Table of Frequency
Allocations to support a wide range of space research missions;

*d)* that space research service (space-to-Earth) transmissions in the
25.5-27.0 GHz band will be used to support space research service
missions in near-Earth orbit, including missions in transit to the moon
and at or near the moon;

*e)* that the space research service (space-to-Earth) transmissions in
the 25.5-27.0 GHz band will be used for both scientific data retrieval
and voice/videocommunication with the Earth;

*f)* that there is a need for a companion uplink space research service
(Earth-to-space) band to provide the mission data, command and control
links for the lunar exploration missions;

*g)* that due to the potential for many concurrent exploration-related
systems and the large bandwidth requirements of these systems,
especially those supporting manned missions, it is envisioned that a
total uplink bandwidth of up to 500 MHz will be needed;

*h)* that the 22.55-23.15 GHz band is both far enough from the
25.5-27.0 GHz band to provide adequate frequency separation and wide
enough to accommodate a 500 MHz sub-band, while allowing adequate
bandwidth to protect existing systems;

*i)* that the 22.55-23.55 GHz band is used by data relay satellite
systems to communicate with user satellites (forward links) in the
existing primary inter-satellite service allocation;

*j)* that the 22.55-23.15 GHz band is the logical companion band to
provide the necessary uplink bandwidth and by using the same band as
data relay satellite systems in *considering i)* for communication in
the Earth-to-space direction, it provides a degree of redundancy and
coverage that may prove vital for future missions,

recognizing

*a)* that the band 22.55-23.55 GHz is allocated to the fixed,
inter-satellite and mobile services;

*b)* that the inter-satellite forward links in the 22.55-23.55 GHz band
are paired with inter-satellite return links in the 25.25-27.5 GHz band;

*c)* that non-GSO inter-satellite service links have been operating for
several years and are expected to continue to operate in the
23.183-23.377 GHz band and that these links are increasingly being used
in situations of emergencies and natural disasters;

*d)* that sharing between the space research service (Earth-to-space)
and the fixed, inter-satellite and mobile services may be feasible in
the band 22.55-23.15 GHz,

resolves

1 to invite ITU‑R to conduct sharing analyses between the space research
service systems operating in the Earth-to-space direction and the fixed,
inter-satellite and mobile services in the band 22.55-23.15 GHz, to
define appropriate sharing criteria with a view to allocating up to
500 MHz in the band 22.55-23.55 GHz for the space research service in
the Earth-to-space direction;

2 to recommend that WRC‑11 review the results of the studies under
*resolves* 1 and consider the inclusion of the sharing criteria within
the Radio Regulations and appropriate modifications to the Table of
Frequency Allocations, based on proposals from administrations,

invites administrations

to contribute to the sharing studies between the space research service
and the fixed, inter-satellite and mobile services in the
22.55-23.55 GHz band,

invites ITU‑R

to complete the necessary studies, as a matter of urgency, taking into
account the present use of the allocated band, with a view to
presenting, at the appropriate time, the technical information likely to
be required as a basis for the work of the Conference,

instructs the Secretary-General

to bring this Resolution to the attention of the international and
regional organizations concerned.

**Reasons (14A2/407, IAP/14A2/408, IAP/14A2/409, IAP/14A2/410):**
Allocating sufficient primary space research service frequency spectrum
in the 22.55-23.55 GHz band will provide the space exploration
initiatives adequate uplink (Earth-to-space) bandwidth capacity in a
band that is paired with the inter-satellite service and thus is a
reasonable companion to the primary space research service 25.5-27.0 GHz
space-to-Earth band.

Proposal for Agenda item 7.2: additional agenda item considering the
modification of the primary mobile service allocation in the 37-38 GHz
band to exclude aeronautical mobile stations

Background information

The 37-38 GHz band is allocated to the fixed, space research
(space-to-Earth) and the mobile services on a primary basis, and the
37.5-38 GHz portion of this band is also allocated to the
fixed-satellite service (space-to-Earth) on a primary basis. In
addition, No. 5.547 (MOD WRC‑2000) identifies the 37-40 GHz band as
being available for high-density applications in the fixed service
(HDFS).

Space research earth station receivers are being implemented in the
37-38 GHz band to support manned missions, for both near Earth and deep
space distances, and use of the wider bandwidth available in the
37-38 GHz band will be required to support the increasing data
requirements of planned manned missions.

Aeronautical mobile stations are capable of causing unacceptable levels
of interference whenever they are within line-of-sight of a receiver in
the space research and Earth-exploration satellite services. Preliminary
calculations within WP 7B have shown that aeronautical mobile
transmissions could cause unacceptable levels of interference for
significant periods of time. In particular, space research service earth
station receivers operating in the 37-38 GHz band have very low
thresholds for which the ITU‑R has already established both deep space
and non-deep space protection criteria Recommendations. Exceeding the
protection criteria of the space research service for an extended period
of time could jeopardize the success of a manned or scientific space
mission.

Presently, the Table of Frequency Allocations has already excluded
aeronautical mobiles in several frequency bands in which the mobile
service is co-allocated on a primary basis with the space research
service downlinks. These include 2.29-2.3 GHz (space research deep
space), 8.4-8.5 GHz (space research deep space and non-deep space),
22.21-22.5 GHz and 31.5-31.8 GHz (Earth exploration-satellite and space
research passive). Based on current information, to date there are no
aeronautical mobile systems operating in the 37-38 GHz band, nor are any
planned. Considering the planned developments of manned space research
service missions in the 37-38 GHz band, now might be the appropriate
time to consider the exclusion of aeronautical mobile stations from this
band as well.

Proposal

CITEL Administrations propose to submit a new agenda item on considering
the modification of the primary mobile service allocation in the
37-38 GHz band to exclude aeronautical mobile stations to be considered
at WRC‑11 as follows:

**ADD** IAP/14A2/411

PROPOSAL FOR ADDITIONAL AGENDA ITEM CONSIDERING THE MODIFICATION OF THE
PRIMARY MOBILE SERVICE ALLOCATION IN THE 37-38 GHz BAND TO EXCLUDE
AERONAUTICAL MOBILE STATIONS

***Subject:*** Proposed future WRC agenda item for WRC‑11 considering
the modification of the primary mobile service allocation in the
37-38 GHz band to exclude aeronautical mobile stations

***Origin:*** CITEL Administrations

***Proposal:*** to consider modifying the primary mobile service
allocation in the 37-38 GHz band to exclude aeronautical mobile
stations, or to take such other regulatory action as needed to protect
the other primary services in the band from interference from the
aeronautical mobile service, taking into account the results of ITU‑R
studies and Resolution \[IAP/14A2/414\] (WRC‑07)

***Background/reason:*** Planned manned space research missions require
access to the wider bandwidth available in this band. Aeronautical
mobile stations are capable of causing unacceptable interference when
they are within line-of-sight of a receiver operating in the space
research service and such interference levels may exist for extended
periods, so jeopardizing manned or scientific mission success. Excluding
aeronautical mobile systems in the 37-38 GHz band may be necessary to
protect the other primary services in the band from harmful
interference.

***Radiocommunication services concerned:*** SRS, FSS, FS and MS

***Indication of possible difficulties:*** None foreseen

***Previous/ongoing studies on the issue:*** Recommendation ITU‑R
SA.1016 highlights the difficulty of sharing between aeronautical mobile
stations and space research service stations in other bands. Specific to
the 37-38 GHz band, Working Party 7B has done some preliminary studies
that indicate similar sharing concerns.

+-----------------------------+----------------------------------------+
| ***Studies to be carried    | > ***with the participation of:*** SG  |
| out by:*** SG 7             | > 4, SG 8 and SG 9                     |
+-----------------------------+----------------------------------------+

***ITU‑R Study Groups concerned:*** SG 7, SG 4, SG 8 and SG 9

***ITU resource implications, including financial implications (refer to
CV126):*** Minimal

***Common regional proposal:*** Yes/No ***Multicountry proposal:***
Yes/No

Number of countries:

***Remarks***

**MOD** IAP/14A2/412

RESOLUTION 803 (Rev.WRC‑07)

Agenda for the 2011 World\
Radiocommunication Conference

The World Radiocommunication Conference (Geneva, 2007),

**ADD** IAP/14A2/413

2.XD to consider modifying the primary mobile service allocation in the
37-38 GHz band to exclude aeronautical mobile stations, or to take such
other regulatory action as needed to protect the other primary services
in the band from interference from the aeronautical mobile service,
taking into account the results of ITU‑R studies and
Resolution** \[IAP/14A2/414\] (WRC‑07)**;

**Reasons (IAP/14A2/411, IAP/14A2/412, IAP/14A2/413):** Planned manned
space research missions require access to the wider bandwidth available
in this band. Aeronautical mobile stations are capable of causing
unacceptable interference when they are within line-of-sight of a
receiver operating in the space research service and such interference
levels may exist for extended periods, so jeopardizing manned or
scientific mission success. Excluding aeronautical mobile systems in the
37-38 GHz band may be necessary to protect the other primary services in
the band from harmful interference.

**ADD** IAP/14A2/414

RESOLUTION \[IAP/14A2/414\] (WRC‑07)

Protection of primary services in the band 37-38 GHz

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that the band 37-38 GHz is allocated on a primary basis to the
fixed, mobile and space research (space-to-Earth) services, and the
37.5-38 GHz portion of this band is also allocated on a primary basis to
the fixed-satellite service (space-to-Earth);

*b)* that space research earth station receivers are being implemented
in the 37-38 GHz band to support both manned and unmanned missions, for
both near-Earth and deep-space distances, and use of the wider bandwidth
available in the 37-38 GHz band is required to support the increased
data requirements of planned manned and scientific missions;

*c)* that an aeronautical mobile station can cause unacceptable
interference to receivers in the space research service whenever it is
within line-of-sight of the receiver, as indicated in Recommendation
ITU‑R SA.1016;

*d)* that interference from the emissions of an aeronautical mobile
station to a space research service earth station receiver may
significantly exceed the permissible interference levels for extended
periods of time, thus jeopardizing the success of a space mission,

recognizing

*a)* that the Table of Frequency Allocations already excludes the
operation of aeronautical mobile stations in 2.29-2.3 GHz, 8.4-8.5 GHz,
22.21-22.5 GHz and 31.5-31.8 GHz where the mobile service is
co-allocated on a primary basis with the space research service
(space-to-Earth);

*b)* that RR No. **5.547** indicates that the 37-38 GHz band is
available for high-density applications in the fixed service,

noting

that aeronautical mobile service systems are currently not deployed nor
planned in the 37-38 GHz band,

resolves

1 to invite ITU‑R to conduct appropriate studies involving the
aeronautical mobile service, the space research service, and the other
affected services in the band 37-38 GHz to determine the compatibility
of the aeronautical mobile service with these other services;

2 to recommend that WRC‑11 review the results of the studies under
*resolves* 1 and consider the inclusion of any appropriate compatibility
criteria within the Radio Regulations or appropriate modifications to
the Table of Frequency Allocations, based on proposals from
administrations,

invites administrations

to contribute to the compatibility studies between the aeronautical
mobile service and the other services in the 37-38 GHz band,

invites ITU‑R

to complete the necessary studies, as a matter of urgency, taking into
account the present use of the allocated band, with a view to
presenting, at the appropriate time, the technical information likely to
be required as a basis for the work of the Conference,

instructs the Secretary-General

to bring this Resolution to the attention of the international and
regional organizations concerned.

**Reasons:** Future manned and unmanned space research missions will
require access to the wider bandwidth available in this band.
Aeronautical mobile stations are capable of causing unacceptable
interference when they are within line-of-sight of a receiver operating
in the space research service, and such interference levels may exist
for extended periods, thus jeopardizing the success of manned or
scientific missions. Excluding aeronautical mobile systems in the
37-38 GHz band, or the establishment of appropriate compatibility
criteria, may be necessary to protect systems operating under a primary
service allocation in the band from harmful interference. This
Resolution provides guidance on the ITU‑R studies required in support of
the proposed WRC‑11 agenda item.

Proposal for Agenda item 7.2: Modifications on Resolution 803 (WRC‑03)

Background information

Agenda item 7.2 of the Conference agenda deals with the agenda for the
next WRC, taking into account Resolution 803 (WRC‑03), and views on
possible agenda items for future conferences. CITEL Administrations
believe that Agenda item 1.12 of the WRC‑07 agenda should be included as
a standing item on the WRC‑11 agenda, as it will also need to be dealt
with at future conferences, subsequent to each Plenipotentiary
Conference. Further, CITEL Administrations believe that Agenda item 2.1
of the WRC‑11 agenda should become a standing item, as it should also be
visited at each WRC. Therefore, CITEL Administrations submit the
proposed modifications to Resolution 803 (WRC‑03), as outlined below.

In addition to these standing items, CITEL Administrations believe that
Agenda item 3.1 should be moved up for consideration at WRC‑11. WRC‑03
made the tentative decisions in No. 5.444A that the FSS in the frequency
band 5 091-5 150 MHz should be made secondary to the ARNS on 1 January
2018, and that there be no new assignments to FSS earth stations after 1
January 2012. However, WRC‑03 decided in Resolution 114 (Rev.WRC‑03)
that the allocation to the aeronautical radionavigation service and the
FSS in the frequency band 5 091-5 150 MHz should be reviewed at a future
competent conference prior to 2018.

After WRC‑07 the next WRC will likely occur in about 2011 and then
possibly in 2014 or 2015. The constraint to not be able to implement new
earth stations after January 2012 would constrain the provision of an
expanding service, if there was a moratorium on growth for over three
years, 2012 to at least 2015. Further, the use of airport network and
location equipment (ANLE) and possibly other AMS applications as well in
the 5 091-5 150 MHz band requires that the review stated in *resolves* 2
of Resolution 114 (Rev.WRC‑03) should be reviewed at a future competent
conference prior to 2018. On this basis, the CITEL Administrations
propose to move Agenda item 3.1 to the WRC‑11 agenda.

**MOD** IAP/14A2/415

RESOLUTION 803 (Rev.WRC‑07)

Agenda for the 2011 World\
Radiocommunication Conference

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that, in accordance with No. 118 of the ITU Convention, the general
scope of the agenda for WRC‑11 should be established four to six years
in advance;

*b)* Article 13 of the Constitution relating to the competence and
scheduling of world radiocommunication conferences and Article 7 of the
Convention relating to their agendas;

*c)* the relevant Resolutions and Recommendations of previous world
administrative radio conferences (WARCs) and world radiocommunication
conferences (WRCs),

resolves

1 to recommend to the Council that a world radiocommunication conference
be held in 2011 for a period of \[4\] weeks, with the following agenda:

2 on the basis of proposals from administrations and the Report of the
Conference Preparatory Meeting, and taking account of the results of
WRC‑07, to consider and take appropriate action in respect of the
following items:

2.1 to consider frequency allocations between 275 GHz and 3 000 GHz
taking into account the result of ITU-R studies in accordance with
Resolution **950** **(WRC‑03)**;

2.2 to consider results of ITU‑R studies in accordance with
Resolution **222 (WRC‑2000)** to ensure spectrum availability and
protection for the aeronautical mobile-satellite (R) service, and to
take appropriate action on this subject, while retaining the generic
allocation for the mobile-satellite service;

2.3 to consider allocations to the mobile service in the band 806-862
MHz in Region 1, following the transition of analogue to digital TV;

2.4 to consider the results of studies related to Resolution **136
(Rev.WRC‑03**) dealing with sharing between non‑GSO and GSO systems;

2.5 to consider the need to modify the provisional protection ratio
values in the Annex to Resolution **543** **(WRC‑03)**, taking into
account the experience of the coordination of seasonal scheduling of the
HF bands allocated to the broadcasting service and relevant studies
conducted by ITU‑R since WRC‑03;

2.6 to consider the progress of ITU-R studies concerning the technical
and regulatory issues relative to the fixed service in the 81‑86 and
92-100 GHz frequency bands, taking into account Resolutions **731
(WRC‑2000)** and **732 (WRC‑2000)**;

2.7 to consider the progress of the ITU‑R studies concerning the
development and regulatory requirements of terrestrial wireless
interactive multimedia applications, in accordance with
Recommendation **722** **(WRC‑03)** and to take any appropriate action
on this subject;

2.8 to review the use of the band 5 091-5 150 MHz by the fixed-satellite
service (Earth-to-space) (limited to feeder links of the non-GSO
mobile-satellite service) in accordance with Resolution **114
(Rev.WRC‑03)**;

3 to consider the results of the studies related to the following, with
a view to considering them for inclusion in the agendas of future
conferences:

4 to examine the revised ITU-R Recommendations incorporated by reference
in the Radio Regulations communicated by the Radiocommunication
Assembly, in accordance with Resolution **28 (Rev.WRC‑03)**, and to
decide whether or not to update the corresponding references in the
Radio Regulations, in accordance with the principles contained in Annex
1 to Resolution **27** **(Rev.WRC‑03)**;

5 to consider such consequential changes and amendments to the Radio
Regulations as may be necessitated by the decisions of the Conference;

6 in accordance with Resolution **95 (Rev.WRC‑03)**, to review the
Resolutions and Recommendations of previous conferences with a view to
their possible revision, replacement or abrogation;

7 to review, and take appropriate action on, the Report from the
Radiocommunication Assembly submitted in accordance with Nos. 135
and 136 of the Convention;

8 to identify those items requiring urgent action by the
Radiocommunication Study Groups;

9 to consider and take appropriate action on requests from
administrations to delete their country footnotes or to have their
country name deleted from footnotes, if no longer required, taking into
account Resolution** 26 (Rev.WRC‑97)**;

10 to consider possible changes in response to Resolution 86
(Rev. Marrakesh, 2002) of the Plenipotentiary Conference: "Coordination
and notification procedures for satellite networks" in accordance with
Resolution **86 (WRC‑03)**;

11 in accordance with Article 7 of the Convention:

11.1 to consider and approve the Report of the Director of the
Radiocommunication Bureau on the activities of the Radiocommunication
Sector since WRC‑07;

11.2 to recommend to the Council items for inclusion in the agenda for
the following WRC,

invites the Council

to consider the views given in this Resolution,

instructs the Director of the Radiocommunication Bureau

to make the necessary arrangements to convene meetings of the Conference
Preparatory Meeting and to prepare a report to WRC‑11,

instructs the Secretary-General

to communicate this Resolution to international and regional
organizations concerned.

**Reasons:** The justification for the proposed changes to Agenda item
2.1 and Agenda item 3.1 has been provided in the background section of
this proposal. The other changes, including the deletion of the word
'Preliminary' from the title of Resolution 803 (WRC‑03), the
modification of the '*resolves*', and the deletion of Agenda item 1 have
all been proposed in order to update the Agenda for 2011. It is noted
that as a result of deleting Agenda item 1, all subsequent Agenda items
will require renumbering.

Proposal for Agenda item 7.2: accommodation of new applications and
technologies

Background information

It is important that the Radio Regulations reflect and encompass
existing and new wireless technologies and services. To remain relevant,
Radio Regulations must evolve and the time-frame for effecting changes
to the Radio Regulations is somewhere in the range of 4-8 years
depending upon the timing of conferences. In an environment of
fast-evolving technology, the time and efforts required via the WRC
process may prevent administrations from accommodating new and emerging
applications, systems and technology in a timely manner. Consequently,
increased flexibility in the Radio Regulations would enable a more
responsive regulatory mechanism to rapidly developing technologies.

In response to Resolution 951 (WRC‑03), a preliminary draft report has
been developed which provides an assessment by the ITU‑R of the
effectiveness, appropriateness and impact of the Radio Regulations, with
respect to the evolution of existing, emerging and future applications,
systems and technologies. The report also identifies four possible
options for improvements in the Radio Regulations: maintaining current
practice, reviewing and possibly revising some of the current service
definitions, introducing a new provision in the Radio Regulations
enabling substitution between assignments of specific services, as well
as introducing composite services in the Table of Frequency Allocations.

Proposal

CITEL Administrations propose to submit a new agenda item to review the
Radio Regulations, in accordance with new Resolution IAP/14A2/418
(WRC‑07), to accommodate new applications and technologies, as well as
spectrum management practices, taking into account existing services.

**ADD** IAP/14A2/416

IMPROVING THE INTERNATIONAL SPECTRUM REGULATORY FRAMEWORK

***Subject:*** Proposed future WRC agenda item for WRC‑2011 improving
the international spectrum regulatory framework

***Origin:*** CITEL Administrations

***Proposal:*** to review the Radio Regulations, in accordance with new
Resolution **\[IAP/14A2/418\] (WRC‑07)**, to accommodate new
applications and technologies, as well as spectrum management practices,
taking into account existing services

***Background/reason:*** In response to Resolution 951 (WRC 03), four
possible options have been identified for improving the effectiveness,
appropriateness and impact of the RR with respect to the evolution of
existing, emerging and future applications, systems and technologies.
These four options are:

-- maintaining the current practice;

-- reviewing and possibly revising some of the current service
definitions;

-- introducing a new provision in the RR enabling substitution between
assignments of specific services; and

-- introducing composite services in the Table of Frequency Allocations.

Consistent with Resolution 71 (Rev. Antalya, 2006), which contains the
Strategic Plan of the Union for 2008-2011, in order to meet the
requirements of the membership for spectrum, orbit access and operations
in application of the Constitution, in light, *inter alia*, of the
accelerating convergence of radiocommunication services, the RR should
continue to be re appraised periodically. The ITU R studies in response
to Resolution 951 (WRC‑03) have shown that any change intended to
improve the flexibility of administrations in accommodating converging
services has to rely on a combination of service definitions,
allocations and procedures. Improving flexibility of the RR and the
timeliness of their implementation will therefore require continuation
of the studies, with more focus on the allocation and sharing issues.

***Radiocommunication services concerned:*** To be assessed.

***Indication of possible difficulties:*** To be assessed.

***Previous/ongoing studies on the issue:*** ITU‑R WP 1B has been
mandated with producing options to improve the international spectrum
regulatory framework. The results of the ITU‑R studies which have been
carried out since 2003 are to be included in the Director's Report to
WRC‑07.

The ITU‑R SG 1 report introduces the four options identified and lists
some of the procedural and regulatory implications pertaining to the
first three options, based on studies by the Special Committee.

+-----------------------------+----------------------------------------+
| ***Studies to be carried    | > ***with the participation of:*** All |
| out by:***                  |                                        |
|                             |                                        |
| ITU‑R SG 1                  |                                        |
+-----------------------------+----------------------------------------+

***ITU‑R Study Groups concerned:*** All

***ITU resource implications, including financial implications (refer to
CV126):***

***Common regional proposal:*** Yes ***Multicountry proposal:***\
Number of countries:

***Remarks***

**MOD** IAP/14A2/417

RESOLUTION 803 (Rev.WRC‑07)

Agenda for the 2011 World\
Radiocommunication Conference

The World Radiocommunication Conference (Geneva, 2007),

**ADD** IAP/14A2/417A

2.y to review the Radio Regulations, in accordance with
Resolution **\[IAP/14A2/418\] (WRC‑07)**, to accommodate new
applications and technologies, as well as spectrum management practices,
taking into account existing services;

**ADD** IAP/14A2/418

Resolution  \[IAP/14A2/418\] (WRC‑07)

Improving the international spectrum regulatory framework

The World Radiocommunication Conference (Geneva, 2007),

considering

*a)* that spectrum is a finite resource and there is an increasing
number and diversity of applications that need to be accommodated in the
radio spectrum;

*b)* that some administrations are considering a flexible allocation
framework with the aim of more efficient utilization of the spectrum on
a national basis;

*c)* that applications have been developed and implemented based on the
existing Radio Regulations;

*d)* that applications are emerging in which elements of different
radiocommunication services (as defined in the Radio Regulations) are
combined;

*e)* that some radio technologies can be used in different systems that
operate in different radiocommunication services where similar data
rates and quality of service attributes are available;

*f)* that the use of modern underlying communication architectures and
protocols, such as those used in packet radio systems, enables the
concurrent provision of different applications from the same platform
operating in the same frequency bands;

*g)* that evolving and emerging technologies, such as frequency-agile
and interference-tolerant equipment, may enable sharing between
different technologies across different allocations eliminating the need
for traditional band segmentations and consequently providing more
flexible use of the spectrum,

recognizing

*a)* that, consistent with Resolution 71 (Rev. Antalya, 2006), which
contains the Strategic Plan of the Union for 2008‑2011, in order to meet
the requirements of the membership for spectrum, orbit access and
operations in application of the Constitution, in light, *inter alia*,
of the accelerating convergence of radiocommunication services, the
Radio Regulations should continue to be re‑appraised periodically;

*b)* that as a global trend, an increasing number of administrations are
moving towards technology neutral authorizations;

*c)* that the need to harmonize internationally has a direct impact on
spectrum efficiency and economies of scale,

noting

*a)* that the purpose of the Radio Regulations is the effective
management and use of spectrum;

*b)* that ITU‑R studies[^16] have shown that any change intended to
improve the flexibility of administrations in accommodating converging
services has to rely on a combination of service definitions,
allocations and procedures,

resolves

1 to invite WRC‑11 to review the Radio Regulations, in accordance with
the Annex to this Resolution, to accommodate new applications and
technologies, as well as spectrum management practices, taking into
account existing services;

2\) to invite WRC‑11 to take appropriate actions, based on the results
of the review specified under *resolves* 1,

invites ITU‑R

to conduct the necessary studies in time for consideration by WRC‑11 and
in accordance with the Annex to this Resolution,

invites administrations

to participate actively in the studies supporting this review by
submitting contributions to ITU‑R.

ANNEX to Resolution \[iap/14a2/418\] (wrc‑07)

Scope of the Radio Regulations review

# 1 Review and possibly revise some of the service definitions

Under this approach, the current service definitions in RR Article **1**
would be reviewed in order to ensure that they adequately and clearly
cover actual use while providing flexibility for emerging technologies.
After an extensive consultation within the ITU‑R Study Groups, this
review may encompass the fixed and mobile (except aeronautical and
maritime mobile) services and possibly other services if considered
appropriate[^17]. It may lead to reviewing the current definitions for
these services and modifying them as necessary.

Possible changes to the service definitions would need to be addressed
from the point of view of their regulatory implications in the
assignment and use of frequencies, in particular in the ITU
coordination, notification and recording process, impact on assignments
made under the current definitions, and impact on other services.

# 2 Introduction of a new provision in the Radio Regulations enabling substitution between assignments of specific services

Under this approach, a new provision would be introduced in the RR in
order to enable substitution between assignments of specific services.
For example, in the context of fixed and mobile (except maritime and
aeronautical mobile) services, substitution could be applied in the same
way as it is applied by Nos. **5.485** or **5.492** in the context of
the fixed‑satellite and broadcasting‑satellite services.

Using the example of fixed and mobile services, this could reflect the
current convergence between the services, address the current
ambiguities between the definitions of these services, facilitate timely
implementation of new applications, provide adequate regulatory
protection for such applications and protect the rights of other
administrations against interference caused by them.

A new provision enabling substitution would need to be addressed from
the point of view of its regulatory implications in the assignment and
use of frequencies, in particular in the ITU coordination, notification
and recording process, impact on assignments made under the current
definitions, and impact on other services.

# 3 Introduction of composite services in the Table of Frequency Allocations

Under this approach, which could reflect the convergence between some
radiocommunication services in a specific frequency band, the Table of
Frequency Allocations (Article **5** of the RR) could be modified by
replacing the current separate allocations to some radiocommunication
services by a joint allocation to these services (e.g. a specific
frequency band allocated to the "fixed service" and to the "land mobile
service" could be modified to a composite allocation of "fixed and land
mobile service"). The above approach would only be applicable if all
concerned services, referred to in the allocation to the composite
services, have equal regulatory status.

This approach would provide administrations with increased flexibility.
In the example above, administrations could opt for either the fixed
service alone, for the land mobile service alone, for separate
applications in both services in an independent manner, or for
a composite application which would include both services. This option
would not require any revision to the current definitions of the
concerned radiocommunication services (i.e. neither to the fixed nor to
the land mobile service).

To enable notification and recording of frequency assignments in such
composite service, a new class of station could be introduced named
"Station in the fixed and land mobile service" (with a separate symbol
than those used for the fixed and for land mobile service), with
appropriate forms of notice, or other adequate notification mechanisms.

**Reasons (IAP/14A2/416, IAP/14A2/417, IAP/14A2/418):** To add a new
agenda item to review the Radio Regulations, in accordance with new
Resolution \[IAP/14A2/418\] (WRC‑07), to accommodate new applications
and technologies, as well as spectrum management practices, taking into
account existing services.

**SUP** IAP/14A2/419

RESOLUTION 951 (WRC-03)

Options to improve the international spectrum\
regulatory framework

**Reasons:** The results of ITU‑R studies in response to Resolution 951
(WRC‑03) are included in the Director's Report. Consequently, the task
called for in Resolution 951 (WRC‑03) has been completed and options
have been identified for improvements in the Radio Regulations. The
proposed Resolution \[IAP/14A2/418\] (WRC‑07) intends to further the
studies in this regard, and consequently Resolution 951 (WRC‑03) should
be suppressed.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_

[^1]: Note that AM(R)S allocations in the band 108-117.975 MHz are only
    being considered by the United States for new aviation navigation
    surveillance technology consistent with No. 5.197A.

[^2]: ^1^ *xx* equals 2% if an allocation to the aeronautical mobile
    service for the use of aeronautical mobile telemetry in the band
    5 091-5 150 MHz is made by WRC-07 under Agenda item 1.5, and 3%
    otherwise.

[^3]: ^41^ If the payments are not received in accordance with the
    provisions of Council Decision 482, as amended, on
    the implementation of cost recovery for satellite network filings,
    the Bureau shall cancel the publication specified in § 6.11 and the
    corresponding entries in the List under § 6.27 or 6.29, as
    appropriate, after informing the administration concerned. The
    Bureau shall inform all administrations of such action and that the
    network specified in the publication in question no longer has to be
    taken into consideration by the Bureau and other administrations.
    The Bureau shall send a reminder to the notifying administration not
    later than two months prior to the deadline for the payment
    specified in the above‑mentioned Decision 482, unless the payment
    has already been received (see also Resolution **87
    (WRC‑03)**).     (WRC‑0[7]{.underline}~~3~~)

    ^4^ \[^ADD\ 6.1^ The "other provisions" shall be identified and
    included in the Rules of Procedure.\] (Note of Editor)

[^4]: ^ADD\ 6.22^ The "other provisions" shall be identified and
    included in the Rules of Procedure.

[^5]: ^ADD\ 6.29^ The entry shall be definitive in the case of a
    frequency assignment to a receiving station, under the condition
    that the notifying administration has undertaken that no complaint
    will be made in respect of any harmful interference which may be
    caused to that assignment by the assignment which was the basis for
    the unfavourable finding.

[^6]: ^4^ The "other provisions" shall be identified and included in the
    Rules of Procedure.     (WRC-03)

[^7]: ^5^ [The rain rate corresponds to the rain rate which is exceeded
    for the worst 0.01% of the time in an average year in accordance
    with]{.underline} *[recommends]{.underline}* *[2]{.underline}* [of
    Recommendation
    ITU]{.underline}‑[R]{.underline} [P.837-4.]{.underline}

[^8]: ^\*^ Figure 2 represents patterns for same combinations of
    *B~min~* and ~0~.     (WRC-03)

[^9]: ^1^ For the purpose of this Annex, "interfered-with satellite
    network" could refer to operational satellite networks, assignments
    in the List, networks for which the Bureau has already received
    complete information, and allotments in the Plan.

[^10]: ^1^ WRC-97 made editorial amendments to this Resolution.

[^11]: ^^ Distress and safety communications include distress, urgency
    and safety calls and messages.

[^12]: ^1^ These stations may include rescue coordination centres. The
    term "Rescue Coordination Centre" as defined in the International
    Convention on Maritime Search and Rescue (1979) refers to a unit
    responsible for promoting the efficient organization of search and
    rescue services and for coordinating the conduct of search and
    rescue operations within a search and rescue region.

[^13]: ^2^ The use of the Standard Marine Communication Phrases and,
    where language difficulties exist, the International Code of
    Signals, both published by the International Maritime Organization,
    is also recommended.

[^14]: ^3^ Mobile stations communicating with the stations of the
    aeronautical mobile (R) service in bands allocated to the
    aeronautical mobile (R) service shall conform to the provisions of
    the Regulations which relate to that service and, as appropriate,
    any special arrangements between the governments concerned by which
    the aeronautical mobile (R) service is regulated.

[^15]: ^7^ Alarm signals may consist of transmissions of sinusoidal
    audio frequency tones 1 300 Hz, 2 200 Hz, or both. Different tone
    generation patterns may be used to signal the type of message which
    follows, and an alarm signal ending in a 10-second continuous tone
    could be used to identify a transmission by a coast station.

[^16]: ^1^ *Editor's Note:* These studies were conducted in response to
    Resolution **951 (WRC‑03)**.

[^17]: ^2^ The ITU‑R studies indicated that the current definition of
    the fixed‑satellite service has been able to accommodate new
    technologies and applications in the fixed‑satellite service.